Dedicated DataPower hardware appliances can process XML message at wire speed, and their robust security features protect against threats such as buffer overflows or XML denial-of-service attacks. This article describes an end-to-end XML message flow sent from a client through the Internet via HTTP to an intermediary WebSphere DataPower Appliance, which further transports it over JMS to a queue destination on a messaging engine running in the service integration bus for persistence. In addition, you can use a message-driven bean associated with a listener on the destination to asynchronously consume any message that arrives in the queue: Figure 1. Asynchronous messaging support provides applications with the ability to create, send, receive, and read asynchronous requests as messages.
|Published (Last):||23 October 2008|
|PDF File Size:||19.28 Mb|
|ePub File Size:||20.91 Mb|
|Price:||Free* [*Free Regsitration Required]|
While the service definition and artifact generation are important to understand, if you want to get serious about SOA, you must consider the problems of security, performance, governance and monitoring. Those issues can many times not be solved with the service definition, but they require additional infrastructure and configuration steps.
IBM WebSphere DataPower provides a distinct and competitive hardware, software, and infrastructure stack which allows you to address many of the SOA challenges mentioned earlier.
This gives a wide variety of clients the ability to talk to DB2 — without even being database-aware. These appliances offer an innovative, pragmatic approach to harness the power of SOA. By using them, you can simultaneously use the value of your existing application, security, and networking infrastructure investments. This tutorial focuses on DataPower as a transformation and protocol conversation engine to transform Web service requests into database calls and the result back into service responses to implement a data access service.
Figure 1 shows this transformation process: Figure 1. Transforming requests into database calls View image at full size A transformation is defined by a set of rules which determine how an input is mapped to an output. A very common format for Web service is XML. Therefore, XSL is used to transform service requests into database calls and back.
Use IBM Data Studio Developer to generate DataPower service artifacts While the information provided so far gives you the ability to write the appropriate XSL scripts by hand to implement the transformation mappings necessary for a data access service, this is a very time-consuming and error-prone task.
After a service has been defined, artifacts for a specific runtime environment can generated. The generated artifacts consist of the WSDL file of the service as well as a set of XSL scripts defining the mapping between service requests and database calls. Those artifacts can now be deployed on a DataPower XI50 appliance. Figure 2 shows how this process works: Figure 2.
DataPower provides different configuration categories for different kind of services as Figure 3 illustrates. Figure 3. Configuration in DataPower DataPower has a completely metadata-driven configuration approach. All service configurations have a front-end and back-end configuration as well as a processing policy which defines one or more processing rules.
Depending on the selected service configuration, some of the configurations might be masked. For example, an XSL Accelerator configuration does not have an explicit back-end setup. Figure 4. DataPower configuration View image at full size Front end The front end defines the "client-facing" part of a configuration. Back end The back end defines the configuration of the service and server the processed request should be sent to.
It usually contains protocol-specific settings and addresses information of the back-end service. Note: A database is not considered to be a back-end system for DataPower. In case of Data Web services, the requests are terminated at the DataPower appliance and not sent to a back-end system.
Instead of providing a real back-end system with the configurations, we use a loopback configuration which turns an incoming request into a response. Policy A policy defines a set of one or more processing rules. Every service configuration on DataPower contains a policy setup.
Rule A rule defines a sequence of actions like matching, validation, transformation, routing, and so on which get applied to a request or response message. For example, the XSL artifacts generated by Data Studio are added to such a processing rule in form of a transform action. Step 1. Base this project on a connection to a DB2 sample database.
Your DataPower XI50 appliance also needs to be able to connect to this database. The DataPower setup is described later in this document. Figure 5. Step 2. Figure 6. Click Finish. Alternatively, you can also use the SQL builder to assemble the statement. Figure 8. You can locate the procedure by navigating to the Stored Procedure folder under the appropriate schema in the database connection in the Data Source Explorer view: Figure 9.
Step 3. Create the Web service Create a new Web service by selecting the DataPowerSamples project and right-clicking on the Web services folder.
Select New Web Service Figure New Web service View image at full size Click Finish to create the service. Check the Fetch only single row for queries option since you know that this query only returns one row at a time - an employee record - and click Finish. This setting simplifies the XML structure of the service response. The Data Web Services tooling lets you adjust the result set schema by executing the procedure and taking the schema information from the returned result set metadata.
Specify 1. This executes the procedure, and the metadata from the returned result set can be analyzed. After the execution, you can click Finish on the Edit Operation dialog. That concludes the fine tuning of the Web service operations. Execute stored procedure View image at full size Step 4. Build service artifacts Up to this point, the tutorial has not discussed the difference between a service to be deployed in a J2EE environment or one to be deployed on DataPower.
In this step, you will create the service runtime artifacts, so you have to decide which runtime environment to use. Select DataPower as the Web server type. The name needs to match the data source, which you will set up on DataPower to connect to the DB2 sample database. The DB2 data source setup on DataPower is shown in the next section. Click Finish to generate the artifacts. Deploy Web service The artifacts are written to a sub-directory inside the Data Development project.
Since the Data perspective does not show the created folder, you need to open the Navigator view as shown: Figure In there you will find one directory for every Web service defined in your Data Development Project.
A Web service folder contains the service metadata information in the. In case DataPower was selected as the runtime environment, you will also find an artifacts folder. This folder contains all the necessary service implementation files which need to be copied to DataPower appliance. Refresh project This concludes the work in Data Studio.
Make sure the Admin State is set to enabled or DataPower will not connect to the database. Select DB2 version 9 as the Database type. The version 9 driver also works with older DB2 versions. Enter your connection username and password. Set the Maximum Connections to Configure a database connection View image at full size Click Apply to save your settings.
To persist configuration settings beyond DataPower shutdowns, click the Save Config button in the upper right corner. The data source will be up and running and ready for use when the Op-State says up Figure You can refresh the view by clicking the Refresh List link -- it can take some time until the data source is connected to the database.
Operation state is up View image at full size Set additional driver parameters The Data Source Configuration Parameters tab allows you to specify additional connection parameters. This concludes the data source setup. Now you need to copy the generated artifacts over to the DataPower box. Copy artifacts to DataPower In order to keep the setup simple, copy all artifacts into the local DataPower file system.
File Management icon Click on the Actions Create subdirectory Provide the name "DataPowerSampleService" as the subdirectory name and click Confirm Create to create the directory. Provide new directory name Finally click Continue to get back to the directory overview. Click the Upload Files Figure To add a new file to the upload list, click the Add button.
After all files are selected, click Upload to transfer them to the DataPower box. Upload generated files Finally click Continue to get back to the directory overview. Now that you understand how to copy the artifacts, you can see how to configure the service.
Name the Proxy Service Select loopback-proxy as proxy type and click Next. Loopback Proxy Service On the next screen, keep 0. Click Next. Confirm XSL Proxy settings.
IBM Community Home
Shakagal Create and deploy Data Web Services on WebSphere DataPower XI50 Integration Appliance Click on the Actions While the information provided so far gives you the ability to write the thtorial XSL scripts by hand to implement the transformation mappings necessary for a data access service, this is a very time-consuming and error-prone task. For example, the XSL artifacts generated by Data Studio are added to such a processing rule in form of a transform action. Related Resources Store Articles Blogs. DataPower provides different configuration categories for different kind of services as Figure 3 illustrates. This folder contains all the necessary service implementation files which need to be copied to DataPower appliance.
Create and deploy Data Web Services on WebSphere DataPower XI50 Integration Appliance
DATAPOWER XI50 TUTORIAL PDF