Set up the database.
Set up the Web Container for the New Database.
Configure Community Membership and Configuration.
Configure the communitymc database configuration file:
PORTAL-DATA-DIR/portals/PORTAL-ID/config/portal.dbadmin.
Parameters
db.driver=vendor-specific-classpath.jdbc.ClientDriver
db.driver.classpath=/opt/jarfile-directory-pathclient.jar
community.db.user=database-user-account (created in step 1c).
community.db.password=database-user-account-password (created in step 1c).
community.db.url=jdbc:xxx://xxxxx.pstest.com:port/database-instance-created-in-step-1b.
Remove the derby-specific property in:
PORTAL-DATA-DIR/portals/PORTAL-ID/config/communitymc.properties.
For example: javax.jdo.option.Mapping=derby
Load the schema onto the database by using the following commands:
cd /var/opt/SUNWportal/portals/portal1/config
/usr/sfw/bin/ant -f config.xml -D"portal.id=portal1" configure
Edit the JDBC resource in the web container configuration to point to the new database.
Configure and Install Portlet Applications.
Locate the portlet applications:
PORTAL-DATA-DIR/portals/PORTAL-ID/portletapps
Configure the portlet applications to use the new database, for example:
cd /var/opt/SUNWportal/portals/portal1/portletapps/surveys
Edit the tokens_xxx.properties file.
Create the JDBC Resource for each application using the values from the tokens_xxx.properties file.
Resource JNDI Name: jdbc/DB-JNDI-NAME
Resource Type: javax.sql.DataSource
Datasource Classname: DB-DATASOURCE
User: DB-USER
Password: DB-PASSWORD
URL: DB-URL
Undeploy the existing portlets that use Derby Database as the datastore.
Deploy the newly configured portlet applications.