Structure of a payment plug-in
A payment plug-in consists of the following items:
- A payment plug-in EJB module. This module implements financial transactions.
- A payment plug-in descriptor. This XML file describes the plug-in and contains descriptions of static data or data used at initialization. It includes the protocol metadata description (the supported payment actions and parameters).
- (Optional) A payment plug-in utility JAR module. Most of the payment protocol manipulation and wrapping is done through this JAR file. The JAR file contains the classes necessary to help the plug-in EJB module work. The payment plug-ins provided with WebSphere Commerce do not use a plug-in utility JAR file.
- (Optional) A payment plug-in messages bundle. This bundle contains an explanation of return codes. Messages are translated to languages supported by WebSphere Commerce. It also includes a properties file with explanations, descriptions, and recommended actions for return codes. The WCPayment plug-in uses a messages bundle. The SimpleOffline plug-in and LOC plug-in do not use a messages bundle.
To see an example of a plug-in, refer to the SimpleOffline plug-in or LOC plug-in.
(C) Copyright IBM Corporation 1996, 2006. All Rights Reserved.