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.  Resource management: ini vs. administration settings

    Posted 06/28/05 06:36 AM

    Originally posted by: SystemAdmin


    Coul anyone explain the interaction of the CentralMgmt setting in the ini file and the option in the Event Server Administration tool?

    I found this in the doc, but leaves me very confused:

    quote:76570022ecIf the Event Server Administration is set to run systems in separate processes and the resource manager setting for a system is set to Local, the CentralMgmt entry in the initialization file has precedence over those other settings. Setting CentralMgmt to 1 will enable global (centralized) resource management. The default is 0 or local resource management.[/quote:76570022ec]

    How would you for example do global management except for one system?

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


  • 2.  Re: Resource management: ini vs. administration settings

    Posted 06/28/05 10:48 AM

    Originally posted by: SystemAdmin


    Global is global. In 7.5.1 you would have to have separate settings for all (but the same file) except for the one separate file.
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender
    #DataExchange


  • 3.  Re: Resource management: ini vs. administration settings

    Posted 06/28/05 11:26 PM

    Originally posted by: SystemAdmin


    It is possible to set the global/local setting in both the ini file and explicitly through the Event Server Administration.

    Which takes precedence, the ini or the Administration tool?
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender
    #DataExchange


  • 4.  Re: Resource management: ini vs. administration settings

    Posted 06/29/05 07:59 AM

    Originally posted by: SystemAdmin


    Got this from dev: If the admin is local and the ini is global, then it's global.
    If the admin is global, then it's global. If the admin is local and the ini is local, then it's local. There is no real reason to use local unless you only have one MSL, then use local and get a possible slight performance increase. By using global you make sure there are no resource conflicts between processes in the Event Server. The local / global is only for resource management. You can define different thread settings and idle settings in different .ini files and still have global resource management. Without it, you could get some real problems if you share single threaded maps between processes or copies of the same single threaded map.
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender
    #DataExchange