Troubleshooting Connectors in BMC Helix Digital Workplace Catalog

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.
   
   

3. Configure the Flexera Connector by using the URL format, https://schema/hostname/port.
    → For example, https://appbroker.customerdomain.com

    

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] 
--------------

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

You receive a Tomcat error 500 in BMC Helix Digital Workplace
 while opening CLM Services even after successfully configuring the CLM Connector via BMC Helix Digital Workplace Catalog.

Potential cause is related to Certificates.

KA:  000314139

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”.

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.