BMC Helix Intelligent Integrations is not displaying the expected Helix Destination and attempting to configure a Source displays the following error: "Something went wrong (render)"

A Helix Destination is required for BMC Helix Intelligent Integrations (BHII) to function correctly. A Source cannot be added if the Helix Destination is not present and attempting to do so results in the "Something went wrong (render)" error being displayed.

This error is often misinterpreted as being a problem with the Source being configured but is unrelated to the Source configuration.. 

Under normal circumstances, a Helix Intelligent Integrations environment will always have a functioning Destination but there have been cases where the Destination is not present - sometimes due to an Empty backup being restored.

These steps will guide the user on how to restore the missing Helix Destination by populating a json file with the required Helix environment information and then performing a restore from the json file.



1. A backup of the configuration can be taken before any changes are made. In this case, the Helix Intelligent Integrations environment is missing the Destination and will likely also have no Sources configured so a backup will have no value.
If prevously-configured Sources are present but the Destination is missing, a backup may be useful to preserve the Source settings in the generated json file for future reference.







2. From the “User Access” -> “Users and keys” -> “Access keys” -> “Add Key” area of the Helix Portal, create an Access Key of type "Access key" (not API key). And make sure the new keys have admin permissions.

https://docs.bmc.com/docs/helixportal/231/setting-up-access-keys-for-programmatic-access-1162691760.html


3. Copy the Access and Secret key to a text file for future reference.



4. Download the template JSON file attached to this knowledge article(KA) and replace the following details in the JSON file:

• host (line 30): FQDN e.g.          
  • "host": "mycompany-or1.onbmc.com",
• tenantId (lines 25 and 47):  Located in two locations in the file e.g.
  •  "tenantId": "1994412345",
• accessSecretKey (line 9): Generated and copied in previous steps e.g. 
  •  "accessSecretKey": "A7vCuGNaWy852CZ9f9Qrnh1sh4oR0OFsJOT1wyzkvsimfTybTf",
• accessKey (line 22): Generated and copied in previous steps e.g
  •  "accessKey": "TRPJOTTQJHQ5V60V22CS0R10SQ0N3J",
• instanceName (line 46) : This will be the reference name which will appear on the Destination. Usually the same value as "host" is used
  • "host": "mycompany-or1.onbmc.com",
• id (line 49): Generate unique GUID from https://www.uuidgenerator.net/version4 e.g.
  •   "id": "0b6f20ad-01d7-4e57-9d94-cb7ef7e8fbe2",

Save the updated json file

5. Navigate to the Intelligent Integration console and restore using the updated json file:





6. The missing Destination should be created. If so, click on the Configure Mediator button on the Destination:



And click on Validate:




7. If Validate fails, check the connection information defined on the Destination and, if necessary, correct from the Intelligent Integrations console


8. If the missing Destination is not created by the Restore in step 5, open a BMC Customer Support case and share the error screenshot from Intelligent Integrations console.