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.
Thank you for raising this request.
The locations documented in the referenced Docker Hub article relate to an earlier deployment model where App Connect Enterprise was distributed as a standalone container image. Since then, the product has evolved towards an Operator-based deployment model, and the underlying implementation of the container image has changed accordingly.
As a result, many of the directories and files within the
initial-configarea are now considered implementation details of the image. These internals may change between releases as part of ongoing product development and maintenance, and therefore cannot be treated as stable, customer-facing interfaces.At present, the only directory within
initial-configthat customers should rely on as a supported and stable interface is:/home/aceuser/initial-config/bars/BAR files placed in this directory will continue to be processed during Integration Server startup, and we remain committed to supporting this capability.
Customers should not depend on the structure or contents of other locations within the
initial-configdirectory, as these are subject to change without notice. For this reason, we do not currently plan to document the internalinitial-configdirectory structure beyond the supported interfaces that are intended for customer use.