IBM Sterling Transformation Extender

Sterling Transformation Extender

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

 View Only
Back to discussions
Expand all | Collapse all

More CPU Utilization, swapping issue and launcher log file generation

  • 1.  More CPU Utilization, swapping issue and launcher log file generation

    Posted Fri June 01, 2007 08:10 AM

    Originally posted by: Bhoju


    We are using DSTX 7.5.1 compiled maps deployed to run on solaris installed UNIX boxes. We are facing more CPU utilization , more context switching and more swapping issue when we deployed the maps on production. Is there any utility in DSTX installation set-up or launcher which will load all the maps once in the memory and then execute them so that CPU utilization , context switching and memory utilization will be minimum.

    Also when i enable the LauncherLog parameter to ewsc in dstx.ini to enable the launcher logs. i did not find the loancher log is created. Please advice do i need to do any more setting for this or where this file is generated if the LauncherLog parameter setting is perfect.

    Thanks in advance!!
    #DataExchange
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender


  • 2.  Re: More CPU Utilization, swapping issue and launcher log file generation

    Posted Fri June 01, 2007 08:50 AM

    Originally posted by: Kepa_Screen


    LauncherLog
    In the Launcher section of the dtx.ini file, you can specify the settings for a Launcher log file.

    The LauncherLog file is not created by default. To ensure that a log file is created, you must remove the semicolon from the beginning of the designated line of text in the dtx.ini file. For example, the following line entry has had the semicolon removed and will create a file that contains error, warning, startup, and configuration information, and will be created in the product installation directory by default.

    LauncherLog=ewsc

    The default syntax is:

    LauncherLog=[E][W][S][C]

    Each option is described in the following table.
    Option Description
    E
    Logs map errors
    W
    Logs map warnings
    S
    Logs Launcher startup statistics
    C
    Logs configuration information

    Regardless of the options you choose to log, the debug log (.txt) file will
    contain header information that is similar to the following example:

    ***
    WebSphere Transformation Extender Launcher for Windows
    Version:n.n(999)
    Copyright:
    2005 IBM Corporation
    Started:Thu Nov 21 10:53:05 2005
    Computer:MYCOMPUTER
    Logging:Configuration, Start Up, Errors, Warnings, Exit
    Note:This file views correctly under fixed font editors.
    #IBM-Websphere-Transformation-Extender
    #DataExchange
    #IBMSterlingTransformationExtender


Related Content