The name of the client program determines the TIBCO Object Service Broker client style. Refer to the table in
Client Style Summary for a listing of the program names and the types of styles for which they are used.
To replace an existing non-TIBCO Object Service Broker transaction without changing other non-TIBCO Object Service Broker programs, use a seamless client program name. Seamless clients, by definition, cannot be passed a session parameter string. The external transaction name is used as the TIBCO Object Service Broker profile name. The startup rule named in the TIBCO Object Service Broker profile is the first rule run. Refer to
Setting Up the User Profile for Seamless Clients.
To provide session parameters not supported in the user profile or to explicitly specify the startup rule, use a non-seamless client program name. From the viewpoint of the external application, the session parameter string followed by application data is passed as data to TIBCO Object Service Broker.
TIBCO Object Service Broker Parameters for more information about parameters.
If you use an external user security program name, the default user ID of the TIBCO Object Service Broker sessions is the user ID authenticated by the external security manager. This ensures strict security on an individual user basis and requires that the external security manager authenticate the user ID.
If you use an external transaction security program name, the TIBCO Object Service Broker sessions uses the name of the external transaction as its TIBCO Object Service Broker user ID. The external security manager is responsible for authorizing the execution of this external transaction.
To avoid setting up a TIBCO Object Service Broker user ID for every external user ID, use an external transaction client style. This sets the user ID to the external transaction name.
If you use a display client program name, the TIBCO Object Service Broker sessions can use the TIBCO Object Service Broker DISPLAY, UNTIL... DISPLAY, and DISPLAY & TRANSFERCALL rules language statements to present data to a screen.
If you use a conversational client program name, the TIBCO Object Service Broker session started under IMS TM has a Scratch Pad Area (SPA). Screen I/O is supported.
If you use a non-conversational client program name, the TIBCO Object Service Broker sessions started under IMS TM does not have a Scratch Pad Area (SPA). Screen I/O is supported but an IMS Physical Terminal Input Edit exit routine must be installed first.
The following table identifies the program name for a particular external environment and client style. For details, refer to the appropriate chapter for each client.
TIBCO Object Service Broker Managing Security for the evaluation of user IDs and passwords.