Digital Business Automation Ideas


This is an IBM Automation portal for Digital Business Automation 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

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):

  • Cloud Pak for Business Automation - including Business Automation Studio and App Designer, Business Automation Insights

  • Business Automation Workflow (BAW) - including BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management

  • Content Services - FileNet Content Manager

  • Content Services - Content Manager OnDemand

  • Content Services - Daeja Virtual Viewer

  • Content Services - Navigator

  • Content Services - Content Collector for Email, Sharepoint, Files

  • Content Services - Content Collector for SAP

  • Content Services - Enterprise Records

  • Content Services - Content Manager (CM8)

  • Datacap

  • Automation Document Processing

  • Automation Decision Services (ADS)

  • Operational Decision Manager

  • Robotic Process Automation

  • Robotic Process Automation with Automation Anywhere

  • Blueworks Live

  • Business Automation Manager Open Edition

  • IBM Process Mining


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.


Add a new idea Subscribe
Status Future consideration
Workspace FileNet Content Manager (CPE)
Created by Guest
Created on Mar 9, 2022

RELATED 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 :

  1. Logrotation (i.e. daily)

    1. 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.

    2. 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.

  2. Logpath configuration doesnt work properly

    1. 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.

Idea priority Urgent

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.