This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Thank you for this RFE.
The current design of z/OS Connect EE does support a DevOps pattern for moving services between dev, test and production environments without having to change. There has to be some level of affinity between a service and where that service is running. The idea behind the connectionRef is to have the lowest possible affinity between services and environmental configuration. As long as you have the same logical connectionIDs defined in each of your dev, test, and production servers you are free to have the specifics and differences of the environmental config be completely transparent to the service.
You can read more about "How to move services between environments for DevOps" in our knowledge centre here: https://www.ibm.com/support/knowledgecenter/SS4SVW_3.0.0/designing/changing_connection.html
The DevOps lifecycle of our artefacts is important to us and being able to automate the build and deployment of services and APIs as been the sentiment behind RFEs that we have previously delivered eg RFE 113573:
http://www.ibm.com/developerworks/rfe/execute?use_case=viewChangeRequest&CR_ID=113573
We hope that by using the functionality we have delivered, and following these recommended patterns, you are able to satisfy your requirements of promoting services between environments without change.