8 Upgrading the Signal application software from 8.0 to 8.0.1

This chapter is only for users who have installed Empirica Signal release 8.0 and are now upgrading to release 8.0.1. It includes the following topics:

Components of the installation package
Unpacking the installation files into the installation directory
Stop Signal
Applying upgrade scripts to schema
Setting up the property files
Preserving custom home pages, release notes, and images from the 8.0 installation
Deploying the Signal application
Verifying the Empirica Signal setup

Components of the installation package

The installation package contains the following components that you need toupgrade Empirica Signal version 8.0 to version 8.0.1..

File	Description
`Signal-8_0_1_0_XXX.zip`	Build that you install, where XXX is the build number.
`Database.zip`	Scripts for setting up and upgrading the Empirica Signal database account.
`UQ_Test.doc`	Document for upgrade qualification information.
`OQ_Test.doc`	Document for operational qualification information.

Unpacking the installation files into the installation directory

Note:

In this document, <INSTALL_DIR> refers to the folder where the Signal 8.0 software is already installed; for example, /u01/stage/Signal_Install.

Start a login shell to the application server as the non-privileged user.
Rename the existing <INSTALL_DIR>/Signal directory to <INSTALL_DIR>/Signal_8.0. For example:

$ mv /u01/stage/Signal_Install/Signal u01/stage/Signal_Install/Signal_8.0
Create directory Signal in <INSTALL_DIR>. For example:

$ mkdir /u01/stage/Signal_Install/Signal
Using a tool, such as Unzip, unpack the Signal-8_0_1_0_XXX.zip file into the <INSTALL_DIR>/Signal directory.
Execute the following command to make the MGPS program executable:

$ chmod u+x <INSTALL_DIR>/Signal/WEB-INF/classes/MGPS
Rename the existing /u01/stage/Database directory to /u01/stage/Database_8.0. For example

$ mv /u01/stage/Database /u01/stage/Database_8.0
Create the directory Database. For example:

$ mkdir /u01/stage/Database
Using a tool, such as Unzip, unpack the contents of the Database.zip file into the directory.
If you plan to document your upgrade with the provided UQ_Test.doc, familiarize yourself with its contents now and fill it in as you proceed through the following sections.

Stop Signal

Perform these steps by connecting to the application server using a web browser:

Log in to the WebLogic Administration Console using the WebLogic administrator credentials provided to you by the system administrator. Typically, the address for the WebLogic Administration Console is in the form:

https://<servername>:<port>/console
On the left pane named Domain Structure, click Deployments.
In the Change Center section on the left, click Lock & Edit.
Select Signal in the Deployments table.
In the Deployment table on the right, click the Stop button and click force stop now.

Applying upgrade scripts to schema

In a command shell, use the following command on the app server to navigate to the /u01/stage/Database directory:

$ cd /u01/stage/Database
Enter the following commands to upgrade the Empirica Signal schema for version 8.0.1:

$ sqlplus webvdme@<TNS_NAME> @update_8_0_to_8_0_1.sql
When prompted, type the webvdme user password.

Setting up the property files

Copy property files from the previously backed-up Signal 8.0 setup. For example:

$ cp /u01/stage/Signal_Install/Signal_8.0/WEB-INF/classes/webvdme.properties /u01/stage/Signal_Install /Signal/WEB-INF/classes

$ cp /u01/stage/Signal_Install/Signal_8.0/WEB-INF/classes/webvdme-fonts.properties /u01/stage/Signal_Install/Signal/WEB-INF/classes

$ cp /u01/stage/Signal_Install/Signal_8.0/WEB-INF/classes/listener.properties /u01/stage/Signal_Install /Signal/WEB-INF/classes

$ cp /u01/stage/Signal_Install/Signal_8.0/WEB-INF/classes/log4j.properties /u01/stage/Signal_Install/Signal/WEB-INF/classes
To support Asian Fonts in PDF documents, Unicode font Albany WT is packaged with Signal Installation. To make the Empirica Signal application use the appropriate font, the font file name has to be configured to the applicable properties in webvdme-fonts.properties. For example:

iText.TABLE_WRITER_BASE_FONT_PATH=ALBANYWTJ.TTF iText.CASE_SERIES_DETAIL_BASE_FONT_PATH=ALBANYWTJ.TTF iText.TOPIC_WRITER_BASE_FONT_PATH=ALBANYWTJ.TTF
If report_listener.properties file exists in the previously backed-up Signal 8.0 setup, copy it to the upgraded installation. For example:

