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.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).
Ensure that the TIBCO Enterprise Message Service server has started. One way to start the server is as follows:Start > All Programs > TIBCO > TIBCO EMS VersionNumber > Start EMS Server.
1.
2. In each window enter the following command (modified as needed according to the location of your EAR file):
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.
3. Open three more command windows in BE_HOME/bin, and in each window enter one of the following commands:
C:\tibco\be\3.0\bin>be-engine -n engine1 -p agent1.tra c:\temp\FDCache.ear
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):
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.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.
Copyright © TIBCO Software Inc. All Rights Reserved.