Create and Test ODBC / Data sources IBM WebSphere Message Broker v8 on Linux www.mwschool.in | Ankil Patel   Objective: Set and Test ODBC data sources connections for broker in IBM WebSphere Message Broker v8. Steps: • Edit odbc.ini with following information. Here is an info-center pointer – o http://www01.ibm.com/support/knowledgecenter/?lang=en#!/SSKM8N_8.0.0/com.ibm .etools.mft.doc/bk58070_.htm o You can get necessary information to complete the mandatory fields of stanzas in the odbc.ini from your organization’s DBA, Security Analyst and/or Windows/Unix Engineer. o Example of odbc.ini. [ODBC Data Sources] DB_NAME=IBM DB2 ODBC Drive ;# DB2 stanza [DB_NAME] DRIVER=/opt/IBM/path/to/libdb2o.so Description=IBM DB2 ODBC Database Database=DB2INST1 • Next is, edit/update environment profile to include ODBCINI and ODBCSYSINI pointing to actual odbc.ini and odbcinst.ini respectively. • To create data source connection for your broker, use mqsisetdbparms command. o mqsisetdbparms can be executed when broker is running but you must stop and start the execution group(s) associated with the datasource you are dealing with. o For basic connection setup you will need following.  Name of the broker. BRKNAME.  Name of the resource, may be the database instance. DB_NAME.  Username and Password that have enough access to the database we targeting here. USER, PWD. This username must have ability to accept inbound connections on the database server. o Execute the following command –  mqsisetdbparms BRKNAME -n DB_NAME -u USER -p PWD • Restart either broker or EG – execution group related to the database connection. • You have three ways to test connection – 1. Tail the sys log while the instance was being restarted. Newer version of broker tests the database connection while starting up. 2. If you have database client installed on your broker machine, use it. 3. Run native broker command called – mqsicvp.  To test all defined connections in odbc.ini, execute – • mqsicvp BRKNAME  To test any particular database connection, execute – • mqsicvp BRKNAME -n DB_NAME -u USER -p PWD • If the test connection fails and you are sure that the configuration you built is perfect, it could be happening because of firewall. o Try telnet to verify that firewall is not blocking the communication.  telnet

Ankil  Patel      |      [email protected]      |      http://www.mwschool.in      |      Last  saved:  7/11/14