• Administrator and TIBCO Business Studio wizards and CLI property files
• Components that use dynamic wiring
• Resource templates
IPv6 Address Representation
IPv6 address representation is described in the IPv6 Addressing Architecture and Format for Literal IPv6 Addressing in URLs specifications, and summarized in Table 7: IPv6 Address Representation on page 47.
Table 7: IPv6 Address Representation Representation Address Type
Eight fields of four hexadecimal digits, where each field is separated by a colon.
If the field is non-zero there must be at least one digit. For example, All
2001:db8:1234:ffff:4354:45ab:3455:ab45. You can apply the following shortening procedures:
• Omit leading zeros in a field. For example, :00db: can be represented as :db:.
• Replace one or more consecutive fields of zeros and separators (:0:0:0:0:) with a single empty field (::). For example, 2001:db8:0:0:0:0:3455:ab45 can be represented as 2001:db8::3455:ab45.
0:0:0:0:0:0:0:1 or ::1.
Localhost or loopback
0:0:0:0:0:0:0:0 or ::. This address is equivalent to the unspecified IPv4 address 0.0.0.0.
Unspecified
Enclose the address in square brackets ([]). For example, the URL of an Administrator server running on a machine at the address
Embedded in a URL
FEDC:BA98:7654:3210:FEDC:BA98:7654:3210 is
http://[FEDC:BA98:7654:3210:FEDC:BA98:7654:3210]:8120/amxadministrator.
IP Address Use and Resolution
The default configuration of the Administrator server network adapter is the unspecified IP address (0.0.0.0), which means that it listens on IPv4 and IPv6 addresses. When clients access the Administrator server by machine name, the name lookup resolves to both addresses. By default, Administrator clients use the IPv4 address. To override this behavior and use the IPv6 address, set the value of the JVM system property
java.net.preferIPv6Addresses to true. For further information, see Networking IPv6 User's Guide for JDK/JRE 5.0 . The Nodes chapter in Administration explains how to set a JVM property for a node.
TIBCO Configuration Tool Requirements
You can run TIBCO Configuration Tool right after installation or at a later time. To run the tool successfully, you must first make sure your system meets the requirements.
Each product installation has a set of requirements. TIBCO Configuration Tool has additional requirements.
• You must have access to a running instance of TIBCO Enterprise Message Service Server. See Enterprise Messaging Server Requirements on page 48.
TIBCO ActiveMatrix Service Grid Installation and Configuration Configuration | 47
• If you do not have administrator privileges for the Enterprise Message Service server, you must set you Enterprise Message Service for a non-administrator user. See Configuring TIBCO Enterprise Message Service Servers for Non-Admin Users on page 48.
• If you want to secure communication with SSL, you must perform additional setup. See Secure
Communication Channels on page 40 for background and setup information and SSL Requirements on page 48 for specific requirements.
See the readme file for additional requirements.
Enterprise Messaging Server Requirements
To run successfully, TIBCO Configuration Tool must have access to a TIBCO Enterprise Message Service that meets certain requirements.
A TIBCO Enterprise Message Service server acts as a notification server for the ActiveMatrix Administrator servers and TIBCO Host instances within an enterprise. The enterprise is defined by the enterprise name and the TIBCO Enterprise Message Service server that you specify when you run one of the configuration wizards.
Ensure that the following requirements and prerequisites are satisfied:
• Each enterprise must use a different TIBCO Enterprise Message Service server.
• The TIBCO Enterprise Message Service server must be running before you run the Create TIBCO ActiveMatrix Administrator Server and Create TIBCO Host Instance wizards or create these components in console mode or silent mode.
• If you manually start the TIBCO Enterprise Message Service server, make sure you use the same configuration files as the Windows service. Use the following command
TIBCO_HOME/ems/version number/bin/tibemsd -config EMS_CONFIG_HOME/tibco/cfgmgmt/ems/data/tibemsd.conf
where EMS_CONFIG_HOME is the configuration folder for TIBCO Enterprise Message Service.
• The clocks of machines within the same enterprise must be synchronized to within to 30 minutes. You can run an NTP synchronization daemon on each machine to achieve synchronization.
• If you do not have administrator privileges for TIBCO Enterprise Message Service, you can request privileges or configure the service for a non-admin user from the TIBCO Enterprise Message Service server console. See Configuring TIBCO Enterprise Message Service Servers for Non-Admin Users on page 48.
SSL Requirements
By default, ActiveMatrix runs with SSL disabled. You can enable SSL for individual connections or for all connections in your environment.
See Secure Communication Channels on page 40 for information on setting up SSL. If you intend to enable SSL, ensure the following prerequisites are satisfied.
• TIBCO Enterprise Message Service Server - The TIBCO Enterprise Message Service server must be enabled with SSL and configured with a certificate file that contains both the server and issuer certificates before you run the Create TIBCO Administrator Server and Create TIBCO Host Instance wizards or before you create these components in console mode or silent mode.
• Database and LDAP Servers - Database and LDAP servers must be enabled with SSL before you run the Create TIBCO Administrator Server wizard or before you create these components in console mode or silent mode.
See Secure Communication Channels on page 40.
Configuring TIBCO Enterprise Message Service Servers for Non-Admin Users
Configuration of TIBCO ActiveMatrix runtime objects and services is easiest if you have administrative privileges on the TIBCO Enterprise Message Service server you want to use. If you do not have administrative privileges, you can set up the TIBCO Enterprise Message Service server to allow configuration for non-admin users.
TIBCO ActiveMatrix Service Grid Installation and Configuration 48 | Configuration
About this task
If you want to configure TIBCO ActiveMatrix runtime objects and services, and you do not have administrator privileges on the TIBCO Enterprise Message Service server you want to use, you can configure the TIBCO Enterprise Message Service server to allow configuration for non-admin users. The following steps presents the most restrictive permissions necessary.
Procedure
1. In the Enterprise Message Service server console, set permissions for the Administrator server users. In the following commands, replace username and password with the username and password values appropriate for each bus.
– Messaging Bus
delete queue >
delete topic >
create user username "Description of the user" password=password create queue AMX_SV.>
grant queue AMX_SV.> user=username create, delete, modify, send, receive
– Notification Bus
delete queue >
delete topic >
create user username "Description of the user" password=password create topic EMSGMS.>
grant topic EMSGMS.> user=username create, modify, subscribe, publish grant topic $sys.monitor.connection.* user=username subscribe
grant admin user=username view-connection,view-server create topic AMX_MGMT.>
grant topic AMX_MGMT.> user=username create, modify, subscribe, publish
– Management Bus
delete queue >
delete topic >
create user username "Description of the user" password=password create queue com.tibco.amf.admin.deploymentServerQueue.>
grant queue com.tibco.amf.admin.deploymentServerQueue.> user=username create, delete, send, receive
– Logging and Payload Buses
delete queue >
delete topic >
create user username "Description of the user" password=password create queue cl_logservice_queue.physical
create queue cl_payload_queue.physical
grant queue cl_logservice_queue.physical user=username send, receive grant queue cl_payload_queue.physical user=username send, receive
create jndiname cl_logservice_queue queue cl_logservice_queue.physical create jndiname cl_payload_queue queue cl_payload_queue.physical
– Monitoring Bus
delete queue >
delete topic >
create user username "Description of the user" password=password create queue amx.governance.stats
grant queue amx.governance.stats user=username send, receive create queue amx.governance.internal.stats
grant queue amx.governance.internal.stats user=username send, receive
2. If you intend to manually separate notification, management, and messaging buses, group their constraints first.
The Notification, Management, and Messaging buses are initially grouped together as are the Monitoring, Logging, and Payload buses.
– Messaging, Notification, and Management Buses
delete queue >
delete topic >
create user username "Description of the user" password=password
TIBCO ActiveMatrix Service Grid Installation and Configuration Configuration | 49
create queue AMX_SV.>
grant queue AMX_SV.> user=username create, delete, modify, send, receive create topic EMSGMS.>
grant topic EMSGMS.> user=username create, modify, subscribe, publish grant topic $sys.monitor.connection.* user=username subscribe
create queue com.tibco.amf.admin.deploymentServerQueue.>
grant admin user=username view-connection,view-server
grant queue com.tibco.amf.admin.deploymentServerQueue.> user=username create, delete, send, receive
– Monitoring, Logging, and Payload Buses
delete queue >
delete topic >
create user username "Description of the user" password=password create queue cl_logservice_queue.physical
create queue cl_payload_queue.physical create queue amx.governance.stats
create queue amx.governance.internal.stats
grant queue cl_logservice_queue.physical user=username send, receive grant queue cl_payload_queue.physical user=username send, receive grant queue amx.governance.stats user=username send, receive
grant queue amx.governance.internal.stats user=username send, receive create jndiname cl_logservice_queue queue cl_logservice_queue.physical create jndiname cl_payload_queue queue cl_payload_queue.physical
3. Configure and create the Administrator server and TIBCO Host instances as described in Create TIBCO ActiveMatrix Administrator Server on page 62 and Create TIBCO Host Instance on page 80.