A Documentum Messaging Services (DMS) server is an intermediary server that provides messaging services between an ACS or BOCS server and a web application server. The messaging server configuration object must be created and set up in the global registry using Documentum Administrator. Administrators with superuser privileges only can configure the messaging server configuration object. Administrators with superuser privileges connecting to 6.7 and below global registry can only create default messaging server configuration object. If a messaging server configuration object exists, administrator cannot create new objects.
You can create multiple messaging server configuration objects using Documentum Administrator 7.0 on 7.0 and later versions of Content Server and repositories. Use the File > New > Messaging Server Configuration in the Messaging Server list page.
Use the Administration > Distributed Content Configuration > Messaging Server navigation to access the Messaging Server Configuration list page.
To modify or view the DMS server configuration object, you must be connected to the repository known to DFC on the Documentum Administrator host as a global registry and you must be logged in as a user with superuser privileges. Administrators logging in to a Documentum 6 repository that is not the global registry do not see a Messaging Server Configuration list page. If they click the Messaging Server node, the system displays a message informing administrators that they logged in to a non-global registry repository and the messaging server configuration object is stored only in the global registry repository. The system also shows a link for the administrator to click to navigate to the login page of the global registry repository.
To view or modify the messaging server configuration:
Connect to the global registry known to DFC as a user with superuser privileges.
Navigate to Administration > Distributed Content Configuration > Messaging Server.
The Messaging Server Configuration list page appears. The messaging server configuration is not visible if you are not connected to the global registry.
Click the Global Registry Login link and connect to the correct repository if you see the following warning message instead of the Messaging Server Configuration list page:
Messaging Servers can only be created in repositories that are designated as global registries. The current repository is not a global registry. Click the link below to log in to the global registry repository known to DFC on the Documentum Administrator host. You must have superuser privileges to create Messaging Servers.
Select the messaging server configuration and then select View > Properties > Info.
The Messaging Server Configuration Properties - Info page appears.
View the properties or change the messaging flag:
Name: The name of the messaging server configuration.
Messaging Server Version: Indicates the version of the messaging server, which is automatically set when creating a new messaging server. The messaging server version must be 1.0 for Documentum 6.
Messaging: Select to enable content transfer messaging to the DMS server. This checkbox must be selected to enable asynchronous content transfer through BOCS and for predictive caching to work.
Clear the checkbox to disable content transfer messages to the DMS server, even if the DMS server is running.
Enter information in the BOCS Message Routing section:
Post URL: Type the hostname and port where to send messages to the DMS server. This is a required field.
Consume URL: Type the hostname and port where BOCS servers in pull mode pick up messages from the DMS server. If you do not have BOCS servers using the pull mode, then this field is optional.
Click OK to save changes made to the messaging server configuration object or Cancel to exit without saving the changes.
The Messaging Server Configuration list page appears.
To save time retyping existing information, you can copy a messaging server configuration using the Save As option. To copy a messaging server, you must be connected to the repository known to DFC on the Documentum Administrator host as a global registry and you must be logged in as a user with superuser privileges.
To copy a messaging server:
Connect with superuser privileges to the global registry repository.
Select Administration > Distributed Content Configuration > Messaging Server.
The Messaging Server page appears.
Click the Global Registry Login link and connect to the correct repository if you see the following warning message instead of the Messaging Server Configuration list page:
Messaging Servers can only be created in repositories that are designated as global registries. The current repository is not a global registry. Click the link below to log in to the global registry repository known to DFC on the Documentum Administrator host. You must have superuser privileges to create Messaging Servers.
On the Messaging Server page, do one of the following:
Select a messaging server in the Name column, then select File > Save As.
Select a messaging server in the Name column and then right-click. From the available menu options, select Save As.
The Messaging Server Configuration Properties page appears. The fields display the values copied from the selected messaging server; however, the Name field display Copy [x] of [name]/[display name] to keep the messaging server and display names unique.
Modify the properties on Info tab of the Messaging Server Configuration Properties page.
Click OK to save the changes or Cancel to exit without saving.