Monitoring Performance of Tibco Components

Performance test  TIBCO BW

The scope of Stress/Performance testing primarily included monitoring the behavior of Tibco Components while processing peak volume data. The data transfer was across RVRD

The main aim of  the stress tests was to

ü  Monitor the Memory usage of each Tibco Component.

Measure the Processor time consumed by each Tibco Component

Capturing Performance Parameters

This is achieved by capturing the data in Performance Logs. Tibco online training deals with the creation of Performance Logs is explained in the steps below.

 Step 1:-

The first step involves creation of counter logs. Counter logs can be accessed from below path.

 

           Control Panel à Administrative Tools à Performance

Step 2:-  Start adding the counters to the counter logs.

Step 3:-  To gather the details of the processor id add Process as the performance object and counter as ID Process .  Include all the adbagents, bwengines, adr3 processes running on the server. 

Step 4:-  For capturing the percentage processor time consumed by the component add Processor Time as

a counter. Apply this counter to all the Tibco Components which need to be monitored.

Step 5:-  Memory usage of the components can be captured by including Working Set from the counter list.

Please note that the above counters need to be added to all the Tibco Component instances running on the server.

Step 6:- After inclusion of all the counters configure Performance log file in to which all the information needs to be logged in to. The below snapshots give an idea for confirmation of the file.

Step 7:- We can select the time limit during which the components need to be monitored by configuring various scheduling options available.

TIBCO Businessworks File alias Creation

USING LIBRARY –THROUGH ALIASES

1. Aliases are used to manage access to LibraryBuilder resources. The aliases created are saved in user profiles and available to all projects are created on a machine. Other developers can export aliases to LibraryBuilder resources, so they can be imported into other projects.

2. n you add a LibraryBuilder resource to a project you can create an alias to it when loading the library, or pick an alias and load the corresponding library.

3.  LibraryBuilder resource allows you to share resources you have defined in a project with other project developers. This allows you to create shareable resources once, then allow other project developers to use them in their projects

File Aliases

         

   In tibco online training you can have the topic called creating a File Alias (Through Preferences)

       The following screen shots help in understanding in creating file aliases.

       1. Open the designer and go to Preferences in the Edit tab.

2. Go to the File Aliases tab and click on the new tab to add an alias.

3. Add an alias name and browse the file path for the location of libraries (Eg: -    C:\Projects\Lib) and select the required library.

4. The alias is added, click OK.

 The alias to the library is added to the project.

Adding the library to the repo

             The library can be added to the repo in the following way-

1.    Select the top-most folder which is the project name. In the right panel, three tabs appear.

            2. In the “Design Time Libraries” tab, click on the ‘+’ icon and browse for the library.

3. The Alias is added to the designer as seen below.

Creating File Alias from Resource

To create a file alias from resource,

1.    Open the palettes window.

2.    Select the AliasLibrary palette from the general palettes.

·         In the configuration tab add the name and the description as required.

·         In the aliases tab, use the ‘+’ to browse the aliases, the second button to select a previously defined Alias entry to add to the library and the bin button to delete any added aliases.

Resources that reference an AliasLibrary as above, will package all the referenced files when their enterprise archive file is built. Because AliasLibraries reference files via a reference, it must be ensured that the machine where the enterprise archive file is generated can access all externally referenced files.

                    The resources added in the library are grayed out because they cannot be modified. AliasLibrary resource is crucial for resources that depend on external files, such as the Java Activity in TIBCO Business Works. Resources in your project can reference aliases in the AliasLibrary to resolve external file dependencies that they may have at runtime or debug time.

TIBCO Businessworks - Library builder

INTRODUCTION

                         This document discusses about using tibco library and also creating projects using templates in Tibco. Tibco libraries can be designed, included into projects and used across projects. An existing design of project can be reused using the template. This document throws light on all these aspects.

1.    LIBRARY BUILDER IN TIBCO

     What Are Design Time Libraries?

     The design-time support architecture lets developers build libraries that are used across in many projects.

     For example, if there exists a schema which has a standard format. The same schema is used by two projects. Instead of creating the schema in both the projects, a common library is built which includes the schema. Once the library is loaded into the project the schema is available in the project.

     Libraries in Tibco can be created using the library builder.

LibraryBuilder: The LibraryBuilder resource allows you to build a design-time library that includes resources defined in one project that can be shared with other projects.

   In tibco, A LibraryBuilder resource is the basis for a design-time library.

 The LibraryBuilder resource allows sharing resources that have been defined in a project with other project developers. This helps create shareable resources once, and then allow other project developers to use them in their projects.

For example, Rendezvous resources, JMS resources, schemas, and process definition libraries can be part of a design-time.

As library is a shared resource, many project developers might change or update the library to suit their requirements. Hence a Revision Control System is maintained to get the updates that are done in the library. Since the same library can be used by many projects and many people, it is advisable to make minimum changes so that reloading the library is not done frequently.

2.    CREATING A LIBRARY

1. Open the designer and from the palettes select the LibraryBuilder as shown.

2. The Library Builder icon is added.

1.    In the configuration tab, provide the name of the library, the description if any, and the location where the library should be built in your system. The version number is updated automatically. Every time the library is updated the version number gets incremented.

3. In the resources tab, add the resources which will be a part of the library.

E.g.:- Schemas, data formats as shown in the figure.

In the following screenshot, there exist two resources. An Employee Schema and a EmployeeFileDataFormat that need to be added to the library. Browse for them and say OK. The resources are added to the library.

4. Say apply and then a Build Library. The library is created successfully in the path mentioned.

Using and Creation of FILE ALIAS -->

TIBCO Hawk Introduction

