Using Named Subsystems for Transport Parameters

Named subsystems are groupings of defined enterprise parameters that are stored in the Siebel Gateway. You use named subsystems to specify methods and parameters for EAI Transports. Transport business services take two subsystem names as parameters, which you define using the Siebel Server Manager:

• Transport Connection Subsystem (ConnectionSubsystem)

• Transport Data Handling Subsystem (DataHandlingSubsystem)

Values for parameters in a named subsystem are common to every user of the subsystem across the enterprise. Subsystem names themselves are parameters for server components. You can logically group parameters into various subsystems.

For the two EAI Transport named subsystem parameters, ConnectionSubsystem and DataHandlingSubsystem, two parameters exist for the EAI receivers: ReceiverConnectionSubsystem and ReceiverDataHandlingSubsystem. The EAI Receiver looks up these parameters from the server component parameters and copies the corresponding properties (ConnectionSubsystem and DataHandlingSubsystem) to the input property set of the transport business service.

Note: You must create named subsystems and specify the parameters for the subsystems. Then, you specify the named subsystems you created, for example, as business service user properties in a workflow or through scripting. You must specify named subsystem parameters by the values of their Alias fields in the Profile Parameters list.

The following subtopics are discussed in this topic:

• Rules of Precedence for Parameter Specification

• Common EAI Transport Parameters