InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.46: Administering WebSphere administrative servers >
6.6.46.6: Using administrative server agents

6.6.46.6: Using administrative server agents

The product installation program always installs full administrative servers. To produce an administrative agent, edit the administrative server configuration file.

  1. Install an administrative server on a machine.
  2. Edit the admin.config file in the bin directory of the product_installation_root.
    • Remove the name service JAR property:
      com.ibm.ejs.sm.adminServer.nameServiceJar=jar-file
      
    • Specify the dbUrl, dbUserId, and dbPassword properties:
      com.ibm.ejs.sm.adminServer.dbUser=user_name
      com.ibm.ejs.sm.adminServer.dbUrl=location
      com.ibm.ejs.sm.adminServer.dbPassword=password
      
    • Set:
      install.initial.config=false
    • Add the property:
      com.ibm.ejs.sm.adminServer.primaryNode=value
      where value is the name of the node containing the full administrative server to which this agent will connect. To be safe, use the fully qualified name.
    • Add the property:
      com.ibm.ejs.sm.adminServer.bootstrapHost=value
      where value is the host name of the machine containing the full administrative server. To be safe, use the fully qualified name.
    • Add the property:
      com.ibm.ejs.sm.adminServer.agentMode=true
    • Optionally, specify the properties:
      com.ibm.ejs.sm.adminServer.bootstrapPort=value
      com.ibm.ejs.sm.adminServer.lsdPort=value
      
      if the default values (9000 and 900, respectively) are not being used by the full administrative server. Both nodes must use the same values.
  3. Save the file.
  4. Start the full administrative server.
  5. Start the administrative agent the same way you started the full administrative server.
  6. Start the Java administrative console on the machine containing the administrative server agent. Pass the administrative console the host name of the machine containing the full administrative server:
    adminclient full_adminserver_hostname
    To be safe, use the fully qualified host name.
  7. Start the Java administrative console on the full administrative server machine. Confirm that the administrative server agent is displayed as a node in the topology.

    If the console was already running when you configured and started the agent, you might need to refresh the console in order to see the new node for the agent.

Go to previous article: Having administrative servers start automatically Go to next article: Establishing multiple administrative servers on an AS/400 or iSeries machine

 

 
Go to previous article: Having administrative servers start automatically Go to next article: Establishing multiple administrative servers on an AS/400 or iSeries machine