Integrate Cyber source with IBM WebSphere Commerce 7.0

Below are the steps to be followed to integrate:
1. Place cybsclients15.jar and cybssecurity.jar in WC\lib (ALL ENV)
The above jars are shared by CyberSource which helps to integrate with any system.
2. Place cybs.properties, opsm_au.p12, opsm_nz.p12 in Toolkit\wasprofile (LOCAL ENV) & /app/IBM/WebSphere/AppServer/profiles/ (Server ENV)
cybs.properties - is the Configuration File where all the key value pairs to integrate with CyberSource (Sandbox/Production) system.
keysDirectory=./
targetAPIVersion=1.28
sendToProduction=
_country=
_merchantID=
.p12 keys provided by Cybersource which acts as an authentication token to interact with CyberSource Gateway
3. PaymentSystemPluginMapping.xml
  LOCAL ENV
3.1 Go to WC_eardir/xml/config/payments/ppc/plugins/ PaymentSystemPluginMapping.xml & Add/Check if the below tag is present
  Server ENV
3.2  Go to /app/IBM/WebSphere/AppServer/profiles//installedApps///xml/config/payments/ppc/plugins/PaymentSystemPluginMapping.xml
 <PaymentSystemName name="XXXXXXXXX">
        <Mapping paymentConfigurationId="default" pluginName="WCPaymentsPlugin">
            <Property name="ProfileName" value="WCPPlugin_XXXXXXXXXX"/>
            <Property name="SupportsOnlineTransaction" value="yes"/>
            <Keyword mask="-" name="cc_cvc" plain="0" removeAfterApproval="true"/>
            <Keyword mask="*" name="cc_nameoncard" plain="0" removeAfterApproval="true"/>
            <Keyword mask="*" name="account" plain="-5" searchable="true"/>
        </Mapping>
    </PaymentSystemName>

4. PluginDeployment.xml
  LOCAL ENV
4.1  Keep back up of PluginDeployment.xml & rename and place PluginDeployment_CS.xml in this location WC\xml\config\payments\ppc\plugins\CyberSourcePlugin\PluginDeployment.xml
  Server ENV
4.2 Same as above, path  /app/IBM/WebSphere/AppServer/profiles//installedApps///xml/config/payments/ppc/plugins/CyberSourcePlugin
5. PaymentMethodConfiguration.xml
  LOCAL ENV
5.1 Go to WC_eardir/xml/config/payments/edp/groups/default/ PaymentMethodConfigurations.xml & Add/Check if the below tag is present
  Serveer ENV
5.2 Go to /app/IBM/WebSphere/AppServer/profiles//installedApps///xml/config/payments/edp/groups/default/PaymentMethodConfigurations.xml
maximumAmount="Unbounded" minimumAmount="0"
name="CreditCardOnline" partiallyConsumable="true"
paymentSystemName="CyberSourceSystem" priority="MEDIUM"
refundAllowed="true" systemEditable="true"/>
6. PaymentMappings.xml
  LOCAL ENV
6.1 Go to WC_eardir/xml/config/payments/edp/groups/default/ PaymentMappings.xml & Add/Check if the below tag is present
Serveer ENV
6.2 Go to /app/IBM/WebSphere/AppServer/profiles//installedApps///xml/config/payments/edp/groups/default/PaymentMappings.xml
paymentConfiguration="CreditCardOnline" paymentMethod="VISA"/>
paymentConfiguration="CreditCardOnline" paymentMethod="Master Card"/>
paymentConfiguration="CreditCardOnline" paymentMethod="AMEX"/>
7. Certificates
7.1. Log into the administrative console.
7.2 Expand Security and click SSL certificate and key management. Under Configuration settings, click Manage endpoint security configurations.
7.3 Select the appropriate outbound configuration to get to the (cell):WC_OPSMCI_cell:(node):WC_OPSMCI_node management scope.
7.4 Under Related Items, click Key stores and certificates and click the NodeDefaultTrustStore key store.
7.5 Under Additional Properties, click Signer certificates and Retrieve From Port.
7.6 In the Host field, enter ics2wstest.ic3.com in the host name field; enter 443 in the Port field, and CyberSourceTestCertificate in the Alias field.
7.7 Click Retrieve Signer Information.
7.8 Verify that the certificate information is for a certificate that you can trust.
7.9 Click Apply and Save.
RESTART YOUR SERVER
You also need to make Database Configuration, so that IBM WCS interacts with the database configured and then interact with the Payment Gateway.
Check if entries are present in MERCHANT, STOREMERCH, MERHCONF, MERHCONFINFO tables.