Siebel Mobile Connector Guide > About the Siebel Mobile Connector >

How to Work with the Siebel Mobile Connector

Third-party applications created with the Siebel Mobile Connector use standard Web protocols or specific Siebel interfaces such as a Java Data Bean or the COM Data Control to send and retrieve data between users and the Siebel database. These steps describe the flow in greater detail and assume that real-time access to Siebel data is available.

1. Using the third-party application's user interface, the user requests information residing in the Siebel database.
2. The third-party application passes the information requested by the user to Siebel Web Engine (SWE) in the form of an XML document. The request is made through HyperText Transfer Protocol (HTTP), Java Data Bean, COM Data Control or any Siebel object interface.
3. The Siebel Mobile Connector, which is part of the Siebel Server, invokes SWE to retrieve information from the Siebel database.
4. This information is then passed back through Siebel Object Manager to SWE.
5. When SWE has the requested data, it returns it in the form of an XML document to the third-party application. If less than the total data set is wanted, the request specifies a style sheet that should be applied to the data. The style sheets are located at the Siebel Server.
6. The third-party application parses the XML document and presents the Siebel data to the user in its own user interface.

NOTE:  If your application provides online or offline capabilities, it must have the capability for storing and forwarding messages. In other words, your application must have a feature that queues messages between server and client, allowing the exchange of messages.

For more detailed information on how the business services of the Siebel Mobile Connector work, see How the Metadata Business Service Works and How the Alert Business Service Works.