USER GUIDE

Entuity® 16.5
Entuity Migration Guide

Entuity empowers service providers, systems integrators, and enterprises with

network control and predictability foundational to meeting any of today's
complex IT infrastructure challenges. Entuity provides a succinct suite of the
most important functionality for network management – inventory, fault, and
performance management – but presented in an easy to use, quick to deploy
format.

North America Headquarters EMEA Headquarters

4 Mount Royal Avenue 9a Devonshire Square
Suite 340 London,
Marlborough, MA 01752 EC2M 4YN
Tel: +1 508 357 6344 Tel: +44 (0)20 7444 4800
Fax: +1 508 357 6358 Fax: +44 (0)20 7444 4808

www.entuity.com 0000-0165-PD009 entuity_core_migration.rev1.fm

Entuity

Entuity

The Entuity product and its related documentation are protected by copyright and distributed under licenses restricting
use, copying, distribution and decompilation. Unless you have negotiated with Entuity specific terms and conditions
for using its product and associated documentation, such use shall be governed by Entuity's standard licence terms, a
copy of which is distributed with the product.

Entuity may make improvements and/or changes to the product(s) and/or program(s) described in this publication at
any time. These changes will be incorporated into new editions of the relevant publication.

Entuity®, SurePath®, Eye of the Storm®, InSight Center®, Green IT Perspective™, Network Delivery Perspective™ and Service
Delivery Perspective™ are registered trademarks of Entuity. All other trademarks are the property of their respective
owners.

License terms and conditions of use for Entuity and included third party software can be found on the Entuity server at
entuity_home/licenseTerms/. A listing of these third party trademarks, references and software included with Entuity
is available through its web UI.
Contents

1 Entuity 16.5 Migration Overview

Migration Prerequisites .............................................................................................5
Entuity 16.5 Licenses ...........................................................................................5
Entuity 16.5 Multi-Server Environments ...............................................................5
System Requirements and Shipped Software.....................................................6
Changes to Shipped Third Party Software Versions ................................... 6
JRE Upgrade Overrides SSL/TLS Certificates in the Default Keystore ....... 7
Entuity Web UI System Requirements .................................................................8
Entuity 16.5 Migration Path .......................................................................................8
Entuity Version and Patch Level...........................................................................8
Event Project Deployment....................................................................................9
Migrating to Entuity 16.5 ......................................................................................9

2 Entuity 16.5 Migration Guide Migration

Component Viewer (Java Client) Removed ...........................................................10
eyeclientrpc Removed ............................................................................................10
Entuity Configuration Management ........................................................................10
Pre Entuity 16.5 Scripts Obsolete ......................................................................10
Annotations on Views .............................................................................................11
View-level Streams ..................................................................................................11

3 Entuity 16.0 Migration

Map Migration and mapToView Utility ....................................................................13
mapToView Overview.........................................................................................13
Convert Maps with User Defined Connections..................................................14
Map Folder Structure .........................................................................................14
mapToView Parameters .....................................................................................15
Convert All of a User’s Maps ..............................................................................15
Convert a Named Map .......................................................................................15
Reassign Ownership of a User’s Maps ..............................................................18
Convert Shared Maps ........................................................................................18
Physical Connections .............................................................................................18
Entuity Integration for BMC Remedy AR System ...................................................18
Power over Ethernet Module Removed ..................................................................19

4 Views and User Access Control Migration

Entuity 16.5 Migration Guide 3

Entuity

Views Summary ......................................................................................................20

View Migration Preparation .....................................................................................22
View Migration Report .............................................................................................23
Migration Status: Shared non-ACL view ............................................................24
Migration Status: Special case: duplicated for each user .................................25
Migration Status: Private non-ACL view.............................................................25
Migration Status: Reference view.......................................................................25
Migration Status: Child of a reference view .......................................................25
Migration Status: Some groups with access do not have visibility ...................26
Migration Status: Ok...........................................................................................26
Check Entuity 16.0 View Migration .........................................................................26

Entuity 16.5 Migration Guide 4

1 Entuity 16.5 Migration Overview

This migration guide covers issues for users migrating from earlier versions of the Entuity
software to Entuity 16.5 GA (General Availability).
h

Before you upgrade to Entuity 16.5 you are strongly recommended to back up your current
! installation; the Entuity 16.5 upgrade process does not include a rollback facility.

Migration Prerequisites
Before installing Entuity 16.5 you should read its accompanying:
 Known Issues note which details open Issues and resolutions.
 Release Notes which identifies for you new, changed and removed functionality.

This Migration Guide, the Known Issues note and the Release Notes are all available from the
Entuity Customer Portal. If you require login credentials for the Customer Portal please
contact your Entuity representative for assistance.
You can find detailed install and configure instructions in the Entuity Getting Started Guide.
The Getting Started Guide and Release Notes are available at the root of the supplied Entuity
installation DVD or ISO image.
When migrating from Entuity 15.0 or earlier you should also read the Release Notes and
Migration Guide of intermediate releases, for example Entuity 16.0.

Entuity 16.5 Licenses

You must obtain from your Entuity representative an Entuity 16.5 license; licenses valid with
earlier versions of Entuity are not valid with Entuity 16.5.

Entuity 16.5 Multi-Server Environments

Entuity does not prevent you using different versions of Entuity to manage your network, and
where these servers run independently of each other, or you directly log onto them, you can
continue to use them without issue.
If during the migration process you have a consolidation server running a different version of
Entuity to one or more of its remote servers then you may not be able to access data on
those specific remote servers through the consolidation server. The implementation of views
in Entuity 16.5 is incompatible with the view implementation used with Entuity 15.0 and
earlier. The servers themselves can be accessed directly and do continue, for example, to
collect data. When both consolidation and remote servers are upgraded to Entuity 16.5 then
the remote servers would again be accessible through the consolidation server.

Entuity 16.5 Migration Guide 5

Entuity Migration Prerequisites

 If you require further guidance on migrating multiple Entuity servers to Entuity 16.5 please
contact your Entuity Support representative.

System Requirements and Shipped Software

Entuity 16.5 server is only certified for use with the 64-bit English edition variants of:
 Red Hat Enterprise Linux ES version 6
 Red Hat Enterprise Linux ES version 7
 Oracle Linux 6
 Windows Server 2008 R2
 Windows Server 2008 SP2
 Windows Server 2012
 Windows Server 2012 R2.

Table 1 Minimum Server Specifications provides a by component breakdown of the minimum

requirements for each of the device-port management bands:
 High, 1000 devices and 70000 ports.
 Intermediate, 800 devices and 50000 ports.
 Low, 400 devices and 25000 ports.
There is no change from Entuity 16.0 to Entuity 16.5.

Server Component Low Intermediate High

Minimum CPU Clock Speed 2.5 GHz 2.5 GHz 2.5 GHz
Intel Processor Family (or Xeon E3 Family Xeon 5000 Sequence Xeon E5 Family
equivalent)
Minimum No Cores 4 6 12
Windows Minimum Physical 6 GB 12 GB 24 GB
Memory
Linux Minimum Physical 8 GB 16 GB 32 GB
Memory
Disk Capacity 60 GB 90 GB 120 GB

Table 1 Minimum Server Specifications

Changes to Shipped Third Party Software Versions

Product Entuity 16.0 GA Entuity 16.5

Apache Tomcat 7.0.62 7.0.70
Apache HTTPD 2.4.12 2.4.23

Table 2 Third Party Software Versions

Entuity 16.5 Migration Guide 6

Entuity Migration Prerequisites

Product Entuity 16.0 GA Entuity 16.5

JRE 1.8.0_45 1.8.0_101
MariaDB Server 10.0.16 10.0.26
MariaDB Library (libmariadb) 2.1.0 2.3.0
MariaDB Java Client 1.1.8 1.2.3
OpenSSL 1.0.2a 1.0.2h

Table 2 Third Party Software Versions

JRE Upgrade Overrides SSL/TLS Certificates in the Default Keystore

This section is only relevant to you if you have implemented Entuity external authentication
using secure LDAPs.
The default keystore file entuity_home\install\JRE\lib\security\cacerts is
overwritten during the JRE upgrade. If you had imported certificates into that keystore then
those security certificates are lost.
To preserve your certificate setup you can export them before migrating to Entuity 16.5 and
import them after completing the migration. It is important that you export and then import all
of the security certificates in a certificate chain. A gap in the chain will cause Java to fail to
resolve a certificate to a trusted authority and in turn prevent users from logging on.

To retain imported SSL/TLS certificates:

1) Before starting the Entuity 16.5 upgrade export the security certificate chains using
entuity_home\install\JRE\bin\keytool. For example to export the dvlz certificate
enter:
keytool -keystore ..\lib\security\cacerts -export -alias dvlz -file
c:\certificates\dvlzcertfile.crt
Where:
 ..\lib\security\cacerts is the path to the keystore.
 dvlz is the user friendly name used to identify the certificate in the keystore.
 c:\certificates\dvlzcertfile.crt is the exported certificate file. The export
directory should exist before you export the certificate, keytool does not create it.

2) Enter the keystore password. The default keystore password is changeit although your
system administrator may have previously amended it.
3) After migrating to Entuity 16.5 import those security certificates using keytool. For
example to import the dvlz certificate enter:
keytool -keystore ..\lib\security\cacerts -import -alias dvlz -file
c:\certificates\dvlzcertfile.crt