Overview of TIBCO components

2.1 Overview of TIBCO HAWK

TIB/Hawk Display is an application for viewing and managing TIB/Hawk objects on a network. You use TIB/Hawk Display to discover TIB/Hawk Agents that are running, and to create configuration objects such as rules and schedules that can be stored locally or on the network. TIB/Hawk Display also allows you to communicate with the microagents that respond to instructions or rules on each agent machine.

While monitoring or performing management tasks, TIB/Hawk Display communicates with TIB/Hawk Agents on your network. A TIB/Hawk Agent receives the alerts and uses a microagent to do the work.

Like other TIB/Hawk product components, TIB/Hawk Display is location-independent. One or more instances of the application can run on any machine on your network, and each can show the same view of objects and events. TIB/Hawk Display is also platform-independent, so an instance running on one platform can monitor the events on any other platform supported by TIB/Hawk.

2.2 TIB/HAWK Agents and Microagents

TIB/HAWK agent is a process that monitors activity on a particular machine by processing loaded rulebases. They send regular messages that broadcast their identity and active state. The TIB/Hawk Display application listens for TIB/Rendezvous messages from agents and maps the agents it has detected.

The agent makes use of the managed objects on its local machine using microagents. Microagents represent managed objects such as networks or applications. Each microagent consists of a set of methods to the agent that the agent uses to collect information and take action. A set of default microagents is included when you install TIB/Hawk software. These lists of microagents vary depending on the operating system and some standard microagents get installed in every platform.

2.3 Rulebases

A rulebase is a collection of rules that contain management logic. Several default rulebases get installed with TIB/Hawk software for general monitoring activities.

A rulebase can be loaded on a single agent, on a group of agents, or on every agent in the network. These rules monitor different parameters of an operation system and perform the tasks. The rules in a rulebase should be related to make the administration simpler. A particular application can be monitored by multiple rules in a rulebase each one issuing different alerts based on the test condition.     

3. TIB/HAWK Display

When you start TIB/HAWK display, the display would be in icon view in which the containers are displayed in standard icons. Then the network nodes are arranged in a tree of containers. By clicking the container in the left pane displays the items based on the subnet or location whichever we choose which can be done in preferences options in the right pane. When you start the HAWK display the agents container is empty initially which keeps discovering till all the nodes are found. Both the icons for the agents and discovered are green in color initially. You can have rulebases also in the containers display in the left pane. The repositories can also be included if we are maintaining them in our network. The color of the agents, discovered and rulebases change based on the alert messages or the heartbeat of the agents.

The icon color also changes based on the alerts found in each of the agent. By default an icon can have six different colors each color stating different meaning.

Default Color	Alert level meaning
Purple	The agent was discovered but currently no heartbeat message is being received. The lack of response could mean the agent is not running, the agent machine is down, or a network communication problem exists.
Red	At least one high-level alert is active.
Orange	At least one medium-level alert is active.
Yellow	At least one low-level alert is active.
Cyan	The agent is recovering. At least one alert was active within the last 30 minutes (default), but any active alerts were recently cleared or suspended.
Green	No alerts are in effect.

These alert level colors can also be changed in the Preferences dialog. Please refer TIBCO documentation for TIBCO HAWK to get the detailed explanation on how to change the preferences.

Each container icon is split horizontally into two equal sections. The upper section represents all the agents in the container, and is always in a single color. This color reflects the highest level of alert found on any agent. The lower section shows the distribution of each alert level on the network.

4.  Viewing Alert Messages

Alerts are messages an agent sends to TIB/Hawk Display when a specified test condition occurs. Alerts initiate from rulebases that enforce your monitoring logic. In TIB/HawkDisplay, the colors of each agent and container icon will show alert levels, and the Alert Display window shows alert details for a particular agent or all agents.

To view alert messages for an agent:

1. Arrange TIB/HawkDisplay so that the agent to view alerts for appears on the right.

2. Right-click on the agent icon and select “Show Alerts” from the menu.

The Alert Display window displays messages for the selected agent as below:

The Alert Display shows alert and notification messages. When a test with an Alert or some notifying action becomes true, TIB/Hawk Display receives the message unless advanced options delay it.

Each line in the Alert Display represents a single message published by a TIB/Hawk Agent. However, a single condition can generate multiple alert messages and other actions, depending on how the rule is designed in the rulebase.

To see the active alerts for which the action needs to be taken yet Active alerts radio button needs to be checked. To see the detailed information about any alert, you need to double click on any alert. After checking the alert detail, Done button needs to be clicked.

5.  Suspending Alert Messages

An alert message can be temporarily cleared manually by suspending an alert message to prevent it from interfering with other monitoring tasks. This suspension can be done if the alert is continuously interrupting other monitoring tasks and if the problem is being resolved. You need to provide the reason for suspending an alert which will be visible to everyone who is using the HAWK display.

To suspend an alert:

1.    Open the Alert Detail dialog by double-clicking the alert to suspend.

2.    Click the “Suspend Alert” button.

3.    Specify a suspension interval by selecting a value from the dropdown list or typing a different value. The default value is 60 minutes.

4.    Type a reason for suspension to communicate to other users in the Alert Detail dialog.

5.    Click “OK” button.

6. Clearing AlertMessages

Alerts are cleared when the alert condition, as defined by the rulebase, does not exist anymore. Alerts generated by tests on synchronous data sources, which deliver data at fixed intervals, are cleared by default at the first test repetition when the condition no longer holds. Alerts generated by tests on asynchronous data sources, which deliver data when it becomes available, are cleared by default when the test does not evaluate to true for 15 minutes. You can modify this default behavior using advanced test and action properties in the rule.