InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.46: Administering WebSphere administrative servers >
6.6.46.0: Administrative server configuration file properties

6.6.46.0: Administrative server configuration file properties

The admin.config file is located in:

product_installation_root/bin/admin.config

  Directives in admin.config are similar to their counterparts on the Java command line for the administrative server. The command line argument name is appended to a standard package name for the administrative server. For example, the command line argument:
-lsdPort
becomes
com.ibm.ejs.sm.adminServer.lsdPort
in admin.config.

Some admin.config file properties are platform specific. Review your admin.config file to see which properties appear in your installation. Click any property in the table for a description of that property. Platform specific properties are identified by an icon.

Administrative server and database settings

com.ibm.ejs.sm.adminServer.agentMode
Whether this administrative server should run as a full administrative server (false), or in administrative server agent mode (true).

  • true
  • false
com.ibm.ejs.sm.adminServer.bootFile
The full path to a file containing configuration data for starting the administrative server, and product in general.
com.ibm.ejs.sm.adminServer.bootstrapHost
Fully qualified host name of the machine containing the administrative server
com.ibm.ejs.sm.adminServer.bootstrapPort
Port number for the administrative server. See also the information about administering ports.
com.ibm.ejs.sm.adminserver.classpath
Values for the administrative server classpath, such as:
d\:/WebSphere/AppServer/properties;
d\:/WebSphere/AppServer/lib/bootstrap.jar
com.ibm.ejs.sm.adminServer.connectionPoolsize
The number of concurrent database connections to allow from the administrative server to the administrative database. The default value is 5.
com.ibm.ejs.sm.adminServer.dbdataSourceClassName
The data source corresponding to the administrative database.
COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource 
com.ibm.ejs.sm.adminServer.dbInitialized
Whether to create the administrative database tables the next time you start the administrative server (typically, the first time you start the administrative server after product installation).

  • true
  • false

By default, this flag is initially set to false. The first time you run the administrative server, the administrative server creates the database table or tables that it needs to store administrative data. It sets this flag to true.

See the information about administering administrative servers for additional discussion of this setting.

In Version 4.0, this setting is called com.ibm.ejs.sm.adminServer.createTables.

com.ibm.ejs.sm.adminServer.dbpassword
The password for the administrative database
com.ibm.ejs.sm.adminServer.dbSchema
The database schema for the administrative database
Data source properties - com.ibm.ejs.sm.adminServer.dbUrl
What was called com.ibm.ejs.sm.adminServer.dbUrl in Version 3.5 is replaced by specific data source properties for each database brand, including a dbUrl property for certain brands.
com.ibm.ejs.sm.adminServer.dbuser
The administrative database user ID, such as db2user
com.ibm.ejs.sm.adminServer.diagThreadPort
The port on which DrAdmin listens
com.ibm.ejs.sm.adminServer.disableAutoServerStart
Whether to disable the feature that tries to start the application servers on an administrative node when the administrative node is started.

  • true - start the administrative server, but not any of the application servers on it
  • false - when the administrative server is started, try to start the application servers whose administrative settings indicate they should be started
com.ibm.ejs.sm.adminServer.disableEPM
Whether to disable the performance monitoring classes, to avoid collecting performance data when it is not needed.

  • true - disable EPM classes
  • false
com.ibm.ejs.sm.adminServer.disableLocationService
Whether to disable the location service daemon.
  • true - disable LSD
  • false

Applies only to Version 3.5, Standard Edition.

com.ibm.ejs.sm.adminServer.exclusiveDBAccess
Whether to true indicates exclusive acess to the database.

  • true - exclusive access enforced
  • false
