Shared Services Installation Guide

AVEVA Shared Services 3.
3
Installation Guide
AVEVA Solutions Limited
Disclaimer
1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from viruses.
1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss of anticipated
savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; any special, indirect, consequential
or pure economic loss, costs, damages, charges or expenses which may be suffered by the user, including any loss suffered by
the user resulting from the inaccuracy or invalidity of any data created by the AVEVA software, irrespective of whether such
losses are suffered directly or indirectly, or arise in contract, tort (including negligence) or otherwise.
1.3 AVEVA shall have no liability in contract, tort (including negligence), or otherwise, arising in connection with the performance
of the AVEVA software where the faulty performance of the AVEVA software results from a user's modification of the AVEVA
software. User's rights to modify the AVEVA software are strictly limited to those set out in the Customisation Manual.
1.4 AVEVA shall not be liable for any breach or infringement of a third party's intellectual property rights where such breach results
from a user's modification of the AVEVA software or associated documentation.
1.5 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the performance of the
AVEVA software shall be limited to 100% of the licence fees paid in the year in which the user's claim is brought.
1.6 Clauses 1.1 to 1.5 shall apply to the fullest extent permissible at law.
1.7 In the event of any conflict between the above clauses and the analogous clauses in the software licence under which the
AVEVA software was purchased, the clauses in the software licence shall take precedence.
Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every part of it (including
source code, object code, any data contained in it, the manual and any other documentation supplied with it) belongs to, or is
validly licenced by, AVEVA Solutions Limited or its subsidiaries.
All rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this document is
commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without the prior written
permission of AVEVA Solutions Limited. Where such permission is granted, it expressly requires that this copyright notice, and
the above disclaimer, is prominently displayed at the beginning of every copy that is made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material or electronic form, without
the prior written permission of AVEVA Solutions Limited. Subject to the user's rights, as set out in the customisation manuals to
amend PML software files contained in the PMLUI and PMLLIB folders and any configuration files, the user may not reverse
engineer, decompile, copy, or adapt the software. Neither the whole, nor part of the software described in this publication may be
incorporated into any third-party software, product, machine, or system without the prior written permission of AVEVA Solutions
Limited, save as permitted by law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and
criminal prosecution.
The AVEVA software described in this guide is to be installed and operated strictly in accordance with the terms and conditions of
the respective software licences, and in accordance with the relevant User Documentation. Unauthorised or unlicenced use of the
software is strictly prohibited.
Copyright 2012 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. AVEVA shall not be liable for
any breach or infringement of a third party's intellectual property rights where such breach results from a user's modification of the
AVEVA software or associated documentation.
AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.
Trademark
AVEVA™, AVEVA Everything3D™ and AVEVA E3D™ are registered trademarks of AVEVA Solutions Limited or its subsidiaries.
Unauthorised use of the AVEVA™, AVEVA Everything3D™ and AVEVA E3D™ trademarks is strictly forbidden.
AVEVA, the AVEVA logos and AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Limited or its
subsidiaries in the UK, Europe and in other countries.
3rd Party Software

The copyright, trademark rights, or other intellectual property rights in any other product or software, its name or logo belongs to
its respective owner.
The following 3rd party software is included in some of the AVEVA products contained in this Online Help:
• Based on Teigha® from the Open Design Alliance.
• Microsoft® Office Fluent™ user interface. Fluent is a trademark of Microsoft Corporation and the Fluent user interface is
licensed from Microsoft Corporation. The Microsoft Office User Interface is subject to protection under U.S. and
international intellectual property laws and is used by AVEVA Solutions Limited under license from Microsoft.
• DevExpress® redistributables are used by AVEVA under license from Developer Express Inc. Copyright © 2000-2014
Developer Express Inc.
• 3D input device development tools and related technology are provided under license from 3Dconnexion. © 3Dconnexion
1992 - 2013. All rights reserved.
• Portions Copyright © GrapeCity, Inc. 1987-2012. All Rights Reserved.
Shared Services Installation Guide
Revision Sheet
Date Version Comments / Remarks

Nov 2015 3.3 First Release
Contents Page
Shared Services Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:5
Introduction to Global Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1

Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2
IIS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2
SQL Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5
Plant Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:21
Table Schemas for Global Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:23
Configure the Application Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:23
Notification Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1

Engineering and Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2
3.3 © Copyright 1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. i
3.3 © Copyright 1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. ii
Shared Services Installation
1 Shared Services Installation
The AVEVA Shared Services installs a suite of Services that compliment AVEVA E3D™
features to feedback messages on Global Operations and schedule key Global commands.
There are three components in suite of Services, these are:
• AVEVA Global Manager Service
• AVEVA Global Scheduler Service
• AVEVA Global Notifications Server
AVEVA Shared Services is compatible with:
• AVEVA Administration 1.4
• AVEVA Diagrams 14.1
• AVEVA Engineering 14.1.1
• AVEVA Global 3.2.1.
AVEVA Shared Services 3.3 should be used with the above AVEVA Engineering and AVEVA
Administration products only. It should not be used with another product, other products
should be installed according to the appropriate installation process.
Note: Before installing AVEVA Shared Services 3.3, make sure that AVEVA Shared
Services 3.2 is un installed.
The AVEVA Global Scheduler Service is required by the new Scheduler feature in AVEVA
E3D™. The AVEVA Global Notifications Service is required to feedback messages from
the daemon to AVEVA E3D™ and the AVEVA Shared Service supports both.
All services must be installed on the same machine. It is also possible to install the AVEVA
Global Scheduler Service or the AVEVA Global Notifications Service on the corporate
network, but neither of these will work without the AVEVA Shared Service also being
installed on the same corporate network.
The AVEVA Shared Service requires IIS 7 or above to host the service. IIS 7 or higher must
be installed as a pre-requisite to installing the AVEVA Shared Service. If the installer does
not detect IIS 7 or higher on the machine it is being installed on, the AVEVA Shared
Service will not be visible.
As a pre-requisite Net.Tcp Port Sharing Service must be started in Services to start the
Global Notifications Service.
3.3 © Copyright 1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. 1:1
Only the AVEVA Global Notification Service is required for Engineering and should be
selected.
If installing both services it is best to make sure that the AVEVA Global Scheduler Service is
not started. From the Control Panel, select Services, double click to display the AVEVA
Scheduler Service Properties (Local Computer) window.
Make sure the Service status is stopped and the Startup type is Manual.
1.1 Silent Installation

It is possible to run the Global Services installation from setup.exe (which will assume
Administrator privilege), or from the Command Prompt with Administrator privileges by
running the commands in the following sections.
The following sections are examples of different silent install depending on user
requirements, the users installer location path maybe different to that of the example and the
log file path can be changed. If the user runs the silent install without Administrator
privileges the install will fail without an obvious reason.
The user will need to replace the following strings:
• /qb - This forces the install to be silent, by removing this option the installation process
will be interactive.
• /LV globalService.log - The log file to record the install progress, any errors occurring at
install time will be listed in this file.
The user can run the installation without the log file, but if the install fails it will be difficult to
determine what went wrong.
Default
msiexec /I "C:\temp\Downloads\SharedServices3.30.msi” /LV

globalServices.log /qb
The default setting assumes that the Global Server and Global Services are running on the
local server.
Global Server and Global Services on Different Machines
msiexec /I "C:\Temp\Downloads\E3D\GlobalServices\
GlobalServices1.00.msi" /LV.\globalService.log /qb-
GLOBALMANAGERSERVICEHOST=hostname
GLOBALNOTIFICATIONSERVICEHOST=notifyname
This setting assumes that the Global Services machine is running on one machine and
Global Server is running on another machine. If both the notification Service and the AVEVA
Global Manager Service are on the same machine, both SHAREDSERVICEHOST and
NOTIFICATIONSERVICEHOST can be the same setting, but both settings must be
declared.
Advanced
msiexec /I "C:\Temp\Downloads\E3D\GlobalServices
\GlobalServices1.00.msi" /LV .\globalService.log /qb-
GLOBALMANAGERSERVICEHOST=hostname
GLOBALNOTIFICATIONSERVICEHOST=notifyname SQLDBNAME=SqlDb
SQLUSER="User Id=SqlUser;Password=sqlpassword123"
SQLHOST=SqlHost/SQLversion
The advanced setting allows the SQL Database to be defined.

