This is an IBM Automation portal for Integration 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Idea / RFE Review. Thank you for taking the time to raise this enhancement request, which we agree is a good suggestion for expanding the flexibility for the App Connect on IBM Cloud part of our architecture. As noted, in recent ACEv11 fix packs for software, and in ACEv12 software, in the Toolkit experience we have the option of specifying a CCDT URI location in an MQEndpoint Policy. MQEndpoint policies can be referenced from MQ nodes in a flow to control how the connections to MQ queue managers should be made. As noted, we don't currently provide a mechanism in our public cloud offering for the upload of the CCDT file itself, which you would then wish to have injected into the integration server's container when it is started up with the user's BAR file content loaded. In general, CCDT files can be accessed remotely using URIs which are either file based or HTTP based... although my understanding is that currently HTTPS is not supported. Given this, and also given most users preference in this area, we will interpret this idea to be requesting us to use a locally mounted CCDT file in the container rather than a request for enabling remote access. The status of the RFE is updated to Future Consideration.