Configuring the Web Interface › Web Directors and Web Engines Configuration › Server Configuration › Object Managers

Object Managers

Object managers manage all the CA SDM objects. An object manager always exists on the primary server. Each object manager has a name, which is synonymous with the name it uses to communicate with other objects. The default object manager on the primary server is always named domsrvr. Enterprise systems with multiprocessor servers or secondary servers can add more object managers to the primary server and secondary servers. You can navigate, add, edit, and delete object managers.

Each object manager is assigned a host. Object managers that are assigned to the primary server always enter primary as the host name.

You can group object managers so that the groups can be assigned to provide service to specific groups of web engines and Java clients. Typically, group can be left as none and the load balancing feature of the system spreads the load across all object managers. Users that require this feature often have web engines geographically separated from the primary server and would like to co-locate an object manager near the webengine. The users group the object managers that are assigned to the local webengines, and then assign the webengines to this group of object managers.

The Accept mask is an advanced feature that tells the object manager from which clients it accepts connections. Usually, a webengine attempts to connect to an object manager with a name like web:seattle:1, web:seattle:2 or web:texas:1. The administrator can specify an Accept mask like web:seattle.* to accept all seattle connections and reject others. The administrator can also specify a mask like web:.* to accept connections from webengines and reject connections from clients.

The Display value is sometimes useful. Most users let the system default this value to the host name. This value appears on the clients to indicate which object manager it is connected to.