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

Best practices for multiple instances of ITX/B2B Gateway

Archive User

Archive UserMon February 19, 2018 02:29 AM

  • 1.  Best practices for multiple instances of ITX/B2B Gateway

    Posted Fri February 16, 2018 10:38 AM

    Originally posted by: MargoNoel


    Good morning,

    We will be using ITX on a development server where we would like to have multiple development environments existing concurrently.  Is it preferable to define the environment at the system level within a single instance of ITX or is it preferable to install multiple instances?  Is there a best practice?  Are there any Redbooks or papers that address this need?

    We also have the IBM Sterling Gateway in our tool mix and have the same question on multiple instances on a single server.  I could not find documentation on such an installation configuration.

     

    Thanks very much!

    Margo


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


  • 2.  Re: Best practices for multiple instances of ITX/B2B Gateway

    Posted Mon February 19, 2018 02:29 AM

    Originally posted by: Laurent(Satisco)


    Good morning,

     

    I'd rather have multiple installs, using separate accounts, so that control is easy and efficient. This means you can have the .profile script set the environment for each account, so that each team/person/project is always in the right context when they connect to the server. This also means you can give them more rights as they are unable to alter other people's environment. They could even reinstall without having the other projects needing to stop their running environments. You could also support multiple versions on the same server,which can be useful for migrations.

     

    If you use one ITX installation for multiple environments, you depend on settings, like separate deployment directories, separate processes for the different systems, etc. It will work, but you may discover some rigidities in some areas.

     


     


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