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

  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.

Add a new idea Subscribe
Status Delivered
Workspace z/OS Connect
Created by Guest
Created on Sep 28, 2018

RELATED IDEAS

API Requester configuration server.xml vs ara file

We need zero server.xml modifications when deploying, updating and moving an API requester between environments:
- Fully automatic deployment and update from an ara file, like we've with APIs and services, without necessity to create a section in the server.xml file. So, we drop in an ara file and z/OS Connect pick it up.
- Be able to set all settings available in the API requester configuration section (in server.xml) directly in the ara file when creating an API requester.
- All configuration parameters available now in an individual API Requester section (apiRequester) must be available in the general section (zosconnect_apiRequesters), ex. requireAuth. Right now, we can write these parameters in the general section, but it has no effect. It will allow to setup general settings and manage exceptions in an individual API requester, if necessary.

Idea priority Medium
  • Guest
    Reply
    |     Oct 2, 2018

    Thank you for your RFE.

    Currently the product is designed with the intention of allowing .ara files to be deployed, in the general case, without any server.xml configuration. Environmental settings can be configured globally in the zosconnect_zosConnectManager element to be shared across all APIs, Services and API Requesters in the server.

    The apiRequester element is entirely optional and is intended for use in the few exception cases when you have API Requesters that require overrides to the general config. Since we do not require server.xml modification to deploy an API Requester int he product today, this RFE is being closed as delivered.

    If you have any specific environmental config fields that you'd need to often set differently on a per API Requester basis, please raise an RFE specifying which fields and why the settings need to differ on an individual API Requester basis.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.