Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 Running the Central Administration Server : Starting and Stopping the Central Administration Server

Starting and Stopping the Central Administration Server
This section describes how to start and stop the Central Administration server.
Create a Data Directory
Before starting the Central Administration server for the first time, you must create a data directory for the server. This directory is where the server stores deployment and working directories for each EMS server it manages.
You cannot share the data directory between Central Administration server instances. That is, each running Central Administration server requires its own data directory.
On startup, the Central Administration server looks for a data directory named emsca_data in the working directory. If you wish to specify a different name or location, use the --data command line option or related configuration file property to point the server to the correct location.
Create a Configuration File
You can optionally create a configuration file to hold Central Administration server options, and pass this file to the server at startup. The properties that can be specified in the configuration file correspond to the startup options, and are described in Table 3, Central Administration Server Options.
The configuration file takes the form of a typical Java properties file and must use the .properties file extension. In a text-based file, specify one property on each line, using the format:
property=value
For example:
com.tibco.emsca.data.dir=/emsca_data
com.tibco.emsca.http.hostport=*:8080
com.tibco.emsca.jaas=/emsca_security/emsca.jaas
By default, the Central Administration server looks for a file named emsca.properties in the current directory. However, you can direct the server to a different file using the --config command line option.
Start the Central Administration Server
To start the Central Administration server from the command line, navigate to EMS_HOME/bin and run the script:
On UNIX
tibemsca [options]
On Windows
tibemsca.bat [options]
 
To configure Central Administration server settings, use the command line arguments shown in Table 3.
The command options to Central Administration server can also be passed using a configuration file described above in Create a Configuration File. However, the command options override any value specified in the configuration file.
host:port
If this argument is not present, the default is *:8080. Note that * implies all interfaces on the machine.
By default, the server looks for the file emsca.properties in the current directory.
When present, the Central Administration server configures security using the JAAS configuration file at path. When absent, the server neither requires nor verifies credentials.
Replaces the default JAAS emsca-admin group with one or more admin group names. Administrators running Central Administration utility executables must be in one of these admin groups.
Replaces the default emsca-guest group with one or more guest group names. JAAS guests can browse configurations, but are not able to modify, monitor, or deploy configurations.
The number given should be greater than 0. If this argument is not present, the default is 10 concurrent tasks.
Optional. Can be used if --ems-ssl-identity or --https-identity is provided.
Valid policy settings are:
REQUIRED — The Central Administration server only communicates with an EMS server using SSL listens. Any other type of listen is ignored.
PREFERRED — The Central Administration server attempts to communicate with an EMS server using SSL. If all the SSL listens for the EMS server fail, it then attempts non-SSL listens.
ANY — The Central Administration server attempts to connect through any of the listens defined in the configuration.
You can also configure the SSL policy using the com.tibco.emsca.ssl.policy parameter.
If the --ems-ssl-identity option is provided and --ems-ssl-password is not, the login screen to the Central Administration web interface presents fields for username, password, and certificate password. This scenario is only supported when JAAS is configured.
If the --ems-ssl-password option is provided with --ems-ssl-identity, the Central Administration server does not prompt for a certificate password.
The --https-identity option must be specified with the --https-password option.
Stop the Central Administration Server
You can stop the Central Administration server by ending the process using tools provided by your operating system.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved