Copyright © 1999-2015 TIBCO Software Inc. All Rights Reserved
Copyright © 1999-2015 TIBCO Software Inc. All Rights Reserved


Chapter 2 Creating an EMS Central Administration Server Component

Chapter 2
TIBCO Enterprise Messaging Service Central Administration Server (EMS Central Admin Server) provides a web-based GUI for configuring and monitoring multiple TIBCO Enterprise Message Service servers at one time.
To create and configure a TIBCO Enterprise Message Service Central Administration Server Component for TIBCO Silver Fabric, hereafter called simply a Central Admin Component, perform the following tasks:
Task A Create a Central Admin Component
1.
2.
Figure 1 Creating a TIBCO EMS Server Component
 
If you have more than one EMS Enabler installed then you will be presented with a dialog to choose which version you want to use. You should always use the latest Enabler unless you have some specific reason to use an older version.
3.
Figure 2 Configuring General Properties
 
4.
In almost all cases you should select the latest versions of any installed distributions shown.
Figure 3 Choosing TIBCO EMS Product Distribution Version
 
5.
Select EMS Central Administration Server as the EMS Execution Mode to continue creating a TIBCO EMS Server component.
Figure 4 Select the EMS Server Execution Mode
At this point you could have chosen to configure and publish a TIBCO EMS Server. If you choose to set the EMS Execution Mode to EMS Server then go to the section describing TIBCO Enterprise Message Service Basic Configuration settings page (EMS Server Execution Mode only) to create a TIBCO EMS Server Component.
6.
It is easiest and recommendable to configure the Central Administration Server using the properties exposed in the Component Wizard UI, but you can choose to configure the Central Administration Server Component by checking the Configure with Properties File checkbox.
Figure 5 Set up the Central Administration Server
If you keep the Configure with Properties File check box clear to use the property settings exposed by the Component Wizard UI for configuration then skip ahead to Configuring the Central Admin Component with the Component Wizard
a.
When the Configure with Properties File checkbox is selected the property settings exposed by the Component Wizard UI are hidden and the Component Wizard adds another page for uploading a custom properties file that you must create for your custom Central Administration Server installation configurations.
Create your custom properties file with one "property=value" pair per line specifying installation values for the EMS Central Administration Server. The properties file can be named anything, but it must use the .properties file extension. The properties file takes the form of a typical Java properties file that specifies one property on each line using the format:
property=value
For example:
#Comment lines start with #
com.tibco.emsca.data.dir=/emsca_data
com.tibco.emsca.http.hostport=*:8200
com.tibco.emsca.jaas=/emsca_security/emsca.jaas
Refer to the TIBCO Enterprise Message Service Central Administration Guide for more information on what properties may be modified.
b.
Server Port - Specifies the HTTP listen port for the Central Administration Server. Once the Central Admin Component is published and running on an Engine the Central Administration web client interface will be available at: <HostName_or_IP>:<Server_Port>
Working Data Directory - By default when no value is supplied, files will be stored in the directory: emsca_data, within the current Silver Fabric Engine working directory. The directory set here will be on the ".../bin" folder, which is the default location for emsca_data.
Concurrent Tasks - Specifies the maximum number of deployment executions that the Central Administration Server can perform at any given time. If you will install your Central Administrator Server with only minimal hardware specifications you may want to reduce the maximum number of concurrent tasks, but if you have great hardware with many EMS instances to support this number can be increased for faster concurrent configuration deployments.
Max Deployments to Keep - numerical box to specify the maximum number of deployments to keep. If the number of deployments exceeds this number, the older deployments are removed. Default is -1, which is keep all.
SSL Identity (optional) - Upload a certificate file with a private key providing the Identity of the Central Administration Server to EMS servers.
SSL Password (required if Identity is specified) - Specify the SSL password associated with the private key or store set using this encrypted text field.
SSL Policy - Set the policy for connecting the Central Administration Server with EMS servers to one of three options:
REQUIRED - The Central Administration Server only communicates with an EMS server using SSL listens. Any other type is ignored.
PREFERRED - The Central Administration Server first attempts to communicate with EMS servers using SSL, then tries using non-SSL.
ANY (default) - The Central Administration Server attempts to connect via any means defined in the configuration.
For most common implementations you can click Finish and this TIBCO EMS Central Administration Server Component will be completely functional and ready for management of TIBCO EMS instances once you Publish Component and Run in Ad Hoc Stack.
7.
The Component Wizard page that allows addition, edit, or removal of Runtime Context Variables enables direct configuration of more than forty context variables. It is beyond the scope of this Enabler document to describe all the TIBCO Enterprise Message Service configuration variables directly exposed here, but refer to TIBCO Enterprise Message Service documentation for information on the variables and for the mechanics of adding String, Environment, System, or Encrypted variables refer to the TIBCO Silver Fabric documentation.
8.
All the other Component screens are generic for TIBCO Silver Fabric Enablers use the Help button to display contextual help. Refer to TIBCO Silver Fabric User’s Guide for additional information on these configurations. The configurations for these is optional for the TIBCO EMS Component.
9.
After you click the Finish button, the Component is created.
10.
Click the Component Actions menu icon and select Publish Component and then do it again and select Run in Ad Hoc Stack.
The TIBCO EMS Central Administration Server will be published and running automatically on an available Silver Fabric Engine. After a minute you can use a browser to open the Central Administration web client interface by going to: <HostName_or_IP>:<Server_Port>
To use the Central Administration you will have to enter a name and the URL (HostName_or_IP) for each of your TIBCO EMS servers running with JSON configurations to manage and monitor your TIBCO EMS instances using TIBCO Enterprise Message Service Central Administration.

Copyright © 1999-2015 TIBCO Software Inc. All Rights Reserved
Copyright © 1999-2015 TIBCO Software Inc. All Rights Reserved