Download and Unpack the Release Package

Copy the CenterView release package with a name matching centerview-x.y.z-yyyymmdd.zip to the release area $RELEASE on the server. By default $RELEASE is at [c:]/opt/centerview/release.

Unix

Change the owner and group of the release package to tomcat:cview:

chown centerview-x.y.z-yyymmdd.zip tomcat:cview

Switch to the tomcat user (makes sure that login scripts are run. The syntax for this may vary between operating systems:

su -l tomcat

Change back to the release directory and unzip / unpack the release:

unzip centerview-x.y.z-yyyymmdd.zip

This will create a release directories like:

centerview-x.y.z-yyyymmdd

centerview-x.y.z-yyyymmdd/schema

centerview-x.y.z-yyyymmdd/webapps

Windows

Unzip the release package using WINZIP or similar.

centerview-x.y.z-yyyymmdd

centerview-x.y.z-yyyymmdd/schema

centerview-x.y.z-yyyymmdd/webapps

Setting up the CenterView Database

The schema installation has 4 main steps, regardless of platform:

Create the database user
Create the tables required
Populate them with initial configuration data
Set the customer name

All of the commands below should be run from an operating system command window e.g. bash (Linux) or cmd (Windows), and the current directory should be set to that containing the installation instructions for the target platform.

E.g.

cd $RELEASE/centerview-x.y.z-yyyymmdd/install

Create the database user

Creating the database user is heavily dependent on the database platform, and will often have to be varied to meet local requirements regarding naming and security. These example commands will be adequate for basic installations.

Platform	Create the database user
Oracle:	This command will prompt for the name of the user to be created. sqlplus SYS/SYSPassword@SID as SYSDBA @schema/oracle/install/create_user
Sql Server:	This command requires the user, the password, the login and the database to be provided as parameters. sqlcmd -S localhost\myservice -i schema/sql_server/install/create_database_and_user.sql -v dbName="cview" dbLogin="cview" dbUser="cview" dbPassword="mypass"
MySQL:	Start a session the database: mysql --user=myrootuser --password Create the user, supplying the name of the database, the user and the password in the commands below: create database cview; grant all privileges on cview.* to 'myuser'@'%' identified by 'mypass'; exit

Populate the Database

Once you have created the database and/or database user, run the Installer to create the database tables and initial data.

The customer name in the commands below must exactly match the customer name used by CenterView Support to generate licence files. This argument (–customer="Your Customer Name") is optional, but without a valid customer name and matching licence key you will not be able to run any tasks in CenterView.

cd $RELEASE/centerview-x.y.z-yyyymmdd/install

Oracle:

java -jar bin/installer.jar -url="jdbc:oracle:thin:@localhost:1521:cview" -user=myuser -pass=mypass -install -customer="Your Customer Name"

SQL Server:

java -jar bin/installer.jar -url="jdbc:sqlserver://myhost\myserver;database=cview" -user=myuser -pass=mypass -install -customer="Your Customer Name"

MySQL:

java -jar bin/installer.jar -url="jdbc:mysql://localhost/cview" -user=myuser -pass=mypass -install -customer="Your Customer Name"

Further information on the installer

The database installation is now complete. For further information on the installer:

See the appendices for how to specify URLs for the database platforms supported by CenterView
To see all available options for the installer:

java -jar bin/installer.jar -help

Install the Webapp in the Tomcat application server

Copy or Move the CenterView web application into Tomcat

To install the CenterView web application into Tomcat:

Copy $RELEASE/webapps/centerview to $TOMCAT/webapps/centerview

Configure centerview-datasource.xml

The CenterView webapp must be configured to give access to the database user that has been created to hold the CenterView data.

In $TOMCAT/webapps/centerview/WEB-INF/classes, copy centerview-datasource.xml.<database>.example to centerview-datasource.xml and edit the properties for <bean id="dataSource"...., e.g.:

<value>jdbc:oracle:thin:@[SERVER IP ADDRESS]:1521:[SID]</value>

</property>

<value>[USERNAME]</value>

</property>

<value>[PASSWORD]</value>

</property>

See Database URLs for how to specify URLs for the database platforms supported by CenterView.

Configure centerview-instance.xml

The CenterView webapp instance must be configured to identify the instance and set whether the instance is active on startup.

For a single instance, non-resilient configuration, simply copy the example file centerview-instance.xml.example to centerview-instance.xml.

Resilient Configuration

A resilient CenterView configuration consists of 2 or more web applications all connected to a common database and configured such that at any one time, only one is active; the other instances will monitor the first and one will take over if they detect that the first has failed.

In such a configuration, set the instance name and id for each CenterView webapp instance to unique values and set leaderOnStartup to “true” for an instance if it should become active immediately on startup.

e.g.:

<bean id="clusterInstance"

class="com.accipia.centerview.service.cluster.main.ClusterInstance"

p:name="MAIN"

p:id=”1”

p:leaderOnStartup="true"

/>

See Configuring for Resilience for more information.

Configure centerview-domains.xml

The CenterView webapp can be configured to authenticate users’ usernames and passwords against an external Domain / Active Directory server.

If you don’t want want to enable domain logins, simply copy the example file provided.

For more information on how to configure for domain logins, see the CenterView ActiveDirectory Configuration userguide

Configure log4j.properties

The log4j.properties file controls detailed event/error logging on the server.

To configure for default logging:

Open or cd to $TOMCAT/webapps/centerview/WEB-INF/classes
Copy log4j.properties.example to log4j.properties

It is not necessary to make any changes to this file unless so instructed by CenterView Support.

If it is ever necessary to change this file, those changes will take effect within a few seconds, without having to restart the Tomcat server.

Multiple CenterView instances

To install multiple instances of CenterView on a single server, complete the installation steps above to create a first CenterView instance. Then install a further instance:

Create a second database user to hold the data for the new instance.
Copy the CenterView web application into the Tomcat again:

cp $RELEASE/webapps/centerview to $TOMCAT/webapps/alternative_name
where “alternative_name” is the name of your test system.
Be sure to set up a separate user and schema in the database for the new CenterView instance and to set centerview-datasource.xml as needed
To ensure log messages are sent to a separate file, change the following line in log4j.properties

log4j.appender.myAppender.file=logs/ alternative_name.log
To allow a user to view this instance of CenterView at the same time as the default instance, edit $TOMCAT/webapps/alternative_name/index.html:

Find the line containing the call to window.open and change the 2^nd parameter from ‘CenterView’ to ‘alternative_name’

Browser not supported