Siebel Adapter 6.0 SP3 | webMethods Siebel Adapter Documentation | webMethods Siebel Adapter Installation and User’s Documentation | Overview of the Adapter | Siebel-to-webMethods Communication | EAI webMethods Transports
 
EAI webMethods Transports
 
EAI webMethods Transport Run-Time Processing
The EAI webMethods Transports are custom Siebel business service methods. They enable Siebel to notify Integration Server services when a change (such as an Insert, Update, or Delete) occurs within a particular Siebel business component. Transports are designed to provide interactive transportation of small volumes of data between the Siebel application and the Integration Server. Transports are built using Siebel's eScript scripting language. To see an example function that invokes a transport, see Example Transport Invocation Function.
To test transports, you can use the Siebel Business Service Simulator. For an example, see Testing Synchronous IS Service Invoke.
Transports run on the Siebel Server, using Java Data Beans to connect to the Siebel Server. You can call transports from within a Siebel business component script or from a Siebel workflow. Calling transports from workflows allows you to easily update parameters for the transports.
You can use transports to perform many tasks, including synchronously or asynchronously invoking a service on the Integration Server, getting a transaction's status or data, restarting or ending a transaction, and reporting exceptions. For more information, see EAI webMethods Transports.
Note:
EAI webMethods Transports are supported on Siebel 7.x on Windows, HP-UX, and Solaris platforms. Before you can use transports, you must configure your system as described in Installing, Upgrading, and Uninstalling the Siebel Adapter .
Note the following:
*The data returned by an Integration Server service must be of the data type String.
*The data returned by an Integration Server service must not be nested. If you need to return nested data, add to your Integration Server service the webMethods flow service docToString to convert the incoming data into a single string before returning the data. The transport's outputData child property set will contain this string when the Invoke operation is completed. You can retrieve the data (which is in the form of a string) from outputData.