4) Enter the keystore password. During the migration the JRE was updated and the keystore
password was reset to the default password, changeit.

Entuity 16.5 Migration Guide 7

Entuity Entuity 16.5 Migration Path

5) After you have imported all of the security certificates you must ensure they are picked up
by Apache Tomcat on the Entuity server. When Tomcat starts it updates its security
certificates. You do not have to stop Entuity, you only have to stop Tomcat (and it will
automatically restart). For example from entuity_home\bin enter:
stop tomcat

Entuity Web UI System Requirements

The Entuity web UI is certified for use with:
 Internet Explorer 10.0 or later
 Microsoft Edge v38.14393 (with EdgeHTML v14.14393)
 Firefox 38 ESR (Extended Support Release) or later
 Google Chrome 46 or later releases.

Users must enable their web browsers for both JavaScript, for example to allow the working
of the Entuity menu structure, and cookies, for example to maintain their login status.
The greatest call on the resources of a client machine is the map. An Entuity map is drawn on
the client machine, the more objects you have in the map the greater the resource required
to render it. To use maps with 500 or more objects the client machine should have:
 8GB or more of memory.
 The equivalent, or better, of an Intel 4 Cores i5 2.8 GHz processor.

Entuity 16.5 Migration Path

The certified migration paths to Entuity 16.5 are from:
 Entuity 15.0 Patch 4
 Entuity 15.5 Patch 3
 Entuity 16.0 Patch 2.
You can check the Entuity Support site for the latest patches.
h

If you are upgrading to Entuity 16.5 from a version of Entuity or patch level that is different to
! the certified migration path please contact Entuity Support for guidance.

Entuity Version and Patch Level

To check the current version and patch level of an Entuity server:
1) From the Entuity server click Help > About Entuity.
Entuity displays server details, including release version and patch details, for example:
Entuity 16.0 Patch (P01)

To install a patch to an Entuity server:

Entuity 16.5 Migration Guide 8

Entuity Entuity 16.5 Migration Path

1) From the Entuity customer support site download the patch file to a temporary location.
2) Stop the Entuity server and take a backup.
3) Apply the patch using the patch installer, entuity_home\install\installPatch, for
example:
installPatch c:\temp\ENTUITY_15.5.P01.WinNT.patch
4) After installing the patch run configure. The patch is only applied once configure
successfully completes.
5) Restart the Entuity server.

Event Project Deployment

Entuity 16.5 has an updated Event Management System (EMS) event project, that for
example includes:
 Remote server availability events and incidents.
 Virtual Machine events and incidents.
When you upgrade Entuity the new event project is available but it is only applied to the
installation when it is deployed.
If you have customized your current event project then use the Merge tool that is available
from the EMS Project History page. It identifies differences between two selected projects.
You can then choose how to resolve conflicts between the two. On completion it creates a
new event project ready for deployment (the two source projects are not changed).

Migrating to Entuity 16.5

Installing Entuity 16.5 is the same process whether migrating from Entuity 16.0 Patch 2 or an
earlier supported version of Entuity. When migrating from Entuity15.0 Patch 4 you only need
to install Entuity 16.5; you do not first install Entuity 16.0. Ensure you:
 Are migrating a server on the migration path. (See Entuity Version and Patch Level.)
 Read Chapter 2 - Entuity 16.5 Migration Guide Migration.
 Read Chapter 4 - Views and User Access Control Migration if migrating from Entuity 15.0
or earlier.
 Have an Entuity 16.5 license.

To migrate to Entuity 16.5:

1) Stop the Entuity server and take a backup.
2) Run install to install Entuity 16.5. You should add the new license before running
configure (by default the license is installed to entuity_home\etc).
3) Run configure. After install completes you are prompted to continue with the
installation process.
4) Restart the Entuity server.
5) Deploy the updated event project or apply the changes within it to your current project.

Entuity 16.5 Migration Guide 9

2 Entuity 16.5 Migration Guide Migration

This section details areas of Entuity 16.5 where there are changes in either its behavior or
management.

Component Viewer (Java Client) Removed

Component Viewer (Java Client) is removed in Entuity 16.5:
 Administrators should remove the Java installation used to run Component Viewer on
client workstations.
 Functionality delivered through the Java Client is now available through the Entuity 16.5
web UI, e.g. Ticker, Object Editor, Annotations. (See the Entuity 16.5 Release Notes.)
 Any user scripts which called Component Viewer must be updated to call the same
functionality available from the Entuity web UI.

eyeclientrpc Removed
eyeclientrpc was deprecated in Entuity 16.0 and is now removed. The Entuity RESTful
API is enhanced to support functionality which was previously delivered through
eyeclientrpc. Any scripts run through eyeclientrpc must be re-implemented using the
Entuity RESTful API.

