Troubleshooting issues with the high-level integration language

The best option when troubleshooting an issue with high-level integration language flows is to examine the BigInsights logging information. It's important to know that the Social MDM Matching application does not generate its own logging information. Instead, when a failure occurs within BigInsights, the information is sent to a logging directory at the 50060 port of the BigInsights instance. (This assumes that the instance is using the default port for logging.) If you find that a job has failed, go to the logging directory and find the last log available there. Search for the workflow ID / application ID within the log.

The default flows have been tested and they are not likely to cause issues. However, if you make any customizations, you might see issues with the Jaql code. For example, the logging information might indicate that the code is missing a required attribute. The Jaql error is specific to the failed step of the flow and it specifies which statement caused the problem. Modify the high-level integration language script to correct the error. For example, you might need to adjust the entity attributes. After you make changes, regenerate the Jaql scripts.

You can also encounter issues if your rules are generating too many matches. Generating too many matches can cause issues within your matching results. Generating too many or too few matches does not cause a failure. Begin by observing the results of the flow. To find the rule that is causing the issue, inspect the intermediate files that are generated by the matching steps, for example er.hil or pmeSocialRuleNN. Look at the rule source to determine the specific file name.

Note that if an issue causes a failure within a flow, the whole flow fails and does not complete successfully.