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
Start by posting 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 offering manager 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 notifications 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 that cannot be implemented in a reasonable time.
Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):
Cloud Pak for Automation - incl Business Automation Studio, Business Automation Insights
Business Automation Workflow (BAW) - incl BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management
Content and Capture Services - incl Filenet, Automation Document Processing, Daeja, Navigator, Content Collector, Enterprise Records, Business Automation Content Analyzer, Datacap, Automation Mobile Capture, Content Manager OnDemand, IBM Content Manager
Robotic Process Automation with Automation Anywhere
IBM Blueworks Live
If you encounter any issues accessing the Ideas portals, please send email describing the issue to firstname.lastname@example.org for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.
CPE: JUL Logging should be enhanced with operational functions similar to the former Log4J-implementation
Since Content Platform Engine has changed the underlaying logging framework from Log4J to JUL there are several important functions missing that existed before with log4j standard configuration :
Logrotation (i.e. daily)
It's very important to administer several stages, analyze errors of many applications (ICN, CMIS, different plugins, ICC4SAP) in a distributed large environment to have a log rotation that enables us to find the correct logfile by name (with date included) within a short time instead of guessing and searching in which logfile the required information maybe could be located. With log4J there was a simple configuration mechanism (dailyRollingFileAppender), with JUL there is no such or similar option. The very low configuration with size and number of generations to keep is absolutely not sufficient.
In order to keep logfiles for a year, which is a compliance rule, with JUL implementation the only way is to estimate daily log volume and calculate it for a year to make sure logs are not rolled over and overwritten. This is more of a lottery than a solid reliable solution. With a daily rollover this was not necessary.
Logpath configuration doesnt work properly
Eventhough the documentation offers a logpath-configuration with JUL, this is not working for all Content Engine messages. Part of the messages are still located in an extra, not configurable logpath that is located in the WebSphere runtime environment.
The change from Log4J to JUL is a very big problem for us and prevents us from updating our production environment from 5.5.3 to a current version. We have done the update in our DEV and TEST environment and can't do it in the production environment with this fundamental problems. Eventhough IBM is stating that this works as designed.
Do not place IBM confidential, company confidential, or personal information into any field.