1. Transports and Interfaces: Siebel Enterprise Application Integration
  2. EAI HTTP Transport Named Subsystems

EAI HTTP Transport Named Subsystems

The EAI HTTP Transport, like every other Siebel transport, reads required parameters from a named subsystem instead of the configuration (.cfg) file. The eai.cfg file entries list the external service name and the name of the named subsystem to be used. For example:

SiebelQuery = SiebelQueryDispatch

There is no [Properties] section for SiebelQueryDispatch in the .cfg file. The name is used to look up the named subsystem list and dispatch accordingly. Use named subsystems for property specification. Predefined named subsystems have been created for you already, such as:

  • SiebelQueryDispatch

  • SiebelExecuteDispatch

  • SiebelUpsertDispatch

Note: You can create additional named subsystems as needed using Siebel Server Manager.

For a discussion of named subsystems for Siebel EAI, see EAI Transports and Interfaces Overview. For more information about named subsystems, see Siebel System Administration Guide.