Tutorials

Tutorial 2. Transforming a Loan Application

Data transformation is the mapping of data from one format to another. This section describes how BEA AquaLogic Service Bus routes messages and transforms messages, when necessary, according to specific criteria that you configure for a proxy service.

This section includes the following topics:

• Prerequisites
• Tutorial Goals
• Definition of the Scenario

 

---

Prerequisites

Complete Tutorial 1. Routing a Loan Application.

 

---

Tutorial Goals

The goal of the tutorial is to provide the steps to create and test a routing and transformation scenario developed using the graphical environment provided in AquaLogic Service Bus Console.

Using the AquaLogic Service Bus Console you will build on what you learned in Tutorial 1. Routing a Loan Application, to:

• Configure content-based routing.
• Use an XPath expression to change the content in the message body.

 

---

Definition of the Scenario

A primary mortgage company uses BEA AquaLogic Service Bus to identify and re-route loan applications that can be sold to secondary loan companies. Loan applications with a principal request of greater than 25,000,000.00 are candidates for sale to a secondary loan company. When AquaLogic Service Bus receives a loan application meeting these criteria, the applicant's credit rating information is retrieved (by making a callout to a Web service) and added to the loan application, then the application is forwarded to the secondary mortgage company's Web service to be processed.

Loan applications with a principal request equal to or less than 25,000,000.00 are routed to a different business service for processing.

The target business services respond indicating whether the loan application is approved or rejected.

The following figure illustrates where BEA AquaLogic Service Bus fits in your enterprise to mediate the messaging between the enterprise services and the business services.

Figure 4-1 Expose a Loan Application Processing Web Service via AquaLogic Service Bus

 

Overview of the Run-Time Process in AquaLogic Service Bus

A primary mortgage company receives a loan application. It is routed through the AquaLogic Service Bus proxy service, LoanGateway2, to determine the target business service to process the application. If the loan amount is greater than 25000000, the application is routed to the LoanSaleProcessor business service. If the amount is less than or equal to 25000000, the application is routed to the NormalLoan business service. When the loan amount is more than 25000000, the request pipeline makes a service callout to the CreditRatingService and receives the credit rating of the applicant using the $creditRating variable. To satisfy the interface requirements of the secondary loan company service, the message body is transformed by adding the credit rating details. The transformed message ($body) is routed to a business service that handles applications for large loan amounts. The service returns a response of:

Loan Application Response: CREDIT RATING: AA: LOAN PURCHASED BY THE <i><b>LARGE</b></i> LOANS SERVICE

Required Resources

You will use the Project folder, MortgageBroker, and the directory structure you created in the previous tutorial to hold the project artifacts. The resources required for this scenario are described in the following table.

Table 4-1 Routing a Loan Application Tutorial Resources

 

 

---

Steps in This Tutorial

In this tutorial, you will build on what you learned in Tutorial 1. Routing a Loan Application—you will import additional WSDL resources, register new business and proxy services, and configure the routing behavior for the proxy service. Configuring the routing behavior includes:

• Adding a Service Callout to get a credit rating
• Changing the namespace and inserting a new CreditRating element in the outbound (request) message
• Reverting the namespace change and removing the CreditRating element on the response message.

Complete the following steps to design and configure the proxy service and the associated resources in AquaLogic Service Bus to resolve this user case scenario:

• Step 1: Prepare Your Environment
• Step 2: Create a Session and Set up a Project
• Step 3: Create the Resources
• Step 4: Configure the Routing for the LoanGateway2 Proxy Service
• Step 5: Configure the Routing Table Request Actions for the LoanGateway2 Proxy Service
• Step 6: Configure the Routing Table Response Actions for the LoanGateway2 Proxy Service
• Step 7: Add a Default Routing Case
• Step 8: Test Your Loan Application Routing Configuration

Step 1: Prepare Your Environment

Ensure that AquaLogic Service Bus is running in the domain you created for the tutorial and that you have completed the steps described in Tutorial 1. Routing a Loan Application.

Step 2: Create a Session and Set up a Project

For this tutorial, you use the project folder, MortgageBroker, and the directory structure you created in Tutorial 1. Routing a Loan Application to hold the project artifacts.

Click Create in the Change Center to create a new session.
In the AquaLogic Service Bus Console navigation panel, select Project Explorer.

The Project Explorer pane is opened in the navigation panel and a project page is displayed in the console.

