Description:

In TIBCO BusinessEvents WebStudio, using the BuildAndDeploy you can generate the class file and hot deploy the decision table. There are however a few prerequisites.

1). For generation of class file and hot deployment of a decision table, you must have a generated EAR for the project.

2). Ensure that JMX connection details for the environments where you deploy are configured for the projects in the hot deploy properties group in the RMS.cdd file. Here is a sample RMS configuration for reference.

            <property-group comment="" name="HotDeploy">
                <property name="CreditCardApplication.ws.applicableEnviroments" type="string" value="QA,PROD"/>
                <property name="CreditCardApplication.QA.ws.jmx.host" type="string" value="localhost"/>
                <property name="CreditCardApplication.QA.ws.jmx.port" type="integer" value="9990"/>
                <property name="CreditCardApplication.QA.ws.jmx.user" type="string" value=""/>
                <property name="CreditCardApplication.QA.ws.jmx.password" type="string" value=""/>
                <property name="CreditCardApplication.QA.ws.jmx.clusterName" value="CreditCardApplication"/>
                <property name="CreditCardApplication.QA.ws.jmx.agentName" value="inference-class"/>
                
                <property name="OverdraftNotifications.ws.applicableEnviroments" type="string" value="QA,PROD"/>
                <property name="OverdraftNotifications.QA.ws.jmx.host" type="string" value="localhost"/>
                <property name="OverdraftNotifications.QA.ws.jmx.port" type="integer" value="9992"/>
                <property name="OverdraftNotifications.QA.ws.jmx.user" type="string" value=""/>
                <property name="OverdraftNotifications.QA.ws.jmx.password" type="string" value=""/>
                <property name="OverdraftNotifications.QA.ws.jmx.clusterName" value="overdraftnotifications"/>
                <property name="OverdraftNotifications.QA.ws.jmx.agentName" value="inference-class"/>
            </property-group>?
            

3) .Please make sure you uncomment the property java.property.be.engine.jmx.connector.port=%jmx_port% in be-engine.tra and start the BE cache and Inference with --propVar jmx_port_number

Example:  --propVar jmx_port=9990

4). While doing BuildAndDeploy, select "Environment" (under tab beside status tab) as well.

5). For hot deployment of the decision table, ensure that the project's CDD file (for which the decision table is hot deployed) has the be.engine.cluster.externalClasses.path property under the appropriate processing unit.

Example: default

6). For hot deployment of the business rule, ensure that the project's CDD file (for which the business rule is hot deployed) have the be.cluster.ruletemplateinstances.deploy.dir property under the appropriate processing unit.

Example: default

Note: Using Global variable for these properties 'be.engine.cluster.externalClasses.path' and 'be.cluster.ruletemplateinstances.deploy.dir' is not supported.

How to resolve JMX exceptions while performing BuildADeploy operations from WebStudio.

Hot Deployment in WebStudio currently works only for cluster based projects, i.e., Cache OM. Build and Deploy happens as a combination. You cannot disable one of them. These following JIRA's were raised to support hot deployment for In Memory projects: