Bookshelf v7.5: Final Configuration of the Siebel CORBA Object Manager

Final Configuration of the Siebel CORBA Object Manager

After copying the latest version of your customized Siebel repository file (the .srf file) to the \OBJECTS\language subdirectory of each CORBA Object Manager installation, you may have to take additional steps to configure the Siebel CORBA OM.

These steps may be required or optional depending on which third-party CORBA software you are using and conventions of other CORBA software used in your organization. The additional steps relate to how the Siebel CORBA Object Manager will be started so that it is available for requests from client programs, and whether or not the Siebel CORBA Object Manager will publish the reference to its SiebelAppFactory object in the CORBA naming service.

NOTE: This section assumes you have a detailed understanding of CORBA, the tools, and the utilities provided by your ORB vendor.

Before performing the final configuration, you must make a decision about the following:

Whether you want a persistent server or an automatic server. If you use persistent server you need to start and stop the Siebel CORBA Object Manager server process or processes manually; otherwise, you need to configure the third-party CORBA software to automatically start a Siebel CORBA Object Manager server process when a client request is dispatched.

NOTE: The ORBIX implementation only supports persistent mode.

Whether the Siebel CORBA Object Manager should publish a reference to its SiebelAppFactory object in the naming service, or if clients will use proprietary methods of the third-party CORBA software to bind to the SiebelAppFactory.

There are several areas in which these decisions overlap:

What your existing CORBA policies or conventions are.

Whether you want to load-balance between several Siebel CORBA Object Manager servers.

Whether you want to use the CORBA naming service.

Which third-party CORBA software you have chosen.

If you are going to use the CORBA Naming Service, then you must use the persistent method. This is because the Siebel CORBA Object Manager registers its SiebelAppFactory object when it starts and removes it when it shuts down. Since the client (that uses the naming service) would not be able to invoke requests on that server unless it was running, you should not configure for automatic starting of servers.