Skip to main content

skip to main content

developerWorks  >  SOA and Web services  >

Develop and Deploy Multi-Tenant Web-delivered Solutions Using IBM Middleware: Part 7: A Web service mediation proxy pattern for routing multiple tenant requests using WebSphere Enterprise Service Bus

developerWorks
Page 1 of 7 Go to the next page

Document options
PDF format - Fits A4 and Letter

PDF - Fits A4 and Letter
320 KB (18 pages)

Get Adobe® Reader®

Discuss

Sample code


My developerWorks needs you!

Connect to your technical community


Rate this tutorial

Help us improve this content


Level: Intermediate

Indrajit Poddar (ipoddar@us.ibm.com), Software Architect, IBM
Devaprasad Nadgir (devaprasad@in.ibm.com), IBM Certified Senior IT Architect, IBM
Sobha R. Warrier (sobharwa@in.ibm.com), SOA Architect, IBM

29 Jul 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. We presented a mediation approach for addressing this challenge and introduced three implementation options using multiple IBM middleware products. In this tutorial, we describe detailed implementation steps for utilizing WebSphere Enterprise Services Bus for enabling multi-tenancy for existing Web services.

Before you start

About this tutorial

In this tutorial, we will describe how to exploit the routing capability of WebSphere Enterprise Service Bus in conjunction with dynamic searches for service endpoint metadata from WebSphere Service Registry and Repository for enabling multi-tenancy. We will also show how to integrate the routing capability with access control functions by integrating with Tivoli Access Manager.


Figure 1. Enabling multi-tenancy for a Web service using a WESB mediation module
Enabling multi-tenancy for  an example web service using a WESB mediation module

In part 4, we described a scenario and a use case with Sam Peters as the service provider for the Jivaro bank multi-tenant application. In this tutorial, we will show how Sam Peters, enables multi-tenancy for his existing single tenant Credit Check Web service through the following steps:

  1. Create a mediation module in WESB for routing tenant requests (Section 3)
  2. Add tenant specific service metadata for routing to WSRR (Section 4)
  3. Add authorization policies in Tivoli Access Manager (Section 5)


Back to top


Prerequisites

Sam Peters will use the following tool to develop the mediation approach:

  1. WebSphere Integration Developer (WID) v6.1

following software to deploy the mediation approach:

  1. WebSphere Enterprise Service Bus (ESB) (or process server) v6.1
  2. WebSphere Service Registry and Repository (WSRR) v6.1
  3. Tivoli Access Manager (TAM/TDS v6)

The following software to deploy multiple instances of the credit check Web service, one per tenant:

  1. WebSphere Portal Server v6
  2. WebSphere Process Server v6.1

Please refer to the Resources section for further details on the installation and integration of these products.



Back to top



Page 1 of 7 Go to the next page