Instant Oracle BPM for Financial Services How-to

Launch the terminal and run the following command:

cd /home/james/Oracle/Middleware/Oracle_SOA1/common/bin
[james@james bin]$ ./config.sh

This will launch the domain configuration wizard. Select the option to create a new Domain.

Select Oracle WebCenter Spaces, Oracle BPM Suite for developers, Oracle SOA Suite for developers, Oracle Universal Content Management, Oracle BAM, and Oracle Enterprise Manager. Once you have done that, click on Next.

Select all the component schemas and give the corresponding DBMS/ service names, database port numbers, and schema passwords. Once you have done that, click on Next.

Create a domain with the name fmw_domain, and then click on Finish.

Once again launch the domain creation wizard, and this time extend fmw_domain and patch it up with the oracle.bpm.spaces_template_11.1.1.jar template to enable BPM Process Spaces within WebCenter.

Edit process-portal-install.properties in the /home/james/Oracle/Middleware/Oracle_SOA1/bpm/process_spaces folder, and run the Ant script as shown in following command:

/home/james/Oracle/Middleware/modules/org.apache.ant_1.7.1/bin/ant -f install.xml

Log in to Enterprise Manager (http://localhost:7001/em) and configure Content Server with its default intradoc server port, 4444, and a UCM connection in WebCenter.

Restart all the Managed Servers, Admin Server, WebCenter, Oracle Business Activity Monitoring (BAM), and the Content Server.

Launch JDeveloper and create a new BPM application.

Name the application as JamesBank and then click on Next.

Name the project as LoanEligibilityProj and then click on Next.

In Project SOA Settings, select Composite with BPMN Process.

Select Synchronous Service and name it as LoanEligibilityProcess.

Change to the BPM Project Navigation view and select LoanEligibilityProcess.

Create a business object and name it as EligibilityBO. Create a new destination module and name it as Module. Select Based on External Schema; this schema then needs to be picked from the schema browser. This is where we need to pick up eligibilityRequest from the jamesbank.xsd schema file.

Similarly, create another business object and name it as EligibilityRespBO. This maps to the eligibilityResponse element of the jamesbank.xsd schema.

Now we need to create input and output argument definitions. Name the input arguments as inputArgs.

Similarly, create outputArgs that maps to the EligibilityRespBO business object.

Under Process Data Objects, create a new process data object and name it as EligibilityPDO.

Similarly, create EligibilityRespPDO that maps to the Module.EligibilityRespBO component.

From the Component Palette, drag-and-drop a Business Rule component between the start and end activities of the BPM process and name it as EligibilityRule.

Create a new business rule by clicking on the + icon to the right of the Business Rule field and name it as EligibilityBR.

Pass input and output parameters from the process data objects.

Edit the business rule in the Rules Editor:

The user submits a loan request at the Start event.

EligibilityRule gets fired. This determines various rule parameters based on the business rule defined in the previous section.

A decision is made as to whether the applicant is eligible or not. If the applicant is not eligible, the process ends.

If the applicant is a Platinum customer, a special discount is offered and a notification is sent to the loan officer as a heads up.

If the customer is from the Platinum, Gold, Silver, or Bronze category, then the process moves ahead for further modeling, which will be discussed in next recipe. At this stage, we can leave that as a "not implemented" activity or mark it as Is Draft.

Deploy the business process to SOA Administration Server.

Let us log in to Enterprise Manager (http://localhost:7001/em) as weblogic, and run the process by selecting LoanEligibilityProj.

Provide the following test inputs:

The output of this process will be a Platinum customer, which can be viewed from the Audit Trail and Flow tabs. The green line in the flow denotes a happy path or the path taken by the process for the given input data.

Log in to Oracle Database as the SYS user.

Create the JAMESBANKDB user and grant all the required create table, create trigger, and create sequence privileges to this user.

Log in as JAMESBANKDB.

Create the procedure to calculate EMIs and write the data in the database table.

Compile and Run the Insert Eligibility procedure. This procedure will insert the eligibility data into a table, calculate the EMI amount for fixed and variable rate of interest, and also return a unique ID for the eligibility request.

Launch JDeveloper and open the James Bank application developed in the previous recipe.

Open composite.xml in the Design view.

In the External References area on right side in the Design view, insert a Database Adapter service.

Set up the necessary database connection parameters:

Test the connection and proceed if it is successful.

In the Adapter Configuration Wizard, select the Call a Stored Procedure or Function operation type.

From the configuration wizard, select the EMI Calculator stored procedure.

Open the LoanEligibility process in the Design view, and change the EligibleCustomers activity into a service task, and make it active (earlier it was marked as draft).

Select the Database Adapter service that we have created in the service list.

Now click on Data Associations and ensure that the necessary input and output parameters are passed.

Save the process and deploy on SOA Suite.

Generate a web service-based Application Development Framework (ADF) data control by using the deployed WSDL URL, and drag-and-drop it on the JSPX page.

Right-click and Run the JSPX page to test the web service from the browser by giving necessary input parameters, and then clicking on the Check Eligibility button, as shown in the next screenshot.

Launch JDeveloper and create a new project under the James Bank application. Name this project as LoanApplicationProj.

Create input arguments, output arguments, business objects, and business process data objects.

Map all the request objects to the loanRequest element of the schema, and map all the response elements to the loanResponse element of the schema.

Create LoanApplicant, VerificationOfficer, FieldOfficer, and FinanceOfficer swimlanes on the process canvas, which can be seen in the extreme left vertical lane in the Flow tab. Each of these represents a participant role.

Switch to the BPM Project Navigator view and open the Organizational Chart roles. Add the required actors as discussed in the preceding use case for each of the swimlane roles.

Drag-and-drop a task initiator from the Component Palette on the LoanApplicant BPM process swimlane.

Create the Loan Application human task and associate it with the loanRequest process data object as an input parameter.

Select Loan Application Task and click on Auto-Generate Task Form….

Add a parallel task and link up AgencyVerification and Application Verification Officer, so that they merge again at the ParallelGateway endpoint.

Add an exclusive gateway to check if the customer is a Platinum customer. If yes, take the customer to a subprocess (Partner Loan Request Process) which is marked as Is Draft, for later implementation.

If the customer is not a Platinum customer, then the process moves to the next human task—Finance Approval.

Save the loan application data in the required database table by using a Database Adapter at the Save Loan Application service invocation.

Finally, send an e-mail notification to the customer by dragging and dropping the Email notification activity.

Deploy the application to WebLogic Server from JDeveloper.

Log in to BPM Workspace (http://localhost:7001/bpm/workspace) as James Cooper (loan applicant).

He checks for loan eligibility, fills in the required data, and submits the form.

He also attaches required documents such as proof of age, proof of address and salary slips that get checked into the UCM content repository.

John Steinbeck—who is the Field Officer—visits James Cooper's home and office, and approves the Loan Application Task in the BPM Workspace application.

Jack London—who is the Application Verification Officer—has access to the corporate intranet WebCenter Portal. He logs in and verifies all the related documents such as Income Tax Permanent Account Number (PAN), address proof, and employment certificate and provides his approval on them.

After login, he selects his group space related to home loans and views the task assigned to him in the process workflow:

He then selects Application Verification Task assigned to him and verifies the documents. Once done, he clicks on the Approve or Reject button to approve or reject the application based on his verification of the documents.

William Faulkner—who is the Finance Officer at James Bank—gives the final approval, and the loan is sanctioned to James Cooper.

Launch JDeveloper and open the Application Verification Task human task.

Click on the Deadlines tab, and in the Task Duration Settings field, change the value of the Escalate after drop-down list to 7 days.

To set up an escalation rule, from the Task Duration Settings field, select the Expires after drop-down list and then in the Fixed Duration drop-down list, set the value to 5 working days. One can also set the escalation process to notify the manager if no action is taken within a specified time.

We can also set up document management capabilities for the document that has been checked in. To do this, enable the document package under the documents tab.

In this process, we will set AgencyVerification to have a fixed cost of $100. Similarly, we can set up a number of process instances to be simulated based on time and cost on a given task.

In JDeveloper, click on the BPM Project Navigator tab.

Then under Simulations, create a new simulation model named LoanSimulationModel.

Save the simulation model.

Create a new simulation definition named LoanSimulationDefinition based on the current simulation model. We can also specify start and end times, and there can also be multiple processes simulated in one simulation definition.

Run the simulation model by clicking on the green run button located in the process simulation taskbar below the process canvas.

Launch JDeveloper and open BPM MDS Navigator from the View menu.

Configure a new BPM MDS connection.

Create a database connection with username as DEV_MDS and password as welcome1, and test the connection.

Similarly, select the application server connection that we created earlier during the process deployment, and set the MDS partition to obpm. Again, test the connection

Select the connection for the SOA MDS section and test the BPM MDS connection.

In the BPM Project Navigator view, right-click on the project and save LoanApplicationProj to BPM MDS.

Log in to BPM Composer as the weblogic user and select the LoanEligibilityProj project.

Open the EligibilityBR business rule. Here we can update the business rules as required or add new conditions.

To change a business rule, select the Globals tab where we have defined fixed and variable rate of interests.

Now edit the rate of interests. We will change the fixed rate of interest from 12 percent per annum to 14 percent, and change the variable rate of interest from 10 percent per annum to 12 percent:

We can also make changes to the business process. Let's say we were previously offering special discounts to our Platinum customers only. Now the business has decided to offer the same discounts to the Gold customers as well.

Select the LoanEligibility business process. Then select the condition of Platinum customers and rename this as Gold and Platinum customers.

Edit the condition and make changes to it to include Gold customers as well. The condition will be eligibility status == "Platinum" or eligibility status == "Gold". This can be defined by using Expression Builder.

Validate the changes and then click on the Save button. Now our business changes have been done. The changes need to be deployed from BPM Composer.

Launch JDeveloper and then right-click on the Loan Application initiator task and add a counter mark.

Assign it to the application counter.

We will now create the following dimensions and measurements, as discussed earlier at the start of this recipe:

Right-click on LoanApplicationProj and select Project Preferences. Under Process Analytics Summary, ensure that eis/bam/soap is selected. Also, the Enable Cubes and Enable BAM checkboxes are selected. We can select the default folder path or select a new path as required.

Log in to BAM as the weblogic user at http://localhost:9001/OracleBAM/.

Click on Architect. We can now view data in the BAM data objects that got pushed from BPM. Usually, the data object name will be of the form BI_default_<project name>_<process name>. In our case, it will be BI_default_LoanApplicationProj_LoanApplicationProcess.

In BAM Active Studio, create the report by selecting a report type and the data objects that holds our BPM data. The Data tab shows all the available columns. We can select the one that is needed to generate our report.

We can click on the Properties tab to enable formatting of text on the x and y axes. We can also select themes, or create calculated fields, depending on the nature of the report requirements.

BAM also is capable of sending BAM alerts and notifications that can be configured. For example, we can set up an alert when a fraud is detected during the document verification stage.

Launch JDeveloper and open the composite.xml of LoanApplicationProcess in the Design view.

Drag-and-drop a new BPMN Process component from the Component Palette.

Create the Send Notifications process next to the existing LoanApplicationProcess, and edit the new process.

The Send Notifications process will take input parameters as To e-mail ID, From e-mail ID, Subject, CC, and send e-mail to the given e-mail ID.

Similarly, we will drag-and-drop a File Adapter component from the Component Palette that saves the customer data into a file. We place this component the end of the LoanApplication process, just before the End activity.

We will use this notification service to notify Verification Officers about the arrival of a new eligible application that needs to be verified.

In the Application Verification Officer stage, we will add a subprocess, KYC, that will be assigned to the loan initiator—James Cooper in our case.

This will be preceded by sending an e-mail notification to the applicant asking for KYC details such as PAN number, scanned photograph, and voter ID as requested by the Verification Officers.

Now, let us implement Save Loan Application by invoking the File Adapter service. The Email notification services are also available out of the box.

When the process is initiated, the e-mail notification gets triggered at appropriate stages of the process.

Conan Doyle and John Steinbeck will get the e-mail, requesting them to process the application, with the required information of the applicant, along with the link to BPM Workspace.

The KYC task also sends an e-mail to James Cooper, requesting him for the documents required for the KYC check.

James Cooper logs in to the James Bank WebCenter Portal and sees there is a task assigned to him to upload his KYC details.

James Cooper clicks on the task link and submits the required soft copy documents, and gets them checked into the content repository once the form is submitted.

Lets create a simple Partner Business Process, LorenRateofInterestQuoteProcess, that accepts loan request input from James Bank's LoanApplicationProcess and returns quotes for fixed and variable rates of interest. It also waits for some time before completing the process. This can be considered as a waiting period for the Quote Officer to complete his/her task of sending the quote back.

Deploy the process.

Log in to Enterprise Manager (http://localhost:7001/em) and download the WSDL as LorenRateofInterestQuoteProcess.service.xml from the process WSDL URL.

To create OSB resources, log in to OSB at http://localhost:7001/sbconsole.

Create a new project.

Under Change Center click on the Create button.

Create a resource of type WSDL and upload the LorenRateofInterestQuoteProcess.service.xml WSDL file.

Similarly, create one more resource of type XML Schema and upload the jamesbankloanapplication.xsd file.

Create a business service as PartnerQuoteBusinessService. This will make an HTTP request to our Partner Business Process that we had deployed. It also makes it easier for the Partner to modify the endpoint URL in case the process gets redeployed into some other machine or into some other WSDL URL.

Create a proxy service as PartnerQuoteProxyService that maps to PartnerQuoteBusinessService. This proxy service uses the SB protocol to communicate with a business service.

To test the proxy service, click on the Launch Test Console icon under the Actions column to launch the test console for the proxy service.

Provide the required XML input as the request message.

Log in to BPM Composer, enter the quote, and we will be able to see the response message in SOAP format.

In JDeveloper, open the composite.xml file of LoanApplicationProcess in the Design view.

Insert a Direct Binding service from the Component Palette, as this invokes our OSB layer proxy service.

Edit LoanApplicationProcess and call the partner service before the finance approval stage. Also pass the required payload parameters.

Save and redeploy LoanApplicationProcess to involve the partner. Optionally, we can also call the notification service to e-mail or SMS the partner before sending in the task.

Applicant James Cooper logs in to the James Bank Portal and submits his loan application online.

After a series of approvals—that is after document check, agency verification check, KYC check, and before finance approval—Partner Quote Officer Irving Stone gets this application request to quote a rate of interest that Loren Kelleher Bank can offer.

Loren Kelleher Bank offers a rate of interest that is less than the rate of interest quoted by James Bank to the loan applicant. Irving Stone quotes 6 percent for fixed and 8 percent for variable rate of interest to James Bank.

From the JDeveloper let's open the Loan EMI UI Fusion ADF project that we created earlier in the Implementing a home loan process recipe.

Create a simple JSPX page that can render on mobile devices. Let's drag-and-drop the data controls on the page as Trinidad components, which are preferred lightweight components on mobile devices.

Deploy the process, access it over a mobile device or a mobile simulator, and test it.

Log in to WebCenter Portal and click on the Administration link.

Under the Administration tab, click on the Resources tab and in the Mashup Styles, select Create Data Control.

Log in to WebCenter Content Server (http://localhost:16200/cs) and check in an HTML file that can be a public facing corporate page. Also, check in the related CSS and images files into a public folder, or a private folder, depending on the content security

James Cooper (loan applicant) checks the James Bank website on his mobile device to see if he has loan eligibility or not. Based on whether or not he does, the system generates a unique request ID that he can use later on for applying a loan.

James Cooper visits the customer portal and sees the promotional campaign.

James Cooper applies for a home loan, as discussed in the Integrating with business partners recipe.

This action sends notification e-mails to Conan Doyle (Application Verification Officer) and John Steinbeck (Field Officer). They will verify the application and approve it to the next level.

The application is routed to the KYC check. An e-mail is sent back to James Cooper asking for KYC-related documents.

James Cooper logs in to the portal again, and submits the required KYC documents such as the Income Tax PAN, photograph, and passport copy.

The request is routed to Irving Stone (Partner Quote Officer) of Loren Kelleher Bank, and he sends a quote.

The quote is finally reviewed by William Faulkner (Finance Officer) of James Bank.

William Faulkner logs in on the WebCenter Portal's intranet and views some of the business dashboards that are related to changes in the rate of interest, the current status of various applications, corporate news, and any other task that needs his approval and decision making.