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.
Thank you for raising this requirement. It is being closed as a duplicate of existing RFE 132443:
http://www.ibm.com/developerworks/rfe/execute?use_case=viewChangeRequest&CR_ID=132443
RFE 132443 was rejected on the basis that it lies outside the scope of z/OS Connect EE. There is a longer description in the comments of RFE 132443, but the summary is that:
- REST is an inherently synchronous interaction pattern.
- Building a framework of asynchronous interactions is outside the scope of z/OS Connect EE. Solutions for asynchronous interactions such as MQ already exist today.
- For inbound APIs, there is nothing stopping you designing an asynchronous interaction spanning multiple, synchronous, REST requests (eg a POST that responds with a 202 and an ID, then a GET with the ID for the result). You could use z/OS Connect EE in front of an asynchronous messaging framework like MQ with help facilitate this
- For outbound API calls, you can use the facilities in your application hosting environments to manage asynchronous calls, eg using the CICS Async API to wrap calls to z/OS Connect EE's API requester.