We are running TIBCO IntegrationManager as services - where do the messages, which used to show upin the dos window, get logged?
Article ID: KB0088452
Updated On:
| Products | Versions |
|---|---|
| TIBCO IntegrationManager | - |
| Not Applicable | - |
Description
Resolution:
There are several types of IM messages that are handled differently
1. Engine Errors - Also captured in engine log files. Can be seen when running as a service or standalone.
2. Some messages to stdout - Such as engine startup message. These are NOT viewable in service mode. A future release of IM will implement some solution to this
3. Trace information - Can be redirected to file if needed, which is what needs to be done in service mode.
4. Output to stdout/stderr from Javascript (such as writeln) - It is best to abstract such functions out to common points that
can write to a log file or the screen depending on the scenario. This has to be done by the user. Key information can be logged
to files using the Audit log task.
If you are using the writelns for debugging purposes then it may be more convenient to use Signal Outs instead and that way you can get the output on the tibrvlisten window.
In production, this may not be a feasible solution and you may wish re-design your process diagrams to abstract the writelns out to common points that can write to a log file.
There are several types of IM messages that are handled differently
1. Engine Errors - Also captured in engine log files. Can be seen when running as a service or standalone.
2. Some messages to stdout - Such as engine startup message. These are NOT viewable in service mode. A future release of IM will implement some solution to this
3. Trace information - Can be redirected to file if needed, which is what needs to be done in service mode.
4. Output to stdout/stderr from Javascript (such as writeln) - It is best to abstract such functions out to common points that
can write to a log file or the screen depending on the scenario. This has to be done by the user. Key information can be logged
to files using the Audit log task.
If you are using the writelns for debugging purposes then it may be more convenient to use Signal Outs instead and that way you can get the output on the tibrvlisten window.
In production, this may not be a feasible solution and you may wish re-design your process diagrams to abstract the writelns out to common points that can write to a log file.
Issue/Introduction
We are running TIBCO IntegrationManager as services - where do the messages, which used to show upin the dos window, get logged?
Feedback
Yes
No
Powered by
