Page History

...

1. Put payflow.jar from Payflow Pro's Java SDK in the directory in

   No Format
   ${ofbiz install dir}applications/accounting/lib.

   
   
2. Change the accounting build.xml and comments to not exclude verisign sources like here :
   <!- - <exclude name="org/ofbiz/accounting/thirdparty/verisign/**"/> - ->
3. Confirm that applications/accounting/build/classes/org/ofbiz/accounting/thirdparty/verisign/PayflowPro.class was built and exists
4. The installation of certificate is now no more necessary
5. Go to Accounting - Payment Gateway Config and select "Payflow Pro Payment Gateway" from the list
6. Please fill all those fields to made working correctly to work with Payflow Pro:
   
   Certs Path : Path the the VeriSign Certificate (No more used from version v4)
   Host Address : Address of the payment processor (example (Test pilot-payflowpro.paypal.com or Production payflowpro.paypal.com)
   Host Port : Port of the payment processor (default is 443)
   Timeout : Timeout (default is 80 seconds)
   Proxy Address : Proxy Address
   Proxy Port : Proxy Port (default is 80)
   Proxy Logon : Proxy Logon
   Proxy Password : Proxy Password
   Vendor : Vendor of account information
   User Id : PayFlow UserID of account information
   Pwd : PayFlow Password of account information
   Partner : PayFlow Partner of account information
   Check Avs : Use Address Verification
   Check Cvv2 : Require CVV2 Verification
   Pre Auth : Pre-Authorize Payments (if set to N will auto-capture)
   Enable Transmit : Set to false to not transmit anything
   Log File Name : Log file name
   Logging Level : Logging level
   Max Log File Size : Max log file size
   Stack Trace On : Stack trace on/off
7. Once Payflow Pro Payment Gateway has been configurated you have to go to Catalog - Stores - select your Store - Payments tab
   
8. Edit the Payment Method Type Credit Card and after selected a Service Type (Authorize, Capture, ...) you can choose the Custom Method related to the Service Type choosen and as Payment Gateway Config Id "Payflow Pro Config".
   

...

1. Put cybsclients15.jar, cybssecurity.jar and xalan.jar from CyberSource SDK in the directory in

   No Format
   ${ofbiz install dir}applications/accounting/lib/cybersource.

   
   
2. Change the accounting build.xml and comments to not exclude verisign sources like here :
   <!-- <exclude name="org/ofbiz/accounting/thirdparty/cybersource/**"/> -->
3. Confirm that applications/accounting/build/classes/org/ofbiz/accounting/thirdparty/cybersource/IcsPaymentServices.class was built and exists
4. The installation of certificate is requested and you can follow the instructions into the CyberSource Certificate Update manual.
5. Go to Accounting - Payment Gateway Config and select "CyberSource Payment Gateway" from the list
6. Please fill all those fields to made working correctly to work with CyberSource:
   
   Merchant Id : your merchant Id
   CyberSource API version : target API version (now is 1.43)
   Directory of the keys from CyberSource : Generate using online tools
   Name of the keystore : keystore file name (default is "merchantID".p12)
   Log transaction information : log activated true/false (default is true)
   Log directory : Log directory (default is runtime/logs)
   Log File Name : Log file name (default is cybersource.log)
   Max log size : Megabytes allowed for the log file
   Merchant Description : Shown on credit card statement Vendor
   Merchant Description Contact Information : Shown on credit card statement Vendor
   Auto-Bill In Authorization : Capture automatically true/false (default is false)
   Use DAV In Authorization : May not be supported any longer
   Use Fraud Scoring In Authorization : May not be supported any longer
   Ignore AVS results : Ignore Address Verification Service true/false (default is false)
   Disable AVS for Capture : May not be supported any longer
   AVS Decline Codes : May not be supported any longer
7. Once CyberSource Payment Gateway has been configurated you have to go to Catalog - Stores - select your Store - Payments tab
   
8. Edit the Payment Method Type Credit Card and after selected a Service Type (Authorize, Capture, ...) you can choose the Custom Method related to the Service Type choosen and as Payment Gateway Config Id "CyberSource Config".
   

...

Marketing overview

Anchor
marketingSetup marketingSetup

The overal purpose of the Marketing component is the support to select leads from parties obtained from a certain source or marketing segment to convert to opportunities by contacting these parties via a contact-list related to a marketing campaign.

The first option of the marketing component is the definition of a datasource \[DataSource\], and connecting or loading party information to it \[PartyDataSource\]. In the party component a data source Id can be added to the party.

A second input to the marketing component is the Segment group and classification which again can be allocated to parties in the party component.

Now a marketing campaign can be created. A contact list can be created using the parties related to a datasource or marketing segment classification and referring back to the marketing campaign

Contact lists are currently email mailinglists, the OFBiz system could be extended to inlcude the support of calling by telephone and entering the results. On the email sent via this lists tracking codes can be used to measure the reponse when the readers of the email mailing click on a link where a trackingcode is specified.
For more info look at the program: applications/marketing/src/org/ofbiz/marketing/tracking/TrackingCodeEvents.java

Opportunities resulting from these actions can be entered in the SFA component referring back to the marketing campaign.text now maintained within ofbiz, check http://demo.ofbiz.org/cmssite/cms/APACHE_OFBIZ_HTML#N200F2