Incorrect Flow Configuration
This document will use the actual root cause analysis information to make a generic view that can be used if you run into the same or similar problem. Finally, the document will describe the situation, the problem, the analysis, and the result.
Should you have any questions, please get in touch with academy@emagiz.com.
1. Situation
Sometimes, a ticket suggests that something on the flow level might not work as expected and warrants further investigation. In these situations, executing various checks in the Design, Create, and Deploy phases of eMagin is good for zooming in on the problem. This entry will look at a generic approach to this and various situations we have encountered in the past few years.
2. Problem
A suspected configuration problem on the flow level needs to be analyzed generically.
3. Analysis
3.1 Reproduction
First, you should check the assumptions of the person coming to you with a ticket. This is for both the Create and the Deploy phase of eMagiz. In Deploy, you check which version of a flow is running and whether this matches the client's expectations. Once you have established the correct flow version, it could happen that what is running is not what a user expected. The first step is to eliminate this mismatch.
If the flow version is as expected, we can check the properties to see whether we see any changes. In this situation, always verify whether the user deployed the flow after the property value was changed.
Thirdly, we zoom into the Manage phase to gather related information in the form of error messages or logging that help us identify at what place in the integration the message has exited the process. Once we have that, we can determine the cause of the error message better. If there is no indication in the Error messages where the message broke down, it is wise to check the log entries and queue statistics for more information.
3.2 Analysis
You can analyze most flow configuration problems in eMagiz with the above steps. The list below indicates various cases where part of the flow was misconfigured.
For more specific cases, please check out the following:
- Incorrect property configuration
- Incorrect queue configuration
- Incorrect groovy configuration
- FTP Configuration
- Design runtime changes after Create
4. Result
Once the flow configuration problem is identified, you can work towards analyzing and fixing the problem.