Adxstudio Portals ecommerce payment processing integrates with the Pay Pal payment service provider's Classic API - Pay Pal Payments Standard.This method allows the portal to control the payment flow and does not require the portal to store credit card information which simplifies PCI compliance.Although Google Analytics is free, it can be tricky getting the Ecommerce section to provide you with the kind of data you need to track specific transactions.As you may know, when Ecommerce analytics work you can see things like: When you have data like this, it helps in making decisions about pricing, product lines, shipping, locations to target and much more. Click Website Payment Preferences in the Seller Preferences column. Scroll down to the Payment Data Transfer section of the page to view your PDT identity token. For a list of issues and workarounds pertaining to Oracle SOA Installation, Upgrade, High Availability, Enterprise Deployment, Performance Tuning, and Web Services, as well as SOA on IBM Websphere, see the Oracle Fusion Middleware Release Notes.For known issues and workarounds for other Oracle SOA releases, see Known Issues for Oracle SOA Products.The portal will require SSL for secure processing of the payment response and the website must be publicly visible for Pay Pal to be able to post a response back to verify the payment.
You must also acquire a PDT identity token, which is used in all PDT communication you send to Pay Pal. Modify your identity token and your Google Analytics UA number and you should be good to go with the above code. Curiously, we are working on a Pay Pal to Google Analytics Tracker Wizard that does the bulk of this coding for you.
However, the documentation has a note which reads "The EDN does not support durable subscriptions (whether they are backed by native AQ or Oracle Web Logic Server JMS).
The subscribing service component must be running to receive events."This note in the documentation is outdated and in the documentation and is not valid anymore.
Bug: 22628159Added: 05-May-2017Platform: All SOA Suite 12.1.3 version supports SHA2.
While renaming a service component or binding component artifact, you cannot rename SOA Projects and Composites as opposed to what is stated in the documentation.