Level: Intermediate Indrajit Poddar (ipoddar@us.ibm.com), Software Architect, IBM
Devaprasad Nadgir (devaprasad@in.ibm.com), IBM Certified Senior IT Architect, IBM
10 Aug 2009 Part 1 of this series describes multi-tenancy and several technical
challenges faced by service providers for deploying multi-tenant web-delivered
solutions. In part 4, we presented a technical challenge on how to enable
multi-tenancy for existing single tenant web services with little or no code
changes for shorter time to market and lower costs. In this tutorial we will
present detailed implementations steps using a WebSphere® DataPower SOA
appliance in combination with Tivoli® Access Manager.
Before you start
About this tutorial
WebSphere DataPower SOA appliances are network devices which can act as
mediators between service providers and service consumers. Key advantages
offered by these appliances include high performance hardware based XML and Web services message processing, protocol transformation, easy configuration and security. In this tutorial, we will demonstrate how service providers can exploit content-based message routing features in DataPower to route service requests from a tenant’s user to service endpoints dedicated to that tenant. We will also demonstrate how service providers can integrate DataPower with Tivoli Access Manager so that centrally managed authorization policies can be used to authorize tenant specific service requests. Finally, we will demonstrate how service providers can monitor service requests using Web services traffic shaping features in DataPower.
Scenario and major implementation steps
Figure 1. Multi-tenancy with mediation implemented using WebSphere DataPower SOA appliances
In part 5 of this series, we described a scenario and a use case in which the
service provider for the Jivaro bank multi-tenant application would like to
enable multi-tenancy for his existing credit score service. In this tutorial,
we will demonstrate how to configure WebSphere DataPower SOA appliance to
implement a mediation pattern for multi-tenancy as illustrated in Figure 1. We will perform the following major steps:
- Configure Web service Proxies in WebSphere DataPower for authentication, authorization and routing tenant’s requests
- Configure tenant specific users and groups in Tivoli Access Manager
- Setup Service Level Monitoring policies to monitor tenant specific service requests
Prerequisites
This tutorial assumes that the following products are setup to work on an integrated platform. Detailed discussions on setting up the hardware and software components listed below are outside the scope of this article. Please refer to the Resources section for further details.
The following IBM development products are required to enable
multi-tenancy for his credit check Web service solution:
- WebSphere DataPower SOA appliance XI50
- Tivoli Access Manager v6.0
In addition, the following software is required to deploy multiple instances of the
credit check Web service:
- WebSphere Portal Server v6.0
- WebSphere Process Server v6.1
- Tivoli Directory Server v6.0
| 
