Ellipse 8 Installation Guide

Ellipse 8 Installation Guide

Contents
Ellipse 8 Installation Guide 2
Commercial In Confidence 4
Preface 5
Summary information 5
Confidentiality 5
Document Control 5
Who should use this guide? 5
How to use this guide 5
Purpose 5
Scope 5
Update Notes 5
Installation Definitions 6
Introduction 7
Appliance Networking Configuration and Setup 9
Ellipse 8 Appliance Networking Setup 10
Ehcache configuration 12
Database Preparation 13
Ellipse 8 database creation 13
Appliance Creation - Fresh install 14
Creating the Appliance Manager 14
Data Initialisation 18
Loading Cold Start Data (new customers) 18
To login an Ellipse instance with coldstart data 18
Secure Sockets Layer (SSL) Certificates 20
Create Ellipse 8 Environments 21
Install Ellipse 8 Environments 21
Access the Environment 22
Secure WebDAV Connectivity 24
GIT Customer Software Repository Override 25
AD Domain Administrator CRT distribution 25
Local Administrator CRT distribution 25
Map Network Drive 25
Monitor Installation of appliance and environments 27
Monitor appliance creation 27
Monitor Ellipse environment creation 27
Appendix 29
Creating an Oracle Ellipse Database 29
Database Parameter recommendations 30
Password issue 30
Fix for password expiry Oracle 11g 30
Workaround 30
Ellipse 8 VIP Tablespace 30
Creating a MS SQL Server Ellipse Database 31
 Create Schema SQL 32
Ellipse support for Microsoft's SQL Server 2014 33
In SQL Server 33
Installation Information Collector 34
Virtualisation and Installation Check List Form 35
Commercial In Confidence
Copyright 2016 ABB
All Rights Reserved
Confidential and Proprietary
Legal Disclaimer
The product described in this documentation may be connected to, and/or communicate information and data via, a network
interface, which should be connected to a secure network. It is your sole responsibility to ensure a secure connection to the
network and to establish and maintain appropriate measures (such as but not limited to the installation of firewalls, application
of authentication measures, encryption of data, installation of antivirus programs, etc.) to protect the product, the network,
your systems, and the interface against any kind of security breach, unauthorised access, interference, intrusion, leakage,
damage, or corruption or theft of data. We are not liable for damages or losses related to any such security breach,
unauthorised access, interference, intrusion, leakage, damage, or corruption or theft of data.
Preface
The Ellipse 8 Installation Guide is part of the Ellipse Technical Documentation Library. This documentation library comprises a
number of guides that provide information for the implementation, administration, and operation of the Ellipse application in a
networked environment.

Summary information

Confidentiality
The contents of this document are confidential between ABB and its customers. The parties must keep the information herein
confidential at all times and not disclose it, or permit it to be disclosed, to any third party, apart from any of their officers,
employees, agents or advisers who have a specific need to access the information herein and have agreed to be bound by the
terms of confidentiality.

Document Control
Once the project is completed or terminated, this document will revert to an uncontrolled document status. No further advice
will be provided, and each recipient may either destroy the document or mark it as obsolete and retain it for future personal
reference.
All copies of this document will be issued electronically.

Who should use this guide?

This guide provides information on Ellipse 8 installation for Ellipse Technical Consultants.

How to use this guide

This guide describes:

• The installation tools

• The activities related to installation, post installation and installation support
This guide does not address Ellipse architecture and deployment, nor does it address operational activities. Separate guides
address these topics.

Purpose
This document is a guide to Technical Consultants involved with installing Ellipse 8.

Scope
This section indicates what is included and also what is not included in the document.
The following is in scope and covered in a section of this document.

• Creating an application server environment using KVM virtualisation

• The steps for installing the appliance manager (VEAM) as a prerequisite to installing Ellipse 8 environments
• What is needed prior to installation
• What is required to be completed after installation so that you can proceed to use Ellipse 8
The following is not covered in this document as it is out of scope.

• Testing any connectivity, network or database

• Database activities that would be required to be performed before starting Ellipse 8:

• Creating a database
• Setting up a database
• Populating a database
• Maintaining and supporting the Ellipse environment.

Update Notes
Please refer to the Ellipse 'Update Notes' to check if there is information that applies to your release or upgrade
path. All Update Notes versions have a summary table that covers notes up to that release. Detailed information will only be
provided in a particular version. This version will be refered to in the Summary Table.
Installation Definitions
The following table introduces terminology needed to understand the Ellipse Installation.

Term Definition
Appliance The infrastructure that supports the VEAM, Monitoring Server the Central HTTP Server
IP address Internet Protocol address; a numerical label assigned to each device (for example: computer, printer)
participating in a computer network.
Scalable unit The scalable unit contains a pre-package environment that includes all the necessary components
required to set up and run Ellipse 8, excluding the database server.
Instance Example: Ellipse production
NIC Network Interface Controller
SAN Storage Array Network. SANs primarily are used to make storage devices (such as disk arrays)
accessible to servers.
Kickstart The Red Hat Kickstart installation method is used primarily (but not exclusively) by the Oracle Linux
operating system to automatically perform unattended operating system installation and configuration.
A Kickstart file contains a series of options, to be passed to the Anaconda installer that describes how to
set up the system. It may also include custom scripts to be run before or after the installation.
Oracle Linux (OL) An operating system based on Red Hat Enterprise Linux.
VEAM Ellipse Appliance Manager, the application for managing Ellipse Environments.

Table: Installation terminology and definitions

Introduction
This document provides instructions for the preparation and installation of Ellipse 8.

Figure: overview of install to upgrade

Once Ellipse 8 is installed refer to the following documentation:

Ellipse 8 Operations guide Used to manage, maintain and support Ellipse 8 environments and application servers
Ellipse 8 Customisation and Outlines tools that support integration applications and customisations through API's
Personalisation Guide

The following figure outlines the key tasks linked to each of the activities.

Activities associated with an Ellipse 8 installation

Table: Activities description

Activity Comment
Prepare Prior to any Ellipse 8 installation onto the Ellipse 8 scalable unit there is the requirement to:

• Create a DVD with Oracle Linux version 7.2

• Purchase the physical server
• Connect the physical server to the network
• Ensure that the SAN disk is allocated (if applicable)
• Ensure the latest firmware is applied to Network/BIOS/RAID/ and any others
• Ensure a customer representative has ready access to all details required for the Appliance Manager
(VEAM) parameters
• Ensure that there is an authentication server (AD or LDAP) available prior to the installation. If
required can be configured with no authority.
Database Create the database with appropriate schema and tablespaces for Ellipse 8
Creation
Install Install Ellipse 8 components onto the application server environment and activate the Ellipse 8 system.
This means the Ellipse Login Page displaying, authentication working, the Ellipse Menus working and Load
Balancer working.
Post install Once an environment is created it is started immediately.
Refer to the operations guide or developers guide for information and activities associated with managing,
maintaining and supporting the Ellipse 8 environment, including the application servers.

Note
ABB does not supply the OL distribution for Ellipse builds. This is a customers' responsibility. See the Architecture
Deployment guide.
Appliance Networking Configuration and Setup
The Ellipse 8 Appliance provides advanced network configuration options which enable the creation of clustered and
non-clustered production Appliance deployments. Customers can specify:

