corner imagecorner image
FeaturesPluginsDocs & SupportCommunityPartners

Creating a Loan Processing Composite Application

Contributed by and , and maintained by <br>
April 2008

This publication is applicable to NetBeans IDE 6.1, 6.5 and 6.7 releases

This tutorial provides an overview of a simple loan processing composite application and illustrates deploying, executing, and testing of a Composite Application.

Contents

Content on this page applies to NetBeans IDE 6.0 and 6.1

Business Use Case

The loan processing composite application satisfies the following business use case, also illustrated in Figure 1:

  • The user applies for a loan by filling out a loan request, including information such as personal identifying information, amount of loan requested, and credit history.
  • When the loan request is received, the personal information supplied by the user is verified across an existing database, and approval is granted or rejected based on the information and the amount requested.
  • After certain formalities are fulfilled, a report, in the form of an approval letter, is generated and sent to the user, confirming the approval of the loan.
  • If the loan is rejected for some reason, then a report showing the reason for the rejection is generated and displayed.

Figure 1: Loan Processing Use Case

Figure 1: Loan Processing Use Case Diagram

Expected duration: 45 minutes

Tutorial Requirements

Before you proceed, make sure you review the requirements in this section.

Prerequisites

This tutorial assumes that you have some basic knowledge of, or programming experience with, the Java language and platform and the NetBeans IDE.

Software Needed for This Tutorial

To follow this tutorial, you need the following software and resources.

Software or Resource Version Required
NetBeans IDE "All" installation, version 6.1-6.7.
Version 6.7 also requires the SOA and the XML Schema plugins
Java Development Kit (JDK) version 6 or
version 5
Java EE-compliant web or application server GlassFish V2 UR2 for NetBeans 6.1
GlassFish V2 UR1 for NetBeans 6.0

In IDE versions before 6.7, The  Download "All" option includes SOA Pack and the GlassFish V2 Application Server, which are required for this tutorial. In version 6.7, you must install the SOA plugin and the XML Schema plugin separately.

top

Configuring and Starting the GlassFish Application Server

Before you can deploy your application, the GlassFish Application Server must be configured correctly and running.
The "All" NetBeans 6.1 download includes the GlassFish V2 Application Server. When you install NetBeans 6.1, you also install the GlassFish V2.

To start the GlassFish Application Server:

  1. If the Services window is not visible, choose Window > Services.
  2. In the Services window, expand the Servers node.
    The Servers node should contain a GlassFish V2 subnode. If a GlassFish Application Server node does not appear, go to To configure the GlassFish Application Server.

    Graphic shows Service window with GlassFish V2 node expanded


  3. Right-click the GlassFish V2 node and select Start.

    The Output window displays logging information about the application startup. If the Output window is not visible, choose Window > Output > Output.
    When the message Application server startup complete appears in the Output window, the application server is running.

    Note: If a green arrow badge appears on the GlassFish Application Server node, the server is running.

    Did You Know: Deploying an application to the GlassFish Application Server automatically starts the GlassFish. Thus you do not have to manually start the application server.

Selecting an alternative application server:

The following procedure shows how to configure the NetBeans 6.1 IDE to use an alternate version of the GlassFish V2 Application Server. It assumes that you have downloaded and installed the alternate version of the application server.

  1. In the Services window, right-click the Servers node and choose Add Server from the pop-up menu.
    The Add Server Instance dialog box opens.
  2. In the Choose Server page, from the Server drop-down list, select GlassFish V2.
  3. Click Next.
    The Platform Folder Location page opens.
  4. In the Platform Location field, use the Browse button to navigate to and select the installation location of the application server.

    If you installed the GlassFish application server in the default location, then use Table 1 as a guide for locating the installation. Otherwise, navigate to the location where you installed GlassFish V2 Application Server.

    Table 1: Default Application Server Installation Directory

    Platform Installing As... SOA Installation Tools Bundle Installation
    Solaris OS 
    Linux    		 root /opt/SUNWappserver /opt/SDK
    Solaris OS
    Linux    		 user ~/SUNWappserver ~/SDK
    Mac OS X N/A ~/SUNWappserver ~/SDK
    Windows N/A C:\Sun\AppServer C:\Sun\SDK
  5. Select the Register Local Default Domain radio button and click Next.
  6. Enter the user name and password for the domain's administrator.
    If you accepted the default values during the installation, the user name is admin and the password is adminadmin.
  7. Click Finish.

