Configure an ActiveMatrix Administrator server
Start the ActiveMatrix server
Create an ActiveMatrix environment
Create an ActiveMatrix Node
TIBCO EMS 5.0.0
TIBCO Active Matrix Service Grid 2.2.0
Configure Environment and Node
Create an ActiveMatrix Administrator Server
First, you will create an ActiveMatrix server using the wizard. The Administrator server requires a database with a JDBC connection. We will use the lightweight Hibernate database that is shipped with ActiveMatrix.
1. Create ActiveMatrix Administrator instance
Go to Start >Programs >TIBCO >ActiveMatrix 2.1 >Start HSQLDB Server
Open the Services window (Control Panel > Administrative Tools > Services)
__Start EMS: Confirm EMS Server service is running
__Start TIBCO Management Daemon 2.0 Service
__Start the Administrator Server Creation Wizard
Go to Start > Programs > TIBCO > TIBCO ActiveMatrix 2.1 > Administrator Server Creation Wizard
__ Launch the Administator Server wizard and configure Administrator Server instance
- Keep the defaults for Server name, cluster name and ports
- Authentication Realm: Database Realm, click Next
- Configure the database credentials:
__Database URL: jdbc:hsqldb:hsql://localhost:1234/amx
__Password: <leave blank>
__Verify the parameters and click Next
__Enter the following credentials
- Configuration details for AMX Database:
__Check: User Configuration details from Database Authentication Realm
- __Uncheck Create Default runtime node, click Next
- __Click Finish when done.
2. Start ActiveMatrix Administrator instance
__ Open Windows Services, locate the TIBCO ActiveMatrix Administrator Server service and start it
__Start from command line. Double-click: c:\tibcoam\amxadminstrator\2.1\bin\amx_admin.bat
Note: Wait for the message, “Server [Instance Name] started…” before continuing. This may take a few seconds
3. Log into ActiveMatrix Administrator.
_Log in to ActiveMatrix Administrator as root/root
Open Internet Explorer and type in the following url:
– Username: root
– Password: root
4. Using AMX Administrator, create a new ActiveMatrix Environment.
_In the Perspective list, click Configure Enterprise Assets
_Under Environment, click the New button
- Name: TestEnv
- Description: For AMX Class
- Click Save
5. Add a messaging bus to the Environment.
Note:: An AMX Environment uses EMS for communication between the nodes. You must configure an EMS server for this purpose
__Click on the newly created Environment
- A submenu appears at the bottom. Select Messaging Bus Tab
- Now click Add
- Name: EMSServer
- Connection Type: Direct (default)
- EMS Username: admin and Password: <leave blank>
- Provider URL: http://localhost:7222 (default)
6. Enable your machine for this Environment. _Click the Machines tab
__Choose YES in the Enabled column
__Click Save, to save your changes
__Verify Machine settings by clicking Machines, in the Main Menu
__Notice that your machine’s status is Bound and Available
__Note the JMX Ports: 9999 and 9998
Note: To discover other machines for your Environment, you must use the Discover option, in this tab
7. Create a JMS Shared Resource for monitoring your Environment.
Note: The shared resource definition is needed, before you can configure monitoring and management for your Environment.
_Click on Shared Resource Definitions tab (top menu)
_Choose New >JMS and enter these details
- Name: JMSMonitoring
- Username: admin, Password: (leave it blank)
- Connection type: Direct (default)
- Provider URL: tcp://localhost:7222
8. Create a JDBC Shared Resource for your Environment.
__Still in Shared Resource Definitions tab, choose New >JDBC
- Name: JDBCMonitoring
- JDBC Driver: org.hsqldb.jdbcDriver
- Database URL: jdbc:hsqldb:hsql://localhost:1234/amx
- Username: sa
- Password: <blank>
9. Enable your JMS and JDBC Resources for this Environment.
__Click the Environment Definition tab
__Select your environment and then choose Shared Resource Definitions tab
__For JDBCMonitoring and JMSMonitoring, set Enabled = YES
__Save your changes
10. Enable monitoring and logging for this Environment.
_Click the Administrator Cluster tab
__Click Monitoring Configuration and then Edit
– Enable Monitoring = YES
- JMS Configuration: Choose JMS Configuration >JMSMonitoring
- Metrics Manager Server: Select your server (only one in the list)
Log Services tab: Click New
- Name: DefaultLogService
- JMS Connection: JMSMonitoring
- QueueName: DefaultLogServiceQueue
- Destination: DB (choose JDBCMonitoring from dropdown list)
- Selected Models:
__Highlight the DefaultLogService and click Start
11. Configure a new Node in the Configure an Environment Perspective.
Analysis: A node is a basic unit in an ActiveMatrix environment representing one virtual machine. Typically, a node is associated with a jvm engine. In this step, you will create a node for your environment.
_Choose the Configure an Environment Perspective from the list
_In Nodes, click New
- __Name: MyNode
- __Machine Name: Select your machine
- __Windows Service?: NO
- __Product: C:\TIBCO\amx\22.214.171.124.2.009
- __Messaging Server: EMSServer
- __Management Port: 8130
12. Install the Node and run it.
Analysis: A typical order in the ActiveMatrix environment to get a node to a “Running” state is (1) Create, (2) Install and (3) Start. In this step you will start the Node created from the previous step.
_The Install button is enabled. Click on it
Note: After a few seconds, click the Refresh button on the same screen (right corner), Node status is Installed/Stopped
__This action takes a couple of minutes
__Click Refresh, and verify that the Node is Running
__Logout of ActiveMatrix Administrator when done.
For training on TIBCO AMX Administrator mail us at firstname.lastname@example.org