Using the "Web Engine HTTP TXN" Business Service to Access Cookies, Querystring Parameters, Form Field Parameters, HTTP Headers, and Server Variables
(Doc ID 476473.1)
Last updated on JULY 26, 2019
Applies to:Siebel Tools - Version 8.0  to 17.0 [IP2017] [Release V8 to V17]
Siebel Tools - Version 17.0 [IP2017] and later
HTTP provides several means to allow Web Servers to obtain information from the browser. The most familiar example is that when a user enters data into a form on a Web page, the data is sent to the Web Server, which can access the value of each form field. This example illustrates sending form field parameters to the Web server with a POST method. In general, a browser can send Cookies, headers, querystring parameters, as well as form field parameters to the Web server. Web servers can also respond back to the browser with Cookies and custom headers. The "Web Engine HTTP TXN" business service enables Siebel eBusiness Applications to retrieve or set Cookies, headers, and querystring and form field parameters.
This document is informational and intended for any user.
Note that there are complications in attempting to use this Business Service from a Workflow.
1) For a Business Service that accepts/returns hierarchical arguments, the argument name is used to identify the child property set to pass/store. This is problematic in workflow, because it places a restriction on the argument name across Busines Service. For example, if Business Service BS1 returns a property set of type A, and Business Service BS2 accepts a property set of type B, you cannot pass the output of BS1 directly into BS2 in workflow, without adding an intermediately step to alter the type. (BUG 10448594 - SHOULD BE ABLE TO SPECIFY CHILD TO PASS/STORE IN WORKFLOW")
2) This BS is meant to be run exclusively at a graphical user interface object manager such as call center. HTTP Headers are not meaningful in a non GUI component such as wfprocmgr. (BUG 10503454 - "WEB ENGINE HTTP TXN" NOT WORKING WITH "WORKFLOW" )
Both of the above Enhancement Request Bugs were created to address the complications, but the Enhancement Request were both rejected. It is a fact of life that the Web Engine HTTP TXN" business service should not be used from a workflow using "Workflow Process Manager (Server Request)" and that there may be issues when passing the resulting Property Sets to other WF steps.
If using this BS in a Workflow, rather than calling the BS directly from the WF, you may be able to use the WF to call a custom BS, and then in the custom BS, use scripting to call the "Web Engine HTTP TXN" BS.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document