Creating the BPEL Module Project

In this section, you create a BPEL Module project called LoanRequestor.

Important: In NetBeans IDE 6.7, BPEL and XML Schema Editing functionality is NOT installed by default. Open Tools > Plugins and install the "SOA" and "XML Schema and WSDL" plugins. Both are in the SOA category.

To create the LoanRequestor project:

  1. From the NetBeans toolbar, click File > New Project.
    The New Project wizard appears.
  2. In the Categories list, select the SOA node, and in the Projects list, select the BPEL Module node.
  3. Click Next.
  4. In the Project Name field, type LoanRequestor.
  5. (Optional) In the Project Location field, use the Browse button to navigate to and select the location where the IDE will store the project files.
  6. Click Finish.
    The Projects window now contains a project node for a BPEL Module project called LoanRequestor.

top

Creating the XML Schema

In this section, you add a new XML schema file to your BPEL Module project and then add XML schema components to the schema.

To create LoanRequestor.xsd:

  1. In the Projects window, expand the LoanRequestor project node, and right-click the Process Files node and click New > Other.
    The New File wizard appears.
  2. In the New File wizard, do the following:
    1. In the Choose File Type page, select XML as the Category, and XML Schema as the File Type. Click Next.
    2. In the File Name field, type LoanRequestor.
    3. Click Finish.
    In the Projects window, the Process Files node now contains a subnode labeled LoanRequestor.xsd. The Source Editor contains a tab for the XML schema file, LoanRequestor.xsd, with the Schema view open.

  3. In the Schema view, click the Design button to open the Design view of the XML schema editor.

    Graphic shows the new schema file open in Design view of XML Schema Editor

To add complex types to the XML schema:

  1. In the Palette of the Design view, expand the XML Schema Components section and select the Complex Type icon.
    If the Palette window is not visible, choose Window > Palette from the main menu.
  2. Drag your selection to the schema design area to the Complex Types node.
    The IDE adds a Complex Type node and the name of the complex type (newComplexType) is selected and ready for you to change.
  3. Type processApplicType in the new node and press Enter.
    The Design area now shows your new complex type, called processApplicType.
  4. Repeat steps 1 to 3 to create the complex type called processApplicRespType.

    Graphic shows Complex types added in XML schema in the Schema Design area of the Source Editor, as described in context

To add local elements to processApplicType:

  1. In the XML Components section of the Palette, select the Element icon and drag your selection onto the processApplicType node in the schema design area.
    The IDE adds an element node labeled newElement.
  2. If the Properties window is not visible, choose Window > Properties.
  3. In the Schema design area, select the newElement node.
  4. In the Properties window, select the value field of the Name property to make it editable and type socialSecurityNumber.
  5. In the Properties window, set the value field of the Nillable property to True.
  6. In the Properties window, in the Definition property, click the ellipsis button.
    The Definition dialog box opens.
  7. In the list, expand the Built-in Types node, select the string node, and click OK.
  8. Repeat steps 1 to 7 to add the following elements:

    Name Nillable Definition
    applicantName True string
    applicantAddress True string
    applicantEmailAddress True string
    applicantAge True int
    applicantGender True string
    annualSalary True double
    amountRequested True double

To add a local element to processApplicRespType:

  1. In the XML Components section of the Palette, select the Element icon and drag your selection onto the processApplicRespType node in the schema design area.
    The IDE adds an element node labeled newElement.
  2. In the schema design area, select the newElement node.
  3. In the Properties window, select the value field of the Name property to make it editable and type return.
  4. In the Properties window, in the Definition property, click the ellipsis button.
    The Definition dialog box opens.
  5. In the list, expand the Built-in Types node and select the string node.
  6. Click OK.
    When you have added all the local elements to the complex types, your Design view should look similar to the one shown below.

    Graphic shows local elements add to the complex types in the Schema Design area of the Source Editor

To add global elements:

  1. In the XML Components section of the Palette, select the Element icon and drag your selection to the Elements node in the Design area.
    The IDE adds a newElement component below the Elements nodes in the schema design area.
  2. In the Schema design area of the Design view, select the newElement node.
  3. In the Properties window, select the value field of the Name property to make it editable and type processApplicElement.
  4. In the Properties window, in the Definition property, click the ellipsis button.
    The Element's definition - Definition dialog box opens.
  5. In the list of types, expand the Complex Types node and select the processApplicType complex type node.
  6. Click OK.
  7. Repeat steps 1 to 6 to add another global element called processApplicRespElement, and select the processApplicRespType complex type as the definition.

    Image shows Global elements added to XML schema in the Source Editor as described in context

  8. To save your changes, in the Projects window, select the LoanRequestor project node, and from the main menu, choose File > Save All.

