Step 2: Creating a payments cassette plug-in

In this part of the tutorial you will create the payments cassette plug-in. In order to create the plug-in, you do know the following prerequisite tasks:

This tutorial uses WebSphere Commerce Developer as the development tool.

To create the payments cassette plug-in, do the following tasks:

  1. In WebSphere Commerce Developer, create a new EJB project
    1. Click File > New > EJB Project.
    2. In the Name field, type Payments-Plugin-MyWCPayments.
    3. For EJB version, select 2.0.
    4. Select Add module to an EAR project.
    5. For EAR project, select WC.
    6. Click Finish.

  3. In the Project Explorer:
    1. Click Payments-Plugin-MyWCPayments.
    2. Select Project > Properties.
    3. Add the Java JAR dependencies for WebSphereCommerceServerExtensionData.jar and lib/payment/etilCal.zip:
      • Select the check boxes and click OK.
    You should add any jar files that you want your plug-in to use WebSphereCommerceServerExtensionData.jar enables you to use any class in IBM WebSphere Commerce, including the Payments-Plugin.jar.


  4. Create an Enterprise Bean:
    1. Select the Payments-Plugin-MyWCPayments project.
    2. Select File > New > Enterprise Bean.
    3. Select Session Bean.
    4. In the EJB Project field, select Payments-Plugin-MyWCPayments.
    5. In the Bean name field, type MyWCPaymentsPlugin.
    6. In the source folder field, select ejbModule.
    7. In the Default package field, type com.ibm.commerce.payments.plugin.mywcpayments.bean .
    8. Click Next.

  6. In the Enterprise Bean Details page, in the Session type field, select Stateless. In the Transaction type field, select Container. Select Remote client view and click Next.


  7. In the "Which interfaces should the remote interface extend?" field, type com.ibm.commerce.payments.plugin.QueryablePlugin. Click Finish.


  8. Now that you have a session bean payment plug-in created, add the logic for your design to the MyWCPaymentsPluginBean.java. For this tutorial, you just import the files from the attached Payments-Plugin-MyWCPayments.jar file and override the source code when you import the project.
  9. For the NLV messages, you should create the properties files for your payment plug-in. In this tutorial, the MyWCPaymentsPluginErrorMessages_*.properties files are included in Payments-PluginPayments-Plugin-MyWCPayments.jar\com\ibm\commerce\payments\plugin\mywcpayments\util
  10. Create the payment plug-in descriptor or other configuration files required by your payment plug-in. For the payments cassette plug-in, you need PluginDeployment.xml, and cassette profiles to connect to the old implementation of WebSphere Commerce Payments. They are included in Payments-Plugin-MyWCPayments.jar. Copy the MyWCPaymentsPlugin directory and its content to the following directory:WCDE_installdir\xml\config\payments\ppc\plugins
  11. Generate deployment code for the enterprise bean MyWCPaymentsPlugin:
    In J2EE perspective,
    1. Select the Payments-Plugin-MyWCPayments>Deployment Descriptor:Payments-Plugin-MyWCPayments>Session Beans>Payments-Plugin-MyWCPayments to highlight it.
    2. Right-click and select deploy.
  12. Build the Payments-Plugin-MyWCPayments project in WebSphere Commerce Developer if your Rational Application Developer environment is not configured to build automatically.
  13. Republish WebSphere Commerce Test Server.
You have created "MyWCPaymentsPlugin" and you are ready to test it in IBM WebSphere Commerce Developer. You must set up the remote Payment server (which is the old implementation of IBM WebSphere Commerce Payments) on another machine and configure your WebSphere Commerce Developer to use the remote payment server.

In the next step of the tutorial you will learn how to configure the remote payment instance.

(C) Copyright IBM Corporation 1996, 2006. All Rights Reserved.