Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.


Status Needs more information
Workspace WebSphere Liberty
Created by Guest
Created on Nov 12, 2025

Add Response Payloads to IBMJMXConnectorREST APIs

Currently the JMXConnectorREST APIs return no response payloads, only the HTTPS response codes. We would like to use the APIs for administering z/OS Connect server artifacts, however, without response payloads it is difficult to do so. A 200 or 204 is not always indicative that the call works. For example, the file may have been moved and a 204 received, but the z/OS Connect server may reflect that the file is invalid (i.e. not in correct format) or that it is in use by another API in the messages.log file.

In order to speed the development of building a deployment solution around these APIs for our application teams at Ford, we would like to see response payloads that include the results in the messages.log as a response returned from the JMXConnectorREST APIs.

Idea priority High
  • Admin
    Jahnvi Bedia
    Nov 25, 2025

    Thank you for the request. To proceed further and properly assess the feasibility, we would need some additional detail about your use case. Could you please clarify:

    • The specific API or endpoint being used

    • The exact file operation that is being performed

    • The specific log messages or message categories you require access to

    This will help us evaluate whether this scenario is supported today and whether additional changes are required. We’ll review further once we receive this information. Thanks!