Appendices

CollabraSuite, BEA Edition J2EE components require specific services and security to be configured and deployed. The following table summarizes the configuration created by the CollabraSuite, BEA Edition Domain Extension Template:

Table 4-1 Domain Extension Summary
Component	Settings
JDBC Connection Pool	Name: csuiteConnectionPool
JDBC Data Source	Name: csuitePool JNDI Name: weblogic.jdbc.jts.csuitePool
JMS Server	Name: csuiteJMSServer JNDI Name: weblogic.jms.csuiteEventTopic
JMS Connection Factory	Name: csuiteConnectionFactory JNDI Name: weblogic.jms.csuiteConnectionFactory
JMS Topic	Name: csuiteEventTopic JNDI Name: weblogic.jms.csuiteEventTopic
JMS Topic	Name: csuiteRemoteEventTopic JNDI Name: weblogic.jms.csuiteRemoteEventTopic
Mail Session	Name: csuiteMailSession JNDI Name: csuiteMail
Admin User	Name: csadmin Default Password: password Member of: CollabraSuiteUsers, CollabraSuiteAdministrators
User Group	Name: CollabraSuiteUsers
Admin Group	Name: CollabraSuiteAdministrators
Remote Group	Name: CollabraSuiteRemote

WebLogic Portal Extension Summary

Integrating CollabraSuite, BEA Edition J2EE components into a WebLogic portal requires specific files to be configured and deployed into the portal application. The following summarizes the configuration performed by the CollabraSuite, BEA Edition Portal Extension Template:

The following files are copied into <portalApplication>/<portalProject>/WEB-INF/lib. They can be found on the distribution CD under the lib directory.

csuite-taglib.jar
common-server.jar
csuite-client.jar
csuite-ejb-client.jar
csuite-i9n-client.jar
csuite-ria-common.jar
csuite-ria-client.jar

The following taglib is added to <portalApplication>/<portalProject>/WEB-INF/web.xml:

<taglib>

   <taglib-uri>csuite-taglib.tld</taglib-uri>

   <taglib-location>/WEB-INF/lib/csuite-taglib.jar</taglib-location>

</taglib>

The following ejb-refs are added to <portalApplication>/<portalProject>/WEB-INF/web.xml:

<ejb-ref>

    <ejb-ref-name>ejb/CSuiteAdmin</ejb-ref-name>

    <ejb-ref-type>Session</ejb-ref-type>

<home>com.collabraspace.csuite.server.i9n.interfaces.CSuiteAdminRemoteHome</home>

<remote>com.collabraspace.csuite.server.i9n.interfaces.CSuiteAdminRemote</remote>

</ejb-ref>

<ejb-ref>

    <ejb-ref-name>ejb/CSuiteCollaboration</ejb-ref-name>

    <ejb-ref-type>Session</ejb-ref-type>

<home>com.collabraspace.csuite.server.i9n.interfaces.CSuiteCollaborationRemoteHome</home>

<remote>com.collabraspace.csuite.server.i9n.interfaces.CSuiteCollaborationRemote</remote>

</ejb-ref>

The following ejb-refs are added to <portalApplication>/<portalProject>/WEB-INF/weblogic.xml:

<ejb-reference-description>

<ejb-ref-name>ejb/CSuiteAdmin</ejb-ref-name>

<jndi-name>ejb/CSuiteAdmin</jndi-name>

</ejb-reference-description>

<ejb-reference-description>

<ejb-ref-name>ejb/CSuiteCollaboration</ejb-ref-name>

<jndi-name>ejb/CSuiteCollaboration</jndi-name>

</ejb-reference-description>

Sample CollabraSuite portlets are installed under <portalApplication>/<portalProject>/portlets/CollabraSuite.

Upgrading CollabraSuite

The process of upgrading an existing installation of CollabraSuite is similar to the process of creating a new installation.

Be sure to shut down WebLogic and backup your entire domain directory before applying the extension template to an existing domain. The Configuration Wizard will overwrite all scripts in the domain, removing any local modifications. One strategy for updating an existing domain with local customizations is to first make a copy of the domain. You can then apply the extension template to the copy. When finished with the template, copy the config.xml and the CollabraSuite.ear file back into the original domain. This will allow you to update a domain with CollabraSuite, BEA Edition while preserving any local modifications.
With WebLogic running, delete the CollabraSuite, BEA Edition application via the WebLogic Administration Console under Deployments/Applications.
Shutdown the WebLogic server.
Connect to the database configured for CollabraSuite, BEA Edition and run the necessary upgrade SQL scripts. These scripts can be found under the CollabraSuite, BEA Edition installation sql directory and they should be run in order. For example, to upgrade from CollabraSuite, BEA Edition 3.4.5 to CollabraSuite, BEA Edition 3.6.0, run alter320to350.sql and then run alter350to360.sql.
Extend the domain.

For WebLogic 8.1, perform the steps 1-6 and 8-11 from Extending the Domain, extending the copy of the domain. Be sure to skip step 7, which creates the CollabraSuite, BEA Edition database schema. In step 11, point to the applications directory in the original domain, rather than the copy of the domain.
For WebLogic 9, perform the steps 1-6 and 8-10 from Extending the Domain, extending the copy of the domain. Be sure to skip step 7, which creates the CollabraSuite, BEA Edition database schema.

