Validating composite controls
Composite sensor data is persisted in the database during runtime, enabling you to search for all authorized or denied payments.
Composite sensors enable you to perform the following tasks: The composite sensor is defined on the inbound SOAP web service binding component, as shown in Figure 3-14. Company X can create proxies, pipelines, and business services by dragging icons from the Components window on the right into the designer.
A key area for improvement is the need to streamline the ordering process to provide better order tracking visibility through the following parts of the ordering life cycle: A key issue in their current system is that credit card payments are often denied for minor reasons.
Since the process to correct these issues varies across Company X's order entry systems, there is no consistent follow-up and resolution to customers.
If the credit card number is not available in the database, payment is denied.The consolidated credit validation service is to be initially hosted in-house to control quality.However, once the interface is stabilized, this service is to be outsourced to a third party provider.The database adapter retrieves credit card payment information from the database, using the customer's credit card number as the key.The validation process includes three steps: Company X creates a BPEL process service component in the SOA composite application.