Start a Global Project

Once the Global daemon files have been configured, Global will operate in the same way that it has historically done so for RPC.

Start a Global Project section summarises in brief how to start an instance of Global on a machine. Throughout the section reference is made to the Global User Guide which describes then standard process of starting a daemon. Any differences in WCF configuration are clearly highlighted in this section.

The administrator must first prepare a project in the base product for use with Global refer to the Global User Guide (section 4.2 Making the Project Global).

In brief the administrator must load the Admin module within the base product and issue the following commands at the command line to convert the project for Global use:

Lock

make global

unlock

The user must continue to refer to the Global User Guide to Initialise the Hub location.

Navigate to base product folder:

C:\AVEVA\plant\PDMS12.1.1

Referring to Enable RPC or WCF Security locate the file GlobalWCFClient.config and set the protocol key within the GlobalWCFClient.config file to WCF.

Global Server is supplied with singleds.bat and multids.bat sample batch files that can be used to start the Global daemon. The operation of these batch files is consistent with that of RPC, however these is an addition of a new GLOBAL_PROTOCOL key which controls whether RPC or WCF is to be used.

Refer to the Global User Guide (section 4.8.3 Single Project Service).

Navigate to the Global Server install path:

C:\AVEVA\GlobalServer12.1.1

Open the singleds.bat file in a text editor.

By default the GLOBAL_PROTOCOL will be set to RPC and WCF will be included as a remark.

Locate the following:

set GLOBAL_PROTOCOL=RPC

rem set GLOBAL_PROTOCOL=WCF

Delete the RPC line and uncomment the WCF as follows:

set GLOBAL_PROTOCOL=WCF

Modify the projects_dir variable to point to the base product project files.

set projects_dir=C:\AVEVA\plant\PDMS12.1.1\project