1. Is the webMethods Integration Cloud: Container Edition available for Free Download and Use ?
2. Is there a docker script for Windows yet - Assume , all my wM packages are running on Windows and not linux ?
3. How is the Architecture between webMethods Integration Cloud and webMethods API cloud going to be ?
4. Why is there no option to custom Recipes ?
5. Is there a roadmap for making integrations with JMS , JDBC , etc other than SOAP and REST ?

Hi Suresh,

Please see inline.

1. Is the webMethods Integration Cloud: Container Edition available for Free Download and Use ?
   This is cloud only offering
2. Is there a docker script for Windows yet - Assume , all my wM packages are running on Windows and not linux ?
   This runs in the IC datacenters
3. How is the Architecture between webMethods Integration Cloud and webMethods API cloud going to be ?
   API Development - Integration Cloud, API run-time Governance - API Cloud
4. Why is there no option to custom Recipes ?
   You can create the recipes and publish them to GitHub. Custom recipe store - Software AG · GitHub
5. Is there a roadmap for making integrations with JMS , JDBC , etc other than SOAP and REST ?
   JDBC, SOAP, REST are already covered. JMS - IC uses this internally. But you can use any cloud messaging offerings like AWS SQS, Google Pub-sub with IC.

How does that now map to webmethods.io? Integration Cloud no longer available and there are differences between IC and wM.io.

webMethods.io = IC + Built.io.

IC is not going anywhere.

IC is the base for all Integration & API Management products.

API Cloud, B2B Cloud, webMethods.io, Hybrid Integration all depends on the same.

webMethods.io workflow is best suited for event driven integrations (App integraitons, webhooks, workflows, connectors, etc.) whereas IC brings in API Led, Hybrid, Point to Point integration capabilities.

P.S: Don’t miss out Cloud Deployment - Implement on premise and deploy to cloud.

webMethods.io = IC + Built.io.

• Very well clarified…

Cheers!
RMG