Installing the framework server in WebSphere 8.5
This document should be used, where the application server in use is WebSphere v8.0+ or WebSphere v8.5
System Requirements
| Database | Oracle 9i + (All distributed platforms). DB2 (All distributed platforms plus AS400). Hypersonic HSQLDB (Any Platform) |
| Application Server | WebSphere 8.5.5.9+ and Java 8 JDK |
| JDK | JDK 1.8+ installed on the RapidDeploy server and on any servers to which RapidDeploy will deploy |
| Browsers | IE 8+, Firefox 5+, Google ChromeMinimum screen resolution is 1024 x 768. For best results use the highest resolution. |
| 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 |
| 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. The Deployment Manager needs the maximum JVM heap size set to 1024 to be able to install the application via the console. |
Unpack the Binaries
Download and unzip the rapiddeploy binaries. The default location is /var/rd, which would make the environment variable MV_HOME=/var/rd/midvision
WebSphere Configuration
Create a shared Library
In order to run in WebSphere, RapidDeploy needs some additional jars adding to a shared library.
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: Where WAS_WAR_LIB = WAS_HOME/profiles/PROFILE_NAME/installedApps/CELL_NAME/MidVision_war.ear/MidVision.war/WEB-INF/lib/
${MV_HOME}/web-apps/tomcat/lib/el-impl-2.2.jar
${MV_HOME}/web-apps/tomcat/lib/el-api-2.2.jar
<WAS_WAR_LIB>/jsf-api-2.2.5.jar
<WAS_WAR_LIB>/jsf-impl-2.2.5.jar
<WAS_WAR_LIB>/jersey-core-1.17.1.jar
<WAS_WAR_LIB>/ant-1.9.6.jar
<WAS_WAR_LIB>/jaxb-api-2.1.jar
<WAS_WAR_LIB>/jaxb-impl-2.1.12.jarCreate a WebSphere Variable
Create a new WebSphere variable called MV_HOME which points to the midvision home directory (e.g. /var/rd/midvision).
Create Database Provider and Data Source
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 (e.g. jdbc/rapiddeploy). Ensure the following settings are set in the rapiddeploy.properties file.
rapiddeploy.datasource.context.filename=applicationContext-jndi-data-source.xml rapiddeploy.datasource.jndi.name=jdbc/rapiddeploy rapiddeploy.datasource.dialect=org.hibernate.dialect.Oracle10gDialect rapiddeploy.quartz.driverDelegateClass=org.quartz.impl.jdbcjobstore.StdJDBCDelegate
Configure WebSphere Server
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.
Application Server
Create a WebSphere application server and Cluster if required. Ensure the maximum JVM heap size is set to 1024M+. Also set the following 2 JVM system properties:
-DMV_HOME=${MV_HOME}
-Drapiddeploy.properties=${MV_HOME}/bin/rapiddeploy.propertiesRapidDeploy for Application Release Automation 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.
For the application class loader order, make sure it is set to: "Classes loaded with parent class loader first". Also ensure that the WAR class loader policy is set to "Class loader for each WAR file in application".
For the application web module "MidVision.war" class loader order, make sure it is set to: "Classes loaded with parent class loader first".
Once RapidDeploy is installed, remove the jboss-logging-spi-2.0.5.GA.jar file from the WAS lib directory. This jar file can cause errors in some cases when running RapidDeploy in Websphere application server.
Shared Library Association
Add the shared library to the Application and Web Modules.