In Project Explorer, expand the MortgageBroker project tree to expose the sub folders containing the project artifacts.:
• ProxyService
• BusinessServices
• WSDL

Step 3: Create the Resources

In this step, you will import the WSDL resource, and create the proxy service and the business services required for the tutorial:

• Create the WSDL Resources
• Create a Proxy Service
• Create a Business Service

Create the WSDL Resources

Because the WSDLs are the basis on which you create the business services and the proxy service, you must create the WSDL resources (LoanSale and CreditRatingService) before creating the other resources required for this scenario.

To import the appropriate WSDLs and create the WSDL resources, follow the steps described in To Import a WSDL, but for this instance, name your resources and base them on the WSDLs as described in the following table.

Table 4-2 WSDL Configuration Settings

 

When you complete this step, the MortgageBroker/WSDL folder contains the WSDL resources created in this tutorial and in Tutorial 1. Routing a Loan Application as shown in the following figure.

Figure 4-2 WSDL Resources

 

Create a Proxy Service

In this step, you create a proxy service. The proxy service is used to route the loan application to the appropriate business service. It also calls a look up service to get the credit rating of the requestor if the loan amount requested is greater than 25 000 000.00. (Note that no units are assigned to the loan amount; it can be dollars or any other unit of currency.)

To create a new proxy service, follow the steps described in To Create the Proxy Service, but for this instance, use the proxy service name and the Endpoint URI described in the following table.

Table 4-3 Proxy Service Configuration Settings

 

After you complete this step, a summary of the configuration settings for the proxy service is displayed as shown in the following figure. Review the configuration settings prior to registering the proxy service.

Figure 4-3 LoadGateway2 Proxy Service - Configuration Settings Summary

 

When you complete this step, the MortgageBroker/ProxyService folder contains the proxy services you created in this tutorial and in Tutorial 1. Routing a Loan Application as shown in the following figure.

Figure 4-4 Proxy Service Resources

 

Create a Business Service

In this scenario, the proxy service is configured to route to one of several different business services, depending on the business requirements:

• CreditRatingService—returns the customer's credit rating when a loan application meeting specified criteria is received. This is implemented using a Web service callout (Service Callout).
• NormalLoan—is the secondary mortgage company's business service. This service is invoked when a loan request is made for amounts of 25 000 000 or less.
• LoanSaleProcessor is the secondary mortgage company's business service. This service is invoked when a loan request is made for amounts greater than 25 000 000.00.

You created the Normal Loan service in Tutorial 1. Routing a Loan Application. To create the LoanSaleProcessor and CreditRatingService business services for this scenario, follow the steps described in To Create the Normal Loan Business Service. However, in this case, configure your services using the names, service types, and endpoint URIs described in the following tables.

Table 4-4 Configuration Settings for the LoanSaleProcessor Business Service

 

Table 4-5 Configuration Settings for the CreditRatingService Business Service

 

When you complete this step, the MortgageBroker/BusinessService folder contains the business services you created in this tutorial and in Tutorial 1. Routing a Loan Application as shown in the following figure.

Figure 4-5 Business Service Resources

 

Summary

By completing Step 1: Prepare Your Environment to Step 3: Create the Resources, you created the resources required for this scenario. You configured the proxy service with a base configuration. Subsequent steps (Step 4: Configure the Routing for the LoanGateway2 Proxy Service to Step 6: Configure the Routing Table Response Actions for the LoanGateway2 Proxy Service) describes how to complete the configuration of the proxy service to add the routing, transformation, and Service Callout behavior for the loan application messages.

Step 4: Configure the Routing for the LoanGateway2 Proxy Service

The proxy service is implemented in Service Bus as a Message Flow, which includes request and response pipelines. This step includes the following tasks:

• Create a Routing Table
• Configure the Routing Expression

Create a Routing Table

In the AquaLogic Service Bus Console navigation panel, select Resource Browser.

The Resource Browser pane is opened in the navigation panel and the Summary of proxy Services page is displayed in the console.

Note: You must be in a session to edit resources. If you have not already done so, begin a session (click Create in the Change Center) so that you can configure the proxy service and edit the message flow.

In the Actions column associated with the LoanGateway2 proxy service, click the Edit Message Flow icon .

The Edit Message Flow page for the proxy service LoanGateway2 is displayed.

Click LoanGateway2, then select Add Route Node.

In the configuration dialog, RouteNode1 is added.

Click RouteNode1 and from the pop-up menu select Edit—>Route Node.

The Edit Stage Configuration page is displayed. The page contains a single link, Add an Action.

