Setting up Message Broker environment
Setting up the command environment
After you have installed the product on any of the distributed systems, you must initialize the environment before you can use any runtime component or command.
When you start a runtime component on Linux and UNIX systems, it inherits the environment from where you issue the mqsistart command. You must therefore initialize the environment before you start a component; the command mqsiprofile located in the directory install_dir/bin, performs this initialization.
You must not change the location of the mqsiprofile command, or make user modifications to the command, because it might be replaced if you install service, or an update, to the product.
If you want to run your own additional environment settings, add a script called your_file_name.sh to the broker’s work_path directory which contains the: /common/profiles subdirectory. When you run mqsiprofile again, the command automatically calls the additional user-written scripts in this location. The newly added script will not be picked up if you run an mqsistart command from an existing initialized command shell. work_path identifies the broker’s working directory; if you are unsure of the broker’s work path, enter the following command: echo $MQSI_WORKPATH
-> Issue the mqsiprofile command: . install_dir/bin/mqsiprofile
You must include the period and space preceding the location for this invocation to work correctly. Add this command to your login profile if you want it to be run at the start of every session.
This command accesses additional scripts that you have copied to the common/profiles directory, therefore the environment is initialized for runtime components and other resources such as databases.
-> Start the components that you want to run on this system using the mqsistart command.
=>Running database setup scripts
A broker requires access to a database to maintain operational and state data, and might also require access to user databases from deployed message flows.
When you install a database product on Linux and UNIX systems, some database managers provide a profile to perform the environment set up that the database requires, or provide details of actions that you must take in their documentation.
# If you can update the profile (mqsiprofile script) to provide permanent values for the details that are required (for example, the database server name or the installation directory):
1. Complete the changes to the profile.
2. Copy the profile file to the directory work_path\common\profiles.
# If you cannot update the profile permanently, but need to make changes each time, you must run it independently of the mqsiprofile command:
Run the appropriate profiles to initialize the environment for the database:
DB2: . db2_instance_directory/sqllib/db2profile
Oracle: . ${ORACLE_HOME}/bin/oraenv
Note: If you have installed 64-bit instances of DB2 or 64-bit Oracle databases, you need to complete additional setup steps, including adding 32-bit libraries to the LIBPATH.
Setting up the command environment
After you have installed the product on any of the distributed systems, you must initialize the environment before you can use any runtime component or command.
When you start a runtime component on Linux and UNIX systems, it inherits the environment from where you issue the mqsistart command. You must therefore initialize the environment before you start a component; the command mqsiprofile located in the directory install_dir/bin, performs this initialization.
You must not change the location of the mqsiprofile command, or make user modifications to the command, because it might be replaced if you install service, or an update, to the product.
If you want to run your own additional environment settings, add a script called your_file_name.sh to the broker’s work_path directory which contains the: /common/profiles subdirectory. When you run mqsiprofile again, the command automatically calls the additional user-written scripts in this location. The newly added script will not be picked up if you run an mqsistart command from an existing initialized command shell. work_path identifies the broker’s working directory; if you are unsure of the broker’s work path, enter the following command: echo $MQSI_WORKPATH
-> Issue the mqsiprofile command: . install_dir/bin/mqsiprofile
You must include the period and space preceding the location for this invocation to work correctly. Add this command to your login profile if you want it to be run at the start of every session.
This command accesses additional scripts that you have copied to the common/profiles directory, therefore the environment is initialized for runtime components and other resources such as databases.
-> Start the components that you want to run on this system using the mqsistart command.
=>Running database setup scripts
A broker requires access to a database to maintain operational and state data, and might also require access to user databases from deployed message flows.
When you install a database product on Linux and UNIX systems, some database managers provide a profile to perform the environment set up that the database requires, or provide details of actions that you must take in their documentation.
# If you can update the profile (mqsiprofile script) to provide permanent values for the details that are required (for example, the database server name or the installation directory):
1. Complete the changes to the profile.
2. Copy the profile file to the directory work_path\common\profiles.
# If you cannot update the profile permanently, but need to make changes each time, you must run it independently of the mqsiprofile command:
Run the appropriate profiles to initialize the environment for the database:
DB2: . db2_instance_directory/sqllib/db2profile
Oracle: . ${ORACLE_HOME}/bin/oraenv
Note: If you have installed 64-bit instances of DB2 or 64-bit Oracle databases, you need to complete additional setup steps, including adding 32-bit libraries to the LIBPATH.
Comments
Post a Comment