Mobile Web Client Automation Server

The Mobile Web Client Automation Server accesses the server object that the Siebel application starts. If your configuration can access this object, then it can get other Siebel objects and run Siebel object interface methods through these other objects.

The following image illustrates how an external application can control a Siebel application that uses the Mobile Web Client Automation Server.

The Mobile Web Client Automation Server includes the following requirements:

• The Siebel Mobile Web Client must be running.

• An external program that executes methods on a running instance of the Siebel Mobile Web Client Automation Server, uses resources that are out of process for the Mobile Web Client. The running instance of the Mobile Web Client has its own process and resources and the external calls don't have access to its internal resources and memory. If you've created a DLL that's loaded and accessible to the running instance of a Siebel application, and that DLL calls out to a running Mobile Web Client instance, the memory and resources used in those calls are also out of process relative to the Mobile Web Client that it's accessing. For more information, see How Siebel CRM Uses Memory and Resources with the Mobile Web Client Automation Server.

For more information, see Accessing the Mobile Web Client Automation Server.