1. A network interface bonding configuration, enabling customers to take advantage of multiple physical network cards to
create redundancy in the network configuration of each Appliance
2. The corporate IP address (and other relevant information) of the Appliance host
3. Any private network address range to be used by the Appliance when creating virtual servers for environments
4. An appliance number for when an Appliance is required to operate as a member of a cluster of appliances
accommodating the same logical environment (eg. production environment spread over 3 physical Appliance hosts)
A brief description of the three key Appliance networking features follows:
Bonded Appliance Network Interfaces
Bonded networking enables customers to logically combine multiple physical ethernet ports on an Appliance to create a
single logical network interface. Customers do this to provide redundancy at the network configuration level of an
appliance. It is an important step to make an Appliance highly available.
From Ellipse 8.3.7 onwards, production appliances support dual bonded networks, representing a minimum of 4 physical
Ethernet interfaces in dual Ethernet bond configuration. The first bonded network is required to enable inbound traffic to
the host on its public IP address. The second network bond is required to enable cross appliance communications.
Bridged Appliance Networking
Bridged appliance networking is a configuration option that enables two or more Appliances to communicate with each
other. This feature works on the basis that link level (OSA level 2) networking, typically handled by switches and network
interface cards ensures that the private networks stood up and managed by each appliance are routable to/from each
other as long as they are part of the same VLAN. This VLAN should be private to the Appliances only for reasons of
security and isolation from from other similar private network ranges in use in the organisation.
Private Network Reservation
For Ellipse 8.3.6 and below, the private subnet range that the appliance utilised was fixed as 192.168.1.0/2, representing a
Class C network in networking parlance. This approach had the potential to be problematic because some customers may
have existing networks in the same range. To solve this problem, flexibility was added to enable customers to specify their
own private network. In practical terms, this translates to the IP address that must be used to login to a virtual server from
the host (as only the host can see servers in the private network).

Non clustered, non production environment

The Appliance implementation of Bonding uses Bond Mode 6 (balance-alb). This bonding mode provides redundancy and load
balancing. This bond mode does not require any special switch port configuration.
 Clustered, Production environment

Benefits of using private networks within an appliance:

1. Project managers can have systems when they want them and do not have to wait for networking teams, virtualisation
teams and other technical disciplines. Database issues are resolved with some basic up-front planning and preparation.
2. New environments can be created in under 30 mins instead of days or weeks.
3. Increased security because corporate systems are not directly accessible to users and other systems unless through
approved protocols.
Things to be aware of:

1. The Appliance firewall will prevent external users and/or applications from communicating directly with virtual servers
“inside” the appliance using non-HTTP protocols.
2. The Appliance virtual servers and associated applications rely on the Command and Control server to route HTTP traffic
based on the URL being requested by the client.
The history and future of Ellipse 8 Appliance networking (for reference purposes only)

Ellipse 8 Appliance Networking Setup

1. Physical cabling of the server
• Non-clustered Appliance (eg. non production)

• 2 cables total
• 2 interfaces cabled to switch ports mapped to the same VLAN
• Switch ports configured as "access" mode
• Clustered (eg. production)

• 4 cables total
• 2 interfaces cabled to switch ports on the same VLAN (routable within corporate network)
• 2 interfaces cabled switch ports on private VLAN (not routable within the corporate network)
• You should obtain console (local or remote) access to the server to ensure that you fix any errors/issues should the
network interface become unavailable.
2. General recommendations:

• The above physical cabling recommendations assume the specification of network bonding configuration during
Appliance installation. Network bonding is a an Appliance feature that enables customers to "bond" or join physical
network interfaces to create a single, redundant (high availability) network configuration.
• Customer should aim to split physical network interfaces for the private and corporate (public) networks between PCI
and onboard network interfaces for maximum redundancy.
• For clustered appliance configurations, customers will need to reserve an IP range, preferably class C, that is NOT
already in use by the customer to ensure no routing loops are created. If customers select a private network range
that conflicts with an existing range in use with the organisation, a situation can arise where packets originating
from the existing corporate network and delivered to the Appliance will be unable to leave the appliance because the
appliance itself will believe the packet is already in the right private network.
 • It is important to understand that the private network range selected for use by the Appliance does NOT have to be
from the currently allocated and in-use corporate private network range. The private network range to be used by
the appliance can be ANY range in the list of ranges that the Internet Engineering Task Force (IETF) , through the
Internet Assigned Numbers Authority (IANA) has reserved for private networks, as published in RFC 1918. For
example, if in the customer organisation today they have servers on a 172.16.x.x range there is no requirement for
the Appliance to allocate IP address in this range. Any network range in the follow table will work as long as it is NOT
already in use somewhere within the organisation.
Largest CIDR
RFC1918 Number of Classful block (subnet Host id Mask
name IP address range addresses description mask) size bits
24-bit block 10.0.0.0 - 16,777,216 single class A 10.0.0.0/8 24 bits 8 bits
10.255.255.255 network (255.0.0.0)
20-bit block 172.16.0.0 - 1,048,576 16 contiguous class 172.16.0.0/12 20 bits 12 bits
172.31.255.255 B network (255.240.0.0)
16-bit block 192.168.0.0 - 65,536 256 contiguous 192.168.0.0/16 16 bits 16 bits
192.168.255.255 class C network (255.255.0.0)

Reference: http://en.wikipedia.org/wiki/Private_network
Ehcache configuration
Each application server in a given environment shares cache information with other application servers. To do this each
application server has a Cache Manager component that must be configured to communicate with other Cache Managers on a
"multicast" ip address and port common to each application server in the same environment whilst remaining unique across
different environments. Following re-installation via the Ellipse installation binary (DIY) or re-deployment via VEAM, the Ellipse
installation process will place a configuration file, named ehcache.xml on the filesystem.
The following (example only) table illustrates a typical multiple environment deployment and possible associated Ehcache
configuration multicast group IP and multicast port values to ensure successful operation:

Application
Create Environment servers per Multicast IP Multicast Example
order name environment Address Port Comment OK?
1 Development 2 (1 x online, 230.0.0.1 40001 Assume initial OK
environment so no
1 x batch)
conflicts
2 Test 2 (1 x online, 1 x 230.0.0.1 41001 Same IP as OK
batch) Development but
different port
3 Training 2 (1 x online, 1 x 230.0.0.2 40001 Different IP to OK
batch) Development and
Test
4 Sandbox 1 2 (1 x online, 1 x 230.0.0.2 40002 Same IP as Training OK
batch) but different port
5 Sandbox 3 (2 x online, 1 x 230.0.0.1 41001 Same IP as NOT OK
batch) Development and
Test AND same port
as Test
6 Production 7 (6 x online, 1 x 230.10.0.230 42001 Should never be OK
batch) using ABB supplied
defaults, IP and port
are unique