com.ibm.ejs.sm.adminServer.jarFile
Paths to the JAR files required by the administrative server, such as:
product_installation_root/lib/repository.jar;
product_installation_root/lib/tasks.jar
com.ibm.ejs.sm.adminServer.logFile
The log files for recording administrative server events, such as:
product_installation_root/tranlog/your_server_name_tranlog1,
product_installation_root/tranlog/your_server_name_tranlog2
com.ibm.ejs.sm.adminServer.lsdHost
The host name of the administrative server
com.ibm.ejs.sm.adminServer.lsdPort
Port number for the administrative server Location Service Daemon. See also the information about administering ports.
com.ibm.ejs.sm.adminServer.managedServerClassPath
Used by the application server
com.ibm.ejs.sm.adminServer.nameServiceJar
A value such as:
product_installation_root/lib/ns.jar
UNIX identifiercom.ibm.ejs.sm.adminServer.nannyPort
The port on which the nanny process listens
UNIX identifiercom.ibm.ejs.sm.adminServer.processPriority
Possible values are:
  • 24 for Solaris
  • 28 for AIX
UNIX identifiercom.ibm.ejs.sm.util.process.Nanny.adminServerJvmArgs
JVM arguments for the nanny process
UNIX identifiercom.ibm.ejs.sm.util.process.Nanny.path
Classpath for the nanny process, such as:
product_installation_root\bin;
product_installation_root\SQLLIB\bin;
product_installation_root\SQLLIB\\function;
product_installation_root\jdk\bin
com.ibm.CORBA.ConfigURL
The path to the file specifying ORB configuration values, such as:
file\:/product_installation_root/properties/sas.server.props
com.ibm.CORBA.ServerSocketQueueDepth
The ServerSocket maximum queue depth. Specify an integer greater than 50. Values less than 50 or invalid integer values will cause a warning to be logged to the message file and the default value of 50 to be used.

This property allows the ServerSocket maximum queue depth to be increased beyond its default value of 50. The default value is according to the JDK122 javadoc for java.net.ServerSocket.

The ServerSocket queue is where incoming socket connection requests from clients are held until the server can accept the request. When the queue becomes full, other open socket requests from clients are rejected with a java.net.ConnectException. This exception will be returned to the client application. If clients are receiving java.net.ConnectExceptions, it is an indication that you should consider increasing the queue depth.

Note, some operating systems impose other limitations on the server socket queue depth. Become familiar with the guidelines imposed by your operating system. Setting this property to a value beyond the platform-imposed limitation will likely not have any effect.

install.initial.config
If set to true, attempts to create the default resources (such as the default application server) the next time you start the product administrative server.

  • false
  • true
server.root
See the installation root reference for the default values.
com.ibm.ejs.sm.adminServer.seriousEventLogSize
The number of entries to record in the serious events log. Allowing the log to grow too large can affect performance negatively. The default value is 1000 entries.
UNIX identifiercom.ibm.ejs.sm.util.process.Nanny.errtraceFile
The trace file for the nanny process, such as:
product_installation_root\logs\adminserver_stderr.log
com.ibm.ejs.sm.adminServer.qualifyHomeName
This value can be:

  • true
  • false
install.initial.config.file
The full path to the property file defining the default configuration, such as:
product_installation_root/properties/initial_setup.config
com.ibm.ejs.sm.adminServer.traceString
The trace specification for the administrative server. See the trace property reference for a description.
com.ibm.ejs.sm.adminServer.traceOutput
The trace output file for the administrative server. See the trace property reference for a description.
UNIX identifiercom.ibm.ejs.sm.util.process.Nanny.traceFile
The trace file for the nanny process, such as:
product_installation_root/logs/nanny.trace
UNIX identifiercom.ibm.ejs.sm.util.process.Nanny.maxtries
How many time the nanny process should attempt to start the administrative server before giving up. The default is 3.
com.ibm.ws.jdk.path
The path to the root directory of the JDK installed with the product, such as:
product_installation_root/jdk
Go to previous article: Administering WebSphere administrative servers Go to next article: Having administrative servers start automatically

 

 
Go to previous article: Administering WebSphere administrative servers Go to next article: Having administrative servers start automatically