Building SOA portfolio Business Services, part 8th

Part 8th: Using the WebSphere portlet Factory dynamic Overview to build portlets for multiple tenants

This article is part 8th of this series of articles, which focuses on the development of a composite business service (CBS). CBS provides the ability to integrate existing technologies and products to reflect the business intent required, such as configurable. IBM Websphere®portlet Factory is a portlet creation environment that simplifies and accelerates the development, deployment, maintenance, and reuse of portlets. This article describes how to use the WebSphere Portlet Factory to implement configurable in the presentation layer by leveraging dynamic overviews.

Introduction

The dynamic profiling feature of the WebSphere Portlet Factory can help developers create multiple, highly customized applications from a code base. With this dynamic profiling feature, you can define various variables in a common profile set, and multiple tenants in a shared environment can configure the profile set. You can create multiple applications by applying these configured profiles to portlets to change their appearance, content, and portlet behavior. In this article, you will see an extension of the multiple tenant scenarios described in part 1th. In part 8th, you will learn how to implement, manage, and specify the WebSphere Portlet Factory profile for multiple tenants in a composite application that is used in a banking business. This paper compares the dynamic profiling configuration function with the basic configuration function provided by the Portlet, and ends with this.

Defining scenes

The use case of the Jivaro banking business is described in Figure 1, and the dynamic summary functionality is shown here.

Figure 1. Jivaro Use Cases

Participants in this scenario include:

Bank Provider Operations Administrator: Administrators with configuration permissions for the bank profile of the Jivaro bank.

Bank administrator: A manager in each managed bank that can perform account operations through a Web page.

Bank Customers: A client in a managed bank that has permission to view account information through a Web page.

The account object is the subject in this scene. This scenario illustrates how the two banks in the Jivaro environment Bank1 and BANK2 Customize the display appearance of public account objects in each bank's portal.

Implementation scenario

The WebSphere Portlet Factory runtime can be run as a public dynamic WEB application in the Portal server. In this scenario, each bank has a profile configured, and the WebSphere portlet Factory uses this profile to generate different portlets. When bank customers log in to their bank, the portal Server selects the profile for their bank to provide the appropriate parameters for the portal. Figure 2 shows two different Web pages on the left and right, using different profiles and generating them from the same code. Note that the values of the labels and optional options are different. Bank 001 marks the Sixth field as account Name, and bank 002 marks the sixth field as Branch. In the Account Type field, Bank 001 provides two choices (savings or checking), while Bank 002 provides three choices (savings, checking, and external).

The Portlet at the top of Figure 2 shows the configuration features of the banking Provider Operations Administrator.

Figure 2. Overview mechanism