Installing the OpsMJE z/OS Connect EE Interceptor

Install the API Requester Interceptor by using symlink (preferred method)

1. Depending on your setup, perform one of the following actions:

   • If the API Requester Interceptor is already installed using symlink, the API Requester Interceptor is automatically updated the next time the interceptor loads or the server restarts.

     Important

     If you change the path of the runtime library, you must renew the symlink.

     To renew the symlink:

     1. Unlink the symlink using the MJEINSU0 job.
     2. Renew the symlink by running the MJEINSL0 job (as described in Step 3).
   • If the API Requester Interceptor is not installed, proceed to Step 2.
     

2. Make sure that the following directories exist:

   • $WLP_USER_DIR/extension
   • $WLP_USER_DIR/extension/lib
   • $WLP_USER_DIR/extension/lib/features

   WLP_USER_DIR is the directory in which your server.xml file resides.

   
   

3. Customize and run BBSAMP job MJEINSL0.

   1. Create the following symlink that points to runtimeLibrary/com.bmc.mje.interceptor.jar: 

      $WLP_USER_DIR/extension/lib/com.bmc.mje.interceptor.jar

   2. Create the following symlink that points to runtimeLibrary/com.bmc.mje.feature.mf:

      $WLP_USER_DIR/extension/lib/features/com.bmc.mje.feature.mf 
4. Configure and activate the API Requester Interceptor in the server.xml file. For more information, see Configuring-the-OpsMJE-z-OS-Connect-Interceptor-for-z-OS-Connect-EE-servers.

Install the API Requester Interceptor by using the IBM installUtility command

1. Depending on your setup, perform one of the following actions:

   • If the API Requester Interceptor is already installed, using the installUtility command, uninstall the mjeZconnInterceptor.
     For more information about using the installUtility command, see Installing assets using the installUtility command in the IBM WebSphere Application Server Liberty documentation.

     Important

     • You must stop all servers before you uninstall a feature.
     • If you previously installed the mjeZconnInterceptor using symlink, unstalling with the installUtility removes the symlink.
   • If the API Requester Interceptor is not installed, proceed to Step 2.
2. Customize and run MJEINES1 to install the mjeZconnInterceptor using installUtility.
3. Configure and activate the API Requester Interceptor in the server.xml file. For more information, see Configuring-the-OpsMJE-z-OS-Connect-Interceptor-for-z-OS-Connect-EE-servers.

Upgrading from version 3.3.00 to 4.1.00

If you upgrade from version 3.3.00 to 4.1.00, to start z/OS Connect EE, you must use the --clean parameter option. For more information, see zosconnect command syntax in the IBM z/OS Connect (OpenAPI 2) documentation.