App Connect

 View Only
Expand all | Collapse all

WIN10 ACE12.0.3 MQSI_WORKPATH - how to change

  • 1.  WIN10 ACE12.0.3 MQSI_WORKPATH - how to change

    Posted Mon December 27, 2021 02:28 AM
    Today I ran ACESetup12.0.3.0.exe with target E:\Program Files\IBM\ACE
    When running Enterprise Console my experience is:
    MQSI_REGISTRY=C:\ProgramData\IBM\MQSI
    MQSI_SECURITY_PROVIDER_PATH=E:\Program Files\IBM\ACE\12.0.3.0\server\bin
    MQSI_WEBADMIN_HOME=E:\Program Files\IBM\ACE\12.0.3.0\server\webadmin
    MQSI_WORKPATH=C:\ProgramData\IBM\MQSI
    MQSI_BASE_FILEPATH=E:\Program Files\IBM\ACE\12.0.3.0
    MQSI_CATALINA_HOME=E:\Program Files\IBM\ACE\12.0.3.0\server\catalina
    MQSI_CONSOLE_NLSPATH=E:\Program Files\IBM\ACE\12.0.3.0\server\messages\
    MQSI_EXMLTCONFIGPATH=E:\Program Files\IBM\ACE\12.0.3.0\server\exmltConfig
    MQSI_EXTENSIONS_PATH=C:\ProgramData\IBM\MQSI\extensions\12.0.3

    Is it safe to move that stuff from C to E drive?
    Is there a good way available to make ace.cmd work with E drive.

    ------------------------------
    Matthias Jungbauer
    ------------------------------


  • 2.  RE: WIN10 ACE12.0.3 MQSI_WORKPATH - how to change

    Posted Wed January 19, 2022 12:07 PM

    Hi Matthias,

    On Linux this is not too hard as there is an environment variable (MQSI_WORKPATH or MQSI_FORCE_GLOBAL_REGISTRY) and a file ($MQSI_BASE_FILEPATH/common/GLOBAL_REG) you can use to set the desired location. For those interested, the order these are looked at is MQSI_REGISTRY, $MQSI_BASE_FILEPATH/common/GLOBAL_REG, then MQSI_FORCE_GLOBAL_REGISTRY.

    On Windows, it is a bit more complicated.  ace.cmd gets the path from mqsiprofile.cmd, called from ace.cmd.  In mqsiprofile.cmd, MQSI_REGISTRY is set by MQSI_WORKPATH which is set by %PROGRAMDATA%\IBM\MQSI.  Windows does not have an override option.  Thus, in order to use a custom path, you need to either update PROGRAMDATA or you need to update mqsiprofile.cmd to point MQSI_WORKPATH to a different value.  Changing PROGRAMDATA may have consequences outside of ACE.  Changing mqsiprofile.cmd is fine, but each new release will have a default copy of this, so you will have to remember to change it yourself after upgrading.

    Once you update either, you can certainly copy the files over to the new location.  You can also use the command mqsicreateworkpath after updating for node installs to create an empty workpath.  If you are using independent integration servers, you can use the command mqsicreateworkdir.

    -Matthew



    ------------------------------
    MATTHEW SEGALL
    ------------------------------

    Original Message