Entuity Configuration Management

The Configuration Monitor module is removed from Entuity 16.5:
 Its functionality is now part of the Entuity Configuration Management module. Enable this
module to retain Configuration Monitor functionality.
 It is now licensed under the Entuity Configuration Management license.
 It retains a separate Tool Permission, Configuration Monitor, to allow users access to the
Configuration data, e.g. through th Configuration tabs in the web Explorer, the Check
Configuration Now context menu option.
Also note that the Configuration Monitor feature will now be made available to Ping Only and
Basic Managed devices, as well as Fully Managed devices.

Pre Entuity 16.5 Scripts Obsolete

Configuration Monitor functionality is now delivered through the Configuration Management
framework and uses Tasks and Steps to define the retrieval actions.
Scripts written for the Configuration Monitor module do not work in Entuity 16.5. Entuity 16.5
includes system tasks to replace the obsolete Configuration Monitor scripts:
 Retrieve Configuration (Cisco)

Entuity 16.5 Migration Guide 10

Entuity Annotations on Views

 Retrieve Configuration (Juniper)

 Retrieve Configuration (HP)
 Retrieve Configuration (Huawei)

During the upgrade:

 Entuity attempts to match old system configuration retrieval scripts with the appropriate,
new configuration retrieval tasks.
 Custom scripts will not be matched to tasks, and will be left blank.
f you have written or modified scripts you must convert them to the new tasks/steps
format. Contact Entuity Support for guidance on converting your scripts.
 Policy and exclusion file settings are retained.

Annotations on Views
In Entuity 16.5 annotations are managed through the web UI. Entuity 16.5:
 Migrates annotations associated with network objects to the new implementation.
 Discards any annotations associated with views. Entuity 16.5 does not support view
annotations.

View-level Streams
The existing view-level reachability stream (viewReachability) is replaced by a new stream
that reflects the toponode status of devices in the view (viewDeviceStatus), i.e. give a
breakdown of the number of devices in each of the possible status categories. The new
stream has these attributes:
 okDeviceCount
 adminDownDeviceCount
 uninitialisedDeviceCount
 unknownDeviceCount
 degradedDeviceCount
 downDeviceCount.

These new streams:

 Provide a historical record of the count of the devices in each of the possible states per
view
 Are displayed in a view’s Advanced tab.
 Available for use in Report Builder.

The AvailMonitor Low View Device Reachability event and its associated Device Reachability
threshold are unchanged. However how view device reachability is calculated is updated.
Entuity now raises this event when the combined number of devices responding to the ICMP

Entuity 16.5 Migration Guide 11

Entuity View-level Streams

ping and therefore reachable, set to Admin Down or in an Uninitialized state is, expressed as
a percentage, below the Device Reachability threshold for the view.
Any existing customer reports that use the old streams will not work and will need to be
updated.

Entuity 16.5 Migration Guide 12

3 Entuity 16.0 Migration

This section details migration issues raised with the release of Entuity 16.0. Entuity 16.0
changed the behavior of these functions:
 Map Migration and mapToView Utility
 Physical Connections
 Entuity Integration for BMC Remedy AR System
 Power over Ethernet Module Removed.

Map Migration and mapToView Utility

Maps in Entuity 16.0 are representation of views. Users must therefore consider which of
their current maps they want to create in Entuity 16.0 as views.
After migrating to Entuity 16.0 users can use the mapToView utility to convert old maps into
views. Users will be able to create a view for a selected map along with any sub-views to
match the map’s old hierarchy. This method will keep the map’s X and Y co-ordinates and
any background image and drill downs. Custom links will be removed.

mapToView Overview
mapToView creates a view and map definition for each specified map saved on the current
server. If a map contains components that are managed by remote Entuity servers it will also
create views on those remote servers (when using a valid user account with the Create Views
permission).
h

 When migrating maps on a central Entuity sever that include objects managed by remote
Entuity servers then the central and remote servers should be running Entuity 16.0.

You can control:

 Which maps are converted by specifying the owner of the map and specifying either the
name of a map or all of that user’s maps.
Public maps do not have an owner but can be converted in a similar way.
 The owner of the new view. The view owner must have the Create View permission.
h

 After the view is created the view owner or a member of the administrator user group can,
through the web UI, setup user group access.

If a map included:
 A drill-down (i.e. a group) to another map then mapToView would create a sub-view that
included the objects in that grouping.

Entuity 16.5 Migration Guide 13

Entuity Map Migration and mapToView Utility

 Entuity servers they are not included in the converted map. Entuity 16.0 maps do not
represent the Entuity server.
 Hypervisors then the associated VM Platforms are migrated to the view. A VM Platform
and all of its hypervisor are included to the map.
h

 Hypervisors may be dragged into maps. They do not appear in the navigation tree but are
listed in the View Summary and can be first dragged into Drop Box before dragging into a
map.

 Components from remote Entuity servers then mapToView will also create views on
those remote servers.
You should ensure the server on which you are running mapToView has access to those
remote servers and that the user account to which you are assigning view ownership
exists on all of the remote servers with the appropriate Create Views permission level.

Convert Maps with User Defined Connections

User Defined Connections are usually migrated to the new map. mapToView converts User
Defined Connections to physical connections, connecting endpoints at the port or when that
is not available at the device level.
mapToView does not convert User Defined Connections that include a group as an endpoint
on the link. However in Entuity 16.0 maps do represent links between sub-views (i.e. between
objects in the sub-views) and between a sub-view and an object on the map and if that were
the purpose of the User Defined Link it may appear as though the link was migrated.

Map Folder Structure

Pre-Entuity 16.0 maps were saved to sub-folders of entuity_home\maps. Entuity derived the
name of the sub-folder from the username of the map owner. Public maps did not have an
owner and instead were saved to the Shared folder.
Maps and the map folder structure are migrated to Entuity 16.0 so that they are available for
conversion to the new map implementation (they are not used by Entuity 16.0). When you
run mapToView you must specify the owner of the map as it:
 Identifies the folder in which the map, or maps, to be converted reside.
Public maps were saved to the Shared folder and are specified through a separate
parameter.
 May determine the owner of the migrated view (there is an option to specify a different
owner). The owner of the view must have the appropriate Create View permission level for
mapToView to create the view and map.

Users cannot globally convert all maps unless they write their own script from which to call
mapToView.

Entuity 16.5 Migration Guide 14

Entuity Map Migration and mapToView Utility

mapToView Parameters
The conversion utility mapToView is located in the /install directory of the Entuity server,
for example entuity_home/install.
To view the command line help run mapToView without any parameters:
maptoview
Usage: mapToView [OPTION].. [map]..

Parameters Description
-h --help Outputs to the command line a listing and brief description of the
mapToView parameters.
-u --user Converts map(s) owned by the user. If a user account name includes
spaces then enclose that name in double quotes, e.g. "James Smith".
-c --createAs The username of the Entuity user assigned ownership of the converted
map. This user account must be a member of the Administrator user
group or have the Create Views tool permission.
-p --password Password of the Entuity user assigned ownership of the converted map.
-s --shared Parameter used to identify maps that were shared, set to Public. They do
not have an owner.
-a --all Convert all maps owned by the specified owner (--user) or are public
(--shared).
-v --verbose Sends to the command line progress messages on map conversion.

Table 3 mapToView Parameters

Convert All of a User’s Maps

To convert all maps on the Entuity server that belong to one user and have that user retain
ownership of the map (and view) you must specify the user account and password. For
example to convert all admin’s maps enter:
mapToView -u admin -p admin -a

If the maps saved to a server contain content from multiple servers then you should run
mapToView:
 When the remote servers are available.
 And ensure the user account has the appropriate permission level on all servers.
mapToView would create views and sub-views on the remote servers.

Convert a Named Map

This example uses a map
 Created in Entuity 15.5.
 Named global user defined connections added.
 Created by the user admin.

Entuity 16.5 Migration Guide 15

Entuity Map Migration and mapToView Utility

 Which includes groups, Cloud_Close and Cloud_Far that are connected to each other
and c3560 using user defined links. User defined links are not migrated to Entuity 16.0
however these user defined links represent the connections that are available to the
devices within the two groups.

Figure 1 An Entuity 15.5 Map

To migrate a specific map to Entuity 16.0:

From the updated Entuity 16.0 server:
1) Navigate to entuity_home\install and enter:
mapToView -u admin -p admin "global user defined connections added"

mapToView reports the progress of the view generation. mapToView creates views and
sub-views on all of the connected servers to which the owner of the new map currently
has access and the permission to create a view.

Entuity 16.5 Migration Guide 16

Entuity Map Migration and mapToView Utility

Figure 2 Map with User Defined Connections

2) Login into the Entuity server and view the newly created view.
mapToView creates the Cloud_Close and Cloud_Far sub-views. The map shows links
between these sub-views because the devices within the views have connecting links.

Figure 3 Imported Map and View

Entuity 16.5 Migration Guide 17

Entuity Physical Connections

Reassign Ownership of a User’s Maps

You can set ownership of the converted maps (views) to a different user to that who originally
owned the map. For example to assign all of RILee’s maps to NanaToure enter:
mapToView -c NanaToure -p password -u RiLee -a

The password is for NanaToure’s user account, as NanaToure’s account is used to create
the view.

Convert Shared Maps

