Configure an ODBC data source using the
ODBC Data Source Administrator:
- Click .
- Click the System DSN tab.
When you define a new data source, select the appropriate driver for
your database and complete the dialog that is displayed. Refer to your relevant
database product documentation for more information.
Setup considerations
specific to WebSphere Message Broker are described below
for the supported databases.
The Default
Configuration wizard and the database commands to create a broker,
or a database, on Windows automatically create the ODBC data source
names (DSNs) for you.
- DB2® UDB
- When you define a data source for DB2 UDB you must choose the driver:
- Enter the data source name (DSN) and description.
- Select the correct database alias from the list.
You must register the data source as a system data source.You
might find it easier to use the Configuration Assistant:
- Open the DB2 Configuration
Assistant.
- Right-click the database. Select Change Database.
- Select Data Source.
- Select Register this database for ODBC. Select
the system data source option.
- Click Finish.
- The Test Connection dialog opens automatically and
you can test the various connections.
- Informix® Dynamic
Server
- When you define a data source for Informix Dynamic Server, choose the
driver:
Complete these steps to configure the driver:
- On the Connection tab, specify:
- The Informix server
name.
- The machine host name.
- The Informix network
service name (as defined in the services file).
- The network protocol (for example, olsotcp).
- The Informix data
source name.
- The user identifier to access the data source within.
- The password for that user identifier.
- Click Apply.
- Click Test Connection to check your supplied values.
- Click OK to finish.
- Microsoft® SQL
Server
- When you define a data source for Microsoft SQL Server you must choose
the driver:
The driver level must be Version 3.60, or later.
- Specify a name and description.
- Select the correct server from the list.
- Oracle
- When you define a data source for Oracle, choose the driver:
- MQSeries DataDirect Technologies 5.20
32-BIT Oracle
The ODBC Oracle Driver Setup dialog opens.
Complete
these steps to configure the driver:
- On the General tab:
- Enter the DSN name, description, and server name (where the server name
is the "Service Name" that resolves to a "Connect Descriptor", for example
through a mapping in the TSNAMES.ORA file).
- Select the appropriate Oracle client version from the list.
- On the Advanced tab:
- Select Enable SQLDescribeParam.
- Select Procedure Returns Results. The
resultant ODBC definition in the Windows registry has a string value
called ProcedureRetResults with the value 1.
- Click .
- Type REGEDIT in the Open field.
- Click OK.
- Use REGEDIT to navigate to the correct location. Create
a new registry subkey for each of your DSNs that reference an Oracle database.
HKEY_LOCAL_MACHINE
SOFTWARE
ODBC
ODBC.INI
- Click OK to close ODBC Data Source Administrator.
- Right-click DSN. Select .
- Specify WorkArounds for the string.
- Right-click WorkArounds.
- Select Modify.
- Type the data value 536870912.
- Sybase Adaptive Server Enterprise
- When you define a data source for Sybase Adaptive Server Enterprise, choose
the driver:
- MQSeries DataDirect Technologies
5.20 32-BIT Sybase Wire Protocol
Complete these steps to configure the driver:
- Enter the DSN name, description, and network address of the server (for
a description of the format of this address, see the explanation for NetworkAddress= in odbc.ini sample file).
- Select Enable Describe Parameter. This parameter
is on the Advanced tab.
- Ensure the Prepare Method setting is 1 -
Partial. This parameter is on the Performance tab.
- Use REGEDIT to navigate to the correct location. Create
a new registry subkey for each of your DSNs that reference an Sybase database.
HKEY_LOCAL_MACHINE
SOFTWARE
ODBC
ODBC.INI
- Right-click the DSN, and select . Specify SelectUserName for
the string, and set the value to 1.
You have now configured your ODBC data source
names on Windows.
Next:
You must configure the environment for issuing console commands, and for running the broker, so that the broker can access the required database libraries. For more information, see Setting your environment to access databases.