Bookshelf Home | Contents | Index | Search | PDF

Transports and Interfaces: Siebel eBusiness Application Integration Volume III > 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 as 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 client side

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

[HTTPSubSys]
HTTPRequestURLTemplate = http://myserver.com/app.exe?User=$user$&Pass=$password$

NOTE:  The preceding entry sets the HTTPRequestURLTemplate to a specific location and passes parameters $user$ and $password$. The user and password parameters must be set as either user properties or as run-time parameters.

Save the file and exit the text editor.

To specify the parameters on the server side

Start the Siebel client and navigate to Server Administration > Enterprise Configuration.
Navigate to the Enterprise Parameters form.
Add a new key and value pair that specifies the parameter and its corresponding value.

If the parameter already exists, select it to make it the active parameter, then type the value you want to use in the Value field.

Restart the Siebel Server.

Any parameter values you set using a configuration file overrides parameters with the same name you might have specified as user properties in your Siebel .srf file. The name and password you specify should already exist in your database.

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:  Any parameters specified in an input property set overrides parameters with the same name that have been specified in the .srf file or in your subsystem 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.

Bookshelf Home | Contents | Index | Search | PDF