Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 4 System Settings : Visibility

Visibility
Visibility settings allow you to integrate TIBCO BusinessConnect with several other TIBCO applications: tibbr, TIBCO BusinessEvents, and TIBCO Hawk. This integration provides near real-time visibility of the overall TIBCO BusinessConnect implementation. For more conceptual information about these TIBCO BusinessConnect visibility, see TIBCO BusinessConnect Concepts, TIBCO BusinessConnect Architecture.
Configuring tibbr Settings
TIBCO BusinessConnect can post error messages to a specified tibbr subject. You can define one global tibbr subject to which TIBCO BusinessConnect will post error messages generated by transactions involving any installed and enabled protocol for all partners. You can also define a tibbr subject for error messages generated by each trading partner. For more information on how to configure error message posting for trading partners, see Visibility Tab for Partners.
All tibbr subjects created by TIBCO BusinessConnect are public. If TIBCO BusinessConnect posts to a private subject that already exists on the tibbr host, an error message in the trace log will be generated.
To post TIBCO BusinessConnect error messages to tibbr on a global level, follow the steps below.
1.
Go to BusinessConnect > System Settings > Visibility > tibbr.

The tibbr Settings dialog is displayed.
2.
Note: To enable error posting for trading partners, see Configuring Participant Visibility Settings for tibbr.
The hostname of the server hosting tibbr. The hostname must include the protocol prefix, either http:// or https://. If the hostname is secure (that is, preceded by https), you must provide a tibbr certificate, as explained below.
Example: https://acme.tibbr.com
If the tibbr instance is a secure one (that is, if the hostname you entered was preceded by https), you must provide a certificate. If the tibbr instance is not a secure one (that is, if the hostname is preceded by http), select None from the list (this is the default).
1.
Expand BusinessConnect > System Settings > Certificate Store.
2.
In the Certificate Store dialog, click the Server Identities & Certificates > Fetch Third Party Server Certificate tab.
5.
Example: bcadmin
The prefix of all the error messages posted to tibbr. The default value is bc. You can also define a subject prefix for each trading partner.
Configuring TIBCO BusinessEvents Settings
To enable TIBCO BusinessConnect to send messages to TIBCO BusinessEvents, follow these steps:
1.
Expand BusinessConnect > System Settings > Visibility > BusinessEvents.

