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:
- Start the WebSphere Application
Server administrative
console.
- 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 securityVersion |
Steps |
7.0 |
- Click .
- Remove the entire cell or the selected specific servers and cluster
that were previously assigned to Content Platform Engine in the security domain.
- 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.
- Use Configuration Manager to
create the JAAS logins at the global security level.
- Ensure the Java 2 security is disabled in global security configuration.
- Restart the application server for your changes to take effect.
|
8.0 |
- Click .
- Remove the entire cell or the selected specific servers and cluster
that were previously assigned to Content Platform Engine in the security domain.
- 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.
- Use Configuration Manager to
create the JAAS logins at the global security level.
- Ensure the Java 2 security is disabled in global security configuration.
- Restart the application server for your changes to take effect.
|
8.5.5 |
- Click .
- Remove the entire cell or the selected specific servers and cluster
that were previously assigned to Content Platform Engine in the security domain.
- 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.
- Use Configuration Manager to
create the JAAS logins at the global security level.
- Ensure the Java 2 security is disabled in global security configuration.
- Restart the application server for your changes to take effect.
|