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 4, 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.
If an argument is passed to the Central Administration executable that is also configured in the file, the value provided in the command line overrides the value in the configuration file.
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.sh [options]
On Windows
tibemsca.bat [options]
 
To configure Central Administration server settings, use the command line arguments shown in Table 4.
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.
Specifies the working data directory. The Central Administration server stores its working data files in the path given. This location must exist.
If this argument is not specified, the default is to store working data files in a directory called emsca_data within the current working directory.
You can also configure the working directory by setting the system property or configuration file property named com.tibco.emsca.data.dir.
If you run several distinct Central Administration servers, you must supply a unique path location for each server.
Points the Central Administration server to a file containing configuration properties. For more information see Create a Configuration File.
By default, the server looks for the file emsca.properties in the current directory.
host:port
Specifies the HTTP user interface host and port. Browsers send graphic user interface requests (using the HTTP protocol) to this service. You may specify host:port, or just port.
If this argument is not present, the default is *:8080. Note that * implies all interfaces on the machine.
When specifying the host and port on the command line, you must escape the argument if the * character is specified. For example, on Windows platforms:
You can also configure the HTTP interface by specifying the configuration property com.tibco.emsca.http.hostport.
Specifies the number of concurrent deployment tasks that can be active at any one time during a deployment. Each deployment task implies a connection to an EMS server.
The number given should be greater than 0. If this argument is not present, the default is 10 concurrent tasks.
You can also configure the concurrent deployments using the property com.tibco.emsca.concurrent.tasks.
Configures the Central Administration server to configure security using the Java Authentication and Authorization Service (JAAS).
When present, the Central Administration server configures security using the JAAS configuration file at path. When absent, the server neither requires nor verifies credentials.
Optional flag specifying the path to a certificate providing the identity of the Central Administration server to EMS servers. The identity certificate must include its private key.
The --ems-ssl-identity option can be specified with or without the --ems-ssl-password option.
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.
You can also include the identity by including the property com.tibco.ems.ssl.identity.
Provides the SSL password associated with the private key or store set with the --ems-ssl-identity flag. This setting is optional.
If the --ems-ssl-password option is provided with --ems-ssl-identity, the Central Administration server does not prompt for a certificate password.
Note that providing a private key on the command line is not recommended and may pose a security risk. Consider configuring this property using a configuration file. If you must provide the password on the command line or in a configuration file, please use tibemsadmin -mangle to generate an obfuscated version first.
You can include the password in a configuration file using the com.tibco.ems.ssl.password parameter.
Sets the SSL policy for the Central Administration server. This optional flag specifies the policy of iteration over the EMSCA Deployment Listens when communicating with an EMS server. Note that the Central Administration server only communicates with the EMS server using the EMSCA Deployment Listens specified on the Server Properties page.
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.
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