Note
1. The assignment of multicast group IP address and port are arbitrary within the range of addresses reserved for IP
multi-casting. This range includes the addresses from 224.0.0.0 to 239.255.255.255. Customers are advised to take
care to avoid assigning multicast IP addresses that conflict with the well known address registered with the Internet
Assigned Numbers Authority (IANA).
2. This manual procedure is a required step for VEAM customers until a new version which fully automates the process
has been released. In practical terms, this means customers should use VEAM to do the deployments and then they
will need to shutdown the app servers to perform the reconfiguration of ehcache.xml followed by a restart of the
application server.
3. ABB recommends changing the default multicast group IP address and or multicast port values that are provided in
the default ehcache.xml initially created by the installation process.
Database Preparation
Ellipse 8 supports Oracle 11g and 12c, SQL Server 2014 and Azure SQL databases.
Database product software installation and patching is assumed to be completed by the customer, directly or indirectly via an
appropriately skill person or organisation.
On completeion of the default Database product installation and associated feature enablement, customers are asked to follow
ABB provided instructions regarding the creation of the pre-requisite database roles, permissions, tablespaces and schemas to
enable the Appliance to create working application environments.
Initial installation of an Ellipse Appliance does not have any interaction with any external Database product therefore no
Database environment is required at the time of Appliance installation. Databases schemas for Ellipse, Ellipse Datamarts,
Integration Platform are only required at the time of Ellipse environment creation.

Once the database has been created:

