Running database setup scripts before starting an integration node

Configure an integration server to access databases from deployed message flows by customizing the command environment. This process is relevant only when you are starting an integration node.

When you install a database product, the relevant settings might be made to the system environment (typical for Windows systems). However, some database managers provide a profile to perform this setup, or provide details of actions that you must take. Always check the database product documentation for environment setup details; the information that is provided here is for general guidance only.

If a profile is provided for the database that you are using, complete the following process:

If you can update the profile to provide permanent values for the details that are required (for example, the database server name or the installation directory), complete Step 1. You must also complete either Step 2 or Step 3. If you cannot update the profile to provide permanent values, then you must complete Step 4

  1. Complete the changes to the database profile.
  2. If your platform is Windows copy the profile file to the appropriate directory:
    • For an HA integration node, use shared_work_path\config\node_name\profiles.
    • If the integration node was created with a specified work path, which has a subdirectory workPath\config\node_name\profiles, then use that profiles directory.
    • In the default case, use %MQSI_REGISTRY%\config\node_name\profiles.
  3. If your platform is Linux® or UNIX copy the profile file to the appropriate directory:
    • For an HA integration node, use shared_work_path/common/profiles.
    • If the integration node was created with a specified work path, under which has a subdirectory work_path/config/node_name/profiles, then use that profiles directory.
    • In the default case, use ${MQSI_REGISTRY}/config/node_name/profiles.
  4. If you cannot update the profile permanently, but need to make changes repeatedly, you must edit it in the appropriate directory as specified in Step 2 or Step 3. You must edit the profile each time before you start the integration node.
Note:
The directory, workPath is the machine-wide IBM® App Connect Enterprise working directory. To verify the machine-wide IBM App Connect Enterprise working directory, enter the following command in a command console:
echo %MQSI_WORKPATH%

The directory, shared_work_path is the working directory for a multi-instance integration node.

For more information about the parameters for the working directory of an integration node, see ibmint create node command, and mqsicreatebroker command - Windows systems.