Click Add an Action, then select Routing Table.

The Edit Stage Configuration page changes to display routing table configuration page.

You will configure the routing table to route messages to business services based on evaluating the amount element of the incoming message. You must create an XQuery expression to do this. You can do so using the XQuery Expression Editor.

Configure the Routing Expression

In the Routing table, click the <Expression> link. The XQuery Expression Editor page is displayed.
Accept the default selection of XQuery Text in the page.
Click Variable Structures. The Variable Structures pane is displayed.
From the Select Structure drop-down list in the Variable Structures pane, select body.

A structural representation of the body element is displayed in the Variable Structures pane.

Click + beside the processLoanApp element to expand the element.

The processLoanApp element is within the $body - processLoanApp (request) element.

Click + to expand the loan request element.

A graphical representation of the structure of the loan request document is displayed.

At run time, the proxy service makes its routing decision based on the value in the amount element of the message.

Select the circle icon associated with the Amount node element, drag and drop it in the XQuery Expression text box.

The $body/exam:processLoanApp/loanRequest/java:Amount XQuery expression is written in the text box.

Note: The drag and drop functionality works only in Internet Explorer (IE) browsers. If you are using a browser other than IE, select the amount element in the Variable Structures pane. The expression is displayed in the Property Inspector palette. Place the cursor in the XQuery expression text box and click Copy Property. The expression is copied to the text box. You can also copy the expression in the palette and paste it into the XQuery Expression text box.

Click Validate to validate the XQuery.

It is good practise to do this before you submit the expression. The expression is validated for syntax. If there are errors in the expression, they are displayed directly above the Validate button. In this case, the expression is valid as shown in the following figure.

Figure 4-6 Validate Routing Expression




 

Click Save.

You are returned to the routing table on the Edit Stage Configuration page. <Expression> is now replaced by the expression that returns the value of the amount element in the message.

In the Operator drop-down list, select > and in the associated text field, enter the number 25000000 (without commas).

The routing table now contains an expression that determines the routing behavior. If the value in the Amount field is greater than 25000000, then messages are routed according to the routing table configuration.

Click the Service link to define the service to which you want to route when the amount is greater than 25000000. The Select Service browser window is displayed.
Select the LoanSaleProcessor business service
Click Submit.
In the Routing Table Operation drop-down list, select the processLoanApp operation.

This is the operation on the LoanSaleProcessor service business service that is invoked at run time if the amount of the loan requested in the loan application is greater than 25000000.

You have now defined the case for routing the loan application to the LoanSaleProcessor business service.

Figure 4-7 Routing the Loan Application to LoanSaleProcessor

 

When a loan application with the amount of the loan greater than 25000000 is identified, a Web service callout (Service Callout) is performed to retrieve the customer's credit rating. The credit rating information is added to the loan application and the application is then forwarded to the secondary mortgage company's business service to be processed. The next section (Step 5: Configure the Routing Table Request Actions for the LoanGateway2 Proxy Service) describes how to configure the proxy service to do the Service Callout and transform the message appropriately for the target service.

Step 5: Configure the Routing Table Request Actions for the LoanGateway2 Proxy Service

To configure the Routing Table Request actions, execute the following steps:

• Configure the Service Callout Input Parameter
• Add a Service Callout Action
• Configure the Message Transformation

Configure the Service Callout Input Parameter

A Service Callout is used to send the loan application to the CreditRatingService business service, which returns the credit rating of an applicant. Before configuring the Service Callout action, you must assign an input parameter for the Service Callout action as follows:

Ensure that the Edit Stage Configuration page for the routing table you created in Step 4: Configure the Routing for the LoanGateway2 Proxy Service is open in the AquaLogic Service Bus Console.
In the Request Actions panel of the Routing Table, click Add an Action, then select Assign.

The Assign action is added to the Request Action pipeline in the Routing Table.

Click the <Expression> link. The XQuery Expression Editor page is displayed.
Accept the default selection of XQuery Text in the page.
Select body from the Variables Structures drop-down list in the Variables Structures pane, then expand the element list and drag the loanRequest element and drop it into the XQuery expression text box. The XQuery expression is written in the text box:

$body/exam:processLoanApp/loanRequest

Click Validate to validate the XQuery, then Save.

You are returned to the routing table on the Edit Stage Configuration page. <Expression> is now replaced by the expression that returns the content of the message to be sent to the Service Callout service.

Enter inputparam in the variable text box.

