InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.46: Administering WebSphere administrative servers >
6.6.46.7: Establishing multiple administrative servers on an AS/400 or iSeries machine

6.6.46.7: Establishing multiple administrative servers on an AS/400 or iSeries machine

On the AS/400 and iSeries systems, multiple WebSphere administrative servers can be run on a single machine, whether or not the servers share a common administrative database.

The following administrative server properties are provided in the administrative server configuration file (admin.config) to support running multiple administrative servers on the same machine.

server.root
The default product installation directory. Used to locate properties files, servlets, and other WebSphere resources.
com.ibm.websphere.servlet.admin.config.file
Override to specify the full path, including filename, to the admin.config file, instead of using server.root/bin
com.ibm.websphere.servlet.initialEJSSetup.file
Override to specify the full path, including filename, to the initialEJSSetup.xml file, instead of using the server.root/properties directory. Used to created the initial system configuration.
com.ibm.websphere.servlet.default.servlet.engine.file
Override to specify the full path, including filename, to the default.servlet_engine file, instead of using the server.root/properties directory. Used to create the initial system configuration
com.ibm.websphere.servlet.webapp.root.directory
Override to specify the directory containing the webapp configuration tree, instead of using server.root/hosts. Used to create the initial system configuration.
com.ibm.websphere.servlet.admin.bootstrap.file
Override to specify the full path, including filename, to the bootstrap.properties file, instead of using the server.root/properties directory. The load order for the plug-in configuration used by the admin server is now:
  1. This property
  2. The root of the classloader (for example, a path on the classpath)
  3. The server.root/properties directory

All configuration for the plug-in used in the administrative server is acquired from this file and has no dependency on server.root.

The queues, rules, and vhosts property files are written to the ose.tmp.dir location specified in bootstrap.properties. The default is server.root/temp.

An additional property can be set from the WebSphere Administrative Console. Add it as a command line argument of the target application server, again using the standard Java command line argument notation -D property_name=property_value:

default.client.encoding
The default language encoding to be used by the servlet engine for writing client data. Standard encoding values are listed in Java 2 documentation.

Go to previous article: Using administrative server agents Go to next article: Administering generic servers

 

 
Go to previous article: Using administrative server agents Go to next article: Administering generic servers