This is the second part of the blog on Basic Monitoring and Administration for the Integration Developer. The first one can be accessed here.
In this blog, we shall go through a check-list of Post-Deployment activities. Deploying an integration flow is a very common activity for the developer. And checking whether the integration flow has been deployed successfully is a good debugging practice. In most cases you would have a successful deployment, but in cases of failure or doubt – the procedure discussed in the blog helps you get to the root cause of the problem.
Part 2: Checking the status of Integration Deployments in HCI-PI
In the Eclipse Integration tool set, this is the sequence of steps that you must follow:
After you deploy the integration flow to the tenant –
1. Check the Console Output
In the Console Output, you must get a Task ID for the deployment. That shows that the integration flow has been successfully sent to the Tenant Management Node (TMN) and a task has been registered. Using the ID, the task status can also be checked in the Task Logs (Note, this step is not necessary). When you deploy an integration flow, the consistency checks are executed first and its results shown in the Console. That is the output after the text “Project:”
2. Check the Deployed Artifacts tab
The second step that you must do is check the Deployed Artifacts tab. The tab is available as part of Message Monitoring view and lists all the artifacts deployed on the particular tenant.
Check the Date on deployment and the User. Once you have deployed the integration flow, the time of deployment should be verified. The time would match the one from where you are deploying the integration flow.
3. Check the Component Monitoring Tool
The third step is to check the Component Monitoring view. The view shows the status of the deployed integration flow. If the integration engine could not start the integration flow, then you can right click-and check for the errors. A detailed error report would be available in the Tail Logs view; more information on this error scenario is provided in the third part of this blog.
Causes for common deployment issues:
- Consistency check for the integration flow has failed. If the consistency check has errors, then the tool shall not deploy the integration flow to the tenant. This can be checked in the Console Output.
- Connectivity to tenant is not working. The connection to the tenant would have timed out or got terminated. Do a connection refresh in the Node Explorer to establish the connection and then deploy the integration flow again.
- Configuration issues in the integration flow. Runtime configuration issues could also lead to non-started integration flows – examples include Keystore not deployed to the tenant, incorrect key alias, and so on. These errors can be viewed in the tail log. An example is provided in the 3rd part of the blog.
That is all! A simple procedure to check the deployment trail of your integration flow.