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:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Allow service accounts to be longer than 8 characters
Our corporate service account naming standards across multiple platforms assumes that all operating systems support up to 20 characters. All of the OSes we use, do support longer names. We have had to make exceptions for service accounts that will be used for various InfoSphere components. The default account names that many applications provide in their installation scripts, examples, etc. are usually already close to 8 characters. When you have multiple instances of those applications (such as test, dev, QA, prod, etc. instances) you should likely use different service accounts for each instance. For example, we have multiple products that come with a DB2 component. DB2's default instance owner is db2inst1. However, since there are multiple products (not just InfoSphere) include a DB2 component, we do not want to use the same service account name across all of them, but would like that account name to be long enough to relate it to the specific application instance it supports. This logic applies to WebSphere, etc.
Do not place IBM confidential, company confidential, or personal information into any field.