Summary of Key User IDs for the Integrated e-mail Archiving and Records Management Solution

Published 09 March 2006

More options


Authors: Wei-Dong Zhu


This technote summarizes the various user IDs used in the e-mail archiving and records management solution.


The e-mail archiving and records management solution architecture is open, portable, and extensible. There are four main components involved in the integrated solution:

  • Content Manager: Used as the backend server for the content repository
  • CommonStore for Lotus Domino (CSLD) or CommonStore for Exchange Server (CSX): Used as the archiving engine that archives e-mail messages including attachments to Content Manager
  • Records Manager: Used as the engine to provide the records management function
  • Content Manager Records Enabler: Works with both Content Manager and Records Manager to provide records management capability to Content Manager, and thus records enabling the entire integrated solution

Because there are four products involved in this integrated solution, there are multiple user IDs involved in the solutions. These IDs are used to enable communication between various products and execution of tasks.

In this technote we provide an overview of all the key user IDs that are used for different components. You should understand the importance of these IDs with the effected components.

The users IDs are summarized in the following table.

Product that uses
the user ID
System that the ID belongs toSample or default
user ID name
CommonStore for Lotus DominoDomino CSLD Task
Content Manager CSLD
CommonStore for Exchange ServerExchange ServerCSX Admin
Content ManagerCSX
Content Manager Records EnablerContent ManagerCMREID
Content ManagerRMEADMIN (or icmadmin)
Records ManagerRecords Managerirmwas
administrator (default)
Content Manager Content Manager icmadmin

User IDs for CommonStore for Lotus Domino

CommonStore for Lotus Domino uses at least two user IDs, as described in the following table.

User ID type
(sample user ID)
Domino user ID
(CSLD Task or CS Task)
The CommonStore Task is a program that interfaces with Domino. It accesses a Domino system using the Domino APIs. It needs this Domino user ID to log on to the system.
The CommonStore Task needs to search through all the mail databases that have e-mails to be archived.
This user ID must therefore be able to log into the Domino system and have access to all the mail databases that need to have e-mails to be archived.
The CommonStore Task needs to read its configuration from the Domino’s configuration database. The user ID must therefore have read access to the configuration database.
The CommonStore Task processes jobs in the job database. The user ID therefore needs access to all jobs in the job database. The role [CSLDUser] is predefined in the job database and it should be assigned to this user.
Content Manager user ID
(ArchPro or CSLD)
The CommonStore ArchPro is a program that interfaces with Content Manager. It accesses the Content Manager system using the Content Manager APIs. It needs this Content Manager user ID to log on to the system. The ArchPro configuration file (archint.ini) specifies the Content Manager user ID that is used by ArchPro. The user ID has to have the privileges to store, update, and delete documents in the Content Manager system.
At least one item type has to be defined for CommonStore to be able to archive e-mails into Content Manager. The ACL for this item type should include the Content Manager user ID used by ArchPro.

User IDs for CommonStore for Exchange Server

CommonStore for Exchange Server uses at least two user IDs, as described in the following table.

User ID type
(sample user ID)
Exchange Server user ID
(CSX Admin)
This ID is used for all configuration steps, to run the CSX System Manager, and to run the CSX Task. This user ID should be added to the Windows groups Schema Administrators and Domain Administrators. Grant the user ID permissions Folder visible, Create items, and Read items to the Organizational Forms libraries for the languages supported by your Exchange environment. Give the user ID the role Exchange Administrator on the entire Exchange Organization.
Content Manager user ID
This user ID must have the appropriate privilege set to create, update, and delete items. You need to add this user to the item type created to store archived e-mails from the Exchange Server.

User IDs for Content Manager Records Enabler

Content Manager Records Enabler needs at least two IDs, as shown in the following table.

User ID type
(sample user ID)
Content Manager user ID
This user ID is created by the Content Manager enable code, but it has to exist on the operating system level on the machine running the Content Manager Library Server. The user has to be in the DB2 administrator group.
It is a Content Manager system administrator ID. Records Enabler saves this user ID in the host configuration, and uses it to configure Content Manager. For example, Records Enabler uses this user ID to create the needed item types, privilege sets, and ACLs when a Content Manager system is records enabled. This is also the ID that is stored in the WebSphere® Data Source and later used to add (and remove) triggers to eRecord-enabled item types. This user should not be imported into Records Manager. It is meant to be used under the covers by the Record Enabler code.
Content Manager user ID also is a
Records Manager user ID
(RMEADMIN or icmadmin)
This user ID should be used by the Records Enabler administrator to log into the Records Enabler administration client. Records Enabler does not create this user ID automatically. This user should be first created in Content Manager before the Records Enabler installation. It can be the Content Manager system administrator ID (for example, icmadmin). The user does not need to have any explicit Content Manager permissions. At a minimum, this user can be assigned the privilege set NoPrivs and the ACL NoAccessACL. When this user logs into the Records Enabler administration client, the CMREID user will be used to perform any necessary Content Manager configurations.
After creating this user ID in Content Manager, this user should be imported into Records Manager and given the System Configuration Management function access. This user does not require any other Records Manager permissions to use the Records Enabler administration client.

User IDs for Records Manager

Records Manager needs at least three IDs, as described in the following table.

User ID type
(sample user ID)
irmwas This is the Connection Factories Authentication User. You must create this user ID first in the operating system before installing Records Manager. The user ID does not need any special rights and is used just for authentication. This user ID must not be longer than 8 characters (which is the current WebSphere limitation). An application component uses a connection factory to access a connection instance, which the component then uses to connect to the underlying enterprise information system (EIS). Examples of connections include database connections, Java Message Service connections, and SAP R/3 connections.
irmadminThis is the Records Manager database schema owner. This user has the database administration privileges in the Records Manager database. Important: This user must exist first before the installation of Records Manager because it is not created automatically during the installation.
AdministratorThe default Records Manager administrator user ID with a default password of “cronos”.

Other important user IDs

There are other important IDs used by Content Manager, DB2, and WebSphere, as described in the following table.

System User IDDescription
Content Manager icmadminLibrary Server administrator ID
Content Manager rmadmin Resource Manager administrator ID
Content Manager icmcontA connection user ID that is used for clients to connect to the Library Server database if they do not have a valid database user ID
DB2db2admin DB2 administrator ID
WebSpherewasadmin WebSphere administrator ID

Special Notices

This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment.

Follow IBM Redbooks

Follow IBM Redbooks