In development environment, Policy server instance is centrally located. JRTE,ADK and WebSEAL instances are installed and configured on development machines to point to Policy Server.
When Policy Server crashes for whatsoever reasons, WebSEAL, AMADK instances can not be unconfigured and configured to a new Policy Server instance. It throws a message saying "policy server instance not available". we can not uninstall WebSEAL or AMADK with out unconfiguration. In such cases, following steps will help you to configure WebSEAL and AMADK instances.
1. Take pd.sth and pd.kdb from /var/PolicyDirector/keytab folder (in Linux) or equivalent as per Operating System.
2. Copy them to /Tivoli/PolicyDirector/keytab on development machines. If these files are already there, overwrite them with files which you copied from central Policy Server
3. Open ldap.conf and pd.conf on development machine at /Tivoli/PolicyDirector/etc folder. Replace old policy server machine name with new policy server machine name.
4. Go to Tivoli Access Manager - configuration window. Click on unconfigure WebSEAL. It will prompt for sec_master password after which it should unconfigure successfully.
5. Repeat Step 4 for AMADK as well.
6. Now you can configure AMADK and WebSEAL to latest Policy Server instance.
Subscribe to:
Post Comments (Atom)
Relevant Information here:
0 comments:
Post a Comment