Knowledge Base
CMS Fiona
Portal Manager
Installing and Configuring the Portal Manager
Using the Portal Manager with another Application Server
Using the Portal Manager with Tomcat 5.x

Using the Portal Manager with Tomcat 5.x

Please proceed as described in the following instructions if you wish to operate the Portal Manager in conjunction with the Tomcat Application Server, version 5.5. For Tomcat 5.0, the procedure is similar. However, you require the installation package for Tomcat 5.0. It is not necessary to install the compatibility package for using the JDK 1.4.

Download Tomcat
1. Download the apache-tomcat-5.5.17.tar.gz package from the Apache Tomcat website.
2. If Tomcat is to be operated with the JDK 1.4, please also download the apache-tomcat-5.5.17-compat.tar.gz package.
Install Tomcat
1. Unpack the package you downloaded in step 1.1. In the following, the directory created is referred to as tomcatInstallDir.
2. If Tomcat is operated using the JDK 1.4, please also unpack the package you downloaded in step 1.2 and use the same target directory as for the Tomcat package because additional jar files are placed into the tomcatInstallDir/common/lib directory.
Adapt the PATH environment variable so that the JDK to be used can be found.

If on the same machine a Trifork server is installed which uses the standard ports, adapt three ports in the tomcatInstallDir/conf/server.xml file:

<Connector port="8080" maxHttpHeaderSize="8192"
  maxThreads="150" minSpareThreads="25"
  maxSpareThreads="75"
  enableLookups="false" redirectPort="8443"
  acceptCount="100"
  connectionTimeout="20000" disableUploadTimeout="true" />

<Connector port="8009"
  enableLookups="false" redirectPort="8443"
  protocol="AJP/1.3" />

<Connector port="8082"
  maxThreads="150" minSpareThreads="25"
  maxSpareThreads="75"
  enableLookups="false" acceptCount="100"
  connectionTimeout="20000"
  proxyPort="80" disableUploadTimeout="true" />

Copy the JavaBeans™ Activation Framework from fionaInstallDir/share/lib/activation.jar to tomcatInstallDir/common/lib.
Copy JavaMail from fionaInstallDir/share/lib/mail.jar to tomcatInstallDir/common/lib.
Recursively copy the PM and PM-PL web applications from the fionaInstallDir/instance/myInstance/webapps directory to tomcatInstallDir/webapps/.
In the files tomcatInstallDir/webapps/PM/WEB-INF/web.xml and tomcatInstallDir/webapps/PM-PL/WEB-INF/web.xml, adapt the path to the license.xml file contained in the config directory of your CMS instance. If the CMS is running on a different machine, also copy the licence file to a location where Tomcat can find it.
In the tomcatInstallDir/webapps/PM/WEB-INF/logging.xml and tomcatInstallDir/webapps/PM-PL/WEB-INF/logging.xml files, enter the path to the directory where the log files of the web applications are located. Example:
```
<param name="File" value="tomcatInstallDir/logs/PM.log"/>
```
Delete the file trifork-app-conf.xml from the META-INF directories of both web applications, PM and PM-PL. Into each directory place a version of the file context.xml, adapted to the respective web application. For PM:
```
<Context docBase="${catalina.home}/webapps/PM" path="/PM" crossContext="true" />
```
For PM-PL:
```
<Context docBase="${catalina.home}/webapps/PM-PL" path="/PM-PL" crossContext="true" />
```
Prepare PM and PM-PL for live operation:
1. If you use version 6.0.x of the Portal Manager, please deactivate the com.infopark.pm.PreviewDocumentSource bean in the documentManager bean contained in the tomcatInstallDir/webapps/PM/WEB-INF/pm.xml file (by commenting it out)
2. Activate the com.infopark.pm.FileDocumentSource bean (by removing the comment characters). In the documentRoot property, specify the path to the export directory.
3. In the userManager bean contained in the tomcatInstallDir/webapps/PM/WEB-INF/pm.xml file, activate the user manager bean you wish to use and configure it. Deactivate the other user managers.
4. In the searchEngine bean contained in the tomcatInstallDir/webapps/PM-PL/WEB-INF/pm.xml file, deactivate the bean in the com.infopark.libs.search.cm.AdvancedCmSearchEngine class and activate this bean in the com.infopark.libs.search.ses.SesSearchEngine class. Adapt the host and port properties so that they match the Search Server ports of the CMS instance (see the server.xml file in the config directory of the instance.
5. Change the portletPathMapping specified in the tomcatInstallDir/webapps/PM-PL/WEB-INF/pm.xml file to /PM-PL = /PM-PL.
Start the Tomcat server by running tomcatInstallDir/bin/startup.sh. You can now open the following URL to access your exported pages containing portlets:
```
http://myTomcatHost:myTomcatPort/PM/
```
Should problems arise, please look into the log files contained in the tomcatInstallDir/logs directory. With general errors, the catalina.out and catalina.yyyy-mm-dd.log files are instructive. With application-specific errors, please examine the files configured in step 9 above.