Migrate Payments application using one machine

(Linux)(AIX)(Solaris) WCIM will connect to the migrated Payments database, so ensure that the user running WCIM can access this database.

The basic steps for Payments application tier migration involving one machine, using WCIM are:

1. Backing up your previous Payments application

2. Migrate Payments application using WCIM

3. Configure Web server for the migrated Payments application using WCIM

 

 

Backing up your previous Payments application

To back up your previous Payments application, run WCIM by specifying the -backup flag from the following directory:

• (i5/OS)(Linux)WC60_installdir/bin

• (Windows)WC60_installdir/bin

For Linux, AIX, Solaris platforms, run wcim.sh with non-root user, for example, wasuser.

(i5/OS)(Linux)(AIX)(Solaris)  ./wcim.sh -component wpm -from previous_version
-action backup -instanceName payments_instance

(Windows) wcim.bat -component wpm -from previous_version
-action backup -instanceName payments_instance

where

• previous_version is either wcp55, wcp56 or wcp561.

• payments_instance is the name of your previous Payments instance.

You are prompted for the following inputs:

• (Linux)(Windows)(AIX)(Solaris)

• The location of the previous Payments installation directory for example, WCP55_installdir, WCP56_installdir, or WCP561_installdir.

• The location of the previous Commerce installation directory for example, WC55_installdir, WC56_installdir, or WC561_installdir.

• The location of the previous WAS installation directory for example, WAS50_installdir, or WAS511_installdir.

• The previous WAS node name.

• 

• Enter the previous WAS installation directory.

• Enter one of the following which ever is applicable to your environment: /QIBM/ProdData/WebAS5/Base /QIBM/ProdData/WebAS51/Base /QIBM/ProdData/WebAS5/ND /QIBM/ProdData/WebAS51/ND

   

  Migrate Payments application using WCIM

  Run WCIM, specifying migrate with the -action flag. For example:

  
  
  
  (i5/OS)(Linux)(AIX)(Solaris) ./wcim.sh -component wpm -from previous_version -action migrate
  -instanceName payments_instance
  
  

  
  
  
  (Windows) wcim.bat -component wpm -from previous_version -action migrate
  -instanceName payments_instance
  
  

  
  

  (i5/OS) The WCIM script will prompt 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).

  • Whether the new Web server is remote for the new instance? (As this is not supported on i5/OS, please enter no.)

  • The WAS node name.

  • The new Payments instance name. (type in the name of your previous payments instance)

  • The Payments database name (use the WRKRDBDIRE command).

  • 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)

  (Linux)(Windows)(AIX)(Solaris) The WCIM script will prompt 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 Web server host name (specify a fully-qualified host name).

  • 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:\QIBMHTTPServer6)

    • IBM HTTP Server configuration file path (For example, c:\IBMHTTPServer6

    • )

    The path must be specified as the newly generated config file will be placed here via FTP or be copied via mapped remote path

    • Remote WebSphere plugin install path (For example, c:\ibm\websphere\plugins).

    If you select to copy the generated httpd.conf file and plugin-cfg.xml file to the remote Web server host, map the remote path to local.

  • The new WebSphere Commerce Server node name (the default is your current host name).

  • The old Payment instance name

  • The new Payments instance name

  • If the new Payments instance name you entered already exists, WCIM will prompt you to enter another new instance name. (

    The instance name is no more than 12 characters, otherwise WCIM will prompt you to enter another new instance name.)

  • The Payments instance password. (

    This password must be the same as the previous WebSphere Commerce Payments password.)

  • Whether the previous Payments instance and the new Payments instance are using the same database server. If yes, WCIM will then prompt you to enter a different database name for DB2 databases, or a different service ID for Oracle databases.

  • When the dbtype is db2, here ask whether a new db schema owner will be used for the migrated payment database. If yes, you will be prompted to input the new db schema owner.

  • The migrated Payments database name for the migrated application.

  • Enter the database user ID.

  • The Payments database password. (

    The database password must be the same as the password for the previous Payments database.)

  • The host name for the associated WebSphere Commerce instance (the default is your current host name).

   

   

  Configure Web server for the migrated Payments application using WCIM

  1. WCIM only supports the configuring of IBM HTTP Server version 6.0 or later. For other type of Web server, configure them manually.

  2. This step is not needed for iSeries.

  To configure Web server for the migrated Payments application, run the WCIM script (with any optional flags that you might require for your instance) from the following directory:
  
  

  (Linux)(AIX)(Solaris)WC60_installdir/bin
  
  

  (Windows)WC60_installdir\bin
  

  The following WCIM command configures Web server for your migrated Payments application with minimal options:

  
  
  (Linux) (AIX) (Solaris) ./wcim.sh -component wpm -from previous_version -action config -instanceName payments_instance
  
  
  
  (Windows) wcim.bat -component wpm -from previous_version -action config -instanceName payments_instance
  
  

  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.

  Run the WCIM command will configure the IBM HTTP Server for your Payments application to v6 level. If the Web server is local, the newly created httpd.conf file is located in the following directory:

  
  
  (Linux) (AIX) (Solaris) WC60_installdir/instances/new_PMInst_Name/httpconf/httpd.conf
  
  
  
  
  
  (Windows) WC60_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.

  After Web server is configured, the user needs to check the newly configured httpd.conf to ensure the configuration is correct before starting the migrated Payments instance.

  Related tasks

  • Run the WCIM utility

  • Migrate Payments application using two machines

  • Post Payments application and database tier migrating steps