IBM Sterling Transformation Extender

Sterling Transformation Extender

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


#Sterling
#Supplychain
 View Only
  • 1.  Unique name for launcher log

    Posted 05/09/05 04:25 AM

    Originally posted by: SystemAdmin


    Hi,

    I want to set a unique name for launcher log file in DSTX v7.5.1.
    In the online library, it is given as we can set unique name for launcher using event server administartion. But not able to find any option to set the same.Could anyone help on this.

    Thanks
    #IBM-Websphere-Transformation-Extender
    #DataExchange
    #IBMSterlingTransformationExtender


  • 2.  Re: Unique name for launcher log

    Posted 05/09/05 04:53 AM

    Originally posted by: SystemAdmin


    Are you using the multi-process Event Server?
    If not, you can set the name in the dstx.ini file.
    If you are using the multi-process ES, there should be a unique name in the / or \ logs directory, including msl name & time stamp.
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender
    #DataExchange


  • 3.  Re: Unique name for launcher log

    Posted 05/09/05 06:37 AM

    Originally posted by: SystemAdmin


    Thanks for the reply.
    i am not using multiprocess event server. i set the file name as launcher.txt in the DSTX.ini file in windows version .

    LauncherLog=ewsc=launcher.txt

    But it is not creating the same. Instead it is creating the file named "CompoundSystem05-09-05-05-17-48-PM" under logs folder.
    Can you pls clarify this?.

    Thanks
    #DataExchange
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender


  • 4.  Re: Unique name for launcher log

    Posted 05/10/05 10:52 AM

    Originally posted by: SystemAdmin


    If you are not using the multi-process ES, you will get a unique compoundsystems-timestamp-txt file in the logs directory.

    Are you starting the ES from the Management Console with debug turned on?
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender
    #DataExchange


  • 5.  Re: Unique name for launcher log

    Posted 07/05/05 03:19 PM

    Originally posted by: SystemAdmin


    I got the same problem too.
    The Event Server is just running as single process. In the previous version, there will be a launcher.txt produced in the $MERC_HOME_DIR.

    I have set the LauncherLog=ewsc=launcher.txt in the dstx.ini, but what I have seen is the CompoundSystems-timestamp.txt under the $MERC_HOME_DIR/logs directory.

    Is there a way we can get a launcher.txt so that it will be easier for us to check whether it starts up successfully by looking at one file, rather than going to the logs directory and look for the latest file?

    We use eventserver.sh -start to start up the Event Server

    Thanks
    #IBM-Websphere-Transformation-Extender
    #DataExchange
    #IBMSterlingTransformationExtender


  • 6.  Re: Unique name for launcher log

    Posted 07/06/05 02:07 AM

    Originally posted by: SystemAdmin


    In 7.5 the command LauncherLog=ewsc in the dstx.ini file is only used to turn the msl logs On and Off, and if On then to what degree (e.g. LauncherLog=e will only print errors).

    The ini file no longer seems to have any bearing on the launcher log filename. The filename will always be CompoundSystemdatetime.txt (for single process) or SystemNamedatetime.txt, no matter whether you use single or multi process ES. The logs will always be in the /logs or \logs directory.

    In previous versions you could put -lewsc in the start parameters of the Windows Mercator Event Server service. This would have also produced the launcher.log... but even this option seems to be ignored in 7.5.

    What I can't confirm is whether this is by design or by fault! ;-)[/i]
    #IBMSterlingTransformationExtender
    #DataExchange
    #IBM-Websphere-Transformation-Extender


  • 7.  Re: Unique name for launcher log

    Posted 07/06/05 03:34 AM

    Originally posted by: SystemAdmin


    It is by design. The compoundsystem or mslname (timestamp) .txt is the correct file in the /logs directory.

    Too many times the file was directed to nonexistant file systems or places where the user did not have rights etc. so that diagnosing start up problems became next to impossible.
    #IBMSterlingTransformationExtender
    #DataExchange
    #IBM-Websphere-Transformation-Extender