SAP Hybrid ALM - SAP Cloud ALM / ServiceNow Concepts
This concept shows a Conigma Connect setup at which a user story should not be created in SAP Cloud ALM until a corresponding task is created for that solution.
The world software industrialisation is changing, fast. Keep up.
This concept shows a Conigma Connect setup at which a user story should not be created in SAP Cloud ALM until a corresponding task is created for that solution.
When communication between different ALM tools, including SAP ALM tools, is to be implemented, e.g. using a middleware like Conigma™ Connect, it is a good approach to upfront check the prerequisites on network level.
Often network components like SAP CPI / SAP Integration Suite, firewalls, reverse proxies, MID servers, etc. or challenges like missing certificates require different actions for a communication between the ALM tool and the middleware server on OS level (called middleware OS in the following text).
This example video shows how to create SAP Cloud- LM sub tasks out of ServiceNow change tasks. It also demonstrates the rules how to create SAP Cloud ALM user stories out of ServiceNow changes.
In certain server setups you have no GUI available and for example only SSH access. In such an environment for connetion tests you need to run Mockoon as command line version (mockoon-cli).
This articel describes hot to run mockoon-cli with SSL support.
When communicating via the Internet (e.g. between an ALM tool via Jira, ServiceNow or SAP Cloud ALM and Conigma Connect), encrypted communication via HTTPS is usually desired (HTTP would be unencrypted). This blog entry explains the concept behind this as a basis for the project managers of our customers to plan the right internal resources for this.