mapToView does not assign user groups to views. When converting Shared maps assign an
administrator as the owner and then - as with all other converted views - through the Entuity
web UI assign user group access. This example assigns to JamesSmith ownership of all
views converted from Public maps:
mapToView -c JamesSmith -p password -s -a

Physical Connections
In Entuity 16.0 the option to disable physical connections is removed. Entuity will migrate
physical connections that are disabled and will maintain their disabled status. If you edit
those connections then they are automatically enabled and you cannot subsequently disable
them.
You can check the current status of a connection through the Physical Connections page:
1) Click Administration > Inventory/Topology > Physical Connections.
2) Position the mouse over the column titles and from the context menu click Configure
Columns.
3) Move Enabled to the Show column and click OK.

Figure 4 View Migrated Disabled Connections

Entuity Integration for BMC Remedy AR System

When Entuity 16.0 is installed to machines running the Linux operating system the Entuity
Integration for BMC Remedy AR System uses a 64-bit version of arforward. Entuity also
include a 32-bit version, arforward_32. If you want to use the 32-bit version then you must

Entuity 16.5 Migration Guide 18

Entuity Power over Ethernet Module Removed

rename it to arforward. Both versions of arforward are found in entuity_home/integ/

Remedy/.
In Entuity 16.0 Windows installations continue to use a 32-bit version of arforward.

Power over Ethernet Module Removed

In Entuity 16.0 the Power over Ethernet (PoE) module is removed.
This includes the removal of:
 PoE module option from configure.
 The PoE and VLAN by Port and Device Report.
 Support for Ethernet Switch PoE and therefore after migration the loss of the per port PoE
metrics. If you require more information please contact Entuity Support.

Support for PoE Midspan Injectors is retained and is now included to Entuity by default.

Entuity 16.5 Migration Guide 19

4 Views and User Access Control Migration
h

Entuity 15.5 included a major enhancement to views. If you are upgrading from Entuity 15.0
! or earlier you must read the following sections on view migration. If you are migrating from
Entuity 15.5 then you are already using the new view mechanism, do not have to prepare for
view migration and can safely ignore this chapter.

Entuity 15.5 included a major enhancement of views, with the content of a view being the
same for all users accessing it, with new mechanisms for building views and controlling user
access to those views, updated view tool permissions and new view reports.
The upgrade process automatically migrates your current view structure, and user access to
content in those views, to the new view structure. Before upgrading to Entuity 16.0 users are
strongly advised to:
 Consult this section to understand and prepare for view migration.
 Review how you are currently using Entuity views and access permissions. The more you
have used ACL and Non-ACL views to control user access to content the more carefully
you will have to consider how to prepare your current server before migrating to Entuity
16.0.
 Ensure your current Entuity server is patched to the correct level.
A correctly patched server will include the View Migration report which is an important
tool in preparing your current install for migration to Entuity 16.0.
 Run through the migration in a test environment.
 Always take a full backup before migrating to Entuity 16.0.
 Contact your Entuity Support representative if you have any questions about, or require
guidance on, the migration process.

Views Summary
The key changes to views introduced in Entuity 15.5 are:
 All views now act as Access Control List (ACL) views, non-ACL views are not supported
and will be converted to ACL views during the migration process, therefore
 Different users accessing the same view will always see the same objects, whereas
previously visible view content would potentially have varied according to their Access
Control List setup.
 The distinction between the two view types and the terminology are dropped. The
padlock icon now represents a view that the current user cannot edit.
 Reference views are not available in Entuity 16.0. The new base view facility can deliver
similar functionality.
A reference view was really a different path to the same view. For example if view1 had
the sub-view2 and viewA was then assigned a sub-view that was a reference to

Entuity 16.5 Migration Guide 20

Entuity Views Summary

sub-view2, you had not increased the number of views on your server. Instead there were
now two paths to the same sub-view, view1>sub-view2 and viewA>sub-view2.
 The option to make a view Visible or Not Visible to a user group is removed. Previously an
administrator may have assigned views to a user, so they had access to objects in those
views, but not made the views themselves visible.
On migration these Not Visible views are made visible.
 A new All Objects view:
 Is a system view with the owner system.
 Contains all objects under management of the Entuity server.
 By default can only be accessed by members of the administrators user group.
Administrators can assign access and edit permissions to other user groups. Those
non administrator users with edit permission to the All Objects view can only edit it,
i.e. assign access to other user groups, if they have the Share View permission.
 Contains all services under management of the Entuity server.
 Is always displayed at the top of the Explorer tree and at the top of any other listing of
views in Entuity.
 Has the internal view id of 1, which was previously the My Network view id. If you have
