BW6 monitoring using TIBCO RT View

Hi All,

We are workign on POC where we are trying to implement BW6 monitoring using TIBCO RT View. With the default configuration given in the document, we couldn't see any domain, app space or app node information in RT View. In RT view logs, we could see below error. Can anyone help on this issue plz?

 

2018-11-06 16:53:08,396 INFO  main - [rtview] ... common.RtvApmAppManager.initialize()

2018-11-06 16:53:08,523 INFO  main - [rtview] (running daemon)

2018-11-06 16:53:08,633 INFO  main - [rtview]   ... added appManager: bwmon

2018-11-06 16:53:08,648 INFO  main - [rtview]   ... added appManager: hawkmon

2018-11-06 16:53:08,845 INFO  main - [rtview] ... adding Function Handler for package (rtvmgr)

2018-11-06 16:53:08,847 INFO  main - [rtview] ... adding Function Handler for package (hostbase)

2018-11-06 16:53:08,847 INFO  main - [rtview] ... adding Function Handler for package (bw6mon)

2018-11-06 16:53:08,850 INFO  main - [rtview] ... adding Function Handler for package (bwmon)

2018-11-06 16:53:08,862 INFO  main - [rtview] ... adding Function Handler for package (hawkmon)

2018-11-06 16:53:11,344 INFO  main - [rtview] Unable to connect to database <RTVHISTORY>:

2018-11-06 16:53:11,344 INFO  main - [rtview]     socket creation error


2018-11-06 16:53:14,360 INFO  main - [rtview] Unable to connect to database <ALERTDEFS>:

2018-11-06 16:53:14,360 INFO  main - [rtview]     socket creation error

2018-11-06 16:53:14,360 INFO  JMX ConnectionThread--local - [rtview] ... initializing RtvApmJmxHandler (common) for: local

2018-11-06 16:53:15,536 INFO  main - [rtview] ERROR: Invalid data source key: hawk

4 Comments

Another thing to check. Assuming that you have added the following entry to your logback.xml ($TIBCO_HOME/bw/6.3/domains/<domain>/appnodes/<appspace>/<appnode>/logback.xml):

    <logger name="com.sl.rtvapm.osgi"> 

        <level value="TRACE"/>

    </logger>

then your bwappnode.log should show the following entries where the bold lines confirm the host:port that your osgi is sending data to.

2018-06-05 14:34:44.921 INFO  [AppNodeStateNotificationThread] com.tibco.thor.frwk - AppNodeStateNotificationThread started

2018-06-05 14:35:21.098 TRACE [main] com.sl.rtvapm.osgi.Activator - Activator.start: BundleContext org.eclipse.osgi.internal.framework.BundleContextImpl@6d842877

2018-06-05 14:35:21.098 TRACE [main] com.sl.rtvapm.osgi.Updater - Updater.constructor

2018-06-05 14:35:24.202 INFO  [main] com.tibco.bw.frwk.engine.BWEngine - TIBCO-BW-FRWK-300002: BW Engine [Main] started successfully.

2018-06-05 14:35:24.327 TRACE [main] com.sl.rtvapm.osgi.ServiceComponent - ServiceComponent.setManagementClient: BWManagementClient com.tibco.bw.thor.management.node.BWInternalManagementClient@17e725fb

2018-06-05 14:35:24.327 TRACE [main] com.sl.rtvapm.osgi.Updater - Updater.setManagementClient: BWManagementClient com.tibco.bw.thor.management.node.BWInternalManagementClient@17e725fb

2018-06-05 14:35:24.343 INFO  [main] com.sl.rtvapm.osgi.Updater - RTView OSGi Plugin for TIBCO BusinessWorks v4.2.0: / qawin5agent / devnode / DevSpace

2018-06-05 14:35:24.358 TRACE [main] com.sl.rtvapm.osgi.Updater - Statistics enabled

2018-06-05 14:35:24.421 INFO  [main] com.sl.rtvapm.osgi.Updater - Agent qawin5agent sending to localhost:4572 every 10 seconds


2018-06-05 14:35:44.457 TRACE [Timer-0] com.sl.rtvapm.osgi.Updater - updateData for devnode

2018-06-05 14:35:44.457 TRACE [Timer-0] com.sl.rtvapm.osgi.Updater - sending Bw6OsgiAgents for qawin5agent

