(zos)

Configure optimized local adapters in development mode on the local node

The optimized local adapters for z/OS resource archive (RAR) file must be installed on the local node. When running on a non-z/OS platform, the optimized local adapters RAR file communicates with an instance of the optimized local adapters proxy EAR file on a remote z/OS node using Remote Method Invocation over Internet Inter-ORB Protocol (RMI-IIOP).

For more information about optimized local adapters in development mode, read the Optimized local adapters deployment in development mode topic.

When creating an optimized local adapters connection factory on the local node, several properties must be set to enable this communication to occur:

RemoteHostname

The host name of the remote z/OS node

RemotePort

The RMI port on the remote z/OS node. This can be the RMI port for a specific WebSphere Application Server for z/OS instance or the node agent.

RemoteJNDIName

The Java Naming and Directory Interface (JNDI) name where the optimized local adapters proxy EAR has been bound in JNDI on the remote node. The JNDI lookup is performed using a JNDI InitialContext, which is obtained using the specified RemoteHostname and RemotePort properties and by requesting the NameSpaceServerRoot namespace.

RemoteJNDIUsername

The user name to use when obtaining the JNDI naming context from the remote node

RemoteJNDIPassword

The password to use when obtaining the JNDI naming context from the remote node.

RemoteJNDIRealm

The realm name to use when obtaining the JNDI naming context from the remote node. Specifying the realm name might be required when both the local and remote nodes use WebSphere security but are in different realms.

1. The optimized local adapters RAR file on the local node obtains a reference to the optimized local adapters proxy EAR by performing a JNDI lookup. A naming context is obtained using a URL of corbaloc:iiop:<RemoteHostname>:<RemotePort>/NameSpaceServerRoot. Once this context is obtained, a lookup is performed using RemoteJNDIName. Assuming that the optimized local adapters proxy EAR was installed on a remote z/OS node using the default JNDI binding location, the optimized local adapters RAR on the local node can be installed by specifying the RMI port of the target WebSphere Application Server for z/OS instance, and a RemoteJNDIName of com.ibm.ws390.ola.jca.ProxyEJBRemote, which is the default binding for the optimized local adapters proxy remote interface.

2. Other properties of the optimized local adapters RAR connection factory on the local node, such as registerName, can be set by specifying them on the connection factory attributes for the resource adapter. These values are honored on the remote z/OS node.

3. The local node and the remote z/OS node might not share the same user registry.

   Two additional properties are available on the optimized local adapters RAR connection factory to give the request an opportunity to log on and to specify the user ID to use for the optimized local adapters interaction:

   Username

   The user name to use when executing the optimized local adapters interaction

   Password

   The password to use with the Username property.

   When specifying Username and Password, a logon occurs just before the optimized local adapters interaction is performed. If the logon is successful, the z/OS user ID corresponding with the Username is sent with the optimized local adapters request. Currently, the MVS™ user ID is used when communicating with CICS using the optimized local adapters link server. The target CICS transaction is started using the z/OS user ID only if the link server is started with the SEC=YES parameter and the CICS region is running with SEC=YES. For IMS, this user ID will be propagated and asserted only when the SYNC-TO-THREAD option is enabled on the WAS for z/OS server and the OTMASE=FULL OTMA parameter is in effect.

   A J2C JAAS alias may also be used to provide the Username and Password values. To use a J2C JAAS alias, in the console, click Resources > Resource Adapters > J2C connection factories > cf_name > JAAS-J2C authentication data > alias_name, and enter the userid and password. The resource adapter retrieves the userid and password from this setting. Should a JAAS alias be provided as well as the Username and Password on the connection factory, the Username and Password on the connection factory will take precedence. The setUserid() and setPassword() methods on the ConnectionSpecImpl takes precedence over both of these other methods.

Related concepts

Optimized local adapters deployment in development mode

WebSphere Optimized Local Adapter (WOLA) remote work request on an Enterprise Java Bean target

Related tasks

Configure optimized local adapters in development mode on the remote z/OS node