This chapter covers the following topics:
Oracle One-to-One Fulfillment supports only the third-party application Captaris RightFax for sending collateral by fax. Use the following procedures to integrate these two applications.
Integrate Oracle One-to-One Fulfillment with RightFax in the following sequence:
Install RightFax Enterprise Server.
Install fax board driver from RightFax fax board driver CD-ROM.
Configure IIS to create virtual directory to support rfwebcon.dll.
If the fulfillment server is running, use the server start/stop script to shutdown the server.
Download the RightFax zip file from the following URL:
http://www.captaris.com/support/downloads/rightfax/9/index.html#Oracle
The file Oracle_Patch.zip contains java API from Captaris and is required to be in the CLASSPATH for the One-to-One Fulfillment server in order to process a fax or print request successfully.
The administrator should copy this zip file to a location where the Fulfillment server is able to access it. The recommended location is $OA_JAVA/3rdparty directory.
The fully qualified path to Oracle_Patch.zip should be appended to the Fulfillment server CLASSPATH. Verify that there is no reference to the older versions of RightFax zip file RFJavaInt.zip in the Fulfillment server CLASSPATH.
Configuration change is now complete. Use the server start/stop script to start the server. One-to-One Fulfillment server is now ready to process fax requests.
The design of the Fulfillment Server allows the user to define a fax solution based on a static API call. This fax solution, written in Java, is called from the Server as specified in the startup script. If the class exists, the Fulfillment Server loads the specified class file and associated class files, with all supporting classes, in the classpath. The Fulfillment Server then matches the class name in the startup property definition -Dengine.FaxEnabler=your.fax.Enabler with the startup script. The class your.fax.Enabler is the user-defined fax solution. To use this class with the Fulfillment Server, the class must meet two requirements:
Have a default constructor without parameters.
Implement the interface oracle.apps.jtf.fm.engine.disp.FaxEnabler (available in the apps.zip file).
The oracle.apps.jtf.fm.engine.FaxEnabler interface has one method,
public String faxContents(String Sender,
String SenderFax,
String SenderPhone,
String SenderCompany,
String Recipient,
String RecipientFax,
String RecipientPhone,
String RecipientCompany,
String Message,
HtmlContent[] Contents)
throws EnablerFailedException;
Sender is the person who is sending the fax. This should be defined as an optional field that can take the empty string "" as an argument value.
SenderFax is the fax number of the person sending the fax. This should be defined as an optional field that can take the empty string "" as an argument value.
SenderPhone is the phone number of the person sending the fax. This should be defined as an optional field that can take the empty string "" as an argument value.
SenderCompany is the company of the person sending the fax. This should be defined as an optional field that can take the empty string "" as an argument value.
Recipient is the person who will be receiving the fax. This should be defined as an optional field that can take the empty string "" as an argument value.
RecipientFax is the fax number that will be dialed to send the fax. This parameter must have a value.
RecipientPhone is the phone number of the person who is to receive the fax. This should be defined as an optional field that can take the empty string "" as an argument value.
RecipientCompany is the company of the person who is to receive the fax. This should be defined as an optional field that can take the empty string "" as an argument value.
Message is the message that appears on the cover sheet of the fax being sent. This should be defined as an optional field that can take the empty string "" as an argument value.
Contents are the actual contents to fax.
The design of the Fulfillment Server allows the user to define a print solution that is based on a static API call. This print solution, written in Java, will be called from the Server as specified in the startup script. The Server will load the specified class file and associated class files (assuming that the class exists), with all supporting classes, in the classpath. The Server recognizes the class name from the startup property definition '-Dengine.PrintEnabler=your.print.Enabler' in the Server startup script; the class 'your.print.Enabler' being the user-defined print solution. To use with the Fulfillment Server, this class must meet two requirements:
It must have a default constructor; one that has no parameters.
It must implement the interface 'oracle.apps.jtf.fm.engine.disp.PrintEnabler' (available in the apps.zip file).
The 'oracle.apps.jtf.fm.engine.PrintEnabler' interface has one method:
public String printContents(String PrinterName, HtmlContent[] Contents)
throws EnablerFailedException;
PrinterName is the name/alias of the Printer to send the print job to.
Contents are the actual contents that are to be printed.