7. Confluence Docs 3.0 : Installing Confluence EAR-WAR on Websphere This page last changed on Jul 22, 2009 by rhartono. This documentation provides a guide to install Confluence on Websphere 6.1 with basic settings and an external database. On this page: Step 1. Configuring the Confluence War File Step 2. Install Confluence in Websphere Step 3. Starting Confluence Step 4. Modifying Files in an Exploded War After installing Websphere, follow the instructions below. ### Step 1. Configuring the Confluence War File Download the Confluence EAR/WAR zip file. (You need to click the 'Show all' link to see the EAR/WAR zip file.) Check your unzip program before extracting the downloaded zip file. Some archive-extract programs cause errors when unzipping the Confluence zip file: Windows users must avoid the Windows built-in unzip utility, as it doesn't extract all the files. Use a third-party unzip program like 7Zip or Winzip. Solaris users will need to use GNU tar to handle the long file names. Extract the downloaded zip file. You have now unzipped your Confluence installation directory, which should contain the version number e.g. `confluence-2.10.0` or `confluence-2.10.2`. This directory will be later referred to as the Confluence installation directory. Inside is a `confluence` subdirectory, referred to later as the (Exploded) Confluence WAR directory. Record the absolute path to the Confluence WAR directory. Modify its confluence-init.properties and set Confluence Home. Inside the Confluence installation directory, edit `...confluence/WEB-INF/classes/confluence-init.properties` in a text editor. Now define your Confluence Home directory, by setting the `confluence.home` property to a directory of your choosing. We suggest using different paths for your installation and home directories. This will facilitate upgrades. This is the directory that will contain all of Confluence's configuration, backup and attachment files. Tip: Another term for 'Home directory' would be 'data directory'. For Confluence versions 2.10.1, 2.10.2 and 2.10.3, delete the package-scanner-0.7.2.jar from the WEB-INF/lib directory, and place package-scanner-0.7.jar in its place. See Known Issues for Websphere. Add your database driver jar file to the WEB-INF/lib directory. If your driver already exists in the main classpath and is used for other applications, you can skip this step. Check the Database Installation Instructions. If you're not already committed, we recommend Postgres.
   | The built-in evaluation database may not work on a Websphere deployment.
Build the war file. Windows Open the command line prompt Navigate to the Confluence installation directory Run the command `build war` Linux Open a terminal window Navigate to the Confluence installation directory Add executable mode to `build.sh` — `chmod +x build.sh` Run `build.sh` The WAR file is now located in the `dist` subfolder in your Confluence installation directory ### Step 2. Install Confluence in Websphere Start Websphere Admin Server. Access Websphere Admin console: https://localhost:9043/ibm/console On the left hand panel, click Servers > Application Servers. Select your server. Choose Allow for Access to internal server classes. Choose Multiple for Classloader Policy. On the left hand panel, click Applications > Enterprise Applications. Import your war. Note your context path and choose all the defaults. Once the war file is imported, select it, then choose Class loading and update detection. Select Classes loaded with application class loader first and Single class loader for application. Restart Websphere to make sure that all settings are picked up. ### Step 3. Starting Confluence Start your Websphere Server. Go to Applications > Enterprise Applications and locate your installed Confluence. Tick the box next to the Confluence war file and click Start. Access Confluence at http://localhost:9080/contextPath (chosen above) To access Confluence go to http://localhost:9080/contextPath ### Step 4. Modifying Files in an Exploded War It's a bit inconvenient to modify files - add patches or configure velocity or xml files - if you have to rebuild and redeploy the war file. Websphere requires deploying Confluence as a built .war archive originally. After that, however, you can drop files in the exploded war directory and restart the server to pick up changes (just the application isn't enough, given classloading issues). For the case of Velocity (vm or vmd) files or jsp files, you don't even need to reload the application - just refresh your page! A typical exploded war directory might be found in a path similar to:
    /usr/lib/IBM/WebSphere/AppServer/profiles/AppSrv03/installedApps/serverName-laptopNode01Cell/confluence-2_10_2_war.ear/confluence-2.10.2.war/
Keep in mind that this isn't a technique for deploying war files, but rather for modifications after deploy. ##### RELATED TOPICS Known Issues for Websphere Websphere JVM Tuning

Document generated by Confluence on Nov 05, 2009 23:27