When installing Global Services the installation defaults the SQL Server URL to
localhost\SQLEXPRESS. This can be changed by using the SHAREDSERVICEURL
property on silent install. It is possible to change the SQL server URL after installation if it
was not known when the installing Global Services, or the SHAREDSERVICEURL property
was not set when Global Services was installed. To do this edit the selected text in the
web.config file under the Global Services\Shared Service folder:
Install settings
All three products:
• SHAREDSERVICEHOST sets the host that the Global Manager Service is running on.
• NOTIFICATIONSERVICEHOST sets the host the Notification Manager is running on
(likely to be the same as SHAREDSERVICEHOST.
Global Services:
• SQLDBNAME Determines the name of the SQL Database
• SQLUSER sets User name and Password for the user access to SQL, only the strings
SqlUser and sqlpassword123 can be changed
• SQLHOST allows the URL for the SQL Server to be defined.
Complete Silent Install

When installing with silent install the user will not be prompted for any input. The installer will
automatically go through the installation options as follows:
The install will configure itself.
Depending on privileges the User Access Control may ask the user to confirm to run the
installation. Click Yes.
The installation will then run.
Once the installation has completed the installer window will close.
1.2 Installation
If installing without the -qb silent installation flag or from setup.exe, the user will need to do
the following installation process accordingly:
If the autostart feature on the PC is working correctly, the browser will automatically load the
correct file on the disc and display the Installation menu.
Note: The exact appearance of installation window and screens may be different
depending on which browser is being using. The windows used in this manual are
from Microsoft Internet Explorer 9.
If the browser was not running, or the page failed to load, navigate to the setup.exe file and
double click on it; alternatively, right-click and choose the browser from the Open With
option on the popup menu.
To install the software, click Install. A message window is displayed asking the user if they
want to run the software. Click Run.
After a short duration a Welcome to the AVEVA Shared Services Setup Wizard window is
displayed. On this and subsequent screens a Cancel button is displayed. If Cancel is
clicked at any stage a pop-up window will be displayed prompting for confirmation. If Yes is
clicked partially installed files are removed and the installation process is stopped. If No is
clicked the installation will continue.
Click Next to display the End-User License Agreement window
The user must read the End-User License Agreement and then select the I accept check
box to activate Next.
Note: If the user does not select the check box, Next will not activate and the installation
cannot continue.
After clicking Next the installer will display the feature list for the AVEVA Shared Services,
it is possible to select one, two or all features to install.
By default, all services are selected for installation as only the AVEVA Global Notification
Service is required, click to deselect the AVEVA Global Scheduler Service and AVEVA
Global Shared Manager Services.
Click Browse to change the installation location if the user wants the product to be installed
to a different directory or leave at default location and click Next.
Select Install to install the AVEVA Global Services.
Once the files have been copied a final window is displayed confirming that the install
process is complete.
Click Finish to complete the installation.
Introduction to Global Services
2 Introduction to Global Services
The AVEVA Shared Services Installation Guide explains how to do the IIS Configuration,
SQL Configuration and installation of AVEVA Global Manager Services (as supplied by
AVEVA Solutions Limited on a DVD). Only AVEVA Global Server supports Windows XP and
Windows Server 2003. AVEVA Global Services can only be installed on Windows Server
2008 or Windows 7.
To enable AVEVA Global to make use of the Transfer technology a number of Services need
to be installed, these are:
The full deployment is spread between three installers, these are:

• Base Product - this now includes the Global client as a part of the standard install, but
there are some configuration steps that are required, this needs to be installed by any
Project Administrator or Designer.
• AVEVA Global Daemon12.1.SPx - the traditional AVEVA Global Product, this installs
the Daemon. This is installed onto machines that need to run the daemon. As one
daemon is required per project per location.
• AVEVA Global Services - The AVEVA Global Services product contains three features,
these are:
• AVEVA Global Manager Service
• AVEVA Global Scheduler Service
• AVEVA Global Notifications Server
The AVEVA Global Scheduler Service allows regular scheduled Extracts commands to
simplify the distribution of data in distributed extracts. The AVEVA Global Notifications
Service allows key global commands to feedback information to the Designer when they
have completed. Both the AVEVA Global Scheduler Service and the AVEVA Global
Notifications Service are independent of each other. The AVEVA Global Manager is only
required by the Scheduler Service.
All services must be deployed on the same machine. If only one feature is required then
only one of the AVEVA Global Notifications Service or the AVEVA Global Scheduler Service
needs to be installed. However, the AVEVA Global Manager Service must be available on
the local network. One instance of each service is required per location, and serves all
projects running.
2.1 Assumptions
The Global Services Manager Services Installation Guide is intended to detail the
installation and configuration process of running the AVEVA Global Services product. It
covers how to setup AVEVA Global Services with new and existing Global projects.
Therefore the Global Manager Services Installation Guide targets the IT administrator or
Global Project Administrator. As a result knowledge of AVEVA Global will be helpful but is
not essential.
Depending on the Operating System the user is installing on, the sections that follow may
differ on the screenshots. The following installations are done on Windows 7 machine.
Note: IIS and SQL configuration can be installed in any order, but both are pre-requisites
for the AVEVA Global Services Installation.
The base product installation requires specific configuration that can be undertaken at install
time, or post install. If changes are being made during installation then the base product will
need to be silently installed with the extra flags.
2.2 IIS Configuration

IIS needs to be configured to host the WCF Service that allows Project Administrators to set
up and maintain Extract Transfer schedules and Designers to Transfer items between
locations. To do this IIS must be configured before the AVEVA Global Manager services are
installed. The user must do the following:
Enable IIS on the Machine
Enable IIS8 and WinServer 2012
Enable IIS on the Machine

To enable IIS on the machine from the Start menu, click Control Panel.
Select Programs.
Select Turn Windows features on or off under the Programs and Features heading.
Windows Feature takes a short while to load.
Select Internet Information Services check box, this will automatically select what sub
options it requires.
Click OK and close the Control Panel.
Enable IIS8 and WinServer 2012

To enable IIS8 and WinServer 2012 on the machine from the Start menu, click Control
Panel then Programs.
Select Turn Windows features on or off, the Windows Features window is displayed.
Click to expand .NET Framework 4.5 Advanced Services then WCF Services in the
hierarchy. Make sure the HTTP Activation check box is selected.
Open Internet Information Services Manager, from IIS Manager window in the
Connections part of the IIS Manager window, select the top level node.
From the Actions part of the IIS Manager window, select Restart.
2.3 SQL Configuration

Install SQL Express
The following example uses SQL Express 2008 R2 64 bit.
Locate and click on the Installer to display the SQL Server Installation Centre window.
Click New Installation or add features to an existing installation to start the installation
process.
The SQL Server 2008 R2 window is displayed, indicating to the user that the setup for the
current operation is being processed.
Select I accept the licence terms check box, if the user agrees to the licence text.
The installation process will then begin by setting up the process files.
The installer now allows the user to customise the installation.
Note: In this example the default settings are used. Only customise the installation if the
user wants to enable or disable particular features.
Click Next > to continue and accept the selection of default Features.
Specify the Named instance and Instance ID of the SQL Server. Make sure the Default
Instance is selected and then click Next >.
The installer now allows the Service accounts to be created, click Next > to except the
default Accounts.
Configure the Database Engine Configuration, click Next > to accept the default settings.
The user has the option of sending information to Microsoft. The default option for this
feature is disabled. Unless the user wants to register information with Microsoft leave this as
disabled and click Next >.
Once all configuration settings have been made SQL will complete the installation process
(the installation may take some time).
Once the installation process has completed, the Complete window is displayed.
Click Close to close the Installer.
Create Table Entries in SQL to Store Schedule Data

The user needs to create the required table entries in SQL for the Schedule data to be
stored. This is done by running a series of scripts to create the tables. By allowing the user
to run the scripts the Project Administrator can use any version of SQL (full or Express) for
the Scheduler tables to be stored.
Start the SQL Server Management Studio as an Administrator:
Click Start > All Programs and select Microsoft SQL Server 2008 R2 Folder.
Right click on SQL Server Management Studio and select Run as Administrator.
The user will be asked if it wants to run the SQL Server Management Studio in
Administrator mode. Select Yes.
The user will need to login into the SQL Server, if the user has followed the installation steps
so far in this document, the user should be able to login with the default settings, click
Connect.
The Microsoft SQL Server Management Studio is loaded. The first step is to create a new
database for the Global Scheduler to store the schedule data.
Right click Databases and select New Database to display the New Database window.
The user will need to change the following fields:
• Database name: GlobalAddInDB
• Owner: sa
• Initial size(MB): 300MB
Click OK when the fields are correct to create the database.
Note: Make sure that the case for GlobalAddInDB is correct. The size is an initial size and
may vary for various deployment scenarios. This will be used late in the installation
process.
A new Database called GlobalAddinDB is created and is displayed under the Databases
node in the Explorer.
Create a new login to all the Service to read and write data to the database. Using the
explorer navigate to Security > Logins.
Right click Logins and select New Login to display the Login - New window.
The user will need to make the following changes:

• Login name: GlobalAddInUser
• Click on SQL Server authentication
• Enter a Password
• Confirm Password
• Deselect User must change password at next login check box.
• In Default database select GlobalAddinDB from the drop-down list.
• In Default language select English from the drop-down list.
Do not close the window.
The user will need to grant the User with SQL privileges. To do this select the Server Roles
page in the Login - New window.
Select all the Server roles check boxes to provide full privilege, these are:
• bulkadmin
• dbcreater
• diskadmin
• processadmin
• public
• securityadmin
• serveradmin
• setupadmin
• sysadmin
Do not close the window.
The user needs to map the User to the database. To do this select User Mapping page in
the Login - New window.
In the Users mapped to this login section, select the Map check box next to
GlobalAddInDB.
Then in the Database role membership for: GlobalAddInDB section, select the following
check boxes:
• db_accessadmin
• db_backupoperator
• db_datareader
• db_datawriter
• db_ddladmin
• db_denydatareader
• db_denydatawriter
• db_owner
• db_securityadmin
• public
Click OK when the fields are correct to create the login.
A new login called GlobalAddinUser is created and is displayed under the Logins node
and a registered user for the database under the Databases > GlobalAddInDB > Security
> Users node in the Object Explorer.
Note: Make sure that the case for GlobalAddInUser is correct. The size is an initial size
and may vary for various deployment scenarios. This will be used late in the
installation process.
Set Up Table Schemas for Global Databases

To set up the table schemas for the Global database a series of installer SQL scripts need to
be run. The scripts will be provided as part of the install. The PopulateDatabase.bat file will
run the scripts in Microsoft SQL Server Management Studio.
Before executing the PopulateDatabase.bat file, make sure that the Database and user is
already created (refer to Create Table Entries in SQL to Store Schedule Data).
Run PopulateDatabase.bat file and do the following:
Type the SQL Server instance name. For example: server\SQLEXPRESS.

Type the Database name. It is recommended to use GlobalAddInDB.
If the information provided is correct, the following information is displayed indicating the
success of creating tables, Procedures and functions for Global Services.
Open Microsoft SQL Server Management Studio to view the SQL Database which
contains the saved Tables, Procedures and functions.
Common Errors
If the information provided is incorrect or missing, the following errors are displayed:
Example 1: both server and database contain a word 'name':
Example 2: both server and (or) database name does not exist:
2.4 Plant Installation

The global client is now automatically installed with the base product. Both the WCF and
RPC dlls are installed but the product is now configured WCF ready, with the default
configuration being HTTP with No security and port set to 8000. If installing by running the
setup.exe, the installation of AVEVA E3D™ will be configured not to support AVEVA Global
Services.
It is possible to run the AVEVA Global Services installation from setup.exe (which will
assume Administrator privilege) or from the Command Prompt with Administrator
privileges by running the following command:
Note: The following is an example of a silent install, the users installer location path maybe
different to that of the example and the log file path can be changed. If the user runs
the silent install without Administrator privileges the install will fail without an obvious
reason.
msiexec /I "C:\Temp\Downloads\E3D\Plant\Plant1.10.msi" /LV

.\plant.log /qb- GLOBALMANAGERSERVICEHOST=hostname
GLOBALNOTIFICATIONSERVICEHOST=notifyname
The user will need to replace the following strings:

• hostname - The hostname of the computer that the AVEVA Global Manager Service
will be installed on.
• notifyname - The notification service host name of the computer that the AVEVA
Global Notification Service will be installed on.
• /qb - This forces the install to be silent, by removing this option the installation
process will be interactive.
The user can run the installation without the log file, but if the install fails it will be difficult to
determine what went wrong.
If installing without the -qb silent installation flag, the user will need to step through the
normal installation process.
If installing with silent install the user will not be prompted for any input. The installer will
automatically go through the installation options as follows:
The install will configure itself.
Depending on privileges the User Access Control may ask the user to confirm to run the
installation, click Yes.
The installation will then run.
Once the installation has completed the installer window will close.
2.5 Table Schemas for Global Databases

The table schemas for the Global database has a series of scripts need to be run. The
scripts will be provided as part of the install. There are 5 scripts which must be run in the
order defined:
1. SP_CreateTable.sql
2. DayOfWeekFunction.sql
3. SP_SelectSchedulesForToday.sql
4. SP_UpdatetblClaimedItemsList.sql
5. SP_UpdatetblLocationWiseSchedules.sql
Once all scripts are run, the SQL Database will have the Tables, Procedures and functions
displayed.
2.6 Configure the Application Pool

Select the application pool ASP.NET v4 and under the Actions pane click Advanced
Settings to display the Advance Settings window.
Select Identity to display a browse button.

Click on the browse button to display the Application Pool Identity window.
Select Built-in account (if not already selected). From the drop-down menu select
LocalSystem.
Click OK to submit and close the Advanced Settings window.
Select File > Exit to close IIS.
Notification Service
3 Notification Service
The Notification Service can be installed via the UI, or via silent install; if install via the UI
then the installation will assume all default values. The default values will install the service
and the notification project onto the machine. The service will be automatically started and
therefore immediately available for subscriptions to be configured.
It is possible to override some of the key settings with the silent install by using the following
command line:
The two variables NOTIFYPROJECT and LOGFILE NAME are optional overrides:
• NOTIFYPROJECT - the file location where the Notification Project is to be installed
• LOGFILENAME - the name of the log file that the service will report errors and
warnings
This makes the following changes to the file AVEVA.SharedServices.DBLib.dll.config
Note: Shared Services includes the original 3 Global Services from E3D1.1 as well as the
new Shared Service:
Notification Service
The 3 AVEVA Global … Services are the original E3D services. The AVEVA Notification
Service is the new Shared Services Notification Service used by Engineering. It is not
possible to run both the Shared Services and Global Notification Managers on the same
host machine as this has a communication channel conflict.
The AVEVA Manager Service has an IIS dependency; if IIS has not be configured on the
machine that the services is being installed on then the AVEVA Manager Service will not be
installed.
It is possible to install the AVEVA Notification Service by silent install by defining only that
feature on the silent install command line:
3.1 Engineering and Administration

AVEVA Administration and AVEVA Engineering can also be installed using the UI, or via
silent install. The default installation will result in both Administration and Engineering
assuming that the service is running on the local machine.
At deployment this is unlikely, so it is possible to configure both products to determine the
machine the notification service is running on via a variable override
and
The variable NOTIFYSERVER is an optional override:

• NOTIFYSERVER- the hostname of the machine that Notification Server has been
installed on
This makes the following changes to the file AVEVA.SharedServices.Client.dll.config.
Note: If AVEVA Engineering or AVEVA Administation is installed using the UI, or by silent
install without the NOTIFYSERVER override, the highlighted values will need to be
changed. This is done by editing the AVEVA.SharedServices.Client.dll.config file to
indicate the hostname of the machine that the AVEVA Shared Services Notification
Service has been installed on.

Shared Services Installation Guide

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Shared Services Installation Guide

Загружено:

Авторское право:

Доступные форматы

AVEVA Shared Services 3.

3rd Party Software

Date Version Comments / Remarks

Shared Services Installation Guide

Shared Services Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

Introduction to Global Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1

Notification Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1

1 Shared Services Installation

1.1 Silent Installation

msiexec /I "C:\temp\Downloads\SharedServices3.30.msi” /LV

Global Server and Global Services on Different Machines

The advanced setting allows the SQL Database to be defined.

Complete Silent Install

Click Next to display the End-User License Agreement window

Select Install to install the AVEVA Global Services.

Click Finish to complete the installation.

2 Introduction to Global Services

The full deployment is spread between three installers, these are:

2.2 IIS Configuration

Enable IIS on the Machine

Windows Feature takes a short while to load.

Enable IIS8 and WinServer 2012

2.3 SQL Configuration

The installer now allows the user to customise the installation.

Create Table Entries in SQL to Store Schedule Data

The user will need to change the following fields:

• Database name: GlobalAddInDB

• Initial size(MB): 300MB

Click OK when the fields are correct to create the database.

The user will need to make the following changes:

Set Up Table Schemas for Global Databases

Type the SQL Server instance name. For example: server\SQLEXPRESS.

2.4 Plant Installation

msiexec /I "C:\Temp\Downloads\E3D\Plant\Plant1.10.msi" /LV

The user will need to replace the following strings:

2.5 Table Schemas for Global Databases

2.6 Configure the Application Pool

Select Identity to display a browse button.

Select File > Exit to close IIS.

3.1 Engineering and Administration

The variable NOTIFYSERVER is an optional override:

Вам также может понравиться