Figure 4-8 Configure Service Callout Input Parameter




 

This step completes the assignment of the value returned by the XQuery expression ($body/exam:processLoanApp/loanRequest) to the inputparam variable.

Add a Service Callout Action

This section describes how to configure the Service Callout action to send the loan application to the CreditRatingService business service, which returns the credit rating of an applicant.

In the Request Actions panel of the Routing Table, click , then select Add an Action—> Service Callout.

The Service Callout action is added to the Request Action pipeline in the Routing Table.

Click the Service Callout Service link. The Select Service browser window is displayed.
In the Select Service window, select CreditRatingService.
Click Submit.
From the Operation drop-down list, select processLoanApp. The fields that allow you to configure the request and response parameters for the Service Callout are displayed:
In the Service Callout Request Parameters section, set the Loan request parameter to inputparam (the message context variable you defined in the preceding section).
In the Service Callout Response Parameters section, set the return parameter name to creditRating.

Figure 4-9 Configure Service Callout Action




 

This step completes the configuration of the Service Callout to the CreditRatingService Web Service. The credit rating returned by the Web service is assigned to the creditRating context variable.

Configure the Message Transformation

In this section, you will configure the transformation of the message to match the public contract (interface requirements) of the loanSaleProcessor Service. Specifically, this section describes how to:

• Configure the proxy service to rename the namespace for the message to the namespace required by the target service. You do this using XPath expressions. This configuration is described in To Rename the Namespace.
• Configure the proxy service to insert an new element into the message. To do this, you must add an element action in the configuration. This configuration is described in To Insert a New Element into the Message.

To Rename the Namespace

Click the Service Callout icon , then select Add an Action—>Rename.

The Rename action configuration fields are added to the Request Actions panel.

In the Rename statement, click the <XPath> link. The XPath Expression Editor is displayed.
In the XPath Expression text box, enter the following XPath expression:

.//java:*

This expression identifies every instance of a namespace with a prefix of java.

Click Save. You are returned to the Edit Stage Configuration page.
In the variable text box, enter body.

The body context variable holds the body of the message. By completing these steps, you created a condition in which the XPath expression finds all the namespaces with the java prefix in the body context variable. The next step specifies the namespace with which to replace the namespaces identified by the XPath expression.

Select the namespace option and enter the fully qualified namespace to be substituted in the message. The new namespace is java:large.client.

Note: The namespace that you are replacing in this case is java:normal.client.

The Rename action should now look like the following figure.

Figure 4-10 Rename Namespace

 

To Insert a New Element into the Message

Click the Rename icon , then select Add an Action—>Insert.

The Insert action configuration fields are added to the Request Actions panel.

In the Insert action, click <Expression>.

The XQuery Expression Editor page is displayed. You will add a new namespace on this page.

In the Namespace Definitions palette, locate to the User Defined Namespaces area.

Figure 4-11 User Defined Namespace




 
Click Add Namespace.
In the Prefix field, enter lg.
In the URI field, enter java:large.client
Click Add.

The new namespace is displayed in the User Defined Namespaces area in the Namespace Definitions palette.

In the XQuery Expression text box, enter the following expression to specify how the new element is constructed:

<lg:CreditRating>{data($creditRating)}</lg:CreditRating>

• The element you add to the message must be associated with the java:large.client namespace. Therefore you specify the namespace for the element with lg:.
• {} tells the XQuery engine that the content between the {} is not XML and must be interpreted.

At run time, the $creditRating variable is assigned a credit rating value by the credit rating service (to which we configured a Service Callout action in Add a Service Callout Action).

Click Validate, then Save.

Note: It is good practice is to validate your expressions before submitting them.

In the Insert statement, select after from the drop-down list.
Click the <XPath> link. The XPath Expression Editor page is displayed:
Click Variable Structures. The Variable Structures pane is displayed.
In the Select Structure drop-down list in the Variables Structures pane, select body.
Expand the element list and drag the Notes element and drop it into the XPath Expression text box.

The following XPath expression is written to the text box

./exam:processLoanApp/loanRequest/java:Notes

Note: The drag and drop functionality works only in Internet Explorer (IE) browsers. If you are using a browser other than IE, select the notes element in the Variable Structures pane. The XPath expression is displayed in the Property Inspector palette. Place the cursor in the XPath expression text box and click Copy Property. The expression is copied to the text box. You can also copy the expression in the palette and paste it into the XPath Expression text box.

In this statement, replace the namespace java with the namespace lg:

