<<

. 17
( 87 .)



>>

administrative user system with a password of manager into the
wps50 database. Replace manager with the System Administrator™s
password.
2. Create the WebSphere Portal users and grant them appropriate
privileges.
create user WPSDBUSR identified by PASSWORD default tablespace USERS
temporary tablespace TEMP;
create user WMMDBUSR identified by PASSWORD default tablespace USERS
temporary tablespace TEMP;
grant connect, resource to WPSDBUSR;
grant connect, resource to WMMDBUSR;

3. Connect to the content publishing database by entering connect and
then username: system/manager@wpcp50. This will log the
administrative user system with a password of manager into the
wpcp50 database. Replace manager with the System Administrator™s
password.
4. Create the content publishing users and grant them appropriate
privileges.
create user PZNADMIN identified by PASSWORD default tablespace USERS
temporary tablespace TEMP;
create user EJB identified by PASSWORD default tablespace USERS
temporary tablespace TEMP;
create user WCMDBADM identified by PASSWORD default tablespace USERS
temporary tablespace TEMP;
grant connect, resource to PZNADMIN;
grant connect, resource to EJB;
grant connect, resource to WCMDBADM;
grant insert any table to WCMDBADM;

5. Connect to the Feedback database by entering connect and then
username: system/manager@fdbk50. This will log the administrative
user system with a password of manager into the fdbk50 database
and again replace manager with the System Administrator™s
password.
6. Create the content publishing feedback user and grant it appropriate
privileges.
create user FEEDBACK identified by PASSWORD default tablespace USERS
temporary tablespace TEMP;
grant connect, resource to FEEDBACK;

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




78 Chapter 4


Con¬guring WebSphere Portal to Access a
Remote Database
Now that the database is installed and con¬gured, you need to con¬gure
WebSphere Portal to access and populate the database with WebSphere
Portal system and user data. The method used, as stated previously, will
be the same for any remote database, except that the property values will
be different. The con¬guration for a local database is simpler, because con-
¬guration templates exist for Oracle, SQL server, Informix, and DB2 that
con¬gure and transfer the data all in one step.
However for a remote database, such as the one shown in Figure 4-1, the
process is more dif¬cult. Perform the following steps to con¬gure a remote
database for WebSphere Portal on a Windows 2000 Advanced Server:

1. Open a command prompt and change the directory to
<wp_root>\config.
2. Export the current database data by entering WPScon¬g.bat
database-transfer-export. Execution of this command can take some
time; if execution is successful, a message will be displayed indicating
success. You can also see if it has executed successfully by looking at
the logs at <wps_root>\log\configmessages. Executing the
command is similar under Unix except for the OS syntax differences.
However in Linux the task name is database-transfer-export-linux.
After the command has executed, all the data will be stored in the
directory <wps_root>\config\DBTRansfer.
3. Copy <wp_root>\config\wpconfig.properties to
<wp_root>\config\wpconfig.bkp.
4. Using a test editor, edit <wp_root>\config\wpconfig
.properties and for the properties described in Tables 4-4“4-6,
enter the appropriate values. The values entered in the table support
the example de¬ned in Figure 4-1. Note that this is a Java properties
¬le, so a backward slash (\) is represented as a forward slash (/).
5. Save the ¬le.
6. Test that the properties are valid by entering the following
commands in a command prompt:
WPSconfig.bat validate-database-connection-wps
WPSconfig.bat validate-database-connection-wmm
WPSconfig.bat validate-database-connection-wpcp
These commands will test the database connection. If the response is
positive go to the next step, otherwise check your properties to see if
they are valid. Very often it is an invalid port or a port/IP address
that is inaccessible due to a ¬rewall con¬guration.
P1: GIG
WY009-04




Table 4-4 Con¬guration Database Properties
PROPERTY VALUE

PROPERTY DESCRIPTION DB2 ORACLE SQL SERVER
WY009-BenNatan-v1.cls




DbSafeMode If this property is set to true, no False False False
database-speci¬c updates are performed

DbType Database used to store information for db2 oracle sqlserver
WebSphere Portal

WpsDbName Database name or alias name if remote wps50 wps50 wps50
where WebSphere Portal objects are stored

