Transports and Interfaces: Siebel Enterprise Application Integration > EAI Transports and Interfaces Overview > Using Named Subsystems for Transport Parameters >

Rules of Precedence for Parameter Specification

You can specify the two named subsystem parameters, ConnectionSubsystem and DataHandlingSubsystem, as either business service user properties or as run-time arguments. If you specify the parameters in both locations, then the business service user property takes precedence over the run-time arguments.

NOTE:  For additional information about named subsystems, see Siebel System Administration Guide.

You specify every other parameter in one of the two named subsystems or as run-time arguments. Siebel EAI looks for the parameter in the ConnectionSubsystem or the DataHandlingSubsystem, depending on which parameter it is. If you specified the appropriate named subsystem, then Siebel EAI always looks for the parameter there.

If you do not specify the parameter in this named subsystem, even if you specified it as a run-time argument, then the run-time specification is ignored. Siebel EAI looks for the parameter in a run-time specification only if no appropriate named subsystem is specified.