2018-06-05 14:35:44.457 TRACE [Timer-0] com.sl.rtvapm.osgi.Updater - sending __Bw6HawkAppNodeProcessInfo 1 rows

2018-06-05 14:35:44.457 TRACE [Timer-0] com.sl.rtvapm.osgi.Updater - sending __Bw6HawkApps 1 rows

2018-06-05 14:35:44.457 TRACE [Timer-0] com.sl.rtvapm.osgi.Updater - sending __Bw6HawkProcessStatistics 2 rows 

2018-06-05 14:35:54.472 TRACE [Timer-0] com.sl.rtvapm.osgi.Updater - updateData for devnode

2018-06-05 14:35:54.472 TRACE [Timer-0] com.sl.rtvapm.osgi.Updater - sending Bw6OsgiAgents for qawin5agent

2018-06-05 14:35:54.472 TRACE [Timer-0] com.sl.rtvapm.osgi.Updater - sending __Bw6HawkAppNodeProcessInfo 1 rows

2018-06-05 14:35:54.488 TRACE [Timer-0] com.sl.rtvapm.osgi.Updater - sending __Bw6HawkApps 1 rows

2018-06-05 14:35:54.488 TRACE [Timer-0] com.sl.rtvapm.osgi.Updater - sending __Bw6HawkProcessStatistics 5 rows 

2018-06-05 14:36:04.503 TRACE [Timer-0] com.sl.rtvapm.osgi.Updater - updateData for devnode

2018-06-05 14:36:04.503 TRACE [Timer-0] com.sl.rtvapm.osgi.Updater - sending Bw6OsgiAgents for qawin5agent

2018-06-05 14:36:04.503 TRACE [Timer-0] com.sl.rtvapm.osgi.Updater - sending __Bw6HawkAppNodeProcessInfo 1 rows

2018-06-05 14:36:04.519 TRACE [Timer-0] com.sl.rtvapm.osgi.Updater - sending __Bw6HawkApps 1 rows

2018-06-05 14:36:04.519 TRACE [Timer-0] com.sl.rtvapm.osgi.Updater - sending __Bw6HawkProcessStatistics 5 rows


 

If you don't see the above lines (when TRACE is enabled), then the osgi plugin is not working properly.

Ed

ekoo2008 - Nov 08, 2018 - 11:06pm ::

Hi

>bw6mon ./bw6mon dataserver rundata -propfilter:receiver 

The readme.txt is misleading in this regard.  The above line is not valid for a different RTView product, not TIBCO RTView BW Monitor.

For BW Monitor, you should do the following instead

1. edit rtvservers.dat

2. locate the following entry (line 4)

default    .    dataserver    rundata

3. add -propfilter:receiver to the end of line 4, e.g.,

default    .    dataserver    rundata -propfilter:receiver

4. save rtvservers.dat

5. type

start_rtv.bat default dataserver

or

start_rtv.sh default dataserver

Your dataserver should start now.

Ed

ekoo2008 - Nov 08, 2018 - 11:00pm ::

Hi Ed,

 

Thanks a lot for you reply. We are using BW 6.4.2 and RTView BWMON 6.7. Application was deployed to AppSpace. We are not using any containers for now. (That is the next step though).

We are using latest version of OSGI plugin and follwed the instructions that were given in Readme.txt file. 

When I added below line in rtvservers.dat file, moniotoing console is not getting displayed at all. Only Historian and DB services are being started. 

bw6mon ./bw6mon dataserver rundata -propfilter:receiver 

Don't understand why the service is not being up with the above command.

Please let me know your inputs.

 

 

rnimmala - Nov 08, 2018 - 1:29am ::

Hi 

The errors you have outlined in bold are not the cause of your problem. These are simple db connection errors that prevent you from retrieving historical data stored in your database. But you should be able to see live current data regardless of the db errors.

Can you clarify how you are currently deploying your BW6 appnodes? You are deploying in the standard appspace and not in docker or pcf containers, correct? What specific version of BW 6 are you using?

What version of RTView BWMON are you using? We recommend using the latest v6.7 that can be downloaded from TIBCO Download site.

We recommend that you use the osgi plugin to retrieve metrics from your appnodes. The plugin is more efficient than getting the metrics directly from hawk. Instructions on how to configure the osgi plugin for your environment can be found under BWMON_6.7/rtvapm/bw6mon/agents/osgi/README.txt

I've included the relevant parts of the README below. If you continue to have problems with getting BWMON to work, please email support@sl.com so we can assist you.

