![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
After you complete these tasks, the TIBCO Administrator component should be published. At runtime, you can access the TIBCO Administrator GUI, an HTTP redirector (refer to Virtual Router for TIBCO Administrator), with the following URL:This automatically redirects to the machine where TIBCO Administrator is running with the port calculated using the base port set in Task G, Set the HTTP Base Ports.
1. In the TIBCO Silver Fabric Administration Tool, select Stacks > Components.
2. In the components page, select Create New TIBCO Administrator Component in the Global Actions drop-down list as shown in Figure 1.Figure 2 Configuring General PropertiesSelect a version of each of the installed distributions. It is generally a good practice to use the latest version of a product distribution. Refer to the TIBCO Silver® Fabric Enabler for TIBCO Administrator™ - Enterprise Edition Readme for more information on supported distributions. All product versions which are displayed are compatible with the component being defined.If you don’t see the latest release versions of all the Distributions shown below you should gather these dependencies from https://edelivery.tibco.com and refer to the Installation guide for more specific information.
Figure 4 Choosing Optional Distribution
7. Click the Next button after selecting the TIBCO product distribution versions and the TIBCO Administrator: <ComponentName> - Basic Configuration panel is displayed as is shown in Task B, Set Basic Configurations.Task B Set Basic Configurations
Once published TIBCO Administrator can be accessible via Virtual Router at: http://<BrokerName_IP>:<Port>/<DomainName>The default value is admin. It is strongly recommended that you change it.
Choose either Disabled, UI, or XML. UI and XML settings enable LDAP configuration with settings made with either a graphical user interface or an uploaded XML settings file.For more information on transport settings, refer to one of the following sections, Configure Default Transport - TIBCO Rendezvous or Configure TIBCO EMS as Transport (Optional).
If TIBCO EMS is used for the transport messaging, a database is required to store domain information. Check the box to Store Domain Information in a Database if TIBCO EMS is to be used.When you check this checkbox and publish a dependent TIBCO Silver Fabric Enabler for TIBCO EMS server component, the connection and configuration settings are set automatically and the TIBCO EMS Connection Configuration page is not displayed.Select the checkbox to Use Dependent EMS Server if TIBCO EMS is to be used as a dependent component. When this setting is used, you must also make the TIBCO Silver Fabric Enabler for TIBCO EMS component a dependency of the TIBCO Administrator component in the stack setting.
FT mode requires that allocated TIBCO Administrators use the same shared drive available to all Engines. FT mode is not fully compatible with Windows operating systems because Windows services don’t have access to shared drives. It is strongly recommended that implementations requiring FT mode target operating systems other than Windows based resources. This can be accomplished by defining a Resource Preference - Allocation Rule to specify the OS Platform as equal to a preferred operating system. If Windows platforms must be used then the Silver Fabric Engines can be run as stacks by the desktop user so that the Silver Fabric Engine and child processes can use mapped drives.Use the Next button to proceed with your component configuration. Changes are saved when you click the Finish button.TIBCO Rendezvous (RV) is the default transport . That is, in the Task B, Set Basic Configurations if the Use EMS as transport option remains unchecked, RV is used for transport.The default value is tcp:7500This specifies TIBCO Rendezvous Daemon used for communication with TIBCO Hawk. The default value is tcp:7474Like the RV Daemon, if you need to use a remote daemon, you can set the value to tcp:ADMINMACHINE:port_number, for example, tcp:ADMINMACHINE:7474.This specifies the TIBCO Rendezvous network used for communication with TIBCO Hawk. Use the default value unless you are an experienced TIBCO Rendezvous user. See TIBCO Hawk Installation and Configuration for details about this parameter.This specifies the TIBCO Rendezvous service used for communication with TIBCO Hawk. Use the default unless you are an experienced TIBCO Rendezvous user. The default value is 7474. See TIBCO Hawk Installation and Configuration for details about this parameter.
tcp:ADMINMACHINE:port_numberThe placeholder value, ADMINMACHINE, will be automatically replaced during runtime by the value of the machine name or IP address where TIBCO Administrator is running.For example when you set the value to tcp:ADMINMACHINE:7500, it starts TIBCO Rendezvous on the TIBCO Administrator machine. All machines that join this TIBCO Domain use this remote daemon.Figure 7 TIBCO Hawk AMI ConfigurationAMI Hawk Service - specifies the TIBCO Hawk port number, for example, TIBCO Rendezvous connects with TIBCO Hawk on the default port 7475. AMI Hawk Service and AMI Hawk Daemon must be set with valid values together. Setting only one of them results in an error.AMI Hawk Daemon - specifies the location of the TIBCO Hawk Daemon. A value of "tcp:yyyy" would correspond to a local Hawk Daemon where "yyyy" would be the port number. A Hawk Daemon located elsewhere would be specified by a value of the protocol, IP address, and port number: "tcp:xxx.xxx.xxx.xxx:yyyy".
The actual AMI Hawk Service port for the runtime component instance is incremented by an integer according to the engine instance ID. For example, if the user sets the AMI Hawk Service to 6464 and the component is instantiated to run on engine instance 1, then the service is reported in the hawkagent.cfg file as 6465. Then when the component is scaled up to other engine instances, the AMI Hawk Service value is incremented higher by the Enabler automatically.If your TIBCO Administrator component is configured to use independent EMS as a transport in Task B, Set Basic Configurations, then only the Configure TIBCO EMS Connection Configuration page is displayed. Here you add the URL, port, and login profile.
The URL of the TIBCO Enterprise Message Service server is in the following format: tcp://hostname:portMultiple Enterprise Message Service servers may be configured for use by the Administrator component for fault-tolerance by specifying all of them here. Enter multiple EMS Server URL by separating them with a comma between entries. For example:
− Oracle Thin: oracle.jdbc.driver.OracleDriver
− MSSQL Server: com.microsoft.sqlserver.jdbc.SQLServerDriver
− Oracle 11 driver: ojdbc6.jar
− Oracle 10 driver: ojdbc14.jar
− MS SQL driver: sqljdbc4.jarUse the Upload button in the "Upload a JDBC driver..." field below for this.Specify a JDBC driver to publish with the TIBCO Administrator™ Distribution for TIBCO Silver® Fabric so that it can communicate with a runtime TIBCO Administrator Domain database. When the TIBCO Administrator uses a database as the domain storage, you must upload a JDBC driver so the component can interact with it.Task G Set the HTTP Base PortsIn order to avoid HTTP port conflicts for TIBCO Administrator when more than one TIBCO Administrator servers are running on the same machine, TIBCO Silver® Fabric Enabler for TIBCO Administrator™ - Enterprise Edition automatically sets the port to the following value:HTTP Base Port + EngineInstanceValueThe EngineInstanceValue is the Engine number of where TIBCO Administrator runs.For example, on a dual core machine, the default number of Engines is 2 (one per core). The first Engine has the number 0, the second one has the number 1.As an example if you set the HTTP Base Port to 8483, the HTTP ports used by TIBCO Administrator would be 8483 and 8484 for the first and second engines respectively.Figure 10 HTTP Base Port settingsIn order to avoid shutdown port conflicts for TIBCO Administrator when many TIBCO Administrator servers stop working on the same machine, TIBCO Silver® Fabric Enabler for TIBCO Administrator™ - Enterprise Edition automatically sets the shutdown port to the following value:HTTP Shutdown Base Port + EngineInstanceValueThe value is calculated in the same way as the TIBCO Administrator HTTP Base Port described previously.Figure 12 Add Third Party JAR FilesString, Environment, System, or Encrypted variables may be added to the component to define and set runtime specific context variables.Select a variable type from the Add Variable pull-down list or Add from Enabler to use a variable from a selected Enabler.Figure 13 Adding a Runtime Context VariableOnce you have added any runtime context variable you may select the variable (selected row is highlighted) and Edit to change its attributes. Selected rows may also be removed.Variable values from the Enabler may be added to the runtime as well. Use the Add from Enabler button to add Enabler-specific context variables.Task K Configure HTTPSThis setting helps the system avoid HTTPS port conflicts for the TIBCO Administrator when more than one TIBCO Administrator servers are running on the same machine. TIBCO Silver® Fabric Enabler for TIBCO Administrator™ - Enterprise Edition sets the port to the following value:HTTPS Base Port(value) + EngineInstanceValueThe EngineInstanceValue is the Engine number where TIBCO Administrator runs.For example, on a dual core machine, the default number of Engines is 2 (one per core). The first Engine has the number 0, the second one has the number 1.If for example you set the HTTPS Base Port to 8483, the HTTPS ports used by TIBCO Administrator would be 8483 and 8484 for the first and second engines respectively.To avoid shutdown port conflicts for TIBCO Administrator, TIBCO Silver® Fabric Enabler for TIBCO Administrator™ - Enterprise Edition automatically sets the shutdown port to the following value:HTTPS Shutdown Base Port + EngineInstanceValueEnter your Email Address, Common Name (CN), Organizational Unit (OU), Organization (O), City/Locality, State (required), Country Code (two letters), and Validity. These values are required.This configuration page appears only when the HTTPS Enabled field on the Basic Configuration page is set to CA_Signed_Certificate.This setting helps the system avoid HTTPS port conflicts for the TIBCO Administrator when more than one TIBCO Administrator servers are running on the same machine. TIBCO Silver® Fabric Enabler for TIBCO Administrator™ - Enterprise Editionsets the port to the following value:HTTPS Base Port(value) + EngineInstanceValueThe EngineInstanceValue is the Engine number where TIBCO Administrator runs.For example, on a dual core machine, the default number of Engines is 2 (one per core). The first Engine has the number 0, the second one has the number 1.For example if you set the HTTPS Base Port to 8483, the HTTPS ports used by TIBCO Administrator would be 8483 and 8484 for the first and second engines respectively.To avoid shutdown port conflicts for TIBCO Administrator, TIBCO Silver® Fabric Enabler for TIBCO Administrator™ - Enterprise Edition automatically sets the shutdown port to the following value:HTTPS Shutdown Base Port + EngineInstanceValueUpload the server Certificate returned from the third-party Certificate Authority using the Upload button to browse for the proper file.The CA chain certificate is optional. Use the Upload button to browse for the proper file.
• Because this process uses a pre-existing certificate, you don’t have to go through the step of generating a CSR for each component server, but the certificate must be in PEM (Privacy Enhanced Mail) format and a private key (in the PKCS#8 format) is required. The name of the private key file must be "key.p8". Use the Upload button to browse for the proper file.Task L Configure LDAPYou can choose either Disabled, UI, or XML. The UI and XML settings enable LDAP configuration with settings made with either a graphical user interface or an uploaded XML settings file. An LDAP configuration page is added to the component wizard when UI or XML are selected.When LDAP is enabled with the UI option, the LDAP Configuration Using User Interface page is added to the wizard for setting basic LDAP properties. See the following figure to evaluate whether the LDAP configuration using the UI is adequate for your environment implementation.Figure 16 LDAP Configuration Using UIf your implemented LDAP environment is more complex and requires configuration settings that are not exposed by this UI, then you should use an XML settings file to configure LDAP for the component. If this is the case use the Menu button to go back the TIBCO Administrator Basic Configuration page and set LDAP Enabled to "xml".TIBCO_HOME/tra/version/template/domainutility/cmdline/ ModifyLDAPConfiguration.xmlFigure 17 LDAP Configuration Using XML FileFor more information on "Creating a Domain that integrates with an LDAP Directory Server" refer to the section with that same name in the TIBCO Runtime Agent Domain Utility User’s Guide.To configure LDAP for use with SSL connections refer to the TIBCO Runtime Agent Domain Utility User’s Guide section on "Configuring LDAP Integration With SSL Connections."
String, Environment, System, or Encrypted variables may be added to the component to define and set runtime specific context variables.Select a variable type from the Add Variable pull-down list or Add from Enabler to use a variable from a selected Enabler.Figure 18 Adding a Runtime Context VariableOnce you have added any runtime context variable you may select the variable (selected row is highlighted) and Edit to change its attributes. Selected rows may also be removed.Variable values from the Enabler may be added to the runtime as well. Use the Add from Enabler button to add Enabler-specific context variables.Task N Add Allocation Rule SettingsMore information on using statistics for scaling is available in the TIBCO Silver Fabric Cloud Administration Guide.Refer to TIBCO Silver Fabric User’s Guide for more information on these configuration screens.After you click the Finish button, make sure to publish the component to make it available when creating a stack or to use the configuration changes in existing stacks.From the Actions drop-down list located at the left side of the row for the component you just created, select Publish Component or Publish Changes if you were editing a component that was already published.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |