This documentation supports the 23.3 version of BMC Helix Digital Workplace Basic and BMC Helix Digital Workplace Advanced. Icons distinguish capabilities available only for the Advanced and External license levels. For more information, see License types and features.To view an earlier version, select the version from the Product version menu.

Troubleshooting Connectors in BMC Helix Digital Workplace Catalog


Service connectors connect your catalog to external systems. BMC Helix Digital Workplace Catalog integrates with external fulfilment systems through service connectors, which pass the information from a service request to an external system.


Consult the following topics for information about troubleshooting the BMC Helix Digital Workplace products and components, such as problems you might encounter during installation, configuration, and use of the product, as well as error messages and how to enable logs and collect diagnostic information.

Logs required to troubleshoot issues with BMC Helix Digital Workplace connectors

Depending on your version of BMC Helix Digital Workplace, either refer to the bundle.log (in TRACE/DEBUG mode) or the myit-sb.log (in TRACE/DEBUG mode) and server.log files.

See the following topics to enable and troubleshoot the logs:


Resolutions for common issues

Issues/Symptoms

Steps

Reference

Unable to connect to the Flexera Appbroker by using Flexera Connector

Potential cause can be that Flexera Appbroker is not correctly configured in Flexera Connector and Flexera Authentication Method.

Make sure that Kerberos authentication is turned off in Flexera. The Flexera connector does not support Kerberos. Only NTLM authentication is supported.

Note: Before deploying the BMC Helix Digital Workplace Catalog with the Flexera connector, turn off Negotiate authentication (only leave NTLM authentication) in Internet Information Services (IIS) on the Flexera server.

 Follow the steps below to configure:

  1. Go to http://dwpcatalogserver:port/myitsbe/connections.
  2. Create a new Flexera Connection by clicking New Connection.
    1.PNG
  3. Configure the Flexera Connector by using the URL format, https://schema/hostname/port.
     → For example, https://appbroker.customerdomain.com 2.PNG

     

  4. Click Save and Test Connection.

If there is still an issue, enable wire logs on the BMC Helix Digital Workplace CatalogServer/POD to see what traffic is being sent to Flexera and make sure that the URL is getting built correctly.

  1. Add the following to the logback_server.xml file (at the end):
    <logger name="org.apache.http.wire" level="DEBUG">

             <appender-ref ref="BUNDLE"/>

          </logger

  2. Save the file.
  3. Restart the BMC Helix Digital Workplace Catalog Service.
  4. Get the bundle.log/myit-sb.log file while configuring the Flexera Connector.
  5.  Contact BMC Support by raising a Support Case and send the log file for reference.

See Flexera Connector for the connector details.

KA: 000259304

AD Connector CONNECTION_FAILURE occurs when connecting to the Kaazing Gateway


When connecting to the AD Connector from BMC Helix Digital Workplace Catalog using Kaazing Gateway, the following error is observed in the bundle logs:

checkHealth call on connection Active Directory / Active Directory

 response payload: {"status":"CONNECTION_FAILURE","message":null,"messages":[{"message":"Failed to connect to ml-kaaztool-01 server via LDAP","severity":"ERROR"}]}

Use the following steps to confirm the domain configuration in the connection settings::

  1. Open the AD Connector in BMC Helix Digital Workplace Catalog.
  2. Check the Username and User Domain in the Active Directory Connector settings in BMC Helix Digital Workplace Catalog.
    The User Domain should be empty and the Username should contain the User Domain.

The AD Server does not accept domain\user  format, format the user name as username@domain.

For example: test_bmc@dev.local


Unable to set up the TrueSight Orchestration Platform Connector for BMC Helix Digital Workplace Catalog -Error: Connection Failed


You receive the following error even though you are able to access the URL using the curl command from the same BMC Helix Digital Workplace Catalog server. 

-----------
DEBUG com.bmc.myservice.connect.commons.rest.EnabledPostRedirectStrategy Redirect requested to location 
DEBUG com.bmc.myservice.connect.commons.rest.RestRequestExecutor POST 
ERROR com.bmc.myservice.common.util.HttpUtils java.net.SocketTimeoutException: Read timed out 
javax.ws.rs.ProcessingException: java.net.SocketTimeoutException: Read timed out 
at org.glassfish.jersey.client.internal.HttpUrlConnector.apply(HttpUrlConnector.java:287) ~[na:na] 
at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:255) ~[bundlefile:na] 
at org.glassfish.jersey.client.JerseyInvocation$1.call(JerseyInvocation.java:684) ~[bundlefile:na] 
at org.glassfish.jersey.client.JerseyInvocation$1.call(JerseyInvocation.java:681) ~[bundlefile:na] 
at org.glassfish.jersey.internal.Errors.process(Errors.java:315) [bundlefile:na] 
--------------

