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 (OpenAPI 2) 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.
Very good idea, IBM team is there any update on this RFE?
Very good idea, IBM team is there any update on this RFE?
Agree, Good idea having a similar tooling functionality to creation of incoming and outgoing API's (having .ara created in a similar way to .sar and .aar files), this will make things easier.
Reason I ask now is that I may recommend holding off from developing outgoing API in our shop until this is delivered if we know this RFE is coming, will stick with a working alternative i.e.MQ).
For reference: In the days of ZCEE V2 we had to configure WOLA API's in the server.xml. Going to V3 and using IPIC meant the configuration could be done in the tooling (IDz) and not server.xml (making deployment easier, less complex and with less risk). The current example I see for creating outgoing API's requires command line (conbt) and the need to update the server.xml, will there be a solution similar to how IPIC can be configured in the tooling (i.e. build and deploy in the tool and also reduce the need for updating server.xml per API).
Our Development team use API Toolkit to create and manage API prodiver and use Zconbt to create API requester.
They claim a unique solution to create and administrate the API Provider and the API requester.
That unique solution is mandatory for them to use and to exploit the API requester
We have a line of business area that would like to move their Batch Outbound API call into production. We definitely need a streamlined, easy to deploy process for our LOB developers. Our company is in the beginning phase of z/OS Connect API development and we believe more developers will be moving into API economy. We want them to have a positive experience in all aspects of their development lifecycle. We see this RFE as a must have. Please.
We have a line of business area that would like to move their Batch Outbound API call into production. We definitely need a streamlined, easy to deploy process for our LOB developers. Our company is in the beginning phase of z/OS Connect API development and we believe more developers will be moving into API economy. We want them to have a positive experience in all aspects of their development lifecycle. We see this RFE as a must have. Please.
Is there any update on this RFE? We are also very interested in this RFE as it is not feasible to have users deploy via "FTP". It would make a lot more sense in the work flow if the ARA's could be imported to z/OS Connect EE and deployed via the deploy option the same way AAR's are deployed today.
Very good idea. The development, generation, deployment and source code control for an API Requester project would become similar to an API or a SERVICE.
Very good idea. The development, generation, deployment and source code control for an API Requester project would become similar to an API or a SERVICE.