System Requirements

Basic Installation

The software distribution is shipped with an embedded hypersonic database (HSQL-DB) and is preconfigured to use this database. The framework server application is a web application and runs within a Tomcat application server also shipped in the software distribution. Therefore the basic installation is to simply unzip the MidVision binary to a directory of your choosing. This will create a midvision directory structure.

e.g.

c:\midvision
/usr/midvision
/Users/user/Downloads/midvision/

This location is referred to as MV_HOME

Starting the framework server

The framework server runs within a Tomcat Application Server instance and start and stop scripts for the web application are contained within the bin directory. Running these scripts will, by default, extract a Java Runtime Environment specific to your platform and start the Tomcat Server which in turn will deploy the framework web application.

Navigate to the MV_HOME/bin directory. Execute the desired script. The name varies depending on your platform

start-web-app.bat (double click the icon on Windows)
./start-web-app.sh (execute as written on Unix)

Verifying Startup

By default the framework server web application is configured to listen on port 9090. The quickest verification is to navigate to your host address in a web browser:

e.g

http://<your-host-name-or-ip-address>:9090/MidVision

You should then see the MidVision login prompt

The default username/password is: mvadmin/mvadmin. It is recommended this is changed at the earliest opportunity.

Agent

By default an internal RapidDeploy agent is started on localhost, port 20000. This is also configured by default as the first target server in the RapidDeploy server list. You can disable this agent by amending the following property to 'false' in the MV_HOME/bin/rapiddeploy.properties file.

rapiddeploy.built.in.remote.agent.enabled=true

IPv6 Support

If you want to deploy to IPv6 servers, you will need to amend the RapidDeploy MV_HOME/bin/start-web-app.sh or bat file. Amend the following line to remove the -Djava.net.preferIPv4Stack=true

Change:

export JAVA_OPTS="-Dcom.sun.xml.bind.v2.bytecode.ClassTailor.noOptimize=true -Xms1024m -Xmx1024m -XX:NewSize=512m -XX:MaxNewSize=512m -XX:MetaspaceSize=100m -XX:+CMSClassUnloadingEnabled -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=70 -XX:+ScavengeBeforeFullGC -XX:+CMSScavengeBeforeRemark -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=$MV_HOME/logs/midvisionhd1.hprof -DMV_HOME=$MV_HOME -Drapiddeploy.properties=$MV_HOME/bin/rapiddeploy.properties -Djava.net.preferIPv4Stack=true"

To:

export JAVA_OPTS="-Dcom.sun.xml.bind.v2.bytecode.ClassTailor.noOptimize=true -Xms1024m -Xmx1024m -XX:NewSize=512m -XX:MaxNewSize=512m -XX:MetaspaceSize=100m -XX:+CMSClassUnloadingEnabled -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=70 -XX:+ScavengeBeforeFullGC -XX:+CMSScavengeBeforeRemark -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=$MV_HOME/logs/midvisionhd1.hprof -DMV_HOME=$MV_HOME -Drapiddeploy.properties=$MV_HOME/bin/rapiddeploy.properties"

Licensing

If you are using 10 nodes or less, you can use the shipped community license which is installed by default.

If you wish to use more than 10 nodes you'll need a license key. If you have not received a license key please indicate this in an email to sales@midvision.com. Simply paste in the sections of the key into the appropriate input fields on the form, no formatting is required.

Troubleshooting

The basic installation typically works straight out of the box. Logfiles should be investigated and some platform features should be noted

Logfiles are located in MV_HOME/logs There are 2 that you may need to investigate in the event of problems

rapiddeploy-web-app.log

AIX typically does not apply appropriate permissions to execute scripts and binaries for newly created files. In that instance when the software distribution package is unzipped the start-web-app.sh scripts are not executable. Furthermore when the start script is run, if you are relying on the shipped Java Runtime Environment you may need to ensure that the Java executable is executable (this is extracted from a zip file the first time the start-web-app.sh is run. Therefore you may need to run a 'chmod' command a number of times.

e.g.

chmod -R 755 MV_HOME

Ports may already be in use. See advanced configurations for details about changing ports: HSQL DB uses port 9001, the framework server GUI application uses port 9090, 8005 and 9443.