Installing the IBM Integration feature: z/OS

Learn about how to install IBM® Integration Administration for WebSphere® Application Server on z/OS®.

Before installing the IBM Integration Administration package, complete the following preparation steps:

1. Identify the file system locations that are used in the installation.
   The instructions use the following variables to represent these locations:

   WAS_HOME

   This term represents the location of your server configuration, and its value is usually assigned to the $WAS_HOME environment variable. The path typically ends with /AppServer. $WAS_HOME/bin is the path that you specify for WebSphere Application Server commands such as startServer.sh.

   WAS_RO_HOME

   This term represents the location of the WebSphere Application Server product installation files that are referenced from the server configuration. Its value is not assigned by default to an environment variable. It is usually defined to be read-only. The path to WAS_RO_HOME/systemApps/isclite.ear/isclite.jar typically has no symbolic links.

2. Ensure that your user ID has write access to both WAS_HOME and WAS_RO_HOME, and has administrative authority to make WAS_RO_HOME writable.
3. For WebSphere Application Server V8, you must set the program control on the bbgjutil module. A user ID with administrative authorities is required to set this control.
   For example:

   extattr +p WAS_HOME/lib/s390x9-64/bbgjutil
   extattr +p WAS_HOME/lib/s390x-64/bbgjutil

4. Copy the installation file wmb.admin.zos.tar to a suitable location on your WebSphere Application Server system.
   The file is installed as part of your IBM Integration Bus installation at the following location:

   • On Windows: install_dir\server\tools\wmb.admin.zos.tar
   • On Linux® and z/OS: install_dir/server/tools/wmb.admin.zos.tar

   where install_dir is the IBM Integration Bus installation directory.
5. Create a directory into which to extract the contents of wmb.admin.zos.tar. The creating user ID is automatically given write access to the directory.
   For example, run the following command:

   mkdir /tmp/unpack

6. Extract the files from wmb.admin.zos.tar into the directory that you created.
   For example, from directory /tmp/unpack, enter the following command:

   tar -xvf wmb.admin.zos.tar

   You can now see three new files in this directory:

   • installBrokerPlugin.sh
   • uninstallBrokerPlugin.sh
   • wmb.admin.tar
7. Ensure that the files are executable.
   For example, run the following command:

   chmod a+x *.sh

8. Create a new directory to permanently contain the IBM Integration Bus installation files. The creating user ID is automatically given write access to the directory.
   For example, run the following command:

   mkdir /my/brokerplugin

To install the IBM Integration Administration package, complete the following steps:

9. First, ensure that any servers created from this WebSphere Application Server installation are stopped.

   Navigate to the WAS_HOME/bin directory. On a command line, enter the following command:

   stopServer server1 -profileName profileName

   server1 is the name of the application server.

   profileName identifies the profile of the server process in a multi-profile installation. This parameter is not required for a single-profile installation.

10. Go to the location where the installation files were unpacked.
    For example, run the following command:

    cd /tmp/unpack

11. If the WAS_RO_HOME directory is read-only, set it as writable during the installation.
    For example, run the following command:

    chmount -w WAS_RO_HOME

12. As a user with administrative authorities, run the installation script installBrokerPlugin.sh. This script generates a large amount of output, so direct this output to a file or to a utility such as more to read it easily.
    For example, run the following command:

    ./installBrokerPlugin.sh -u extract_location -d was_install_root -f tar_file

    • extract_location is the directory into which wmb.admin.tar is to be extracted. In this example /my/brokerplugin would be used.
    • was_install_root is the WAS_HOME directory if you are using WebSphere Application Server V7, or the WAS_RO_HOME directory if you are using WebSphere Application Server V8.
    • tar_file is the full path and file name for wmb.admin.tar. In this example /tmp/unpack/wmb.admin.tar would be used.

    The script returns information about any running WebSphere Application Server processes that are preventing the installation from completing. These processes must be stopped before the script is run again.

13. If the WAS_RO_HOME directory was set to writable, set it back to read-only.
    For example, run the following command:

    chmount -r WAS_RO_HOME

14. Restart any WebSphere Application Server servers that were previously stopped.