Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform 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 (

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.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace WebSphere Liberty
Created by Guest
Created on Feb 16, 2017

Enhance the dynamicRouting setup and genPluginCfg commands to set piped logger for plugin log

Enhance the dynamicRouting setup and genPluginCfg commands so the plugin log location can refer to a piped logger.

This is related to RFE 94444 which implemented something similar.

Today, when dynamicRouting is used to generate plugin config files

dynamicRouting genPluginCfg --host=host1 [ ... ] --webServerNames=web1,web2,web3 --pluginInstallRoot=PLG_ROOT

the generated http_plugin log location is based on the plugin install root:

We would like to be able to not only write the plugin log to a different directory but also to a piped logger.

If a new parameter we added to dynamicRouting called "logFileName" the command might look like this:

dynamicRouting genPluginCfg --host=controllerHost [ ... ] --webServerNames=web1,web2,web3 --pluginInstallRoot=PLG_ROOT --logFileName="|IHS_INSTALL/bin/rotatelogs /some/path/http_plugin.log.%Y-%m-%d-%H_%M_%S 86400"

and the LogLevel entries generated as

Idea priority Medium
RFE ID 101157
RFE Product WebSphere Application Server

set plugin rotation in generated plugin-cfg.xml using dynamicRouting

Set plugin rotation in generated plugin-cfg.xml using dynamicRouting.
over 7 years ago in WebSphere Liberty 0 Future consideration