Implementation Guide for Oracle Self-Service E-Billing > Customizing Payment >

Packaging Oracle Self-Service E-Billing Payment Custom Code

You can package your custom code, both plug-in code and custom A/R jobs and templates, by adding it to Payment_custom.jar. The Oracle Self-Service E-Billing Payment EAR files will access this JAR, and find the custom code. The Oracle Self-Service E-Billing Payment EAR files merge into the Command Center EAR file as part of installation, so your custom code will also be seen by the Command Center.

To make this JAR file accessible by all of the Oracle Self-Service E-Billing Payment EJB, JAR and WAR files, place it in the classpath of the MANIFEST file of each JAR and WAR file. For details of how the MANIFEST file works, refer to the J2EE or EJB specifications or the SDK: Customizing and Deploying Applications document that comes with the Command Center SDK. When the EJB JAR or WAR files are loaded, this JAR will be loaded and can be accessed by the EJB JAR files or WAR files.

CAUTION:  Never put your custom EJB code into Payment_custom.jar; put your EJB code in your own JAR files.

To write a new plug-in for IAchCheckSubmitPlugIn

1. Write and then compile your implementation class. You might want to use Payment_common.jar and Payment_client.jar from Oracle Self-Service E-Billing Payment as part of your class path.
2. Create a JAR file called Payment_custom.jar, or use the Payment_custom.jar from any of the Oracle Self-Service E-Billing Payment EAR files. Place your implementation class into that JAR file using the JAR command.
3. Replace all the Payment_custom.jar files under the lib directory of all the deployed Oracle Self-Service E-Billing Payment EAR files with the new Payment_custom.jar, using JAR command.
4. Deploy the new Oracle Self-Service E-Billing Payment EAR files on your application server.
5. Go to Payment Settings in the Command Center, and configure the payment gateways to use the new class by replacing the default one, com.edocs.payment.cassette.ach.AchCheckSubmitPlugIn, with your new plug-in.
6. Run the pmtCheckSubmit job, which will load the new class from Payment_custom.jar, because you added it to the classpath of the MANIFEST file of ejb-Payment-chksubmit.jar.