Document Management Using WebSphere Portal V5.0.2 and DB2 Content Manager V8.2

262 Document Management Using WebSphere Portal V5.0.2 and DB2 Content Manager V8.2

7.1 Planning

This section describes the scenario for ITSO working example development

environment, and provides information regarding the hardware and software

levels we used to implement the environment.

7.1.1 Architecture overview

Figure 7-1 depicts the development environment used for the ITSO working

example.

Figure 7-1 ITSO working example development environment

We would like to highlight a few key points regarding the ITSO development

environment.

 Although Figure 7-1 displays four physical nodes, we used VMWare for the

Document Management node and Portal Server node test nodes.

 The Developer node includes WebSphere Studio Application Developer,

Portal Toolkit and Test Environment and is the primary node for development.

In addition, the Developer node includes DB2 Information Integrator for

Content.

Developer

node

Developer

(dev1)

Developer

node

Developer

(dev1)

Document

Management

(cmtest1)

Portal

Server

(wpstest1)

Code

Repository

(cvsrep1)

1..n Developer nodes

Unit Test

Integration Test

• WebSphere Portal Extend 5.0.2.1

• IBM HTTP Server 1.3.26.2

• WebSphere Application Server

Enterprise 5.0.2.3

• DB2 UDB Enterprise 8.1.4.428

• DB2 Information Integrator for

Content V8.2 – CM Connector

• Windows 2000 Server + SP4

• DB2 Content Manager 8.2

• DB2 UDB Enterprise 8.1.4.428

• DB2 Net Search Extender 8.1.4

• IBM HTTP Server 1.3.26.2

• WebSphere Application Server 5.0.2

• Microsoft Visual C++ Professional 6.0

• Tivoli Directory Server 5.2 (Server,

Client SDK, Web Admin Tool)

• Windows 2000 Server + SP4

•CVSNT 2.4

• Windows 2000 Server + SP4

• WebSphere Studio Application

Developer 5.1.1

• WebSphere Portal Toolkit 5.0.2.1

• DB2 UDB Enterprise 8.1.4.428

• DB2 Information Integrator for

Content V8.2 – CM Connector

• Windows 2000 Server + SP4

Chapter 7. Development environment installation 263

 There are several possibilities in the ITSO development environment that

developers can develop and test the portlets.

– Local Portal Test Environment

Developers may choose to run and test portlets in the local Portal Test

Environment. This method was used while writing the redbook. The

downside to this environment is that the portal debug page displays all

portlets on a page, thus a developer cannot see the application as it would

run in a production environment.

– Shared Portal Server node

Developers may choose to deploy the portlets to a full WebSphere Portal

integration test node such as the Portal Server node. This environment

allows developers to see the application as it would run in a production

environment. We also used a shared Portal Server node while writing the

redbook. We prefer this configuration for reliability and its production like

capability.

– Remote WebSphere Portal Server with IBM Agent Controller

It is possible to install the IBM Agent Controller. In this case, the Portal

Toolkit is used to develop the portlets in WebSphere Studio Application

Developer and the code is tested on a remote WebSphere Portal Server

with the IBM Agent Controller installed for debug capability with

WebSphere Studio Application Developer.

We did not test this type of configuration while writing the redbook. For

more information refer to the Installation Guide, WebSphere Portal Toolkit

V5.0.2.1 product guide found at:

http://www.ibm.com/websphere/portal/toolkit

7.1.2 Hardware used within the ITSO development environment

We used the following hardware within the ITSO working example document

management development environment on Windows:

 Code Repository node

–IBM

~ xSeries 230

• 1 CPU, Intel PIII 1 GHz

• 1152 MB main memory

• 18 GB hard disk

• 1 IBM Ethernet adapter

Note: We found that the workspace did get corrupted on occasion. We

strongly recommend that once you do get the environment working to

backup your workspace.

264 Document Management Using WebSphere Portal V5.0.2 and DB2 Content Manager V8.2

• Hostname: cvsrep1.itso.ral.ibm.com

 Developer node

– IBM Thinkpad T40

• 1 CPU, Mobile Intel Pentium® 4-M 1.5 GHz

• 2048 GB main memory

• 80 GB hard disk

• 1 IBM Ethernet Adapter

• Hostname: dev1.itso.ral.ibm.com

 Document Management node

–IBM

~ xSeries 230

• 1 CPU, Intel PIII 1 GHz

• 1152 MB main memory

• 18 GB hard disk

• 1 IBM Ethernet adapter

• Hostname: cmtest1.itso.ral.ibm.com

 Portal Server node

–IBM

~ xSeries 230

• 1 CPU, Intel PIII 1 GHz

• 1152 MB main memory

• 18 GB hard disk

• 1 IBM Ethernet adapter

• Hostname: wptest1.itso.ral.ibm.com

7.1.3 Software used within the ITSO development environment

We used the following software levels within the ITSO working example secure

portal development environment on Windows.

Table 7-1 Code Repository node

Note: The configurations described above are not necessary the minimum

requirements for the setup, only the values for memory were chosen to be as

small as possible.

Software Version

Microsoft Windows 2000 Server 2000 + Service Pack 4

CVSNT 2.0.4