used this id, for example when specifying Flex Reports or when forwarding events and
incidents then you may see a change in behavior depending upon the permissions of
the associated user account. When used with a user that is a member of the
administrators user group there will be no change in behavior however when used
with non-administrators the view would now include all objects whereas previously it
would only have included objects to which the user had access.
 A revised implementation of the My Network view, where each user has their own My
Network view:
 With their username appended to it and enclosed in brackets, e.g. My Network
(jamessmith), My Network (nanatoure).
 That contains all objects that a user can view. It does not determine what a user can
view, i.e. it is a union of all other views associated to the user and therefore its content
is not directly editable.
 That is sorted towards the top of any view listing in Entuity but below the All Objects
view. If an administrator is viewing all private views then My Network views are sorted
alphabetically.
 That is now a Private view. It is only accessible to that user (and system administrators
if they set their user preference to show private views).
 Which cannot be used as a base view because the contents of a My Network view can
change dynamically and would create cyclic dependencies since a user's My Network
view is calculated by making every other view of that user a base view for it.
 New concept of base views. A base view is one on which another view is based. All views
apart from My Network views can act as a base view, however Entuity will prevent circular
dependencies.

Entuity 16.5 Migration Guide 21

Entuity View Migration Preparation

 A view can be based on more than one view and users can select whether the content of
the new view is derived from the union or intersection of objects in the selected views:
 Union, results in a view that contains all of the objects in the selected views.
 Intersection, results in a view that contains only the objects that are in all of the
selected views.
If you alter the contents of a base view or remove a view from a union/intersection
definition this alters the resultant view. Entuity does warn when deleting a view that it may
impact other views, it does not warn if you edit a view.
 A user’s default view is now a user preference setting. Factory default is the user’s My
Network view.
 A user with access to a Parent view can now access all of the Child views implicitly,
whether they have explicitly been given access or not.
 A user with access to a Child view will now see the Parent view in the Explorer tree, but
depending upon their permissions may not see content in that view. These parent views
allow users to navigate to the child view to which they do have access.
 When Explorer is in Consolidation mode a new All Servers icon in the tree:
 Indicates servers’ views are consolidated.
 Provides a base from which to create new top level views and to move or copy
existing sub-views back to the top level (when in consolidated mode).
 Provides a method for clearing the current selection (which is why it is available when
there is only a single server) which is not otherwise easy to do, but sometimes
desirable.
 Removes the requirement for the Create new top level view icon, so it is removed.
 Green It Perspective used the My Network view, which varied depending upon the user
running the perspective. In Entuity 16.0 the Green IT Perspective uses the All Objects
view and is therefore consistent for all users.

View Migration Preparation

Entuity 15.5 introduced major changes to how views operate and how user access to objects
in those views is controlled. Before attempting to upgrade to Entuity 16.0 you should always
run the View Migration report which will identify the migration status of every view on a
server. However you can expect that where you configured view and user access control by:
 Only using ACL views, or assigned all users access to all managed objects, then
automatic view migration would result in users having the same access permissions after
migration as before migration.
 Using hidden ACL views to assign access permissions to users and using non-ACL views
for users to access managed objects then after migration:
 All Non-ACL views would have been converted to ACL views.
 All previously hidden ACL views would be visible.

Entuity 16.5 Migration Guide 22

Entuity View Migration Report

Users that previously might only have had access to a subset of objects in shared
Non-ACL views would now have access to all objects in those views (the objects in the
migrated view being determined by the permissions of the view owner).
Reference views create alternative view paths to the same view. Reference views are not
supported in Entuity 16.0 so the Entuity 16.0 migration:
 Converts each reference view to a sub-view that uses the original referenced view as its
base to determine its contents. Changes in the base view therefore automatically appear
in the new migrated view.
 Does not migrate sub-views of the referenced view. If you require the same view hierarchy
then before you migrate to Entuity 16.0 create a copy of the referenced view and its view
hierarchy.

View Migration Report

You run the View Migration report on your current Entuity installation to check its view setup
for issues that may cause the migrated view and user access control setup to behave
significantly differently than before. The report comprises of:
 A first page that details the type of checks made and suggested potential actions for each
state.
 Subsequent pages that report the results of those checks against each view on the
server.

To run the View Migration report:

1) Click Reports.
2) Click Administrative Reports. Entuity displays the list of available reports.
3) Click View Migration.
4) Select the Output Format, e.g. HTML, and then click Run.

Entuity 16.5 Migration Guide 23

Entuity View Migration Report

Figure 5 View Migration Report

The Migration Status of each view indicates the type of issue discovered, you can refer to the
first page of the report (or the following sections) for suggested actions to resolve each issue.
You can:
 Run the report as often as is required.
 Access the generated reports after upgrade to Entuity 16.0 through the server file
