In order to enable communication between WebSphere® and Content Engine, you must configure LDAP
settings on the WebSphere Application
Server.
To configure stand-alone LDAP:
- Open the WebSphere administrative
console.
- Navigate to the security settings page.
Option |
Description |
WebSphere Application
Server 6.1 |
Navigate to . |
WebSphere Application
Server 7.0 |
Navigate to . |
- Disable security using the following Security settings:
- Turn off (clear) the Enable Administrative Security flag.
- Turn off (clear) the Enable application security flag.
- Turn off (clear) the Use Java 2 security to restrict
application access to local resources security flag.
- From the bottom of the panel, in the dropdown list called Available
realm definitions, select Standalone LDAP registry and
click Configure.
- Configure the LDAP provider to exactly match the corresponding
settings on the Content Engine application
server.
Tip: Open the
WebSphere administrative console for
Content Engine to the same panels to see
and copy all settings.
- Primary administrative user name
- Automatically generated server identity
- Type
- Host
- Port
- Base distinguished name (DN)
- Bind distinguished name (DN)
- Bind password
- Configure the LDAP user registry settings to exactly match
the corresponding settings on the Content Engine application server.
Tip: Open the
WebSphere administrative
console for
Content Engine to
the same panel to see and copy all settings.
- User filter
- Group filter
- User ID map
- Group member ID map
- Certificate map mode
- Certificate filter
- Save these settings.
- Next to Available realm definitions,
ensure that Standalone LDAP registry is still
selected, and click Set as current.
- Re-enable the following Security settings:
- Turn on (select) the Enable Administrative Security flag.
- Turn on (select) the Enable application security flag.
- Turn off (clear) the Use Java 2 security to restrict
application access to local resources flag.
The IBM® FileNet® P8 Platform uses
LDAP-based security, and does not support Java™ 2 security. Enabling Java 2 security will cause unexpected behavior.
- Save your changes to the master configuration.
- Test the connection on the Standalone LDAP registry page.
If the test fails, correct the error before proceeding. If it passes,
click OK to return to the previous page.
If you see a message about the ID not existing in the user
repository, you can ignore it.
- Stop and restart the application server.