Choose to replace the existing configurations and Apply that choice to all future choices.
Copy the config.xml file from the copied domain into the original domain
If upgrading a WebLogic 8.1 portal, copy the following jars into <portalApplication>/<portalProject>/WEB-INF/lib. They can be found on the distribution CD under the lib directory.

csuite-taglib.jar
common-server.jar
csuite-client.jar
csuite-ejb-client.jar
csuite-i9n-client.jar
csuite-ria-common.jar
csuite-ria-client.jar

If upgrading a WebLogic 9.2 portal, upgrade is supported only when using J2EE library modules. In this case, find any files that have been copied into the project from a CollabraSuite, BEA Edition library module. Remove and then re-copy them into the local project applying any local customizations.
Start the WebLogic server.
Perform all steps in Finish Extending the Domain.

Clustering Configuration

This section discusses deployment of CollabraSuite into a WebLogic cluster. This section can safely be skipped for single server installations.

Use the WebLogic Domain Configuration wizard to extend a cluster domain as described in the Extend the Domain section of this guide.

In WebLogic 8.1 SP4 or later, the CollabraSuite components will automatically be targeted to the cluster. In earlier versions you may have to target the CollabraSuite components to the cluster manually.

Confirm the following configuration for the CollabraSuite JMS Connection factory:

General -> 'Server Affinity Enabled' is checked
Transactions -> 'XA Connection Factory Enabled' is checked

When running in a cluster, the system clocks of all server nodes must be synchronized by using Network Timing Protocol (NTP) or some similar means of clock synchronization. When system clocks are not synchronized, incorrect event timestamps will occur and CollabraSuite users may be disconnected from the application.

Supported Configurations

Please see the Supported Configurations Guide for supported platforms and known limitations associated with particular configurations.

Special PointBase Instructions

WebLogic 8.1

When using PointBase with WebLogic 8.1, take the following special steps when extending a domain:

Before step 5, start PointBase:

For Windows:

> cd %DOMAIN_DIR%

> setDomainEnv.cmd

> %WL_HOME%\common\bin\startPointBase.cmd -port=9093 -ini=%DOMAIN_DIR%\pointbase.ini

For Unix:

% cd $DOMAIN_DIR

% . setDomainEnv.sh

% ${WL_HOME}/common/bin/startPointBase.sh -port=9093 -ini=${DOMAIN_DIR}/pointbase.ini

After step 7, stop PointBase:

For Windows:

> cd %DOMAIN_DIR%

> setDomainEnv.cmd

> %WL_HOME%\common\bin\stopPointBase.cmd -port=9093 -name=workshop

For Unix:

% cd $DOMAIN_DIR

% . setDomainEnv.sh

% ${WL_HOME}/common/bin/stopPointBase.sh -port=9093 -name=workshop

Special MySQL Instructions

WebLogic 8.1

When using MySQL with WebLogic, some documentation states that the MySQL JDBC driver JAR file should be placed in the JDK's jre/lib/ext directory. However, this causes errors when deploying J2EE applications in WebLogic. Instead, follow these steps to deploy with MySQL:

Create a WL_HOME/server/ext/jdbc/mysql directory in the WebLogic installation and place the MySQL JDBC driver JAR file in it. For this example, the MySQL JDBC driver JAR file is mysql-connector-java-3.1.12-bin.jar.
Add the MySQL JDBC driver to the CLASSPATH:

For Windows, edit the WL_HOME\common\bin\commEnv.cmd script and add the following lines to the bottom of the file:

SET DATABASE_CLASSPATH=
%WL_HOME%\server\ext\jdbc\mysql\mysql-connector-java-3.1.12-bin.jar

SET WEBLOGIC_CLASSPATH=%WEBLOGIC_CLASSPATH%;%DATABASE_CLASSPATH%

For UNIX, edit the WL_HOME/common/bin/commEnv.sh script and add the following lines to the bottom of the file:

DATABASE_CLASSPATH=
${WL_HOME}/server/ext/jdbc/mysql/mysql-connector-java-3.1.12-bin.jar

export DATABASE_CLASSPATH

WEBLOGIC_CLASSPATH=${WEBLOGIC_CLASSPATH}:${DATABASE_CLASSPATH}

WebLogic 9

Follow the instructions above for WebLogic 8.1.
For Windows, edit the following lines at the bottom of WL_HOME\common\bin\config.cmd and add the text in bold:

IF "%ARGUMENTS%" == "" (

	%JAVA_HOME%\bin\javaw %MEM_ARGS% -Xbootclasspath/a:%DATABASE_CLASSPATH% -jar configwiz.jar  %ARGUMENTS%

) ELSE (

	%JAVA_HOME%\bin\java %MEM_ARGS% -Xbootclasspath/a:%DATABASE_CLASSPATH% -jar configwiz.jar %ARGUMENTS%

For UNIX, edit the following line at the bottom of WL_HOME\common\bin\config.sh and add the text in bold:

"${JAVA_HOME}/bin/java" ${MEM_ARGS} -Xbootclasspath/a:${DATABASE_CLASSPATH} -jar configwiz.jar ${ARGUMENTS}

Installation Guide

Appendices

WebLogic Domain Extension Summary

WebLogic Portal Extension Summary

Upgrading CollabraSuite

Clustering Configuration

Supported Configurations

Special PointBase Instructions

WebLogic 8.1

Special MySQL Instructions

WebLogic 8.1

WebLogic 9