top

Creating the WSDL Document

In this section, you add a WSDL file to your BPEL Module project and then configure the components of the WSDL Document.

To create LoanRequestor.wsdl:

  1. In the Projects window, expand the LoanRequestor project node, then right-click the Process Files node and choose New > WSDL Document.
    The New WSDL Document wizard opens.
  2. In the Name and Location page, do the following:
    1. In the File Name field, type LoanRequestor.
    2. Select the Import XML Schema File(s) checkbox.
    3. In the XML Schema(s) field, click the Browse button.
      The Add Import dialog box opens. This dialog box shows the XML schemas you can import.
    4. Expand By File > LoanRequestor > Process Files, and select LoanRequestor.xsd.
      Make sure the checkbox in the Import column is selected for the LoanRequestor.xsd row.

      Graphic shows the New WSDL Document wizard with the LoanRequestor.xsd selected for import, as described in context

    5. Click OK.
    6. In the New WSDL Document wizard, click Next.
    The Abstract Configuration page opens.
  3. In the Input area of the Abstract Configuration page do the following:
    1. In the Message Part Name column, double-click the default value to make the field editable.
    2. Type requestLoanMessage and press Enter.
    3. In the Element Or Type column, click the ellipsis button.
      The Select Element Or Type dialog box opens.
    4. Expand By File > LoanRequestor > src/LoanRequestor.xsd > Elements.

      Note: You may need to scroll up to the top of the list in the Select Element Or Type dialog box to see the By File node.
    5. Under the Elements node, select the processApplicElement node and click OK.
  4. In the Output area of the Abstract Configuration page do the following:
    1. In the Message Part Name column, double-click the default value to make the field editable.
    2. Type responsePart and press Enter.
    3. In the Element Or Type column, click the ellipsis button.
      The Select Element or Type dialog box opens.
    4. Expand By File > LoanRequestor > src/LoanRequestor.xsd > Elements.

      Note: You may need to scroll up to the top of the list in the Select Element Or Type dialog box to see the By File node.
    5. Under the Elements node select processApplicRespElement and click OK.
    The completed Abstract Configuration page should look similar to the one shown below.

    Image shows the completed Abstract Configuration page of New WSDL Document wizard, as described in context. Click to enlarge

  5. Click Finish.
    In the Projects window, the Process Files node now contains a subnode labeled LoanRequestor.wsdl. The Source Editor contains a tab for the WSDL file, LoanRequestor.wsdl, with the WSDL view open.

    Image shows the LoanRequestor WSDL document in the IDE, as described in context. Click to enlarge

top

Opening and Deploying the Partner Web Service

The Loan Application communicates with its partner services via their public interfaces. These interfaces are defined in partner-specific WSDL files.

In this tutorial, you use a J2EE project called LoanProcessor. You can create this project from scratch by following the instructions in Creating the EJB Module Project, or you can download the compressed project files in loanprocessing-loanprocessor.zip. The LoanRequestor project contains a very basic EJB implementation of a partner service.
The partner web service must be deployed to the bundled GlassFish Server before you can test run the LoanRequestorCompositeApp.

This implementation is only meant to serve as a test harness for the Loan Service process.

To open the LoanProcessor project:

  1. Download the loanprocessing-loanprocessor.zip file and extract it into your working directory for the IDE.
    This will create a LoanProcessor project directory.
  2. From the main menu, choose File > Open Project.
    The Open Project wizard opens.
  3. Navigate to the directory where you extracted the project, select the LoanProcessor project, and click Open Project Folder.
    A progress dialog box appears, and then the project appears in the Projects window.

To deploy the LoanProcessor project:

  1. Right-click the LoanProcessor project node and choose Undeploy and Deploy.
  2. Wait until the BUILD SUCCESSFUL message appears in the Output window.
  3. To verify that the LoanProcessor enterprise application is successfully deployed, switch to the Services window.
  4. In the Services window, expand Servers > GlassFish V2 > Applications > EJB Modules.
    A LoanProcessor node has been added. If this node does not appear, the deployment failed.

top

