Deploying the inference engine and cache server using TIBCO Administrator.

Deploying the inference engine and cache server using TIBCO Administrator.

book

Article ID: KB0090154

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition -
Not Applicable -

Description

Resolution:
Description:
=========
Deploying the inference engine and cache server using TIBCO Administrator.

Environment:
==========
BusinessEvents 3.x
All OS

Symptoms:
=========

Cause:
======

Reference:
==========
"Chapter 26 Deploytime Configuration : Customizing the List of Properties on the Advanced Tab" in BE user's guide.


Resolution:
=========

All the relavant properties of the inference engine and cache server need to be added to  the be-engine.xml file which is under:
%TIBCO_HOME%\be\3.0\lib\com\tibco\deployment.    
        
    &ltproperty>
    &ltname&gtjava.property.tangosol.coherence.cluster</name>
    &ltdefault></default>
    &ltdescription&gtCluster Name</description>
    </property>
    &ltproperty>
        &ltname&gtjava.property.tangosol.coherence.clusteraddress</name>
        &ltdefault></default>
        &ltdescription&gtCluster Address</description>
    </property>
    &ltproperty>
    &ltname&gtjava.property.tangosol.coherence.ttl</name>
    &ltdefault></default>
    &ltdescription&gtTime-to-live setting for multicast packets</description>
    </property>
    &ltproperty>
    &ltname&gtbe.engine.cluster.multiEngineOn</name>
    &ltdefault></default>
    &ltdescription&gtMulti-engine mode (true or false)</description>
    </property>
    &ltproperty>
    &ltname&gtbe.engine.cluster.minCacheServers</name>
    &ltdefault></default>
    &ltdescription&gtNumber of cache servers to be up and running before the other agents start up and the data is loaded from backing store if backing store is configured. Default is 1</description>
    </property>
    &ltproperty>
    &ltname&gtjava.property.tangosol.coherence.distributed.localstorage</name>
    &ltdefault></default>
    &ltdescription&gtConfigure a node as a storage node or inference agent/query agent only</description>
    </property>
    &ltproperty>
    &ltname&gtAgent.&ltagentgroup>.maxActive</name>
    &ltdefault></default>
    &ltdescription&gtNumber of active inference agents. In single engine mode this property is ignored and its default to 1</description>
    </property>    
    &ltproperty>
        &ltname&gtAgent.&ltagentgroup>.priority</name>
        &ltdefault></default>
        &ltdescription&gtAgent priority</description>
    </property>
    &ltproperty>
        &ltname&gtAgent.&ltagentgroup>.key</name>
        &ltdefault></default>
        &ltdescription&gtAgent name or key</description>
    </property>    
    

Please note that (Agent.&ltagentgroup>.maxActive, Agent.&ltagentgroup>.priority and Agent.&ltagentgroup>.key) is set using the agent group name that is set in the BAR of  the designer.


Open the designer and configure the BAR and EAR and build the EAR file. Then in the admin GUI, do the following:

1). Create 2 (1- inference and 1- cache server) by uploading the above EAR file.

2). To view the properties that you have set in the be-engine.xml, expand Application Management > application_name > Configuration > application_name.bar, and then click the Advanced tab. Both applications will  have the same set of properties that are used in the  be-engine.xml file.

3). The relavant values for these properties can be populated in each of the applications.

Issue/Introduction

Deploying the inference engine and cache server using TIBCO Administrator.