This portal is to open public enhancement requests for IBM Sterling products and services. 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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
When Launcher starts in cooperative listener mode on RHEL servers a hidden directory is created under each watch point. That dir is named .WTX_<pid>_<hostname>.
Each coop listener will have its own one of these hidden dirs. The dirs are owned by the account running the Launcher engine with permissions of 700.
Two other dirs are also created: WTX_ERRDOCS and WTX_KEEPDOCS.
These are owned by the account of the FIRST Launcher to start in coop mode, and the have permissions of 700.
BUT - all other coop Launchers want to use these same dirs. If the other coop Launcher is running under a different account (such as running two coop launchers on one server) the SECOND Launcher to start cannot use these two dirs and will report errors accessing them in the Launcher logs.
The default dirs permissions for the WTX_ERRDOCS and WTX_KEEPDOCS should be 770 at a minimum, which will allow two different accounts to run Launcher in cooperative listener mode if they are in the same group. Putting accounts in the same group is simple enough to manage access to these two shared dirs without having to change Launcher beyond this default dir setting.
Another approach would be similar to the log permissions settings in the dtx.ini file. Have a setting aligned the cooperative listener mode that allows these two dirs to be set to a user defined permissions level.
Do not place IBM confidential, company confidential, or personal information into any field.