Tibco BusinessWorks and EMS discovery

Discovery can find Tibco ActiveMatrix BusinessWorks and Enterprise Message Service (EMS). Service Mapping can discover application services containing Tibco BusinessWorks, Enterprise Message Service (EMS), and their components.

Data collected by Discovery for Tibco ActiveMatrix BusinessWorks

The following data is collected in the ActiveMatrix Business Works [cmdb_ci_appl_tibco_matrix] table.

Table and field	Description
ActiveMatrix Business Works [cmdb_ci_appl_tibco_matrix]
Name [name]	The attributes of ActiveMatrix BusinessWorks configuration item.
Version [version]
TCP port(s) [tcp_port]
Class [sys_class_name]
Fully qualified domain name [fqdn]
IP Address [ip_address]
Configuration directory [config_directory]
Configuration file [config_file]
Installation directory [install_directory]
Project [project]

Data collected by Discovery for Tibco Enterprise Message Service

By default, Discovery uses the Enterprise Message Service pattern to discover Tibco Enterprise Message Service.

For a list of privileged commands that you need for Discovery and Service Mapping, see Service Mapping commands requiring a privileged user. This list includes commands that require elevated rights to discover and map Unix-based hosts in your organization.

注:

For information on Probe to Pattern migration see the knowledge article KB0694477.

Table and field	Field Name
Tibco Enterprise Message Services [cmdb_ci_appl_tibco_message]
Name [name]	Attributes of the Tibco Enterprise Message Services configuration item.
Version [version]
Class [sys_class_name]
Fully qualified domain name [fqdn]
IP Address [ip_address]
Installation directory [install_directory]
TCP port(s) [tcp_port]
Configuration directory [config_directory]
Configuration file [config_file]
Installation directory [install_directory]

Data collected by Service Mapping

Service Mapping can discover application services that contain Tibco ActiveMatrix BusinessWorks (including BusinessWorks Process), Tibco Enterprise Message Service (EMS), Tibco Enterprise Message Service (EMS) Queue.

Map application services containing Tibco BusinessWorks and EMS

Map an application service containing Tibco BusinessWorks and Enterprise Message Service (EMS) and verify that Service Mapping discovered all Tibco components correctly.

始める前に

• (If hosted on Unix) Configure applicative credentials for the Tibco EMS.
• (If hosted on a Windows server) On the ServiceNow AI Platform, configure Windows credentials.
• (If hosted on a Unix server) On the ServiceNow AI Platform, configure SSH credentials.
• (Optional) For discovering using the WinRM protocol, see Configure WinRM trusted hosts on MID Server.

Role required: service_mapping_admin

手順

1. Create a service instance.
   1. Navigate to All > Service Mapping > Service Instances.
   2. Click New.
      The Discoverable by Service Mapping option is selected by default.
   3. In the Name field, enter a descriptive name for the service instance.
2. Define the entry point for this application service:
   1. Select the Other application tile.
      The Discoverable by Service Mapping option is selected by default.
   2. From the Select Entry Point Type list, select HTTP(s) Endpoint, TCP Endpoint, Tibco BW Endpoint.
   3. Define the entry point as follows:
      • The URL to the process that correlates to the Tibco BusinessWorks Project, for example, http://10.xx.xx.xx:6710/GetMemberActivitiy/Processes/ServiceGetMemberActivitiy.service .
      • (Optional) The hostname on which the BusinessWorks Project runs as a service.
   4. Click Add.
   5. Click Save.
3. Click Additional Info on the left and clear the Traffic based discovery check box.
4. Click Update.
5. Verify that the mapping result is satisfactory:
   1. Click View Map and wait until the mapping is complete.
      It may take a few minutes.
   2. Review the application service map and make sure that the service layout is as in the following examples.

      
      
      

   In addition, verify that the BusinessWorks CIs are inclusions each of which contain a BusinesWorks process. Also, verify that the EMS CIs are inclusions containing EMS Queues.

   
   
   

If the mapping result is not as you expected, perform basic troubleshooting.

Symptom	Cause	Solution
(Only for deployments hosting BusinessWorks on a Unix server) The service instance map shows the BusinessWorks CI without an inclusion of the BusinessWorks process. The discovery log shows the error message stating that the user does not have sufficient credentials.	Service Mapping failed to run the TibcoFilesParser.ksh command.	Make sure that you provided a user with elevated rights as described in Service Mapping commands not requiring a privileged user.
Service Mapping failed to discover the outgoing connections of EMS to the EMS process.	Service Mapping failed to run the tibemsadmin command.	Make sure that you provided a user with elevated rights as described in Service Mapping commands not requiring a privileged user.