IBM Sterling Transformation Extender

Sterling Transformation Extender

Come for answers, stay for best practices. All we're missing is you.

 View Only
Expand all | Collapse all

DSTX-75 and launcher.txt file..

  • 1.  DSTX-75 and launcher.txt file..

    Posted Tue November 09, 2004 07:28 PM

    Originally posted by: SystemAdmin


    Haven't seen any posts on this so wondering if this 'bug' has been fixed in 7.5.1 or there's a solution in 7.5.

    Reading through the 7.5 documentation I noted that we are not able to create the 'Launcher.txt' file.

    Nore are we able to define a unique path for the compoundsystem log file.

    Correct me if I've misread the documents. Below are a few concerns I have about the bug itself.

    The compoundsystem log file is now created all the time. Before it was only created when the debug option was on. In addition it always has a unique name (which you would probably want if you were debugging but not on normal basis). So unless you run a system to clean things up or do so manually the files will slowly consume space.

    The launcher.txt file allowed the system admin to define a path and select the level of error tracking desired. The compundsystem file logs everything all the time.

    Because the debug option appears to run all the time now, all related debug files are also being created all the time, again consuming space that will require additional maint.

    Because the path is static we will have a harder time locking Oncall developers out of the TX directories for support reasons.
    #IBM-Websphere-Transformation-Extender
    #DataExchange
    #IBMSterlingTransformationExtender


  • 2.  Re: DSTX-75 and launcher.txt file..

    Posted Thu November 11, 2004 02:12 AM

    Originally posted by: SystemAdmin


    Hi jvanbogart,

    In 7.5, the naming convention has changed. You cannot specify the names of the log files, and they always reside in the logs subdirectory named after the display name in the management console (i.e., either CompoundSystemXXX or <SystemName>XXX. The extensions are .log and .txt for the Debug and LauncherLog files.

    The reason this was done is for the MultiProcess Event Server feature so the Debug log and LauncherLog files wouldn't have conflicts.

    Furthermore, the resource manager and connection manager log files are rolled into the same Debug log file.

    This appears to be a bug in the documentation.

    Regards,
    Lew
    #DataExchange
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender