{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/b2e2da747cb846698c12d5d058091050\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/b2e2da747cb846698c12d5d058091050-c58ed1d1819c1493.gif","duration":1206.572,"title":"Prepare SAP Integration Suite","description":"This Loom walks through preparing the SAP Integration Suite environment to work with the IoT Pursuit. It shows creating CPI instances for both SAP Process Integration Runtime for API and for Integration Flow, assigning roles, creating and downloading service keys, and importing the “subplot integration suite” certificate into the FlowClient external certificates. It then deploys the int for dispatcher script package as needed and sets up an INT4 environment with the CPI checkbox via the configuration app, creating four RFC destinations in SM59 including an ESAPI token and integration flow runtime destination with basic auth and SSL. Finally, it customizes INT4 to assign the created RFCs and checks connectivity, confirming correct responses for the token, manage, and runtime destinations."}