Configure Web Sphere Portal to use Oracle
Added by Asmita Mohapatra | Edited by Asmita Mohapatra on December 2, 2011 | Version 4
Abstract
No abstract provided.
Configuring Web Sphere Portal to use Remote Databases
Portal will be configured to use an external database. For the purposes of this document, Oracle will be used as the external database . This may vary in your Environment. For
more information about databases that can be used with Portal, please visit the Web Sphere Portal v6.1 Information Center for configuring external databases at this link and follow
the instructions there as appropriate:
http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/index.jsp?topic=/com.ibm.wp.ent.doc/config/win_remote_db.html
This doc assumes oracle has been already installed on the server.
Creating ORACLE database
A remote database resides on a different system than Web Sphere Portal. When you use a remote server, you must manually create the databases that are required by Web
Sphere Portal.
1.Run dbca command on the oracle server system to create the necessary databases:
In Unix,log in as Oracle User instead of root with the correct password
On Windows,go to Oracle installation path in command line then fire dbca
Notes:
* Run the command and each time give dbname as release, community, customization, Java Content Repository, Feedback, and Likeminds.
Remember: database names cannot exceed eight characters. Therefore, consider using these database names: release, commun, custom, jcrdb, fdbkdb, and lmdb.
( For space constraint , create only two dbs like orcl and jcr in stead of creating six separate dbs.Instances can be created under orcl db as mentioned below section)
Run dbca cmd and follow the below screen shots to create all the required dbs
Community Articles > IBM Accelerators for WebSphere Portal > IBM Mobile Portal Accelerator > Configure Web Sphere Portal to use Oracle
Creating Users
1. Start the Oracle SQL command line processor 'SQL*Plus' by entering sqlplus /nolog on the operating system
command prompt
2. Log into Oracle database by executing command
sqlplus user/password@database name
For JCR DB
sqlplus sys/password@jcrdb as sysdba
create user icmadmin identified by password default tab lespace users temporary tab lespace temp;
GRANT create session,alter session,create tab le,create view,create procedure,create trigger,create library,create tab lespace,alter tab lespace,drop tab lespace,execute any
procedure,unlimited tab lespace,create public synonym,drop public synonym,create sequence to icmadmin;
grant select on dba_pending_transactions to icmadmin;
grant connect,resource,dba to icmadmin;
grant insert any tab le to icmadmin;
Note: If you had created separate DBs , use that DB name instead of orcl in the below commands while creating the user
For Others DB under ORCL
sqlplus sys/orcl@orcl as sysdba
create user releaseusr identified by password default tab lespace users temporary tab lespace temp;
create user releaseusr identified by password default tab lespace users temporary tab lespace temp;
GRANT create session,alter session,create tab le,create view,create procedure,create trigger,create library,create tab lespace,alter tab lespace,drop tab lespace,execute any
procedure,unlimited tab lespace,create public synonym,drop public synonym,create sequence to releaseusr;
grant select on dba_pending_transactions to releaseusr;
grant connect,resource,dba to releaseusr;
grant insert any tab le to releaseusr;
quit
sqlplus sys/password@orcl as sysdba
create user communityusr identified by password default tab lespace users temporary tab lespace temp;
GRANT create session,alter session,create tab le,create view,create procedure,create trigger,create library,create tab lespace,alter tab lespace,drop tab lespace,execute any
procedure,unlimited tab lespace,create public synonym,drop public synonym,create sequence to communityusr;
grant select on dba_pending_transactions to communityusr;
grant connect,resource,dba to communityusr;
grant insert any tab le to communityusr;
quit
sqlplus sys/password@orcl as sysdba
create user customizationusr identified by password default tab lespace users temporary tab lespace temp;
GRANT create session,alter session,create tab le,create view,create procedure,create trigger,create library,create tab lespace,alter tab lespace,drop tab lespace,execute any
procedure,unlimited tab lespace,create public synonym,drop public synonym,create sequence to customizationusr;
grant select on dba_pending_transactions to customizationusr;
grant connect,resource,dba to customizationusr;
grant insert any tab le to customizationusr;
quit
sqlplus sys/password@orcl as sysdba
create user lmdbusr identified by password default tab lespace users temporary tab lespace temp;
GRANT create session,alter session,create tab le,create view,create procedure,create trigger,create library,create tab lespace,alter tab lespace,drop tab lespace,execute any
procedure,unlimited tab lespace,create public synonym,drop public synonym,create sequence to lmdbusr;
grant select on dba_pending_transactions to lmdbusr;
grant connect,resource,dba to lmdbusr;
grant insert any tab le to lmdbusr;
quit
sqlplus sys/password@orcl as sysdba
create user feedback identified by password default tab lespace users temporary tab lespace temp;
GRANT create session,alter session,create tab le,create view,create procedure,create trigger,create library,create tab lespace,alter tab lespace,drop tab lespace,execute any
procedure,unlimited tab lespace,create public synonym,drop public synonym,create sequence to feedback;
grant select on dba_pending_transactions to feedback;
grant connect,resource,dba to feedback;
grant insert any tab le to feedback;
quit
For JCRDB
a. Remember to create the direcroties "data" and "index" under /oradata/jcrdb
b. Grant the permission for icmadmin as given below:
c. Do the following
mkdir -p /u01/app/oracle
chown -R oracle:oinstall /u01/
chmod -R 775 /u01/
d. Create table space
Before executing the script jcr_ora_tablespaces.sql file ... edit the values for
jcrdb = jcrdb
define dbpath = /oracle/oradata; (give the path)
Execute the SQL script jcr_ora_tablespaces.sql, This file is available in portal machine.
portal_server_root/ installer/wp.config/config/templates/db/oracle/.Copy this file to Oracle server.
1. sqlplus icmadmin/password@jcrdb
Enter dbadmin: icmadmin
Enter password: password
SQL > @jcr_ora_tablespaces.sql
************************************************************************************************
DB Migration
If are using a Cluster all of the steps in this section will be done from the primary Portal node.
1. Stop the WebSphere_Portal and server1 by executing the following commands from thecommand window in the
/bin directory:
stopServer.bat WebSphere_Portal -user -password stopServer.bat server1 -user -password
2. Ensure the Oracle database is installed and configured on the node.
For Oracle 11G
copy ojdbc6.jar file from Oracle server (/u01/app/oracle/product/11.1.0/db_1/jdbc/lib)to some directory on the
primary Portal server.
3. From the /ConfigEngine/properties directory, make a backup of the following files:
wkplc.properties
wkplc_dbtype.properties
wkplc_comp.properties
4. Edit the wkplc_dbtype.properties file and make the following changes:
oracle.DbDriver=oracle.jdbc.OracleDriver
oracle.DbLibrary=/opt/IBM/WebSphere/oraclejar/ojdbc6.jar
oracle.JdbcProviderName=wpdbJDBC_oracle
NOTE: The entry for oracle.DbLibrary is an example only. Please ensure this is a valid path on your system.
5. Edit the wkplc_comp.properties file and make the following changes: ( Use wkplc_dbdomain.properties in Portal 7.0
instead wkplc_comp)
This setting assumes that there are only two dbs created orcl and jcrdb.Rest are the instances for orcl.
release.DbType=oracle
release.DbName=orcl
release.DbSchema=releaseusr
release.DbNameOnZos=WPSTST02
release.DataSourceName=reldbDS
release.DbUrl=jdbc:oracle:thin:@mydbserver.in.ibm.com:1521:orcl
release.DbUser=releaseusr
release.DbPassword=password
release.DBA.DbUser=releaseusr
release.DBA.DbPassword=password
community.DbType=oracle
community.DbName=orcl
community.DbSchema=communityusr
community.DbNameOnZos=WPSTST02
community.DataSourceName=commdbDS
community.DbUrl=jdbc:oracle:thin:@mydbserver.in.ibm.com:1521:orcl
community.DbUser=communityusr
community.DbPassword=password
community.DBA.DbUser=communityusr
community.DBA.DbPassword=password
customization.DbType=oracle
customization.DbName=orcl
customization.DbSchema=customizationusr
customization.DbNameOnZos=WPSTST02
customization.DataSourceName=custdbDS
customization.DbUrl=jdbc:oracle:thin:@mydbserver.in.ibm.com:1521:orcl
customization.DbUser=customizationusr
customization.DbPassword=password
customization.DBA.DbUser=customizationusr
customization.DBA.DbPassword=password
jcr.DbType=oracle
jcr.DbName=jcrdb
jcr.DbSchema=icmadmin
jcr.DbNameOnZos=WPSTST02
jcr.DataSourceName=jcrdbDS
jcr.DataSourceName=jcrdbDS
jcr.DbUrl=jdbc:oracle:thin:@mydbserver.in.ibm.com:1521:jcrdb
jcr.DbUser=icmadmin
jcr.DbPassword=password
jcr.DBA.DbUser=icmadmin
jcr.DBA.DbPassword=password
feedback.DbType=oracle
InitializeFeedbackDB=true
feedback.DbName=orcl
feedback.DbSchema=feedback
feedback.DbNameOnZos=WPSTST02
feedback.DataSourceName=fdbkDS
feedback.DbUrl=jdbc:oracle:thin:@mydbserver.in.ibm.com:1521:orcl
feedback.DbUser=feedback
feedback.DbPassword=password
feedback.DBA.DbUser=feedback
feedback.DBA.DbPassword=password
likeminds.DbType=oracle
likeminds.DbName=orcl
likeminds.DbSchema=lmdbusr
likeminds.DbNameOnZos=WPSTST02
likeminds.DataSourceName=likemindsdbDS
likeminds.DbUrl=jdbc:oracle:thin:@mydbserver.in.ibm.com:1521:orcl
likeminds.DbUser=lmdbusr
likeminds.DbPassword=password
likeminds.DBA.DbUser=lmdbusr
likeminds.DBA.DbPassword=password
Update the following property in the file wkplc.properties.
For WasPassword, type the password for the WebSphere Application Server security authentication used in your
environment.
PortalAdminPwd=password
WasPassword=password
6. From a command window, change directories to /ConfigEngine
7. Execute the following ConfigEngine scripts to validate the database properties:
ConfigEngine.bat validate-database-driver
ConfigEngine.bat validate-database-connection
8. Execute the following ConfigEngine script to transfer the database from Derby to DB2:
ConfigEngine.bat database-transfer -DPortalAdminPwd=password -DWasPassword=password
9. Restart all servers and check the logs. (server1 and WebSphere_Portal)
Attachments (0)
Versions (4)
Comments (0)