structure.
 Not run the report after migrating to Entuity 16.0, however Entuity 16.0 does include a
report for you to check your view and user access control setup, the View Permissions
and User Access Control report.

Migration Status: Shared non-ACL view

A shared non-ACL view would show different content according to the access permissions of
the user. After migration to Entuity 16.0 all users with access to the view would now have
access to all objects in that view; the content of a shared non-ACL view after migration will
depend upon the owner of that view. If this is acceptable then no action is required. If this is
not acceptable then before you upgrade you can:
 Delete the view.
 Remove access to all non-administrator groups.

Entuity 16.5 Migration Guide 24

Entuity View Migration Report

 Modify the view contents to only contain those objects that you wish to grant access to.

Migration Status: Special case: duplicated for each user

Pre Entuity 15.5 each server has one My Network view, although the objects a user can
access is dependent upon their access permissions. In Entuity 16.0 each user has their own
My Network view that only contains the managed objects for which they have permission to
access.
Report schedules that run against the My Network view will be migrated to the My Network
view of the user that created the schedule. If you do not want the report schedules to run
against a user's private My Network view you should do one of the following:
 Edit the report schedule and change the view it runs against.
 Delete the report schedule.
 Suspend the report schedule and decide what action to take after upgrading.

Migration Status: Private non-ACL view

These views are only accessible by their owner and members of the administrators group.
They will be converted to have the same content as their owner currently sees in them. If this
is not acceptable then you may wish to do one of the following prior to upgrade:
 Delete the view.
 Change the view to be an ACL view. This will give the owner access to all objects within it.

Migration Status: Reference view

Reference views create alternative view paths to a view. Reference views are not supported in
Entuity 16.0. Entuity 16.0:
 Migrates each reference view to a sub-view that uses the original referenced view as its
base to determine its contents. Changes in the base view therefore automatically appear
in the new migrated view.
 Does not migrate sub-views of the referenced view. If you require the same view hierarchy
then before you migrate to Entuity 16.0 create a copy of the referenced view and its view
hierarchy.

Migration Status: Child of a reference view

Entuity 16.0 view migration only migrates top-level reference views, it does not migrate any
sub-views of a reference view. These views are still available but only through the original
(referenced) view path.
Where the child of a reference view is used, for example in report schedules, then the
schedule will remain assigned to that view but the view path will be amended from that using
the reference view to that using the original view.
If you wish to maintain the hierarchy that currently exists under a reference view you will need
to create a copy of the referenced view instead of a reference to it.

Entuity 16.5 Migration Guide 25

Entuity Check Entuity 16.0 View Migration

Migration Status: Some groups with access do not have visibility

This is an ACL view where one or more of the user groups that have read access to it do not
have visibility on the view itself. This means members of those groups have access to the
contents of this view, but will not see this view in their view hierarchy. The ability to have read
access but no visibility is not supported in Entuity 16.0.
After migration some users may see this view in their view hierarchy when they did not see it
before. If this is not acceptable then you can do one of the following prior to upgrade:
 Delete the view.
 Change the user groups that have access to the view.
 Change the users that are members of the user groups that have access to the view.

After upgrading to Entuity 16.0 through their preferences settings users can choose to hide
any combination of views they want to.

Migration Status: Ok
View will migrate without significant change of functionality. No action is required prior to
upgrade.

Check Entuity 16.0 View Migration

When migrating from a pre Entuity 15.5 installation then on running Entuity 16.0 install
users are warned that the view implementation is revised in Entuity 16.0 and reminded again
to consult this migration guide.

Entuity 16.5 Migration Guide 26

Entuity Check Entuity 16.0 View Migration

Figure 6 Install Migration Warning

After migrating to Entuity 16.0 you can run the View Permissions and User Access Control
report to verify the view and user access control permissions have been migrated as you
expected. You can run the report against one or more Entuity servers. The report comprises
of a series of optional tables that detail user and user group access to views and devices that
you can select to include to the report:
 Show group membership, includes to the report a table that lists for each user, by
Entuity server, the user groups of which they are members.
 Show group view access, includes to the report a table that lists for each view, by
Entuity server, the devices available through that view.
 Show device user access membership, includes to the report a table that lists for each
device, by Entuity server, the users that have access.
 Show device access membership, includes to the report a table that lists for each
device, by Entuity server, the users that have access.
 Show user’s tool permissions, includes to the report a table that lists for each user
group, by Entuity server, the tools to which they have access.

To run the View Permissions and User Access Control report:

1) Click Reports.
2) Click Administrative Reports. Entuity displays the list of available reports.
3) Click View Permissions and User Access Control.

Entuity 16.5 Migration Guide 27

Entuity Check Entuity 16.0 View Migration

4) Set the report options and run the report.

Entuity 16.5 Migration Guide 28