Modifying the dmcl.ini File on the Oracle WebCenter Content Service for Documentum Host
On all computers that host the Oracle WebCenter Content Service for Documentum, you can increase the max_session_count variable in the dmcl.ini file to allow for additional concurrent sessions. By default, the max_session_count is set to 10, meaning there can be 10 concurrent sessions to Documentum.
- The number of Documentum sessions depends on the number of content crawlers you expect to run concurrently, as well as the number of users you expect to click through links concurrently. We recommend you set the max_session_count parameter accordingly. You can increase this setting later if you find that you run out of sessions or want to increase the number of content crawlers running simultaneously.
- A session is started for each user with a unique user name/password that tries to click through to a Documentum document in the portal. The max_session_count must accommodate the estimated number of click through users to be handled concurrently.
Modifying the server.ini File on the Documentum Server
On the Documentum Server computer, you can change the settings in the server.ini file to allow for additional concurrent sessions.
- The concurrent_sessions variable controls the number of connections the Documentum server can handle concurrently. This parameter should accommodate for the sum of all the max_session_count values in your environment.
If you plan to use the Oracle WebCenter Content Service for Documentum with several different docbases, you must modify the server.ini for each docbase. When making these configuration changes, consider the following:
- As with any configuration changes, take into account any hardware limitations.
- The configuration settings depend on both existing and projected Documentum usage.