./exam:processLoanApp/loanRequest/lg:Notes 

Click Validate, then Save to return to the Edit Stage Configuration page.
Enter body in the Variable text field (the last field in the expression). This is the context variable into which the new <CreditRating> element is inserted at run time.

The Insert action should now look like the following figure.

Figure 4-12 Insert New Element into Message

 

This step completes the configuration of the outbound message. You added a credit rating element to the message and changed the namespace so that the message complies with the public contract (interface) of the target service.

After completing the above steps, the configuration of the outbound message should look like the following figure.

Figure 4-13 Configuration of Outbound Message

 

The next step describes how to configure the response actions for the LoanGateway2 proxy service.

Step 6: Configure the Routing Table Response Actions for the LoanGateway2 Proxy Service

This step describes how to configure the response actions in the Routing Table so that the message that is returned by the proxy service to the client complies with the client's public contract (WSDL). Specifically, this section describes how to:

• Configure the proxy service to remove the CreditRating element from the response message. This configuration is described in To Delete an Element.
• Configure the proxy service to revert the namespace to the namespace in the original message: java:normal.client. This configuration is described in To Add a Rename Action.

To Delete an Element

Ensure that the Edit Stage Configuration page for the routing table you created and configured in the preceding steps is open in the AquaLogic Service Bus Console.
In the Routing Table Response Actions panel, click Add an Action—>Delete.

The Delete action configuration fields are added to the Response Actions in the Routing Table.

Select the < XPath> in variable option, then click <XPath>. The XPath Expression Editor page is displayed.
In the XPath Expression text box, enter the following expression:

./exam:processLoanAppResponse/return/lg:CreditRating 

where processLoanAppResponse represents the WSDL operation that was invoked with the string Response appended to it, and return is the WSDL part name.

Click Validate, then Save. You are returned to the Edit Stage Configuration page.
Enter body in the variable text field in the Delete action.

The configuration for the Delete action is therefore:

Delete ./exam:processLoanAppResponse/return/lg:CreditRating in variable body as shown in the following figure.

Figure 4-14 Delete Element




 

By completing these steps, you have specified that AquaLogic Service Bus removes the credit rating element from the response message as the message is processed in the response pipeline.

To Add a Rename Action

