Deprecated feature

Migrating Payments application using one machine

This type of migration will have both your previous version of WebSphere Commerce Payments and WebSphere Commerce Payments, Version 7.0 running on the same machine. For example, if you have a previous version of Payments application, then you can migrate the application to WebSphere Commerce, Version 7.0 Payments level on the same machine and use it. Whether both the original application and the migrated application can run concurrently on the same machine depends on if they use same database and Web server port number.

Procedure

  1. Optional: Complete this step if both of the following conditions are true: WebSphere Commerce and WebSphere Commerce Payments are on the same machine; and you are not using IBM HTTP server.
    1. Verify if the web server plugin path to the WebSphere Commerce instance is set to the default Plugin installation directory. For example, drive:/WebSphere/Plugins/config/webserver1/plugin-cfg.xml.
    2. If it is, change the Web server plugin path to the WebSphere Commerce instance profile directory. For example, C:/WebSphere/AppServer/profiles/commerce_instance_name/config/WC_commerce_instance_name_cell/nodes/WC_commerce_instance_name_node/servers/webserver1/plugin-cfg.xml
  2. SolarisLinuxAIX The WCIM utility will connect to the migrated Payments database. Ensure that the user running WCIM can access this database.
  3. Back up your previous Payments application.
    1. SolarisLinuxAIX Switch to a non-root user, for example wasuser.
    2. Navigate to the following directory:
      • WC70_installdir/bin
    3. Run the following script:
      • SolarisLinuxAIXFor IBM i OS operating system
        ./wcim.sh -component wpm -from previous_version
          -action backup -instanceName payments_instance_name
        
      • Windows
        wcim.bat -component wpm -from previous_version
          -action backup -instanceName payments_instance_name
        
      Where:
      previous_version
      is either wcp561 or wcp60.
      payments_instance_name
      is the name of your previous Payments instance.
      The script prompts you for the following input:SolarisLinuxWindowsAIX
      • The location of the previous Payments installation directory for example, WCP561_installdir or WCP60_installdir.
      • The location of the previous Commerce installation directory for example, WC561_installdir, or WC60_installdir.
      • The location of the previous WebSphere Application Server installation directory for example, WAS511_installdir, WAS60_installdir, or WAS61_installdir.
      • The previous WebSphere Application Server node name.
      For IBM i OS operating system
      • The previous WebSphere Application Server installation directory. Enter the value that applies to your installation directory:
        • /QIBM/ProdData/WebAS5/Base
        • /QIBM/ProdData/WebAS51/Base
        • /QIBM/ProdData/WebAS5/ND
        • /QIBM/ProdData/WebAS51/ND
        • /QIBM/ProdData/Websphere/AppServer/V6/Express
        • /QIBM/ProdData/Websphere/AppServer/V6/Base
        • /QIBM/ProdData/Websphere/AppServer/V6/ND
        • /QIBM/ProdData/Websphere/AppServer/V61/Express
        • /QIBM/ProdData/Websphere/AppServer/V61/Base
        • /QIBM/ProdData/Websphere/AppServer/V61/ND
  4. Migrate the Payments application.
    1. If there is third-party or custom cassette installed for the old instance, copy the content in the Old_WC_installdir/payments/cassettes/cassetteName directory to the New_WC_installdir/payments/cassettes/cassetteName directory. If the third-party or custom cassette provides an installation script, install the cassette to the new New_WC_installdir.
    2. Run the following script:
      • SolarisLinuxAIXFor IBM i OS operating system
        ./wcim.sh -component wpm -from previous_version -action migrate -instanceName payments_instance_name 
      • Windows wcim.bat -component wpm -from previous_version -action migrate -instanceName payments_instance_name

      The script prompts you for the following items. Provide the values for your system as responses to the prompts:

      • Whether a new Web server host name is used for the new instance. If yes, you are prompted for the new Web server host name (specify a fully-qualified host name including port number).
      • Whether the new Web server is remote for the new instance? If yes, you are promoted for:
        • Remote IBM HTTP Server install path (For example, c:\IBMHTTPServer7)
        • The remote Web server configuration file path (For example, c:\IBMHTTPServer7)
        • The remote WebSphere plugin installation path (For example, c:\ibm\websphere\plugins)
        Note:
        • You must specify the path. If the new remote Web server is IBM HTTP server, the newly generated configuration file will be placed here using FTP or to be copied using a mapped remote path.
        • If you select to copy the generated httpd.conf file and plugin-cfg.xml file to the remote Web server host, you need to map the remote path to the local machine.
      • The WebSphere Application Server node name.
      • The new Payments instance name
      • The old Payments instance name
      • The password for the new Payments instance.
      • The Payments database name.
      • Enter the database user ID.
      • The Payments database user password.
      • The host name of the associated WebSphere Commerce application (specify a fully-qualified host name)
  5. SolarisLinuxWindowsAIX Configure the Web server for the migrated Payments application. WCIM only supports the configuring of IBM HTTP Server Version 6.0 or later. For other type of Web server, you need to configure them manually.
    1. Run the following script, the example configures Web server for your migrated Payments application with minimal options:
      • SolarisLinuxAIX./wcim.sh -component wpm -from previous_version -action config -instanceName payments_instance_name
      • Windows wcim.bat -component wpm -from previous_version -action config -instanceName payments_instance_name

      The WCIM script will prompt you for the following items. Provide the values for your system as responses to the prompts:

      • Enter your previous Payments instance name
      • Enter your migrated Payments instance name
      • Whether a new Web server will be used. If yes is entered, you will be prompted to input the new Web server hostname. If no is entered, the original Web server hostname will be extracted from the previous_payments_instance.xml file.
      Running the WCIM command will configure the IBM HTTP Server for your Payments application to Version 7.0 level. If the Web server is local, the newly created httpd.conf file is located in the following directory:
      • SolarisLinuxAIX WC70_installdir/instances/new_PMInst_Name/httpconf/httpd.conf
      • Windows WC70_installdir\instances\new_PMInst_Name\httpconf\httpd.conf

      If the Web server is remote from Payments application, the httpd.conf will be placed under the remote config file path specified when migrating the application.

    2. After Web server is configured, check the newly configured httpd.conf file to ensure the configuration is correct before starting the migrated Payments instance.
      If your previous version of Payments uses the default port numbers 80 and 443, the WCIM utility used to migrate Payments will change the port numbers to the default WebSphere Commerce Payments ports, 5432 and 5433. If your previous Payments does not use the default ports 80 and 443, WCIM does not change the port numbers to the WebSphere Commerce Payments default ports.
      Note: If you use ports 5432 or 5433 for other applications you will experience port conflicts when you start WebSphere Commerce Payments.

What to do next

Post payments application and database tier migration steps.