IBM FileNet P8, Version 5.2.1            

Moving Content Platform Engine from a security domain to global security

You can move Content Platform Engine from a WebSphere® security domain back to WebSphere global security.

Procedure

To move Content Platform Engine from a security domain to global security:

  1. Start the WebSphere Application Server administrative console.
  2. Complete the steps in one of the rows of the following table, depending on the version of WebSphere Application Server where Content Platform Engine is deployed:
    Table 1. Steps to move Content Platform Engine from a security domain to global security
    Version Steps
    7.0
    1. Click Security > Security domains.
    2. Remove the entire cell or the selected specific servers and cluster that were previously assigned to Content Platform Engine in the security domain.
    3. Ensure that the LDAP configuration of the global security is identical to the security domain configuration. If you used Configuration Manager to configure the LDAP for the security domain, use Configuration Manager to configure LDAP for WebSphere global security.
    4. Use Configuration Manager to create the JAAS logins at the global security level.
    5. Ensure the Java 2 security is disabled in global security configuration.
    6. Restart the application server for your changes to take effect.
    8.0
    1. Click Security > Security domains.
    2. Remove the entire cell or the selected specific servers and cluster that were previously assigned to Content Platform Engine in the security domain.
    3. Ensure that the LDAP configuration of the global security is identical to the security domain configuration. If you used Configuration Manager to configure the LDAP for the security domain, use Configuration Manager to configure LDAP for WebSphere global security.
    4. Use Configuration Manager to create the JAAS logins at the global security level.
    5. Ensure the Java 2 security is disabled in global security configuration.
    6. Restart the application server for your changes to take effect.
    8.5.5
    1. Click Security > Security domains.
    2. Remove the entire cell or the selected specific servers and cluster that were previously assigned to Content Platform Engine in the security domain.
    3. Ensure that the LDAP configuration of the global security is identical to the security domain configuration. If you used Configuration Manager to configure the LDAP for the security domain, use Configuration Manager to configure LDAP for WebSphere global security.
    4. Use Configuration Manager to create the JAAS logins at the global security level.
    5. Ensure the Java 2 security is disabled in global security configuration.
    6. Restart the application server for your changes to take effect.


Last updated: October 2015
p8pcc323.htm

© Copyright IBM Corporation 2015.