222 Using IBM WebSphere Host Access Transformation Services V5
3.4.1 HATS test scenario with portal credential vault
The objective of this scenario is to create a HATS portlet which can use portal
security features to perform a single signon to an AS/400 system. The
application process occurs as explained here:
1. A user written portlet sets a user name and password pair to a portal
credential vault slot.
2. A HATS portlet runs and connects to an AS/400 system.
3. A HATS screen customization is defined for the initial AS/400 log on screen.
4. The screen customization creates two HATS Global Variables.
5. The screen customization runs some HATS Business Logic which accesses
the portal credential vault to access the user name and password, which were
set by the user written portlet in step 1.
6. The business logic sets the user name and password to the global variables
were created in step 4.
7. A logon macro runs. It uses the global variables (set by step 6) to log on to the
8. The AS/400 system main menu is displayed.
The hardware and software environment are the same as for 3.2, “Scenario
topology and preparation” on page 193.
3.4.2 Building the Credential Vault Populate portlet
In this section, we build a simple portlet using WebSphere Portal Toolkit. We use
use this portlet to set a user name and password pair for an AS/400 administrator
slot in the credential vault.
1. Select Start
→Programs →IBM WebSphere HATS →HATS Studio.
2. Select File
Chapter 3. Integrating HATS with WebSphere Portal Server 223
3. A wizard window opens that guides us to create a project. In the New Project
– Select window (Figure 3-38), in the left pane, select Portlet Development.
In the right pane, select Portlet Application Project. Click Next.
Figure 3-38 Creating a new portlet application project
224 Using IBM WebSphere Host Access Transformation Services V5
4. In the Create a Portlet Project – Define the Portlet Project window
(Figure 3-39), for Project name, enter HATSCredential. For Select a portlet
type, select Create basic portlet. Select the Configure advanced options
check box. Click Next.
Figure 3-39 Defining the portlet project
Chapter 3. Integrating HATS with WebSphere Portal Server 225
5. In the J2EE Settings Page panel (Figure 3-40), accept all default option
values. For portlet development, the Enterprise Archive (EAR) file is not
required. We need only the WAR file. Click Next to continue.
Figure 3-40 J2EE Settings Page panel