Installing the Binaries
As a first step download the trail version of the message broker binaries from IBM site and install them. this part is very simple and process is depends on your operating system. Like for windows, you have .exe file and Linux has rpm and unix you get pkg or other.
After installation
[Windows]
__ 1. Create the broker database, BRKDB.
Open a WebSphere Message Broker Command Console: mqsicreatedb BRKDB
This command also establishes the required ODBC connection.
__ 2. Verify your user account for the broker database.
[Linux]
If you are creating Oracle databases for 32-bit brokers on Linux® and UNIX® systems, run the mqsi_setupdatabase command before you create a database.
mqsi_setupdatabase– Database–Database_Home_Directory
Eg:mqsi_setupdatabase oracle /oracle/product/9i/Db_1
Add $ORACLE_HOME/lib to the end of the MQSI_LIBPATH library search path environment variable
- Copy the odbc32.ini sample file that is supplied in the install_dir/ODBC32/V5.3 directory to a location of your choice; for example, copy the file to your user ID's home directory.
- Ensure that the odbc32.ini file has file ownership of mqm:mqbrkrs, and has the same permissions as the supplied odbc32.ini sample file.
- Set the ODBCINI32 environment variable to point to your odbc32.ini file, specifying a full path and file name. For Linux on x86 only, use the ODBCINI environment variable. On AIX®, HP-UX, Solaris on SPARC, and Linux on x86-64, set the 32-bit library search path environment variable MQSI_LIBPATH32 to show the location of the 32-bit libraries for the database manager that you are using.
For example, on AIX:
export MQSI_LIBPATH32=$MQSI_LIBPATH32:DB2_instance_directory/sqllib/lib32
On Linux on x86 only, set the 32-bit library search path LD_LIBRARY_PATH to show the location of the 32-bit libraries for the database manager.
- Edit the final stanza in the odbc32.ini file (the [ODBC] stanza) to specify the location of the ODBC Driver Manager, and to control tracing.
# In InstallDir, add the WebSphere Message Broker installation location to complete the fully qualified path to the ODBC directory. If you do not set this value correctly, the ODBC definition will not work.
# In Trace, set the value to 0; if your IBM service representative asks you to enable ODBC trace, set the value to 1.
# Start of changeIn TraceOptions, set the value to 3.End of change
# In TraceFile, type the fully-qualified path and file name to which the ODBC trace is written. Trace files can become large; specify a directory with plenty of free disk space.
# In TraceDll, add the WebSphere Message Broker installation location to complete the fully qualified path to the ODBC trace DLL.
# Accept the default values that are shown in the sample odbc32.ini file for all the other entries in the stanza.
Rest of the story you can read at : http://josephamrithraj.gizapage.com (Websphere blog)
As a first step download the trail version of the message broker binaries from IBM site and install them. this part is very simple and process is depends on your operating system. Like for windows, you have .exe file and Linux has rpm and unix you get pkg or other.
After installation
Set up a broker database__ 1. Create the broker database, BRKDB.
Open a WebSphere Message Broker Command Console: mqsicreatedb BRKDB
This command also establishes the required ODBC connection.
__ 2. Verify your user account for the broker database.
[Linux]
If you are creating Oracle databases for 32-bit brokers on Linux® and UNIX® systems, run the mqsi_setupdatabase command before you create a database.
mqsi_setupdatabase– Database–Database_Home_Directory
Eg:mqsi_setupdatabase oracle /oracle/product/9i/Db_1
Add $ORACLE_HOME/lib to the end of the MQSI_LIBPATH library search path environment variable
Connecting to a database from Linux/Unix- Ensure that the odbc32.ini file has file ownership of mqm:mqbrkrs, and has the same permissions as the supplied odbc32.ini sample file.
- Set the ODBCINI32 environment variable to point to your odbc32.ini file, specifying a full path and file name. For Linux on x86 only, use the ODBCINI environment variable. On AIX®, HP-UX, Solaris on SPARC, and Linux on x86-64, set the 32-bit library search path environment variable MQSI_LIBPATH32 to show the location of the 32-bit libraries for the database manager that you are using.
For example, on AIX:
export MQSI_LIBPATH32=$MQSI_LIBPATH32:DB2_instance_directory/sqllib/lib32
On Linux on x86 only, set the 32-bit library search path LD_LIBRARY_PATH to show the location of the 32-bit libraries for the database manager.
- Edit the final stanza in the odbc32.ini file (the [ODBC] stanza) to specify the location of the ODBC Driver Manager, and to control tracing.
# In InstallDir, add the WebSphere Message Broker installation location to complete the fully qualified path to the ODBC directory. If you do not set this value correctly, the ODBC definition will not work.
# In Trace, set the value to 0; if your IBM service representative asks you to enable ODBC trace, set the value to 1.
# Start of changeIn TraceOptions, set the value to 3.End of change
# In TraceFile, type the fully-qualified path and file name to which the ODBC trace is written. Trace files can become large; specify a directory with plenty of free disk space.
# In TraceDll, add the WebSphere Message Broker installation location to complete the fully qualified path to the ODBC trace DLL.
# Accept the default values that are shown in the sample odbc32.ini file for all the other entries in the stanza.
Rest of the story you can read at : http://josephamrithraj.gizapage.com (Websphere blog)
Comments
Post a Comment