IBM FileNet P8, Version 5.2.1            

Moving Content Platform Engine from global security to a security domain

When you deploy Content Platform Engine on WebSphere® Application Server, it is automatically (by default) governed by WebSphere global security. If you created one or more WebSphere security domains, you can have Content Platform Engine use one of them instead.

Procedure

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

  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 global security to a security domain
    Version Steps
    7.0 Complete the steps of the procedure in Creating multiple security domains as guided by the following substeps:
    1. Complete step 1 through 4 of the procedure; but in step 2 click Copy Global Security instead of New.
    2. In step 5, assign the Content Platform Engine application server cluster or application server instance to the security domain.
    3. In step 6, ensure that these security attributes are as follows:
      • User realm: Ensure that the LDAP configuration of the security domain is identical to the WebSphere global security configuration. If you used Configuration Manager to configure LDAP at the global security level, use Configuration Manager to configure LDAP for the security domain.
      • Java 2 security: Select Customize for this domain and disable the Use Java 2 security to restrict application access to local resources option.
    4. Complete steps 7 and 8 of the procedure.
    8.0 Complete the steps of the procedure in Configuring multiple security domains as guided by the following substeps:
    1. Complete steps 1 and 2 of the procedure; but in step 2 click Copy Global Security instead of New.
    2. In step 3, assign the Content Platform Engine application server cluster or application server instance to the security domain.
    3. In step 4, ensure that these security attributes are as follows:
      • User realm: Ensure that the LDAP configuration of the security domain is identical to the WebSphere global security configuration. If you used Configuration Manager to configure LDAP at the global security level, use Configuration Manager to configure LDAP for the security domain.
      • Java 2 security: Select Customize for this domain and disable the Use Java 2 security to restrict application access to local resources option.
    4. Complete steps 5 and 6 of the procedure.
    8.5.5 Complete the steps of the procedure in Creating new multiple security domains as guided by the following substeps:
    1. Complete steps 1 and 4 of the procedure; but in step 2 click Copy Global Security instead of New.
    2. In step 5, assign the Content Platform Engine application server cluster or application server instance to the security domain.
    3. In step 6, ensure that these security attributes are as follows:
      • User realm: Ensure that the LDAP configuration of the security domain is identical to the WebSphere global security configuration. If you used Configuration Manager to configure LDAP at the global security level, use Configuration Manager to configure LDAP for the security domain.
      • Java 2 security: Select Customize for this domain and disable the Use Java 2 security to restrict application access to local resources option.
    4. Complete steps 7 and 8 of the procedure.


Last updated: March 2016
p8pcc321.htm

© Copyright IBM Corporation 2016.