The BE Settings dialog is displayed.
2.
Check the Enable BE Integration check box.
TIBCO BusinessConnect can send six types of messages to TIBCO BusinessEvents: Initiator Request, Initiator Response, Responder Request, Responder Response, Inbound Message, and Error Advisory. These message types are listed in the Message Types area of the BE Settings dialog.
Figure 17 BE Setting
You must enable each message type that you want sent to TIBCO BusinessEvents. You must also specify the destination name and JMS channel type (that is, Topic or Queue) for each message type.
The destination name serves as the TIBCO Rendezvous subject name or the JMS topic or queue name, depending on which private process transport type you selected in Application Management > BusinessConnect > Configuration > BusinessConnect > Private Process Configuration. See TIBCO BusinessConnect Interior Server Administration, Private Process Configuration for more information about private process configuration.
To make changes to any of these settings:
1.
The Edit Entry dialog is displayed.
Figure 18 Message Type Configuration
2.
Enter the destination name you want to use in the Destination name field. This field is pre-populated according to the following form:
AX.BC.BE.installation_name.MESSAGE.TYPE
3.
Check the Enabled check box to enable messages of this type to be sent to TIBCO BusinessEvents.
4.
Select either Queue or Topic from the JMS Channel Type list.
Configuring Application Monitoring and Management Settings
The health and statistical information of TIBCO BusinessConnect Interior Server Instances and Gateway Instances can be exposed to TIBCO Hawk. The health and statistical information of Interior Server Instances and Gateway Instances are also available in TIBCO Administrator through TIBCO Hawk.
TIBCO BusinessConnect Interior Server Instances play the bridge role between the Gateway Instances and TIBCO Hawk Agent. TIBCO Hawk Agent and Display do not have to run within the same DMZ or subnet where the Gateway Instances run.
Rulebases can be used to manage Gateway Instances as other applications.
You have two deployment modes for TIBCO Hawk, one is installing and configuring on one local machine, and the other is using a remote machine to monitor and manage TIBCO BusinessConnect Interior Server Instances and Gateway Instances of your local machine. See Deployment Modes for Application Monitoring and Management.
After installing TIBCO Hawk and TIBCO Hawk JMX Plug-in, the following configuration tasks are required for enabling application monitoring and management:
1. Selecting an internal user that TIBCO Hawk uses for authentication.
See Selecting an Internal User for Application Monitoring and Management for more details.
2.
See Enabling Application Monitoring and Management for Service Instances for more details.
3.
You must define an MBean Server section for each Interior Server Instance you want to monitor. See Editing the JMX Configuration File for Application Monitoring and Management for more details.
4.
See Configuring TIBCO Hawk for Application Monitoring and Management on Windows and Configuring TIBCO Hawk for Application Monitoring and Management on UNIX for more details.
After performing the preceding tasks, see Monitoring and Management with TIBCO Hawk for how to track the status of TIBCO BusinessConnect Interior Server Instances and Gateway Instances.
The rulebases have to be set for monitoring. See Application Monitoring and Management by Processing Rulebases for more details. For more information on how to build a rule, see Building a Rule.
Deployment Modes for Application Monitoring and Management
You have two deployment modes for TIBCO Hawk, one is installing and configuring on one local machine, and the other is using a remote machine to monitor and manage TIBCO BusinessConnect Interior Server Instances and Gateway Instances of your local machine.
To install the required software, see Software Requirements in TIBCO BusinessConnect Installation and Configuration.
To configure TIBCO Hawk for application monitoring and management, you have to perform all the tasks on page 103.
This deployment mode is suitable for the local machine that TIBCO BusinessConnect is installed, but the full version of TIBCO Hawk and TIBCO Hawk JMX Plug-in are not installed. You can set a remote machine to install the full version of TIBCO Hawk and TIBCO Hawk JMX Plug-in.
To install the required software on a remote machine, you have to install TIBCO Rendezvous, TIBCO Runtime Agent, TIBCO Administrator, full version of TIBCO Hawk, and then install TIBCO Hawk JMX Plug-in. You do not need to install TIBCO Hawk Agent component, because this component is contained in TIBCO Runtime Agent.
To configure TIBCO Hawk for application monitoring and management, you have to perform all the tasks on page 103.
Selecting an Internal User for Application Monitoring and Management
1.
Go to BusinessConnect > System Settings > Visibility > Application Monitoring & Management.
2.
Select a user from the Administrator User list.
The TIBCO Hawk Agent authenticates against this user to connect to TIBCO BusinessConnect to monitor and manage the service instances.
Internal users can be viewed and created by going to BusinessConnect > User Management > Users and clicking the Internal tab. The credentials created for this user are used when editing the JMX configuration, as described in Editing the JMX Configuration File for Application Monitoring and Management.
3.
Click Save.
See Managing Users with TIBCO BusinessConnect User Management for more information.
Enabling Application Monitoring and Management for Service Instances
You must enable application monitoring and management in each Interior Server Instance you want to monitor and manage:
1.
Go to Application Management > BusinessConnect > Configuration.
2.
3.
4.
In the Application Monitoring & Management area, select the Enable check box.
5.
In the Monitoring Port field, enter the port number to be used by TIBCO Hawk. The default value is 11010.
6.
Click Save.
7.
Editing the JMX Configuration File for Application Monitoring and Management
The user name and password of the Administrator user selected at step 2 in Selecting an Internal User for Application Monitoring and Management must also be specified in the MBean Server section of the JMX configuration file. To edit the file, follow these steps:
1.
Edit the JMXPluginConfig.xml file in the TIBCO_HOME\hawk\version\plugin directory.
2.
In the MBeanServerList section of the JMXPluginConfig.xml file, add an MBeanServer entry and define values for each parameter. The values should correspond to the Interior Server Instance you want to monitor. Each of these instances must be enabled in TIBCO Administrator GUI, as described in Enabling Application Monitoring and Management for Service Instances.

