<<

. 14
( 87 .)



>>

W wasfix1MediaLocation.cdPath="/mnt/cdrom"

#
# WEBSPHERE PORTAL CD LOCATION
#

-W WPSCDLoc.cdPath="/mnt/cdrom"



#
# PORTAL BASIC CONFIGURATION OPTION
#
# Description: Specify whether you want to perform basic
configuration of
# WebSphere Portal automatically when WebSphere Portal is installed.
# Values:
#
# yes - Basic configuration is performed automatically as part of the
# WebSphere Portal installation. This is the default value and
is
# assumed if the basicConfig.choice parameter is not specified.
#
P1: GIG
wy009-03 WY009-BenNatan-v1.cls May 9, 2004 4:37




60 Chapter 3


# no - Basic configuration is not performed during installation and
must be
# performed manually after installation.

# -W basicConfig.choice="no"

# The options above make this a custom install

-W setupTypePanel.selectedSetupTypeId="custom"

If you have problems creating the response ¬le then before you install,
copy the setup CD to a local drive and CHMOD 777, the installre-
sponse.txt ¬le. The ¬le installresponse.txt is a template of the
response ¬le.


Uninstalling WebSphere Portal on Linux
To uninstall WebSphere Portal on Linux, go to <was_root>/
PortalServer/uninstall and execute ./uninstall.sh. To uninstall
the IBM HTTP Server, go to <ihs_root>/_uninst and enter java -jar
uninstall.jar.

N O T E Even though the IBM Http installed the IBM Global Security Kit, it will not
uninstall it. To uninstall the Global Security Kit, ¬nd the name by entering rpm -
qa | grep gsk; then rpm -e the package.

But what happens if the uninstall does not work, is corrupt, or is acci-
dentally deleted? Then, a manual uninstall is necessary; however, this only
works if you uninstall both WebSphere Portal and WebSphere Application
Server. We are also assuming that you do not have any data that you want
to save. To perform a manual uninstall perform the following steps:
1. Create a backup.
2. Kill all Java processes by typing the command killall -9 java.
3. Edit in the root home directory the vpd.properties ¬le and
remove any entries starting with WS.


Directory Structure
To understand the WebSphere Portal installation in more detail, let™s see
exactly what it creates. In Windows, installation places the information in
the directories as an extension of <was_root>\PortalServer while in
P1: GIG
wy009-03 WY009-BenNatan-v1.cls May 9, 2004 4:37




Installing WebSphere Portal on Linux 61


Linux/Unix, they are an extension of <was_root>/PortalServer. The
following describes the WebSphere Portal directory structure:

wp_root Root directory for WebSphere Portal
|
• uninstall Files used to uninstall WebSphere Portal
|
+-- app Transcoding tag library definition in the /wps.ear/wps.war/WEB-
INF/tld subfolder
|
+-- bin WebSphere Portal tools
|
+-- cloudscape Cloudscape database files
|
+-- config Portal configuration files
|
+-- deployed Copies of the .ear and .war files for
installed portlet applications.
|
+-- dev Resources for portlet developers, including
Struts
|
+-- doc WebSphere Portal InfoCenter and Javadoc
|
+-- IBMTrans Transcoding component
|
+-- installableApps WAR files prior to deployment
|
+-- installedApps Active portlet applications extracted to the
WAR file directory structure
|
+-- launchPad Images used by the WebSphere Portal First
Steps
|
+-- license WebSphere Portal license agreement
|
+-- log WebSphere Portal log files
|
+-- migration Scripts used to assist in migrating from
previous releases of WebSphere Portal
|
+-- odc On-Demand Client files
|
+-- package Response files and utilities for install
|
+-- pb Property broker files for cooperative portlets
| XML files for installing portlets individually
+-- portletscripts
|
+-- shared
P1: GIG
wy009-03 WY009-BenNatan-v1.cls May 9, 2004 4:37




62 Chapter 3


||
| +-- app WebSphere Portal runtime JARs, TLDs, and other resources
||
+-- config Portal configuration files
|||
||
+- services Portal services configuration files (*.properties)
||
| +-- nls WebSphere Portal NLS files
|
| +-- WEB-INF Resources for the WebSphere Portal
||
| +- tld Portal JSP taglibs
|
+-- uninstall Resources for uninstalling WebSphere Portal and components
|
+-- version Version information for various components
|
+-- wmm Member Manager configuration, including attributes of portal
users
|
+-- wpcp WebSphere Portal Content Publisher runtime and resources
|
+-- wts Resources for Transcoding Technology

The WebSphere Portal applications are stored in the WAR directory under
<was_root>/AppServer/installedApps/<hostname>/wps.ear/
wps.war:

wps.war
|
+-- c2a Cooperative portlet resources
|
+-- dtd Document Type Definitions (DTDs) for Portal Server
|
+-- html HTML files for the portal
|
+-- images Graphics for the portal
|
+-- menu Files for MenuService
|
+-- META-INF Metadata for the portal Web application
|
+-- peopleawareness Files for PeopleService
|
+-- screens Screen JSPs for the portal
||
| +-- markup_ name Subdirectory for each markup type
|
|-- skins Skin JSPs for the portal
P1: GIG
wy009-03 WY009-BenNatan-v1.cls May 9, 2004 4:37




Installing WebSphere Portal on Linux 63


||
| +-- markup_ name Subdirectory for each markup type
|_
|-- themes Theme JSPs for the portal
|
| +-- markup_ name Subdirectory for each markup type
|
+-- WEB-INF Resources for the Portal Server Web application




Installing When WebSphere Security Is Enabled
In most production environments, WebSphere security will be enabled. In-
stalling WebSphere Portal with WebSphere security can be unnecessarily
challenging, so disabling security temporarily is highly recommended.
Using the WebSphere administrative console, disable security, install
WebSphere Portal, con¬gure WebSphere Portal to use WebSphere Appli-
cation Server security (discussed in great detail in Chapter 19), and then
re-enable WebSphere Application Server Security.


Summary
In this chapter you learned the tricks to installing WebSphere Portal in a
Linux environment for both graphic and console desktops. However, all of
our installations have dealt with “simplistic” installations. In the next few
installation chapters, we are going to discuss how to con¬gure WebSphere
Portal with more robust databases and to integrate the various supporting
products.
P1: GIG
wy009-03 WY009-BenNatan-v1.cls May 9, 2004 4:37




64
P1: GIG
WY009-04 WY009-BenNatan-v1.cls May 9, 2004 5:18




CHAPTER

4
Customizing WebSphere
Portal

You have now installed WebSphere Portal on both your Windows and Linux
platforms. You are amazed how much easier the installation was compared
to WebSphere Portal 4.X. A few questions to answer, pop in four CDs,
and”voil` !”WebSphere Portal is installed. Now you might be looking at
a
the other 58 CDs and wondering, “what are these for?” Like a person who
has put together a bicycle and ¬nds a few parts left over, you wonder if you
missed something.
Well you haven™t! To simplify the installation process, WebSphere Portal
mandates that the basic con¬guration is installed and then the user modi¬es
it using the tool WPScon¬g. You use WPScon¬g when you want to do the
following:
Change the database from Cloudscape
Use a Directory server
Use a remote Web server
The reason for this design decision is to enable the user to modify the con-
¬guration without having to reinstall the program. This capability clearly
makes sense. Initially, when you install the program, you are testing out the
features, writing some small portlets, and maybe doing a couple of pilots.
For these requirements, you really don™t need security and Cloudscape is
suitable as a database. However, when you want to roll out a real applica-
tion with scalability requirements you will need to add a security model

<<

. 14
( 87 .)



>>