Creating the BPEL Process

To create LoanRequestor.bpel:

  1. In the Projects window, expand the LoanRequestor project node, right-click the Process Files node and select New > BPEL Process.
    The new BPEL Process wizard opens.
  2. In the File Name field, type LoanRequestor.
  3. Click Finish.
    In the Projects window, the Process Files node now contains a subnode labeled LoanRequestor.bpel.
    The Source Editor contains a tab for the BPEL process, LoanRequestor.bpel, with the Design view of the BPEL Designer open.

    Graphic shows the new BPEL process file in the IDE, as described in context. Click to enlarge

To add partner links:

  1. In the Projects window, expand the LoanRequestor project node, then expand the Process Files node and select the LoanRequestor.wsdl node.
  2. Drag your selection (LoanRequestor.wsdl) from the Projects window to the left side of the Design view. The IDE provides you with visual clues to show you where you can drop the selection.
  3. In the LoanRequestor Properties, change the value in the Name field to BpelImplementation.
  4. Accept the other default values (WSDL File = /LoanRequestor.wsdl, Use Existing Partner Link Type radio button selected) and click OK.
  5. In the Projects window, expand the LoanProcessor EJB Module project node, then expand the Web Services node and select the LoanProcessor web service node.
  6. Drag your selection (LoanProcessor web service node) from the Projects window to the Design view. The IDE provides you with visual clues to show you where you can drop the selection.
    The Create New Partner Link dialog box opens.
  7. Change the value in the Name field to EjbImplementation.
  8. Accept the other default values (WSDL File = /Partners/LoanProcessor/LoanProcessor.wsdl, Use a Newly Created Partner Link Type radio button selected) and click OK.
    Notice that the IDE has added a Partners folder under LoanRequestor > Process Files.
  9. Expand the Partners node.
    Notice that this folder contains the LoanProcessor node that includes LoanProcessor.wsdl, LoanProcessorWrapper.wsdl, and LoanProcessor_xsd_1.xsd.

    Image shows Partner links added in the BPEL Editor, as described in context. Click to enlarge

To add a receive activity:

  1. In the Web Service section of the Palette, select the Receive icon and drag your selection to the Design area between the Process Start activity and the Process End activity.
    The IDE provides you with visual clues to show you where you can drop the selection.
    This action places a receive activity called Receive1 in the Design view.
  2. Click the Edit button for the Receive1 activity.
    The Receive1 [Receive] Property Editor opens.
  3. Change the value in the Name field to ReceiveFromCustomer.
  4. From the Partner Link drop-down list, select BpelImplementation.
    The IDE fills in the Operation field with LoanRequestorOperation.
  5. Click the Create button next to the Input Variable field and in the New Input Variable dialog box, accept the default values and click OK.
    This creates a new input variable called LoanRequestorOperationIn.
  6. Click OK to close the Receive1 [Receive] - Property Editor.
    The receive activity is now labeled ReceiveFromCustomer in the Design view and a connection is shown between the BpelImplementation partner link and the receive activity in the LoanRequestor process.

    Image shows the Receive activity added to the BPEL Editor, as described in context. Click to enlarge

To add an invoke activity:

  1. In the Web Service section of the Palette, select the Invoke icon and drag your selection to the Design area below the ReceiveFromCustomer activity.
    The IDE provides you with visual clues to show you where you can drop the selection.
    This action places an invoke activity called Invoke1 in the Design view.
  2. Click the Edit button for the Invoke1 activity.
    The Invoke1 [Invoke] - Property Editor opens.
  3. Change the value in the Name field to InvokeLoanProcessorEJB.
  4. From the Partner Link drop-down list, select EjbImplementation.
    The IDE fills in the Operation field with processApplicOperation.
  5. Click the Create button next to the Input Variable field and in the New Input Variable dialog box, accept the default values and click OK.
    This creates a new input variable called ProcessApplicOperationIn.
  6. Click the Create button next to the Output Variable field and in the New Output Variable dialog box, accept the default values and click OK.
    This creates a new output variable called ProcessApplicOperationOut.
  7. Click OK to close the Invoke1 [Invoke] - Property Editor.
    The invoke activity is now labeled InvokeLoanProcessorEJB in the Design view and a connection is shown between the invoke activity in the LoanRequestor process and the EjbImplementation partner link.

    Image shows an Invoke activity added to the BPEL Editor, as described in context

