2 Planning your installation

This chapter includes the following topics:

• How to use this document

• Prerequisites for upgrading from 7.3.3.x to 8.0.1

• Migrating the database when upgrading from 7.3.3.x to 8.0.1

• Preparing the environment for the Empirica Signal installation

• Information to collect before you begin

How to use this document

This document contains the procedures that guide you through both the installation and upgrade processes.

Sections that are installation-specific or upgrade-specific are labeled as such. Procedures without installation-specific or upgrade-specific labels are applicable to all upgrades and installations.

Prerequisites for upgrading from 7.3.3.x to 8.0.1

You can upgrade from releases 7.3.3.3, 7.3.3.4, or 7.3.3.5 to release 8.0.1 of the Empirica Signal software.

If you are running a release that is earlier than 7.3.3.3, you must upgrade to release 7.3.3.3 before upgrading to release 8.0.1. For information on upgrading to release 7.3.3.3, see the Empirica Signal Windows 2003/2008 Server Installation and Upgrade Instructions for release 7.3.3.3.360.

If you are upgrading from release 8.0 to 8.0.1, skip to Chapter 8, "Upgrading the Signal application software from 8.0 to 8.0.1".

Migrating the database when upgrading from 7.3.3.x to 8.0.1

If you are migrating your database from Microsoft Windows to Linux, back up your database first. Work with a database administrator to migrate the contents of your database to a Linux system.

Preparing the environment for the Empirica Signal installation

Before installing, make sure that the application and database servers meet the software requirements described in the Empirica Signal Release Notes.

describes how to install some of the required software:

1. Installing WebLogic

2. Installing Oracle ADF Runtime

3. Installing RCU and creating repositories

4. Setting up the WebLogic domain:

   1. Creating and configuring the WebLogic domain.

   2. Creating the nodemanager.properties file

   3. Starting WebLogic and the Node Manager

   4. Creating a data source for credential access.

   5. Associating the credential store with the data source.

   6. Restarting the SignalServer managed server

Information to collect before you begin

Before you begin, collect the following information about the setup of the database and application servers. You will need this information for the installation.

Database server

• TNSNAMES entry for the database.

• Service name and SID for the database.

• system and sys password for the database.

• Time zone setting of your database so you can set the WebLogic server to the same time zone.

  Oracle recommends using the UTC time zone for both servers.

• The location of the data files for the instance, if you plan to create the tablespaces in the same location. For example:

  /u01/app/oradata/<sid>

Application server

• JDK installation location, such as:

  /usr/java/jdk1.7.x_xx

• The following information about the Oracle client:

  • Oracle base location, such as:

    /u01/app/oracle

  • Oracle home location, such as:

    /u01/app/oracle/product/11.2.0

• The following information about WebLogic:

  • Installation location, such as:

    /u01/app/oracle/Middleware

  • URL for the WebLogic Administration Console, such as:

    https://<servername>:7002/console

  • URL for Oracle Enterprise Manager, such as:

    https://<servername>:7002/em

  • User name and password of a WebLogic administrator.

• For single sign-on (SSO) installations, the following information:

  • Native login port number to use for initially changing the Empirica Signal admin password.

  • Port number to use for normal SSO Empirica Signal connections on the server.

  • SSO logout URL.

  • SSO header, which contains the user name.

  
  

  Note: If you plan to document your installation or upgrade with the provided IQ_Test.doc or UQ_TEST.doc, familiarize yourself with the contents of the corresponding document and fill it in as you proceed through the instructions in this document.