We are a little late with the November release, there was a few bugs we needed to sort out before we could release it. But it is worth the wait.
This release contains a huge number of fixes around usage handling deployments and testing of systems if Edge Integration Cell is added. Hopefully we got these covered now. Please start to explore it.
We also added a new authentication option for SAP Integration Suite.
We also have a few items for our December release that needs to be resolved.
Using SAP Password for authentication
We wanted to make it as easy as possible to run Figaf and integrate it. And we need to have access to the web APIs because there is a big difference between the APIs there and public APIs. The only way to access these API is by enabling login as a user. Ideally the public APIs should be fully compatible with the private, but that would requite a huge effort on the SAP side and would not be realistic. Best option was it was a separate Service key we should use for it.
We therefore added usage of SAML where Figaf could get users to the integration suite system. Now it is no longer possible to create SAML authentication since new access need to go thru SAP Cloud Identity Services/IAS. It seems a bit more complicated to configure and get to work.
We are instead opting for SAP Password, the X509 certificate you can generate for your self. We will suggest you create a separate user S-User like [email protected]. Then you can use this user on all your SAP Integration Suite system and give it access to the roles needed (PI_Administrator, PI_Business_Expert, PI_Integration Developer and idav-content-developer)
You will have to enable SAP login for the Default Identity Provider for this to work. This is a downgrade based on our SAML based authentication, were there was no change for the login screen.
You can reuse the certificate in multiply agents to make the process simpler.
Deployment in batches
One thing larger organizations have around how to deploy and undeploy a large number of iFlows. It can be if you have a failover or a system is down. Then it can simplify your operation of stop/un-deploy the iFlows.
We have also improved the search to enable to give a better overview of when changes have been introduced to the landscape. Compare the difference between QA and production. You can from the landscape overview still create transports. So this becomes the perfect place to check how your iFlows is moved to production.
When you start the deployment you can define how many iFlows you want to deploy concurrently and how often and long to check of the status. If you want to be aggressive and deploy many integrations simultaneously.
You can also see the status of the deployment to see what kind of errors you are getting. This makes it much easier and then you can redeploy them again.
Deployed vs Configured configuration
You will most likely only check your configured configuration. But may there is a difference between what is deployed. It can happen in many because you forget to deploy the last changed configuration. And without a tool like Figaf good luck finding it.
In the Landscape configuration you now have the option to select show difference between design-time and deployed.
Once click on a warning you can see all the difference between what you have configured and what is deployed. It is one excellent feature for improving what is configured. Notice you should perform a full synchronization to ensure Figaf have access to all objects.
With this you can easily find all the places where there is a difference and then correct it and deploy the configured values. It is a good cleanup before you perform a migration.
Edge support
We have expanded the support of Edge, now you can use it for all the different use cases like testing, monitoring and alerting.
This enables you to use your edge runtime with a lot more scenarios.
There may be some limitations on what is possible so if you find some limitations let us know.
We do not cloud connector access from Figaf in BTP to your on-prem Edge cell in this release. It should be something we will release soon.
One of our struggles was to understand how the runtime location id was set. This is enabled when you enable Edge Runtime for the first time on a tenant. Then it must be sent when running request like deploy or change to
Testing only part of an test suite
When we designed test suites long time ago our main focus was that you ran the full test suite in one go and you could use it for documentation. When working on your test cases we often only wanted to test a limited number of test cases. The ones you have selected with a check mark.
Speaking of test suites, we have also improved the calculation of which system to run on and improved the option for scheduling.
Testing of Camel properties
If you for instance used a SFTP based channel to test your integration with it. Figaf cannot sent data to the SFTP, so instead we create an iFlow with HTTP channel and send the message into it. Apparently the HTTP channel removed Camel headers, so if you want to use the property CamelFilename in your iFlow we need to modify it. So now they use ProcessDirect and our HTTP to ProcessDirect iFlow have been updated.
This allows you to test a few more scenarios without having to modify the iFlows.
API for transport
We have once again improved our public API. We wanted to make it easier to approve and import transport when you came from a system like ChaRM or Jira. Here you would have an external ID and you can then perform the approve action. We have been improving the transport APIs both for searching and approving.
You can see your current APIs at /swagger-ui/index.html#/ here you can also work with them and explore it.
There are so may ways teams use their favorite tools so it is not good enough to create adapters for all tool, but since you have SAP Integration Suite it is quite easy to add the logic there. Remember we also have webhooks, if you want to inform the tool about status of a change request.