Bookshelf Home | Contents | Index | PDF |
Siebel Object Interfaces Reference > About Object Interfaces and the Programming Environment > Object Interfaces You Can Use to Access Siebel Objects > About the Siebel COM Object InterfaceYou can access a Siebel COM object interface in any of the following ways: You can use any of the following languages to access a Siebel COM interface: You cannot use the Perl programming language to access a Siebel COM interface. The programming environment you use might limit the features that Siebel CRM can use the Siebel COM servers. For example, do not use Siebel VB code for the Data Server as a Windows NT service. How an External Application Communicates with a Siebel ApplicationCOM Data Control is a type of Siebel Object Interface that allows an external application to connect and communicate with the Siebel Application Object Manager, which is a multithreaded, multiprocess application server that hosts Siebel business objects and allows session connections with Siebel clients. This connection allows the external application to access Siebel business objects. The Siebel Internet Session Network API (SISNAPI) protocol allows this communication. Figure 1 illustrates how an external application uses COM Data Control to communicate with the Siebel application.
To use COM Data Control to develop a Siebel application, you must install, configure, and make sure Siebel CRM is running a Siebel Application Object Manager on a Siebel Server. For more information, see Siebel System Administration Guide. For information about the SISNAPI protocol, see Siebel Deployment Planning Guide. Servers That the Siebel COM Interface UsesThis topic describes the servers that the Siebel COM Interface uses. Web Client Automation ServerThe Web Client Automation Server does the following:
Figure 2 illustrates how an external application can call a business service and manipulate a property set that resides on the Web Client Automation Server.
The Web Client Automation Server includes the following requirements:
You cannot configure Siebel CRM to call the Web Client Automation Server directly from an active instance of a Siebel application. Siebel CRM uses one of the following names for the process that represents the Web Client Automation Server. The Windows Task Manager displays this name: If the user ends the Siebel Web Client session, then Siebel CRM stops this process. For more information, see Accessing the Web Client Automation Server. Mobile Web Client Automation ServerThe 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. Figure 3 illustrates how an external application can control a Siebel application that uses the Web Client Automation Server.
The Mobile Web Client Automation Server includes the following requirements:
For more information, see Accessing the Mobile Web Client Automation Server. How Siebel CRM Uses Memory and Resources with the Mobile Web Client Automation ServerSiebel CRM starts a process to run the Siebel Mobile Web Client. This process uses memory and resources that are specific to this process, which are in process. If your configuration communicates with the Siebel Mobile Web Client while it is running, then the resources that Siebel CRM uses in this communication are separate form the memory and resources that it uses in the process that it started to run the Siebel Mobile Web Client. These separate resources are out of process. COM Data ServerFigure 4 illustrates how an external application uses the COM Data Server that does not include user interface objects. The COM Data Server uses the same technology that the Siebel Mobile Web Client uses to connect to the Siebel database.
The Mobile Web Client Automation Server includes the following requirements:
Note the different ways that the following servers handle DLLs:
For more information, see Accessing the COM Data Server. |
Siebel Object Interfaces Reference | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |