Configure the JACC provider for TAM using the wsadmin utility

 

+

Search Tips   |   Advanced Search

 

Overview

In a network deployment architecture, verify that all the managed servers, including node agents, are started. The following configuration is performed once on the deployment manager server. The configuration parameters are forwarded to managed servers, including node agents, when a synchronization is performed. The managed servers then require their own restart for the configuration changes to take effect. Use the wsadmin utility to configure Tivoli Access Manager security for WebSphere Application Server:

 

Procedure

  1. Start WebSphere Application Server.

  2. Start the command-line utility by running the wsadmin command from the install_dir/bin directory.

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

    $AdminTask configureTAM -interactive

    You are prompted to enter the following information:

    Option Description
    WebSphere Application Server node name Specify a single node or enter an asterisk (*) to choose all nodes.
    Tivoli Access Manager Policy Server Enter the name of the TAM policy server and the connection port. Use the format, policy_server : port. The policy server communication port is set at the time of TAM configuration – the default port is 7135.
    Tivoli Access Manager Authorization Server Enter the name of the TAM authorization server. Use the format auth_server : port : priority. The authorization server communication port is set at the time of TAM configuration – the default port is 7136. More than one authorization server can be specified by separating the entries with commas. Having more than one authorization server configured is useful for failover and performance. The priority value is the order of authorization server use. For example: auth_server1:7136:1,auth_server2:7137:2. A priority (of 1) is still required when configuring against a single authorization server.
    WebSphere Application Server administrator's distinguished name Enter the full distinguished name of the WAS security administrator ID as created in Creating the security administrative user. For example: cn=wasadmin,o=organization,c=country
    Tivoli Access Manager user registry distinguished name suffix For example: o=organization,c=country
    Tivoli Access Manager administrator's user name Enter the TAM administration user ID, as created at the time of TAM configuration. This ID is usually, sec_master.
    Tivoli Access Manager administrator's user password Enter the password for the TAM administrator.
    Tivoli Access Manager security domain Enter the name of the TAM security domain that is used to store users and groups. If a security domain is not already established at the time of TAM configuration, click Return to accept the default.
    Embedded Tivoli Access Manager listening port set WAS needs to listen on a TCP/IP port for authorization database updates from the policy server. More than one process can run on a particular node and machine so a list of ports is required for the processes. Enter the ports that are used as listening ports by TAM clients, separated by a comma. If you specify a range of ports, separate the lower and higher values by a colon. For example, 7999, 9990:9999.
    Defer Set to yes, this option defers the configuration of the management server until the next restart. Set to no, configuration of the management server occurs immediately. Managed servers are configured on their next restart.

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

 

What to do next

Now enable the JACC provider for Tivoli Access Manager- Enable the JACC provider for Tivoli Access Manager.


 

Related Tasks

Configure the JACC provider for Tivoli Access Manager using the administrative console
Create the security administrative user

 

See Also


Tivoli Access Manager JACC provider configuration