IBM Z Software
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).
Shape the future of IBM!
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:
Search existing ideas
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 your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
This requirement has been evaluated. Looking at current plans, it is not likely that this would be implemented in future zOS Connect EE releases, so correspondingly this requirement is being rejected. You have an opportunity to resubmit in twelve months time if you wish it to be considered then.
We are however interested in supporting multiple development teams creating separate APIs. Today, each team can work on their own API project(s) (controlled by source control) and deploy them to a shared development server. "Per API" and "per service" security can be used to control which team has access to call which API. If complete segregation of development environments between teams is required, separate z/OS Connect EE servers can be used. If you have requirements that would improve the experience for multiple teams developing APIs please submit them for consideration.
Hi all,
I work in Intesa Sanpaolo Bank, Italy and we would like to put the different Zos Connect objects,developed by different teams ,in different locations, in order comply with our change management file system structure, that assign to every team a specific path.
All our support to the RFE.
Kind Regards
Alessandro Santini.
Hi all,
I work in Intesa Sanpaolo Bank, Italy and we would like to put the different Zos Connect objects,developed by different teams ,in different locations, in order comply with our change management file system structure, that assign to every team a specific path.
All our support to the RFE.
Kind Regards
Alessandro Santini.
Additionally, we have come to learn that an instance of z/OS Connect can only reference one set of API and SAR folders. We have a need for multiple LOBS to use an instance of z/OS Connect and place their APIs and SARs in separate LOB folders. We would like an instance of z/OS Connect to be able to access multiple LOB API & SAR folders.