-- Verify Optimizer Stats job has been disabled exec dbms_auto_task_admin.disable('auto optimizer stats
collection',NULL,NULL);
Disable default gather statistics job exec dbms_scheduler.disable('BSLN_MAINTAIN_STATS_JOB', FALSE);
Once for the Schema (Set the default):
-- Ensure histograms will not be collected for the ELLIPSE user
exec dbms_stats.set_schema_prefs ('ELLIPSE','METHOD_OPT','FOR ALL COLUMNS SIZE 1');
Run after large data loads or part of weekly maintenance of the database
-- Execute "gather stats" job.
exec sys.dbms_stats.gather_schema_stats(ownname => 'ELLIPSE', estimate_percent =>
dbms_stats.auto_sample_size, options => 'GATHER', method_opt => 'for all columns size 1', degree => 40, cascade
=> TRUE);

Ellipse 8 database creation

The Ellipse 8 database needs to be created before you can create an Ellipse 8 "environment" using VEAM.
An Ellipse database can be created using Oracle Database or Microsoft SQL Server. Please refer to the following appendices as
appropriate to the Database to be created:

• Creating an Oracle Ellipse Database

• Creating a MS SQL Server Ellipse Database
Database Setup for Performance
The following table summarises the key actions, described above but repeated here, following each and every database
preparation related activity. These actions are important to ensuring that Oracle is configured in a way that ABB recommends
for optimal performance of Ellipse:

After... do/check this.... with this....

On Database creation Verify Optimizer Stats job has
been disabled Disable default
gather statistics job
Schema creation Ensure histograms will not be
collected for the ELLIPSE user
Large data Execute "gather stats" job
loads/purges
exec dbms_auto_task_admin.disable('auto optimizer stats
collection',NULL,NULL); exec
dbms_scheduler.disable('BSLN_MAINTAIN_STATS_JOB', FALSE);
exec dbms_stats.set_schema_prefs
('ELLIPSE','METHOD_OPT','FOR ALL COLUMNS SIZE 1');
exec sys.dbms_stats.gather_schema_stats(ownname =>
'ELLIPSE',
estimate_percent => dbms_stats.auto_sample_size,
options => 'GATHER', method_opt => 'for all columns
size 1', degree => 40, cascade => TRUE);
Appliance Creation - Fresh install
This section of the document provides the instructions for creating the Appliance manager. Ellipse Scalable Unit environments
are created on the ABB Appliance base.
Assumptions:

• Intel hardware meeting the minimum specification for an Ellipse Appliance

• The installation software has been transferred to a USB (thumb) drive
• An Oracle 7.2 DVD is mounted (physical or virtual)
• Once the host, Command and Control (CmdCtl) server are created, the Virtual Enterprise Appliance Manager (VEAM) is
used to create Ellipse 8 instances.

Note
The Documentation is included on the DVD.

Creating the Appliance Manager

These steps create the base appliance on the physical server; install the Appliance Manager (VEAM) as well as the shared HTTP
web load balancer.
Once the Appliance Manager has been created all other activities related to creating and managing the Ellipse 8 scalable units
are done through the Appliance Manager (VEAM) interface.

Note
Please ask the local system administrator for assistance when following these steps on the customer's hardware. Due to
manufacturer's different implementations, these steps will vary.

Steps

1. Gather the connectivity information required for creating the Appliance Manager.
Parameter How / why used
Appliance host IMM/RAC Access to remote IMM / remote admin
IP address console
RAC login credentials Required for IMM/RAC access
Appliance number Unique identifier for each mewmber
of Appliance cluster.
Appliance fully qualified Provide an absolute fully qualified
domain name domain name
Appliance host IP address IP address to assign to the Appliance
Appliance netmask Subnet mask associated with the
Appliance host network
Appliance default Default gateway asspociated with the
gateway Appliance
Appliance network device Override for the default ethernet
device (eth0)
Appliance Interface Use if bonding multiple physical
bonding devices
DNS server Numbered list of existing corporate
DNS servers that the Appliance shall
forward DNS requests it can't resolve.
DNS search path Name resolution for unqualified
hostnames (host only)
NTP server address Ensure Appliance and Guests clocks
are kept in sync
Guest network subnet Class B address range to use for the
guest network
Guest network shared Determine whether guest network is
to shared with other Appliances.
Example values
172.17.120.129
user=root, password=admin
host.network.appliance.number=2 (default is 1)
host.fqdn=dev.company.com
host.network.ipaddress=198.168.1.15
host.network.netmask=255.255.255.0
host.network.gateway=10.20.30.254
host.network.device=eth1
host.network.bond.member.0=eth0
host.network.bond.member.1=eth1
host.network.nameserver.1=10.20.30.1
host.network.nameserver.2=10.20.40.1
host.network.searchpath=corp.com east.corp.com
west.corp.coM south.corp.com
host.network.ntp.server.1=ntp1.corp.company.com
guest.network.subnet=172.17.0.0
guest.network.shared=true (default is false)
Guest network device Specify which host device should be guest.network.device=eth1 (default is eth1)
used to connect Appliance guest
networks in the case of a cluster.
Guest network bonding Numbered list of host devices to bond guest.network.bond.member.1=eth1
together to form single logical "bond" guest.network.bond.member.2=eth3
device

Note
There can be an issue with the Intel network card not being detected by OL – hardware impacted IBM x3650 M4 (and
potentially other IBM M4 Series servers).
While the hardware supports PCIe GEN3 I/O cards, some GEN1 and GEN2 I/O cards are not recognised. For this reason there
may be a requirement to change the PCI speed selection for certain slots from GEN3 to GEN2.
Note 2 - The Network Time Protocol is based on a "consensus" model rather than the usual active/backup model. An NTP
client talks to all of its configured servers so is inherently high availability given enough servers. It derives the time from
the servers who's times are in agreement. It is recommended to configure at least 4 NTP servers to allow for one to fail and
another to give an inaccurate time value. For systems that provide a sub-optimal number of NTP servers, the Oracle
Enterprise Linux NTP client can be configured to ignore inconsistencies between servers and use the time from one server
in preference.
For an Appliance, this can be configured in appliance.properties by appending "true" after the preferred NTP server
hostname:

host.network.ntp.server.1=time1.domain.com true host.network.ntp.server.2=time2.domain.com

2. A "wildcard" DNS entry needs to be created for each Appliance in the corporate DNS server. This allows dynamic
resolution of environment resources without requiring further DNS changes for each environment creation/change.
This can be achieved by creating a "domain" entry for the Appliance server (that is a domain called <appliance server
name>.<domain>) instead of an 'A resource record' and configure the default (*) resolution to the IP address of the
appliance server.

Note
This step does not prevent the installation of the appliance from completing. It will only prevent access to the
Command and Control server (cmdctl) and any environments that may have been created.

3. Update the kickstart.ks and application.properities configuration files on the USB drive.
 a. Connect the USB to a machine and browse to '\ventyx\' (for example if the USB comes up as drive F, then
F:\ventyx\).
b. Edit the Appliance properties file '\ventyx\appliance.properties' and modify according to the Ellipse Appliance
installation parameters gathered, using the instructions and guidelines provided in the file to help:

Note
For Oracle's Sun Server X4-2 systems, additional installation parameters are provided that may help:

Parameter Description Usage

host.os.firstboot.device=sdb Device name for USB media Used during first boot at installation
host.os.device=sda Device name for OS Use for subsequent OS bootstrap
Installation procedure

c. Edit the kickstart timezone.ks file '\ventyx\timezone.ks' and modify according to the information gathered, as
per the instructions and tokens indicated, then save the file

Note
Consider removing the '--utc' flag from the desired timezone statement, if you do not intend to set the Hardware
clock to UTC timezone. Setting the Hardware clock to the local timezone, and keeping the '--utc' flag set at the
same time, will cause Linux to add (or subtract) an offset to the current operating system time, resulting in
incorrect timestamps being displayed in various logs.

4. Attach the Appliance USB drive and load the Oracle Linux DVD into the DVD drive of the physical server. The DVD should
be left in the drive until the appliance build is copmleted.
5. Using an Internet browser, navigate to the URL os the host's Remote Access Console (RAC), also known as:

IMM Integrated Management Module DRAC Distributed Remote Access Console

The RAC provides the important functions enabling: - remote server administration such as boot device selection and
ordering - device activation and configuration - diagnostics - console access.
6. Launch the Console from the RAC.
7. Reboot the server by either resetting or powering off and on again.
8. Enter the Setup / Menu (may have various names and associated key depending on manufacturer and BIOS revision) to
check/configure the boot sequence.
9. Set the boot sequence to Hard Drive, USB Device, then CD/DVD
10. Save the changes and restart the host.
11. Enter the Boot/Menu (may have various names and associated key depending on manufacture and BIOS revision).
12. Select the USB device. Wait for the Oracle Linux screen to display.
13. Press Enter to install Oracle Linux / Appliance.

a. The installation process provides a text based output indicating activities.

Note
Only core packages to the OS and additional package dependencies are installed.

b. After the operating system (OS) install, cloud infrastructure is copied to the local disk.
 c. The automated install will complete and system will reboot.
d. The host boots the OS on the local disk array (previously booted from the USB).
e. The Appliance is built following the first boot.
f. The command and control will be configured and takes 20-30 minutes. It will provide:

i. The basic monitoring application

ii. The Appliance Manager
iii. The Central HTTP Server

Note
To check on progress during the installation refer to “Monitor Installation of appliance and environments”. If this
process fails as a result of the DVD not being available rebuild the Appliance again.

14. For a list of all services running - http://[fully qualified hostname]. No credentials are required.
For example: http://cloud.company.com displays the list of all services running on the server
Versions from 8.3.11 display a window containing the Configuration and Monitoring Menu items. Go to the next step for
earlier versions.
15. Confirm the Appliance Manager is running http://cmdctl.[fully qualified hostname]/veam/ No credentials are
required.
For example: http://cmdctl.cloud.company.com/veam/ links to the Ellipse Appliance Manager
16. Confirm the Monitoring application is running http://monitor.[fully qualified hostname] The credentials are
ventyx/ventyx

Note
The full installation of operating system through to standing up the Appliance Manager, Monitoring and Apache HTTP server
can take from 1 to 3 hours depending on the hardware performance.

Note
Please refer to Operations > Site, Environments and the VEAM > Troubleshooting to check for installation troubleshooting
information.
Data Initialisation
The following choices cover initialising the data within the system:

1. The ABB supplied Cold Start Data is loaded as part of the installation. This is typically used for new customers or creation
of a new environment
2. The Ellipse 8 data is converted to the current Ellipse 8 version as part of the installation. Customers should back their
database up prior to installing the new version of Ellipse.
3. Convert from a pre Ellipse 8 release. Customers should consult the Operations guide - Ellipse Legacy Data Conversion, for
converting data from these releases.

Note
Core data, security data and GIS data is loaded automatically nto the database as part of each and every installation of
Ellipse. Change from one version to another is handled automatically by Ellipse.

Ellipse Database preparation

Refer to the Operations Guide (Part 4 Load Core Data) for information about re-running the core data load in situations where a
problems has led to the core data not being loaded.

Loading Cold Start Data (new customers)

Loading coldstart data is situational from version 8.3. This means when the deployment detects that the connected Ellipse
database is empty it will initialise the database and insert all the coldstart data.

Note
By default the installation either performs an Ellipse 8 data conversion, or loads the coldstart data when the database is
empty.

To login an Ellipse instance with coldstart data

When a new Ellipse environment is added, by default, Authentication Mode is Active Directory.
To login without any authentication the environment property Authentication Mode needs to be set to None.
To login to an Ellipse that has been loaded with Cold Start data, either login without any authentication or setup proper
authorization for user admin in the directory service.
To set the property to None go to Appliance Manager >> Manage Environments >> Environment Defaults and ensure the
following are set:

• Authentication Mode = None

Access to Ellipse Cold Start and exising data
Secure Sockets Layer (SSL) Certificates
For browser-based applications such as Ellipse, access is provided using both HTTP and HTTPS. HTTPS is provided by a default
set of SSL certificates and key, which is generated during Appliance installation. Because certificates are generated
automatically, they are not signed by a valid CA, and thus users will see a warning message when they connect to an instance
through HTTPS. This warning can be ignored however, so a user need only sees it once.
If you have your own CA signed certificate, you can input the details using VEAM.

Note
You must use a wildcard SSL certificate, of the format "*.applianceHostname.domain", for example
"*.appliance01.acme.com".

The details are:

• Signed Server Certificate - The signed certificate returned to you from the CA in response to your CSR.
• Server Private Key - The key used to generate the CSR.
• CA Intermediate Certificate Chain - (Optional: only if required by your CA)
If you leave these fields blank then the default set is used. These certificates are site-wide, that is they are used across all
environments.

Important
The Server Private Key MUST be generated WITHOUT a password, ensuring that HTTPD avoids prompting for a password at
the time it loads. If you do not remove the password then the HTTP server and VEAM will not start!
For information on how to remove the key, see Step 3 of: http://www.akadia.com/services/ssh_test_certificate.html

Important
If you input the Signed Server Certificate, you MUST input the Server Private Key that accompanies it at the same time! If
you do not, then the HTTP server and VEAM will not start!

To access an environment through HTTP, use the URL on the VEAM splash page.
To access an environment through HTTPS, use the "SECURE" URL on the VEAM splash page.
Create Ellipse 8 Environments
The installation of the Ellipse 8 environments is performed through the Ellipse Appliance Manager. It provides the ability to:

• Create, delete and update Ellipse 8 Environments

• Add the latest version of the Ellipse 8 installation package (MOR zip) ensuring all Ellipse 8 installations can easily be
updated.

Install Ellipse 8 Environments

The Ellipse Appliance Manager manages the installation of environments in the way it is meant to be installed and configured.
This includes installation of core data, security data and GIS data.
Move through the tabs in order to complete the creation of an environment(s).
Steps:

1. Access the Appliance Manager at the following URL - http://cmdctl.[fully qualified Appliance hostname]/veam/

2. Complete the Site Defaults required and press submit
Notes: a. The HTTP Alias Domain enables customers to nominate an alternate name by which Ellipse Application instance may
be accessed instead of the normal method which is via a URL containing the the Appliance host name. The most common
example of where the HTTP Alias Domain comes into play is when an external load balancer is introduced and the customer
wants a generic URL, not tied to any particular Appliance for end-users to access. The following diagram illustrates how the
HTTP Server Alias enables the generic name that becomes the main entry point to the cluster:

HTTP Server Alias is a site level property. As such, changes to the HTTP Server Alias Domain will be inherited as a default into
all furture environment deploys. Changes to the HTT Server Alias Domain will not impact exsiting environments until they are
redeployed.

3. Move to the "Environments" tab and click on the Add button to display the Add Environment window
4. Complete the fields:

a. Version
b. Type (ensure you select the appropriate type of environment)
c. Name
d. Description
e. Long Description
5. Click on the save button within the Add Environment window to save the selection to the Environments grid
6. Click on the environment that has been created to display information in the Properties table
7. Go to the Properties table and complete the properties for the Application Servers listed. Expand the entries if necessary.
Environment Defaults

Requirements Usage Example ONLY

 SMTP Mail Server Mail server for Email fromEllipse mail.company.com
SMTP Mail From Batch Email value environment@host.tld
Authentication Mode AD, LDAP, or None
Directory Naming Provider The authentication server: ldap://domaincontroller.
domain.com:389
Directory Service Bind Path User Name service-ldap
Directory Service Bind Credentials Password for the bind if required ldap-access
Directory Service Base Context OU=Framework,DC=corp,DC=
company,DC=com
Directory Service Base Filter (sAMAccountName={0})
Active Directory Role Context OU=Framework,DC=corp,DC=
company,DC=com
Active Directory Role Filter (sAMAccountName={0})
Active Directory Role Attribute Id RoleAttributeId
Active Directory Role Name Attribute Id RoleNameAttribute
LDAP Principal DN Prefix PrincipalDnPrefix
LDAP Principal DN Suffix PrincipalDnSuffix
Ellipse JDBC URL The Ellipse database schema URL jdbc:oracle:thin:@db.
company.com:1521:elldev
Ellipse JDBC User The Ellipse database schema ellipse
Username
Ellipse JDBC Password The Ellipse database schema ellipse
Password
Ehcahe Enabled Ellipse caching true
EFS Appliance ID Appliance ID that will host the EFS Self
or "Self"
Ellipse Events Enabled Enable/Disable Ellipse Events false
District Timezones Enabled Enable/Disable Timezones for false
Districts
VIP
VIP JDBC User VIP schema user
VIP JDBC Password VIP schema password

8. Once you have finished editing the properties click Save.

9. Click on Submit to create the environment

Note
For instructions on this application refer to the Ellipse 8 Operations Guide, Using the Appliance Manager
To check on progress during the installation refer to "Monitoring Appliance Instiliasation and Environment Creation".

Access the Environment

To access the working environment use the following:

1. Ellipse

http://ellipse-[name].[fully qualified hostname]/ria/ui.html

For example:

http://ellipse-dev.cloud.company.com/ria/ui.html

2. VIP

http://vip-[name].[fully qualified hostname]/vip``

For example:

http://vip-dev.cloud.company.com/vip
 Credentials admin/Admin0

Note
[name] refers to step 4c of “Install Ellipse 8 Environments” above.

Note
Please refer to Operations > Site, Environments and the VEAM > Troubleshooting to check for installation troubleshooting
information.
Secure WebDAV Connectivity
As part of the environment creation using the Appliance Manager (VEAM), a secure WebDAV filestore for Ellipse Interfaces is
published.
In order to securely connect to the Environment Interfaces WebDAV, the Certification Authority (CA) used to generate the SSL
Certificate (CRT) needs to be distributed to each client's Trusted Root Certification Authorities certificate store.
The default WebDAV CA of a VEAM managed Environment is at the following Command & Control server filesystem locaton:
/etc/pki/CA/private/[fully qualified hostname].crt

This task can either be done the preferred method by an Active Directory (AD) Domain Admistrator using Group Policy or by
each client user who is a Local Administrator.
GIT Customer Software Repository Override
The Ellipse Appliance provides its own Git server, as an initial deployment option and to ensure that out of the box, Ellipse
Appliances are ready for customer developed software to be introduced to Ellipse environments that might be deployed.
A downside to this approach is that unless configured to do otherwise, each Appliance Git service stores its repositories locally,
that is, on its local filesystem. If the Appliance was to become unrecoverable for any reson, it could result in loss of
customer-software (if it was never backed up). Git is a distributed version control system and so it is possible , even likely, that
one or a number of developers or system administrators may have a recent enough copy of the repository however this
approach is hardly a planned and reliabel approach.
With these limits in mind, some customers choose to change the customer-software deployment model slightly by externalising
their customer-software repository away from the Appliance to a Git service managed by the customer or by a third party,
often in the cloud. GitHub (www.github.com) is a good example of a cloud based Git service.
Through appliance.properties, customers are provided with the option to override the standard GIT customer-software
repository with git service URL external to the Appliance. The Git Service identified must of course have network connectivity to
each Appliance(s). This effectively giving provides a central location rom which software components can be pushed out to all
guests defined on all Appliances and / or to other appliances.

1. Specify the new software URL in /mincom/data/conf/etc/appliance.properties. For example

customer.software.url=git://gitserver/company-repo.git

2. If trusted authentication is required (when using ssh-based protocols, git for example), retrieve the locally generated ssh
public key and upload it to the server. This key can be found at the following location on the appliance
/appliance/data/conf/keys/appliance/key.pub

3. Upon detection of a git customer override in appliance.properties, appliance(s) and guests will automatically clone and
refresh the repository at
/appliance/data/conf/git-repos/customer-software

with the new location.

AD Domain Administrator CRT distribution

1. Start the Server Manager application and install the Group Policy Management feature using Add Features.
2. Once installed, start the Group Policy Management console from Administrative Tools.
3. Navigate to the specific Default Domain Policy object in Group Policy Objects for the domain and forest used to build the
Ellipse environment.
4. Edit the Default Domain Policy and navigate to the Public Key Policies from Computer Configuration, Windows Settings,
Security Settings.
5. Open Trusted Root Certification Authorities and import the above CRT using the wizard.

Local Administrator CRT distribution

1. Start the Microsoft Management Console (MMC) from the Start menu, search using mmc.
2. Add the Certificates snap-in from the Add/Remove Snap-in menu option.
3. Expand the Certificates tree and navigate to the Trusted Root Certification Authorities store.
4. Import the above CRT by using the wizard available by right clicking on Trusted Root Certification Authorities, All Tasks.
Once the CA has been distributed using either method, verify connectivity by navigating to the following URL using a supported
Internet browser.

https://interfaces-<Ellipse Environment>.<Sub Level Domain>.<Corporate Domain>

Using the Sample Environment information the WebDAV URL follows, when prompted supply AD user credentials.

https://interfaces-development.cloud.corp.tld

Successful connectivity can be confirmed if the browser does not report any Certificate warnings. When prompted, supply the
AD credentials relevant to the Environment configuration.
To test read/write access to the Interface WebDAV, map a network drive using Windows Explorer or equivalent WebDAV
compatible utility.

Map Network Drive

1. Start the Map Network Drive wizard from either File Explorer or right click on Computer from the Start Menu.
 2. Do not specify a folder when prompted, click on the alternative option "Connect to a Web site that you can use to store
your documents and pictures".
3. Clicking through the following prompt, select "Choose a custom network location".
4. Input as the location the HTTPS URL for the Interfaces WebDAV site, supplying valid AD user connection details for the
Environment.
Perform some standard file operations once the drive is mapped. Sample operations include file and directory creation,
modification and deletion.
This completes the configuration of secure WebDAV access to the Interfaces file system.
Monitor Installation of appliance and environments
While the installation is running there is the opportunity to monitor progress through various logs.

Monitor appliance creation

During the installation process, when you see the prompt “Starting Ellipse Green deployment” on the console, you will be able
to make a ssh connection to the server.
Steps:

1. ssh into the hostname, using the hostname you provided in the appliance.properties file For example >ssh
cloud.company.com The credentials are root/ventyx
2. Tail the log to display installation activity and any evidence of issues such as error and failure messages. If this occurs
review the log for details and contact ABB for support assistance. For example: >tail –f /var/log/messages
When the console screen changes to the login prompt it is possible to login as oneadmin.
Steps:

1. ssh into the hostname, using the hostname you provided in the appliance.properties file
For example >ssh cloud.company.com
The credentials are root/ventyx
2. Switch to the oneadmin user, and using the commands listed in the table check on the status of the first environment
Command Comment
onehost list List the host name when it is up (value = on)
onevnet list Indicates if the virtual network is running
oneimage list Lists the image used for the installation when it is installed
onevm list Lists the VM name for the appliance and monitoring server once it is up (value = running)

Note
The onvevm list command can also be used when an environment is being created and will indicate which VM's have been
created at the time the command is run.

Once the VM has a status of running (and has CPU and Memory allocated) you should be able to log into it.
Steps:

1. ssh into the hostname, using the hostname you provided in the appliance.properties file
For example >ssh cloud.company.com
The credentials are root/ventyx
2. Log into the server - ssh cmdctl.ventyxinternal. The credentials are root/ventyx.
3. Tail the logs to display installation activity and any evidence of issues such as error and failure messages. If this occurs
review the log for details and contact ABB for support assistance.
For example >tail –f /var/log/messages

Monitor Ellipse environment creation

You can monitor the installation of the VMs, firstly from the host and then on each VM.

1. SSH into the hostname, using the hostname you provided in the appliance.properties file
For example >ssh cloud.company.com The credentials are root/ventyx
2. Switch to the oneadmin user (su – oneadmin) and run the onevm command (see above for further details).
3. Once the VM has a status of running (and has CPU and Memory allocated) you should be able to log into it
4. From a root session on the host ssh to the relevant VM for example > ssh ellipse01.dev.ventyxinternal
Each server uses the naming convention [application server name].[name].internal
For example ellipse01.dev.ventyxinternal
[application server name] is the first part of Name shown in the onevm command
[name] is the name you gave the environment (refer to step 4c of Install Ellipse 8 Environments)
 Note
The application servers are only accessible from the host.

5. Tail the log to display installation activity and any evidence of issues such as error and failure messages. If this occurs
review the log for details and contact ABB for support assistance.
For example: >tail –f /var/log/messages
6. Also check the following logs for Ellipse and Batch VMs

a. All logs in /opt/ellipse/logs

b. /opt/ellipse/jboss/standalone/log/server.log
c. VIP logs are: /opt/vip/jboss/standalone/log/server.log
Appendix

Creating an Oracle Ellipse Database

The Ellipse 8 database needs to be created with the Oracle Locator package installed and configured to use the following
character sets:

• Database Character Set is AL32UTF8

• National Character Set is UTF8
• Database Role XAUSERS with following privileges:

• select on dba_pending_transactions
• select on v$xatrans$
• select on pending_trans$
• select on dba_2pc_pending
• execute on dbms_system
A schema for the Ellipse data must be created as follows:

• Tablespaces:

• Table Tablespace (name as ELLIPSE_TAB)

• Index Tablespace (name as ELLIPSE_IDX)
• Unlimited quotas for the Ellipse schema/user on these tablespaces
• Username ellipse
• Grant the following privileges to the ellipse user:

• CREATE SESSION
• CREATE TABLE
• CREATE VIEW
• CREATE SEQUENCE
• CREATE PROCEDURE
• XAUSERS (Role)
The following are set of permission grants for database system objects that required by a standard user to query performance
statistics tables and views.

grant select on sys.v_$session to ellipse;

grant select on sys.v_$lock to ellipse;
grant select on sys.v_$sqltext to ellipse;
grant select on sys.v_$locked_object to ellipse;
grant select on sys.v_$sql to ellipse;
grant select on sys.v_$process to ellipse;
grant select on sys.v_$session_wait to ellipse;
grant select on sys.v_$session_blockers to ellipse;
grant select on sys.v_$global_transaction to ellipse;
grant select on dba_scheduler_jobs to ellipse;
grant select on sys.obj$ to ellipse;
grant select on sys.user$ to ellipse;
grant select on sys.v_$sql_plan_statistics_all to ellipse;
grant select on sys.v_$sql_bind_capture to ellipse;

Note
These grants will allow an administrator to run an Oracle performance data capture without DBA involvement. The capture
will be supplied as a Groovy script to run at command line when batch is not available, or as an Ellipse batch job.

Assumptions:

• A server has been configured running Oracle Database with either of the following supported versions:

• 11gR2 (Standard or Enterprise Edition)

• 12c
 • The database was installed with Oracle Locator. This is a standard extension that is used by the Ellipse Geospatial
Gateway location tables. This extension contains the MDSYS user, the SDO_Geometry data type and a number of spatial
capabilities required for storing and manipulating spatial entities.
• The JDBC connection string and credentials are available, as it is required for the installation of Ellipse.

Note
It is a requirement that the schema and tablespace names match the defined names of 'ellipse' for the schema, and
'ELLIPSE_TAB' and 'ELLIPSE_IDX' for the tablespaces.

Database Parameter recommendations

open_cursors = 1000 (oracle default is 50)
processes = 500 (oracle default is 100)

Password issue
Profiles in Oracle are a means to limit the resources available to a user. The Oracle profile parameter PASSWORD_LIFE_TIME
determines the maximum period a password is valid.

Note
The value of PASSWORD_LIFE_TIME parameter for the default Oracle profile has being reduced from unlimited in Oracle 10g
to 180 days in Oracle 11g.

All database logins created with the default Oracle 11g profile will expire after 180 days (6 months) and upon expiry, access to
the database using this login(s) will cease. The password must then be reset by the Database Administrator.

Fix for password expiry Oracle 11g

This issue has been resolved by creating an additional Oracle user profile called ELLIPSE with PASSWORD_LIFE_TIME and other
related parameters set to appropriate values, so that when you create a new database user it is assigned the ELLIPSE profile as
shown in the workaround example below.
For an existing database, please follow the steps outlined in the Workaround section below.

Workaround
The following commands can be run using the Oracle SQL*Plus utility or similar interfaces.
To display the current user expiry date

SELECT USERNAME,EXPIRY_DATE,PROFILE FROM dba_users WHERE username='ELLPRD';

USERNAME EXPIRY_DA PROFILE

------------------------------ --------- ------------------------------
ELLPRD 16/JUN/10 DEFAULT

Create a profile called ELLIPSE and assign it to the user(s):

CREATE PROFILE ELLIPSE LIMIT PASSWORD_LIFE_TIME UNLIMITED FAILED_LOGIN_ATTEMPTS UNLIMITED PASSWORD_LOCK_TIME 1/144;

Profile created.

ALTER USER ELLIPSE PROFILE ELLIPSE;

User altered.

To display user new profile settings:

SELECT USERNAME,EXPIRY_DATE,PROFILE FROM dba_users WHERE username='ELLPRD';

USERNAME EXPIRY_DA PROFILE

------------------------------ --------- ------------------------------
ELLPRD ELLIPSE

Ellipse 8 VIP Tablespace

Prior to installing the integration platform server there is a requirement to create a user and tablespace in the same database
instance as Ellipse:
A schema for the VIP data must be created as follows:

• Tablespaces:

• Table Tablespace (name as MIB_TAB)

• Unlimited quotas for the VIP schema/user on these tablespaces
• Username mib
• Password: mib
• Grant the following privileges to the mib user:

• CREATE SESSION
• CREATE TABLE
• CREATE VIEW
• CREATE SEQUENCE
• CREATE PROCEDURE
• XAUSERS (Role)
Assumptions:

• A server has been configured running Oracle Database with either of the following supported versions:

• 11gR2 (Standard or Enterprise Edition)

• 12c
• The JDBC connection string (including credentials) is available, as it is required for the installation of VIP.
• There is only one tablespace required for the VIP schema as it has its tables and the indexes in one tablespace.

Creating a MS SQL Server Ellipse Database

Regardless of the DB type. whether Oracle or SQL, a schema for Ellipse must be created as follows:

• Tablespaces:

• Table Tablespace (name as ELLIPSE_TAB)

• Index Tablespace (name as ELLIPSE_IDX)
• Unlimited quotas for the Ellipse schema/user on these tablespaces
• Username <schema_user>
• Grant the following privileges to the <schema_user> user:

• CREATE SESSION
• CREATE TABLE
• CREATE VIEW
• CREATE SEQUENCE
• CREATE PROCEDURE
• XAUSERS (Role)
where:
<schema_user> is the name of the schema / user required to "connect" to the DB via standard J2EE JDBC connections
<schema_pwd> is the password associated with the <schema_user>
The following are set of permission grants for database system objects that required by a standard user to query performance
statistics tables and views.

grant select on sys.v_$session to ellipse;

grant select on sys.v_$lock to ellipse;
grant select on sys.v_$sqltext to ellipse;
grant select on sys.v_$locked_object to ellipse;
grant select on sys.v_$sql to ellipse;
grant select on sys.v_$process to ellipse;
grant select on sys.v_$session_wait to ellipse;
grant select on sys.v_$session_blockers to ellipse;
grant select on sys.v_$global_transaction to ellipse;
grant select on dba_scheduler_jobs to ellipse;
grant select on sys.obj$ to ellipse;
grant select on sys.user$ to ellipse;
 grant select on sys.v_$sql_plan_statistics_all to ellipse;
grant select on sys.v_$sql_bind_capture to ellipse;

Note
These grants will allow an administrator to run an Oracle performance data capture without DBA involvement. The capture
will be supplied as a Groovy script to run at command line when batch is not available, or as an Ellipse batch job.

Assumptions prior to creating Ellipse 8 database

• A database server has been configured.

• The JDBC connection string and credentials are available, as it is required for the installation of Ellipse.

Note
It is a requirement that the schema and tablespace names match the defined names of 'ellipse' for the schema, and
'ELLIPSE_TAB' and 'ELLIPSE_IDX' for the tablespaces.

Create Schema SQL

This is a suggested create schema sql. It has directory privileges granted in order for the 'ELLIPSE' user to be able to perform
Data Pump import/export operations, which may be convenient.

Note
This relies on a database having been created.

CREATE ROLE XAUSERS;

GRANT SELECT ON DBA_PENDING_TRANSACTIONS TO XAUSERS;

GRANT SELECT ON V$XATRANS$ TO XAUSERS;

GRANT SELECT ON PENDING_TRANS$ TO XAUSERS;

GRANT SELECT ON DBA_2PC_PENDING TO XAUSERS;

GRANT EXECUTE ON DBMS_SYSTEM TO XAUSERS;

CREATE SMALLFILE
TABLESPACE "ELLIPSE_IDX"
LOGGING
DATAFILE '/oracle/oradata/btcxst/ellipse_idx_01.dbf' SIZE 4096M REUSE AUTOEXTEND
ON NEXT 100M MAXSIZE 32767M EXTENT MANAGEMENT LOCAL UNIFORM
SIZE 128K SEGMENT SPACE MANAGEMENT AUTO;

CREATE SMALLFILE
TABLESPACE "ELLIPSE_TAB"
LOGGING
DATAFILE '/oracle/oradata/btcxst/ellipse_tab_01.dbf' SIZE 4096M REUSE AUTOEXTEND
ON NEXT 100M MAXSIZE 32767M EXTENT MANAGEMENT LOCAL UNIFORM
SIZE 128K SEGMENT SPACE MANAGEMENT AUTO;

CREATE USER ELLIPSE

IDENTIFIED BY ELLIPSE
DEFAULT TABLESPACE USERS
TEMPORARY TABLESPACE TEMP
PROFILE DEFAULT
ACCOUNT UNLOCK;

GRANT CREATE SESSION TO ELLIPSE;

GRANT CREATE TABLE TO ELLIPSE;

GRANT CREATE VIEW TO ELLIPSE;

 GRANT CREATE SEQUENCE TO ELLIPSE;

GRANT CREATE PROCEDURE TO ELLIPSE;

GRANT XAUSERS TO ELLIPSE;

ALTER USER ELLIPSE QUOTA UNLIMITED ON ELLIPSE_TAB;

ALTER USER ELLIPSE QUOTA UNLIMITED ON ELLIPSE_IDX;

GRANT READ, WRITE ON DIRECTORY SYS.DATA_PUMP_DIR TO ELLIPSE;

Ellipse support for Microsoft's SQL Server 2014

ABB Enterprise Software recommend that the database use a Collation of SQL_Latin1_General_CP1_CI_AS (default) but will
support SQL_Latin1_General_CP1_CS_AS with others subject to confirmation.
ABB Enterprise Software does not recommend the use of dbo as default schema for Ellipse, and in future may disable Ellipse
access on all database objects that use the dbo schema. The schema name with be the same as the database login (and
mapped user) and is created by the conversion script at coldstart.
As Azure SQL does not support the use of filegroups, the SQL Server with only use the Primary filegroup (default) and any
reference to indexTableSpace and tableTableSpace in the conversion and the coredata load script will be ignored.
The database login (and mapped user) for the Ellipse database will have the db_owner role assigned.
Because of the complexity in the nature of a production database environment, it is recommended that the production
database be created and administrated by an experienced IT professional.
The following are example Transact-SQL scripts to create a simple ellipse database environment with login (mapped user) and
database role assign.

In SQL Server
USE [master]
GO
CREATE DATABASE [elltst]
ON PRIMARY (NAME = N'elltst',
FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\elltst01.mdf',
SIZE = 30GB, MAXSIZE = UNLIMITED, FILEGROWTH = 1GB)
LOG ON (NAME = N'elltst_log',
FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\elltst01_log.ldf',
SIZE = 5GB, MAXSIZE = 2048GB, FILEGROWTH = 10%)
COLLATE SQL_Latin1_General_CP1_CI_AS
GO
CREATE LOGIN [elltst] WITH PASSWORD=N'example_password', DEFAULT_DATABASE=[elltst], DEFAULT_LANGUAGE=[us_english], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF
GO
USE [elltst]
GO
CREATE USER [elltst] FOR LOGIN [elltst] WITH DEFAULT_SCHEMA=[elltst]
EXEC sp_addrolemember 'db_owner', 'elltst'
GO

For more detail on creating a database in SQL Server 2014 by using SQL Server Management Studio or Transact-SQL. go to
https://msdn.microsoft.com/en-au/library/ms186312(v=sql.120).aspx
Installation Information Collector
Consultants should collect information for each environment and project by printing off the Virtualisation and Installation Check
List Form following. A copy of these pages will be required for each environment in each project.
You are asked to complete the administrative aspects of the sheet as well as the installation related information.
This information covers:

• Virtualisation activities
• Installation activities
Virtualisation and Installation Check List Form
Virtualisation Name: _____________________ Project: ____________________
Environment: _____________________ Customer: ____________________

Requirements Usage Example ONLY

Wild card DNS entry provided for appliance. Allows dynamic resolution of <appliancehost. ventyxellipse>
Wildcard certs *.ventyxellipse.domain Environments .<domain>
Values:
RAC
URL for the host RAC Allows remote server admin 172.17.120.129
Values:
Login details for RAC Allows access User = root P/W = admin
Values:
Kickstart (appliance.properties)
NTP server address Appliance Time Sync. time.company.com
Values:
Name Servers Appliance Network 10.20.30.1,10. 20.40.1
Configuration
Values:
Fully Qualified Domain Name Appliance Network ellipse01.com pany.com
Configuration
Values:
Server IP Address Appliance Network 10.20.30.1
Configuration
Values:
Netmask Appliance Network 255.255.255.0
Configuration
Values:
Network Gateway Appliance Network 10.20.30.254
Configuration
Values:
Network search path Appliance Network .ventyx.com .dev.ventyx.com
Configuration
Values:
Guest network subnet Appliance Network 172.29.0.0
Configuration
Values:
Host network appliance number Appliance Network 1
Configuration. Uniquely
identifies this Appliance on the
network.
Values:
Guest domain suffix Appliance Network ventyxinternal
Configuration
Values:
Host network device Appliance Network eth0
Configuration
Values:
Guest network device Appliance Network eth1
Configuration
Values:
Guest network shared Appliance Network true
Configuration
Values:
Timezone Valid linux Timezone -utc Australia/ Brisbane
Values:
Mail Server
SMTP Mail Server Mail server for Email from mail.company.com
Ellipse
Values:
SMTP Mail From From header for Email from environment@company.com
Ellipse
Values:
Directory services information
Authentication Mode Active Directory, LDAP, or Active Directory
None.
Values:
Directory Naming Provider The LDAP authentication ldap://domain controller.domain.
server: com:389
Values:
Directory Service Bind Path User Name service-ldap
Values:
Directory Service Bind Credentials Password for the bind if ldap-access
required
Values:
Directory Service Base Context OU=Framework, DC=corp,DC=
company,DC=com
Values:
Directory Service Base Filter (sAMAccountName ={0})
Values:
AD Directory Role Context OU=Framework,DC=corp,DC=
company,DC=com
Values:
AD Directory Role Filter (sAMAccountName={0})
Values:
AD Directory Role Attribute Id RoleAttributeId
Values:
AD Directory Roles Name Attribute Id RoleNameAttribute
Values:
LDAP Principal Dn Prefix PrincipalDnPrefix
Values:
LDAP Principal Dn Suffix PrincipalDnSuffix
Values:
SSL Signed Server Certificate Certificate file File contents
Values:
SSL Server Private Key Private key file File contents
Values:
SSL CA Intermediate Certificate Chain Certificate Authority and who File contents
you trust in the chain
Values:
HTTP Server Alias Domain Hostname alias for Appliance ellprd.company.com
Values:
Database information
Values:
Ellipse JDBC URL The Ellipse database schema jdbc:oracle:thin:@db.
URL company.com:1521:elldev
Values:
Ellipse JDBC User The Ellipse database schema ellipse
Username
Values:
Ellipse JDBC Password The Ellipse database schema ellipse
Password
Values:
BSI Database The BSI database schema bsi/bsi@msdvml23.db.
comapny.com:1521/ellperf
Ehcahe Enabled Ellipse caching true
Values:
EFS Appliance ID Identify multiple site Self
appliances
Values:
Ellipse Events Enabled Ellipse Events true
Values:
District Timezones Enabled Enable/Disable Timezones for false
Districts
Values:
VIP
VIP JDBC User JDBC username
Values:
VIP JDBC Password JDBC password
Values:
GIT Customer Software Repository Source
GIT Source Override GIT Repos URL git://1.2.3.4/cust-rep.git
Values:

Consultant Name: ___________________________ Date: ___ / ___ / 20____