Chapter 5. Before you begin integration: pre-integration validation
5.2 Software requirements and case study setup
In this section, we list all the software requirements for the LWWCM server and the Content Manager server. Depending on the configuration you want to implement, you might have different ways of combining what software should be installed on which machines. For a more specific configuration set, refer to Chapter 8, ”System architecture considerations’ on page ’167’.
5.2.1 Software requirements for LWWCM
LWWCM supports many operating systems and different back-end data repositories.
Operating systems
Operating systems that support LWWCM include the following with their required software levels:
AIX 5.1 ML4, 5.2 Solaris 8, Solaris 9
Windows 2000 Server SP4
Windows 2003 Server
SuSE SLES 8.0 (Kernel 2.4) / Intel® Red Hat AS 2.1 (Kernel 2.4) / Intel
OS400 V5R2 / iSeries™
SuSE SLES 8.0 (Kernel 2.4) / zLinux
Application server
LWWCM supports the following application server with the required software level and fixpacks:
WebSphere Application Server 5.0.1 or 5.0.2. The following fixpacks are mandatory: PQ75699, PQ76313, PQ77142, PQ80288, and PQ81144.
Data repository server
LWWCM supports the following system, database, and software (with the supported software levels) as its back-end data repository:
File system
DB2 7.2.x, 8.1 FP4
DB2 400
Oracle 9i (9.0.2.1)
IBM Content Manager 8.2
Cloudscape™ 5.1.26
SQL Server 2000 SP3a
5.2.2 Software requirements for Content Manager
We list the software requirements for Content Manager V8 for Multiplatforms, including those for Windows and for AIX.
Windows
Running Content Manager V8.2 on Windows NT® or Windows 2000 requires the following software and software levels (Always see the Content Manager installation README information (<ICMROOT>\readme) for the latest version requirements of prerequisite software, including related update or fixpack.):
Database for both Library Server and Resource Manager
– DB2 Application Development Client (known as DB2 Software Development Kit, or SDK) and one of the following:
• DB2 Universal Database™ (DB2 UDB) Enterprise Edition version 7.2 (or later)
• IBM DB2 UDB Enterprise Extended Edition version 7.2.1 with latest fix pack
• IBM DB2 UDB Enterprise Server Edition version 8.1 (included in the IBM Content Manager package with a limited use license)
– For optional support of Oracle:
• Oracle 8.1.7.4 or later
or
Oracle 9.2.0.1 or later Library Server:– Microsoft Visual C++ 6.0 or Microsoft Visual Studio.Net Professional – IBM DB2 Information Integrator Relational Wrappers version 8.1 (included
in the IBM Content Manager package with a limited use license)
Resource Manager:
– WebSphere Application Server V4.0.3 or later or WebSphere Application Server 5.0 (included in IBM Content Manager package with a limited use license)
– Tivoli Storage Manager API Client V4.2.1 (or later), and Tivoli Storage Manager Server version 4.2.1 (or later) if you want to provide long-term storage for your objects on devices other than the fixed disks
Note: Use of IBM DB2 Information Integrator Relational Wrappers version
8.1 requires IBM DB2 UDB Enterprise Server Edition version 8.1 (included in the Content Manager package with a limited use license).
Chapter 5. Before you begin integration: pre-integration validation 69
For text search:
– Text Information Extender V7.2 (if using IBM DB2 UDB version 7.2) – IBM Net Search Extender V8.1 (if using IBM DB2 UDB version 8.1)
AIX
Running Content Manager V8.2 on AIX requires the following software and the software levels:
AIX 4.3.3 with fix pack 8, or later versions of AIX TCP/IP (installed with AIX)
Database for both Library Server and Resource Manager – DB2 SDK for AIX and one of the following:
• IBM DB2 UDB Enterprise Edition 7.2 (or latter)
• IBM DB2 UDB Extended Enterprise Edition 7.2 with the latest fix pack • IBM DB2 UDB Enterprise Server Edition V8.1 (included in the IBM
Content Manager package with a limited use license) – For optional support of Oracle:
• Oracle 8.1.7.4 or later, or • Oracle 9.2.0.1 or later Library Server compiler:
– VisualAge® C++ Professional batch compiler (for AIX 4.3.3, V5.0.2.0) IBM DB2 Information Integrator Relational Wrappers V8.1 (included in the
IBM Content Manager package with a limited use license)
Resource Manager:
– WebSphere Application Server V4.0.3 or later, or
– WebSphere Application Server 5.0 (included in IBM Content Manager package with a limited use license)
– Optional: Tivoli Storage Manager API Client V4.2.1 (or later) and Tivoli Storage Manager Server V4.2.1 (or later) if you want to provide long term storage for your objects on devices other than the fixed disks.
Note: Use of IBM DB2 Information Integrator Relational Wrappers V8.1
requires IBM DB 2 UDB Enterprise Server Edition V8.1 (included in the Content Manager package with a limited use license).
For text search:
– Text Information Extender V7.2 (if using IBM DB2 UDB version 7.2) or – IBM Net Search Extender V8.1 (if using IBM DB2 UDB version 8.1)
5.2.3 Case study setup
Here, we list the software requirements for the case study we set up for this redbook.
Windows
For our case study setup on Windows, we use the following software and the software levels:
IBM WebSphere Application Server V5.0.2.2 with IBM HTTP Server 1.3.26.
IBM Lotus Workplace Web Content Manager V2.0 (LWWCM).
Microsoft Visual C++ V6.0.
DB2 Enterprise Server Edition V8.1 (DB2 ESE).
DB2 NetSearch Extender V81 (DB2 NSE) and Fixpack IC35476.
IBM Content Manager V8.2, Fixpack 3, enable UTF-8 during Library Server Installation, including Content Manager System Administration Client. IBM Content Manager V8.2 Windows Client and/or eClient to import
Document
item objects into the Content Manager system, see “Datamodeling” on page 25.
IBM Information Integrator for Content V8.2, Fixpack 3, EIP Server with Administration Client, Content Manager V8 and the Federated connector. They are used to create federated search templates and to create new federated content Components in LWWCM (see 7.3, “Federated content component” on page 123).
IBM DB2 Content Manager VideoCharger Server and Player V 8.2.
Internet Explorer Browser, the Java Runtime Environment 1.3.9 for LWWCM server is installed automatically on first time startup of the LWWCM user interface. Prerequisite is an
existing
Internet connection. If you are using Internet Explorer as the Web browser, you should also update to V6 including SP1 or higher.AIX
For our case study setup on AIX, we use the following software and the software levels:
Chapter 5. Before you begin integration: pre-integration validation 71
Java 1.3.1.
IBM Visual Age C++ batch Compiler, V5.1.0.25.
IBM WebSphere Application Server V5.0 and Fixpack 5.0.1 with IBM HTTP
Server 1.3.26.
IBM Lotus Workplace Web Content Manager V2.0 (LWWCM).
DB2 Enterprise Server Edition V8.1.1.4 (DB2 ESE).
DB2 NetSearch Extender V81 (DB2 NSE) and Fixpack IC35476.
IBM Content Manager V8.2, Fixpack 3, enable UTF-8 during Library Server Installation.
IBM Information Integrator for Content V8.2, with Information Integrator for Content federated (FED) and Content Manager (ICM) connectors.
Netscape Explorer, the Java Runtime Environment 1.3.9 for LWWCM server is installed automatically on first time startup of the LWWCM user interface. Prerequisite is an
existing
Internet connection.5.2.4 How to check installed software versions
For some of the required software, you can check the version as follows:
For DB2, from a DB2 command window, execute db2level.
For WebSphere, run the versionInfo.bat file.
For IBM HTTP Server, view the version.signature file in the IBM HTTP Server install directory.
For LWWCM, see the version information in the LWWCM user interface. For IBM Content Manager, enter cmlevel.exe in the <ICMROOT>\bin or enter
cmlevel on AIX.
For Information Integrator for Content, execute cmlevel.exe (AIX cmlevel) in the <CMBROOT> directory (AIX <CMBROOT>/bin)
For advanced users, you can also open on Windows Command Prompt window, enter regedit and select My Computer -> HKEY_LOCAL_MACHINE ->
Software. From there, you can find your installed IBM software, open the tree
view and click the Current Version folder. On AIX, you can use smitty and search for example for the Information Integrator for Content product to see the installed version for the content connectors.