Configuring z/OS Connect Enterprise Edition

z/OS® Connect Enterprise Edition is a separately-orderable product; it is not supplied as part of CICS® TS. It extends the basic services of z/OS Connect for CICS 1.0 with extra capabilities and can be used to host CICS' older JSON web services-based services, and also the standard z/OS Connect deployment artifacts such as SAR and AAR files. You must configure a JVMSERVER resource before you can deploy JSON services, and can also configure a PIPELINE resource. This initial configuration is required only once.

Before you begin

Install the z/OS Connect Enterprise Edition run time. Follow the instructions in the z/OS Connect Enterprise Edition V3.0 product documentation. If you are preparing z/OS Connect Enterprise Edition to run embedded in CICS, you do not need to create a separate Liberty server instance. You must ensure that the file system components are available on zFS. Installation of the API Toolkit that is supplied with z/OS Connect Enterprise Edition is not part of this task.

About this task

If you installed z/OS Connect for CICS 1.0 previously, you might have a suitable configuration already and can omit some steps in the following task. The steps that you can omit are indicated in the procedure.

Procedure

  1. Create a JVMSERVER resource and configure it to support a WebSphere® Liberty server. For more information about creating a WebSphere Liberty JVMSERVER, see Configuring a Liberty JVM server.

    If you installed z/OS Connect for CICS 1.0 previously, you can omit this step.

  2. Add ZCEE_INSTALL_DIR to your JVM server options.
    For more information about the option and an example, see JVM server options.
  3. If you are using z/OS Connect Enterprise Edition version 3.0.24.0 or later, add the <installation_directory>/runtime/lib/native/zos directory to the JVM server option LIBPATH_SUFFIX, where <installation_directory> is the z/OS Connect Enterprise Edition installation directory.
    For example:
    LIBPATH_SUFFIX=/usr/lpp/IBM/zosconnect/v3r0/runtime/lib/native/zos

    For more information about setting LIBPATH_SUFFIX, see JVM server options.

  4. Configure WebSphere Liberty for your security requirements. By default, it expects the use of client-certified SSL certificates. To enable HTTP Basic Authentication, add the following configuration option to the server.xml file:
        <!-- Allow fail-over to HTTP Basic Authentication --> 
        <webAppSecurity allowFailOverToBasicAuth="true"/>

    You must also give users of z/OS Connect the zosConnectAccess security role. For more information about WebSphere Liberty security, see Configuring security for a Liberty JVM server, and for z/OS Connect security, see Security for z/OS Connect.

    If you installed z/OS Connect for CICS 1.0 previously, you can omit this step.

What to do next

Follow the steps for your specific version of z/OS Connect Enterprise Edition as described in the following tasks.