Ed

 

    RTView OSGi Plugin for TIBCO BusinessWorks

    Installation and Use

    ------------------------------------------

-------------

Description

-------------

RTView monitor for Tibco BusinessWorks has been enhanced with the ability to monitor 

BW6 applications deployed in AppSpaces, and in Docker and PCF containers, using the 

new RTView OSGi Plugin for TIBCO BusinessWorks. 

The OSGi plugin sends BW6 metrics to a receiving RTView dataserver using a standard 

TCP socket. With the plugin there is no need to use Hawk for monitoring purposes.



-------------

Prerequisites

-------------

BW 6.3.4

BWCE 2.2.0

RTVAPM X.X



-------------

Configuration

-------------

This section describes how to configure the plugin and the receiving dataserver.

Specific procedures for each deployment are given below.

The RTView OSGi plugin is configured with the following properties: 

    sl.rtview.rtvagent.name

This is the name by which the plugin will be identified in the RTView displays.

It should be unique and should identify the sender, for example the hostname.

example: sl.rtview.rtvagent.name=hostname

default: updater        

    sl.rtview.rtvagent.target

    

This is the host and port of the receiving RTView dataserver.

example: sl.rtview.rtvagent.target=receiver:3372

default: localhost:3372

    sl.rtview.rtvagent.update

    

This is how often the plugin sends data, in seconds.

example: sl.rtview.rtvagent.update=30

default: 10

    sl.rtview.bw.activities.enabled

This enables BW6 activity metrics to be collected

example: sl.rtview.bw.activities.enabled=true

default: false



With the container deployments you may also use the following properties

to provide specific names for the domain, appspace, and appnode. 

    sl.rtview.bw.domain        

    sl.rtview.bw.appspace

    sl.rtview.bw.appnode

    

example:         

    sl.rtview.bw.domain=Containers        

    sl.rtview.bw.appspace=Docker

    sl.rtview.bw.appnode=docker-1

    

If you supply specific names then your containers will appear in the displays 

as if they were appnodes in an appspace. Furthermore if multiple containers 

are instances of the same application, the metrics of the container appnodes 

will be summed for the application, as if it were deployed to the appspace.

if you don't supply specific names, a unique name will be created for the appnode 

and used to identify the container, and each container will appear as a standalone 

application with a single appnode.

The receiving RTView dataserver is configured as follows:

1. Include the flag "-propfilter:receiver" in the command used to run the dataserver. 

    You may add this to the dataserver line in your rtvservers.dat file, e.g.

    

    bw6mon ./bw6mon dataserver rundata -propfilter:receiver    

    

    Or use it on the command line, e.g.

    

        rundata.sh -propfilter:receiver -properties:sample



-------------

BusinessWorks

-------------

The plugin is configured using appspace properties with the following procedure:

1. Stop the bwagent, if running.

2. Copy the plugin to $TIBCO_HOME/bw/6.3/system/hotfix/shared.

3. Start the bwagent. Do not start the AppNode(s) yet.

Note: Continue to step 4 if you want to modify the default property values. 

You may skip steps 4-8 entirely if you want to use the default property values.

4. Navigate to the AppSpace folder: $TIBCO_HOME/bw/6.3/config/

5. Copy the appspace_config.ini_template file to a temporary file.

6. Edit the temporary file and set the properties below as needed.

7. Use the bwadmin config command to push the configuration to the AppSpace:

    bwadmin config -d myDomain -cf <temporary-file> appspace myAppSpace

8. Use the bwadmin config command to push the configuration to each AppNode in the AppSpace:

    bwadmin config -d myDomain -a myAppSpace -cf <temporary-file> appnode myAppNode

9. (Optional) To see plugin output (INFO or TRACE) in the bwappnode.log file, 

    add the following to the "user properties" section of the logback.xml file 

    ($TIBCO_HOME/bw/6.3/domains/<domain>/appnodes/<appspace>/<appnode>/logback.xml):

    <logger name="com.sl.rtvapm.osgi"> 

        <level value="INFO"/>

    </logger>

    

    NOTE: When debugging the behavior of the OSGi plugin, it is recommended to set level value to "TRACE". 

10. Restart the AppNode(s).

11. Repeat steps 7-10 for every AppSpace to be monitored.

 

 

ekoo2008 - Nov 07, 2018 - 2:36pm ::
View More Comments + Add a Comment

(1) Answer

Login