---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management
Release :
- yokohama
ft:locale :
- en-US
ft:publication_title :
- Yokohama IT Operations Management
ft:clusterId :
- itom
bundleId :
- itom
workflow :
- Technology
---
# Tibco BusinessWorks and EMS discovery
# Tibco BusinessWorks and EMS discovery {#ariaid-title1}
* Release version: Yokohama
*
* Updated January 30, 2025
*
*  3 minutes to read
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 {#mapping-services-tibco__section_ghj_5dl_flb}
The following data is collected in the ActiveMatrix Business Works
`[cmdb_ci_appl_tibco_matrix]` table.
{#mapping-services-tibco__table_j23_hzl_r2b__entry__2}
| Table and field | Description |
|-|-|
| ActiveMatrix Business Works \[cmdb_ci_appl_tibco_matrix\] ||
| Name \[name\] | The attributes of ActiveMatrix BusinessWorks configuration item. |
| Version \[version\] | The attributes of ActiveMatrix BusinessWorks configuration item. |
| TCP port(s) \[tcp_port\] | The attributes of ActiveMatrix BusinessWorks configuration item. |
| Class \[sys_class_name\] | The attributes of ActiveMatrix BusinessWorks configuration item. |
| Fully qualified domain name \[fqdn\] | The attributes of ActiveMatrix BusinessWorks configuration item. |
| IP Address \[ip_address\] | The attributes of ActiveMatrix BusinessWorks configuration item. |
| Configuration directory \[config_directory\] | The attributes of ActiveMatrix BusinessWorks configuration item. |
| Configuration file \[config_file\] | The attributes of ActiveMatrix BusinessWorks configuration item. |
| Installation directory \[install_directory\] | The attributes of ActiveMatrix BusinessWorks configuration item. |
| Project \[project\] | The attributes of ActiveMatrix BusinessWorks configuration item. |
[ ]
{#mapping-services-tibco__table_j23_hzl_r2b}
## Data collected by Discovery for Tibco Enterprise Message
Service {#mapping-services-tibco__section_tkn_nzl_r2yu}
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](https://servicenow-prod.fluidtopics.net/KmX~uDsV3RoqnUbrW~2SFA "Service Mapping uses commands requiring elevated rights to discover and map Unix-based hosts in your organization. In addition to configuring necessary credentials, configure servers in your organization to allow Service Mapping to run these commands with elevated rights."). This list
includes commands that require elevated rights to discover and map Unix-based hosts in
your organization.
Note:
For information on Probe to Pattern migration see the knowledge article [KB0694477](https://support.servicenow.com/kb_view.do?sysparm_article=KB0694477).
{#mapping-services-tibco__table_ukn_nzl_r2b__entry__2}
| 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\] | Attributes of the Tibco Enterprise Message Services configuration item. |
| Class \[sys_class_name\] | Attributes of the Tibco Enterprise Message Services configuration item. |
| Fully qualified domain name \[fqdn\] | Attributes of the Tibco Enterprise Message Services configuration item. |
| IP Address \[ip_address\] | Attributes of the Tibco Enterprise Message Services configuration item. |
| Installation directory \[install_directory\] | Attributes of the Tibco Enterprise Message Services configuration item. |
| TCP port(s) \[tcp_port\] | Attributes of the Tibco Enterprise Message Services configuration item. |
| Configuration directory \[config_directory\] | Attributes of the Tibco Enterprise Message Services configuration item. |
| Configuration file \[config_file\] | Attributes of the Tibco Enterprise Message Services configuration item. |
| Installation directory \[install_directory\] | Attributes of the Tibco Enterprise Message Services configuration item. |
[ ]
{#mapping-services-tibco__table_ukn_nzl_r2b}
## Data collected by Service Mapping {#mapping-services-tibco__section_kd3_x3m_flb}
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 {#ariaid-title2}
Map an application service containing Tibco BusinessWorks and
Enterprise Message Service (EMS) and verify that Service Mapping discovered
all Tibco components correctly.
### Before you begin
* (If hosted on Unix) Configure [applicative credentials](https://www.servicenow.com/docs/access?context=applicative-creds&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) for the Tibco EMS.
* (If hosted on a Windows server) On the ServiceNow AI Platform, configure [Windows credentials](https://www.servicenow.com/docs/access?context=r_WindowsCredentialsForm&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US).
* (If hosted on a Unix server) On the ServiceNow AI Platform, configure [SSH credentials](https://www.servicenow.com/docs/access?context=r_SSHCredentialsForm&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US).
* (Optional) For discovering using the WinRM protocol, see [Configure WinRM trusted hosts on MID Server](https://www.servicenow.com/docs/access?context=enable-winRM-MID-servers&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).
{#map-service-containing-tibco__ul_lqf_dmf_3gb} Role required: service_mapping_admin
### Procedure
1. Create a service instance.
1. Navigate to AllService MappingService 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.
{#map-service-containing-tibco__substeps_fmn_1by_32b}
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.
{#map-service-containing-tibco__ul_fk3_mbz_dfb}
4. Click Add.
5. Click Save.
{#map-service-containing-tibco__substeps_iwl_q1z_dfb}
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.
{#map-service-containing-tibco__substeps_tzh_ycy_32b}
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.
{#map-service-containing-tibco__table_kjv_sdy_32b__entry__3}
| 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](https://servicenow-prod.fluidtopics.net/PWerd39b5nEL~pJPadH4lQ "Most of commands utilized by Service Mapping for discovery and mapping do not require elevated rights."). |
| 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](https://servicenow-prod.fluidtopics.net/PWerd39b5nEL~pJPadH4lQ "Most of commands utilized by Service Mapping for discovery and mapping do not require elevated rights."). |
[ ]
{#map-service-containing-tibco__table_kjv_sdy_32b}
*[\>]: and then