StruxureWare Data Center Operation
Installation and Upgrade Guide
Version 7.5
1. System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 StruxureWare Data Center Operation Compatibility with Linux-based Operating Systems . . . . . . . . . . . . . . . . . . . . . . . .
2. Installing StruxureWare Data Center Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Configuring a USB Key for StruxureWare Data Center Operation Installation on an HP Server . . . . . . . . . . . . . . . . . . . .
2.2 Installing StruxureWare Data Center Operation in a Virtual Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Installing StruxureWare Data Center Operation on Red Hat Enterprise Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1 List of Dependent Packages for Red Hat Enterprise Linux Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2 Installing with none standard system users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3. Upgrading from Previous Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Upgrading to StruxureWare Data Center Operation 7.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Upgrading to StruxureWare Data Center Operation 7.4.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Upgrading to StruxureWare Data Center Operation 7.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 Upgrading to 7.4 with Power Distribution Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5 Upgrading modular PDUs to 7.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6 Sudoers file update script when upgrading from 7.3.0 cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7 PDU Webmin Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.8 Upgrading the StruxureWare Data Center Operation server on Red Hat Enterprise Linux . . . . . . . . . . . . . . . . . . . . . . . . .
3.9 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.9.1 Migrating to StruxureWare Data Center Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.9.1.1 Migrating data from Emerson Aperture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.9.1.2 Migrating data from StruxureWare Data Center Expert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. Migrating a Cluster Environment to StruxureWare Data Center Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5. Initial Setup of StruxureWare Data Center Operation PRO Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Installing StruxureWare Data Center Operation PRO Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6. Installing IT Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 Upgrading IT Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7. Installing the StruxureWare Data Center Server Access Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
4
5
11
12
13
16
19
20
21
23
25
27
28
29
30
32
33
34
36
38
39
41
42
43
44
45
06/15/2015
Page 1
System Requirements
These system specifications are recommendations for your DCO system configuration in general. The performance and operation of the
system depends largely on the nature of the configuration, such as:
Number and population of racks
Number and nature of integrations to external systems
Number of devices and number of data points stored on these
Power path configuration (one big, several small, across rooms, etc.)
Concurrent and total users of the system and nature of their work cycle
Cluster configuration (recommended to run on hardware, not virtual setup for better ready time)
If StruxureWare Data Center Operation is running on lower specification servers than recommended, users may experience long
response times or timeout issues. In addition, the server may not be able to process scheduled jobs in a timely manner. This can lead to
an infinite job queue, where the amount of queued work on the StruxureWare Data Center Operation server is ever increasing to the
point where one or more StruxureWare Data Center Operation cluster servers are no longer responsive.
Recommended server hardware for StruxureWare Data Center Operation
The StruxureWare Data Center Operation Suite requires a dedicated server, either hardware or a virtual environment. The operating
system is included in the StruxureWare Data Center Operation installation. For further details, see here. The below requirements are
referring to the latest version StruxureWare Data Center Operation.
Recommended server configuration
Server requirement guidelines
CPU: 4 cores minimum. We recommend 8 cores
Memory: 16 GB RAM
100 GB storage, speed minimum 170 MB/s
Cluster network: 1 Gbps connection between nodes
Disaster recovery network: 10 Mbps with low latency <100 ms
Server requirement guidelines for 10,000 racks across 200 rooms with 30
concurrent users
8 CPU cores
32 GB RAM
1 Gbps network connection between cluster nodes
Storage speed minimum 170 MB/s
Server requirement guidelines for 20,000 racks across 400 rooms with 30
concurrent users
16 CPU cores
64 GB RAM
1 Gbps network connection between cluster nodes
Storage speed minimum 170 MB/s
RAID systems
Recommended: Hardware RAID controllers (we have tested hardware controllers in the following server series, DELL x20 series, IBM
M4 series, HP G8 series) Be aware there might be hardware RAID controllers that we have not tested in special configuration of the
server series mentioned.
Not supported:
Generally all software RAID controllers
HP RAID Controller B-Series
DELL RAID Controller S-Series
Security configuration
For information about security configuration, see here.
StruxureWare Data Center Operation Server Communication
06/15/2015
Page 2
For information on server communication, see here.
Recommended StruxureWare Data Center Operation Client Configuration
Processor: 2 GHz Intel Core 2 Duo (or equivalent)
Hard disk: 500 MB free hard disk space for installation
Memory: 4 GB RAM
Display: 1024x768 screen resolution with 16 million colors. For 3D view to work, 3D hardware including working drivers are
needed
Operating System: MS Windows Vista, Windows 7, Windows 8, Windows 8.1, Mac OS X (Mountain Lion), Linux (supported
Linux versions)
Browser: Internet Explorer (v9 and newer), Chrome (all versions), and Firefox (all versions)
These are the absolute minimum recommendations for running StruxureWare Data Center Operation but for larger setups, better
specifications are recommended.
You must have local administration rights on the client computer during installation, first login, and license upgrade.
See also
StruxureWare Data Center Operation Security
StruxureWare Data Center Operation Network Firewall Port Details
Installing StruxureWare Data Center Operation
Troubleshooting Performance Issues
Configuring External System Integration
StruxureWare Portal v.1.2
Installing IT Optimize
Initial Setup of StruxureWare Data Center Operation PRO Pack
06/15/2015
Page 3
StruxureWare Data Center Operation Compatibility with
Linux-based Operating Systems
Due to a wide range of system libraries included with Linux-based operating systems, StruxureWare Data Center Operation may not be
compatible with every Linux distribution currently available. Note that the distributions mentioned below are tested in their x86_64 (64-bit)
versions.
COMPATIBLE distributions that have minor or no known issues with StruxureWare Data Center Operation:
Debian 6.0.10 (released 2014-07-19)
Debian 7.7 (released 2014-10-18)
Linux Mint 13 (released 2012-05-13)
SUSE Linux Enterprise Desktop 11 SP3 (released 2013-07-08)
Ubuntu 12.04.5 LTS (released 2014-08-08)
The following distributions do not support report generation using the Analytics feature of StruxureWare Data Center Operation nor do
they support Asset Provisioning in Planning Mode:
CentOS 7, based on Red Hat Enterprise Linux 7 (released 2014-07-07)
Fedora 21 (released 2014-12-09)
Linux Mint 17 (released 2014-05-31)
openSUSE 13.2 (released 2014-11-04) With the information used here Generating Reports on Linux Asset Provisioning should
work.
Ubuntu 14.04 LTS (released 2014-04-17)
INCOMPATIBLE distributions that have major issues with StruxureWare Data Center Operation or will not work at all:
CentOS 6.6, based on Red Hat Enterprise Linux 6 (released 2014-10-28)
Mageia 4.1 (released 2014-06-20)
openSUSE 13.2 (released 2014-11-04)
SUSE Linux Enterprise Desktop 12 (released 2014-10-27)
There are no workarounds for incompatible distributions at the moment.
06/15/2015
Page 4
Installing StruxureWare Data Center Operation
You can install StruxureWare Data Center Operation in several ways. First, install the Data Center Operation server from a DVD, USB
key, or out-of-band management interface (LOM). Then, after installing the server, install the clients.
On this page:
Configuring the StruxureWare Data Center Operation installation DVD
Configuring the StruxureWare Data Center Operation installation USB key
Installing the StruxureWare Data Center Operation server from USB key or DVD
Installing the StruxureWare Data Center Operation server using out-of-band management interface
Installing the StruxureWare Data Center Operation server using alternative drivers
Installing StruxureWare Data Center Operation clients
If you use ETL integration to external databases, you must upgrade the Webmin ETL module. See more here.
Configuring the StruxureWare Data Center Operation installation DVD
To install from a DVD, download the StruxureWare Data Center Operation ISO and use your favorite application to burn the ISO to the
DVD. Insert the DVD and follow the instructions below.
Configuring the StruxureWare Data Center Operation installation USB key
If you are configuring the USB key for installation on an HP server, read separate instructions here.
Configuring an installation USB key for StruxureWare Data Center Operationonly requires you to run UNetbootin 1 using the Disk Image
and copy the ISO file to the USB key. Subsequently, you can install the Data Center Operation from the installation USB key to any
computer according to your licenses.
Prerequisites:
Before configuring the installation USB key, you must have
A USB key with sufficient space (4GB)
The StruxureWare Data Center Operation Installer Image file 2
The USB Creator Disk Image zip file 2
An installation of UNetbootin 1 on the computer you use for the USB key configuration
1
You can download UNetbootin from here.
2
You can download these from a location provided by the support team. To locate the telephone number for the support you need, visit
Contact Us.
1. Format the USB key in FAT32 or VFAT (recommended to ensure the installation is done from a clean USB key).
a. Plug in the USB key and follow the next steps (these apply to Windows).
b. Double-click My Computer on the desktop.
c. Right-click the USB key drive, and select Format.
d. In the pop-up window, select Quick Format.
2. Start UNetbootin 1.
3. Select Diskimage and make sure ISO is selected in the drop-down menu. Browse to the
StruxureWareOperations-USB-Diskimage-buildnumber.zip file.
4. Select Type: USB drive.
5. Select Drive: The appropriate USB Drive (from step 1).
6. Click OK.
The disk image is now copied to the USB key.
7. When the operation is done, click Exit.
8. Copy the StruxureWare Data Center Operation Installer Image file, StruxureWareOperations-buildnumber.iso, to the root of the
USB key.
9. Safely remove the USB key.
You now have a bootable USB key and can install the Data Center Operation server to any computer according to your licenses.
Illustration of steps 3-5
06/15/2015
Page 5
Installing the StruxureWare Data Center Operation server from USB key or
DVD
It is recommended that you follow the on-screen instructions and select the default options unless you have specific requirements.
1. Insert the StruxureWare Data Center Operation installation USB key or DVD.
2. Connect a keyboard and display.
3. Ensure the BIOS settings enable the server to boot from the USB key or DVD and the server is connected to the network during
the entire installation process.
4. In the StruxureWare Data Center Operation boot menu, select configuration:
Standalone / Disaster recovery, if installing a stand-alone StruxureWare Data Center Operation server or a Disaster
Recovery node.
Cluster, if installing a cluster node.
Alternative Drivers (newer hardware) is used for newer servers that have newer hardware. See more here.
5. In Set up users and passwords, type user credentials for a new user account that will be used for administrative tasks on the
server.
6. In Select a language, select the language to be used for the installation process as well as the default language of the installed
system.
7. In Select your location, select your country or the location matching your time zone.
8. When the server reboots, remove the USB key or DVD.
9. When the cursor reaches the operations login prompt, enter the user credentials created in step 5.
10. Type sudo ifconfig and your password when prompted. Make a note of the IP address of the Data Center Operation server.
Prefixing with sudo allows you to execute the command as a super user.
11. Open a browser and type in the IP address of the server, allowing time for the server to start up before proceeding to the next
step.
12. Click Server Configuration and login with the credentials created in step 5.
13. Click StruxureWare DC Operation -> Setup and complete the setup.
For information on security related settings, see StruxureWare Data Center Operation Security.
The Data Center Operation server is now installed and is ready for use.
Tip: Before leaving the command prompt, type sudo ifconfig and make a note of the IP address of the Data Center
Operationserver. You need this address to install the clients and perform server management tasks.
To set up a clustered environment with multiple servers, perform the above installation steps for each server that will be a node in the
cluster.
Note: If the installation fails due to drivers not found, (see screenshot) you might try to install using alternative drivers.
Boot menu
06/15/2015
Page 6
Drivers not found failure
06/15/2015
Page 7
Installing the StruxureWare Data Center Operation server using
out-of-band management interface
It is recommended that you follow the on-screen instructions and select the default options unless you have specific requirements.
Servers are often equipped with an out-of-band (OOB) management card. Depending on vendor, the technology has different names
(HP ILO, DELL iDRAC, IBM RSA). OOB management allows users to access the server remotely typically through an Ethernet
connection. This also gives access to the local media which makes it possible to install e.g. StruxureWare Data Center Operation server
from a remote location.
1. Access and log into the server OOB management card.
2. Launch the remote console.
3. The server should be connected to the network during the entire installation process (preferably high bandwidth through cable
due to full ISO being transferred to the server).
4. Mount the ISO as a virtual CD/DVD drive.
5. Ensure the BIOS settings enable the server to boot from the CD/DVD (or use the boot menu. Often F11 must be pressed during
server startup).
6. In the StruxureWare Data Center Operation boot menu, select configuration:
Standalone / Disaster recovery, if installing a stand-alone StruxureWare Data Center Operation server or a Disaster
Recovery node.
Cluster, if installing a cluster node.
Alternative Drivers (newer hardware) is used for newer servers that have newer hardware. See more here.
Note: Depending on the network connection, the install might be hanging for a moment. This is normally due to drivers
being transferred to the server.
7. In Set up users and passwords, type user credentials for a new user account that will be used for administrative tasks on the
server.
8. In Select a language, select the language to be used for the installation process as well as the default language of the installed
system.
9. In Select your location, select your country or the location matching your time zone.
10. When the server reboots, unmount the virtual CD/DVD drive.
11. When the cursor reaches the operations login prompt, enter the user credentials created in step 5.
12. Type sudo ifconfig and your password when prompted. Make a note of the IP address of the Data Center Operation server.
Prefixing with sudo allows you to execute the command as a super user.
13. Open a browser and type in the IP address of the server, allowing time for the server to start up before proceeding to the next
step.
14. Click Server Configuration and login with the credentials created in step 5.
15. Click StruxureWare DC Operation -> Setup and complete the setup.
For information on security related settings, see StruxureWare Data Center Operation Security.
The Data Center Operation server is now installed and is ready for use.
Tip: Before leaving the command prompt, type sudo ifconfig and make a note of the IP address of the Data Center
Operationserver. You need this address to install the clients and perform server management tasks.
To set up a clustered environment with multiple servers, perform the above installation steps for each server that will be a node in the
cluster.
Note: If the installation fails due to drivers not found (see screenshot), try to install using alternative drivers.
Boot menu
06/15/2015
Page 8
Drivers not found failure
06/15/2015
Page 9
Installing the StruxureWare Data Center Operation server using alternative
drivers
Alternative drivers are used for servers having newer hardware, such as network cards, harddrive controllers, etc. using drivers that are
not yet tested and verified stable by the OS distributors. When using the alternative drivers, you will get the same options to install Stand
alone/Disaster recovery or Cluster.
1. Follow the above installation instructions, but in step 4, select Alternative Drivers (newer hardware).
2. When you reach the screen with kernel module information, select Yes (see screenshot). Otherwise, the installation will not
complete.
Kernel module installation confirmation
Installing StruxureWare Data Center Operation clients
Prerequisite:
The server installation has been completed.
1. On the client computer, type the server's IP address in a Web browser.
2. On the Data Center Operation server's download page, click to download StruxureWare Data Center Operation and follow the
instructions in the installation wizard.
3. On the Data Center Operation server's download page, click to download the add-on modules according to your licenses and
follow the instructions in the installation wizard.
4. Repeat the installation steps on all client computers.
See also
System Requirements
Cluster Setup
Configuring a USB Key for StruxureWare Data Center Operation Installation on a HP Server
Installing StruxureWare Data Center Operation in a Virtual Environment
Changing the Location of the StruxureWare Data Center Operation Client Temporary Files
Installing StruxureWare Data Center Operation on Red Hat Enterprise Linux
06/15/2015
Page 10
Configuring a USB Key for StruxureWare Data Center Operation
Installation on an HP Server
Configuring a USB key for installing StruxureWare Data Center Operation on an HP server requires you to run UNetbootin 1 and follow
the below instructions. Subsequently, you can install the Data Center Operation from the installation USB key to any computer according
to your licenses.
Prerequisites:
Before configuring the USB key, you must have
A USB key (>=4GB)
The StruxureWare Data Center Operation Installer Image file 2
An installation of UNetbootin 1 on the computer you use for the USB key configuration
1
You can download UNetbootin from here.
2
You can download these from a location provided by the support team. To locate the telephone number for the support you need, visit
Contact Us.
1. Format the USB key in FAT32 or VFAT (recommended to ensure the installation is done from a clean USB key).
a. Plug in the USB key and follow the next steps (these apply to Windows).
b. Double-click My Computer on the desktop.
c. Right-click the USB key drive, and select Format.
d. In the pop-up window, select Quick Format.
2. Start UNetbootin 1.
3. Select Diskimage and click ... to browse to and select the .iso file.
4. Select Type: USB drive.
5. Select Drive: The appropriate USB Drive (from step 1).
6. Click OK.
The disk image is now copied to the USB key.
7. When the operation is done, click Exit.
8. Safely remove the USB key.
You now have a bootable USB key and can install the Data Center Operation server to any computer according to your licenses.
See also
Installing StruxureWare Data Center Operation
Installing StruxureWare Data Center Operation Server
Installing StruxureWare Data Center Operation Clients
06/15/2015
Page 11
Installing StruxureWare Data Center Operation in a Virtual
Environment
Recommendation: When installing StruxureWare Data Center Operation in a virtual environment, select Debian operating system
(version 5 or 6, 64 bit) as the guest operating system.
If you follow this recommendation, the configuration of virtual hardware, especially drivers, becomes easier. During the configuration, you
can simply select the default options that the system suggests. These default options are based on knowledge about the driver
installation on Debian 5 and 6, 64 bit.
If the Debian guest operating system type is not available in the virtual environment, configure the virtual hardware to be compatible with
StruxureWare Data Center Operation:
CPU architecture: 64 bit
SCSI Controller: LSI Logic Parallel
Network adaptor type: E1000
Apart from this recommendation, the same instructions and system requirements apply to the virtual environment as to a stand-alone
server.
For example, you may experience issues with the installation if you do not assign enough vRAM. The recommendation is 16 GB RAM
(as for a stand-alone server).
See also
Installing StruxureWare Data Center Operation
Optimizing Performance of StruxureWare Data Center Operation Running on VMware
System Requirements
06/15/2015
Page 12
Installing StruxureWare Data Center Operation on Red Hat
Enterprise Linux
Starting from version 7.4.5 StruxureWare Data Center Operation is available using Red Hat Enterprise Linux as OS on the server.
On this page:
Installation requirements
Installing the StruxureWare Data Center Operation server on Red Hat Enterprise Linux
Changes to the system
Manual control of creation of users and groups (optional)
Installing StruxureWare Data Center Operation clients
Uninstalling Data Center Operation on Red Hat Enterprise Linux
Installation requirements
Prerequisite: Before starting the install procedure, make sure that the general System Requirements are fulfilled. Furthermore the
following requirements should also be fulfilled:
A server running RHEL 6.x with at least minimal installation
An active RHEL subscription with access to the below channels
RHEL EUS Server Load Balancer channel, RHEL EUS Optional channel
Access to Red Hat Enterprise Linux Server x86_64 DVD
Disk space:
/data is used for indexes and ETL configuration. Minimum size 5 GB.
/data/backup is used for backups. Minimum size 50 GB. Backups should always be mounted on a remote network share.
/opt/jboss-as is used for the application server. Minimum size 10 GB.
/var/lib/pgsql is used for the postgres database. Minimum size 30 GB.
/var/log is used for log files. Minimum size 5 GB.
Total amount of space recommended for an installation is at least 100 GB in addition to the operating system.
If special configuration has been done please make sure /etc/sudoers.conf has the following lines:
## Read drop-in files from /etc/sudoers.d (the # here does not mean a comment)
#includedir /etc/sudoers.d
Installing the StruxureWare Data Center Operation server on Red Hat Enterprise
Linux
Please download the installation file: StruxureWareDataCenterOperation-Installer-x.x.x.el6.tar
Note: The below commands should be run with root credentials
1. Upload the installation file to /tmp/
2. Extract the installer by running the command: tar xvf /tmp/StruxureWareDataCenterOperation-Installer-x.x.x
.el6.tar -C /tmp
3. Execute the install script: bash /tmp/dco-install/install.sh
However, if installing a cluster node, execute the install script: bash /tmp/dco-install/install.s --clusternode
Changes to the system
The following system changes are applied during install of the StruxureWare Data Center Operation software.
DCO will install the listed packages if not already installed. Here is a list of dependent packages for Red Hat Enterprise Linux
installation.
iptables rules are set to DCO default locked down settings.
The SNMPd configuration is replaced with a DCO configuration to provide SNMP status for the DCO services.
The NTP configuration is changed to use default RHEL NTP servers. This can be changed afterwards through the server
management interface (Webmin).
The PostgreSQL configuration is replaced, and certificates for the database gets generated during install.
The Keepalived configuration is replaced.
06/15/2015
Page 13
SELinux is disabled.
CTRL+ALT+DELETE reboot is disabled.
UseDNS in SSH is disabled.
TCP Keepalive settings are modified.
Kernel shared memory, huge pages and network memory settings are modified.
The sudo configuration was changed. Adds sudo permissions to operations-platform and jboss user, removes requiretty
parameter.
logrotate has been configured to handle DCO and PostgreSQL logs.
Loads kernel module ip_vs and ip_vs_rr
The Apache configuration is modified.
The Webmin configuration is modified. Disables unused modules and changes security configuration.
Enable PostgreSQL starts at boot.
The default java is switched to Oracle 1.6.
Maximum number of files has been increased to 100000 for JBoss and root users.
Sudoers rules have been added for the jboss user to allow creation of ETL databases
Manual control of creation of users and groups (optional)
During the install process the setup script will automatically create 3 user accounts: jboss, operation-platform and postgres.
If required these accounts may be manually added by executing the following commands with root credentials prior to installation:
Add jboss user and group
groupadd --system jboss
useradd --system -g jboss --shell /bin/nologin --home-dir /opt/jboss-as -c
"StruxureWare Data Center Operation Application Server" --create-home jboss
Add operation-platform user and group
groupadd --system operation-platform
useradd --system -g operation-platform --shell /bin/sh --home-dir
/home/operation-platform -c "StruxureWare Data Center Operation Platform User"
--create-home operation-platform
Add postgres user
groupadd -g 26 -o -r postgres
useradd -M -n -g postgres -o -r -d /var/lib/pgsql -s /bin/bash -c "PostgreSQL Server"
-u 26 postgres
The postgres package performs the above commands. Changing UID/GID is currently untested.
Installing StruxureWare Data Center Operation clients
Prerequisite:
The server installation has been completed.
1. On the client computer, type the server's IP address in a Web browser.
2. On the Data Center Operation server's download page, click to download StruxureWare Data Center Operation and follow the
instructions in the installation wizard.
3. On the Data Center Operation server's download page, click to download the add-on modules according to your licenses and
follow the instructions in the installation wizard.
4. Repeat the installation steps on all client computers.
Uninstalling Data Center Operation on Red Hat Enterprise Linux
When you uninstall Data Center Operation server, some files will still exist on the server. This causes no problems in regards to installing
06/15/2015
Page 14
a new Data Center Operation.
Running the uninstall command will create a new file, isx-operation/config.rpmsave, containing all general system configurations.
However, if your isx-operations/config file has been modified to embrace any custom configurations (this is not typically the case), these
will be lost in the uninstall process.
Uninstall
rpm -e dco-server dco-platform perl-IPC-Run dco-config dco-clients dco-webminmodule
dco
mv /etc/postgresql/postgresql.conf/var/lib/pgsql/9.1/data/
mv /etc/postgresql/pg_ident.conf/var/lib/pgsql/9.1/data/
mv /etc/postgresql/pg_hba.conf/var/lib/pgsql/9.1/data/
See also
List of Dependent Packages for Red Hat Enterprise Linux Installation
Installing with none standard system users
Cluster Setup
06/15/2015
Page 15
List of Dependent Packages for Red Hat Enterprise Linux Installation
Repositories:
rhel-lb-for-rhel-6-server-eus-rpms = RHEL EUS Server Load Balancer channel
rhel-6-server-optional-rpms = RHEL EUS Optional channel
rhel-6-server-dvd-rpms = Red Hat Enterprise Linux Server x86_64 DVD
thirdparty-swdco-local-rpms = Packages included in the installer
Package name
Repository
apr
rhel-6-server-dvd-rpms
apr-util
rhel-6-server-dvd-rpms
apr-util-ldap
rhel-6-server-dvd-rpms
at
rhel-6-server-dvd-rpms
bc
rhel-6-server-dvd-rpms
cairo
rhel-6-server-dvd-rpms
compat-readline5
rhel-6-server-dvd-rpms
cvs
rhel-6-server-dvd-rpms
db4-cxx
rhel-6-server-dvd-rpms
db4-devel
rhel-6-server-dvd-rpms
ed
rhel-6-server-dvd-rpms
fontconfig
rhel-6-server-dvd-rpms
freetype
rhel-6-server-dvd-rpms
gdbm-devel
rhel-6-server-dvd-rpms
gettext
rhel-6-server-dvd-rpms
glibc-devel
rhel-6-server-dvd-rpms
glibc-headers
rhel-6-server-dvd-rpms
hdparm
rhel-6-server-dvd-rpms
httpd
rhel-6-server-dvd-rpms
httpd-tools
rhel-6-server-dvd-rpms
jdk
thirdparty-swdco-local-rpms
keepalived
rhel-lb-for-rhel-6-server-eus-rpms
kernel-headers
rhel-6-server-dvd-rpms
libX11
rhel-6-server-dvd-rpms
libX11-common
rhel-6-server-dvd-rpms
libXau
rhel-6-server-dvd-rpms
libXfont
rhel-6-server-dvd-rpms
libXft
rhel-6-server-dvd-rpms
libXrender
rhel-6-server-dvd-rpms
libdbi
rhel-6-server-dvd-rpms
libfontenc
rhel-6-server-dvd-rpms
libgomp
rhel-6-server-dvd-rpms
libpng
rhel-6-server-dvd-rpms
libthai
rhel-6-server-dvd-rpms
06/15/2015
Page 16
libxcb
rhel-6-server-dvd-rpms
lm_sensors-libs
rhel-6-server-dvd-rpms
mailcap
rhel-6-server-dvd-rpms
mailx
rhel-6-server-dvd-rpms
man
rhel-6-server-dvd-rpms
mod_ssl
rhel-6-server-dvd-rpms
net-snmp
rhel-6-server-dvd-rpms
net-snmp-libs
rhel-6-server-dvd-rpms
ntp
rhel-6-server-dvd-rpms
ntpdate
rhel-6-server-dvd-rpms
pango
rhel-6-server-dvd-rpms
patch
rhel-6-server-dvd-rpms
pax
rhel-6-server-dvd-rpms
perl-Archive-Extract
rhel-6-server-dvd-rpms
perl-Archive-Zip
rhel-6-server-optional-rpms
perl-CGI
rhel-6-server-dvd-rpms
perl-Compress-Raw-Zlib
rhel-6-server-dvd-rpms
perl-Compress-Zlib
rhel-6-server-dvd-rpms
perl-Config-General
rhel-6-server-dvd-rpms
perl-Crypt-OpenSSL-X509
thirdparty-swdco-local-rpms
perl-Crypt-SSLeay
rhel-6-server-dvd-rpms
perl-DBD-Pg
rhel-6-server-dvd-rpms
perl-DBI
rhel-6-server-dvd-rpms
perl-Data-UUID
thirdparty-swdco-local-rpms
perl-ExtUtils-MakeMaker
rhel-6-server-dvd-rpms
perl-ExtUtils-ParseXS
rhel-6-server-dvd-rpms
perl-HTML-Parser
rhel-6-server-dvd-rpms
perl-HTML-Tagset
rhel-6-server-dvd-rpms
perl-IO-Compress-Base
rhel-6-server-dvd-rpms
perl-IO-Compress-Zlib
rhel-6-server-dvd-rpms
perl-IO-Tty
rhel-6-server-optional-rpms
perl-IPC-Run
thirdparty-swdco-local-rpms
perl-Locale-Maketext-Simple
rhel-6-server-dvd-rpms
perl-Math-Round
thirdparty-swdco-local-rpms
perl-Module-Load
rhel-6-server-dvd-rpms
perl-Module-Load-Conditional
rhel-6-server-dvd-rpms
perl-Net-SSLeay
rhel-6-server-dvd-rpms
perl-Params-Check
rhel-6-server-dvd-rpms
perl-RRD-Simple
thirdparty-swdco-local-rpms
perl-Test-Harness
rhel-6-server-dvd-rpms
perl-Test-Simple
rhel-6-server-dvd-rpms
perl-Time-HiRes
rhel-6-server-dvd-rpms
06/15/2015
Page 17
perl-TimeDate
rhel-6-server-dvd-rpms
perl-URI
rhel-6-server-dvd-rpms
perl-XML-LibXML
rhel-6-server-dvd-rpms
perl-XML-NamespaceSupport
thirdparty-swdco-local-rpms
perl-XML-Parser
rhel-6-server-dvd-rpms
perl-XML-SAX
rhel-6-server-dvd-rpms
perl-XML-Simple
thirdparty-swdco-local-rpms
perl-XML-XPath
rhel-6-server-dvd-rpms
perl-devel
rhel-6-server-dvd-rpms
perl-libwww-perl
rhel-6-server-dvd-rpms
perl-rrdtool
thirdparty-swdco-local-rpms
pixman
rhel-6-server-dvd-rpms
postgresql91
thirdparty-swdco-local-rpms
postgresql91-contrib
thirdparty-swdco-local-rpms
postgresql91-libs
thirdparty-swdco-local-rpms
postgresql91-server
thirdparty-swdco-local-rpms
redhat-lsb-core
rhel-6-server-dvd-rpms
rrdtool
thirdparty-swdco-local-rpms
ruby
rhel-6-server-dvd-rpms
ruby-libs
rhel-6-server-dvd-rpms
smartmontools
rhel-6-server-dvd-rpms
time
rhel-6-server-dvd-rpms
ttmkfdir
rhel-6-server-dvd-rpms
unzip
rhel-6-server-dvd-rpms
uuid
rhel-6-server-dvd-rpms
wbm-sysstats
thirdparty-swdco-local-rpms
webmin
thirdparty-swdco-local-rpms
xorg-x11-font-utils
rhel-6-server-dvd-rpms
xorg-x11-fonts-Type1
rhel-6-server-dvd-rpms
xz
rhel-6-server-dvd-rpms
xz-lzma-compat
rhel-6-server-dvd-rpms
06/15/2015
Page 18
Installing with none standard system users
During the installation process the setup script will automatically create 3 user accounts: dcojboss, dcoplat and postgres (postgres
user is part of the standard postgres database installation and could potentially also be changed).
Starting from version 7.5 it is possible to alter the dcojboss and dcoplat users. To do so the below steps must be performed prior to
installing StruxureWare Data Center Operation.
Altering users dcojboss and/or dcoplat
Install the dco-systemusers rpm package in order to create a system users configuration file (assuming the DCO installer files have been
extracted into the /tmp folder)
rpm -i /tmp/dco-install/rpms/dco-systemusers_*.rpm
The system users configuration file will be located in /etc/isx-operations/dco-system-users
By editing the configuration file prior to installation of StruxureWare Data Center Operation, you allow the system to operate using the
usernames specified in the file.
dco-system-users configuration file
DCO_JBOSS_USER=<JBossUsername>
DCO_PLAT_USER=<PlatformUsername>
Users will be created, if not already available in the system, based on the usernames specified in the dco-system-users file.
If a non-standard /etc/sudoers.conf file is used on the server, a system administrator must edit it and apply the configuration
specific to the two users previously created. This configuration can be found in two configuration files, one for each user, in the
directory /etc/sudoers.d/
Altering the usernames in the dco-system-users file after installation will break the system.
When setting up a cluster environment, you must make sure the DCO_JBOSS_USER, DCO_PLAT_USER usernames are
identical across all the nodes in the system setup.
User requirement if already in the system
As mentioned the users might already be in the system. There are some simple requirements for the users that must be fulfilled.
DCO_JBOSS_USER must have a home directory being /opt/jboss-as
DCO_PLAT_USER must have a home directory located in /home and username as folder name, e.g. /home/<PlatformUsername>
postgres user is added during postgres installation. If you want to change this user, this must be done while manually installing postgres.
06/15/2015
Page 19
Upgrading from Previous Versions
Supported upgrades of StruxureWare Data Center Operation:
From
Migrate to
6.0
6.1
6.2
7.x
7.2.x
7.3.x
7.4.x
From
Upgrade to
7.0
7.0.1
7.0.1
7.0.2
7.1
7.0.2
7.1
7.1
7.2
7.2
7.2.x
7.3
7.3.x
7.4.x
7.4
7.4.x
7.5
Watch this video tutorial to learn the upgrade paths up until version 7.2.5.
See also
Upgrading to StruxureWare Data Center Operation 7.5
Upgrading to StruxureWare Data Center Operation 7.4.5
Upgrading to StruxureWare Data Center Operation 7.4
Migrating to StruxureWare Data Center Operation 7.3
06/15/2015
Page 20
Upgrading to StruxureWare Data Center Operation 7.5
Upgrading to StruxureWare Data Center Operation version 7.5 from version 7.3.x or 7.4.x takes at least 10 minutes (however depending
on size of your solution). An upgrade of the Webmin module is needed when upgrading. You must have a valid service contract to be
able to download this version. It is recommended that you perform a backup of the data on the Data Center Operation server before
initializing the upgrade.
Note: If you have modular PDUs in your setup and run a version prior to v7.4, download and use the Webmin plugin described her
e before you upgrade.
Note: If you run an External system integration through ETL, see ETL - Extract Transform Load before you upgrade.
From Version
Upgrade Path
7.4, 7.4.x, 7.3, 7.3.x
Upgrade to 7.5 following the guide on this page.
Prior to 7.3
Backup existing database > Install 7.5 > Restore database from
previous version in 7.5. Get more info here.
Red Hat
You can restore a DCO backup from an older DCO system on a Red Hat based DCO server.
You can read upgrade instructions for DCO on Red Hat here.
These instructions take you through the upgrade in a cluster environment. If you are upgrading a single StruxureWare Data Center
Operation installation, simply ignore the instructions about additional nodes and follow the rest of the instructions.
If you are upgrading a cluster environment, the StruxureWare Data Center Operation upgrade only needs to be performed on one node.
The upgrade scripts apply the upgrade to all the cluster nodes.
If you have a disaster recovery node, you will have to upgrade that after upgrading the cluster.
If you upgrade in a cluster environment, the upgrade takes up to about 20 minutes.
Prerequisites:
Back up the data on the Data Center Operation server.
Uploading the upgrade file through Webmin requires a browser supporting file upload sizes over 2GB, such as:
Chrome, version 8 or higher (Windows, Mac OS X, Linux)
Safari, version 5 or higher (Windows, Mac OS X)
Opera, version 11 or higher (Windows, Mac OS X, Linux)
If you are upgrading a cluster environment, you must ensure all cluster nodes run and can access the upgrade file before
beginning the upgrade.
If you are upgrading a cluster environment from version 7.3.0, run the sudoers upgrade file script before beginning the upgrade.
1. Download the upgrade file and copy the MD5 key from a location provided by the support team.
To locate the telephone number for the support you need, visit Contact Us.
StruxureWareDataCenterOperation-Upgrade-Webmin-Module-1.6.wbm.tgz: File to update Webmin with the new
upgrade module
StruxureWareDataCenterOperation-Upgrade-7.5.tgz: File with the new version of the Data Center Operation server and
scripts to upgrade StruxureWare Data Center Operation
2. Upgrade the Webmin Module.
On 7.3 and 7.4 this step should be repeated for each node in the cluster environment.
a. Open the Webmin web interface by typing the address of your StruxureWare Data Center Operation server followed by
:10000 in a Web browser, https://<yourservername>:10000/.
b. Log on to Webmin using the user credentials created during the installation.
c. In the left menu, select Webmin>Webmin Configuration.
d. Select Webmin Modules.
e. In the Install tab, select Install from uploaded file and browse to the location of the downloaded
StruxureWareDataCenterOperation-Webmin-Module-1.6.wbm.tgz file.
f. Click Install Module.
3. Upgrade StruxureWare Data Center Operation.
4. In a cluster environment this step is only required on the node where the upgrade is performed.
a. In the Webmin left menu, select StruxureWare DC Operation>Upgrade.
b. In Select upgrade file, browse to the location of the downloaded StruxureWareDataCenterOperation-Upgrade-7.5.tgz
file.
c. Copy the md5 key (available from the download page) and paste it into the MD5 key from the upgrade file field.
d. Click Upgrade.
5. When you have completed the upgrade, download the latest version of the StruxureWare Data Center Operation client.
a.
06/15/2015
Page 21
5.
a. To open the Data Center Operation server's download page, type the address of your StruxureWare Data Center
Operation server in a Web browser, https://<yourservername>.
b. Click to download StruxureWare Data Center Operation and follow the instructions in the installation wizard.
c. Click to download the add-on modules according to your licenses and follow the instructions in the installation wizard.
The next steps are only required under the following circumstances.
If you have a disaster recovery node running, upgrade the disaster recovery node like upgrading a standalone server (Steps 1+2
above).
If you use ETL integration to external databases, upgrade the Webmin ETL module.
1. Open the Webmin web interface by typing the address of your StruxureWare Data Center Operation server followed by :10000
in a Web browser, https://<yourservername>:10000/.
2. Log on to Webmin using the user credentials created during the installation.
3. In the left menu, select Webmin>Webmin Configuration.
4. Select Webmin Modules.
5. In the Install tab, select Install from uploaded file and browse to the location of the downloaded
StruxureWareDataCenterOperation-Webmin-Module-1.6-ETL-Patch.tgz file.
6. Click Install Module.
See also
Upgrading from Previous Versions
What is new in StruxureWare Data Center Operation 7.5?
Upgrading the StruxureWare Data Center Operation server on Red Hat Enterprise Linux
06/15/2015
Page 22
Upgrading to StruxureWare Data Center Operation 7.4.5
Upgrading to StruxureWare Data Center Operation version 7.4.5 from version 7.3.x or 7.4 takes at least 10 minutes (however depending
on size of your solution). An upgrade of the Webmin module is needed when upgrading. You must have a valid service contract to be
able to download this version. It is recommended that you perform a backup of the data on the Data Center Operation server before
initializing the upgrade.
Note: If you have modular PDUs in your setup and run a version prior to v7.4, download and use the Webmin plugin described her
e before you upgrade.
Note: If you run an External system integration through ETL, see ETL - Extract Transform Load before you upgrade.
From Version
Upgrade Path
7.4, 7.3, 7.3.x
Upgrade to 7.4.5 following the guide on this page.
Prior to 7.3
Backup existing database > Install 7.4.5 > Restore database
from previous version in 7.4.5. Get more info here.
You can restore a DCO backup from an older DCO system on a Red Hat based DCO server.
These instructions take you through the upgrade in a cluster environment. If you are upgrading a single StruxureWare Data Center
Operation installation, simply ignore the instructions about additional nodes and follow the rest of the instructions.
If you are upgrading a cluster environment, the StruxureWare Data Center Operation upgrade only needs to be performed on one node.
The upgrade scripts apply the upgrade to all the cluster nodes.
If you have a disaster recovery node, you will have to upgrade that after upgrading the cluster.
If you upgrade in a cluster environment, the upgrade takes up to about 20 minutes.
Prerequisites:
Back up the data on the Data Center Operation server.
Uploading the upgrade file through Webmin requires a browser supporting file upload sizes over 2GB, such as:
Chrome, version 8 or higher (Windows, Mac OS X, Linux)
Safari, version 5 or higher (Windows, Mac OS X)
Opera, version 11 or higher (Windows, Mac OS X, Linux)
If you are upgrading a cluster environment, you must ensure all cluster nodes run and can access the upgrade file before
beginning the upgrade.
If upgrading from version 7.3.0, make sure to run this script on all notes before upgrading.
1. Download the upgrade file and copy the MD5 key from a location provided by the support team.
To locate the telephone number for the support you need, visit Contact Us.
StruxureWareDataCenterOperation-Upgrade-Webmin-Module-1.6.wbm.tgz: File to update Webmin with the new
upgrade module
StruxureWareDataCenterOperation-Upgrade-7.4.5.tgz: File with the new version of the Data Center Operation server
and scripts to upgrade StruxureWare Data Center Operation
2. Upgrade the Webmin Module
On 7.3 and 7.4 this step should be repeated for each node in the cluster environment.
a. Open the Webmin web interface by typing the address of your StruxureWare Data Center Operation server followed by
:10000 in a Web browser, https://<yourservername>:10000/.
b. Log on to Webmin using the user credentials created during the installation.
c. In the left menu, select Webmin>Webmin Configuration.
d. Select Webmin Modules.
e. In the Install tab, select Install from uploaded file and browse to the location of the downloaded
StruxureWareDataCenterOperation-Webmin-Module-1.6.wbm.tgz file.
f. Click Install Module.
3. Upgrade StruxureWare Data Center Operation .
06/15/2015
Page 23
3.
In in a cluster environment this step is only required on the node where the upgrade is performed.
a. In the Webmin left menu, select StruxureWare DC Operation>Upgrade.
b. In Select upgrade file, browse to the location of the downloaded
StruxureWareDataCenterOperation-Upgrade-7.4.5.tgz file.
c. Copy the md5 key (available from the download page) and paste it into the MD5 key from the upgrade file field.
d. Click Upgrade.
4. When you have completed the upgrade, download the latest version of the StruxureWare Data Center Operation client.
a. To open the Data Center Operation server's download page, type the address of your StruxureWare Data Center
Operation server in a Web browser, https://<yourservername>.
b. Click to download StruxureWare Data Center Operation and follow the instructions in the installation wizard.
c. Click to download the add-on modules according to your licenses and follow the instructions in the installation wizard.
The next steps are only required under the following circumstances.
If you have a disaster recovery node running, upgrade the disaster recovery node like upgrading a standalone server (Steps 1+2
above).
If you use ETL integration to external databases, upgrade the Webmin ETL module.
a. Open the Webmin web interface by typing the address of your StruxureWare Data Center Operation server followed by
:10000 in a Web browser, https://<yourservername>:10000/.
b. Log on to Webmin using the user credentials created during the installation.
c. In the left menu, select Webmin>Webmin Configuration.
d. Select Webmin Modules.
e. In the Install tab, select Install from uploaded file and browse to the location of the downloaded
StruxureWareDataCenterOperation-Webmin-Module-1.6-ETL-Patch.tgz file.
f. Click Install Module.
See also
Upgrading from Previous Versions
What is new in StruxureWare Data Center Operation 7.4.5?
06/15/2015
Page 24
Upgrading to StruxureWare Data Center Operation 7.4
Upgrading to StruxureWare Data Center Operation version 7.4 from version 7.3, 7.3.5 or 7.3.6 takes at least 10 minutes (however
depending on size of your solution). An upgrade of the Webmin module is not needed when upgrading from version 7.3.5 or 7.3.6. You
must have a valid service contract to be able to download this version. It is recommended that you perform a backup of the data on the
Data Center Operation server before initializing the upgrade.
Note: If you have modular PDUs in your setup make sure the modular PDU is correctly configured (model name & module
number(s)). Download the PDU webmin plugin to identify configuration issues with modular PDUs before the upgrade. Download
and use of the webmin plugin is described here.
Note: If you are running a version prior to 7.3, you must combine a clean installation of 7.4 with a backup and restore of the
database from the previous version in the same way as described for version 7.3 here.
Note: If you were using External system integration through ETL in version prior to 7.4, you need to migrate your ETL setup as
described in this article: ETL - upgrade
Note: If you have filters configured in Power Distribution Report you need to follow this guide before you upgrade to v7.4. This
applies to all versions prior to v7.4.
From Version
Upgrade Path
7.3.5, 7.3.6
Upgrade to 7.4
7.3
Upgrade to 7.4 however make sure Webmin module is updated
to v1.5 as described here.
Prior to 7.3
Backup existing database > Install 7.4 > Restore database from
previous version in 7.4 more info here.
These instructions take you through the upgrade in a cluster environment. If you are upgrading a single StruxureWare Data Center
Operation installation, simply ignore the instructions about additional nodes and follow the rest of the instructions.
If you are upgrading a cluster environment, the StruxureWare Data Center Operation upgrade only needs to be performed on one node.
The upgrade scripts apply the upgrade to all the cluster nodes.
If you have a disaster recovery node, you will have to upgrade that after upgrading the cluster.
If you upgrade in a cluster environment, the upgrade takes up to about 20 minutes.
Prerequisites:
Back up the data on the Data Center Operation server.
Uploading the upgrade file through Webmin requires a browser supporting file upload sizes over 2GB, such as:
Chrome, version 8 or higher (Windows, Mac OS X, Linux)
Safari, version 5 or higher (Windows, Mac OS X)
Opera, version 11 or higher (Windows, Mac OS X, Linux)
If you are upgrading a cluster environment, you must ensure all cluster nodes run and can access the upgrade file before
beginning the upgrade.
If upgrading from version 7.3.0, make sure to run this script on all notes before upgrading.
1. Download the upgrade file and copy the MD5 key from a location provided by the support team.
To locate the telephone number for the support you need, visit Contact Us.
StruxureWareDataCenterOperation-Upgrade-7.4.tgz: File with the new version of the Data Center Operation server and
scripts to upgrade
StruxureWare Data Center Operation
2. Upgrade Webmin module
a. In the left menu, select Webmin >Webmin Configuration
b. Select Upgrade Webmin
c. In the Upgrade Webmin tab, select Latest version from www.webmin.com
d. Click Upgrade Webmin
e. Repeat the Webmin upgrade process on all nodes so they all have the same version. You have now installed the
Webmin upgrade module on all nodes. To verify that the process was successful, check that the text above Webmin
install complete has been updated or select System Information in the left menu in Webmin and check the version.
Note: If you cannot get the latest version from the Web, because of company policies or other reasons, *upgrade S
truxureWare Data Center Operation first*, and then:
06/15/2015
Page 25
1. In the Webmin left menu, select Webmin > Webmin Configuration.
2. In the Upgrade Webmin tab, select From local file and browse to the /data/webmin-<version>_all.deb file.
3. Click Upgrade Webmin.
You can only do this after the StruxureWare Data Center Operation upgrade, since the necessary file is included in
that upgrade.
If you get this error after upgrading using the .deb file, you can safely ignore it, since the upgrade did complete.
3. Upgrade StruxureWare Data Center Operation .
This step is only required on one node in a cluster environment.
a. In the Webmin left menu, select StruxureWare DC Operation>Upgrade.
b. In Select upgrade file, browse to the location of the downloaded StruxureWareDataCenterOperation-Upgrade-7.4.tgz
file.
c. Copy the md5 key (available from the download page) and paste it into the MD5 key from the upgrade file field.
d. Click Upgrade.
4. When you have completed the upgrade, download the latest version of the StruxureWare Data Center Operation client.
a. To open the Data Center Operation server's download page, type the address of your StruxureWare Data Center
Operation server in a Web browser, https://yourservername.
b. Click to download StruxureWare Data Center Operation and follow the instructions in the installation wizard.
c. Click to download the add-on modules according to your licenses and follow the instructions in the installation wizard.
5. This step is only required if you have a disaster recovery node running.
a. Upgrade the disaster recovery node like upgrading a standalone server (Step 1+2)
See also
Upgrading from Previous Versions
What is new in StruxureWare Data Center Operation 7.4?
Upgrade modular PDUs to 7.4
Upgrade to 7.4 with power distribution filter
06/15/2015
Page 26
Upgrading to 7.4 with Power Distribution Filter
If you have filters configured in the Power Distribution report, you must follow this guide before you upgrade to 7.4. This applies to all
versions prior to v7.4.
The power distribution report has been replaced in 7.4 and above and any power distribution filters will result in a failing upgrade.
1. Backup your solution.
2. Open your currently installed version of StruxureWare Data Center Operation.
3. Go to Analytics > Reports and select Power Distribution Report.
4. If you have filters, they will be listed underneath the power distribution report.
5. You must delete all Power Distribution filters.
a. Right-click and delete each filter.
6. Back up and restore your solution. See Backing up and restoring.
7. You are now ready to upgrade to 7.4.
See also
Upgrading from previous versions
06/15/2015
Page 27
Upgrading modular PDUs to 7.4
For a modular floor-mounted PDU to be recognized as a modular PDU after the upgrade to 7.4, the following must be configured prior to
upgrading:
The PDU model name must contain the word “Modular" or "modular” (see Fig1)
Module number must be defined (see Fig2)
No device sensor mapping (Branch Circuit Monitoring using Modular PDU device is allowed)
No manual measurement must be defined on the PDU
Screenshot from 7.3.6
Fig1. PDU model name
Fig2. How to configure Module number in 7.3.6
See also
PDU Webmin Plugin
06/15/2015
Page 28
Sudoers file update script when upgrading from 7.3.0 cluster
When upgrading a cluster environment from version 7.3.0 make sure to run the following script on all notes before upgrading.
ssh <someuser>@<server ip>
######### Begin ##########
sudo cat /etc/sudoers.d/operation-platform >> /tmp/operation-platform-tmp
/bin/cat <<'EOF' >> /tmp/operation-platform-tmp
operation-platform ALL = NOPASSWD: /usr/sbin/service operations-monitor *
EOF
chmod 400 /tmp/operation-platform-tmp
sudo /bin/cp /tmp/operation-platform-tmp /etc/sudoers.d/operation-platform
########## End ###########
See also
Upgrading from Previous Versions
06/15/2015
Page 29
PDU Webmin Plugin
This PDU Webmin plugin is a tool to identify any configuration issues with modular PDUs that need to be solved prior to an upgrade
to StruxureWare Data Center Operation version 7.4. Download and install the plugin before you upgrade.
Installing the Webmin plugin
1.
2.
3.
4.
5.
6.
Download the file here.
Open the Webmin web interface and click Server Configuration.
In the left menu, select Webmin>Webmin Configuration>Webmin Modules.
In the Install tab, select Install from uploaded file>Choose the PDU webmin plugin on your computer.
If you do not have a root user, you must Grant access to all Webmin users (see picture).
Click Install module.
Note: This plugin does not make any changes on the server. It requests information on configuration issues that you
must fix manually in your client.
7. Log out and log on again.
Get Webmin plugin
Using the plugin
1. In the left menu, select StruxureWare DC Operation>Modular PDU pre 7.4 upgrade.
2. The modular PDUs found here will be recognized as modular PDUs after an upgrade. They may still need configuration.
3. Configuration issues will appear in the Comment section. See configuration issues and how to solve them here.
Note: You cannot edit through the Webmin plugin. Any configurations must take place in your client.
4.
5.
6.
7.
In the left menu, select StruxureWare DC Operation>Generic PDU pre 7.4 upgrade.
The modular PDUs found here must be configured before they can be recognized as modular PDUs in 7.4.
Configure the PDUs in your client according to the causes in the last column in the Webmin module plugin.
Save your client and reopen the plugin to verify that the changes you made have been registered.
Deleting and upgrading
When there are no more comments or causes and all your modular PDUs appear under Modular PDU pre 7.4 upgrade, you should
delete the plugin before you upgrade. The plugin will not work in 7.4.
1.
2.
3.
4.
5.
In the left menu, select Webmin Configuration.
Select Webmin Modules and the tab Delete.
Find Modular PDU pre 7.4 upgrade Check (v1.5) and Generic PDU pre 7.4 upgrade Check (v.1.5).
Click Delete selected modules.
Upgrade - see here.
Modular PDU pre 7.4 upgrade
06/15/2015
Page 30
Generic PDU pre 7.4 upgrade
Configuration Issues
No breaker module numbers - add breaker module numbers in the Power Distribution Panel
Wrong model name - see here
Device sensor mapping - device sensor mapping for modular PDUs is not supported in 7.4. (Branch Circuit monitoring using
Modular PDU device is allowed). If you want the PDU to be recognized as modular after the upgrade, you must delete device
sensor mappings. Otherwise, it will appear as a generic PDU in 7.4.
Manual measurements - no manual measurement must be defined on the modular PDU before upgrade. Manual
measurements are not supported for modular PDUs in 7.4. Otherwise, it will appear as a generic PDU in 7.4.
See also
Upgrading modular PDUs to 7.4
06/15/2015
Page 31
Upgrading the StruxureWare Data Center Operation server on Red
Hat Enterprise Linux
1. Download the Webmin module and DCO upgrade files:
StruxureWareDataCenterOperation-Webmin-Module-RHEL-x.x.tgz
StruxureWareDataCenterOperation-Installer-x.x.x.el6.tar
2. Upgrade the Webmin module.
a. Open the Webmin web interface by typing the address of your StruxureWare Data Center Operation server followed by
:10000 in a Web browser, https://<yourservername>:10000/.
b. Log on to Webmin using the user credentials created during the installation.
c. In the left menu, select Webmin>Webmin Configuration.
d. Select Webmin Modules.
e. In the Install tab, select Install from uploaded file and browse to the location of the downloaded
StruxureWareDataCenterOperation-Webmin-Module-RHEL-x.x.tgz file.
f. Click Install Module.
3. Upgrade StruxureWare Data Center Operation.
a. In the Webmin left menu, select StruxureWare DC Operation>Upgrade.
b. In Select upgrade file, browse to the location of the downloaded
StruxureWareDataCenterOperation-Installer-x.x.x.el6.tar file.
c. Copy the md5 key (available from the download page) and paste it into the MD5 key from the upgrade file field.
d. Click Upgrade.
Note: In a cluster environment, the Webmin module must be upgraded on each node. Upgrading a Disaster Recovery node
requires the same steps as upgrading a standalone server.
See also
Upgrading from Previous Versions
Installing StruxureWare Data Center Operation on Red Hat Enterprise Linux
06/15/2015
Page 32
Migration
Migration is used for moving existing data to and from the Data Center Operation server. Situations in which migration could be used
include:
Backing up and restoring a solution
Restoring an older version of DCO
The migration process depends on which version you restore, see here and here.
Moving existing data from Emerson Aperture
Moving existing data from different solutions into one (merging)
When you migrate more rooms from different solutions into one using the backup process in Webmin together with the Migrate
option in DCO, you do not risk overwriting rooms with other rooms as they will be appended. Do not use the backup/restore
process in Webmin for moving data into an existing solution as this will wipe all data.
See also
Migrating to StruxureWare Data Center Operation
Migrating a Cluster Environment to StruxureWare Data Center Operation
Migrating data from Emerson Aperture
Migrating data from StruxureWare Data Center Expert
06/15/2015
Page 33
Migrating to StruxureWare Data Center Operation
In versions prior to version 7.3 of StruxureWare Data Center Operation, you could upgrade an existing Data Center Operation server to
a later version. However, because of new security enhancements and different hardware requirements, it is not possible to upgrade to
version 7.3 and newer. A new installation of StruxureWare Data Center Operation v7.3 or newer is required, preferably on a new
dedicated server. You can transfer all your data (data center model, user settings and historical data) without loss using the backup and
restore procedure.
It is recommended that you install StruxureWare Data Center Operation on a new server. In this case, you can create a backup of the
existing version on the old server by using the default backup options in the Webmin server interface as described below.
Installing StruxureWare Data Center Operation on the existing server is not recommended. If you choose this approach, be sure to
create an external backup file before beginning the new installation process. This includes mounting a share to save the backup on your
network. See more here
First, remember to back up your solution to be able to restore the backup after installing StruxureWare Data Center Operation on
the new server. The installation will wipe all current data. You will lose all data if you skip creating the backup.
1.
2.
3.
4.
Install on a new server.
Save a backup of the existing server.
Copy the backup file to the new server.
Access the backup file on the new server.
Setting up a new server with a clean installation of StruxureWare Data Center Operation
See the entire installation process here.
Saving a backup from the existing Data Center Operation server
1. Open the Webmin server configuration interface.
a. Type the Data Center Operation server's IP address in a Web browser.
b. On the Data Center Operation server's download page, click Server Configuration.
2. Log into Webmin using the user credentials created during the installation and in the left menu, select StruxureWare DC
Operation.
3. In the submenu, select Backup, and type a comment for the backup if you want to be able to differentiate more backups from
each other.
4. Click Backup now.
You have now created a backup in a local backup directory (/data/backup) on the same disk.
Copying the backup file to the new server
Open the Webmin server configuration interface.
In the left menu, select System>Upload and Download.
Click the Upload to server tab.
In Files to upload, browse to the location of your saved backup file.
Make sure the file format is: <name><yyyy-mm-dd><hh.mm>.tar.gz
5. In File or directory to upload to, select the location on the Data Center Operation server in which to save the file: /data/bac
kup.
1.
2.
3.
4.
Accessing the backup file on the new server
1.
06/15/2015
Page 34
1. Open StruxureWare Data Center Operation
2. In System Setup, select Migrate from StruxureWare Data Center Operation, and select to access the backup on the server.
After making sure that the data successfully migrated, you can decommission the old server.
See also
Upgrading from Previous Versions
Migrating a Cluster Environment to StruxureWare Data Center Operation
06/15/2015
Page 35
Migrating data from Emerson Aperture
You can migrate existing data from Emerson Aperture to StruxureWare Data Center Operation by following the instructions in the
migration wizard.
This feature is not available by default. Contact your local sales representative to purchase a software service that enables the feature.
Prerequisites
Before performing the migration, ensure StruxureWare Data Center Operation can access and retrieve data from the Aperture
database (it must be running, on the same network, no firewall between them, etc.).
To add spaces from Aperture to StruxureWare Data Center Operation (as rooms), you must have user rights in StruxureWare
Data Center Operation to edit the global location.
To add products from Aperture to the StruxureWare Data Center Operation genomes, you must have user rights to edit the
genome library.
Migrating
1. Select System Setup>Migrate from Emerson Aperture.
2. In the migration wizard, specify the Aperture database server credentials. Then follow the next steps:
Migrating spaces (rooms)
1. Select to migrate data center spaces.
2. Click Next to select which data center spaces (rooms) to migrate and if you want to migrate to the client or in batch mode.
Migrating to the client allows you to preview and cancel the migration before it is executed (recommended option). Migrating in
batch mode allows you to migrate large solutions in one step.
3. If you selected to migrate to the client, click Next to preview the changes and view or save a summary report before finishing the
wizard. If you selected to migrate in batch mode, go directly to the next step.
4. Click Finish to start the migration.
Migrating catalog
1. Select to migrate the product catalog.
2. Click Next to select to migrate the products currently in use in Aperture or all products.
3. Click Next to preview the changes before clicking Finish to start the migration.
06/15/2015
Page 36
See also
Emerson Aperture migration mapping overview
06/15/2015
Page 37
Migrating data from StruxureWare Data Center Expert
When upgrading (migrating) from a previous version of StruxureWare Data Center Operation running on a StruxureWare Data Center
Expert server, you must back up your current configuration, install the new server and clients, and migrate the previous data to the new
Data Center Operation server.
To migrate the previous configuration data to the Data Center Operation server, select System Setup>Migrate from StruxureWare
Central, and follow the instructions in the wizard.
NOTE: These instructions do not apply if you are migrating to a StruxureWare Data Center Operation cluster environment. Read
instructions on migrating to a cluster environment here.
See also
Backing up and Restoring Backup
06/15/2015
Page 38
Migrating a Cluster Environment to StruxureWare
Data Center Operation
If you are running StruxureWare Data Center Operation prior to version 7.3 in a clustered environment, you must migrate the existing
solution into a new installation of StruxureWare Data Center Operation version 7.3 or later.
First, remember to back up your solution in a remote location to be able to restore the backup after installing StruxureWare Data
Center Operation. The installation will destroy all data on the node. You will lose all data if you skip creating the backup.
1.
2.
3.
4.
5.
Stop users from accessing StruxureWare Data Center Operation stopcluster.
Save a backup of the current solution to a remote location.
Install on any of the nodes.
Restore the backup file on the node with the new installation.
Attach additional nodes to the cluster environment.
Stopping users from accessing StruxureWare Data Center Operation
1. Open the Webmin web interface.
a. Type the address of the master node in a Web browser.
b. On the server's download page, click Server Configuration.
2. Log on to Webmin using the user credentials created during the installation and in the left menu, select System>StruxureWare
Data Center Operation.
3. In the Status tab, select StruxureWare Data Center Operation and click Stop.
4. Repeat the above for all nodes in the cluster.
The cluster is now unavailable, and users cannot access StruxureWare Data Center Operation.
Backing up the current version to a remote location
Prerequisite: To enable saving the backup on your network, mount the folder in which to save the backup.
1. Open the Webmin web interface.
a. Type the address of the master node in a Web browser.
b. On the server's download page, click Server Configuration.
2. Log on to Webmin using the root credentials and in the left menu, select System>StruxureWare Data Center Operation.
3. In the Backup tab, specify the Backup directory by clicking ... and browsing to the mounted folder in which to save the backup.
4. Type a comment for the backup if you want to be able to differentiate the backups from each other.
5. Click Backup now to save a backup in the specified location.
Installing StruxureWare Data Center Operation on one of the nodes
See the entire installation process here.
Caution: Before installing the new version on the node, be sure you have a valid remote backup. The following installation process
will erase all data on the drive.
Restoring the backup on the node with the new installation
1. Open Webmin.
a. Type the address of the node with the new 7.3 installation.
b. On the server's download page, click Server Configuration.
c. Log on to Webmin using the credentials configured during the installation process.
2. In the left menu, select System>Upload and Download.
3. Click the Upload to server tab.
4. In Files to upload, browse to the location of your saved backup file.
Make sure the file format is: <name><yyyy-mm-dd><hh.mm>.tar.gz
5. In File or directory to upload to, select the location on the new Data Center Operation server in which to save the file: /data/
backup.
Alternatively:
6. Open Webmin.
7. In the left menu, select StruxureWare DC Operation>Restore.
8. Select an uploaded backup file in /data/backup and click Restore selected Backup.
The model data, user information and historical data have been migrated to the 7.3 server. You can verify that the migration was
successful by connecting the client to the new server.
Attaching additional nodes to the cluster
06/15/2015
Page 39
After verifying the data migration to the new server, decommission your old cluster and configure a new cluster.
When the new cluster is running, the migrated data on the first node will be transferred to the other nodes.
See also
Setting up a Clustered Environment
06/15/2015
Page 40
Initial Setup of StruxureWare Data Center Operation
PRO Pack
You must perform the installation and configuration process of the StruxureWare Data Center Operation: PRO Pack before you are able
to import it into Microsoft System Center Operations Manager. When you have set up a profile, you are ready to monitor the health of the
virtual machine hosts and implement the migration of impacted virtual machines to healthy hosts.
Requirement for PRO pack installation
.NET Framework version 4.
Installation and data retrieval configuration
The StruxureWare Data Center Operation: PRO Pack installer is available from a location provided by the support team. To locate the
telephone number for the support you need, visit Contact Us. Once you have run the installer, you need to configure the server
communication between the StruxureWare Data Center Operation server and the Virtual Machine Manager server, and then import the
StruxureWare Data Center Operation: PRO Pack into Microsoft System Center Operations Manager.
For information on installation, configuration, and general usage of Microsoft System Center Operations Manager and Microsoft Virtual
Machine Manager, refer to the Microsoft documentation.
StruxureWare Data Center Operation: PRO Pack is available for System Center Operations Manager 2007 R2 and Virtual Machine
Manager 2008 R2 as well as for System Center Operations Manager 2012 and R2 and Virtual Machine Manager 2012 and R2. These
versions of StruxureWare Data Center Operation: PRO Pack are available:
com.apcc.ISXO.PRO.2008R2.mp
com.apcc.ISXO.PRO.2012.mp
A complete configuration of StruxureWare Data Center Operation with StruxureWare Data Center Operation: Capacity license is
required (including association of monitored devices from StruxureWare Data Center Expert).
Data configuration in StruxureWare Data Center Operation
The StruxureWare Data Center Operation application must be populated with modeled data representing the physical enterprise
infrastructure. This includes objects representing coolers and the physical servers, their location in the data center rack layout, and their
power connections. Once the data center has been modeled with the correct inventory, virtual machine hosts can be associated to the
graphical objects in the layout representing the actual servers.
You can make the data available to StruxureWare Data Center Operation: PRO Pack through web services including a definition of the
polling interval. Read instructions on granting access to web service APIs here or read about the web service API here.
Note: If you are integrating with Virtual Machine Manager 2012 and R2, your setup may look a little different from the instructions
and images in this user assistance since these have been created for integration with Virtual Machine Manager 2008 R2.
See also
StruxureWare Data Center Operation: PRO Pack
Installing StruxureWare Data Center Operation PRO Pack
Configuring StruxureWare Data Center Operation PRO Pack
Configuring StruxureWare Data Center Operation PRO Pack Agent
06/15/2015
Page 41
Installing StruxureWare Data Center Operation PRO Pack
1. In a browser, open the download location provided by the support team. To locate the telephone number for the support you
need, visit Contact Us.
2. Download the StruxureWare Data Center Operation: PRO Pack .msi package to a location on your Microsoft System Center
Operations Manager server.
3. Run the installer from the selected location.
The following files are now installed to the specified location on your System Center Operations Manager server in a StruxureW
are Data Center Operation: PRO Pack folder, and StruxureWare Data Center Operation PRO Pack configuration is available
from Start > StruxureWare Data Center Operation PRO Pack > Configuration.
APC.ISXOCmdlet.dll
APC.ISXOCmdlet.InstallLog
APC.ISXOCmdlet.InstallState
com.apcc.ISXO.PRO.2008R2.mp or com.apcc.ISXO.PRO.2012.mp
InstallActions.dll
InstallActions.InstallState
IsxoMPConfig.exe
System.Management.Automation.dll
To complete the setup, you must configure the server communication between the StruxureWare Data Center Operation: PRO
Pack and Virtual Machine Manager servers and import the .mp file from the installed location into Microsoft System Center
Operations Manager.
If you want to uninstall the StruxureWare Data Center Operation: PRO Pack at any time, remove it from Microsoft System Center
Operations Manager before you run the uninstaller. After uninstalling the StruxureWare Data Center Operation: PRO Pack, the computer
must be rebooted.
Note: If you are integrating with Virtual Machine Manager 2012, your setup may look a little different from the instructions and
images in this user assistance since these have been created for integration with Virtual Machine Manager 2008 R2.
See also
Initial Setup of StruxureWare Data Center Operation PRO Pack
Configuring StruxureWare Data Center Operation PRO Pack
Configuring StruxureWare Data Center Operation PRO Pack Agent
06/15/2015
Page 42
Installing IT Optimize
Follow the below steps or watch this video tutorial.
Install IT Optimize
1. Download the ITO installer from the Data Center Operation server's download page.
a. Type the server's IP address in a Web browser.
b. Click to download IT Optimize for one of the supported operating systems.
The following instructions apply to Windows.
2. Browse to the location of the downloaded StruxureWareItOptimize-setup.zip file and extract the (3) files.
3. Double-click the StruxureWareItOptimize-setup.xxx file and follow the instructions in the wizard to install StruxureWare Data
Center IT Optimize server and Intel's DCM server.
The default installation directory is C:\Program Files\Schneider-Electric\ITOptimize.
The Web application port is the web services port used by StruxureWare Data Center Operation to communicate with
the StruxureWare Data Center IT Optimize server. This port number must match the one specified in the external
system configuration when configuring the system integration in StruxureWare Data Center Operation
The Windows user account will run the IT Optimize services on the StruxureWare Data Center IT Optimize server. It
must be a valid local or domain based Windows user with local administrator rights belonging to the "logon as a service"
role.
The default TCP port used by IT Optimize to access the embedded MySQL database is 3306.
4. Verify the installation and connectivity.
a. Browse to the ITO-Lite client, https://localhost:8090, to verify the installation was completed successfully.
In some facilities, port 8090 may be blocked by firewall or other network policies. If the IT Optimize web services port
was changed during installation, substitute 8090 with the new port address.
5. Browse to the DCM server GUI to test connectivity to the Intel DCM server, http://localhost:8688/DataCenterManager/, to test
connectivity to the Intel DCM server.
You now have DCM and IT Optimize services running on the Windows host.
See also
StruxureWare Data Center IT Optimize Server Requirements
StruxureWare Data Center IT Optimize client requirements
Upgrading IT Optimize
Configuring External System Integration
06/15/2015
Page 43
Upgrading IT Optimize
To upgrade to StruxureWare Data Center: IT Optimize, follow the regular installation procedure. The system will detect an existing
installation and ask if you want to upgrade.
Prerequisites:
1.
2.
3.
4.
5.
6.
Verify the StruxureWare Data Center IT Optimize server meets the minimum requirements.
Note that StruxureWare Data Center: IT Optimize also includes Intel's DCM server. Intel's DCM server must co-exist on the
same server as IT Optimize. Memory requirements for the server have increased to 4GB of memory. It cannot be accessed on a
remote server.
Create a backup of the existing StruxureWare Data Center: IT Optimize installation using the Webmin server configuration
interface to backup StruxureWare Data Center Operation Backing up and Restoring Backup, or using the ITO-lite client GUI, htt
ps://localhost:8090, to create a backup.
Download the ITO installer from the Data Center Operation server's download page.
a. Type the server's IP address in a Web browser.
b. Click to download IT Optimize for one of the supported operating systems.
The following instructions apply to Windows.
Browse to the location of the downloaded StruxureWareItOptimize-setup.zip file and extract the (3) files.
Double-click the StruxureWareItOptimize-setup.xxx file and follow the instructions in the wizard to install StruxureWare Data
Center IT Optimize server and Intel's DCM server.
Confirm that you want to upgrade.
Verify the installation and connectivity.
a. Browse to the ITO-Lite client, https://localhost:8090, to verify the installation was completed successfully.
In some facilities, port 8090 may be blocked by firewall or other network policies. If the IT Optimize web services port
was changed during installation, substitute 8090 with the new port address.
Browse to the DCM server GUI, http://localhost:8688/DataCenterManager/, to test connectivity to the Intel DCM server.
You have now upgraded DCM and StruxureWare Data Center: IT Optimize and have the services running on the Windows host.
See also
Installing IT Optimize
StruxureWare Data Center IT Optimize Server Requirements
06/15/2015
Page 44
Installing the StruxureWare Data Center Server
Access Server
Prerequisite: You must have a valid license to enable the module.
The StruxureWare Data Center Server Access server is available from the Data Center Operation server's download page. The server is
required for discovering servers that can be accessed remotely.
Note: The server download for StruxureWare Data Center: IT Optimize and StruxureWare Data Center: Server Access is identical.
If you already have one of the modules installed when you purchase the other, you do not need to download and install the server
for the other module. The licenses control the exposure of the StruxureWare Data Center: Server Access and/or StruxureWare Data
Center: IT Optimize functionality in the StruxureWare Data Center Operation client. If you purchase both modules together, the
name of the external system is StruxureWare Data Center: IT Optimize and Server Access.
1. Open a Web browser and type the address of your Data Center Operation server: https://yourservername.
2. On the Data Center Operation server's download page, click Download in the Server Access box and follow the instructions to
download the StruxureWare Data Center Server Access server.
See also
StruxureWare Data Center Operation: Server Access
Configuring the Server Access Module
Using the Server Access Module
06/15/2015
Page 45