The AVEVA Shared Service Notification is the communications mechanism which firmly supports the Interdisciplinary project data work flow, as it allows for the exchange of object data between the users of the AVEVA Engineering Tags application.
Each user will have to subscribe to a notification topic which could be object data from within disciplines of an AVEVA Engineering project.
Data changes/modifications made within the subscribed data view generates a notification which is stored in a specified Dabacon database. Subscribing applications can then request (Getwork) a list of notifications against a subscription from the notification service.
Basically, a notification is raised for an object data change after a status promotion has been initiated. This could be when the object is promoted to an ‘Approved’ status level.
The VERCON mechanism will then trigger a dynamic ‘Issue’, in which the modified object will be issued from an extract level to the master databases (Released data).
Users within other disciplines who are subscribed to the source of the change will then be notified (after a
‘Get Work’), and they can chose whether to accept the changes on that object or not (From the Revision Center form).
The notification service works on a ‘Server’ ‘Client’ basis, where the Engineering Tag users can have their machines setup as clients, and a Notification Server will be nominated. Each user will then have to point their client dll’s to this Server system.
This section covers the configuration and setup for the shared services mechanism according to the diagram shown:
www.aveva.com
Setting up a Notification Service Server
The AVEVA Shared Services product must be installed on a nominated ‘Server’ machine, which is made accessible to required (allowed) client systems.
It could be installed in the system/machine of a client/user. Although one Notification Service server location must be referenced by all users.
The Shared Services installation comes as a Separate Product Lifecycle (SPL) install, so should have it’s
‘custom evars’ batch file containing a default pointers to sample and catalogue projects (amongst others) pointing to the correct project. This must be the same project that is accessed by the users. This batch file may be found in the location shown:
Navigate to the ‘Custom Evars’ batch file in the ‘Projects 3.2’ (for example) folder of the AVEVA Shared Services installation as shown:
121
www.aveva.com
© Copyright 1974 to current year.
Open and display the contents of the ‘Custom Evars’ batch file in a suitable text application to view the contents of the file.
Click File > Save to save the changes made to the file.
Ensure that the Shared Service Notification Service is started:
Open and display the Windows ‘Services’ application console by navigating to:
Control Panel\All Control Panel Items\Administrative Tools
Select the ‘AVEVA Shared Service Notification Service’ entry, and click the ‘Start’ control, to get the services started.
This essentially starts the Notification Shared Services server started and ready to receive and transmit data between subscribers and sources.
This services should be started by default normally after the Shared Services 3.1 product has been installedwww.aveva.com
Notification Service Client
The Notification Service Client is basically the machine/systems of the users who will be working with the AVEVA Engineering application, creating/modifying or manipulating data.
AVEVA Shared Services product does not have to be installed on the client users’ machines. The installation locations of both the AVEVA Engineering 14.1 and Administration contain an
‘AVEVA.SharedServices.Client.dll.config’ file. The contents of these files will have to be manually edited to point to the ‘Shared Services notification server’.
The files can be found in the installation location of the Engineering 14.1 and Administration products within the clients’ machine:
The installation location of the products could be different from that displayed aboveNavigate to and select the config file contained within the AVEVA Engineering installation as shown, open and display the contents on this file in a suitable text application. Then modify the contents by including the machine/system name of the server in which the Notification service has been installed as shown below:
The server names being used in the nodes are purely for example. The administrator must include the actual server names of their notification service server123
www.aveva.com
© Copyright 1974 to current year.
Repeat the same actions described for the copy of the ‘AVEVA.SharedServices.Client.dll.config’ file contained within the AVEVA Administration product installation location.
This will make it possible for the shared services notification manager to be able to receive information from the LEXICON module of the AVEVA Administration installation.
The Shared Service Notifications service does not have to be started within the client machine.
These actions carried out will allow the communication links between the Notification Service server, and the clients to be established.
Notification Proxy Agent
Having configured and setup the Notification Service server and the clients, it is essential to get the Notification Proxy Agent up and running as well.
The Notification Proxy Agent is an application which caches notifications raised in the Engineering application when the Shared Services Notification Service is unavailable.
Data change notification will be cached in a queue system until the resumption of the Shared Services server availability. This will then release the information held for downstream consumption.
It should be noted that the subscriber might receive the released notifications about 10minutes after the shared services server is made available.
The AVEVA Notification Proxy agent is silently installed on the clients’ machine during the installation of the AVEVA Engineering product, or can be installed on its own via an executable file,
The installation location will also include an ‘AVEVA.SharedServices.Client.dll.config’ file which will have to be modified as described earlier.
www.aveva.com
Display the selected file and make the changes as demonstrated previously:
The Notification Proxy Agent application installs silently during the installation of the AVEVA Engineering 14.1 productFinally, ensure that the AVEVA Shared Service Notification Proxy Agent service is started within the client’s machine:
The Notification Services communication links and setup is now complete.
125
www.aveva.com
© Copyright 1974 to current year.