Siebel Object Manager

The object manager acts like a dedicated client except that it represents multiple clients instead of just one client. With this in mind, the object manager needs to understand how to display things on the screen, what rules to enforce, etc. To do this, the object manager reads the srf file on an as needed basis. The object manager will cache object definitions for the entire life of the process and will share this information with all clients that connect to this object manager. The object manager also manages client specific information. As a rule of thumb each client will add about 4 mb of memory usage to the object manger on top of all the object definition memory. This is a rule of thumb and can vary greatly depending on usage. 


As thin clients log in and out of Siebel the object manager usage will go up and down. If all users log off the object manager processes may stick around for 20-30 minutes while timeouts are reached. Once all the user connections are cleaned up the object manager process, SIEBMTSH will shutdown. The "Minimum Multi-Threaded Servers" parameter value may prevent SIEBMTSH processes from shutting down. 


Min MT servers govern how many processes to keep running when there is no activity for a component. One reason to do this is to avoid having a login delay when a thin client tries to connect and a new process is started to handle the request

http://www.siebeldigest.com/