Migrating from an earlier version of WebSphere MQ File Transfer Edition

To migrate from an earlier version or from the trial version of WebSphere® MQ File Transfer Edition to a later version, perform the following steps.

About this task

Note: If you have installed an Early Access Program (EAP) or Early Design Program (EDP) driver do not follow the instructions in this topic. For information about how to migrate from an EDP or EAP driver, see Migrating from the Early Access Program or Early Design Program.
You must perform the migration steps in the order that they are listed. You must migrate your database logger and WebSphere MQ Explorer plug-in before migrating any of the agents in your WebSphere MQ File Transfer Edition network.

Procedure

  1. Migrate the WebSphere MQ File Transfer Edition Remote Tools and Documentation installation. The Remote Tools and Documentation installation includes one or many of the following components: the WebSphere MQ Explorer plug-in, the WebSphere MQ File Transfer Edition Information Center, the stand-alone Java™ database logger application, the Java Platform, Enterprise Edition (JEE) database logger application, and the tools to remotely administer WebSphere MQ File Transfer Edition. Perform the following steps, if appropriate for the components you have previously installed on the system:
    1. Optional: If the WebSphere MQ Explorer plug-in is installed, close WebSphere MQ Explorer.
    2. Optional: If the WebSphere MQ File Transfer Edition Information Center is installed, close the web browser that is displaying the information center and ensure that the information center is stopped, by running the install-directory/tools/help/help_end.sh or install-directory/tools/help/help_end.bat command.
    3. Optional: If the tools for remote administration are installed, ensure that all commands have completed.
    4. Optional: If the stand-alone database logger is installed, either upgrade the stand-alone database logger or migrate from the stand-alone database logger to the JEE database logger application. For information about upgrading the stand-alone database logger, see Migrating the stand-alone database logger. For information about migrating to the JEE database logger application, see Migrating from the stand-alone database logger to the JEE database logger.
    5. Back up the Remote Tools and Documentation directory by copying to a new directory. By default, the Remote Tools and Documentation installation is located in the following directory:
      • c:\Program Files\IBM\WMQFTE\tools on Windows platforms.
      • /opt/IBM/wmqfte/tools on UNIX platforms.
      • If the existing level of tools installation is V7.0.3 or earlier /opt/IBM/wmqfte/tools on Linux platforms. For more information, see Installation location on Linux platforms.
      • If the existing level of tools installation is V7.0.4 or later /opt/ibm/wmqfte/tools on Linux platforms. For more information, see Installation location on Linux platforms.
    6. Install the new version of WebSphere MQ File Transfer Edition Remote Tools and Documentation in the same location as the existing installation. When asked if you want to reuse or replace the existing configuration options, select Reuse existing configuration. For information about using the Remote Tools and Documentation installer, see Installing IBM WebSphere MQ File Transfer Edition Remote Tools and Documentation using the graphical installer.
    7. Optional: If the WebSphere MQ Explorer plug-in is installed, start WebSphere MQ Explorer using the command strmqcfg -c.
    8. Optional: If the stand-alone database logger is installed, start the database logger using the command fteStartDatabaseLogger.
  2. Migrate each agent to the new version of WebSphere MQ File Transfer Edition. For each agent perform the following steps. If multiple agents are running on the same system from the same installation of WebSphere MQ File Transfer Edition, you must stop all of these agents before upgrading.
    1. Stop the agent using the fteStopAgent command. The agent will stop when it has completed all currently-running transfers.
    2. Ensure that the agent is stopped using the ftePingAgent command.
    3. Back up the agent installation directory by copying to a new directory. By default, the agent installation is located in the following directory:
    4. Install the new version of WebSphere MQ File Transfer Edition Server or Client installation in the same location as the existing installation, depending on whether the existing installation is a Server or Client installation.
      • Select Refresh existing install, when asked if you want to overwrite the existing installation.
      • Select Reuse existing configuration, when asked if you want to reuse or replace the existing configuration options.
      • If you are migrating WebSphere MQ File Transfer Edition Server from V7.0.3 to a later version, there are no changes to the database schema for the Web Gateway. There is no SQL migration file to run against the database that is used by the Web Gateway.

    5. Optional: If you are migrating from V7.0.1 or earlier, you must create additional security queues for each agent. Run the following MQSC commands against the agent queue manager:
      DEFINE QLOCAL("SYSTEM.FTE.AUTHADM1.agent_name") DEFPRTY(0) DEFSOPT(SHARED) GET(ENABLED) MAXDEPTH(0) +
       MAXMSGL(0) MSGDLVSQ(PRIORITY) PUT(ENABLED) RETINTVL(999999999) SHARE  NOTRIGGER +
       USAGE(NORMAL) REPLACE
      DEFINE QLOCAL("SYSTEM.FTE.AUTHAGT1.agent_name") DEFPRTY(0) DEFSOPT(SHARED) GET(ENABLED) MAXDEPTH(0) +
       MAXMSGL(0) MSGDLVSQ(PRIORITY) PUT(ENABLED) RETINTVL(999999999) SHARE  NOTRIGGER +
       USAGE(NORMAL) REPLACE
      DEFINE QLOCAL("SYSTEM.FTE.AUTHMON1.agent_name") DEFPRTY(0) DEFSOPT(SHARED) GET(ENABLED) MAXDEPTH(0) +
       MAXMSGL(0) MSGDLVSQ(PRIORITY) PUT(ENABLED) RETINTVL(999999999) SHARE  NOTRIGGER +
       USAGE(NORMAL) REPLACE
      DEFINE QLOCAL("SYSTEM.FTE.AUTHOPS1.agent_name") DEFPRTY(0) DEFSOPT(SHARED) GET(ENABLED) MAXDEPTH(0) +
       MAXMSGL(0) MSGDLVSQ(PRIORITY) PUT(ENABLED) RETINTVL(999999999) SHARE  NOTRIGGER +
       USAGE(NORMAL) REPLACE
      DEFINE QLOCAL("SYSTEM.FTE.AUTHSCH1.agent_name") DEFPRTY(0) DEFSOPT(SHARED) GET(ENABLED) MAXDEPTH(0) +
       MAXMSGL(0) MSGDLVSQ(PRIORITY) PUT(ENABLED) RETINTVL(999999999) SHARE  NOTRIGGER +
       USAGE(NORMAL) REPLACE
      DEFINE QLOCAL("SYSTEM.FTE.AUTHTRN1.agent_name") DEFPRTY(0) DEFSOPT(SHARED) GET(ENABLED) MAXDEPTH(0) +
       MAXMSGL(0) MSGDLVSQ(PRIORITY) PUT(ENABLED) RETINTVL(999999999) SHARE  NOTRIGGER +
       USAGE(NORMAL) REPLACE
      Do not use the MQSC scripts that are generated by the installation process, because using these replaces your existing queues and might cause transfers, monitors, or other agent state to be lost.
    6. Start the agent using the fteStartAgent command.

Task Task

Feedback

Timestamp icon Last updated: Tuesday, 30 January 2018
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/migrating_task.htm