BSA CI supports TCP/IP cross-platform communication between various systems, for example UNIX and z/OS, and allows online access from Beta Web applications. Transport can be unencrypted (NOSSL) or encrypted using IBM's System SSL (SSL). If you decide to use SSL, please make sure that the client program you are using also supports SSL.
BSA CI supports the following types of port:
the port used by a product application
the port used for internal communication between the product server and the product application, e.g. to process specific service and administration requests.
These are special service ports used by the BSA Service Manager to provide ISPF online information on the operating status of BSA CI, and to enable to operating status to be modified.
The TCP/IP functionality of BSA CI can be controlled by means of the BSA Service Manager and the appropriate LST parameters. The following are available:
Domain name system support for symbolic IP addresses with a maximal length of 255 characters.
Activation of product-specific security exits that are defined and activated in the product started task. These exits are defined and executed in the started task, and are called via the BSA Service Manager.
In runtime mode NOSSL, encryption and/or compression are used for TCP/IP connections.
Several runtime modes are supported for the relevant application and service ports.
In order to work with a product, the user needs to log onto the security system used by the target system. The logon is made in the runtime mode defined for the port concerned. Following successful logon, the user is administered by BSA CI.
Special messages (in particular LOGON messages) are written to a special message table of the connected product, provided that database table MSG has been created for the product concerned.