With TAMeb, you may have accidentally unconfigured the TAM Policy Server before you unconfigured the authorisation server or WebSEAL instances.

This creates a problem, as now there is no way to unconfigure WebSEAL once the Policy Server has been unconfigured.

The way to solve this is to just delete the flags that TAM uses to tell if a component has been configured.

For UNIX:

The flags are in the directory “/opt/PolicyDirector/.configure”, as shown below

# ls -la /opt/PolicyDirector/.configure

drwxrwxr-x  2 ivmgr ivmgr 4096 Jan  9 14:06 .

drwxrwxr-x 12 ivmgr ivmgr 4096 Feb 24 11:20 ..

-rw-r--r--  1 root  root     0 Jan  9 14:06 PDAcld-PD

-rw-r--r--  1 ivmgr ivmgr   47 Feb 18  2008 PDlic.txt

-rw-r--r--  1 root  root     0 Jan  9 13:51 PDMgr-PD

-rw-r--r--  1 root  root     0 Jan  9 13:50 PDRTE-PD

So this shows that the Authorisation server (PDAcld), the Policy Server (PDMgr) and the Runtime Environment (PDRTE) are configured. If we deleted, say, the PDAcld-PD file, then in pdconfig the Authorisation server will show as not being configured.  We can then configure the Authorisation server as normal.

For Windows:

The flags are in the registry “HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\<component>\<version>”

If you change the value of ‘Configured’ to ‘No’ - then this component will show up as not being configured. We can then configure it as normal.

Note:

As of TAMeb 6.1, WebSEAL uses the existence of the configuration file and the "status" key in the webseal-config stanza to determine which WebSEAL instances exist and their configuration state