Before you begin
Check that you have set up your environment
so that the integration node can connect to the database. Most database
managers set up the required environment when you install, but others
supply a database profile that you must run. For information about
environments and running database profiles, see Running database setup scripts.
About this task
Configure
an ODBC data source by using the ODBC Data Source Administrator:
- Click .
- Click the System DSN tab and click Add.
- Complete the steps in the following sections for the databases
that you are working with.
If you need more information about a
particular database product, see the product-specific documentation.
- DB2® UDB
- Define a data source for DB2 UDB:
- Select the driver IBM DB2 ODBC DRIVER.
- Enter the data source name (DSN) and description.
- Select the correct database alias from the list.
- Click Finish to save your definition.
- Click OK to close the ODBC Data
Source Administrator.
- If you need to use Global Coordination with
your database from IBM® Integration Bus on Windows systems, the next task is
to set up the 32-bit environment that is needed by WebSphere® MQ, see Setting your environment to support access to databases.
You must register the data source as a system data source.If you prefer, you can use the Configuration Assistant
instead of the ODBC Data Source Administrator:
- Open the DB2 Configuration
Assistant.
- Right-click the database and 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
- Define a data source for Informix Dynamic
Server:
- Select the driver IBM INFORMIX ODBC DRIVER.
- On the Connection tab, specify:
- The Informix server name.
- The server host name.
- The Informix network service
name (as defined in the services file).
- The network protocol (for example, olsoctcp).
- 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 close the ODBC Data
Source Administrator.
- Microsoft SQL Server
- Define a data source for Microsoft SQL
Server:
- Select the driver for the version of SQL Server that you are using:
- SQL Native Client 10.0 for SQL Server 2008.
- SQL Native Client 11.0 for SQL Server 2012, 2014, and 2016.
- Specify a name and description.
- Select the correct server from the list.
- To specify the authentication mode that
is used by the server:
- Click Next.
- Select the authentication mode.
- Click Back to move back to the first panel.
- Click Finish to save your definition.
- Click OK to close the ODBC Data
Source Administrator.
- Oracle
- Define a data source for Oracle:
-
- Select the driver IBM Integration
Bus (10.0.0.n)
DataDirect Technologies 64-BIT Oracle Wire Protocol where n is
the level of the installed fix pack.
The ODBC Oracle Driver Setup dialog box
opens.
- On the General tab:
- Enter the DSN name, description, and host name of the machine
where Oracle is running, the port number on which Oracle is listening,
and the Oracle Service Name that you want to connect to.
- On the Advanced tab:
- Select Enable SQLDescribeParam.
- Select Procedure Returns Results.
The resultant ODBC definition in the Windows registry has
a string value that is called ProcedureRetResults with
the value 1.
- Select Login Timeout and set
the value to 0.
- Ensure that Enable N-CHAR is not selected.
- If you are using TIMESTAMP WITH TIMEZONE columns, select Enable Timestamp With Timezone.
- In Extended Options, enter:
WorkArounds=536870912;
- Oracle using Secure Socket Layer (SSL) authentication
Complete the steps for Oracle above.
Then, complete these
additional steps:
- Reopen the ODBC Oracle Driver Setup dialog
box, see Step 1 for Oracle above.
- On the Security tab:
- In the Authentication section, set the Authentication
Method to Encrypt Password.
- In the Encryption Section, set the Encryption
Method to SSL Auto.
- Select the check box if you want to validate the Server
certificate.
- Enter a fully qualified path for your Trust Store.
- Enter your Trust Store Password.
- Enter a fully qualified path for your Key Store.
- Enter your Key Store Password.
- Enter your SSL Key Password.
- Click OK to close the ODBC Data Source
Administrator.
- Oracle using Advanced Security (OAS)
-
Complete the steps for Oracle above.
Then,
complete these additional steps:
- Reopen the ODBC Oracle Driver Setup dialog
box, see Step 1 for Oracle above.
- On the Advanced Security tab:
- Select the Encryption Level that you want to use. Choose from
the following options:
- 0 - Rejected. If rejected, or no match is found between the driver
and server encryption types, data that is sent between
the driver and the database server is not encrypted or
decrypted. If the Oracle server has its sqlnet.encryption_server setting
set to "REQUIRED" and this option is selected, then the
connection to the Oracle database fails.
- 1 - Accepted. Encryption is used on data that is sent
between the driver and the database server if the database
server requests or requires it.
- 2 - Requested. Data that is sent between the driver and
the database server is encrypted and decrypted if the
database server permits it.
- 3 - Required. Data that is sent between the driver and the database
server must be encrypted and decrypted. If the Oracle
server has its sqlnet.encryption_server setting
set to "REJECTED" and this option is selected, then the
connection to the Oracle database fails.
- Select the Encryption Types that you want to use.
- Select the Data Integrity Level you want to use. Choose from
the following options:
- 0 - Rejected. A data integrity check on data that is sent between
the driver and the database server is refused. If the
Oracle server has its sqlnet.crypto_checksum setting
set to "REQUIRED" and this option is selected, then the
connection to the Oracle database fails.
- 1 - Accepted. A data integrity check can be made on data
that is sent between the driver and the database server.
Data integrity is used if the database server requests
or requires it.
- 2 - Requested. The driver enables a data integrity check
on data that is sent between the driver and the database
server if the database server permits it.
- 3 - Required. A data integrity check must be performed on data
that is sent between the driver and the database server.
If the Oracle server has its sqlnet.crypto_checksum setting
set to "REJECTED" and this option is selected, then the
connection to the Oracle database fails.
- Select the Data Integrity Types that you want to use.
- Click OK to close the ODBC Data Source
Administrator.
- Sybase Adaptive Server Enterprise
- Define a data source for Sybase Adaptive Server Enterprise:
-
- Select the driver IBM Integration
Bus (10.0.0.n)
DataDirect Technologies 64-BIT Sybase Wire Protocol where n is
the level of the installed fix pack.
- Enter the DSN name, description, and network address
of the server, where the network address is made up of MyHostMachineName,MyHostMachinePortNumber.
- On the Advanced tab:
- On the Performance tab:
- Ensure that the Prepare Method setting
is 1 - Partial.
- solidDB
- Define a data source for solidDB:
- Select the driver IBM solidDB - (Unicode) DRIVER.
- Enter the description.
- Enter the communication port in the network location field, for
example, tcp 2315.
- Click Finish to save your definition.
- Click OK to close the ODBC Data Source
Administrator.
Results
You have now configured your ODBC data
source names on
Windows.