This note has been tested with Tibco Runtime Agent (TRA) 5.6, Tibco Administrator 5.6, Ant 1.8 and Groovy 1.8

Deploying of (BusinessWorks) ear files in Administrator is often easier using a script calling AppManage (in the TRA distribution) than doing it manually in the Administrator web frontend. With scripted deployments the ear file and the deployment xml file containing the process and global variable settings is usually extracted from a version control system. So a working scripted deployment guarantees that these settings will not be lost.

In some cases deployed processes should not be stopped and restarted during deployment. For example when the tra file needs to be (manually or scripted) updated after deployment. Or when processes are running load balanced and should not have any downtime. Administrator facilitates such deployments, but it can be beneficial to do such deployments in a scripted way. The following targets stop and start processes in Tibco Administrator using AppManage called from ant.

The following ant target starts or stops processes in a deployment within Tibco Administrator:

Note several ant properties. These can be supplied from the command line or from Jenkins/Hudson:

• Administrator host ssh credentials: tibco.admin.host, ssh.user, ssh.password
• Name of Tibco Administrator domain: tibco.admin.domain
• Deployment to start or stop: tibco.app.name, in Administrator directory tibco.admin.dir
• Optional service such as an adapter, or process archive (.par) to start or stop: tibco.app.service
• Start or stop: tibco.app.startOrStop with value “start” or “stop”.

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

Every host where tibco rvd is running expose on HTTP interface using that we can get many useful information e.g

— How many clients are connecting to a particular service
— Which services has been subscribed by rvd
— Which hosts are connected to this rvd.
— How much data has been sent to received
— Viewing tibco log to figure out any tibco issue.
— Hwo many subject a particular service is using and what are those etc.

to check on which Http port your rvd is publishing information do this in your linux/windows host where rvd is running

ps -ef | grep rvd

this will show rvd process with parameters used for starting “-http 7582″ shows that http interface is on port 7582
now just type this in your browser.

http://hostname:7582/


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

DMZ is situated in between two firewall (outside and inside) .
Also any http or https request which is coming from outer world, DMZ forwarded that request to interior server through
rv( rvrd).


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

Integration Framework implementation need to use BusinessConnect (BC) for communications with anexternal ftp. It is good practice we intend to implement this using the BC ‘Dual Firewall DMZ Mode’deployment type. This involves an ‘Interior Server’ component on a machine within the network and a‘DMZ Server’ component operating between two firewalls (the external firewall and the firewallbetween the DMZ and rest of the network).

Our domain uses EMS as its primary communications transport method (the Interior Server is already amember of the domain as it can communicate using EMS), but for the DMZ Server required to useRendezvous in order to employ the protocol break concept for security.

So far we have been able to configure the Rendezvous Routing Daemon (rvrd) to run as a service onthe Interior and DMZ Server. By using the web gui for rvrd to add each machine (Interior and DMZServers) as a neighbor and thus enabled the machines to see each other through the firewall.

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

This note has been tested with Tibco Runtime Agent (TRA) 5.6, Tibco Administrator 5.6, Ant 1.8 and Groovy 1.8

Deploying of (BusinessWorks) ear files in Administrator is often easier using a script calling AppManage (in the TRA distribution) than doing it manually in the Administrator web frontend. With scripted deployments the ear file and the deployment xml file containing the process and global variable settings is usually extracted from a version control system. So a working scripted deployment guarantees that these settings will not be lost.

The following ant target deploys an ear file using AppManage:

Note the use of Flaka to manipulate ant properties.
Note also several ant properties. These can be supplied from the command line or from Jenkins/Hudson:

• Server credentials: tibco.admin.host, ssh.user and ssh.password.
• Tibco Administrator credentials: tibco.admin.domain, tibco.admin.user
• Appmanage location and Administrator domain: ${serverTibcoTraDir}/5.6/bin, ${tibco.admin.domain}
• Ear file and global variables: ${tibco.app.earfile}.ear, ${tibco.app.config}.xml.
• Name and directory of the deployment in Administrator: tibco.admin.dir and tibco.app.name.
• Deployment description, overwrites the description in the global variables xml: appmanage.deployment.description
• Other parameters for AppManage, boolean values: appmanage.nostart, appmanage.nostop, appmanage.forceDeployment.

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

Tibco RV messagging
1) location transparency
2) platform independence
3) reliable and fast
4) comprehensive API
5) point to point delivery and publish/subscribe delivery.

Location transparency
———————–
Location transparency means for sending and receiving message on a multicast network you need not to aware of physical location of sender or receiver as long as you know the topic( also called subject in tibco world) , so its pretty simple Sender publish message on multicast topic in a network and all subscriber which have subscribed on that topic receives message without being knowing physical location of publisher.

Sender could be anywhere in the world e..g New york ,Tokyo , London , receiver can be anywhere e.g. London , Hongkong , Tokyo.

Platform independence
———————–
its doesn’t depend on platform , Sender can be running on unix box while receiver could be running on windows machine. most of the time GUI runs on windows and Server
runs on Linux and they exchange messages via tibco.

Reliable and Fast
—————--
TIbco RV makes best effort (not guaranteed) to deliver message to receiver
and its very fast usually used to send Market data etc but not used for sending Order or execution message because there is always chance of loosing such message.
generally we use  certified message to make guaranteed delivery of those message.

Comprehensive API
—————--
tibco rv comes with rich API in both C++ and Java language and can be plugged to application easily, API provides methods and classes for different modes of communication e.g. Point to Point , publish/subscribe , certified messaging etc.

Point to Point Deliver
———————–
Tibco can be used for point-2-point delivery (some times also called Request/Reply mode), it used “INBOX” topic for doing so , when  tvd sees INBOX topic instead of publishing that message into multicast network it makes direct connection to destination host and sends message.

Publish/Subscribe
——————-
This is achieved using “Subject” or “Topic” , receiver subscribes on multicast network on a particular topic and Sender sends message on those Topic, after that its tibco’s responsibility to deliver those message.



For training on TIBCO mail us at [email protected]

Every host where tibco rvd is running expose on HTTP interface using that we can get many useful information e.g

— How many clients are connecting to a particular service
— Which services has been subscribed by rvd
— Which hosts are connected to this rvd.
— How much data has been sent to received
— Viewing tibco log to figure out any tibco issue.
— Hwo many subject a particular service is using and what are those etc.

to check on which Http port your rvd is publishing information do this in your linux/windows host where rvd is running

ps -ef | grep rvd

this will show rvd process with parameters used for starting “-http 7582″ shows that http interface is on port 7582
now just type this in your browser.

http://hostname:7582/




For training on TIBCO mail us at [email protected]