Transports and Interfaces: Siebel Enterprise Application Integration > EAI HTTP Transport >

Processing and Sending Outbound XML Documents

This section explains how to use Siebel Tools and the Siebel application to set up the EAI HTTP Transport to process and send outbound XML documents. When you want to send XML messages based on Siebel integration objects to an external system across Internet-support protocols, you use the EAI HTTP Transport business service.

Controlling the Behavior of EAI HTTP Transports

You can specify the parameters that control the behavior of transports in the following order:

• Specifying Parameters as Business Service User Properties.
• Specifying Parameters as Subsystem Parameters.
• About Parameters as Run-Time Properties.
• About Parameters in Parameter Templates.

Specifying Parameters as Business Service User Properties

You specify parameters as business service user properties in Siebel Tools. These parameters go into effect when you have compiled the .srf file. When using this method, keep the following in mind:

• These parameters stay in effect as long as you continue to use the same .srf file and do not recompile it with a newer specification for the business service parameters.
• If you define the same parameter as a subsystem parameter or as a run-time property, the subsystem parameter or run-time property overrides any values you have defined in Siebel Tools and compiled into the .srf file.

Specifying Parameters as Subsystem Parameters

You can specify parameters on either the client side or the server side, depending on whether you use the client or server version.

To specify the parameters on the Siebel Dedicated Web Client

1. Using a text editor, create the following section in the proper .cfg file, such as siebel.cfg.
2. Add a [HTTPSubSys] section in the configuration file.
3. Add Name=Value pairs for each parameter, as follows:

   HTTPRequestURLTemplate="http://www.anyURL.com"

   HTTPRequestMethod="GET"

4. Save the file and exit the text editor.
5. In the workflow process, specify HTTPSubSys in the Connection Subsystem parameter value.

To specify the parameters on the Siebel Web Client

1. Start any Siebel Business Application and navigate to Site Map > Administration - Server Configuration > Enterprises.
2. In the top list applet, select the Enterprise Server that you want to configure.
3. In the middle applet, click the Profile Configuration tab.
4. Click New to create a new component profile and set the following parameters:
   1. Profile = HTTP_test
   2. Alias = HTTP_test
   3. Subsystem Type = HTTPSubSys
5. In the Profile Parameters list applet (the bottom applet), specify the parameters required for the type of operations the subsystem will need to support:
   1. HTTPRequestURLTemplate = "http://www.anyURL.com"
   2. HTTPRequestMethod = "GET"

Then, in the workflow process on the Siebel Web Client, you will specify the Connection Subsystem input argument to the HTTP Transport, and the value will be the named subsystem that you created. For the case above, it will be HTTP_test. You can run the workflow process in Simulator using the Siebel Web Client.

About Parameters as Run-Time Properties

You specify HTTP parameters as run-time properties by passing them as values in an input property set to the EAI HTTP Transport business service. You can pass the values to the business service by way of a workflow or through a program that calls the EAI HTTP Transport business service directly.

NOTE:  Subsystem parameters take precedence over run-time parameters.

About Parameters in Parameter Templates

Parameter templates allow you more flexibility in specifying parameters. You can use variables to specify certain elements of a given parameter value. The following example shows how to specify a variable for a login password, rather than hard-coding a password into the parameter.

HTTPLoginURLTemplate = http://www.srvr.com/login?Username=ronw&Password=$PWD$

where

PWD = 421ax7

The business service, EAI HTTP Transport in this case, receives the parameter template. The token, shown above as $PWD$, indicates that the business service should look for a parameter called PWD from a user property or run-time parameter. Dollar signs ($) delimit the token in the template definition. The token specifies the actual password variable. The token is case-sensitive—Pwd is different from PWD or pwd.

The token must be defined as either a business service user property or as a run-time parameter in the input property set. For example, you could specify the HTTPLoginURLTemplate as a user property of the business service, and username and password as run-time properties. Any logins that specify the template will always use the same template, but different users can specify unique user names and passwords at run time.