Disabling embedded Tivoli Access Manager client using wsadmin

Follow these steps to unconfigure the Java Authorization Contract for Containers (JACC) provider for Tivoli Access Manager.

Overview

In a Network Deployment architecture, ensure that all the managed servers, including node agents, are started. Perform the following process once on the deployment management server. Details of the unconfiguration are forwarded to managed servers, including node agents, when a synchronization is performed. The managed servers require their own reboot for the configuration changes to take effect.

Note: It is also possible to unconfigure using the administrative console. For details on unconfiguring the embedded Tivoli Access Manager client using the WebSphere Application Server administrative console, refer to Disabling embedded Tivoli Access Manager client using the administrative console.

Procedure

1. Restart the deployment manager process.

2. Start the wsadmin command-line utility. The wsadmin command is found in theinstall_dir/bin directory

3. From the wsadmin prompt, enter the following command:

   WSADMIN>$AdminTask unconfigureTAM -interactive You are prompted to enter the following information:

   Option	Description
   WebSphere Application Server node name	Enter an asterisk (*) to select all nodes.
   Tivoli Access Manager administrator user name	Enter the Tivoli Access Manager administration user ID, as created at the time of Tivoli Access Manager configuration. This name is usually, sec_master.
   Tivoli Access Manager administrator user password	Enter the password for the Tivoli Access Manager administrator.
   Force	Enter yes, if you want to ignore errors when unconfiguring the JACC provider for Tivoli Access Manager. Enter this option as yes only when the Tivoli Access Manager domain is in an irreparable state.
   Defer	Enter no, to force the unconfiguration of the connected server. Enter No for the unconfiguration to proceed correctly.

4. When all information is entered, enter F to save the properties or C to cancel from the unconfiguration process and discard the entered information.

5. Optional: Synchronize all nodes.

6. Restart all WebSphere Application Server instances for the changes to take effect.