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. Apologies for the length of time this idea has been in the status of Uncommitted Candidate / Future Consideration. Unfortunately with only a single vote in the almost 9 years since this suggestion was first created, we don't intend to continue carrying this suggestion further forward. That said, the arcihtecture of the product has evolved significantly since this request was first raised. With the advent of independent integration servers since the availability of ACEv11, the directory structure which underpins the product has been simplified. With this in mind, in the components directory, each of a node's integration servers has a directory in which its configuration is persisted. This directory is also named after the server's name rather than using the generated UUIDs which used to be used throughout our file systems. This makes mounting specific disks in order to separate disk requirements between servers a much easier task.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Connectivity and Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB
Thanks for raising the requirement. While you can usually use OS tools to mount and redirect filesystems to different physical drives, I understand that it is sometimes desirable to have the broker send core files to a different location directly. Of course, this would introduce a risk that an administrator redirects output to a location that another administrator might not be aware of (an advantage of sending to a constant place means that an administrator knows where to look!), so any feature to implement this would need to carefully address this. Thanks again!