Chapter Use Case

In this chapter, we pick up where we left off in the use case of Chapter 5. In Chapter 3, we went through the steps required to create the topology with the pricing application deployed to its own cluster, its web interface accessible through a fronting OHS instance, and its web service interface secured using OWSM. In Chapter 4, we proceeded to configure this domain with a central LDAP server and to configure it for Single Sign-On (SSO). In Chapter 5, we deployed to this domain a SOA Suite composite that orchestrates the integration of the pricing application’s model update web services with the corporate ERP system and exposes updated data through Oracle BAM.

In this section, we will deploy the PricingWorkList ADF application. As described in the use case section of Chapter 3, the web services interface of the pricing application exposes a single operation named modifyModel, which is used to modify the pricing model for a given product. A business process is executed every time changes occur to the company’s ERP system that can affect the pricing application’s business parameters. The process reads the change event and translates it to the parameters required by the Pricing Update web service and then invokes the web service in order to ensure that the changes are reflected within the pricing application’s business model. Depending on the nature of the changes involved, the process in some cases involves an approval from the specialty product’s product management team before proceeding with the update of the pricing model. The Pricing WorkList application has the user interface where the specialty product’s product management team approves these changes to the business parameters. The topology of the application is illustrated in Figure 6-11.