WAS v8.5 > Secure applications > Authenticate users > Select an authentication mechanism > Configure LTPA and work with keys > Step 1. Configure LTPA and generate the first LTPA keys.

Start and log off the dmgr console

Before beginning

To access the dmgr console, first install WebSphere Application Server and the dmgr console.

You start the dmgr console, access the console through a web browser, and then log into the dmgr console. After finishing working in the dmgr console, save your work and log out.

1. Start the desired dmgr console by starting the server process that runs the console application.

   We can start an application server or an administrative agent server.

   Check the SystemOut.log file of the server that runs the console application to verify the console application starts successfully. If the console application starts successfully, you see the WSVR0221I: Application started: isclite message.

   If we cannot start the dmgr console because the console port conflicts with an application that is already running on the machine, change the port number in both...

   installation root/profiles/profile name/config/cells/cell_name/nodes/node_name/serverindex.xml
   installation root/profiles/profile name/config/cells/cell_name/virtualhosts.xml

   Change all the occurrences of the console port to a new port number. Alternatively, shut down the other application that uses the conflicting port before starting the WAS product.

2. Access the dmgr console.

   1. Enable cookies in the web browser that we use to access the dmgr console.

   2. Enable JavaScript.

      Enablement of JavaScript is required. You must enable JavaScript so that all the features of the dmgr console are available.

      If the application server is on Windows Server 2008 and you are accessing the console with Microsoft Internet Explorer V8.0, disable the enhanced security configuration in the browser. Otherwise, the console does not work correctly.

   3. In the same web browser, type...
      http://your_fully_qualified_server_name:port_number/ibm/console

      ...where your_fully_qualified_server_name is the fully qualified host name for the machine containing the administrative server, and port_number is the dmgr console port number. When the dmgr console is on the local machine, your_fully_qualified_server_name can be localhost unless security is enabled. On Windows platforms, use the actual host name if localhost is not recognized. If security is enabled, your request is redirected to...

      https://your_fully_qualified_server_name:port_number/ibm/console

      ...where your_fully_qualified_server_name is the fully qualified host name for the machine containing the administrative server, and port_number is the dmgr console secure port number.

      The dmgr consoles for the application server and the administrative agent use 9060 as the default port number for an unsecure dmgr console and 9043 as the default port number for a secure dmgr console. Each new dmgr console deployed during profile creation is assigned a new unsecure port number, and, if you enable security during profile creation, a new secure port number. Whichever unsecure dmgr console you create first is assigned port 9060, as long as the port is available. Likewise, whichever secure dmgr console you create first is assigned port 9043, as long as the port is available.

      For a listing of supported web browsers, see WAS system requirements.

   4. Wait for the dmgr console to load into the browser.

      A login page displays after the dmgr console starts.

3. Log into the dmgr console.

   The dmgr console can be for an application server or an administrative agent.

   1. If you are logging into the dmgr console for the administrative agent, and we have registered at least one node with the administrative agent, select the node to administer, and click Continue.

      The node can be the administrative agent node or a node for one of the application servers registered to the administrative agent. After you select a node, the login procedure is the same as that for the other server types, and for administrative agents with no nodes registered.

   2. Enter the user name or user ID.

      The user ID lasts only for the duration of the session for which it is used to log in.

      Changes made to server configurations are saved to the user ID. Server configurations also are saved to the user ID if a session timeout occurs.

      If you enter an ID that is already in use and in session, you are prompted to do one of the following actions:

      • Log out the other user with the same user ID. We can recover changes made during the other user's session.

      • Return to the login page and enter a different user ID.

   3. If the console is secure, you must also enter a password for the user name. The console is secure if someone has taken the following actions for the console:
      • Specified security user IDs and passwords
      • Enabled global security

   4. Click OK.

4. Log off the dmgr console. Click System administration > Save changes to master repository > Save to save work. Then click Logout to exit the console.

   If you close the browser before saving your work, we can recover any unsaved changes the next time that you log in under the same user ID.

Results

You have set up the dmgr console environment, accessed the dmgr console, and logged out of the dmgr console.

What to do next

Use the dmgr console to manage the product.

Subtopics

• uisc_login.html
  
• ucon_master_config.html
  
• Logging in
  Enter the user ID and password to access the console.
• Save changes to the master repository
  Use this topic to update the master repository with your dmgr console changes, to discard your dmgr console changes and continue working with the master repository, or to continue working with your dmgr console changes that are not saved to the master repository.

Related

tcfg_data.html
tsec_install.html
tsec_csec2.html
tcon_console.html
tins_portep.html
tagt_adminagent.html
trun_svr_manage.html

+

Search Tips   |   Advanced Search