2.4 Working with the SOA Order Booking Application Code in Oracle JDeveloper

Once you have opened the applications in Oracle JDeveloper, you can then begin to review the artifacts within each application. The development environment for the SOA Order Booking application is divided into two applications: the SOADEMO application and the SOADEMO-CLIENT application.

Note: For the purposes of the demo, all code is delivered in a preconfigured development environment. In a real-world development environment, you would not have access to much of this code. Instead, you would be given only WSDL files for the different applications with which you need to integrate. Additionally, in many cases, the code for the applications is not indicative of a real-world application, and contains only the functionality needed to demonstrate integrating within an SOA framework. For example, the code for the customer service application is very rudimentary, and exists as a project in the same application as the credit service application. In actuality, the credit service application would exist at a company external to Global Company.

2.4.1 The SOADemo Application

The SOADEMO application contains separate projects, which in turn contain the code for the different applications used in the SOA Order Booking demonstration application.

2.4.1.1 The CreditService Project

The credit service application resides in the CreditService project. Figure 2-7 shows the CreditService project and its associated directories:

Figure 2-7 The CreditService Project

This project contains the following directories:

• Application Sources: Contains the CreditService web service generated from a provided wsdl file, the actual CreditService.wsdl file, along with an EAR file that contains the actual CreditService application that is deployed to the application server.

• Resources: Contains the deployment configuration file.

• Web Content: Contains the files needed to deploy a web service. These are automatically generated when creating web services from WSDL files in Oracle JDeveloper.

For information about creating web services from provided WSDL files, see Section 5.2.6, "How to Create a Top-Down Web Service". For information about how the CreditService project is used at runtime, see Section 2.5.3.3.3, "CreditService Scope".

2.4.1.2 The CustomerService Project

The customer service application resides in the CustomerService project. Figure 2-8 shows the CustomerService project and its associated directories.

Figure 2-8 The Customer Service Project

This project contains the following directories:

• Application Sources: Contains the source for the customer service application.

• Resources: Contains the deployment configuration file.

For information about using Enterprise JavaBeans (EJB) to create a service, see Chapter 4, "Building and Using Application Services". For information about how the CustomerService project is used at runtime, see Section 2.5.1, "Registration Process", Section 2.5.2, "The Login Process", and Section 2.5.3.3.2, "CustomerService Scope".

2.4.1.3 The FulfillmentESB Project

The files required for the fulfillment ESB flow reside in the FulfillmentESB project. Figure 2-9 shows the FulfillmentESB project and its associated directories.

Figure 2-9 The FulfillmentESB Project

This project contains the following directories:

• Application Sources: Contains the source for the code for the FedexShipment application that populates the FEDEXSHIPMENT table.

• Offline Database Sources: Representations of the tables used by the database adapter.

• Resources: Contains the files for the ESB flow, including schemas and WSDL files.

For information about using ESB, see Chapter 6, "Using Oracle Enterprise Service Bus". For information about how the FulfillmentESB project works at runtime, see Section 2.5.3.4, "OrderFulfillmentESB Flow".

2.4.1.4 The OrderBookingESB Project

The files required for the OrderBooking ESB flow reside in the OrderBookingESB project. Figure 2-10 shows the OrderBookingESB project and its associated directories.

Figure 2-10 The OrderBookingESB Project

This project contains the following directories:

• Resources: Contains all the files for the ESB flow.

For more information about using ESB, see Chapter 6, "Using Oracle Enterprise Service Bus". For information about how the OrderBookingESB project works at runtime, see Chapter 2, "The OrderBookingESB Flow".

2.4.1.5 The RapidService Project

The application that allows Rapid Manufacturer to provide prices back to the flow resides in the RapidService project. Figure 2-11 shows the RapidService project and its associated directories.

Figure 2-11 The RapidService Project

This project contains the following directories:

• Application Sources: Contains the web service to Rapid Manufacturer.

• Resources: Contains the deployment configuration file.

• Web Content: Contains the files needed to deploy a web service. These are automatically generated when creating web services in Oracle JDeveloper.

For information about creating a web service from a Java class, see Section 5.2.3, "How to Create a Bottom-Up Web Services". For information about how the RapidService project works at runtime, see Section 2.5.3.3.6, "SelectSupplier Scope".