DbDriver Name of the JDBC provider used to import COM.ibm.db2. oracle.jdbc.driver. com.microsoft.
SQL ¬les jdbc.app.DB2 OracleDriver jdbc.sqlserver.
Driver SQLServerDriver




79
DbDriverDs The data source for the JDBC provider that Not applicable oracle.jdbc.pool. com.microsoft.
WebSphere Portal used to import SQL ¬les OracleConnection- jdbcx.sqlserver.
PoolDataSource SQLServerData
Source

DbUrl The database URL used to access the jdbc:db2:wps jdbc:oracle:thin:@ jdbc:microsoft:
sandbox2
WebSphere Portal database 50 sqlserver://
.rigorconsulta sandbox2
nts.com:1521: .rigorconsultants
.com:1433:Database
wps50
Name = wps50

DbUser The database administrative username wpsdbuser WPSDBUSER WPSDBUSER

DbPassword The 1database administrative username “ “ “
password

(continued)
May 9, 2004
5:18
P1: GIG
WY009-04




Table 4-4 (continued)
PROPERTY VALUE

PROPERTY DESCRIPTION DB2 ORACLE SQL SERVER
WY009-BenNatan-v1.cls




C:/Program C:/Program C:/Program
DbLibrary Location db2java.zip for DB2
Files/SQLLIB/ Files/oracle/ Files/mssql/lib/
java/db2/ jdbc/lib/ mssqlserver.jar;
java.zip classes12
.zip

C:/Program Files/
mssql/lib/msbase
.jar;




80
C:/Program
Files/mssql/lib/
msutil.jar

WpsDsName The name of the datasource used for the wps50DS wps50DS wps50DS
WebSphere Portal database

WpsXDbName The TCP/IP alias for the database to be used wps5TCP Not applicable Not applicable
as dsname. Only needs to be set for Unix or
Linux servers

WpsDbNode The node name of the WebSphere Portal wpsNode Not applicable Not applicable
database. Only needs to be set for Unix or
Linux servers
May 9, 2004
5:18
P1: GIG
WY009-04




Table 4-5 Con¬guration Content Publishing Database Properties
PROPERTY VALUE

PROPERTY DESCRIPTION DB2 ORACLE SQL SERVER
WY009-BenNatan-v1.cls




sandbox2.rigor-
WpcpDbHost Host name of the machine running SQL Not applicable Not applicable
consultants.com
Name Server

WpcpDbNode The node name of the WebSphere Portal wpcpNode Not applicable Not applicable
content publishing database. Only needs to
be set for Unix or Linux server

WpcpXDbName The TCP/IP alias for the WebSphere Portal wpcp5TCP Not applicable Not applicable
content publishing database. Only needs to
be set for Unix or Linux server

FeedbackXDb The TCP/IP alias for the feedback database. fdbk5TCP Not applicable Not applicable




81
Name Only needs to be set for Unix or Linux server

WpcpDbName The database name or alias name where wpcp50 wpcp50 wpcp50
the WebSphere Portal content publishing
objects are created

WpcpDbUser The database administrative username wpsdbusr WCMDBADM WCMDBADM

WpcpDb The password for the database user
Password associated with WpcpDbUser

WpcpDbUrl The database URL used to access the jdbc:db2:wpcp50 jdbc:oracle:thin: jdbc:microsoft:sql-
WebSphere Portal content publishing @sandbox2 server: // sandbox2
.rigorconsultants .rigorconsultants.
database
.com:1521:wpcp50 com:1433:Database
Name = wpcp50

(continued)
May 9, 2004
5:18
P1: GIG
WY009-04




Table 4-5 (continued)
PROPERTY VALUE

PROPERTY DESCRIPTION DB2 ORACLE SQL SERVER
WY009-BenNatan-v1.cls




WpcpDbEjb The password for the Enterprise Java Bean Not applicable
Password (EJB) user

WpcpDbPznad- The password for the PZNADMIN user Not applicable
min Password

sandbox2.rigor-
FeedbackDb host name of the machine Not applicable Not applicable

<<

. 17
( 87 .)



>>