For z/OS platforms

Setting up z/OS Connect

The z/OS® Connect feature runs in a WebSphere® Application Server for z/OS Liberty environment and is installed from the Liberty Repository.

Before you begin

Use IBM® Installation Manager to install Liberty for WebSphere Application Server Version 8.5.5.2, along with the following interim fixes:
  • 8.5.5.2-WS-WLP-OS390-IFPI18279
  • 8.5.5.2-WS-WLP-OS390-IFPI18379

Download the interim fixes from IBM Fix Central, or install the interim fixes directly from the service repository.

Use IBM Installation Manager to install Liberty for WebSphere Application Server version 8.5.5.3 or later.

Use the featureManager command for Liberty to install the z/OS Connect feature from the Liberty Repository. This command requires that the file system for Liberty have read/write access. You can either enable the Liberty file system as read/write, or copy the contents into a read/write file system so new features can be added from the Liberty Repository.

About this task

You can use the featureManager command for Liberty to install the z/OS Connect feature from the Liberty Repository. This command requires that the file system for Liberty have read/write access. You can either enable the Liberty file system as read/write, or copy the contents into a read/write file system so new features can be added from the Liberty Repository.

Procedure

  1. Change to the bin subdirectory under the directory where Liberty is installed. The directory must be enabled for read/write access.
    cd ${wlp.install.dir}/bin
  2. Use the featureManager command to install the z/OS Connect feature:
    featureManager install zosConnect-1.0 
    The feature is downloaded from the online Liberty Repository and installed. You must have Internet access to retrieve the feature from the Liberty Repository.
    Stabilized feature: The zosConnect-1.0 feature is stabilized. You can continue to use the zosConnect-1.0 feature. However, consider using the IBM z/OS Connect Enterprise Edition product.
  3. If you are installing this feature on to Liberty version 8.5.5.2, set the required file permissions by issuing the following commands from the WebSphere Liberty installation directory:
    chmod ugo+rx bin/zosConnect/bbgls2js and chmod ugo+rx bin/zosConnect/bbgjs2ls
  4. You are now ready to add the z/OS Connect feature to the feature manager list in the server.xml file of the Liberty server where you want to enable this support.
    <server description="z/OS Connect Liberty Server">   
    	<featureManager>       
    		<feature> zosConnect-1.0</feature>   
    	</featureManager>
    </server> 
  5. (Optional)
    1. If you are using WebSphere optimized local adapters (WOLA), use the featureManager command to install the Optimized Local Adapters feature:
      featureManager install zosLocalAdapters-1.0 

      For more information, see Installing Liberty Repository assets.

      The feature is downloaded from the Liberty Repository and installed. You must have Internet access to retrieve the feature from the Liberty Repository.

    2. Update the server.xml file to enable WOLA for outbound calls from your Liberty server to your applications with an external address space.
      • Add a zosLocalAdapters element that defines the three-part WOLA group name that is used by clients to connect to the Liberty server.

      • Add a connection factory element and provide a JNDI name. For more information, see the documentation on enabling the Liberty server environment to use optimized local adapters.

      <server>  
      	<featureManager>  
      		<feature>zosConnect-1.0</feature>  
      		<feature>zosLocalAdapters-1.0</feature>  
      	</featureManager>   
      
      <!-- Local adapters connection factory definition -->  
      	<authData id="cauth1" user="user1" password="{xor}LDo8Ki02KyY="/>  
      	<connectionFactory id="wolaCF" jndiName="eis/ola" containerAuthDataRef="cauth1" >  
      		<properties.ola/>  
      	</connectionFactory>   
      
      <!-- Provide WOLA server identity -->  
      	<zosLocalAdapters wolaGroup="LIB1" wolaName2="LIB2" wolaName3="LIB3" />  
      </server> 

Results

You are now ready to add z/OS Connect service elements to your server.xml configuration.