IBM Data and AI RegTech Ideas Portal

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:

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

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


For product documentation, see Knowledge Center.
Create and View Support Cases and Use the Discussion Forum here

Shorter URL for this site is: http://ibm.biz/WFS-Ideas or https://ibm.biz/RegTech-Ideas

Status Not under consideration
Component Security
Created by Guest
Created on Apr 5, 2019

FTMV30012_Dev2_NIT Request that IBM review FTM for compliance with NIT WAS Standards re: Section 22 > logging

Application Logging
The WebSphere Application Server logs such as SystemOut.log and SystemErr.log are for use by WebSphere Application Server only and cannot be used by the application for any type of logging. Applications should utilize an approved logging framework to externalize logging specific to that application. Any legacy systems that are writing application logging to the WAS logs should be changed as soon as possible and must be changed upon upgrading or moving to a new system.
WAS system logging is based on number of logs and size of each log. The baseline is 3 historical logs at 10 MB each. This can be adjusted to a specific system needs to keep more or larger logs to ensure there is enough history for troubleshooting purposes. It is advisable to keep 2-4 weeks of logs unless space is an issue.
NIT WAS implementation standards documentation provides guidelines to the technician on specific log implementation.