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.
RFE Review. Apologies for the length of time this RFE has been held in Uncommitted Candidate status. We suspect this idea would garner a mixed response from users of IIB/ACE if added to the product. For some, the ability to have their own configuration files packaged and moved to the runtime system as part of an App/Lib deployment would be seen as a positive whilst others might like the idea of *not* carrying superfluous testing files into the actual production runtime. That being said, offering users the ability to influence the contents of projects inside a built BAR file as an advanced option would make things more flexible. The mention of test data resources in particular is intriguing to us, given that we have future plans for our next major engineering release to support much better unit testing capabilities, including a new project type to make it easier to isolate test resources from an application whilst still maintaining a hierarchical link to the project. For now we will leave this RFE with maintained status of Uncommitted Candidate and will continue to monitor for popularity.
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
Now I have more experience with Apps and Libs.
The possibility to include non-IIB projects in Apps and Libs would be nice. The build can then ignore non-IIB projects.
We also use this kind of stuff like (ant) build.xml, properties, etc. for scripted builds and deploys. Pre V8 we use a simple project for this (Dev and Doc) but in V8 it resides under uncatagorized resource, away from the Appls and Libs.
For us there is no need to have them in the Apps and Libs project itself, to have the option to reference (simple or non-WMB) projects from Apps and Libs will be a better solution (our Doc simple project is sometimes reffereced by multiple projects so in V8 multiple Apps).