When we create any configured operation in SQL Server Intelligent adapter, we have to specify 1st the user name and when we select the user name the list of tables owned by the user are displayed. Generally all tables in SQL Server are owned by dbo.
But if in our case the table is not owned by DBO and we have different users in development database and production database. After importing the development integration in the production, I have to manually go and chg the user name field in all the integration component. Otherwise the integration does not work.
In this case we are specifically changing the code after moving it in production. How to avoid such problem?
Use the user name to get access to the table first and then select the user tab to select a ‘blank’ user.
This way you can select only the table and when you migrate this to production
This is also a prime candidate for using configuration files. There was a discussion about it last week. Read up at [url=“wmusers.com”]wmusers.com.
can u tell me what driver is required to configure the sql server(intelligent) adapter.what parameter need to pass on “Add to CLASSPATH” Tab. i am unable to configure the SQL server adapter.u need to install SQL client first before configuring the adapter???.
Ur responce will be highly appreciated,
You don’t need a driver for SQL Server adapter. And you don’t need to add any classpath also. Only the server name, user, password are enough.
If you give any specific error it will be helpfull.
ok fine i just gave the username,servername and password but it is giving error. do i need to install sql client before configuring the adapter.
Your problem is what occurs in everyday situation at our workplace. SQL Server, AS400 or DB2. All these databases get their configured operations reset when you import the Integration components.
The best way (not the wM recommended way atleast) is to export the component as an adl. Open the adl either in NotePad or TextPad, look for the Userid, replace it with the Production’s Userid and save the adl. No changes anywhere other than where you require to do so.
Now import the adl, and LO!!!, you should have the exact userid and table name as needed for your Production environment in your Integration.
Hope this helps.