Skip to Main Content
IBM Z Software
Hide about this portal


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.

Support for multiple distribution paths

See this idea on ideas.ibm.com

'- Supports only a single deployment directory per build file type for both inbound and outbound
 (ex) <WLP_USER_DIR>/servers/<serverName>/resources/zosconnect/services
- It is impossible to separate folders by application code (customer, receipt, credit, etc.) and control permissions in KB.
- Support for more than two distribution paths per type (or support for configuring the distribution directory as a subfolder by application code) is required.
 (alternative 1) multiple distribution path
 <WLP_USER_DIR>/servers/<serverName>/resources/zosconnect/services1
 <WLP_USER_DIR>/servers/<serverName>/resources/zosconnect/services2
 (alternative 2) Deploys build files distributed to the specified path as well as its subfolders.
 <WLP_USER_DIR>/servers/<serverName>/resources/zosconnect/services and all of its subfolders

Idea priority High
  • Guest
    Reply
    |
    Mar 11, 2025

    It's for specifying multipath in a single server. 
    This is required to run multiple applications on a single instance(server) and so it's required to distribute application source codes to different paths by application.

  • Admin
    Demelza Farrer
    Reply
    |
    Mar 10, 2025

    This requirement has been evaluated. Looking at current plans, and the requirement details, it is not likely that

    this would be implemented in future zOS Connect releases.

    To achieve locations of API files (AARs and SARs) we recommend using multiple servers. Alternatively, with the latest zOSConnect-3.0 runtime, a configuration can be added to specify the location of each API.

    Note:
    zosConnect-3.0 feature which is currently applicable to OpenAPI 3 APIs specifications. IBM intends to extend the support of the zosConnect-3.0 feature to include all versions of the OpenAPI specification. As such the functionality in the zosConnect-2.0 feature will not be updated to support this.

    This IDEA is therefore being closed