Integration
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).
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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Idea / RFE Review. Apologies for the length of time this request has been held in the status of Uncommitted Candidate / Future Consideration. Since initially raised, it has been our long-term strategy to simplify and improve the portability of the stateful files which IIB holds on disk. Large steps forward were made with the evolution of ACEv11 and the removal of the UUIDs from the integration server's on-disk structures. These changes, coupled with the mqsiextractcomponents command (which operates on a zip file created using mqsibackupbroker), provide us the framework to now be able to move ACE implementations between different platforms. There are still a small number of differences in the format of certain files we store - entries made using the mqsisetdbparms command are still endian specific, and there are a few registry files on windows that still hold .dat extensions that are an issue when moving to/from Windows. The mqsiextractcomponents command has been designed to deal with these anomalies, so if you want to port an integration node backup from one platform to another, you can use the mqsibackupbroker command and then the mqsiextractcomponents command (instead of mqsirestorebroker command). The ACEv11 mqsiextractcomponents command wasn't designed to recognise ACEv11 backups, but the ACEv12 mqsiextractcomponents command can be run against an ACEv11 or ACEv12 backup in order to move operating system. Given these advances, the status of the idea is closed.
We approve of the use case here, ie ability to easily port a node/broker definition between systems which may be based on different OSes. Alteration of the mqsibackup command is likely not the best way of achieving this due to the UUID values which are included as part of the IIB configuration store on disk, and also naming conventions for the artifacts on particular OS. That said, the spirit of the RFE is good, so status is updated to Uncommitted Candidate.
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