To add a reply activity:

  1. In the Web Service section of the Palette, select the Reply icon and drag your selection to the Design area below the InvokeLoanProcessorEJB activity.
    The IDE provides you with visual clues to show you where you can drop the selection.
    This action places a reply activity called Reply1 in the Design view.
  2. Click the Edit button for the Reply1 activity.
    The Reply1 [Reply] - Property Editor opens.
  3. Change the value in the Name field to ReplyToCustomer.
  4. From the Partner Link drop-down list, select BpelImplementation.
    The IDE fills in the Operation field with LoanRequestorOperation.
  5. Make sure the Normal Response radio button is selected.
  6. Click the Create button next to the Output Variable field and in the New Output Variable dialog box, accept the default values and click OK.
    This creates a new output variable called LoanRequestorOperationOut.
  7. Click OK to close the Reply1 [Reply] - Property Editor.
    The reply activity is now labeled ReplyToCustomer in the Design view.

    Image shows a Reply activity added to the BPEL Editor, as described in context

To add the CopyCustomerInfo assign activity:

  1. In the Basic Activities section of the Palette, select the Assign icon and drag your selection to the Design area between the ReceiveFromCustomer activity and the InvokeLoanProcessorEJB activity.
    The IDE provides you with visual clues to show you where you can drop the selection.
    This action places an assign activity called Assign1 in the Design view.
  2. If the Properties window is not visible, choose Window > Properties from the main menu.
  3. In the Design view, select the Assign1 activity.
  4. In the Properties window, change the Name property to CopyCustomerInfo.
  5. In the BPEL Editor, select the Mapper button to open the BPEL Mapper window. Make sure that the LoanRequestor.bpel tab is selected.
  6. In the source (left) pane of the BPEL Mapper, expand the Variables > LoanRequestorOperationIn > requestLoanMessage nodes.
    A node is shown for each local element in the processApplicType complex type in the schema you created earlier.

    Image shows the Local schema elements in BPEL Mapper source pane

  7. In the destination pane (the right pane) of the BPEL Mapper, under the Variables node, expand the ProcessApplicOperationIn and parameters nodes.
    The same schema elements are shown as nodes under this parameters node.

    Image shows the Local schema elements in the BPEL Mapper destination pane

  8. Drag socialSecurityNumber from the source pane to the socialSecurityNumber node in the destination pane.
  9. Repeat step 8 for the following variables:
    applicantName, applicantAddress, applicantEmailAddress, applicantAge, applicantGender, annualSalary, and amountRequested.

    Image shows the completed assignment in BPEL Mapper. Click to enlarge

  10. To save your changes, in the Projects window, select the LoanRequestor project node, and from the main menu, choose File > Save All.

To add the CopyLoanStatus assign active

  1. From the BPEL Editor toolbar, select Design to switch to the Design view.
  2. In the Basic Activities section of the Palette, select the Assign icon and drag your selection to the Design area between the InvokeLoanProcessorEJB activity and the ReplyToCustomer activity.
    This action places an assign activity called Assign1 in the Design view.
  3. Select the Assign1 activity.
  4. In the Properties window, change the value of the Name property to CopyLoanStatus.
  5. From the BPEL Editor toolbar, select Mapper to switch to the BPEL Mapper view.
  6. In the source pane of the BPEL Mapper, expand the Variables > ProcessApplicOperationOut > parameters nodes.
    A return node appears under parameters.
  7. In the destination pane of the BPEL Mapper, expand Variables > LoanRequestorOperationOut > responsePart.
    A return node appears under responsePart.
  8. Drag return from the source pane to the return node in the destination pane of the BPEL Mapper.

    Image shows the completed assignment in BPEL Mapper, as described in context. Click to enlarge

  9. To save your changes, in the Projects window, select the LoanRequestor project node, and from the main menu, choose File > Save All.

top

Building the BPEL Module Project

To build the LoanRequestor project:

  • In the Projects window, right-click the LoanRequestor project node and choose Clean and Build Project.
    If a BUILD SUCCESSFUL message appears in the Output window, then the Build has succeeded.

top

Creating the Composite Application Project

Before you deploy the BPEL Module project, you must create a composite application. Deploying the project makes the service assembly available to the application server, thus allowing its service units to be run.

