Disable embedded Tivoli Access Manager client using wsadmin

 

+

Search Tips   |   Advanced Search

 

Overview

In a network deployment architecture ensure all managed servers, including node agents, are started then 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 then require their own reboot for the configuration changes to take effect.

To unconfigure the Tivoli Access Manager JACC provider:

 

Procedure

  1. Disable global security by clicking Security > Global security and deselect the Enable global security option.

  2. Restart the server or, in a network deployment architecture, restart the deployment manager process.

  3. Start the wsadmin command line utility. The wsadmin command is found in install_dir\AppServer\bin.

  4. 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 * to select all nodes.
    Tivoli Access Manager administrator's 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's user password Enter the password for the Tivoli Access Manager administrator.
    Force Enter yes if you want to ignore errors when unconfiguring the Tivoli Access Manager Java Authorization Contract for Containers (JACC) provider. 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.

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

  6. Optional: If you want security enabled, not using Tivoli Access Manager, re-enable global security.

  7. Optional: In network deployment environments, synchronize all nodes.

  8. Restart all WAS instances for the changes to take effect.

 

See Also

Disable embedded Tivoli Access Manager client