Upgrading Situate

Upgrading Situate-1.2.x to 1.3.2-3

The process to upgrade a Situate installation from 1.2.x to any 1.3.2-3 requires that both the server and agent be upgraded.

Preparation

• Make sure that the current Situate server is at least running version 1.2.0
• Situate agents can be upgraded from any version
• Do a complete backup of the Situate server directory prior to any future steps
• Make sure to have access to the current license.dat file

Step 1. Shutdown Situate Server

The Situate server should be shutdown prior to any of the agents. This insures that no workflows can be executed after an agent becomes unavailable. Login to the Situate server host and execute the following commands.

Unix/Linux Platform

    /etc/init.d/situatectl stop

Windows Platform

On a Windows platform the Situate server can be stopped by simply logging into the Windows host and opening the services application then find the service named SitateAgent and click stop

Step 2. Backup Situate Server Data

The Situate server will maintain all the data with the exception of the taskslogs. Tasklogs are the output that is generated by a specific task in a workflow. A task can execute on any asset and it's output will be saved on that asset in the director ${INSTALLPATH}/logs/tasklogs.

In this step, we will only be concerned with the data associated with the Situate server.

The following directories should be copied forward from your previous release into your new release on the Situate server with one caveat. The directory /opt/situate/data/releases/templates must not be over-written. It contains new templates that were not included in previous versions of Situate.

• /opt/situate/security - This directory maintains your services accounts.
• /opt/situate/data - This maintains all of your workflows, calendars, server configuration, deployment configuration and deployment history.
  • Warning: DO NOT COPY forward the /opt/situate/data/releases/templates directory.
• /opt/situate/logs - This contains your server runtime logs and workflows logs. These are really only used today for troubleshooting but good to have around if you don't care about disk space.
• /opt/situate/java.options - This file contains any Java VM related options, e.g., Xmx1024m
• /opt/situate/license.dat - This is your license file and is required for the Situate server to start.

Moving Situate Server Install Directory

The simplest way to prepare for a Situate server upgrade is to move or rename the Situate install directory. This will insure that are data still exists but allow for a new installation to take place.

Move or rename the installation directory on the server. By default the installation directory will be located in /opt/situate for linux and C:\Program Files (x86)\Situate on Windows

Unix/Linux Platform

    mv /opt/situate /opt/situate.fbk

Windows Platform

Open a file explore and find C:\Program Files (x86)\Situate. Click it to edit the name and change it to Situate.fbk

Step 3. Install Situate Server

The Situate server new installation process has not changed from the previous release. As "root" (or another privileged user) execute the installation packages Situate server will run. Refer to the "Situate-Quick-Install.doc" for details.

*Note: This should include applying your current license key to this install.

Once the Server has been installed and has successfully been started, shut it down as indicated in Step 1. above

Step 4. Reload Data

To insure that we maintain all accounts, assets, security settings and other historical data it is necessary to copy directories indicated in Step 2. from the previous Situate directory that was renamed/moved to situate.fbk.

Copy Data

The following directories and files should be copied from the situate.fbk instance to the new Situate installation directory.

Unix/Linux Platform

    cp /opt/situate.fbk/security /opt/situate/     cp /opt/situate.fbk/logs /opt/situate/     cp /opt/situate.fbk/java.options /opt/situate/

• Warning: DO NOT COPY forward the /opt/situate/data/releases/templates directory.     mv /opt/situate/data /opt/situate/data.orig     cp /opt/situate.fbk/data /opt/situate/     cp /opt/situate/data.orig/releases/templates /opt/situate/situate/data/releases/

Windows Platform

    copy /opt/situate.fbk/security /opt/situate/     copy /opt/situate.fbk/logs /opt/situate/     copy /opt/situate.fbk/java.options /opt/situate/

• Warning: DO NOT COPY forward the /opt/situate/data/releases/templates directory.     copy /opt/situate/data /opt/situate/data.orig     copy /opt/situate.fbk/data /opt/situate/     copy /opt/situate/data.orig/releases/templates /opt/situate/situate/data/releases/

To insure that no data loss can occur make sure to keep the previous Situate directory that was renamed to /opt/situate.fbk. It may even be prudent to tar this directory and keep it.

Step 5. Upgrade Agents

Situate agents, as mentioned earlier, only persist tasks logs for those tasks which have run on these specific assets. You can chose to backup that data or just ignore it. *WARNING: If the data is not backed up and restored to the agent then it will not be possible to get the historical task information.

Task logs for agents will reside in /opt/situate/logs. Backup this directory prior to installing a the latest agent version.

The Situate agent new installation process has not changed from the previous release. As "root" (or another privileged user) execute the installation package required for the core Situate agent. Refer to the "Situate-Quick-Install.doc" for details.

Step 6. Startup Server

After all Situate agents have been upgraded as described in the previous step then simply startup the Situate server

Unix/Linux Platform

    /etc/init.d/situatectl start

Windows Platform

On the Windows platform simply open up the services application, find the SituateAgent server and click start.

Other Information

The following are notable points relating to upgrading from 1.2.

• Warning: If you are upgrading, make sure the domain you enter during installation is the same as it was in the prior version.
• Application Configuration Properties must not use a "." in their names like java property files can use. We recommend using "-" or camel case the name. And note that all application configure properties are referenced using $currrentEnv.[prop-name].