Chapter 3 Cache Object Management Tutorial : Deploy the Agents and Cache Servers

Deploy the Agents and Cache Servers
It is helpful if you can size the command windows so that you can see all five windows at one time. First you will start the cache servers, as is common practice.
Learning Points
Cache servers start first  It is important that cache servers start before inference agents. The order in which you start the engines is not important, as long as you have set the be.engine.cluster.minCacheServers property, which ensures cache servers start up first (see Configure Cache Cluster Properties).
Task K Start the BusinessEvents Engines and Cache Servers
Start > All Programs > TIBCO > TIBCO EMS VersionNumber > Start EMS Server.
1.
Open two command windows and in each navigate to BE_HOME/bin. For example: c:\tibco\be\3.0\bin.
2.
be-engine -n CS1 --propFile cs.tra c:\temp\FDCache.ear
be-engine -n CS2 --propFile cs.tra c:\temp\FDCache.ear
The --propFile argument is case sensitive.
The -n option is optional. It lets you assign a user-friendly name to the engine. The command windows and log files display the name you enter. A separate log file using the name is created as well.
You see many informational messages in the windows as the cache servers come up.
3.
Open three more command windows in BE_HOME/bin, and in each window enter one of the following commands:
be-engine -n engine1 --propFile agent1.tra c:\temp\FDCache.ear
be-engine -n engine2 --propFile agent2.tra c:\temp\FDCache.ear
be-engine -n engine3 --propFile agent3.tra c:\temp\FDCache.ear
You see engine startup messages in the console, beginning like the following:

 
C:\tibco\be\3.0\bin>be-engine -n engine1 -p agent1.tra c:\temp\FDCache.ear
Using property file: C:\tibco\be\3.0\bin\be-engine.tra
******************************************************************
TIBCO BusinessEvents Enterprise Suite 3.0.0.009 (2008-05-27)
Using arguments :-n engine1 -p agent1.tra c:\temp\FDCache.ear
Copyright¬ 2004-2008 TIBCO Software Inc. All rights reserved.
******************************************************************
Using property file: agent1.tra

 
You see various initialization messages, including:
Cluster AcmeCluster starting in MULTIPLE PRIMARY MODE
If you do not see the above, check that you configured the BusinessEvents archive resource Object Management tab to use cache OM.
On the engine that starts first, you see the message (or messages) you configured in the startup rule function (see Configure the InitializeAccount Rule Function and Task F, Add Checks in the InitializeAccounts Rule):

 
############### Created account ActA
 
############### Also created account ActB

 
No other engine displays those messages because of the lock and the check for existence of this concept instance that you added in step Task F, Add Checks in the InitializeAccounts Rule.
Troubleshooting
If another user on the same network is using the same multicast properties as you, you will have to set a different cluster IP address property in all files.