Deploying to a production environment
You have completed the previous steps in a toolkit environment for the convenience of development and unit testing. You can now deploy to a WebSphere Commerce production environment.
Follow the same steps as above, but consider the following points that are different from completing the steps in the toolkit environment:
- When deploying the Payments-Plugin-PayPal project in the toolkit, you need to import and add the project to the WebSphere Commerce modules. For the runtime environment, you need to package the Payments-Plugin-PayPal project from the toolkit to a JAR file (see Packaging Java EE assets for an entire module in the Information Center), and then deploy it to the WebSphere Commerce server as an EJB (see Deploying J2EE assets for an entire module in the Information Center).
- For the Importing PayPal’s digital certificate section, you need to export and import the certificate using the real PayPal express check out URL (https://www.paypal.com) instead of the Sandbox's URL.
- Register a real PayPal account instead of a Sandbox testing account if you want to use the PayPal payment method for online stores. Then configure the USER, PWD, and SIGNATURE of the real PayPal business account as the merchant configuration information.
- Remember to change the following parameters in
PluginDeployment.xml, according to the host name of the WebSphere
Commerce server and the real PayPal express check out URL. Refer
to the PayPal Checkout Integration Guide on how to request the
<PluginProperty name="initializationBaseURL" value="https://api-3t.sandbox. paypal.com/nvp" /> <PluginProperty name="authenticationBaseURL" value= "https://www.sandbox.paypal.com/cgi-bin/webscr" /> <PluginProperty name="RETURNURL" value="http://localhost/webapp/wcs/stores/ servlet/PunchoutPaymentCallBack" /> <PluginProperty name="CANCELURL" value="http://localhost/webapp/wcs/stores/ servlet/PunchoutPaymentCallBack" />
- For ExtPunchoutPaymentCallBackCmdImpl.java, put the class file in the same package as the runtime's WebSphereCommerceServerExtensionsLogic.jar as a patch.