To create the composite application project:

  1. From the main menu, choose File > New Project.
    The New Project wizard opens.
  2. In the Categories list, select the SOA node.
  3. In the Projects list, select the Composite Application node.
  4. Click Next.
  5. In the Project Name field, type LoanRequestorCompositeApp.
  6. Click Finish.
    The Projects window now contains a project node for a Composite Application project called LoanRequestorCompositeApp.

    Image displays the newly added LoanRequestorCompositeApplication Composite Application project listed in the Projects window

top

Using the Composite Application (Service Assembly) Editor

In this section, you use the Composite Application (Service Assembly) editor to modify the project configuration and build the BPEL Module project. You add a WSDL endpoint and a connection, and then verify and change the properties of the auto-generated WSDL endpoints.

To use the Composite Application (Service Assembly) editor to modify the project configuration and build the BPEL Module project:

  1. In the Projects window, expand the LoanRequestorCompositeApp project node. Right-click the Service Assembly node and select Edit from the pop-up menu.
    The IDE opens the .casa file in the Composite Application (Service Assembly) editor. The design area of the Design view of the editor has three parts: WSDL Ports, JBI Modules, and External Modules.

    Note: To invoke the CASA Editor in NetBeans 6.0, right-click the composite application in the Projects window and select Edit Application Configuration.

    Image shows the CASA Editor, design area of the Design view

  2. In the Projects window, select the LoanRequestor project node and drag your selection to the JBI Modules area in the Design view of the LoanRequestorCompositeApp.casa file.

    Image shows a JBI Module added using Composite Application editor. Click to enlarge

  3. In the editor toolbar, click the Build Project button, to build the LoanRequestor BPEL Module project.
    When this step has completed:
    • The Output contains a report of BUILD SUCCESSFUL.
    • The Design view of the LoanRequestorCompositeApp.casa file should look similar to the one shown below.

      Image shows the CASA Editor Design view after BPEL Module project is built, as described in context

To create the WSDL endpoint:

  1. In the WSDL Bindings section of the Palette, select the soap icon.
  2. Drag your selection to the WSDL Ports area in the Design view of the LoanRequestorCompositeApp.casa file.
    The IDE adds a WSDL port labeled casaPort1.

    Image shows the CASA Editor Design view after WSDL endpoint casaport1 is added, as described in context

To create a connection:

  1. In the casaPort1 port in the Design view, click the consume endpoint icon.
  2. Drag your selection to LoanRequestorPortTypeRole_myRole in the (BPEL)LoanRequestor box in the JBI Modules area.
    The IDE creates a new connection.

    Image shows the CASA Editor Design view after adding connection, as described in context

top

Deploying and Testing the Composite Application

You can enhance the Composite Application project by adding test cases, binding to the operation, supplying input, and then using the tester.

To deploy the composite application:

  • Right-click the LoanRequestorCompositeApp project node and choose Deploy Project.
    If the BUILD SUCCESSFUL message appears in the Output window, then the deployment has succeeded.

To add the test case for an approved request:

  1. In the Projects window, expand the LoanRequestorCompositeApp project node, right-click the Test node, and choose New Test Case from the pop-up menu.
    The New Test Case wizard opens.
  2. In the Test Case Name field, type ApprovedTestCase, and click Next.
  3. In the Select the WSDL Document page, expand the LoanRequestorCompositeApp - Process Files node, select LoanRequestorCompositeApp.wsdl, and click Next.
  4. In the Select the Operation to Test page, select the LoanRequestorOperation and click Finish.
    In the Projects window, the IDE has added a new node under the Test node, ApprovedTestCase. This node has two subnodes: Input and Output. The Source Editor contains a tab for the input file, Input.xml.

    The image shows the Input.xml file for the ApprovedTestCase, as described in context. Click to enlarge

    Note: If the Source Editor does not contain a tab for Input.xml, double-click the Input node in the Projects window to open the file.
  5. In the Source Editor tab for the Input.xml file, define the variable values by replacing the Question-marked place holders with the following (bolded) values:
          <loan:socialSecurityNumber>111-11-1111</loan:socialSecurityNumber>
      <loan:applicantName>May JavaOne</loan:applicantName>
      <loan:applicantAddress>1601 Willow Road, Menlo Park, CA 94025</loan:applicantAddress>
      <loan:applicantEmailAddress></loan:applicantEmailAddress>
      <loan:applicantAge>36</loan:applicantAge>
      <loan:applicantGender>female</loan:applicantGender>
      <loan:annualSalary>100000</loan:annualSalary>
      <loan:amountRequested>1000000</loan:amountRequested>
  6. From the main menu, choose File > Save All.
  7. Close the Source Editor tab for Input.xml.