2.4.1.6 The SelectManufacturer Project

The files required for the SelectManufacturer BPEL flow reside in the SelectManufacturer project. Figure 2-12 shows the SelectManufacturer project and its associated directories.

Figure 2-12 The SelectManufacturer Project

This project contains the following directories:

• Integration Content: Contains the files for the BPEL flow, including sensors, test suites, and WSDL files.

• Resources: Contains the deployment files.

For more information about BPEL flows, see Chapter 7, "Using Oracle BPEL Process Manager". For information about how the SelectManufacturer project works at runtime, see Chapter 2, "SelectSupplier Scope".

2.4.1.7 The SOAOrderBooking Project

The files required for the OrderBooking BPEL flow reside in the SOAOrderBooking project. Figure 2-13 shows the SOAOrderBooking project and its associated directories.

Figure 2-13 The SOAOrderBooking Project

This project contains the following directories:

• Application Sources: Contains the source for the application that populates the ORDERS and ITEMS tables, and updates the status.

• Integration Content: Contains the files for the BPEL flow, including sensors, test suites, and WSDL files.

• Offline Database Sources: Representations of the tables used by the database adapter.

• Resources: Contains the deployment files and directories for the decision service, which is used to invoke business rules.

• Web Content: Contains the files for the manual approval web page.

For more information about BPEL flows, see Chapter 7, "Using Oracle BPEL Process Manager". For information about how the SOAOrderBooking project works at runtime, see Section 2.5.3.3, "SOAOrderBooking BPEL Flow".

2.4.2 The SOADemo-Client Application

The SOADEMO-CLIENT application contains projects for the web client application. The files required for the web client reside in the SOADEMO-CLIENT application.

2.4.2.1 The Assembly Project

The Assembly project contains all the files necessary to deploy the web application. Figure 2-14 shows the Assembly project and its associated directories.

Figure 2-14 The Assembly Project

This project contains the following directories:

• Application Sources: Contains the files necessary for deployment.

• Resources: Contains the EAR file.

For information about deploying web applications, see Chapter 11, " Deploying SOA Applications with Enterprise Manager".

2.4.2.2 The ClientModel Project

The ClientModel Project contains the classes that allow the product data to be displayed in the web application. Figure 2-15 shows the ClientModel project and its associated directories.

Figure 2-15 The ClientModel Project

This project contains the following directories:

• Application Sources: Contains the files used to access the product data. Included are the metadata files used by Oracle Application Development Framework (ADF) to bind the data to the view.

• Resources: Contains a file used in deployment.

For information about creating classes that use the Java Persistence API to manage data, see Section 4.2, "Creating JPA Entities that Map to Database Tables". For information about using ADF in web applications, see Chapter 9, "Developing a Web Application in an SOA System".

2.4.2.3 The CustomerService Project

The CustomerService project contains the proxy classes for the customer service application. Figure 2-16 shows the CustomerService project and its associated directory.

Figure 2-16 The CustomerService Project

The project contains the Application Sources directory, which holds the proxy to the customer service application. For information about creating web service proxies, see Section 5.3.1, "How to Create a Web Service Proxy".

2.4.2.4 The OrderService Project

The OrderService project contains the proxy classes used to send order information into ESB. Figure 2-17 shows the OrderService project and its associated directory.

Figure 2-17 The OrderService Project

The project contains the Application Sources directory, which holds the proxy to the web service that invokes the OrderBookingESB, along with the files generated when you create the proxy. For information about creating web service proxies, see Section 5.3.1, "How to Create a Web Service Proxy".

2.4.2.5 The UserInterface Project

The UserInterface project contains the files for the web interface, including the backing beans, deployment files, and JSPX files. Figure 2-18 shows the UserInterface project and its associated directories.

Figure 2-18 The UserInterface Project

This project contains the following directories:

• Application Sources: Contains the code used by the web client, including the managed and backing beans, property files used for internationalization, and the metadata used by ADF to display bound data.

• Resources: Contains the files used to deploy the application.

• Web Content: Contains the web files, including the JSP files, images, skin files, deployment descriptors, and libraries.

For more information about creating web clients, see Chapter 9, "Developing a Web Application in an SOA System".