WebStudio - "BuildandDeploy" step results in error in WebStudio in decision table modification flow.

WebStudio - "BuildandDeploy" step results in error in WebStudio in decision table modification flow.

book

Article ID: KB0091606

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition -
Not Applicable -

Description

Resolution:
Abstract
===========
WebStudio – Received error “Ear for projects: &ltproject_name> either not present or not in sync at deploy location” in WebStudio when selecting “BuildandDeploy” after approving changes to decision table.

Description:
===========
The following are detailed steps to modify, commit, approve, build and deploy changes to decision tables from WebStudio.  If the steps are not followed in the listed order you will run into the error message “Ear for projects: &ltproject_name> either not present or not in sync at deploy location” in WebStudio when selecting “BuildandDeploy”.


1). Start RMS and login to WebStudio at http://&lthostname>:&ltport>/WebStudio.

2). Once logged in, checkout any project which is part of the examples shipped with BE installation or your own project.

3). After checkout click on “Generate Deployable” to generate the EAR file. Basically, BuildAndDeploy for DecisionTable results in a code generated java + class file (which in turn needs an ear to be available to resolve dependencies). However, the result of RuleTemplate changes is a serialized XML model, hence the different behavior. It does not need the “Generate Deployable” step at the beginning of the process.

4). Open decision table that you want to modify and change the value in some field and save the change.

5). Now, COMMIT the change and proceed to “Worklist” to Approve and then “BuildandDeploy”.

6). As a final step you can again use “Generate Deployable” and check the first checkbox to “generate classes” with changes that you just did.


Environment:
=============
TIBCO Business Events 5.1.x, Business Events Decision Manager add-on is needed.

Symptoms:
==============
If you do not perform “generate deployable” step at the beginning you will run into issues when you finally reach the “BuildandDeploy” step after Approval stage.


Cause:
=============
Not generating deployable (EAR file) at the beginning of the decision table modification process.


Resolution:
===========
In WebStudio after project checkout Click on “Generate Deployable” option to generate the EAR file.

Issue/Introduction

WebStudio - "BuildandDeploy" step results in error in WebStudio in decision table modification flow.