$ cp /u01/stage/Signal_Install/Signal_8.0/WEB- INF/classes/report_listener.properties /u01/stage/Signal_Install/Signal/WEB-INF/classes

Or

If report_listener.properties file does not exist in the previously backed-up Signal 8.0 setup, follow the steps below:
1. Note the value of the serverid property in the listener.properties file.
2. Copy the template_report_listener.properties file into the same directory as report_listener.properties. For example:
  
  $ cp /u01/stage/Signal_Install/Signal/WEB- INF/classes/template_report_listener.properties /u01/stage/Signal_Install/Signal/WEB- INF/classes/report_listener.properties
3. Using a text editor, open the report_listener.properties file.
4. If the value of the serverid property in the file is the same value as the serverid property in the listener.properties file, change the value.
5. Save and close the file.
If LDAP is integrated with Empirica Signal 8.0 setup, copy ldap.properties to the upgraded installation. For example:

$ cp /u01/stage/Signal_Install/Signal_8.0/WEB-INF/classes/ldap.properties /u01/stage/Signal_Install/Signal/WEB-INF/classes

Preserving the Plan.xml file

If Plan.xml file exists in the previously backed-up Signal 8.0 setup, copy it to the upgraded installation. For example:

$ cp /u01/stage/Signal_Install/Signal_8.0/Plan.xml /u01/stage/Signal_Install/Signal/Plan.xml

Preserving custom home pages, release notes, and images from the 8.0 installation

Perform these steps using the non-privileged user account on the application server.

Perform these steps to preserve any customizations you made to release 8.0 and to copy Release Notes documents from the previous release.

Copy any relevant Release Notes documents from the previous installation location to the new installation location. For example, copy the Release Notes documents from the following location:

/u01/stage/Signal_Install/Signal_8.0/relnotes

to the following location:

/u01/stage/Signal_Install/Signal/relnotes

Note:

You do not need to copy the following documents: Release Notes documents for data releases that are no longer on your server, MedDRA documents for releases that are no longer on your server, Release Notes documents for prior releases of the Empirica Signal software, and any PDF version of the User Guide for prior releases.

Copy any custom content, such as custom home pages, from the previous installation location to the new installation location. For example, copy your file from the following location:

/u01/stage/Signal_Install/Signal_8.0/customhomes

to the following location:

/u01/stage/Signal_Install/Signal/image

Making the Release Notes available within the application

Obtain the most recent version of the Release Notes. For more information, see Documentation accessibility.
Copy the Release Notes to the following location:

/u01/stage/Signal_Install/Signal/relnotes

Deploying the Signal application

Perform these steps by connecting to the application server using a web browser:

Log in to the WebLogic Administration Console using the WebLogic administrator credentials provided to you by the system administrator. For example:

https://<servername>:<port>/console
In the left pane named Domain Structure, click Deployments.
In the Change Center section on the left, click Lock & Edit, if not done already.
Select Signal in the Deployments table.
In the Deployment table on the right, click the Update button.
Verify that Source path is pointing to the Signal installation directory.
On the Update Application Assistant page, click Finish.

The deployment is updated. This might take a few moments.
In the Change Center section on the left, click Activate Changes.

The deployment changes to the Prepared state.
Select the check box to the left of the Signal deployment, click the Start button, and select Servicing all requests from the drop-down list. Then click Yes.

The Empirica Signal application appears in the Deployments table with a state of active. You might need to refresh the display a few times until the state change occurs.

Restarting the SignalServer managed server

Perform these steps by connecting to the application server using a web browser:

Log in to the WebLogic Administration Console using the WebLogic administrator credentials provided to you by the system administrator. For example:

https://<servername>:<port>/console
In the left pane, expand Environment and select Servers.

The Summary of Servers page appears.
Select the Control tab.
From the list of servers, select the SignalServer.
From the Shutdown drop-down list, select Force Shutdown Now.
Wait.until the state of the server changes to SHUTDOWN.

The page does not refresh automatically. To refresh the page, click the Refresh button, located above the table, or click the Refresh button for your browser.
After the state of the server changes to SHUTDOWN, select the check box for SignalServer in the table, and click Start.
Wait until the state of the server changes to STARTING and then RUNNING.

The page does not refresh automatically. To refresh the page, click the Refresh button, located above the table, or click the Refresh button for your browser.

Verifying the Empirica Signal setup

To document and verify the upgrade, see the following documents:

UQ_Test.doc for upgrade qualification information.
OQ_Test.doc for operational qualification information.