To add the test case for a rejected request:

  1. In the Projects window, expand the LoanRequestorCompositeApp project node, right-click the Test node, and choose New Test Case from the pop-up menu.
    The New Test Case wizard opens.
  2. In the Test Case Name field, type RejectedTestCase, and click Next.
  3. In the Select the WSDL Document page, expand the LoanRequestorCompositeApp - Process Files node, select LoanRequestorCompositeApp.wsdl, and click Next.
  4. In the Select the Operation to Test page, select the LoanRequestorOperation and click Finish.
    In the Projects window, the IDE has added a new node under the Test node, RejectedTestCase. This node has two subnodes: Input and Output. The Source Editor contains a tab for the input file, Input.xml.

    The image shows the Input.xml file for the RejectedTestCase, as described in context. Click to enlarge

    Note: If the Source Editor does not contain a tab for Input.xml, double-click the Input node in the Projects window to open the file.
  5. In the Source Editor tab for the Input.xml file, define the variable values by replacing the Question-marked place holders with the following (bolded) values:
          <loan:socialSecurityNumber>222-22-2222</loan:socialSecurityNumber>
      <loan:applicantName>John Smith</loan:applicantName>
      <loan:applicantAddress>8888 Willow Road, Fremont, CA 94538</loan:applicantAddress>
      <loan:applicantEmailAddress></loan:applicantEmailAddress>
      <loan:applicantAge>15</loan:applicantAge>
      <loan:applicantGender>male</loan:applicantGender>
      <loan:annualSalary>100000</loan:annualSalary>
      <loan:amountRequested>1000000</loan:amountRequested>
  6. From the main menu, choose File > Save All.
  7. Close the Source Editor tab for Input.xml.

To populate the test file with baseline information for ApprovedTestCase:

  1. In the Projects window, double-click the Output node under ApprovedTestCase to examine the contents of the file.
    Notice that initially, Output.xml is empty.

    Image shows the empty Output file for ApprovedTestCase

  2. In the Projects window, right-click the ApprovedTestCase node and choose Run from the pop-up menu.

    Note: The first run is a special case because Output.xml is empty and the IDE cannot compare the test results with the contents of Output.xml. Notice the failed message in the Output window.
    The Overwrite Empty Output? dialog box opens.

    Image show that the first test failed according to JUnit Test Results, as described in context. Click to enlarge

  3. Click Yes.
    The IDE populates Output.xml with default information. This version of the file now contains the baseline information that will be used in subsequent test runs. This version of the file is also known as the "golden" file.

    Image displays the baseline output file created for ApprovedTestCase, as described in context. Click to enlarge

To populate the test file with baseline information for RejectedTestCase:

  1. In the Projects window, double-click the Output node under RejectedTestCase to examine the contents of the file.
    Notice that initially, Output.xml is empty.
  2. In the Projects window, right-click the RejectedTestCase node and choose Run from the pop-up menu.

    Note: The first run is a special case because Output.xml is empty and the IDE cannot compare the test results with the contents of Output.xml. Notice the failed message in the Output window.
    The Overwrite Empty Output? dialog box opens.
  3. Click Yes.
    The IDE populates Output.xml with default information. This version of the file now contains the baseline information that will be used in subsequent test runs.

    Image displays the baseline output file created for RejectedTestCase, as described in context. Click to enlarge

To run the tests:

  1. In the Projects window, right-click the ApprovedTestCase node and choose Run from the pop-up menu.
    Notice that the contents of Output.xml are preserved and are not overwritten by the new result. Double-click the node that represents the passed test (immediately below the Output node) to see the results.

    Image shows the tests passed results, as described in context. Click to enlarge
  2. In the Projects window, right-click the RejectedTestCase node and choose Run from the pop-up menu.
    Double-click the node that represents the passed test to see the results.
  3. In the Source Editor, close all documents.

top

(Optional) Creating the EJB Module Project

In this tutorial, you use a J2EE project called LoanProcessor. You can create this project from scratch by following the instructions in this section, or you can download the compressed project files in loanprocessing-loanprocessor.zip.

