public static void main(String[] args) throws RuntimeException {

DaemonManager daemonManager = new DaemonManager(“http://virtualnuggets.com:7580″);

if(daemonManager.getDaemonType() == DaemonManager.RVD) {
DaemonProxy daemonProxy = daemonManager.getDaemonProxy();

final RvdProxy rvdProxy = (RvdProxy) daemonProxy;

System.out.println(rvdProxy.getComponentName());
System.out.println(rvdProxy.getComponentInformation().getHostname());
System.out.println(rvdProxy.getComponentInformation().getIpAddress());
System.out.println(rvdProxy.getComponentInformation().getLicenseTicket());
System.out.println(rvdProxy.getComponentInformation().getName());
System.out.println(rvdProxy.getComponentInformation().getProcessID());
System.out.println(rvdProxy.getComponentInformation().getVersion());

Service[] services = rvdProxy.getServices();

System.out.println(services.length); //prints 0

for (Service service : services) {
System.out.println(service.getNetwork());
}

}
}





For training on TIBCO mail us at [email protected]

When defining the database stores in EMS 5.x, you will need to define the following parameters in stores.conf:

dbstore_driver_url = JDBCURL
dbstore_driver_username = username
dbstore_driver_password = password

The database password can be entered as clear text for two parameters: dbstore_driver_password and dbstore_driver_url.

1. dbstore_driver_password

You can also use a mangled password for the dbstore_driver_password. That is, you can use the tibemsadmin tool to mangle a database password and define the mangled password for dbstore_driver_password.
For example, you can run the tibemsadmin command to mangle a clear text password:

===================================================
tibemsadmin.exe -mangle
TIBCO Enterprise Message Service Administration Tool.
Copyright 2003-2008 by TIBCO Software Inc.
All rights reserved.
Version 5.0.0 V27 4/29/2008
Enter phrase to mangle:
Confirm phrase to mangle:
$man$-RV84410jfkIKs3GET2dmcc5MPs
===================================================

In stores.conf, you can define the mangled password for dbstore_driver_password:
dbstore_driver_password=$man$-RV84410jfkIKs3GET2dmcc5MPs

2. dbstore_driver_url

When defining dbstore_driver_url for an Oracle database, the URL format is entered as following:

jdbc:oracle:thin:/@:/{remote database name} If you don’t want to enter the clear text database password within the URL, you can define the Oracle service name (aliase name) for the database using the following syntax: dbstore_driver_url=jdbc:oracle:thin:@:/{dbservice name}

This way you don’t need to define dbusername and dbpassword in the dbstore_driver_url parameter.




For training on TIBCO EMS mail us at [email protected]

The steps to create service environments are

Configure an ActiveMatrix Administrator server
Start the ActiveMatrix server
Create an ActiveMatrix environment
Create an ActiveMatrix Node

Prerequisites
TIBCO EMS 5.0.0
Hibernate 3.2.2
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.

Steps

1. Create ActiveMatrix Administrator instance

__Start HSQLDB
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 Driver: org.hsqldb.jdbcDriver
__Database URL: jdbc:hsqldb:hsql://localhost:1234/amx
__Username: sa
__Password: <leave blank>
__Verify the parameters and click Next
__Enter the following credentials
__Username: root
__Password: root
__Click Next

• Configuration details for AMX Database:

__Check: User Configuration details from Database Authentication Realm
__Click Next

• __Uncheck Create Default runtime node, click Next
• __Click Finish when done.

Note: This creates the ActiveMatrix Administrator instance


2. Start ActiveMatrix Administrator instance

__ Open Windows Services, locate the TIBCO ActiveMatrix Administrator Server service and start it
OR
__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:
http://localhost:8120/amxadministrator/admin.jsp
– Username: root
– Password: root
_Click Login


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

__A new menu appears on the right. Enter these details

• Name: EMSServer
• Connection Type: Direct (default)
• EMS Username: admin and Password: <leave blank>
• Provider URL: http://localhost:7222 (default)
• Save

6. Enable your machine for this Environment. _Click the Machines tab

__Click Edit
__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

__Test Connection and Save


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>

__Test Connection and Save your changes


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
__Click Edit
__For JDBCMonitoring and JMSMonitoring, set Enabled = YES
__Save your changes


10. Enable monitoring and logging for this Environment.

_Click the Administrator Cluster tab
_Enable Monitoring
__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)
• Save

__Enable Logging:
Log Services tab: Click New

• Name: DefaultLogService
• JMS Connection: JMSMonitoring
• QueueName: DefaultLogServiceQueue
• Destination: DB (choose JDBCMonitoring from dropdown list)
• Selected Models:
  • BaseEventFormat
  • BWEngineEventFormat
  • EngineEventFormat

Click Save button
__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\2.0.2.0.2.009
• __Messaging Server: EMSServer
• __Management Port: 8130

_Click the Save button


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
_Click Start
__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 [email protected]