Skip to Content
Technical Articles
Author's profile photo Fatih Pense

CPI Partner Directory Postman Collection

As I mentioned in the last blog post I have prepared a Postman collection that is easy to use with CSRF and multiple tenants.

Installation & Configuration

Download environment and collection files from the GitHub repo.
https://github.com/mdpgroup/cpi-postman-collections

Importing the Common Environment Template

Click the environment settings button:

Click import, choose the environment file “cpi-tenant-template.postman_environment.json” and import.

Click on the “CPI Tenant Template” environment:

Enter the values for your tenant. You should create an environment for each tenant. Note the tenant URL format:

Choose your specific tenant environment:

 

Importing the Collection

Click the import button and choose the collection file “cpi-partner-directory.postman_collection.json”

Usage

You should see the collection on the left pane now. Let’s start with Get CSRF request:

 

Click “Send”. If you configured everything correctly, you should see the HTTP 200 success header. CSRF is saved for the following requests.

As an example, you can create an Alternative Partner using “Create Alternative Partner” request:

Congratulations! Now you can see the partner with below requests or using Partner Directory UI

Conclusion

Coupled with SuperEasy Partner Directory UI this collection has vastly improved our workflow. I hope it will be also useful for you.

The GitHub repository is open to contribution. You can create issues or pull requests for Partner Directory APIs or other APIs.

Thanks for reading & see you in the next posts!

Assigned Tags

      10 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Rashmi Joshi
      Rashmi Joshi

      Hi Fatih Pense ,

       

      Thanks for sharing article. I am successfully able to GET CSRF.

      However, I need more knowledge on next service of CREATE PARTNER.

      What exactly we are creating it here? Can I see that on CPI tenant?

      Please help to understand these services from the collection.

       

      BR,
      Rashmi

      Author's profile photo Fatih Pense
      Fatih Pense
      Blog Post Author

      Hello Rashmi,

      Partner Directory is a standard service bundled with CPI. You can think of it as SAP PI B2B TPM on CPI. You can define partners, parameters, and even store XSLT. Currently it only has OData APIs by SAP and no official UI. That's why I shared my Partner Directory UI.

      You can read the help page
      https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/0fe80dc9d3be4dfbbb89ee4c791d326e.html

      or this blog from Franz Forsthofer for more information:
      https://blogs.sap.com/2017/07/25/cloud-integration-partner-directory-step-by-step-example/

      Regards,
      Fatih

      Author's profile photo Alexander Bundschuh
      Alexander Bundschuh

      Hi Fatih,

      great blog, thanks a lot, this definitely helps in working with the partner directory when setting up your integration scenarios (not only) for the b2b use case.

      What a coincident, we were actually working on partner directory guidelines in parallel as well, those will be published soon incl. integration flow examples as part of our integration flow guidelines, our package is currently in review, once available it will be accessible from here where all other guidelines are described that we have published so far incl. patterns

      https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/6803389050a0487ca16d534583414d2b.html

      So stay tuned

      Thanks and Regards

      Alex

      Author's profile photo Fatih Pense
      Fatih Pense
      Blog Post Author

      Hi Alexander,

      I’m glad you find it useful. That means a lot, coming from you.

      A new guideline is a great news. I have just read the “Apply Message-Level Security” design guideline, and I love how they are informative and teach concepts well beyond CPI.

      You can use/modify/republish the Postman collection as it is already MIT licensed. Other than that feel free to guide me if I can contribute to any of the efforts.

      Best regards,
      Fatih

      Author's profile photo Y Z
      Y Z

      Hi Alexander,

      Can we use partner directory for the IFLOWs which will get deployed on PO?(cloud integration content )

       

      Also if we can then where will these entries stored to ensure there is no cloud round trip to read these entries for a premise to premise scenario ?

       

       

      Author's profile photo Alexander Bundschuh
      Alexander Bundschuh

      unfortunately, no, the partner directory is not supported on the cloud integration runtime inside SAP Process Orchestration

      Alex

      Author's profile photo Y Z
      Y Z

      Thanks Alex, so what is the alternative on cloud integration runtime inside SAP Process Orchestration if we have multiple B2B connections with different message types all mapping to single target message ?

      Author's profile photo Alexander Bundschuh
      Alexander Bundschuh

      what about using the b2b add-on?

      Author's profile photo Y Z
      Y Z

      Where  in cloud integration content IFLOW would I configure it or call it ?

      so after my inbound call and before message mapping , somewhere I would need to access the configuration of B2B add on to check which message mapping to use and also to authenticate the caller , how will I do that ?

      Author's profile photo Alexander Bundschuh
      Alexander Bundschuh

      what I meant was to use the b2b add-on instead of the cloud integration runtime

      If you like to use the cloud integration runtime, I'm afraid you need to model the partner connections and mappings explicitly, you may define an own integration flow for each partner and use JMS to decouple the message processing

      Alex