Improving the performance of WPS and WebSphere ESB solutions with dynamic caching

Promoting the performance of WebSphere Process Server and WebSphere ESB solutions with dynamic caching

When you develop an SCA solution, you often need data that is difficult to obtain or computationally difficult to compute. To get this data, you might need to invoke a WEB service, connect to a database, perform a complex logical operation, or summarize data from multiple data sources. If the data does not change over time, you can achieve significant performance gains by moderately using the cache. This tutorial will show you a simple and efficient caching technology dynacache based on a proven product feature that can help you meet your application's performance needs. In addition, by using Dynacache, the complexity of cached data replication and the synchronization of network deployment topology nodes will be handled automatically and transparently by the underlying infrastructure.

About this tutorial

This tutorial is based on a virtual service that retrieves and returns the details of a location. You can imagine the service as part of a room reservation system where the system's campus and facility information is obtained elsewhere. You determine that campus facility information rarely changes, so you are considering that you can use the local cache to achieve this particular service. When local fine-grained data changes, you will also learn how to invalidate cache entries and clear the cache.

Goal

You will learn how to:

Define the service interface.

Build the cache component.

Test the cache component.

Use cache entries and clean cache.

Prerequisite conditions

This tutorial assumes that you have an understanding of the Java™ programming language, familiarity with the SCA programming model, and a more proficient use of WSDL interfaces, data types, SCA components, and integrated test clients in Websphere®integration Developer.

System Requirements

This tutorial is developed using WebSphere integration Developer V6.2.0.2. However, the code can be compiled and run in each version of the product, including the upcoming release 7th edition.

Study time

It takes about 1 hours to study this textbook.

Defining Service Interfaces

In this section, you will begin to prepare the interfaces and data types required to access the service.

Task 1: Create a new WebSphere integration Developer Project

Start the WebSphere integration Developer, create a new workspace, and switch to Business integration view.

Using the File-> New-> Module menu, name the modules cachingtutorial, leave the defaults, and click Finish.

Task 2: Create service Interfaces and message types

You will use four types of data to represent request and response information:

Locationbasicinfo

Address

Facility

Locationdetails