<<

. 16
( 87 .)



>>

db2 update database configuration for wps50 using applheapsz 16384
app_ctl_heap_sz 8192
db2 update database configuration for wps50 using stmtheap 60000
db2 update database configuration for wps50 using locklist 400
db2 update database configuration for wps50 using indexrec RESTART
db2 update database configuration for wps50 using logfilsiz 1000
db2 update database configuration for wps50 using logprimary 12
db2 update database configuration for wps50 using logsecond 10
db2set DB2_RR_TO_RS=yes
P1: GIG
WY009-04 WY009-BenNatan-v1.cls May 9, 2004 5:18




Customizing WebSphere Portal 71


3. Enter the following commands in a DB2 Command Window to set up
WebSphere Portal content publishing database:
db2 create database wpcp50 using codeset UTF-8 territory us collate
using identity
db2 create database fdbk50 using codeset UTF-8 territory us collate
using identity
db2 update database configuration for wpcp50 using applheapsz 4096
db2 update database configuration for fdbk50 using applheapsz 4096
db2 update database configuration for wpcp50 using logfilsiz 4096
db2 update database configuration for fdbk50 using logfilsiz 4096
db2 update database configuration for wpcp50 using logprimary 4
db2 update database configuration for fdbk50 using logprimary 4
db2 update database configuration for wpcp50 using logsecond 25
db2 update database configuration for fdbk50 using logsecond 25

4. Edit C:\WINNT\system32\drivers\etc\services and ensure
the following entries for the DB2 connection and interrupt service
ports:
db2c_db2 50000/tcp # DB2 connection service port
db2c_db2CTLSV 50001/tcp # DB2 interrupt service port

5. In a DB2 Command Window, set DB2COMM to TCP/IP and then set
up the service name:
db2set DB2COMM=TCPIP
db2 UPDATE DBM CFG USING db2c_db2

6. Restart the database server.


Installing DB2 Client on WebSphere Portal Server
Next, you need to install the DB2 client on the WebSphere Portal Server so
that it can access the remote DB2 server. This means you have to install the
DB2 client and then con¬gure it. Assume the following:
WebSphere Portal, IBM HTTP Server, and WebSphere Administrator
Server are on one machine and that it is a Windows 2000 Advance
server.
The user wpsdbusr has been set up and has administrative rights, is
de¬ned locally, can act as part of the operating system, and is able to
create a token object, increase quotas, and replace a process level
token.
You are logged in as wpsdbusr.
Port 50000 and 50001 can access the client. This implies that the
¬rewalls are con¬gured to allow these ports.
P1: GIG
WY009-04 WY009-BenNatan-v1.cls May 9, 2004 5:18




72 Chapter 4


The following are the steps to do this:

1. Place the DB2 Enterprise Edition for windows CD into the drive. If
autorun is enabled, you will see the Welcome screen. If not enter
<D> :Setup, where <D> is your CD drive.
2. Click Install Products.
3. On Select the Product You Like to Install, click Next.
4. The Welcome to DB2 Setup screen appears. Click Next.
5. Accept the license agreement and click Next.
6. Choose Custom as the installation type and click Next.
7. Keep the default installation action and click Next.
8. The next screen will list the features you want to install. Unclick all
features except Client Support. Also choose the installation
directory. Click Next. See Figure 4-2.
9. A warning screen will appear if you have a ¬rewall enabled. Click
OK; however, it is strongly recommended to install the product with
the ¬rewall disabled.




Figure 4-2 DB2 features required on WebSphere Portal Server.
P1: GIG
WY009-04 WY009-BenNatan-v1.cls May 9, 2004 5:18




Customizing WebSphere Portal 73




Figure 4-3 De¬ning the DB2 administrator.


10. Select installation language and con¬rm folder. Click Next.
11. Input user information for DB2 administrator and click Next. We
have de¬ned the DB2 administrator to be wpsdbusr. See Figure 4-3.
12. Set up your administrator contact list as per your company policies
and click Next.
13. Keep the default Create a DB2 Instance and click Next.
14. Under Con¬gure DB2 Instances, keep the default values and click
Next. The name of the DB2 Instance on the client must be the same
as the name of the DB2 Instance on the server.
15. Under Prepare the DB2 Tools catalog, keep the default value and
click Next.
16. Specify your health contact as per your company policies and click
Next.
17. Under Request Satellite Information, specify a satellite ID. This ¬eld
is optional. If not speci¬ed, your login ID or wpsdbusr will be used.
18. Next will appear a screen listing the components you will be
installing (for example, Figure 4-4). Click Install.
P1: GIG
WY009-04 WY009-BenNatan-v1.cls May 9, 2004 5:18




74 Chapter 4




Figure 4-4 DB2 Client installation component list.


19. After you have successfully installed the client and restarted the
server, log in as wpsdbusr.
20. In a DB2 Command Window, set DB2COMM to TCP/IP;
db2set DB2COMM=tcpip

