Security

 

BEA WebLogic Java Adapter for Mainframe (JAM) supports the basic Application Program-to-Program Communication (APPC) style of sign-on security. You can configure a gateway to use one of three types of sign-on security for each link that is defined (refer to the JC_SNALINKS Section in Configuring the BEA WebLogic Java Adapter for Mainframe.). The selected level of security determines what combination of userid and password is used for transactions across the link.

JAM supports the following security options:

• LOCAL
  All security is handled by the local system and the link itself has no security requirement.

  IDENTIFY

  A userid is passed to the mainframe. This userid can originate with the client application or it can be a default userid supplied at Java gateway startup by the -u option in the WebLogic Server properties file as part of the startupArgs entry for the gateway.

  VERIFY

  A userid and password are passed to the mainframe. The userid can originate with the client application or it can be a default userid supplied at Java gateway startup by the -u option in the WebLogic Server properties file as part of the startupArgs entry for the gateway. The password must be supplied by the client application.

In addition, an alternate mirror transaction is supported on each Distributed Program Link (DPL), which can be used to associate different Resource Access Control Facility (RACF) profiles with different services.

Refer to IBM RACF documentation for more specific information about establishing and administrating mainframe security.