Running a second instance ofTIBCO BusinessEvents (BE) Views will cause ports to change.

Running a second instance ofTIBCO BusinessEvents (BE) Views will cause ports to change.

book

Article ID: KB0090429

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition -
Not Applicable -

Description

Resolution:
Description:
============
Two BE Views applications are launched on different ports but only one application shows up on both sets of ports.

Environment:
==========
BE 5.0.x

Cause:
=====
BE Views was not designed to have multiple BE projects running at the same time so running a second BE Views project replace the first BE Views project web root directory.

Resolution:
=========
The default location for BE Views web root is $BE_HOME/views/web-root.  What you must do is create two new web-root directories named after the two projects and then change the two CDD files to reflect the correct web-root directories.

0). Run one of the BE Views application and then stop it.

1). Create two directories:
   a). $BE_HOME/views/web-root-&ltproject_name_A>
   b). $BE_HOME/views/web-root-&ltproject_name_B>

2). Copy everything from $BE_HOME/views/web-root to the two directories EXCEPT clientconfig.xml.  After you deploy the BE Views application a new clientconfig.xml will be created in the new directories.

3). In each project CDD file add the property “be.agent.dashboard.http.docroot” to “dashboard-agent-class” and set the value to $BE_HOME/views/web-root-&ltproject_name_A> or $BE_HOME/views/web-root-&ltproject_name_B> depending on which project CDD you are editing.

Additional Key Points:
1). Make sure be.agent.dashboard.pullrequestport and be.agent.dashboard.streamingport are set to unique values in each project

2). If needed make sure that the data grid is configured properly to allow multiple clusters on the same machine.

Issue/Introduction

Running a second instance ofTIBCO BusinessEvents (BE) Views will cause ports to change.