Edge Integration Cell (EIC) is one of interesting features of SAP Integration Suite that allows customers to run integration on your local network.
In Figaf we have been adding a number of make it possible to support EIC content, so it works smoot with your other integration.
Transport
When you transport an EIC iFlow you can automate the configuration of the different edge cells to your landscape.
IFlows and other artifacts is of cause be transported using the normal Figaf transport method where you have the ability to change the parameters of the engine where it is deployed. You can event this up as a rule.
Testing
You can run test on your EIC the same way as your test other iFlows in Figaf.
This makes it possible to ensure they works correct and changes do not impact them.
Operation
Understanding what iFlows are deployed and being able to un-deploy them is important. With Figaf you have a good overview of your tenants.
You can see what iFlows has been deployed on each Edge node and if the design and deployed configuration matches.
You can also deploy or un-deploy iFlow and the dependent object directly from the overview.
This works scales well to deploy/un-deply many iFlows at the time.
Monitoring
You can see more details about messages that have been processed on edge in an easy format. Both in the overview.
Moreover, you can also dig into details to see more about each message.
Alerting
You can find iFlows that is failed you can setup rules on how to route a notification. You can create a custom Odata filter to find message that have errors. It could also be your custom processing status.
Then you can setup complex Xpath conditions to figure out how to route the notification, it can be an email or a webhook.
Try Figaf Now
You can sign up to Figaf and explore how to use it on both your iFlow in cloud but also in edge. Edge does require a bit more configuration to run.