Migrate > Take the first steps after WebSphere Commerce migration > Migrating from a previous payment implementation

Migrate from WebSphere Commerce Payments Multipayment Framework to a payment plug-in

To migrate from WebSphere Commerce Payments Multipayment Framework to a payment plug-in configure a payment policy. You also need to disable the payment policy used for the cassette from displaying on shopping pages.

Select this migration scenario if you use WebSphere Commerce Payments Multipayment Framework and to use a payment plug-in.

Procedure

1. To determine the payment policy name used by the payment cassette, query the POLICY table. For example:

   select policy_id, policyname, policytype_id, storeent_id, properties from policy where policytype_id = 'Payment' and policyname ='VISA'
   

   The output will be similar to this example:

   POLICY_ID	POLICYNAME	POLICYTYPE_ID	STOREENT_ID	PROPERTIES
   10004	'VISA'	'Payment '	10001	'profileName=WC51_OfflineCard&cassetteName=OfflineCard&attrPageName=StandardCreditCard&display=true&compatibleMode=true'

2. Query the POLICYDESC table:

   select policy_id, language_id, description, longdescription from policydesc 
      where policy_id in (select policy_id from policy where policytype_id = 'Payment' and policyname = 'VISA') and language_id = -1 
   

   The output will be similar to this example:

   POLICY_ID	LANGUAGE_ID	DESCRIPTION	LONGDESCRIPTION
   10004	-1	'VISA Credit Card'	'VISA Credit Card'

3. Configure the old payment policy so that it is no longer displayed on shopping pages:

   update policy set PROPERTIES='profileName=WC51_OfflineCard&cassetteName=OfflineCard&attrPageName=StandardCreditCard&
           display=false&compatibleMode=true'
   

4. Query the POLICY table to determine an unused payment policy_id: select max(policy_id)+1 as policy_id from policy

   The number returned is referred to as newPolicyID in the following steps.

5. Insert the payment policy in the POLICY table. In this example, the policy name is VISACard.

   insert into policy (policy_id,policyname,policytype_id,storeent_id,properties) values(newPolicyID,'newPolicyName','Payment',yourStoreId,
            'attrPageName=StandardVisa&paymentConfigurationId=default&display=true&compatibleMode=false');
   

6. Insert the payment policy in the POLICYDESC table. The description will display to shoppers on shopping pages.

   insert into policydesc (POLICY_ID,LANGUAGE_ID,DESCRIPTION,LONGDESCRIPTION) 
               values(newPolicyID,-1,'VISA Card Payment','VISA Card Payment');
   

   Repeat this step for each language that the store supports.

7. Register the policy commands for the payment policy:

   insert into policycmd (policy_id, businesscmdclass) values (newPolicyID, 'com.ibm.commerce.payment.actions.commands.DoPaymentActionsPolicyCmdImpl') 
   insert into policycmd (policy_id, businesscmdclass) values (newPolicyID, 'com.ibm.commerce.payment.actions.commands.EditPaymentInstructionPolicyCmdImpl') 
   insert into policycmd (policy_id, businesscmdclass) values (newPolicyID, 'com.ibm.commerce.payment.actions.commands.QueryPaymentsInfoPolicyCmdImpl')
   

   Where:

   newPolicyID

   Is the policy_ID you entered in step 5.

   This step enables the payment policy to use the Payment plug-in controller.

8. Configure a payment plug-in.
   

What to do next

You must use WebSphere Commerce Payments in compatibility mode for any transactions that have not completed at the time of migration.

• Convert custom V5.x payment task or policy command implementations to a payment plug-in
  To convert custom implementations of the V5.x payment task commands (that is, DoPaymentCmd, DoDepositCmd) or payment policy commands (that is, DoPaymentPolicyCmd, DoDepositPolicyCmd) to a payment plug-in:

Related concepts

Payment plug-ins

LOC (Line of credit) plug-in

SimpleOffline plug-in

WCPayments plug-in

Related reference

Replacement commands for WebSphere Commerce Payments Multipayment Framework commands

+

Search Tips   |   Advanced Search