Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Integration Platform Technologies: Siebel Enterprise Application Integration > Web Services > Invoking Siebel Web Services Using an External System > Invoking Web Services on the Siebel Mobile Web ClientThe Siebel Mobile Web Client can serve the same Web services as those deployed on the Siebel Server, while protecting access through simple authentication. This feature allows developers to integrate external applications with Siebel Business Applications and test their integrations, without having to install an entire Siebel Enterprise. NOTE: All information provided in this topic for the Siebel Mobile Web Client also applies to the Siebel Developer Web Client. The Web service functionality is an extension of the Siebel Mobile Web Client, and runs as a separate siebel.exe process. This second siebel.exe process is started by the Siebel Mobile Web Client as its child process. The child process listens on the specified port for all Web service requests. The Web service requests are processed and sent to the EAI Inbound Dispatch Service, and then the response is sent back to the Siebel Mobile Web Client. The child process exits when the Siebel Mobile Web Client exits. NOTE: If any changes are made to Web services in the run time, then these will not be available to the child process. You must restart the Siebel Mobile Web Client; you cannot clear the Web services cache. Exceptions to Web Service SupportThe Siebel Mobile Web Client provides the same Web service support as an EAI-enabled Siebel Server, with the following exceptions:
Supported Authentication FormatsUser authentication is the same as for the Siebel Mobile Web Client. The following authentication formats are supported:
Authentication Formats That Are Not SupportedThe following authentication formats are not supported:
Enabling Web Services on the Siebel Mobile Web ClientTwo new parameters have been added to the application configuration file to enable the Web service functionality: EnableWebServices and WebServicesPort. To enable Web services on the Siebel Mobile Web Client
The next time the Siebel Mobile Web Client starts, it will start the siebel.exe child process. After the process has started, it can send requests and receive responses. Starting the siebel.exe Process From the Command LineWhen it is not required to start a Siebel Mobile Web Client instance, you can start the siebel.exe process independently using the command line. To start the siebel.exe process from the command line
NOTE: To stop a siebel.exe process started from the command line, you must end the process from the Windows Task Manager. Confirming that the siebel.exe Process is ListeningYou can use the netstat utility from the DOS prompt to determine whether the siebel.exe child process is listening for Web service calls. To confirm that the siebel.exe process is listening
Invoking Web Services on the Siebel Mobile Web ClientYou can invoke Web services on the Siebel Mobile Web Client by passing credentials in the URL, in the SOAP header, or in the WS-Security header. Example of Passing User Credentials in the URLhttp://< http://localhost:2330?SWEExtSource=WebService&Username=< The following is an example of a request: soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:asi="http://siebel.com/asi/"> <PrimaryRowId>99-28B0A</PrimaryRowId> Example of Passing User Credentials in the SOAP Headerhttp://< http://localhost:2330?SWEExtSource=WebService&WSSOAP=1 The following is an example of a request: soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:asi="http://siebel.com/asi/"> <UsernameToken xmlns="http://siebel.com/webservices">SADMIN</UsernameToken> <PasswordText xmlns="http://siebel.com/webservices">SADMIN</PasswordText> <SessionType xmlns="http://siebel.com/webservices">None</SessionType> <PrimaryRowId>99-28B0A</PrimaryRowId> Example of Passing User Credentials in the WS-Security Headerhttp://< http://localhost:2330?SWEExtSource=SecureWebService&WSSOAP=1 The following is an example of a 2002 request: <soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:asi="http://siebel.com/asi/"> <wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext"> http://schemas.xmlsoap.org/ws/2002/07/secext <wsse:UsernameToken xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility"> <wsse:Username>SADMIN</wsse:Username> <wsse:Password Type="wsse:PasswordText">SADMIN</wsse:Password> <asi:SiebelContactQueryById soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <PrimaryRowId xsi:type="xsd:string">04-LLSQ5</PrimaryRowId> The following is an example of a 2004 request: <wsse:Security mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecuritysecext-1.0.xsd"> <wsse:UsernameToken wsu:Id="UsernameToken-zsXRc97TujDINUug8ibD2Q22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wsswssecurity-utility-1.0.xsd"> <wsse:Username>SADMIN</wsse:Username> <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-usernametoken-profile-1.0#PasswordText">SADMIN</wsse:Password> <wsse:Nonce EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">f61vAYvDD0t2sUFEmXSVU+FlOvA=</wsse:Nonce> |
![]() ![]() |
Integration Platform Technologies: Siebel Enterprise Application Integration | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |