Before you begin
Docs requires an administrative user to be associated with the following security roles in IBM
Connections application. With IBM
Connections installed, these roles have already been mapped to a user.
By default, IBM
Connections has already created an administrative user. The J2C alias is connectionsAdmin
Docs and IBM
Connections are in the same managed cell, and you plan to use the same administrative user for IBM
Docs, then you don't need to perform this task. Just make sure you use the same J2C alias name in the response file.
Docs and IBM
Connections are not in the same managed cell, or there are requirements that IBM
Docs needs to use a dedicated administrative user, you need to perform this task and complete the following items:
- Use a dedicated user account in LDAP to map to the required IBM Connections application security roles.
- Create J2C authentication data in the IBM Docs managed cell.
- Use this J2C alias in the response file (later topics).
About this task
Create administrators in IBM
Connections for IBM
Docs if you meet either of the following conditions:
- Use a different administrator rather than IBM Connections administrators
- The IBM Docs and IBM Connections installations are in different managed cells
To configure administrative access to the IBM
Connections application specially for IBM
Docs, complete the following steps:
Parent topic: Installing IBM Connections
- From the IBM Connections server’s WebSphere® Application Server Integrated Solutions Console, select Applications -> Application Types -> WebSphere enterprise applications.
- Find and click the link to the application that you want to configure. For example, click Files application.
- Click the Security role to user/group mapping link.
- To map a user to the administrative role, select the check box beside the admin role and then click Map users. For Files, select admin and search-admin and for Communities, select dsx-admin and search-admin.
- In the Search String box, type the name of the person to set as an administrator and then click Search. If the user exists in the LDAP directory, the name displays in the Available list.
- Select the name from the Available list and move it to the Selected column by clicking the arrow.
Note: Make sure the original users are in the list.
- Click OK.
- From the Enterprise Applications -> application -> Security role to user/group mapping page, click OK and then click Save to save the changes.
- Repeat steps 1-8 for all other applications, for example Files and Communities.
- Synchronize and restart all your WebSphere Application Server instances.