This section describes how to rename the namespace to the namespace required by the client, that is java:normal.client. (Recall that you configured the request message to the loanSaleProcessor business service to change the namespace to that required by that service. (See To Rename the Namespace.)

Click the Delete icon , then Add an Action—>Rename.

The Rename action configuration fields are added to the Response Actions panel.

In the Rename statement, click <XPath>. The XPath Expression Editor is displayed.
In the XPath Expression text box, enter the following expression:

.//lg:*

This XPath expression finds every namespace with a prefix of lg:.

Click Save. You are returned to the Edit Stage Configuration page.
In the Rename action's variable text field enter body.
Select the namespace option, and in the text field associated with the namespace, enter java:normal.client.

By completing these steps, you have specified that AquaLogic Service Bus replaces all namespaces with the prefix lg: in the response message with java:normal.client as shown in the following figure.

Figure 4-15 Add Rename Action




 

After completing the above steps, the configuration of the response action of the proxy service should look like the following figure.

Figure 4-16 Configuration of Response Actions of Proxy Service

 

The last step in the configuration of the routing table for the LoanGateway2 proxy service is to add a default routing case (an else condition) to the Case expression.

Step 7: Add a Default Routing Case

This step describes how to configure a default routing case for the routing table for the LoanGateway2 proxy service. At run time, AquaLogic Service Bus routes messages according to the configuration of this default case if none of the conditions configured in the Routing Table is met.

Click the routing table Case icon , then select Insert—>Default Case.

The default case is added after the routing table on the Edit Stage Configuration page.

Click <Service> to display the Select Services browser window.
Select the NormalLoan business service.
Click Submit.
In the Default case configuration fields, select the operation processLoanApp as shown in the following figure.

Figure 4-17 Add Default Routing Case




 
Click Save to save the route node configuration and return to the Edit Message Flow page for the LoanGateway2 proxy service.
Click Save on each configuration page until you return to the Summary of Proxy Services page
Click Activate, then Submit to save the session configuration information.

You can view the map of the message flow of the proxy service as shown in the following figure.

Figure 4-18 Map of Message Flow of the LoanGateway2 Proxy Service

 

Step 8: Test Your Loan Application Routing Configuration

Now that you have configured AquaLogic Service Bus to work with the client and the target business services, you can test your configuration. The routing behavior of the proxy service in this scenario is based on the value of the loan amount in the loan application message. Changing the value of the loan amount changes the routing behavior.

• A value equal to or less than 25000000 causes the message to be routed to the normalLoan business service.
• A value greater than 25000000 causes the message to be routed to the LoanSaleProcessor business service (the large loan processing service).

This section describes how to test the proxy service for both cases. The message returned in the command window after running a test indicates the success or failure of the test and identifies the business service that processed the request.

This section includes the following test scenarios:

• To Test the LoanSaleProcessor (the Large Loan Purchasing Service) Business Service
• To Test the NormalLoan Business Service

To Test the LoanSaleProcessor (the Large Loan Purchasing Service) Business Service

Open a Command window.
If you have not run the setEnv.cmd to set up your environment, you must do so now.
Change to the following directory:

BEA_HOME\weblogic91\samples\servicebus\examples\src\ 

In this directory, on the command line, run the following command:

setEnv.cmd

Note: If you are testing the configuration on a UNIX system, run the setEnv.sh script at your command line prompt.

Change to the following directory:

BEA_HOME\weblogic91\samples\servicebus\examples\src\examples\webservices\jws_basic\normal

To change the routing behavior of AquaLogic Service Bus, you must edit the build.xml file run target:
Open build.xml.
Scroll to the end of the build.xml file looking for the string:

<arg line="http://$... 

Replace the string found at this location with the following string and save the changes.

<arg line="http://${wls.hostname}:${wls.port}/loan/gateway2 steve 555 25000001 20 5.1 notes" />

This changes the URI to that of the proxy service to that of the deployed Web service (gateway2) running in the tutorial domain, and specifies a value of 25000001 for the loan amount. (For more information about the input parameters for the test, see Table 3-5.)

If you have not already done so, deploy the business services:
In a Command window, change to the following directory:

BEA_HOME\weblogic91\samples\servicebus\examples\src\examples\webservices\jws_basic\normal 

Enter ant, then press Enter.
To test the build, on the command line, enter:

ant run 

This tests the routing logic of the proxy service. The message from the Web service is output to the command line.

[java] Loan Application Response: CREDIT RATING: AA: LOAN PURCHASED BY THE <i><b>LARGE</b></i> LOANS SERVICE

     [java] Rate: 5.1

BUILD SUCCESSFUL

The response message indicates that the Large Loan Service processed the request because the amount of the loan requested was 25000001 (greater than 25000000).

To Test the NormalLoan Business Service

Follow the procedure To Test the LoanSaleProcessor (the Large Loan Purchasing Service) Business Service to edit the build.xml file in the following directory:

BEA_HOME\weblogic91\samples\servicebus\examples\src\examples\webservices\jws_basic\normal

In this case (to test the normalLoan business service), in the build.xml file, enter a value of 25000000 for the loan amount (see Table 3-5), then save the changes.

If you have not already done so, deploy the business services:
In a Command window, change to the following directory:

BEA_HOME\weblogic91\samples\servicebus\examples\src\examples\webservices\jws_basic\normal 

Enter ant, then press Enter.
To test the routing logic of the proxy service, on the command line, enter:

ant run

A response message from the Web service is output to the command line.

[java] Loan Application Response: APPROVED BY THE <i><b>NORMAL</b></i> LOAN APPLICATION PROCESSING SERVICE

     [java] Rate: 5.1

BUILD SUCCESSFUL

The response message indicates that the Normal Loan Application Processing Service processed the request because the amount of the loan requested was 25000000.

 

---

Best Practices

In this tutorial, you configure the transformation and replace the namespaces in the Route node. Alternatively, it is possible to configure the same logic in the request pipeline in a pipeline pair.

The work you must do to accomplish the transformation and namespace replacement is the same regardless of the model you choose.

In the case of the tutorial scenario, it is easier to add the actions to the request and response actions of the existing route node rather than create a separate pipeline pair, add a stage, and then add the transformation actions to that stage.

The following scenario describes a situation in which the choice of the implementation is important:

A route node routes messages to five different services. Each service requires the same transformation. In this scenario, it is better practice to add a single transformation to a request pipeline rather than configure five identical sets of transformations for each routing configuration in each route node. The run-time execution cost is the same, but the cost of maintaining, configuring, and understanding the latter implementation is higher and more work intensive.

Contact BEA |  Feedback |  Privacy  |