This document should be used as an addition to the RapidDeploy 3.0 Quick Install Guide, where the application server in use is WebSphere v7.0.

1      System Requirements

1.1    System Requirements

The important note here is that WebSphere 7 needs to be at a minimum of 7.0.0.7 with the JPA2.0 and Osgi Feature Packs.

Database	Oracle 9i + (Any Platform). DB2 (Any Platform includes DB2 on AS400). Hypersonic HSQLDB (Any Platform)
Application Server	WebSphere 7.0.0.7+ + JPA2.0 Feature Pack + Osgi Feature Pack.
JDK	JDK 1.6+ installed on the RapidDeployTM server and on any servers to which RapidDeployTM will deploy
SSH	If SSH connection is required, a suitable technology (e.g. SSH Tectia or OpenSSH) must be installed on each target server to which RapidDeployTM will deploy
Browsers	IE 8+, Firefox 5+, Google ChromeMinimum screen resolution is 1024 x 768
Other	There should be 1.5 Gb memory and 500Mb disk space available for use by each RapidDeploy JVM. This does not include any memory requirements for WebSphere services such as NodeAgents or Deployment Managers

2     Additional Feature Packs

2.2   Feature Packs

Install JPA2.0 Feature Pack and Osgi Feature Pack. Please refer to IBM WebSphere 7 documentation.

2.3   Augment profiles

The following commands can be used to augment AppServer and Dmgr profiles. Please refer to IBM WebSphere 7 documentation.

<WAS_HOME>/manageprofiles.sh -augment -profileName <DmgrProfile>
     -templatePath <WAS_HOME>/profileTemplates/JPA/cell.jpafep/dmgr

<WAS_HOME>/manageprofiles.sh -augment -profileName <AppSrvProfile>
     -templatePath <WAS_HOME>/profileTemplates/JPA/cell.jpafep/default

2.4   Test installation

Test JPA 2.0 is installed:

<WAS_HOME>/profiles/<AppSrvProfile>/bin/wsjpaversion.sh

Expected output should look similar to:

WSJPA 2.0.1-SNAPSHOT
version id: WSJPA-2.0.1-SNAPSHOT-r1118:2100
WebSphere JPA svn revision: 1118:2100
OpenJPA 2.0.1-SNAPSHOT
version id: openjpa-2.0.1-SNAPSHOT-r422266:980199
Apache svn revision: 422266:980199

3     Create a shared Library

In order to run in WebSphere, RapidDeploy needs some additional jars adding to a shared library. The following jars should be added.

Create Shared Library Named “JSF 2.0″ (isolated) add to the web module classpath (change the path as required):

Add the following jars in this directory to the library:

<WAS_HOME>\profiles\<AppSrvProfile>\installedApps\CellName\
midvision.ear\midvision.war\WEB-INF\lib\

jsf-api-2.1.7.jar
jsf-impl-2.1.7.jar
validation-api-1.0.0.GA.jar
hibernate-validator-4.0.2.GA.jar
slf4j-api-1.6.1.jar
slf4j-log4j12-1.6.1.jar
log4j-1.2.14.jar
el-api-2.2.jar
el-impl-2.2.jar

4     Configuring WebSphere

RapidDeploy can be installed in the standard way into WebSphere. The below notes provide an indication of specific settings required that are different to the default.

4.1   Application Server

Create a WebSphere application server and Cluster if required. Ensure the maximum JVM heap size is set to 1536M+

4.2   Database Provider

If required, create a database provider and datasource for your application to use. Please ensure that the driver that you use for this data source is XA Enabled. Make a note of the JNDI name. This will need configuring in the rapiddeploy_default.properties file. You will additionaly need to switch from using an internal Data Source connection pool to a JNDI referenced one in this file <WEBAPP_ROOT>/WEB-INF/applicationContext.xml using the proccess detailed here.

4.3   Application Install

Use the wizard to install the RapidDeploy WAR file into WebSphere. Assign the Application Server or cluster you defined above. Set the context root to /MidVision

Ensure that the WAR Classloading policy is set to PARENT_LAST.

4.4   Shared Library Association

Add the shared library to the Web Module:

Module	URI	Shared Libraries
MidVision – RapidDeploy	rapiddeploy-web-app.war,WEB-INF/web.xml	JSF 2.0