21. In a DB2 Command Window, catalog the TCP/IP node with the IP
address of the remote database;
db2 catalog tcpip node was1 remote sandbox2.rigoroconsultants.com
server db2c_db2

Here was1 is the node name we are assigning to the WebSphere
Application Server node, sandbox2.rigorconsultants.com is
our remote database server host name, and dbc db2 is the name of
the DB2 connection service port.
22. In a DB2 Command Window, catalog WebSphere Portal Server
databases as aliases on the client.
db2 catalog db wps50 as wps50 at node was1
db2 catalog db wpcp50 as wpcp50 at node was1
db2 catalog db fdbk50 as fdbk50 at node was1
P1: GIG
WY009-04 WY009-BenNatan-v1.cls May 9, 2004 5:18




Customizing WebSphere Portal 75


In this particular example, the name of the database on the server is
the same as the alias on the client.



Using Oracle and SQL Server with
WebSphere Portal
After you have installed DB2 on the client and server and created the ap-
propriate tables, the next step is to modify WebSphere Portal con¬guration
to support the database. But ¬rst let us go on a bit of a tangent to examine
the support of other databases, since the last step is pretty independent of
the database.
Although DB2 is an excellent database and comes with WebSphere Portal
Extend and WebSphere Portal Experience, many sites have standardized on
other databases. Two most popular databases are Microsoft™s SQL Server
and Oracle™s database. In this section, you will ¬nd out what you need to
do if you want to use SQL Server 2000 or Oracle 9i as the database instead
of DB2 for the con¬guration in Figure 4-1. For the purpose of conciseness,
let™s assume that the databases have already been installed on the remote
server and con¬gured and tested to communicate with the WebSphere Por-
tal Server. For Oracle, this implies that you are using the Oracle JDBC/OCI
Type 2 drivers and that you copied the classes12.zip ¬le from the re-
mote Oracle server to the WebSphere Portal Server.


Step 1: Create the Databases
On sandbox2.rigorconsultants.com, create the databases wps50,
wpcp50, and fdbk50. For SQL Server 2000, insure that your Collation Name
is a case-sensitive collation. For English, set the collation name to SQL
latin1 General CP1 CS AS. For Oracle 8i, insure that the databases are cre-
ated as UTF-8 character set databases.


Step 2: Create the Database Users
To use Oracle 9i or SQL Server 2000 with WebSphere Portal, we recommend
six users be created in uppercase format: WPSDBUSR and WMMDBUSR
that are associated with the database wps50, PZNADMIN, EJB, and WCMD-
BADM that are associated with wpcp50, and FEEDBACK that is associated
with fdbk50. WPSDBUSR will own approximately 76 tables, which will
consist of WebSphere Portal core objects. WMMDBUSR will own approx-
imately 17 pages consisting of Member Manager objects. PZNADMIN
P1: GIG
WY009-04 WY009-BenNatan-v1.cls May 9, 2004 5:18




76 Chapter 4


will own approximately 11 tables and EJB will own approximately 2 tables
and they will both jointly own the tables for personalization information.
WCMDBADM will own approximately 61 tables consisting of content pub-
lishing information. Lastly FEEDBACK will own 48 tables for the purpose
of logging site and personalization usage. Note again this table size might
¬‚uctuate greatly depending on site usage, so con¬gure it carefully.



Step 2a: Create SQL Server 2000 Database Users
To create database users for SQL Server, use SQL Server Enterprise Manager
as follows:

1. Right-click SQL Server Group ➪ Local ➪ Security ➪ Login and
left-click on New Login.
2. Enter the database username ( WPSDBUSR, WMMDBUSR,
PZNADMIN, EJB, WCMDBADM, or FEEDBACK).
3. Select SQL Server Authentication.
4. Set a password for the selected user.
5. Select the default database for each user using the mappings
discussed in the beginning of this section. For instance, WPSDBUSR
default database is wps50.
6. Click on the Server Role tab and make sure that no Server Role is
selected.
7. Click on the Database Access tab. Enable permissions based on
what™s shown in Table 4-3.
8. Click OK to save the user changes.


Table 4-3 Recommended Database Access Roles
USERNAME DATABASE DATABASE ROLE

WPSDBUSR wps50 public, db owner

WMMDBUSR wps50 public, db owner

PZNADMIN wpcp50 public, db owner

EJB wpcp50 public, db owner

WCMDBADM wpcp50 public, db owner

FEEDBACK fdbk50 public, db owner
P1: GIG
WY009-04 WY009-BenNatan-v1.cls May 9, 2004 5:18




Customizing WebSphere Portal 77


Step 2b: Create Oracle Database Users
To create the database users for Oracle, use SQL*Plus:
1. Enter username: system/manager@wps50. This will log the

<<

. 16
( 87 .)



>>