The cause can be an incorrect TrueSight Orchestration Platform URL Configuration. 

Correct the TrueSight Orchestration Platform URL and make sure the URL stops at the port number. 

For example: If the URL is http://baoservername:38080/baocdp/orca, remove /baocdp/orca and ensure that the URL is only until the port number http;//baoservername:38080

For more information, see BAO connector.

BMC Helix ITSM Connector fails with error: Incorrect user name or password.

Details: 

When you test the BMC Helix ITSM Connector, it fails with error “Incorrect user name or password”.


The cause is the Connector user. For example, the "hannah_admin" user password has been changed in BMC Helix ITSM CTM:People and in the User form that caused the error in BMC Helix ITSM Connector.

To resolve the issue, perform the following steps: 

  • Reset the password in BMC Helix Digital Workplace Catalog Connector Configuration as well to fix the error.
  • Ensure the configuration in BMC Helix ITSM forms (CTM:People/User) is  consistent with BMC Helix ITSM Connector Configuration in BMC Helix Digital Workplace Catalog.

Additionally, if the connector user password was changed,  it should also be updated in the forms that follow, to make sure the  BMC Helix Digital Workplace Catalog and BMC Helix ITSM integration works properly:

  • On the BMC Helix ITSM side:
    Update the password for the connector user in following forms (if the same user is used):

    • SB:LocalApprovalConfiguration
    • SB:RemoteApprovalConfiguratio
  • On the BMC Helix Digital Workplace side (if same user is configured in enhanced catalog; if not,  you can ignore this):
    BMC Helix Digital Workplace  Admin Console > BMC Helix Digital Workplace Enhanced Catalog.
  • On the BMC Helix Digital Workplace Catalog side:
    • For BMC Helix Digital Workplace version 20.02:
      Log in to BMC Helix Digital Workplace Catalog AR with BMC Helix Digital Workplace Catalog Administrator credentials and update the Connector User Password in "User" form (AR System Administrator > Applications > Users) 
    • For BMC Helix Digital Workplace version  20.08:
      Log in to BMC Helix Digital Workplace Catalog with BMC Helix Digital Workplace Catalog Administrator credentials.
      Open BMC Helix Innovation Studio > Administration > Foundation Data > Manage People > Search Person login id > Update Password.

For more information, see Helix-ITSM-connector.


(Version 23.3.02 and later) Decentralization of the connection health checks

Before version 23.3.02, BMC Helix Digital Workplace service requests fulfilled in BMC Helix ITSM could fail due to connection errors. For example, users might receive the following error message for a failed service request:

IllegalState: cannot open client on connection 1 / Remedy.

This failure stemmed from centralized connection health checks being conducted on a single main node (the escalation node) in a multinode environment. If the checks failed on the escalation node, all other nodes were automatically impacted. As a result, the execution of all service requests with the connector activities was blocked on all nodes. 

To address this issue, BMC Helix Digital Workplace has introduced the decentralization of connection health checks. Starting with version 23.3.02, each node runs and stores health checks for all connectors independently. The nodes don't save the health check statuses to the database and instead use those statuses locally. As a result, even if connection health checks fail on one of the nodes, other nodes will continue operating, and the request execution will not be interrupted on these nodes. 

BMC Helix Innovation Studio administrators can modify the intervals and the next execution time of the decentralized connection health checks. Also, they can access information about changes to the connectors. 

To modify the connection health check settings

As a BMC Helix Innovation Studio administrator, perform the following steps: 

  1. Log in to BMC Helix Innovation Studio and navigate to the Workspace tab. 
  2. Select the Digital Workplace Catalog application. 
  3. On the Records tab, select the BackgroundJob record and click Edit data
  4. Select a record with the Summary value set to ConnectionStatusUpdater and the JobStatus value set to CUSTOMIZED, and then click Edit.
    BackgroundJob.png
  1. In the IntervalSeconds field, set the frequency of health checks in seconds. 
  2. In the NextExecutionTime field, select a future date and time for the next execution if you want to postpone the health check.
    Settings_record.png
  1. Click Save

To access information about connector changes

As a BMC Helix Innovation Studio administrator, you can find connection details and information about changes occurring to connectors in the SbeConnector records, by performing the following steps:

  1. Log in to BMC Helix Innovation Studio and navigate to the Workspace tab. 
  2. Select the Digital Workplace Catalog application. 
  3. On the Records tab, select the SbeConnector record and click Edit data
  4. To view connection details, select the required record and click Edit.

Important

The SbeConnector records don't store information about connection statuses because the nodes don't save the health check statuses to the database and instead use those statuses locally.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*