<MBeanServer name="BusinessConnect InteriorServer1" type="JSR160">
  <JMXClassPath>D:/tibco/tibcojre64/1.8.0/lib/rt.jar</JMXClassPath>
     <ParameterList>
       <param name = "JMXServiceURL" value = "service:jmx:rmi:///jndi/rmi://127.0.0.1:11010/jmxrmi"/>
        <!-- login/password to connect to the connector server. -->
        <param name = "login" value = "username"/>
        <param name = "password" value = "secure_password"/>
     </ParameterList>
</MBeanServer>

The value for the JMXServiceURL parameter is the service instance you want to monitor. The IP address can be the same as the local server or another, remote server. In either case, the port number must be the same one entered in step 5 of Enabling Application Monitoring and Management for Service Instances.
The values for the login and password parameters must be same as those defined for the Internal User selected in step 2 of Selecting an Internal User for Application Monitoring and Management. If a user and password are not defined, application monitoring and management are disabled.
You must create an MBeanServer entry for each Interior Server Instance. Different MBeanServer entry has different names, but the same type. For example, the JMXClassPath parameter is TIBCO_HOME/tibcojre64/version/lib/rt.jar. Each additional section must be under the same MBeanServerList.
Configuring TIBCO Hawk for Application Monitoring and Management on Windows
Using TIBCO Hawk for application monitoring and management on Windows requires some additional configuration. After editing the JMX configuration file, perform the following steps:
1.
Run tibhawkconfig.exe.
2.
3.
Go to the TIBCO_HOME/tra/domain/domain_name directory.
4.
In the hawkagent.cfg file, ensure that the property hma_plugin_dir is defined as the TIBCO_HOME/hawk/version/plugin directory.
For more detailed information about configuring TIBCO Hawk, see the appropriate TIBCO Hawk documentation.
Configuring TIBCO Hawk for Application Monitoring and Management on UNIX
Using TIBCO Hawk for application monitoring and management on UNIX requires some additional configuration. After editing the JMX configuration file, perform the following steps:
1.
Ensure that the hawkagent_domain_name.tra file correctly references the hawkagent.cfg file. Both of these files are located in the TIBCO_HOME/tra/domain/domain_name directory.
2.
Ensure that the following properties are correctly defined in the hawkagent.cfg file. For example, the auto_config_dir property should be defined as the TIBCO_HOME/hawk/version/autoconfig directory.
The properties that must be defined correctly are:
domain   Your domain name.
agent_name   Your computer name.
rvd_session   Your TIBCO Rendezvous parameters for TIBCO Hawk. The default value is 7474;tcp:7474. If you are going to use the TIBCO Hawk display to add rulebases for TIBCO BusinessConnect, see step 3.
hma_plugin_dir   Your TIBCO Hawk plugin directory. For example, TIBCO_HOME/hawk/version/plugin.
auto_config_dir   Your auto configuration directory. For example, TIBCO_HOME/hawk/version/autoconfig.
3.
If you are going to use the TIBCO Hawk display to add rulebases for TIBCO BusinessConnect, configure the rvd_session property in the hawkdisplay.cfg file in the TIBCO_HOME/hawk/version/bin directory.
For more detailed information about configuring TIBCO Hawk, see the appropriate TIBCO Hawk documentation.
Monitoring and Management with TIBCO Hawk
Log in to TIBCO Administrator, All Alerts, Hawk Console, and Monitoring Console is under Monitoring Management. See TIBCO Hawk Plug-in For TIBCO Administrator for more information.
The rulebases are need to be set for monitoring, see Application Monitoring and Management by Processing Rulebases for more details.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved