- SAP Managed Tags
Today I would like to share with you another new feature: When creating a Message Implementation Guideline (MIG) based on payload, you can now supply multiple payloads and all payloads are considered together by the application. In this blog post I will provide a short description of this new feature.
The picture before depicts the overall building blocks of Integration Advisor (of SAP Integration Suite). This blog post mainly relates to the Message Implementation Guideline area.
Short recap: Payload-based creation of MIGs
Earlier this year I had shared with you a larger extension of our payload-based MIG Creation feature. With the extended feature you were able to provide a single payload and choose the MIG nodes that shall get automatically qualified. As a result, each qualifier value present in the payload will create its own qualification variant in your MIG. Moreover, all nodes present in your payload will get automatically selected and example values are created based on the payload. For more details, please see my earlier blog post: Link
By the way, this blog post also discussed in detail when you should qualify a MIG node in your MIG structure and when it is better not to qualify.
MIG Creation with multiple payloads
It quite frequently occurs that not all nodes or all qualification variants are present in only one payload. In order to use our payload-based MIG creation in the past, you needed to choose the best fitting payload for automatic consideration and afterwards add missing pieces manually.
Now we have extended our payload-based MIG generation to also support multiple payloads. In the step Sample Payload of the Create Message Implementation Guideline wizard you can provide a ZIP file containing multiple payloads. Refer next screenshot for an illustration.
Keep in mind the following technical details:
- The ZIP file can have a maximum size of 10MB and up-to 25 payloads will be considered.
- The options SAP Cloud Integration and SAP Process Integration expect XML files as input.
- The third option EDI Flat File is only available for EDI Type Systems (like ASC X12 or UN/EDIFACT) and requires TXT files.
- Your ZIP archive might contain other files types (like PDF, XSD etc.) - these are simply ignored.
- Your ZIP archive might come with subfolders and all suitable files are extracted from the complete archive.
- Additionally, the extracted payload files (XML or TXT files depending on your choice) must fit to the Message Type for which you want to create your new MIG. Otherwise these payload files can't be considered.
The MIG Creation wizard now finishes with a pop-up window that summarizes which payloads were successfully applied and which payload files in the ZIP archive were not suitable. For an example refer the screenshot above.
Result of the MIG Creation
All the (successfully processed) payloads will contribute to the automatic customization of your new MIG. More specifically:
- Qualified nodes: If you have chosen the automatic qualification for a node (in step Select Nodes of the MIG creation wizard), each qualifier value present in at least one of the payloads will create its own qualification variant.
- Selection of nodes: A node will automatically get selected in your MIG if the node is used in at least one of your payloads.
Please note that the option to add Example Values is not available in case of multiple payloads because input from several payloads can't be combined to auto-generate the MIG Example Payload in a meaningful way.
Conclusion
With this feature extension you can benefit from the payload-based MIG creation even more as it allows you to build your Message Implementation Guidelines (MIGs) faster and with less manual effort.
Further reading
Bluesky| User | Count |
|---|---|
| 11 | |
| 9 | |
| 9 | |
| 8 | |
| 7 | |
| 6 | |
| 5 | |
| 5 | |
| 5 | |
| 4 |
