Scribd
Upload
37 views

05 - EAI HTTP Transport

Uploaded by

abhishek040599
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
37 views

05 - EAI HTTP Transport

Uploaded by

abhishek040599
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

EAI HTTP Transport

Using HTTP Transport

§ To configure HTTP transport in Siebel applications,


you need to understand the following
§ How a Siebel application sends HTTP requests
§ How a Siebel application responds to HTTP requests
§ How security (logging in and out) is handled
§ How data is transmitted in the HTTP request
Fundamentals of HTTP Transport

§ Communication is directional (request/response


model)
§ Client (browser) sends request to Web server
§ Web server responds to the request
§ Client does not receive requests from Web server
§ Communication is stateless
§ Web server treats each request from a client as an
independent request
§ Client can include additional information in the request
to establish any prior context
§ Example: SessionID
§ Communication can be in:
§ Sessionless mode
§ Session mode
Sessionless Mode

§ Client submits a single HTTP request to:


§ Log in using supplied credentials
§ Submit the actual request
§ Log off at end
§ Session does not persist longer than the request
§ Requires that the client identify and authenticate every
request
Session Mode

§ Client submits separate HTTP requests to:


§ Log in using supplied credentials
§ Client receives a sessionID from server
§ Submit the actual request
§ Provides the sessionID in all subsequent requests to
confirm prior login
§ Submit additional requests as required
§ Log off at end
§ Session persists longer than a single request
§ Server recognizes the client for some period of time
Data Transmission

§ HTTP supports two methods to transmit data in a


HTTP request:
§ GET
§ POST
HTTP GET Method

§ Includes all data in the URL itself


§ Does not use a separate HTTP body
§ Is subject to a limit on the length of the URL
§ Typically a total of a 1000 characters
§ Is less secure
§ Is used for:
§ Login and logoff requests
§ Simple commands
§ Is not normally used for data transfer
HTTP POST Method

§ Places data in the body of the HTTP request


§ Is more secure than GET method
§ Is not subject to length limitations
§ Is typically used to send data to an external
application
Siebel Architecture for HTTP Transport

§ Sending (Siebel application as the client):


§ Uses the EAI HTTP Transport business service to
generate HTTP messages to an external application
§ Receiving (Siebel application as the server):
§ Uses the EAI Object Manager to process incoming HTTP
requests
§ Serves as the HTTP receiver component
EAI HTTP Transport

§ Is an EAI business service that uses HTTP to


transport data
§ Supports only Send and SendReceive methods
§ Send: transmits data and completes execution
immediately
§ SendReceive: transmits data and waits for response
from external application
§ Passes response to subsequent business service
§ Supports both session and sessionless modes
§ Typically uses sessionless mode
§ Supports both GET and POST methods
Configuring Outbound HTTP Transport

1. Add the HTTP Transport Step

2. Assign Inputs and Outputs

3. Assign Request Methods and URLs


1. Add the HTTP Transport Step

§ Create a new workflow (or edit an existing workflow)


§ Create a new business service step to send HTTP
§ Assign the EAI HTTP Transport business service
§ Select the method (Send or SendReceive)
2. Assign Inputs and Outputs

§ Assign the workflow process property containing the


XML string to the input argument <Value>
§ For SendReceive, assign the response in <Value> to
a workflow process property
3. Assign Request Methods and URLs

§ For sessionless mode specify the following input


arguments:
§ HTTPRequestMethod
§ HTTPRequestURLTemplate
§ Consult the external application documentation for
the correct URL
3. Assign Request Methods and URLs Continued

§ For session mode specify separate pairs of methods


and URLs for:
§ Login
§ Request
§ Logoff
§ Consult the external application documentation for
the corresponding URLs
EAI Object Manager

§ Is an object manager that handles all incoming EAI


requests
§ Behaves like client application object managers (for
instance call center object manager)
§ Handles requests addressed to //HostName/eai_enu
§ Forwarded by the Siebel Web Server Extension
§ Requires a login and password
§ Siebel application uses the same authentication
mechanism as application object managers

You might also like