Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

API Key and Instance for SAP Build Process Automation

manojsjadhav_jd
Explorer
0 Kudos
732

We are currently working on calling Automations via API triggers for SAP Build Process automation.

Prerequisite for the same is creating service instance in BTP and generating API keys. Question is what is best practice to be adopted about generating the API keys and instance. Whether only one of them has to be created or multiple API keys and instances need to be setup.

3 REPLIES 3

maheshpalavalli
Active Contributor
0 Kudos
570

Hi Manoj,

The best way I think of is using the SAP Cloud SDK - and by using the destination (you can create it from service instance). This will reduce your lines of code and make the consumption so much easier. I wrote a blog post about how one can consume the Build API's.

https://blogs.sap.com/2023/02/08/consuming-sap-build-apis-made-easy-with-sap-cloud-sdk-in-your-sap-c...

Cheers
Mahesh

0 Kudos
570

Thanks Mahesh, the blog is really informative.

However, we were interested in Process Automation instances and API key generation. Do we keep only one instance and one API key. Or we should go for multiple instances and API keys.

0 Kudos
570

manojsjadhav_jd, For my blog post, you don't need to generate keys. It just uses the service instance.

And reg. the service instances, it's based on the requirement and I don't see anywhere the limitation of no of service instances or no of API keys that can be created from SAP. IMO it will be better to have it created per every single application. if more applications are depending on one single service instance (bound) and for sure if someone changes or updates the instance, other applications depending on it will get affected if something goes wrong, let's say something has been changed mistakenly by the developer. (Assuming the service instance is created automatically from the application (MTA).)

But if you are using the destination service, (like my blog post, the second scenario, user token exchange), => it is still better to create multiple instances for the destination service to access the destinations. But in this case, I would create only one service instance for the SAP Build Process Automation and create a destination for it. Because I will not be updating the service instance (SAP Build) from my Application in this case, but I will be creating it manually from the cockpit.

These are just my opinions. I would also invite mbensan to share his thoughts as you are quite active in BTP area 🙂

Cheers!
Mahesh