To create the EJB Module project:

  1. From the main menu, choose File > New Project.
  2. In the Categories list, select the Enterprise node, and in the Projects list, select the EJB Module node.
  3. Click Next.
  4. In the Project Name field, type LoanProcessor.
  5. (Optional) In the Project Location field, use the Browse button to navigate to and select a different folder where the IDE will store the EJB project files.
  6. Click Next.
  7. In the Server and Settings page, make sure that your selected server is GlassFish V2, and click Finish.
    The Projects window now contains a project node for an EJB Module project called LoanProcessor.

To create a web service:

  1. In the Projects window, right-click the LoanProcessor project node and choose New > Web Service from the pop-up menu.
    The New Web Service wizard opens.
  2. In the New Web Service wizard, do the following:
    1. In the Name and Location page, in the Web Service Name field, type LoanProcessor.
    2. In the Package field, type com.sun.loanprocessor.

      Image shows the Name and Location page of New Web Service wizard completed

    3. Click Finish.
    The IDE creates the web service and opens LoanProcessor in the Source Editor.
  3. In the Projects window, expand the LoanProcessor project node, then expand the Web Services node.
  4. Right-click the LoanProcessor node (the web service) and choose Add Operation.
    The Add Operation dialog box opens.
  5. In the Name field, type processApplicOperation.
  6. In the Parameters tab, add the following seven parameters by clicking the Add button and completing the row that the IDE adds for each parameter.

    Name Type
    socialSecurityNumber java.lang.String
    applicantName java.lang.String
    applicantAddress java.lang.String
    applicantEmailAddress java.lang.String
    applicantAge java.lang.Integer
    applicantGender java.lang.String
    annualSalary java.lang.Double
    amountRequested java.lang.Double

    Image shows the Add Operation dialog box completed, as described in context

  7. Click OK.
  8. In the Source Editor, click the Source button to show the Source view of the LoanProcessor.java file.
    Notice that the IDE has updated the LoanProcessor.java document with a skeleton for the processApplicOperation method.
  9. In the Source Editor, replace 
    	//TODO write your implementation code here:

	return null;
    with the following code:
            int MINIMUM_AGE_LIMIT = 18;
        int MAXIMUM_AGE_LIMIT = 65;
        double MINIMUM_SALARY = 20000;
        int AVERAGE_LIFE_EXPECTANCY = 70;
        String result = "Loan Application APPROVED.";

        // Check age of applicant
        // If less than min age limit, rejected
        if(applicantAge < MINIMUM_AGE_LIMIT) {
            result = "Loan Application REJECTED - Reason: Under-aged " +
                    applicantAge +
                    ". Age needs to be over " +
                    MINIMUM_AGE_LIMIT +
                    " years to qualify.";
            System.out.println(result);
            return result;
        }

        // Check age of applicant
        // If more than max age limit, rejected
        if(applicantAge > MAXIMUM_AGE_LIMIT) {
            result = "Loan Application REJECTED - Reason: Over-aged " +
                    applicantAge +
                    ". Age needs to be under " +
                    MAXIMUM_AGE_LIMIT +
                    " years to qualify.";
            System.out.println(result);
            return result;
        }

        // Check annual salary
        // If less than min salary, rejected
        if(annualSalary < MINIMUM_SALARY) {
            result = "Loan Application REJECTED - Reason: Annual Salary $" +
                    annualSalary +
                    " too low. Annual Salary needs to be over $" +
                    MINIMUM_SALARY +
                    " to qualify.";
            System.out.println(result);
            return result;
        }

        // Calculate the years to pay off loan based on applicantAge
        int yearsToRepay = AVERAGE_LIFE_EXPECTANCY - applicantAge;

        // Calculate the max amount of loan based on years to pay off loan
        double limit = annualSalary * yearsToRepay * 0.5;

        // Check amount requested, if higher than limit, rejected
        if(amountRequested > limit) {
            result = "Loan Application REJECTED - Reason: You are asking for too much $" +
                    amountRequested +
                    ". Annual Salary $" +
                    annualSalary +
                    ", Age " +
                    applicantAge +
                    " years. Your limit is $" +
                    limit;
            System.out.println(result);
            return result;
        }
        System.out.println(result);
        return result;
  10. To save your changes choose File > Save from the main menu.
  11. (Optional) Close the LoanProcessor tab in the Source Editor.
  12. Return to Opening and Deploying the Partner Web Service.

top

Next Steps

  • To send comments and suggestions, obtain support, and stay informed of the latest changes to the NetBeans IDE J2EE development features, join the mailing list.



See Also


top