When you run TIBCO Configuration Tool in GUI mode or in console mode, you are prompted for information about the component or components you selected for configuration.
When you select Create Express Developer Environment, a wizard prompts you for information about the Administrator server and information about the
Enterprise Message Service to be used. When you complete the wizard, it creates an
Administrator server, a host named SystemHost, and a node named SystemNode. At runtime, these components communicate using the
Enterprise Message Service server you specify. The following table summarizes the information you need when running the wizard.
|
|
|
|
Administers TIBCO ActiveMatrix applications and infrastructure.
|
|
|
|
|
The Administrator Server Notification and Messaging Bus Server screen prompts you for the connection information for one or more
TIBCO Enterprise Message Service server instances. The Notification and Messaging Bus servers in your express developer environment are then associated with that server.
You must have access to a running instance of TIBCO Enterprise Message Service Server before you can complete this screen. See
TIBCO Configuration Tool Requirements. If you intend to enable SSL communications, see
Secure Communication Channels.
|
|
|
Default: machinename: port, where machinename is the machine on which TIBCO Configuration Tool is being executed and port is 7222.
|
|
|
|
|
Each TIBCO Configuration Tool wizard's summary screen allows you to check the configuration that you specified and see the effects of that configuration. You can click
Back to make changes, save the configuration for use by the silent installer, or click
Configure to start the configuration. If you are using the console configuration tool, you can perform the same actions by typing single-letter commands.
|
|
|
|
|
If an Administrator server was configured in the wizard, a link to the URL of the Administrator server.
|
|
|
|
|
|
|
|
|
|
|
Create TIBCO ActiveMatrix Administrator Server
The Create TIBCO ActiveMatrix Administrator Server wizard allows you to configure many aspects of your server including the database, authentication method, monitoring, log service, and more. You can review this wizard documentation before you start configuration to decide how you want to set up the server.
When you run the wizard, you specify a database for ActiveMatrix Administrator server and for several system services. If you are using an external database (and do not use HSQLDB as an external database), set up the external database before you run the wizard.
ActiveMatrix 3.2 supports a DDL generator utility that you use before you run TIBCO Configuration Tool. When you use DDL scripts produced by the DDL generator, you need different database permissions than if you do not use DDL scripts. The database user must have connect and resource privileges, and cannot have DBA privileges. The database user must be assigned to the default schema.
The following table summarizes the components that are configured in the Create TIBCO ActiveMatrix Administrator Server wizard, their function, and the decisions you must make, the information you must gather, and actions you must perform before running the wizard.
|
|
|
|
Administers TIBCO ActiveMatrix applications and infrastructure.
|
|
|
The TIBCO Host instance that manages the SystemNode node on which the Administrator server runs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Choose the ActiveMatrix Administrator notification server and database or another notification server and database. If the latter, provide the notification server and database configuration details according to Database Requirements.
|
|
|
Choose the ActiveMatrix Administrator database or another database. If you are using a database different than the one the ActiveMatrix Administrator server uses, see Database Requirements.
|
|
|
|
The Administrator Server screen allows you to specify the enterprise name and the name of the
Administrator Server instance.
Each Administrator server runs on a
TIBCO Host instance. You can specify the instance on which the server will run, configure server characteristics such as a Windows shortcut, and specify the environment and the node.
|
|
|
Name of the machine on which the TIBCO Host instance runs. The value of this property must either be a hostname resolvable through DNS or 0.0.0.0; it cannot be an IP address.
Default: machineName, where machineName is the machine on which TIBCO Configuration Tool is being executed.
|
|
|
|
Check to register the TIBCO Host instance as a Windows service named TIBCO ActiveMatrix Admin- enterpriseName- serverName with startup type Automatic. The service is not started.
|
|
Check to add a shortcut named TIBCO ActiveMatrix Admin- enterpriseName- serverName that points to CONFIG_HOME\tibcohost\Admin-enterpriseName- serverName\host\bin\tibcohost.exe to the Windows desktop.
|
|
|
|
|
|
|
|
|
The Administrator Server Connection Settings screen allows you to specify non-default adapters and ports and to enable and configure SSL for the external HTTP port. You can also choose to enable an HTTP load balancer.
|
|
|
Address of the network adapter on the machine on which the Administrator server runs. The default is set to 0.0.0.0 so that Administrator will listen on all network adapters (including http://localhost and http://hostname). If you leave the default, clients can connect to the Administrator server using any of the conventions (localhost, IP address, hostname). The value of this property must either be a hostname resolvable through DNS or 0.0.0.0; it cannot be an IP address.
|
|
|
|
Port on which Administrator clients access the Administrator server.
|
|
|
|
|
|
IIndicate that Administrator server will identify itself to clients with a self-signed certificate When selected it uses the self signed certificate from the samples folder.
|
|
Indicate that Administrator server will identify itself to clients with a certificate imported into Administrator server. When selected, the Keystore fields and Fetch Keystore button are enabled.
|
|
|
|
|
|
|
|
|
|
|
|
Default: machinename: port, where machinename is the machine on which TIBCO Configuration Tool is being executed and port is 7222.
|
|
|
|
|
TIBCO Enterprise Message Service Server is SSL Enabled
|
Configure the Administrator server create SSL connections to an TIBCO Enterprise Message Service server that is enabled for SSL.
|
You can choose to use Administrator server with a default in-process database during development. In production systems, use an external database instead. This screen allows you to configure database details.
The properties that the wizard sets in the build.properties file depend on the context in which the prompts are displayed. By default, you specify the properties for the
Administrator Server database and the information is then used for the Notification Service database, the Log Service database, and the Payload Service database. You can, however, overwrite the values for the Notification Service, Log Service, and Payload Service, and you can change them in the
build.properties file.
Administrator stores information about users and groups in an authentication realm. You can choose to let
Administrator store the information in a database or in LDAP.
TIBCO Configuration Tool will then prompt you for more information about the authentication realm.
|
|
Use ActiveMatrix Administrator Server Database
|
|
The properties that the wizard sets in the build.properties file depend on the context in which the prompts are displayed. By default, you specify the properties for the
Administrator Server database and the information is then used for the Notification Service database, the Log Service database, and the Payload Service database. You can, however, overwrite the values for the Notification Service, Log Service, and Payload Service, and you can change them in the
build.properties file.
If you select an LDAP authentication realm, Administrator stores information about users and groups in LDAP. You are prompted for the user and password, name resolution context, and server URLs. You can also specify the user search configuration and optional group information.
|
|
|
|
|
|
|
Default: com.sun.jndi.ldap.LdapCtxFactory
|
|
Default: machinename:389, where machinename is the machine on which TIBCO Configuration Tool is being executed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
•
|
Group has users - List of users that belong to the group. When selected, the Group Attribute with User Names field is enabled.
|
•
|
User has groups - List of groups to which the user belongs. When selected, the User Attribute with Group Names field is enabled.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Address of the network adapter on the machine on which TIBCO Credential Server runs. The default is set to 0.0.0.0 so that TIBCO Credential Server will listen on all network adapters (including http://localhost and http://hostname). With the default setting, clients can connect to TIBCO Credential Server using any of the conventions (localhost, IP address, hostname). The value of this property must either be a hostname resolvable through DNS or 0.0.0.0; it cannot be an IP address.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Default: TIBCO_HOME/tibcohost/1.2/templates/admin.default.ssl.trust.store.ts.
|
|
|
|
|
|
|
|
|
The monitoring service is an ActiveMatrix application that aggregates performance data from runtime object, that is,
TIBCO Host instances and nodes.
TIBCO Configuration Tool deploys the monitoring service application on the SystemNode node, which is the node that runs the
Administrator server.
Use ActiveMatrix Administrator Notification Server
|
|
|
|
|
Default: machinename: port, where machinename is the machine on which TIBCO Configuration Tool is being executed and port is 7222.
|
|
|
|
|
TIBCO Enterprise Message Service Server is SSL Enabled
|
Configure the Administrator server create SSL connections to an TIBCO Enterprise Message Service server that is enabled for SSL.
|
The monitoring service is an ActiveMatrix application that aggregates performance data from runtime objects. The monitoring service application is deployed on SystemNode, the node that runs the
Administrator server.
|
|
Use ActiveMatrix Administrator Server Database
|
|
The properties that the wizard sets in the build.properties file depend on the context in which the prompts are displayed. By default, you specify the properties for the
Administrator Server database and the information is then used for the Notification Service database, the Log Service database, and the Payload Service database. You can, however, overwrite the values for the Notification Service, Log Service, and Payload Service, and you can change them in the
build.properties file.
A log service is a TIBCO ActiveMatrix application that offers logging services. The log service application is deployed in the environment SystemEnvironment on SystemNode, the node that runs the
Administrator server. A log service receives log entries sent to a JMS destination and stores the entries in a database.
|
|
Use ActiveMatrix Administrator Server Database
|
|
The properties that the wizard sets in the build.properties file depend on the context in which the prompts are displayed. By default, you specify the properties for the
Administrator Server database and the information is then used for the Notification Service database, the Log Service database, and the Payload Service database. You can, however, overwrite the values for the Notification Service, Log Service, and Payload Service, and you can change them in the
build.properties file.
|
|
Use ActiveMatrix Administrator Server Database
|
|
The properties that the wizard sets in the build.properties file depend on the context in which the prompts are displayed. By default, you specify the properties for the
Administrator Server database and the information is then used for the Notification Service database, the Log Service database, and the Payload Service database. You can, however, overwrite the values for the Notification Service, Log Service, and Payload Service, and you can change them in the
build.properties file.
Each TIBCO Configuration Tool wizard's summary screen allows you to check the configuration that you specified and see the effects of that configuration. You can click
Back to make changes, save the configuration for use by the silent installer, or click
Configure to start the configuration. If you are using the console configuration tool, you can perform the same actions by typing single-letter commands, as prompted.
|
|
|
|
|
If an Administrator server was configured in the wizard, a link to the URL of the Administrator server.
|
|
|
|
|
|
|
|
|
|
|
A TIBCO Host instance is one of the central components of any product in the
TIBCO ActiveMatrix family of products. You can create an instance explicitly and give custom information about the instance, associated notification server, and associated
Administrator server.
When you create a TIBCO Host instance, you are first prompted for the basic information that includes the name, enterprise and machine name, and behavior as a Windows application.
|
|
|
Name of the TIBCO Host instance. The name must be unique within the enterprise.
|
|
|
|
Default: hostname, where hostname is the machine on which TIBCO Configuration Tool is being executed.
|
|
|
|
Check to register the TIBCO Host instance as a Windows service named TIBCO ActiveMatrix instanceName, where instanceName is the name you specified in the Name field, with startup type Automatic. The service is not started.
|
|
Check to create a shortcut named instanceName on the Windows desktop that points to CONFIG_HOME\tibcohost\instanceName\host\bin\tibcohost.exe and launches the TIBCO Host instance.
|
TIBCO Host Instance Notification Server
When you create a standalone TIBCO Host instance, you can specify an associated notification server. This notification server can be the same server as that used by the
Administrator, or you can define a different notification server.
|
|
|
Default: machinename: port, where machinename is the machine on which TIBCO Configuration Tool is being executed and port is 7222.
|
|
|
|
|
TIBCO Enterprise Message Service Server is SSL Enabled
|
Configure the Administrator server create SSL connections to an TIBCO Enterprise Message Service server that is enabled for SSL.
|
TIBCO Host Instance
Administrator Server
When you create a TIBCO Host instance, you can immediately bind it to an
Administrator server and specify connection information for that server, or choose not to bind the
TIBCO Host instance to an
Administrator server. You can enable the connection for SSL.
|
|
|
Check to bind the TIBCO Host instance to an Administrator server. When checked, the Administrator server configuration fields are enabled.
|
|
Name of the machine on which the Administrator server is running. The value of this property must either be a hostname resolvable through DNS or 0.0.0.0; it cannot be an IP address.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If an Administrator server was configured in the wizard, a link to the URL of the Administrator server.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
−
|
TIBCO enabled JDBC driver for Microsoft SQL Server 3.0
|
−
|
TIBCO enabled JDBC driver for Microsoft SQL Server 2.0.0
|
−
|
TIBCO enabled JDBC driver for Oracle 10.2.0
|
−
|
TIBCO enabled JDBC driver for Oracle 11.1.0
|
−
|
TIBCO enabled JDBC driver for IBM DB2 2.3.63 Not supported for ActiveMatrix Administrator and ActiveMatrix JDBC resource templates.
|
−
|
TIBCO enabled JDBC driver for IBM DB2 4.12.55
|
−
|
TIBCO enabled JMS client for Sonic 6.1.0
|
−
|
TIBCO enabled JMS client for WebSphere 7.0.0. Support for WebSphere MQ 6.0 is based on the backward compatibility of the WebSphere MQ 7.0 client library. When a JMS binding is configured with JMS topics and needs to work with WebSphere MQ 6.0, you must provide the 7.0.1.3 version of the client library.
|
|
|
|
|
|
|
If an Administrator server was configured in the wizard, a link to the URL of the Administrator server.
|
|
|
|
|
|
|
|
|
|
|
In TIBCO ActiveMatrix 3.2, you can replicate an Administrator server on a second machine by running TIBCO Configuration Tool. Before you can run the TIBCO Configuration Tool wizard that performs replication, you must set up the source environment and the destination requirement.
Machine 1 - Set up the first Administrator server on machine 1 by using the Create TIBCO ActiveMatrix Administrator Server wizard.
a.
|
Copy the folder CONFIG_HOME/admin/enterprise_name/shared to a location accessible from Machine 2.
|
b.
|
To let the Administrator server on Machine 1 know about the new location of the shared folder, Open a command prompt at TIBCO_Home\administrator\3.2\scripts.
|
Machine 2 - Replicate the Administrator server on Machine 2.
b.
|
When you click Next, Machine 2 settings are validated. As part of validation, the wizard checks that.
|
When you log in to one of the Administrator servers (or access the load balancing URL), you see the following system setup:
|
|
|
|
|
|
|
Check to register the TIBCO Host instance as a Windows service named TIBCO ActiveMatrix Admin- enterpriseName- serverName with startup type Automatic. The service is not started.
|
|
Check to add a shortcut named TIBCO ActiveMatrix Admin- enterpriseName- serverName that points to CONFIG_HOME\tibcohost\Admin-enterpriseName- serverName\host\bin\tibcohost.exe to the Windows desktop.
|
|
|
|
Address of the network adapter on the machine on which the Administrator server runs. The default is set to 0.0.0.0 so that Administrator will listen on all network adapters (including http://localhost and http://hostname). If you leave the default, clients can connect to the Administrator server using any of the conventions (localhost, IP address, hostname). The value of this property must either be a hostname resolvable through DNS or 0.0.0.0; it cannot be an IP address.
|
|
|
|
Port on which Administrator clients access the Administrator server.
|
|
|
|
|
|
Indicate that Administrator server will identify itself to clients with a certificate imported into Administrator server. When selected, the Keystore fields and Fetch Keystore button are enabled.
|
|
|
|
|
|
|
|
|
Click Test Connection to make sure that they can connect to EMS from the replica administrator machine.
Click to make sure you can connect to the database from the replica machine.
Click the Test Connection button to make sure the connection between LDAP server and the replica server works properly.
Each TIBCO Configuration Tool wizard's summary screen allows you to check the configuration that you specified and see the effects of that configuration. You can click
Back to make changes, save the configuration for use by the silent installer, or click
Configure to start the configuration. If you are using the console configuration tool, you can perform the same actions by typing single-letter commands, as prompted.
Make sure that the super user specified in the remote_props.properties has
force_delete permission. Only users with explicit
force_delete and super user permission are allowed to delete the Administrator server instance.
3.
|
Edit the deleteAdminInstance_data.xml file to update the node and host name properties.
|
Edit ActiveMatrix Administrator Server Configuration
2.
|
Select a CONFIG_HOME location for the Administrator server that you wish to change.
|
3.
|
Click Edit TIBCO ActiveMatrix Administrator Server Configuration - V3.2
|
|
|
|
Select an Administrator server configuration from the drop-down list.
|
Edit Administrator Server Configuration
|
|
|
Address of the network adapter on the machine on which the Administrator server runs. The default is set to 0.0.0.0 so that Administrator will listen on all network adapters (including http://localhost and http://hostname). If you leave the default, clients can connect to the Administrator server using any of the conventions (localhost, IP address, hostname). The value of this property must either be a hostname resolvable through DNS or 0.0.0.0; it cannot be an IP address.
|
|
Port on which Administrator clients access the Administrator server.
|
|
|
|
Indicate that Administrator server will identify itself to clients with a self-signed certificate. When selected it uses the self signed certificate from the samples folder.
|
|
Indicate that Administrator server will identify itself to clients with a certificate imported into Administrator server. When selected, the Keystore fields and Fetch Keystore button are enabled.
|
|
|
|
|
|
|
|
|
Edit Administrator Server Database Details
The Edit Administrator Server Database Details screens allow you to change the database details for your server. Using the wizard requires that you prepare your environment and that you perform some post-processing steps.
Edit Administrator Server Authentication Realm
Administrator stores information about users and groups in an authentication realm. When you edit the Authentication realm, you can change the settings of the current realm, switch from a database to LDAP, or switch from LDAP to a database.
TIBCO Configuration Tool will then prompt you for more information about the authentication realm.
For this case, use the tibco_user superuser to log in to TIBCO Administrator after you have changed to a database realm and change the password. Consider creating a new superuser and deleting the default
tibco_user user.
Each TIBCO Configuration Tool wizard's summary screen allows you to check the configuration that you specified and see the effects of that configuration. You can click
Back to make changes, save the configuration for use by the silent installer, or click
Configure to start the configuration. If you are using the console configuration tool, you can perform the same actions by typing single-letter commands, as prompted.