1 System Requirements
1.1 System Requirements
| Database | Oracle 9i + (Any Platform).DB2 (Any Platform includes DB2 on AS400).Hypersonic HSQLDB (Any Platform) |
| Application Server | WebSphere 7.0.0.7 +Glassfish 3.1+Tomcat 7.0+ |
| 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 RapidDeploy |
2 Basic Install
2.1 Installation Process Overview
By default, the RapidDeployTM V3.0 runs on a Tomcat server using a Hypersonic HSQLDB database, both of which are provided within the RapidDeployTM module. This is the recommended combination as it provides the simplest installation, configuration and maintenance.
For details on installing onto other supported databases and application servers, please refer to the later sections in this guide.
2.2 Unpack the RapidDeployTM WAR.
Download the RapidDeployTM war file and extract to a dedicated directory of your choice. Any zip utility, such as WinZip or 7-Zip, can be used. This will create a directory structure, the top level of which is called midvision-web-apps. This is the ‘home’ directory for the application, which we shall refer to as %MV_HOME%.
2.3 Start Tomcat
Navigate to %MV_HOME%/bin and run the command ‘start-web-app’.
2.4 Test the Web Application
Open a web browser.
Navigate to URL http://localhost:9090/MidVision and the RapidDeployTM login page will be displayed.
2.5 Stop Tomcat
Navigate to %MV_HOME%/bin and run the command ‘stop-web-app’.
3 Database configuration
The MidVision web application comes initially configured to run in Tomcat connecting to a direct Hypersonic Data Source. This section show you how to point the application to a database.
3.1 Oracle
The first requirement is to run in the database scripts to create the user, schema, etc.Navigate to %MV_HOME%/web-apps/db/bin and run the command ‘install-oracle-db.sh’
You should answer the questions or accept the defaults as applicable. See example below.
[root@deployServerHost bin]# ./install-oracle-db.sh
Enter the oracle SID (default = XE):
Enter the oracle port (default = 1521):
Enter the oracle host name (default = localhost):
Enter the path to the directory to create the rapiddeploy tablespace files (default = /tmp) :
/opt/IBM/RAFServer/midvision/table_space
Enter the rapiddeploy tablespace name (default = rapiddeploy_tablespace) :
Enter the oracle sysdba username (default = sys):
Enter the oracle sysdba password (default = password):
Enter the rapiddeploy application database username (default = rd_db_user):
Enter the rapiddeploy application database password (default = rd_db_password):
—————————————————————–
MidVision is about to create the rapiddeploy tablespace, user and role.
Once the tablespace has been created the schema and data will be installed
into the database.
The schema load will be logged to the file called install-schema.log in this
directory.
Please ensure sqlplus is on the path of this command prompt
—————————————————————–
SID: [XE]
Oracle Port: [1521]
Oracle Hostname: [localhost]
Sysdba username: [sys]
Sysdba password: [manager]
Path to tablespace data files: [/opt/IBM/RAFServer/midvision/table_space]
Rapiddeploy tablespace name: [rapiddeploy_tablespace]
Rapiddeploy username: [rd_db_user]
Rapiddeploy password: [rd_db_password]
—————————————————————–
NOTE: This will delete any datafiles and users before recreating them
are you sure you want to continue.
—————————————————————–
Confirm input data is correct: Y/N
This will run in the database scripts and configure the database.
3.2 DB2
[root@dem-rh601 bin]# ./install-db2-db.sh
Enter the DB2 DB (default = RD_DB):
Enter the path to the directory to create the rapiddeploy tablespace files (default = /tmp) :
Enter the rapiddeploy application database username (default = rd_db_user):
—————————————————————–
MidVision is about to create the rapiddeploy tablespace and grant permission
to a pre-defined database user
Once the tablespace has been created the schema and data will be installed
into the database.
This script should only be run once.
—————————————————————–
DB2 DB: [RD_DB]
Base Path to tablespace data files:[/tmp]
Rapiddeploy username: [rd_db_user]
—————————————————————–
WARNING: This will delete any datafiles and users before recreating them
are you sure you want to continue?
—————————————————————–
Confirm input data is correct (y / n)?
y
This will run in the database scripts and configure the database.
3.3 Configuring the datasource
We now need to configure the application to point to the database. There are two ways you can connect to the application database: direct (which is the default) or via JNDI from the application container data source connection.
Properties are used to defined which data source definition is used in the application. There are two files which configure the data source connections, one is a standard data source definition and the other is a JNDI definition. To determine which file to load you need to add one of these properties to your ${MV_HOME}/bin/rapiddeploy.properties file:
For direct connections use this property value:
rapiddeploy.datasource.context.filename=applicationContext-non-jndi-data-source.xml
or for JNDI connections use this property value:
rapiddeploy.datasource.context.filename=applicationContext-jndi-data-source.xml
If you use a direct data source connection and want to change the default HSQL database to use an Oracle database then change the following properties in your ${MV_HOME}/bin/rapiddeploy.properties file:
rapiddeploy.datasource.username=<DB_USERNAME> rapiddeploy.datasource.password=<DB_PASSWORD> rapiddeploy.datasource.url=jdbc:oracle:thin:@localhost:1521:xe rapiddeploy.datasource.dialect=org.hibernate.dialect.Oracle10gDialect rapiddeploy.datasource.classname=oracle.jdbc.xa.client.OracleXADataSource rapiddeploy.datasource.url.key=URL rapiddeploy.quartz.driverDelegateClass=org.quartz.impl.jdbcjobstore.StdJDBCDelegate
If you use a JNDI data source connection then set the JNDI name in your ${MV_HOME}/bin/rapiddeploy.properties file:
rapiddeploy.datasource.jndi.name=<APP_CONTAINER_JNDI_NAME>
The JNDI resource must use an XA compliant driver.
4 Configuring RapidDeploy to use an external LDAP User repository
1) Set up the implementation class in ${MV_HOME}/bin/rapiddeploy.properties file. Change the authentication.provider.class property from:
#----------------------------------------------- # Authentication Provider Configuration # # Use class RdAuthenticationProviderImpl for DB authentication # authentication.provider.class=com.midvision.rapiddeploy.web.security.RdAuthenticationProviderImpl # # Use class LdapAuthenticationProviderImpl for ldap authentication # authentication.provider.class=com.midvision.rapiddeploy.web.security.LdapAuthenticationProviderImpl #------------------------------------------------- authentication.provider.class=com.midvision.rapiddeploy.repository.security.authentication.RdAuthenticationProviderImpl
to:
#----------------------------------------------- # Authentication Provider Configuration # # Use class RdAuthenticationProviderImpl for DB authentication # authentication.provider.class=com.midvision.rapiddeploy.web.security.RdAuthenticationProviderImpl # # Use class LdapAuthenticationProviderImpl for ldap authentication # authentication.provider.class=com.midvision.rapiddeploy.web.security.LdapAuthenticationProviderImpl #------------------------------------------------- authentication.provider.class=com.midvision.rapiddeploy.web.security.LdapAuthenticationProviderImpl
2) Amend the following section in ${MV_HOME}/bin/rapiddeploy.properties
#----------------------------------------------- # LDAP Configuration # # ldap.initial.context.factory=com.sun.jndi.ldap.LdapCtxFactory # ldap.provider.url=ldap://localhost:10389/ # ldap.security.authentication=simple # ldap.security.principle.pattern=uid=%s,ou=Users,dc=midvision,dc=com #-------------------------------------------------- ldap.initial.context.factory=com.sun.jndi.ldap.LdapCtxFactory ldap.provider.url=ldap://localhost:10389/ ldap.security.authentication=simple ldap.security.principle.pattern=uid=%s,ou=Users,dc=midvision,dc=com ldap.password=password
Where
ldap.provider.url is the url of the LDAP repository
ldap.password is the password granted for read access to the LDAP repository
ldap.security.principle.pattern is the path in the LDAP tree to identify users
5 First Login credentials
In order to log in to RapidDeploy for the first time, please use the following credentials:
Username: mvadmin
Password: mvadmin
Please change the mvadmin password and make a safe note of it.
6 Note about rapiddeploy.properties files
RapidDeploy comes preconfigured with a default file in ${MV_HOME}/tomcat/webapps/MidVision/WEB-INF/classes/rapiddeploy_default.properties
Properties from the default file are over written by properties found in the users property file which by default can be found here: ${MV_HOME}/bin/rapiddeploy.properties. The location of this file is a java system property set in the start script. Users can change the location of this property file.
-Drapiddeploy.properties=<CUSTOMER_DIRECTORY>\rapiddeploy.properties
rapiddeploy_default.properties contains a number of placeholders, of the form &&PLACEHOLDER_NAME&&, which customers can use where they deploy new versions of RapidDeploy using RapidDeploy or another form of automation, in order to perform search/replace of environment specific values.
Customers should edit the rapiddeploy.properties file and not the rapiddeploy_default.properties file.
7 Advanced Configuration
Instructions on how to run a dual instance of the RapidDeploy application on the same server are described in this page: Dual Running RapidDeploy.
