Scribd
Upload
56 views25 pages

07 - Inbound Web Services

Uploaded by

abhishek040599
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
56 views25 pages

07 - Inbound Web Services

Uploaded by

abhishek040599
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 25

Inbound Web Services

Inbound Web Services

§ Allow external applications to invoke a published


Siebel Web service
§ Service is often an inbound application services
interface (ASI)
§ Other business services and workflows can also be
published
Siebel CRM Web Services

§ Siebel CRM includes many prebuilt published Web


services in several industry areas
§ Examples:
§ Order Management
§ ABOWebService
§ AssetWebService
§ CatalogWebService
§ ProductConfigurator
§ Field Service
§ ServiceRequest
§ VerifyEntitlement
§ CME
§ NetworkOrderEntry
§ TroubleTicket
Siebel CRM Web Services Continued

§ Are managed in the Siebel client using the Inbound


Web Services view
§ Are ready for use with a small amount of
administration
§ Address for the service will need to be configured
§ Consult WSDL to determine the service address
§ Web service might need to be set to Active
Inbound Web Service Architecture

§ Uses the HTTP receiver in the EAI object manager to


receive and dispatch incoming Web service requests
§ Makes use of the Web Service profile configuration
§ Invokes the Web Service Inbound Dispatcher
business service
Web Service Inbound Dispatcher

§ Is a business service that:


§ Converts an incoming SOAP messages to Siebel-
structured data
§ Invokes the appropriate business service or workflow
§ Executes the method contained in the SOAP message
§ Converts the data returned by the service to a SOAP
message
Publishing a Siebel Inbound Web Service

1. Publishing a Siebel Inbound Web Service

2. Create a Service Port

3. Publish the Operations

4. Generate the WSDL File


1. Create the Web Service Definition

§ In the Siebel client, navigate to Web Service


Administration > Inbound Web Services
§ Create a record in the Inbound Web Services list
§ Namespace: Enter the namespace for your Web service
§ Required for generating various XML documents
§ Distinguishes this Web service from others
§ Name: Enter the name of the inbound Web service
§ Status: Select Active to enable external systems to call
the Web service
§ Comment: Enter a description of the Web service
(optional)
2. Create a Service Port

§ A service port identifies the underlying Siebel service


to be deployed as a Web service
§ Can be a workflow process, business service, or
application services interface (ASI)
§ In the Inbound Web Services view specify:
§ Business Service: name of the business service or
workflow
§ Transport: HTTP
§ Address: the URL to be used by clients
2. Create a Service Port Continued

§ If the business service is an ASI, make sure that the


ASI is enabled for external use
§ In Siebel Tools, set the External Use property to True
2. Create a Service Port: Binding

§ Select appropriate binding:


§ SOAP_RPC_ENCODED
§ SOAP_RPC_LITERAL
§ SOAP_DOC_LITERAL
3. Publish the Operations

§ In the Inbound Web Services view, specify an


operations record for each method of the service
that can be invoked by a Web service client
§ Not all service methods must be published
§ Only published methods can be invoked
§ Can publish only the RunProcess method for workflow
processes
4. Generate the WSDL File

§ In the Inbound Web Services view:


§ Click Clear Cache to update the cached Web services
definitions
§ Click Generate WSDL to create the WSDL file
§ Distribute WSDL file to Web service clients
Transports for Web Services

§ Siebel applications support publishing Web services


that can be invoked by a variety of transports
§ MQSeries, MSMQ, and JMS, in addition to HTTP
Publishing from Siebel Tools

§ A business service or workflow process can be


published directly as a Web service in Siebel Tools
§ Right-click the service or process, and select Deploy as
a Web Service
§ Creates the Web service, service port, and operations
definitions
Optional SOAP Header Elements

§ Siebel Authentication and Session Management


SOAP headers can be used to:
§ Pass in login credentials in the SOAP message itself
§ Removes the need to include credentials in the URL
§ Warning: To avoid plain-text password transmission, use a
secure transmission protocol such as HTTPS
§ Support several different session types
§ Sessionless
§ Stateless
§ Stateful
Sessionless

§ Sessionless refers to a short-duration session:


§ New session is created to service the request
§ Session is closed after Siebel application sends
response
§ Anonymous login is assumed if user name and
password not provided
§ Anonymous login support requires additional Siebel
Web Engine (SWE) and server configuration
§ Sessionless transaction is specified by either:
§ Omitting SessionType element in SOAP header
§ Setting SessionType element to NONE
Authentication Process: Sessionless

1. An external application sends a SOAP request with


user credentials and session type
2. Siebel application verifies credentials
3. If user is verified, Siebel application creates
appropriate session type
4. Siebel application sends SOAP response to external
application
Stateless Session

§ A stateless session:
§ Is opened with initial request
§ Remains open for subsequent requests
§ Allows relogin automatically if session is closed
§ Occurs transparently to user
§ Benefit:
§ Allows a client to submit multiple requests without the
overhead of verifying credentials for each request
§ Initial request must contain user name and password
§ Anonymous login not supported for stateless sessions
§ Set SessionType element in SOAP header to
Stateless
Authentication Process: Stateless Session

§ Siebel application generates an encrypted session


token
§ Contains user credentials and session ID
§ Session token is sent in request and reply headers
(after initial request)
§ Used by Siebel application to identify user’s session
Example SOAP Headers

§ Example: Stateless session


Example SOAP Headers Continued

§ Example: Stateless session


Example SOAP Headers Continued

§ Example: Stateless session


Stateful Session

§ A stateful session:
§ Is opened with initial request
§ Remains open for subsequent request
§ Does not support automatic relogin if session is closed
§ Supports Web services that maintain some form of
user state
§ Example: a shopping cart Web service that stores items
until the end of the session
§ Initial request must contain user name and password
§ Anonymous login not supported for stateful sessions
§ Set SessionType element in SOAP header to Stateful
Web Services (WS) Security Support

§ Is another industry-standard security framework for


Web services
§ Allows a client to pass credentials in the SOAP message
as opposed to in the header
§ Does not require the creation of a session and use of
session tokens
§ Siebel CRM supports the use of the WS-Security
UserName Token mechanism

You might also like