Migrate Payments application using two machines

(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 two machines, using WCIM are:

1. Backing up your previous Payments application

2. Transferring the back up zip file and ear file to your target machine

3. Migrate Payments application using WCIM.

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

 

 

Backing up your previous Payments application

If you will be migrating your existing Payments application to another machine, you will first need to back up your existing Payments application. The backup will then be copied over to the WebSphere Commerce 6.0 machine where it will be migrated. 1. On your previous Payments machine, run wcimRemoteBackup to backup your existing instances from the following directory:

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

• (Windows)WC60_installdir/bin

Notes :

• Install the Remote WebSphere Commerce Management Utilities component on the the previous version WebSphere Commerce machine. For details on how to install the WebSphere Commerce Management Utilities component, refer to the WebSphere Commerce , version 6.0 Migration Guide, section "Migrating the application"->"Backing up the application".

• For Linux, AIX, Solaris platform, run wcimRemoteBackup with non-root user, for example, wasuser.

The syntax for running wcimRemoteBackup.sh/bat is described in WCIM utility. The following command backs up your current Payments application without any special options (this is sufficient for most migrations)

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



(Windows) wcimRemoteBackup.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.

• (i5/OS)

• 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

• Run the wcimRemoteBackup script produces the following zip file on the previous version payments machine:

• (i5/OS)WC60_userdir/temp/zip/your_backup_file

• (Linux)(AIX)(Solaris)WC60_installdir/temp/zip/your_backup_file

• (Windows)WC60_installdir\temp\zip\your_backup_file
  where your_backup_file is either wcbackupwpm55.zip, wcbackupwpm56.zip, wcbackupwpm561.zip. And the following EAR file:

• (i5/OS)WC60_userdir/temp/zip/payments_instance_Commerce_Payments_App.ear

• (Linux)(AIX)(Solaris)WC60_installdir/temp/zip/ payments_instance_Commerce_Payments_App.ear

• (Windows)WC60_installdir\temp\zip\ payments_instance_Commerce_Payments_App.ear

• WCIM generates log files in the following directory on the previous version Payments machine :

• (i5/OS)WC60_userdir/logs/WCIM/payments_instance

• (Linux)(AIX)(Solaris)WC60_installdir/logs/WCIM/payments_instance

• (Windows)WC60_installdir\logs\WCIM\payments_instance

Review the contents of the log file to make sure that no problems were encountered.

 

Transferring the back up zip file and ear file to your target machine

After you have performed the backup of your previous Payments application:
Copy the generated zip file and ear file for example, wcbackupwpm55.zip and wpm_Commerce_Payments_App.ear, to the following directory on your target WebSphere Commerce Payments v6 machine:

• (i5/OS)WC60_userdir/temp/zip

• (Linux)(AIX)(Solaris)WC60_installdir/temp/zip

• (Windows)WC60_installdir\temp\zip

The backup zip file was generated on the previous Payments machine, in an earlier step.

Do not unpackage the .zip file. The WCIM script that is run in the next step will handle the extracting.

 

Migrate Payments application using WCIM

Run the WCIM script (with any optional flags that may be required) from the following directory:

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

• (Windows)WC60_installdir\bin

The following WCIM command migrates your current Payments application with minimal options:

 
(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

where previous_version is either wcp55, wcp56, or wcp561 and payments_instance is the previous Payment instance name.

Run the WCIM command will migrate your Payments application to the WebSphere Commerce Payments, v6 level.

WCIM requires access to the backup zip file, for example,wcbackupwpm55.zip in the subdirectory under the migration working directory. The working directory is set to either WC60_installdir or WC60_userdir depending on your operating system.

(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 (Enter yes).

• The Web server host name (specify a fully-qualified host name).

• Whether the new Web server is remote for the new instance? (

  This prompt will only be shown if yes was answered previously)

• The current WAS node name.

• The new Payments instance name.

• Whether a new db2 schema will be used for the new instance.

• The new db2 schema of the new payments database (

  This prompt will only be shown if yes was answered previously)

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

• Enter the database user ID

• The Payments database user password.

• If the payments database is remote

• The host name of the associated WebSphere Commerce instance (specify a fully-qualified host name).

• Messages are posted during the migration of the Payments application. When the migration is completed, similar messages, as the following, are posted:

  • WebSphere Server Application Server console for the profile can be accessed at port 9,162.

  • Event: WCIM has completed the job(s) successfully.

  
  

  Record the port number listed in the message above.

(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 (Enter yes).

• The Web server host name (specify a fully-qualified host name).

• Whether the new Web server is remote for new instance. Default is no. If "yes", it will ask for the remote IBM HTTP Server install path (For example, c:\IBMHTTPServer6), IBM HTTP Server config file path (For example, c:\IBMHTTPServer6. The path must be specified because the newly generated config file will be placed here via FTP or be copied via mapped remote path), and 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 to remote Web server host, map the remote path to local.

• The new WAS node name (the default is your current host name).

• The old Payments instance name (type in the name of your old version payments instance)

• The Payments instance password. (

  This password must be the same as the previous Payments password in Payments 5.5, 5.6, or 5.6.1.)

• If the new Payments instance name you enter 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.)

• When the dbtype is db2, it will ask whether a new db schema owner will be used for the migrated payment database.

• The migrated Payments database name for the Payments applicatoin.

• The migrated Payments database User ID.

• The migrated Payments database password. (

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

• The migrated Payments database location. Answer yes for remote database, no (default) for local database. When the Payments database type is Oracle, you need input the Oracle database hostname and port.

• 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 Web servers, 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 older_version
-action config -instanceName payments_instance

(Windows) wcim.bat -component wpm -from older_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, prompt you input the new Web server hostname. Otherwise, the old Web server hostname will be extract from previous_payments_instance.xml.

Run the WCIM command will configure the IBM HTTP Server for your Payments application to v6 level. If the Web server is in local, then 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

• Migrate Payments application using one machine

• Post Payments application and database tier migrating steps