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 Not under consideration
Workspace z/OS Connect
Created by Guest
Created on Mar 12, 2018

RELATED IDEAS

Requester Endpoint not in server.xml

At the current level of zos/Connect v3 you have to set the endpoint url in server.xml. This is the worst choise to place it.

Why?

1) Security reason: Modifikation of server.xml. If you use static zos/connect instances (not zospt) the chance is very high, that the developer of an endoint is not allowed to change server.xml, so every time you need a new endpoint a sysprog has to do something.

2) Architecure: The endpoint url of an outgoing request belongs to an .ara artifact, not to an server configuration. If you have multiple instances of an api (with different endpoints) you should have two possibilities based on the scenario of how you build. Both have a clear separation of the server

a) endpoint url in .ara file

This scenario would need a different .ara package each stage. this don't fits the idea of move the production what you tested in test

b) endpoint url in extra file: if you allow to set a properties file for an .ara file alle properties which can be different on another stage could be set there. This would allow to stage the same .ara file. The developer than could set the properties in an extra file each stage -> this file would then be different on every stage. The ara file (the application) is the same on every stage.

Idea priority High
  • Guest
    Reply
    |     Jun 4, 2018

    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.

    Currently you can specify a "connectionRef" in the .ara file (through the build toolkit properties file) which specifies the ID of the "zosconnect_endpointConnection" element (in server.xml) to use for this API Requester. This allows you to have at static .ara file that can move through environments, and have each environment specify where that endpoint, for that ID, should be.

    Typically a company would use a single API gateway (such as API Connect) to manage API requests from their applications to both internal and 3rd party APIs. In this case only one "zosconnect_endpointConnection" is needed (that points to the the company's gateway) for all API requests, and you don't need to specify a new one for every new API you call.

    In the case that there are multiple gateways in the company (perhaps one for internal and one for external APIs) the developer can use the "connectionRef" to select the ID of connection to the gateway that manages the API they want call.

    More details about the connectionRef property can be found in "The build toolkit properties file" topic here: https://www.ibm.com/support/knowledgecenter/en/SS4SVW_3.0.0/com.ibm.zosconnect.doc/facilitating/build_toolkit_prop.html#build_toolkit_prop

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.