Launcher
Sort by:
Trending
Status:
Showing 11
3
VOTE
ITX - Allow Launcher logging and adapter tracing to report milliseconds
Customers are reporting performance issues so support has the customer enable the launcher compound system logging the logs only report hour:minute:second. With maps running quickly based on cpu speeds today, often enough customers are trying to f...
0
Not under consideration
8
VOTE
Clean the map cache without restarting launcher
Today every time we need to change a map in launcher environment the launcher has to be restarted because the maps are cached there.It doesn't matter if the maps are used directly in the flow or ran by RUN function. For High Availability productio...
1
Not under consideration
7
VOTE
5
VOTE
Alternative to +SETALL permissions requirement on IBM MQ Adapter connections using -EQN
IBM MQ Adapter connections often use the -EQN facility to designate an alternate queue from the input -QN so that error messages do not get stuck in the input queue and interfere with message processing over time.
The use of -EQN requires the +S...
0
Future consideration
4
VOTE
1
VOTE
Reset reused workfiles for maps in the Launcher
Reusing workfiles makes map faster as it speeds up the alidation process. However, changes in data mean special care has to be taken to avoid issues for the concerned maps. Currently, one has to manually remove the workfiles after the Launcher was...
1
Not under consideration
1
VOTE
Reset Launcher "Black list" for failed messages
Whenever a message triggers a map failure, even if the failure is not related to the message's content, the message is blacklisted by the launcher and will not be trigered again. This avoids "poison messages" but needs a restart to have the messag...
1
Not under consideration
2
VOTE
Catching informations about WTX maps dynamically at runtime
The product functionality should be enhanced to make it possible for WTX maps to catch following informations dynamically at runtime 1. its own map name2. the associated WTX system, sub system and component to clearly identify the map3. on which i...
0
Functionality already exists
1
VOTE
Add Ability To Configure Where Launcher Logs Are Written
We are starting to use the Launcher image to deploy and run Launcher in containers. The Launcher Logs are written to <itx_install_dir>/logs by default, and there is no way to change where these logs are written. So, when the pod/container is...
2
Functionality already exists
1
VOTE
WTX service discloses detail software versions & file system
WTX service discloses detail software versions & file system - Cases - IBM Support
The Launcher process uses three TCP/IP ports. The first port is for status, the second port is for monitoring and the third port is port contr...
3
Not under consideration