Process Expert

EIO0000001255 11/2017

Process Expert
Installation and Configuration Guide
11/2017
EIO0000001255.09

[Link]
 The information provided in this documentation contains general descriptions and/or technical
characteristics of the performance of the products contained herein. This documentation is not
intended as a substitute for and is not to be used for determining suitability or reliability of these
products for specific user applications. It is the duty of any such user or integrator to perform the
appropriate and complete risk analysis, evaluation and testing of the products with respect to the
relevant specific application or use thereof. Neither Schneider Electric nor any of its affiliates or
subsidiaries shall be responsible or liable for misuse of the information contained herein. If you
have any suggestions for improvements or amendments or have found errors in this publication,
please notify us.
You agree not to reproduce, other than for your own personal, noncommercial use, all or part of
this document on any medium whatsoever without permission of Schneider Electric, given in
writing. You also agree not to establish any hypertext links to this document or its content.
Schneider Electric does not grant any right or license for the personal and noncommercial use of
the document or its content, except for a non-exclusive license to consult it on an "as is" basis, at
your own risk. All other rights are reserved.
All pertinent state, regional, and local safety regulations must be observed when installing and
using this product. For reasons of safety and to help ensure compliance with documented system
data, only the manufacturer should perform repairs to components.
When devices are used for applications with technical safety requirements, the relevant
instructions must be followed.
Failure to use Schneider Electric software or approved software with our hardware products may
result in injury, harm, or improper operating results.
Failure to observe this information can result in injury or equipment damage.
© 2017 Schneider Electric. All Rights Reserved.

2 EIO0000001255 11/2017
 Table of Contents

Safety Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 1 Process Expert System Infrastructure . . . . . . . . . . . . . . 11
Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Virtual Machine Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Virtual Machine Licensing Considerations. . . . . . . . . . . . . . . . . . . . . . 22
Physical Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Physical Architecture Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Chapter 2 Installing Service Pack 1 for Process Expert 4.3 . . . . . . 33
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Service Pack 1 General Installation Information . . . . . . . . . . . . . . . . . 36
Installing Service Pack 1 for Process Expert 4.3 . . . . . . . . . . . . . . . . . 40
Migrating Databases of Process Expert 4.3 to Service Pack 1 . . . . . . 42
Starting the Process Expert 4.3 Service Pack 1 System Server . . . . . 43
Modifying, Repairing, and Removing Process Expert 4.3 Service
Pack 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Chapter 3 Process Expert 4.3 System and Installation
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
General Installation Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Installing the Controller Simulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Chapter 4 Installing Process Expert . . . . . . . . . . . . . . . . . . . . . . . . 63
Installing Process Expert for the First Time . . . . . . . . . . . . . . . . . . . . . 64
Installing Supervision Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Chapter 5 Updating Process Expert . . . . . . . . . . . . . . . . . . . . . . . . 67
5.1 About Updating Process Expert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Using Templates Supplied with the Process Expert Update . . . . . . . . 73
Stopping and Starting Caché. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
5.2 Migrating Process Expert Databases . . . . . . . . . . . . . . . . . . . . . . . . . 80
Migrating Databases of Process Expert 4.2 or V4.2 SP3 to V4.3 . . . . 80

EIO0000001255 11/2017 3
 5.3 Installing the Process Expert Update . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Installing the 32-Bit Process Expert Update. . . . . . . . . . . . . . . . . . . . . 83
Installing the 64-Bit Process Expert Update. . . . . . . . . . . . . . . . . . . . . 84
Chapter 6 Configuring Process Expert . . . . . . . . . . . . . . . . . . . . . . . 87
Using Configuration Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Configuring the System Server and Clients . . . . . . . . . . . . . . . . . . . . . 93
Configuring the Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Managing Participant Extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Activating the Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Chapter 7 Starting Process Expert . . . . . . . . . . . . . . . . . . . . . . . . . . 115
System Server Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Backing Up and Restoring Process Expert Databases . . . . . . . . . . . . 118
Starting the System Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Starting the Engineering Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Chapter 8 Modifying, Repairing, and Removing Process Expert . . . 127
Modifying The Process Expert Installation . . . . . . . . . . . . . . . . . . . . . . 128
Repairing Process Expert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Removing Process Expert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Chapter 9 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Troubleshooting Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Troubleshooting the System Server. . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Troubleshooting the Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Troubleshooting Client/Server Communication . . . . . . . . . . . . . . . . . . 141
Troubleshooting USB Port Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Troubleshooting the Caché Database . . . . . . . . . . . . . . . . . . . . . . . . . 145
Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Appendix A Installing the Floating License Manager . . . . . . . . . . . . . . 149
Installing the Floating License Manager. . . . . . . . . . . . . . . . . . . . . . . . 149
Appendix B Installation of DTMs by Using a Response File . . . . . . . . 151
Installing DTMs by Using a Response File . . . . . . . . . . . . . . . . . . . . . 151
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

4 EIO0000001255 11/2017
 Safety Information

Important Information

NOTICE
Read these instructions carefully, and look at the equipment to become familiar with the device
before trying to install, operate, service, or maintain it. The following special messages may appear
throughout this documentation or on the equipment to warn of potential hazards or to call attention
to information that clarifies or simplifies a procedure.

EIO0000001255 11/2017 5
PLEASE NOTE
Electrical equipment should be installed, operated, serviced, and maintained only by qualified
personnel. No responsibility is assumed by Schneider Electric for any consequences arising out of
the use of this material.
A qualified person is one who has skills and knowledge related to the construction and operation
of electrical equipment and its installation, and has received safety training to recognize and avoid
the hazards involved.

6 EIO0000001255 11/2017
 About the Book

At a Glance

Document Scope
This document explains how to install Service Pack 1 for Process Expert 4.3.
It also describes how to:
 Install Process Expert 4.3, which is prerequisite for installing the service pack.
 Configure the software.
 Start the system server and engineering clients.
 Migrate databases of earlier versions of Process Expert to make them compatible with the
current version.
 Repair, modify, and uninstall the software.

It is written for users who have a working knowledge in the design of control systems, including
supervision functions.
NOTE: Read and understand this manual and the Process Expert Licensing Guide before
installing and using Process Expert.
The Process Expert Licensing Guide is located in the Process Expert Installation and Licensing
Guides folder of the software installation package.

Validity Note
This document is valid for Service Pack 1 (SP1) for Process Expert 4.3 or later.

Related Documents

Title of documentation Reference number

Process Expert Licensing Guide EIO0000001261 (eng)
Process Expert User Guide EIO0000001114 (eng)
Schneider Electric Floating License Manager User Manual EIO0000001078 (eng)

You can download these technical publications and other technical information at
[Link], PES Document Downloads section.
Registration required.

EIO0000001255 11/2017 7
PlantStruxure PES Support Portal
Visit [Link] for support, software updates, and latest information on
Process Expert.
Registration required.

Trademarks
Schneider Electric, Process Expert, Unity Pro, and Citect are trademarks of Schneider Electric SE,
its subsidiaries, and affiliates.
Microsoft, Windows, and Internet Explorer are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.
Adobe and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated
in the United States and/or other countries.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
Caché and InterSystems are trademarks of InterSystems Corporation.
InstallShield is a registered trademark of Flexera Software in the United States and other countries.
PassMark is a registered trademark of Passmark Software Pty Ltd in Australia and other countries.
Other names are registered trademarks or trademarks of their respective owners.

Product Related Information

Process Expert clients authenticate users against Microsoft® Windows® Active Directory®
domain services or the Windows® user database of the local computer. Using the Process Expert
system server does not require authentication.

WARNING
UNINTENDED EQUIPMENT OPERATION
 Allow only authorized personnel with expertise in the design and operation of control systems
to program, install, alter, and apply this product.
 Follow local and national safety codes and standards.
Failure to follow these instructions can result in death, serious injury, or equipment damage.

The examples in this manual are given for information only.

8 EIO0000001255 11/2017
 WARNING
UNINTENDED EQUIPMENT OPERATION
Adapt examples that are given in this manual to the specific functions and requirements of your
industrial application before you implement them.
Failure to follow these instructions can result in death, serious injury, or equipment damage.

EIO0000001255 11/2017 9
10 EIO0000001255 11/2017
 Process Expert
System Infrastructure
EIO0000001255 11/2017

Chapter 1
Process Expert System Infrastructure

Process Expert System Infrastructure

Overview
This chapter provides a high-level understanding of the main software components that form the
Process Expert system infrastructure. It also describes how these components can be installed on
various computers depending on the tasks you want to accomplish. For example, engineering only
or runtime-related tasks.

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
Software Architecture 12
Virtual Machine Usage 15
Virtual Machine Licensing Considerations 22
Physical Architecture 24
Physical Architecture Examples 27

EIO0000001255 11/2017 11
System Infrastructure

Software Architecture

Overview
The Process Expert system infrastructure is based on a client/server architecture with integrated
as well as third-party software components. It allows you to run multiple clients with one server to
access the tools that are required in engineering time and during operation.
By using multiple clients, several users can work simultaneously on the same system or perform
similar tasks on various systems.
To use the various software components described in this topic, you need to purchase and activate
the necessary licenses (see EcoStruxureTM Hybrid DCS, Licensing Guide).
NOTE: Process Expert and Supervision software components are available in separate installation
packages (see page 50).

Process Expert Software Components

The Process Expert installation package contains the following software components, which form
the system infrastructure:
 A system server: Manages system data, software Participant activity, and requests from clients.
The user interface consists of a console that allows you to monitor server activity.
 Engineering clients: Provide a user interface that gives access to Process Expert platform
resources, such as explorers and editors. In addition, engineering clients display software
Participants with which you can perform in-depth configurations. Together, these resources and
tools allow you to design and maintain systems. You can use several clients at the same time.
 Operation clients: Provide a user interface that allows you to view system components during
runtime (for example, controllers, process objects, process data, and so on) for monitoring and
troubleshooting purposes. These clients display software Participants too. They require a
Supervision client to run in parallel, which is the entry point to runtime navigation services
(RTNS) (see EcoStruxureTM Hybrid DCS, Runtime Navigation Services, User Guide). You can
use several clients at the same time.
 Virtual machines: Provide the services of software Participants (for example Control and
Supervision Participants), which are required in engineering time and during operation. They
are run by third-party software and use the Microsoft® Windows® operating system. Virtual
machines can be accessed by the system server and clients. They can be used in various
configurations depending on the performance of the computers they are installed on and the
number of concurrent users.
For details, refer to the topic describing virtual machine usage (see page 15).
 A database: Consists of several physical databases, which contain template libraries and user
data related to the systems that you create with Process Expert. Each system has its own
database. The database is created during the first system server start and is managed by third-
party software (see page 51), which is included.
NOTE: To manage usage rights and application size Process Expert also utilizes
Schneider Electric license management software (see page 53).

12 EIO0000001255 11/2017
 System Infrastructure

The following figure shows a simplified model of the software architecture of Process Expert.

EIO0000001255 11/2017 13
System Infrastructure

Supervision Software Components

Process Expert also uses the following software components during runtime:
 Operation server: I/O, alarm, trend, and report servers can be installed on one or distributed
over several computers. One computer requires the configuration tools to be installed. These
consist of various editors, which allow you to complete the deployment of Supervision projects
on the network.
 Supervision clients: Provide a user interface that allows you to monitor and/or control the
process during operation. A Supervision system can be made of several clients, which can be
used simultaneously.
Supervision clients can be either:
 Control clients, which allow you to control the process during operation.
 View-only clients, which allow you to monitor the process. They cannot interact with the
process during operation.
Each operation server also acts as a control client across the Supervision system architecture.
 OPC Factory Server: Acts as an interface between the program and the I/O server and
manages OPC items because OFSOPC is the default communication protocol of systems that
you create with Process Expert.
The following figure shows the Supervision client/server part of a Process Expert architecture.

14 EIO0000001255 11/2017
 System Infrastructure

Virtual Machine Usage

Overview
A virtual machine (VM) provides Software Participant services, which are required to complete the
system engineering life cycle. These services are also required if you want to use the runtime
navigation services.
Each VM that you install, gives you access to a limited number of VM instances (see page 22).
Each VM instance can provide a limited number of Participant sessions of each Participant.
NOTE: You must activate the Microsoft® Windows® operating system of each VM with a suitable
product key (see page 22). You need to purchase product keys separately.

Performance Considerations
VMs are demanding in terms of hardware resources and their usage may be limited by the
performance of your computer (see page 46). Especially, sufficient RAM needs to be installed so
that the amount of memory allocated to the VM when it is started is available on the host computer
as free memory.
The amount of physical memory that is allocated to the VM (see page 96) can be configured. This
amount is not available to the host computer anymore while the VM is running. The VM starts as
soon as you start a component that uses it, this is the system server and/or the engineering client.
For optimal VM performance:
 Avoid running simultaneously with Process Expert:
 Hyper-V: If it is installed and enabled the VM cannot use it.
 Other virtualization software and/or hypervisors.

 If you need to run Process Expert inside a virtual machine, refer to the Application Note Running
Process Expert in a Virtual Environment, which is available on the PES Support Portal. It
describes the hardware requirements that are specific to this application.

EIO0000001255 11/2017 15
System Infrastructure

Software Participant Sessions

Each instance of a VM provides the following Participant sessions, also called slots.

Software Participant Number of slots per VM instance

Control Participant 2
Advantys Configuration Software (ACS) 1
Supervision Participant 1

When no more Participant sessions are available because the corresponding slots are used up,
Process Expert informs you that it cannot provide the Participant services.
For more information on using Participants, refer to:
 The Participant Services User Guides.
 The help of software Participants (see EcoStruxureTM Hybrid DCS, User Guide).

16 EIO0000001255 11/2017
 System Infrastructure

Virtual Machine Instances and Sessions

When configured, each installation of a VM makes it possible to use more than one instance of that
VM. Each instance giving you access to an additional set of Participant sessions.
For example, if you allow the execution of 2 instances of a VM that is installed with the engineering
client, a user can use up to 4 Control Participant slots simultaneously. Each VM instance providing
2 of these slots. The user can, for example, refine 2 Control projects and configure 2 controllers at
the same time.
In addition, various instances of a VM can be accessed by different client PCs. Each instance of
the VM being accessible only to one client PC at a time. This means that the slots of one instance
of a VM cannot be shared by several client PCs. On each PC an engineering and/or operation
client can be installed. It is irrelevant whether the same user is logged on to more than one client
PC. This rule applies when the VM instance is accessed through a Participant window (for
example, when you use the Configure or Refine command).
In this example, 2 instances are allowed for the VM installed on the system server computer. When
client PC A accesses an instance of this VM through the Participant window and uses only one
slot, client PC B cannot access the remaining slots of this VM. They are reserved for client PC A.
Client PC B will use the second instance of the VM. If a third client PC tries to access the system
server VM through a Participant window, no Participant services can be provided because this
would require a third VM instance.

EIO0000001255 11/2017 17
System Infrastructure

Sharing the slots of a VM instance is only possible when:

 The VM instance is accessed simultaneously by several client PCs but only one of them is
accessing it through a Participant window. The other client PCs need to access it without using
the Participant window (for example, by using the Generate or Build command). In this case,
slots of the VM instance are assigned to client PCs on a first come, first served basis.
 The VM instance is accessed from the same client PC, for example when the engineering and
operation clients are used simultaneously. It does not matter if the VM instance is accessed
through a Participant window.

NOTE: The use of instances of a VM by more than one user needs to satisfy the VM licensing terms
(see page 22).

18 EIO0000001255 11/2017
 System Infrastructure

Virtual Machine Usage by Software Component

The following figure shows the most common VM usage scenarios in a 64-bit Process Expert
infrastructure consisting of a system server with three client PCs connecting to it. On each PC an
engineering and/or operation client is installed. Dotted double-ended arrows represent the
connection between the system server and a client. Solid double-ended arrows show which VM
the Process Expert component is configured to use.

NOTE: The 32-bit version of Process Expert allows setting up only Operation Client B.

EIO0000001255 11/2017 19
System Infrastructure

The table describes the various possibilities of VM usage that you can configure for each
Process Expert component and their limitations.

Software component
VM that the component can use
requiring VM services
System server VM Engineering client VM (installed on
engineering station)
System server Yes Yes
Engineering client Yes (2) (3)
Yes(3)
By default, the engineering client uses
the local VM to help improve
performance but it can be configured to
use the system server VM instead.
Operation client Yes(1) (2) (3) Yes(1) (3)
NOTE: An operation client Mandatory for 32-bit version. When the operation and engineering
installation does not include clients are installed on the same PC, the
a VM. operation client can use the VM of the
engineering client (64-bit version only).

(1) Each operation client uses 1 Control Participant slot of a VM. The other slots remain available
to the engineering client installed on the same PC.
(2) The system server VM must be configured to allow clients to use it.
(3) When several clients access the same VM, they use instances of that VM on a first come, first
served basis. In the case where more than 1 instance of a VM is allowed, once no more slots
are available to a client, another instance of the VM is started as long as the number of instances
is within the limit.
If clients are configured to use the local VM but can also use the VM of the system server, the
local VM is used first. Once the maximum number of allowed local VM instances is reached, the
VM of the system server is used.

20 EIO0000001255 11/2017
 System Infrastructure

VM Usage Recommendations
To help improve performance, it is recommended to allow the usage of VMs on the following
computers:
 For use by engineering clients: On the local PC (engineering station).
 For use by operation clients: On the system server computer.

The obligation for clients to use their local VM or the right to use the system server VM are
configurable after you install a Process Expert component by using its Configuration wizard
(see page 95).
In addition, the configuration wizards (see page 95) allow you to configure the maximum number
of VM instances that can run in the system server and engineering clients.
NOTE: By default, when you install Process Expert VMs are installed and configured
(see page 95) as per these recommendations.

VM Time Zone
By default, the time zone of the operating system of the VM is set to (UTC-08:00) Pacific
Time (US & Canada).
If needed, you can synchronize the time zone of the VM with the one of the host computer or set
another time zone (see page 112).

EIO0000001255 11/2017 21
System Infrastructure

Virtual Machine Licensing Considerations

Overview
You must purchase licensing rights to use VMs that you install for various Process Expert
components. VMs use the Microsoft® Windows® 7 Professional operating system.
This objective of this topic is to help you understand VM licensing concepts and determine the
number of VM licenses you need to purchase. It also outlines various license types that Microsoft®
offers.
NOTE: The information in this topic is provided for guidance only. It does not constitute legal advice
or interpretation. You must ensure that you comply with Microsoft® Software License Terms in any
case. For more information, contact your local software distributor or visit
[Link]/licensing.

Virtual Machine Licensing Principles

The VM licensing terms of Microsoft® limit the number of instances of an activated VM that 1 user
can use simultaneously at 4.
2 users cannot use the instances of a VM simultaneously with only 1 license.
If, for example, 2 users are using 2 instances of the same VM each, then 2 licenses are required.
If they do not work simultaneously, only 1 license is required.

Determining License Needs

You need to determine how many licenses you need to purchase, depending on the concurrent
usage of Process Expert components that use VMs.
For volume licenses, based on the Microsoft® VM licensing principles, the rule is: Number of
licenses = number of users using a VM simultaneously.
For example, consider the following Process Expert setup:
 PC_1: System server with VM
 PC_2: 1 engineering client with VM
 PC_3: 1 engineering client with VM and 1 operation client

The operation client is configured to use the VM of the system server.

The total number of VMs installed is 3: 1 for the system server and 1 for each engineering client.
At any time, 2 users (User_A and User_B) work simultaneously in the following way:
 No one works on PC_1.
 User_A working on PC_2 uses the VM on PC_2.
 User_B working on PC_3 uses:
 The VM on PC_3 when working with the engineering client.
 The VM on PC_1 when working with the operation client.

The number of licenses that is required is 2 even if sometimes User_B uses both engineering and
operation clients simultaneously on PC_3.

22 EIO0000001255 11/2017
 System Infrastructure

License Types
The table outlines the various Microsoft® license types that are available to activate VMs.

License type Description Operating system of the Activation method

computer
Individual Usage rights for 4 instance of a Microsoft® Windows® 7 or 8 Through product key.
Microsoft® Windows® 7 VM. Professional
Professional license One-time purchase.
Software Assurance (SA) Contract with Microsoft®, 2 possibilities:
which details the software type  Through multiple
and quantity that you want to activation key
run. (MAK)
Monthly fee.  Through Key
Virtual Desktop Access Client Contract with Microsoft®, Management
Access Licenses (VDA CAL) which details the software type Service (KMS)
and quantity that you want to server
run. Provided through the
Monthly fee. Microsoft® Volume
VDA CAL is included with the Licensing Customers
SA. portal.
Windows Server Standard The license includes rights to Microsoft® To run the
license run 2 VMs; however you Windows Server® 2012 R2 Process Expert VM,
cannot use these rights for the you need to purchase
Process Expert VM. either:
 SA
The license includes rights to Windows Server Data Center
run an unlimited number of  VDA CAL
VMs; however you cannot use  Product keys
these rights for the
Process Expert VM.

NOTE: For details, contact your local software distributor or visit [Link]/licensing.

Activating Licenses for VMs

Configuration wizards allow you to activate licenses for VMs by using a product key or through
KMS server.
For more information, refer to the topic describing VM activation (see page 114).

EIO0000001255 11/2017 23
System Infrastructure

Physical Architecture

Overview
Process Expert provides the flexibility to install software components on various physical
architectures depending on the performance of the computers, the number of concurrent users,
and your work method. Client stations and servers need to be connected to each other on an
Ethernet network by a cable connection. A cable connection to the control network is also
necessary.

Physical Architecture Description

Typically, the physical architecture on which a Process Expert infrastructure is running consists of
computers that have the following roles and connections.

Role of the computer Number of Description computer connected

computers to
Servers
System server 1 Runs Process Expert System Server. Ethernet
station/server
network.
Ethernet control
network (if the virtual
machine of the
system server is
used).
Operation server 1 or more Runs Supervision server software to collect Ethernet
real-time data from devices and treat it station/server
according to its nature (for example, alarms or network.
trends). Ethernet control
Each operation server also acts as a control network.
client.
Clients
Engineering station 1 to n Runs an Engineering Client to engineer and Ethernet
maintain systems. station/server
Requires the services of a virtual machine, network.
either locally or on the system server. Ethernet control
network (if the local
virtual machine is
used).

24 EIO0000001255 11/2017
 System Infrastructure

Role of the computer Number of Description computer connected

computers to
Operator station 1 to n Runs Supervision control or view-only client Ethernet
software to monitor and control the station/server
automation system. network.
Requires an Operation Client to do online Ethernet control
diagnosis by using runtime navigation network (required to
services (see EcoStruxureTM Hybrid DCS, use the Operation
Runtime Navigation Services, User Guide). Client).
Operation clients require the services of a
virtual machine.

NOTE: computers can cumulate several roles in which case you need to install the software that
is required for each role. Verify that each computer meets the requirements (see page 49) of each
role.
NOTE:
For more information, refer to the topics describing:
 Example architectures. (see page 27)
 The installation of Supervision software (see page 65).
 Virtual machine usage (see page 15).

EIO0000001255 11/2017 25
System Infrastructure

The following figure shows an example of a physical architecture running Process Expert.

NOTE:
The following can exist but are not represented:
 Multiple engineering and operator stations.
 Redundant and/or multiple operation servers.

Performance Considerations
If you are using a Process Expert client that is installed on the system server computer and perform
CPU-intensive operations (for example, importing many instances), actions that you execute
immediately after may trigger notifications about client/server communication interruptions.
For more information, refer to the troubleshooting topic (see page 141).

Network Connections
If you experience difficulties with client/server communication, refer to the topic providing
troubleshooting information (see page 141).

26 EIO0000001255 11/2017
 System Infrastructure

Physical Architecture Examples

Overview
With the use of examples, this topic describes some common architectures, and outlines the VM
license requirements depending on the number of users working simultaneously.
It also shows the connections to the control network that are required.
Use these examples as a guideline to determine the architecture that is adapted to your needs and
the resulting license requirements.
NOTE: This topic does not describe PES and application size license requirements
(see EcoStruxureTM Hybrid DCS, Licensing Guide).

All-In-One Architecture
The all-in-one architecture is a common small engineering configuration with:
 A single user.
 One VM requiring one license.

The following figure shows an architecture where all Process Expert software components are
installed on one computer (64-bit version only).

(1) computer with the system server, a VM, one engineering, and one operation client. Up to four
instances of the VM are available to the user.
(2) Controllers.
(3) Ethernet control network.

EIO0000001255 11/2017 27
System Infrastructure

NOTE: Optionally, Supervision software (one operation server and its Supervision control client)
can also be installed on the computer for testing purposes. This does not affect the VM license
requirements.

Engineering Architecture
This architecture is a common medium-size configuration that is used by system integrators with:
 Up to three users working simultaneously.
 Three VMs requiring three licenses:
 Two VMs on engineering stations.
 One VM on the system server.

28 EIO0000001255 11/2017
 System Infrastructure

(1) System server combined with operation server: Computer with the system server, a VM, one
engineering client, one operation client, and Supervision software (one operation server and its
Supervision control client).
(2) Engineering station: PC with one engineering client and a VM.
(3) Engineering station: PC with one engineering client and a VM.
(4) Controllers.
(5) Ethernet control network.
NOTE: Up to four instances of the VM are available to each user.
NOTE: In the case where no engineering client is installed on the system server, no separate
license is required for the VM of the system server. Up to two users can work simultaneously on
the engineering stations, which requires two VM licenses. The VM license that is used for one of
the engineering stations can be used for the system server also.

EIO0000001255 11/2017 29
System Infrastructure

On-Site Architecture
This architecture models small to medium-size configurations, which are deployed on site with:
 One engineering user and up to four operators working simultaneously.
 Three VMs requiring five licenses:
 The VM of the engineering client on the engineering station (2) requires one license.
 The VM of the engineering client on the operator station (3) requires one license.
 The three operation clients on the three other operator stations (4) use the VM on the system
server, which requires three licenses.

(1) System server: Computer with the system server and a VM, which is used by operator stations
(4).
(2) Engineering station: PC with one engineering client and a VM.

30 EIO0000001255 11/2017
 System Infrastructure

(3) Operator station combined with engineering station (64-bit version only): PC with one
Supervision control and/or view-only client, one operation client, one engineering client, and a
VM.
(4) Operator stations: Three PCs with a Supervision control and/or view-only client, and an
operation client.
(5) Operation servers (redundant or specific): Computers with Supervision servers.
(6) Controllers.
(7) Ethernet control network.
NOTE:
 Each user of an engineering station ((2) and (3)) can use up to four instances (see page 15) of
the local VM.
 Each user of an operator station ((3) and (4)) can share the instances of the VM (see page 17)
of the system server.

EIO0000001255 11/2017 31
System Infrastructure

32 EIO0000001255 11/2017
 Process Expert
Installing Service Pack 1 for Process Expert 4.3
EIO0000001255 11/2017

Chapter 2
Installing Service Pack 1 for Process Expert 4.3

Installing Service Pack 1 for Process Expert 4.3

Overview
This chapter contains general information on Service Pack 1 for Process Expert 4.3 and describes
how to install it.
NOTE: Process Expert 4.3 is a prerequisite for installing the service pack. If Process Expert 4.3 is
not installed, download and install it first.

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
Prerequisites 34
Service Pack 1 General Installation Information 36
Installing Service Pack 1 for Process Expert 4.3 40
Migrating Databases of Process Expert 4.3 to Service Pack 1 42
Starting the Process Expert 4.3 Service Pack 1 System Server 43
Modifying, Repairing, and Removing Process Expert 4.3 Service Pack 1 44

EIO0000001255 11/2017 33
Installing Service Pack 1 for Process Expert 4.3

Prerequisites

Overview
You need to install Service Pack 1 (SP1) over an existing Process Expert 4.3 installation. You must
have administrator rights.
NOTE:
 The installation of the service pack cannot be undone.
 You need to apply the service pack to all the installed Process Expert components of a same
system infrastructure for the software to function properly.

Accessing the Service Pack Installation Package

A service pack installation package for Process Expert is delivered as an ISO file. Use one of these
software tools to access and extract the installation files:
 ISO file-processing tool: Use this tool to mount two ISO files simultaneously (for example,
DAEMON Tools v10) when the installer needs to access the installation files of the earlier
version of Process Expert.
 ZIP tool: Schneider Electric recommends the 7-Zip tool. Download it as freeware at www.7-
[Link].

PES Licenses
Using SP1 requires PES licenses for Process Expert 4.3.

Software Requirements
You need to have a functional installation of Process Expert 4.3 on the computer on which you
want to install Service Pack 1.
Use the service pack installation package that conforms to your operating system:
 Use the 64-bit installation package to update the Process Expert components installed on 64-
bit operating systems.
 Use the 32-bit installation package to update operation clients installed on 32-bit operating
systems.
NOTE: If you are using a version of Process Expert earlier than 4.3 and you want to keep using
your databases, migrate them in sequence up to V4.3 before installing the service pack.

Machine Roles
You cannot change the role of a computer of the Process Expert system infrastructure during
installation of the service pack.
You can change the role of the computer before or after you install the service pack.

34 EIO0000001255 11/2017
 Installing Service Pack 1 for Process Expert 4.3

Installation Of Unity Pro

The installation of the service pack does not change the Unity Pro installation requirements
(see page 50).

Hardware Requirements
The installation of the service pack does not change the hardware requirements (see page 46) for
computers of the Process Expert system infrastructure.

Supervision Software Requirements

The installation of the service pack does not change the requirements for OPC Factory Server
(OFS) software (see page 50).
For Supervision software, CitectSCADA 2015 (version 7.50) SP1 patch 13 is required.

EIO0000001255 11/2017 35
Installing Service Pack 1 for Process Expert 4.3

Service Pack 1 General Installation Information

Overview
When you install the service pack, it automatically updates any Process Expert component that is
installed on the computer:
 System server.
 Engineering client.
 Operation client.

It does not modify installed virtual machines (VMs) because no update is required.
You can continue using your existing Process Expert 4.3 databases with Service Pack 1. Starting
the system server after you installed the service pack automatically migrates the mounted
database to make it compatible. Once migrated, a database is not compatible with the previous
version of Process Expert anymore, including service packs. You cannot undo the migration
process.
NOTE: You must restart your computer after installing the service pack.

User Interface Language

The user interface of Process Expert and the help are available only in English.

Process Expert Hotfixes

Service Pack 1 for Process Expert 4.3 includes the hotfixes that were available on the PES support
website (see page 8) at the time of the service pack release. As a result, installing the service pack
clears the list of installed hotfixes that may have appeared in the About Process Expert dialog box
before you installed the service pack.
Refer to the release notes for a list of included hotfixes.
NOTE: After you have installed SP1 for Process Expert 4.3, install only hotfixes that are released
for this version.

36 EIO0000001255 11/2017
 Installing Service Pack 1 for Process Expert 4.3

Process Expert Databases

After installing the service pack, starting the system server:
 Creates a new database if no database exists yet.
 Migrates the mounted database.

To continue using databases for Process Expert 4.2 or earlier, migrate (see page 70) them in
sequence to V4.3 before you install the service pack.
The table outlines various scenarios depending on the Process Expert installation that existed
before you installed the service pack:

Process Expert version Software usage Result after installing Service Pack 1
currently installed
None (first Process Expert After installing A new Process Expert 4.3 SP1 database is created
installation). Process Expert 4.3, the (see page 43) when you start the system server. It contains
system server was not templates of V4.3 plus new and/or updated templates
started. provided with the service pack.
For more information on templates provided with the service
pack, refer to the library release notes.
Process Expert 4.3 The system server was The mounted Process Expert 4.3 database is migrated
started and a V4.3 (see page 80) to be compatible with SP1 when you start the
database has been system server.
created. It may contain It contains the same data as when used with
systems and user-based Process Expert 4.3. No new and/or updated templates of the
templates. The database service pack are included.
can also be the one of an Import the service pack templates to use them. For more
earlier version of information, refer to the topic describing when to use new
Process Expert that was and/or updated templates (see page 73).
migrated.

NOTE: Back up your Process Expert 4.3 database before you install SP1. After you install the
service pack, you cannot back up that database for reuse with its respective Process Expert
version.

Configuration of the System Server and Clients

The installation of the service pack does not change the configuration of the Process Expert 4.3
system server and its clients.

Virtual Machines
When you install the service pack, the VM that was installed with Process Expert 4.3 remains in
use.
If you had activated the operating system of the VM, it remains activated; otherwise, you need to
activate it (see page 114).

EIO0000001255 11/2017 37
Installing Service Pack 1 for Process Expert 4.3

Updating Licensing Software

The installation of a Process Expert service pack does not update the Schneider Electric Floating
License Manager or License Manager that are installed on the computer.
Schneider Electric recommends updating both license managers to the latest version that is
available on the PlantStruxure PES Support Portal, PES Software Downloads section.
Updating the Floating License Manager makes all floating licenses activated on this Enterprise
license server temporarily unavailable. An Enterprise license server can also host licenses that are
required by software controlling production systems. When its license becomes unavailable, the
software stops functioning.

WARNING
LOSS OF CONTROL
Update the Floating License Manager only when the floating licenses that are activated on this
Enterprise license server are not required by Process Expert or other software controlling
production systems.
Failure to follow these instructions can result in death, serious injury, or equipment damage.

License Server Port Settings

The installation of a the service pack modifies the default settings of Schneider Electric licensing
software (see page 53) that is installed on the computer running the system server.
These following parameter values are modified when you install the service pack.

Software component Parameter Value after service Comment

pack installation
Floating License License Server Port 27010 If you have modified the default
Manager IP address ([Link]) in the
License Manager Server Port (Only for Host 27010 Host Name / IP Address field of
the License Manager, the
Name / IP Address equal
license server port is not
to [Link])
changed.

The modification is done when you update the Process Expert system server with the service pack
and the Floating License Manager and/or the License Manager is installed on this computer.
Settings of the Floating License Manager and License Manager that are installed on other
computers of the Process Expert (for example, computers on which the engineering client or
operation client is installed) are not modified.
NOTE: If other software acquires license rights from a Floating License Manager whose license
server port was changed, make the necessary changes so that these license rights remain
available to the software. For example, modify the server port value of the corresponding entry in
the License Manager that is used by the software.

38 EIO0000001255 11/2017
 Installing Service Pack 1 for Process Expert 4.3

Third-Party Software Components

The installation of a the service pack does not modify the third-party software components
(see page 53) that were installed with Process Expert.

Destination Folders
The service pack installs at the location where you installed Process Expert. You cannot change
the installation path (see page 57).

Installation Log File

The service pack logs the activity that is completed during the software installation in two log files
(see page 56).
This overwrites any log files that were created during the Process Expert installation.

EIO0000001255 11/2017 39
Installing Service Pack 1 for Process Expert 4.3

Installing Service Pack 1 for Process Expert 4.3

Installation Requirements
Install the service pack on all computers in the Process Expert system infrastructure so that all
components are of the same version (see page 84).
Install the service pack on computers with the following roles:
 System server.
 Operation server: Only if a system server, engineering client, or operation client is installed.
 Engineering station.
 Operator station: Only if an engineering or operation client is installed.

NOTE: Use the 32-bit installation package to update 32-bit Process Expert operation clients.

Installation Procedure
You can update a Process Expert installation only when the system server is not running.

NOTICE
LOSS OF COMMUNICATION
Stop the system server only when no client is running.
Failure to follow these instructions can result in unresponsive clients.

Once you have installed the service pack, you cannot back up your Process Expert 4.3 database
anymore to reuse it with its respective version of Process Expert.

NOTICE
LOSS OF DATA
Back up the installed Process Expert database before installing a software update.
Failure to follow these instructions can result in loss of database or unusable systems.

40 EIO0000001255 11/2017
 Installing Service Pack 1 for Process Expert 4.3

The table describes the procedure to install the service pack on a computer.

Step Action
1 Back up (see page 118) the mounted Process Expert database.
2 Verify that the Process Expert system server and any clients connecting to it are not running.
3 Quit other Schneider Electric applications running on the computer.
4 Temporarily disable antivirus services running on the computer.
5 Double-click the Process Expert service pack setup file (.exe), which is in the root of the
installation package.
Result: The installation procedure starts and updates the Process Expert components that are
installed on the computer.
NOTE: After you double-click the setup file, it may take a few moments for the computer to
indicate that the installation started.
6 Follow the instructions on screen.
7 When prompted, restart the computer to complete the installation.

EIO0000001255 11/2017 41
Installing Service Pack 1 for Process Expert 4.3

Migrating Databases of Process Expert 4.3 to Service Pack 1

Overview
When you start the Process Expert 4.3 Service Pack 1 system server, the software verifies if the
mounted database has already been migrated to the service pack. If not, the migration occurs
automatically.
Once migrated, the database is not compatible with the previous version of Process Expert or
earlier service packs. You cannot undo the migration process.

Mounted Process Expert Database

The database that is mounted is the one that you had used or restored (see page 116) last with
Process Expert 4.3.
NOTE: If you installed Process Expert without starting its system server and without restoring a
database, no database is created nor mounted (see page 37).

Restoring Process Expert 4.3 Database Backups

To migrate other Process Expert 4.3 databases that you had backed up previously, you need to
restore them first. You can do this by using the Restore database command in the system server
console (see page 116) after you install the service pack.
Restoring a database does not migrate it. It mounts the database so that the Process Expert
system server can access it.

Migration Log Files

When you migrate a database, Process Expert creates several log files.

Managing Databases
Database backups that the software creates when you restore databases can use up a lot of disk
space. Manage these folders regularly to recover disk space.

42 EIO0000001255 11/2017
 Installing Service Pack 1 for Process Expert 4.3

Starting the Process Expert 4.3 Service Pack 1 System Server

Starting the System Server

Starting the Process Expert 4.3 Service Pack 1 system server automatically migrates the database
that is mounted (see page 80) to make it compatible if it is not already. No confirmation is required.
Once migrated, a database is not compatible with the previous version of Process Expert anymore,
including earlier service packs. You cannot undo the migration process.

NOTICE
LOSS OF DATA
Allow only authorized personnel to start or use the Process Expert system server.
Failure to follow these instructions can result in an unusable system or database.

Start the system server before starting any client.

For more information, refer to the topic describing how to start Process Expert (see page 115).

Troubleshooting System Server Startup

If you experience difficulties during system server startup, refer to the troubleshooting topic
(see page 135).

EIO0000001255 11/2017 43
Installing Service Pack 1 for Process Expert 4.3

Modifying, Repairing, and Removing Process Expert 4.3 Service Pack 1

Overview
After installing the service pack, you can:
 Modify the installation by installing or removing components (for example, add or remove an
engineering client).
 Repair the installation.
 Remove Process Expert from the computer. The removal of the service pack from the computer
also removes Process Expert and any earlier service packs.
Choose a method to perform these actions:
 Use the corresponding command from the Uninstall or change a program window of the
Windows® Control Panel.
 Double-click the [Link] file in the root of the Process Expert 4.3 installation package.

When you install a new component, it is installed with the Process Expert 4.3 Service Pack 1
version.
For details, refer to the topic describing how to modify, repair, and remove Process Expert
(see page 127).
NOTE: To modify or repair the Service Pack 1 installation by using the Control Panel, the software
needs access to the Process [Link] file of Process Expert 4.3.

44 EIO0000001255 11/2017
 Process Expert
Process Expert 4.3 System and Installation Requirements
EIO0000001255 11/2017

Chapter 3
Process Expert 4.3 System and Installation Requirements

Process Expert 4.3 System and Installation Requirements

Overview
This chapter describes the requirements to install Process Expert 4.3 components on your
computer. It also contains general information, which applies whether you install Process Expert
for the first time or upgrade an existing installation.

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
System Requirements 46
Software Requirements 49
General Installation Information 52
Installation Requirements 58
Installing the Controller Simulator 60

EIO0000001255 11/2017 45
Process Expert 4.3 System and Installation Requirements

System Requirements

Overview
This topic describes the hardware and operating system requirements.
The hardware requirements depend on the role of the computer (see page 24) in the
Process Expert system infrastructure.
NOTE: You must have administrator rights to install Process Expert.

CPU Performance
Because of the various criteria that impact CPU performance, the required processor performance
level is defined by using the PassMark® CPU mark. To find a CPU that meets the indicated
performance requirement, look up the CPU benchmarks available at [Link].

BIOS Settings
Using a CPU that supports hardware virtualization capabilities (HVC) and enabling VT-x or AMD-
V in the BIOS is mandatory to be able to use a VM (see page 19) and start the system server.

System Server Hardware Requirements

Component Requirements
CPU Minimum CPU mark: 5000
16 cores maximum
RAM Recommended: 16 GB
Minimum: 8 GB
Hard drive 250 GB, 7200 RPM. NTFS file system.
40 GB of free space to install and run the software.
Display Recommended: 1024 x 768. 24-bit true color
Ports Ethernet port
Input devices Mouse or compatible device
Keyboard

46 EIO0000001255 11/2017
 Process Expert 4.3 System and Installation Requirements

Operation Server Hardware Requirements

Component Requirements
CPU Minimum CPU mark: 3000
RAM Recommended: 8 GB
Minimum: 4 GB
Hard drive 80 GB, SSD recommended, 7200 RPM minimum. NTFS file system.
Ports Ethernet port
Input devices Mouse or compatible device
Keyboard

Engineering Client Hardware Requirements

Component Requirements
CPU Minimum CPU mark: 3000
16 cores maximum
RAM Minimum: 8 GB
Hard drive 250 GB, 7200 RPM. NTFS file system.
40 GB of free space to install and run the software.
Ports Ethernet port
Input devices Mouse or compatible device
Keyboard

NOTE: The same requirements apply if, in addition, you install an operation client on the computer.

Operation Client Hardware Requirements

Component Requirements
CPU Minimum CPU mark: 2000
RAM Minimum: 8 GB
Hard drive 250 GB, 7200 RPM. NTFS file system.
Ports Ethernet port
Input devices Mouse or compatible device
Keyboard

EIO0000001255 11/2017 47
Process Expert 4.3 System and Installation Requirements

Operating System Requirements

Supported operating systems Recommended for (machine role)

Microsoft® Windows Server® 2012 R2 System server
Microsoft® Windows® 10 Professional 64-bit –
Microsoft® Windows® 7 Professional 64-bit
Microsoft® Windows® 8.1 Professional 64-bit

NOTE: 32-bit operating systems can be used only for the 32-bit operation client.

48 EIO0000001255 11/2017
 Process Expert 4.3 System and Installation Requirements

Software Requirements

Overview
You can install Process Expert 4.3 on a computer in either of the following cases:
 Process Expert is not installed.
 Process Expert 4.2 or Process Expert 4.2 Service Pack 3 is installed.

Installing Process Expert automatically removes the earlier version if installed.

Each case is described more in detail in dedicated chapters.
Only the 64-bit installation package of Process Expert allows installing/upgrading all the
components of the system infrastructure (see page 53) on a 64-bit operating system. The 32-bit
version allows installing/upgrading only the operation client on a 32-bit operating system.
NOTE: If you are upgrading from Process Expert 4.2 or Process Expert 4.2 Service Pack 3, you
can reuse your database (see page 52) after migrating it.

Windows® User Account

If you are installing the Process Expert 4.3 system server or another Process Expert component
along with the Floating License Manager (License Server check box in the Machine Role dialog
box is checked) on a computer on which Schneider Electric licensing software (see page 53) is
installed, confirm that you are logged in to the same Windows® user account as the one used to
install the licensing software.
If you had installed the licensing software along with an earlier version of Process Expert, log in to
the same account as the one used to install Process Expert.
This is because Process Expert 4.3 updates the Schneider Electric licensing software and can
only be installed under the same Windows® user account.
NOTE: To confirm that you are logged in to the same Windows® user account as the one used to
install the licensing software (along with Process Expert or not), open the Windows® Control
Panel. The Floating License Manager and/or License Manager that are installed on the computer
need to appear in the Name column of the Uninstall or change a program window as
Schneider Electric Floating License Manager and Schneider Electric License Manager
respectively. If they are installed but do not appear, you are logged in to a different account.

Accessing the Process Expert Installation Package

The installation packages of Process Expert are supplied in the form of an ISO file. Use either
software to access/extract installation files:
 An ISO file processing tool. Use a tool that allows mounting two ISO files simultaneously (for
example, DAEMON Tools v10) when the installer needs to access the installation files of the
earlier version of Process Expert.
 A ZIP utility. 7-Zip is the recommended tool. It is a freeware. You can download it at www.7-
[Link].

EIO0000001255 11/2017 49
Process Expert 4.3 System and Installation Requirements

Supervision Software Requirements

To complete the deployment of Supervision projects and use Supervision runtime, you need to
install the following software, which is available in separate installation packages:
 CitectSCADA 2015 (version 7.50) SP1 patch 13.
 OPC Factory Server 3.60 SP3 (version 3.60.3111, LARGE configuration).

For more information on the installation of CitectSCADA and OPC Factory Server, refer to
Installing Supervision Software (see page 65).
NOTE: You can download the software from the PES Support Portal, PES Software Downloads
section. Registration required.

Unity Pro Installation Requirements

If you want to create Unity Pro projects and import them into Process Expert or open Control
project files coming from Process Expert with Unity Pro, you need to use the same version of Unity
Pro as installed in the virtual machine, the appropriate Unity Pro DTM library version, and apply
necessary hotfixes. Refer to the platform release notes for version details.
If the appropriate Unity Pro version is already installed, install the appropriate DTM library and
apply necessary hotfixes.
NOTE:
For versions of Unity Pro that are earlier than the one installed in the virtual machine:
 Having Unity Pro installed on the same computer does not interfere with Process Expert as long
as you install Process Expert after Unity Pro; however, you will not be able to exchange Control
project data.
 If Process Expert is already installed and you do not want to uninstall it, you need to install Unity
Pro on another computer.

Other Software Requirements

The following software should be installed on your computer before installing Process Expert:
 Internet Explorer® browser for computers on which the operation client is installed. Minimum:
version 7 or higher. Recommended: Installing the latest version. Configure the browser to be
the default browser.
 Adobe® Reader® software.

50 EIO0000001255 11/2017
 Process Expert 4.3 System and Installation Requirements

Third-Party Components Installed By Process Expert

Process Expert installs third-party components that it requires to function properly, such as
Oracle® VM Virtualbox software, which handles the virtual machine and InterSystems Caché
software, which manages the database.
Only the version that is provided in the installation package is tested and validated. Updating these
third-party components independently of the Process Expert installation leads to incompatibilities.

NOTICE
UNEXPECTED SOFTWARE BEHAVIOR
Use only the version of third-party software that is installed by the Process Expert installer.
Failure to follow these instructions can result in equipment damage.

NOTE: Refer to the topic providing general installation information for details about the version of
third-party software that is installed (see page 53).

License Requirements
To use Process Expert, you need to:
 Activate your Process Expert software license through the Schneider Electric Floating License
Manager. If you are upgrading an earlier version of Process Expert, you may need to update
your current licenses.
For information on licensing, refer to the licensing information (see EcoStruxureTM Hybrid DCS,
Licensing Guide).
 Activate the operating system of the virtual machine (see page 95). If you are upgrading an
earlier version of Process Expert whose virtual machine is already activated, you may be able
to reuse the Microsoft® Windows® product key.

EIO0000001255 11/2017 51
Process Expert 4.3 System and Installation Requirements

General Installation Information

Overview of Installation Scenarios

The table outlines various Process Expert installation and database migration scenarios and
describes the result in terms of available systems and templates.

Process Expert installation Database migration Result

scenario
V4.3 is installed without an None Creates a database containing templates
earlier version installed on delivered with Process Expert 4.3.
the computer.
The V4.3 system server is The migrated database replaces(1) the V4.3
started without database database, which was created during the first
migration. Later only, a server start. Only systems and templates
database of V4.2/4.2 SP3 is contained in the migrated database are
restored and migrated (it can available.
come, for example, from Systems created and templates delivered with
another Process Expert Process Expert 4.3 are not available anymore.
system infrastructure). However, you can import templates delivered
with V4.3.
V4.3 is installed to update None Creates a new database containing templates
V4.2 or V4.2 SP3 installed delivered with Process Expert 4.3.
on the computer. The database of the earlier version is not
removed and needs to be migrated to be used.
The database of the earlier A V4.3 database is not created. Only systems
version of Process Expert is and templates contained in the migrated
restored and migrated during database are available.
the first start of the V4.3 Templates delivered with Process Expert 4.3
system server. are not available. However, you can import
them.
The V4.3 system server is The migrated database replaces(1) the V4.3
started without database database, which was created during the first
migration. Later only, the server start. Only systems and templates
database of V4.2/V4.2 SP3 is contained in the migrated database are
restored and migrated. available.
Systems created and templates delivered with
Process Expert 4.3 are not available anymore.
However, you can import templates delivered
with V4.3.
(1) When you restore a database, it replaces the mounted database, which remains on the computer
(see page 119).

52 EIO0000001255 11/2017
 Process Expert 4.3 System and Installation Requirements

NOTE: Typically, an update of Process Expert contains only the latest version of each template.
Without these latest templates, new functionalities of the update are not available (for example,
support of new controller platforms or new communication modules). For more information on the
latest version of templates, refer to the Library Release Notes.
If you intend to migrate the database of an earlier version, refer to the topic describing how to use
templates of the Process Expert update (see page 73).

User Rights
Process Expert and Schneider Electric licensing software (see page 53) are installed so that they
are available to all the users of the computer.
Clients require that you log in by using your Microsoft® Windows® Active Directory® domain
service credentials.
The system server does not require logging in.
NOTE: If users use Active Directory® domain service credentials, verify that each user who needs
to log in also possesses a local account on the computer in case the connection to the domain
network is interrupted.
For more information, refer to the topic describing the login process (see EcoStruxureTM
Hybrid DCS, User Guide).

Installed Software Components

During installation of the 64-bit version of Process Expert, you have the choice to install any
combination of the following system infrastructure components on the computer.

EIO0000001255 11/2017 53
Process Expert 4.3 System and Installation Requirements

When you install a given Process Expert component, the following additional software components
are installed. The table also indicates the installed version.

Process Expert Virtual machine Database Schneider Electric Schneider Electric Floating License
system (see page 15) (Caché version License Manager Manager version 1.9.9
infrastructure (Oracle® 2016.[Link]) version 1.9.9
component VM Virtualbox
version 4.3.12 and
[Link].4.3.Win7.
[Link](1) virtual
machine file)
System server Yes Yes Yes(2) Optional(2). A Process Expert system
If an earlier infrastructure requires at least one
version is installed Floating License Manager.
on the computer, it It corresponds to the License Server
is upgraded. check box during installation.
If you select it (default) and an earlier
Engineering client Yes No No
version is already installed on the
Operation client No No No computer, you need to allow the
installer to upgrade it (see page 49)
during installation; otherwise setup
cannot complete.
If you want to use the Floating
License Manager on another
computer on which no
Process Expert is installed, verify that
it is of the same version as the
License Manager installed by
Process Expert.
For more information, refer to the
topic describing licensing
mechanisms (see EcoStruxureTM
Hybrid DCS, Licensing Guide).
Operation client No No No No(3)
(32-bit)

(1) Where X is an alphanumerical revision index.

(2) Upgrading the License Manager or Floating License Manager may change the license server
port value (see page 55).
(3) The installation package contains the installation files for the Floating License Manager.
NOTE: If you install the system server and an engineering client on the same computer, it installs
only one virtual machine.

54 EIO0000001255 11/2017
 Process Expert 4.3 System and Installation Requirements

NOTE: You can also install the Floating License Manager separately by running the
Process Expert installer and selecting only the License Server check box in the Machine Role
dialog box. If you are using this method to upgrade an earlier version, verify that you are logged in
to the correct Windows® user account (see page 49) before proceeding.

License Server Port Settings

The installation of Process Expert 4.3 modifies the default settings of Schneider Electric licensing
software (see page 53) that is installed on the computer.
The table indicates which parameters are modified and the new value after the installation.

Software component Parameter Parameter value Comment

after installing
Service Pack 3
Floating License Manager License Server Port 27010 If the Floating License Manager
and License Manager are installed
on the same computer and you
have modified the default IP
address ([Link]) in the Host
Name / IP Address field of the
License Manager, the license
server port is not changed.
License Manager Server Port 27010 The server port value is changed
only for Host Name / IP Address
equal to [Link] (default value).

The modification is done:

 When the installer updates the earlier version of the Floating License Manager or License
Manager that is installed on the computer.
 When you install a Process Expert 4.3 component on a computer on which the Floating License
Manager or License Manager is installed (even if the installer does not update the licensing
software, for example, because you have not selected the License Server check box in the
Machine Role dialog box).
After installation or modification, verify that the server port setting is the same in the Floating
License Manager and License Manager of the Process Expert 4.3 system infrastructure. In
particular if the two are not installed on the same computer.
For information on how to verify and or modify the server port setting, refer to the topic describing
how to configure an Enterprise License Server (see EcoStruxureTM Hybrid DCS, Licensing Guide).
NOTE: If other software acquires license rights from a Floating License Manager whose license
server port was changed, make the necessary changes so that these license rights remain
available to the software. For example, modify the server port value of the corresponding entry in
the License Manager that is used by the software.

EIO0000001255 11/2017 55
Process Expert 4.3 System and Installation Requirements

Installation Log Files

The Process Expert installer logs the activities performed during software installation in two log
files.

File name Path Content

Process Expert C:\ProgramData\Schneider Electric\Proce  Installed, modified, repaired,
[Link] ss Expert x.y(1). and uninstalled software
components.
 Component version.
 Applied hotfixes.
 Status of the action.

Process Expert [Link](1) Folder designated by the Microsoft® installer (MSI) verbose
Microsoft® Windows® %TEMP% logging information.
environment variable.
(1) Where x.y corresponds to the version of Process Expert that you are installing

Database
When you install Process Expert and start the system server, a new database is created.
If you are upgrading an earlier version of Process Expert, its database is not removed. You have
the possibility to reuse the databases of the earlier version after migrating it (see page 80).

Virtual Machine
If you are installing a Process Expert component that uses a virtual machine, the installer may give
you the option to keep the existing virtual machine file or replace it.
During installation, the software verifies if a Process Expert virtual machine file (.vdi) is present at
the location specified in the Destination Folder dialog box.
If no corresponding virtual machine is present at this location (for example, because the virtual
machine of an earlier version is in a different location), the software automatically installs the virtual
machine included in the installation package.
If a corresponding virtual machine is already present at this location, the software gives you the
choice to continue using the existing virtual machine or to replace it with the one included in the
installation package.
If the installer is not able to extract the virtual machine file from the installation package, it displays
a notification during installation. Refer to the troubleshooting section (see page 136) for details.
NOTE: If you replace the virtual machine, you will lose any changes that you have made to it (for
example, updates of the Libset of the Control Participant) and you will need to activate it.

56 EIO0000001255 11/2017
 Process Expert 4.3 System and Installation Requirements

Default Destination Folders

The default installation paths are:
 For Process Expert: C:\Program Files\Schneider Electric\StruxureWare\Process Expert
 For the Db (database, for system server only) and VM (virtual machine, for system server and
engineering clients) folders: C:\ProgramData\Schneider Electric\Process Expert x.y (where
x.y corresponds to the version of Process Expert that you are installing, for example,
Process Expert 4.3).
NOTE: You can change both paths during installation and the path to the VM folder (see page 96)
also after installation.

EIO0000001255 11/2017 57
Process Expert 4.3 System and Installation Requirements

Installation Requirements

Firewall Exceptions
The Process Expert installation process modifies the Microsoft® Windows® firewall settings of the
computer to allow communication with applications that it installs.
If you are using a firewall other than the Microsoft® Windows® one, modify the settings of the
firewall to allow incoming connections with these applications.
The following paths correspond to a default installation of the system server with its virtual machine
on a 64-bit operating system:
 VBoxHeadless: C:\Program Files\Oracle\VirtualBox\[Link]
 VBoxWrap: C:\Program Files\Oracle\VirtualBox\[Link]
 HostAgent: C:\Program Files\Schneider Electric\StruxureWare\Process Expert\System
Server\[Link]
 SystemServer: C:\Program Files\Schneider Electric\StruxureWare\Process Expert\System
Server\[Link]
When you install only an engineering client on the computer, only settings for the VBoxHeadless
and VBoxWrap applications are required in the firewall. No settings are required when you install
only an operation client.
NOTE: The entries created by the installer of an earlier version of Process Expert may remain
when the program is removed.

Enabling .NET Framework 3.5 and 4.5 for Microsoft® Windows® 8.1 and Windows® 10
Before installing Process Expert on a computer with a Microsoft® Windows® 8.1 operating
system, you need to:
 Enable .NET Framework 3.5
 Verify that .NET Framework 4.5 is enabled (normally enabled by default)
(For Microsoft® Windows® 10, the .NET Framework version that appears is 4.6, which is a
point release of .NET Framework 4.5.)
To enable .NET Framework 3.5, from the Microsoft® Windows® start menu, click Control Panel →
Programs → Turn Windows features on or off and select .NET Framework 3.5 in the Windows
Features window.
For .NET Framework 4.5, in the Windows Features window, verify that .NET Framework 4.5
Advanced Services is selected.
NOTE: Microsoft® Windows® needs to download the .NET Framework 3.5 package from the
Internet. If you do not have an Internet connection, refer to the offline activation procedure, which
is described at [Link]. The procedure requires the operating system installation
media.

58 EIO0000001255 11/2017
 Process Expert 4.3 System and Installation Requirements

Enabling .NET Framework 3.5 and 4.5 for Microsoft® Windows Server® 2012 R2
Before installing the Process Expert system server on a computer with a Microsoft®
Windows Server® 2012 R2 operating system, you need to:
 Enable .NET Framework 3.5
 Verify that .NET Framework 4.5 is installed (normally installed by default)

Refer to the activation procedure, which is described at [Link]/en-

us/library/[Link] to enable .NET Framework 3.5. The procedure requires the operating
system installation media.
NOTE: The procedure that uses the Add Roles and Features Wizard allows you to verify that .NET
Framework 4.5 is installed on the computer.

EIO0000001255 11/2017 59
Process Expert 4.3 System and Installation Requirements

Installing the Controller Simulator

Overview
The Process Expert installation package includes the PLC_Simulator folder, which contains the
files required to run an emulated simulator software. You can use it to perform deployment and
execution tasks for Control Participant projects.
When you install any Process Expert component on a computer, the Controller Simulator
application is installed.
By default, the simulator is installed with a setting that secures the Ethernet port of the computer,
which it uses. This setting applies only to the Windows® session of the user who is logged on
during installation.
Modifying this setting during the installation of Process Expert or installing the simulator on another
computer makes the computer vulnerable to cyber attack.
NOTE: If you are upgrading Process Expert, the simulator that was installed by the previous
version of Process Expert is replaced.

Securing the Ethernet Port of the Controller Simulator

During installation, in the Controller Simulator Ethernet Port Vulnerability dialog box a check box
is shown, which impacts the way the simulator is started.

Check box Result

Selected (default and The simulator is started with a password-protected Control project being loaded by
recommended default. This secures the Ethernet port of the computer (port 502 by default) that is
setting) used by the simulator and helps reduce vulnerability to cyber attack.
Cleared The simulator is started without a Control project being loaded. This leaves the
Ethernet port of the computer (port 502 by default) unsecured and may allow a cyber
attacker to gain access to the computer to execute, for example, malicious code.

NOTE: Securing the Ethernet port used by the simulator must be part of a global approach to make
your control environment less vulnerable to cyber attack. A topic dedicated to cybersecurity is
available in the support area of the Schneider Electric website.

Default Control Project Provided

When you install Process Expert, a password-protected Control project file is copied to the
computer:
 Full path: %LocalAppData%\Schneider Electric\Process Expert\[Link] (by default,
the value of the %localappdata% environment variable is C:\Users\
<username>\AppData\Local)
 Password: 31081986@v!sh

This is the file that is loaded into the simulator when you select the check box in the Controller
Simulator Ethernet Port Vulnerability dialog box.

60 EIO0000001255 11/2017
 Process Expert 4.3 System and Installation Requirements

Default Simulator Installation Path

When you install the Process Expert system server, the PLC_Simulator folder is copied to the
computer at the path C:\Program Files (x86)\Schneider Electric.

Installing the Simulator on a Computer Without Installing Process Expert

Schneider Electric recommends to install and use the simulator on a computer on which
Process Expert is installed so that the Ethernet port of the computer that is used by the simulator
is secured by using default installation settings.
To install the simulator separately on a computer on which Process Expert is not installed, proceed
as follows.

Step Action
1 Copy the PLC_Simulator folder to the computer.
The folder is located in the installation package of Process Expert at the path Program
Files\Schneider Electric.
2 Copy the [Link] file to the computer.
The file is located in the installation package of Process Expert at the path
LocalAppData\Schneider Electric\Process Expert.

NOTE: If you had installed the simulator provided with an earlier version of Process Expert on
another computer, you must replace it with the simulator provided with this version of
Process Expert.

Securing the Ethernet Port for Other Windows® Sessions

The setting to secure the Ethernet port of the computer applies only to the Windows® session of
the user who is logged on during installation.
When another user logs on to the computer and starts the simulator, no password-protected
Control project is loaded. The simulator needs to be configured manually (see EcoStruxureTM
Hybrid DCS, User Guide) to load the default Control project provided with Process Expert or
another one.

Using the Simulator

For information on how to use the simulator, load another password-protected Control project, refer
to the topic describing the deployment to an emulated simulator (see EcoStruxureTM Hybrid DCS,
User Guide).

EIO0000001255 11/2017 61
Process Expert 4.3 System and Installation Requirements

62 EIO0000001255 11/2017
 Process Expert
Installing Process Expert
EIO0000001255 11/2017

Chapter 4
Installing Process Expert

Installing Process Expert

Overview
This chapter describes how to install the various components of Process Expert and highlights
specific points of the installation of Supervision software, which is required during runtime.

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
Installing Process Expert for the First Time 64
Installing Supervision Software 65

EIO0000001255 11/2017 63
Installing Process Expert

Installing Process Expert for the First Time

Overview
The installer installs necessary software depending on the Process Expert components that you
select during installation (64-bit version only).
The computer may restart automatically during the installation process and requires a restart to
complete it.
To install the 32-bit operation client, refer to the topic describing how to install 32-bit
Process Expert (see page 83).
NOTE: If you are updating an earlier version of Process Expert, refer to the topic describing how
to update Process Expert (see page 67).

Installing Process Expert

The table describes the procedure to install Process Expert on the computer.

Step Action
1 Verify that the hardware and software requirements (see page 49) are fulfilled.
2 Quit Schneider Electric applications that are running.
3 Verify that .NET Framework is enabled (see page 58) (for Microsoft® Windows® 8.1,
Windows® 10, and Microsoft® Windows Server® 2012 R2 operating systems).
4 Temporarily disable antivirus services (such as real time, scripting) running on the computer.
5 Double-click the setup file (.exe) located in the root of the installation package.
Result: The installation procedure starts.
6 Follow the instructions on screen.
7 Accept the End User License Agreement (EULA).
8 In the Machine Role dialog box, select the Process Expert components (see page 53) that you
want to install on the computer depending on its role (see page 24).
9 Click Finish to exit the installer.
10 Restart the computer when prompted to do so to complete the installation process.

NOTE: To disable the USB port monitoring service of Oracle® VM Virtualbox software after
installation, use the registry entries file provided (see page 142).

64 EIO0000001255 11/2017
 Installing Process Expert

Installing Supervision Software

Installation Requirements
To complete the system engineering life cycle and use Supervision services during operation, you
need to install Supervision software (see page 50) on machines that serve as:
 Operation server: Install operation server software (configuration tools are required on at least
one operation server).
 Operator station: Install a Supervision control and/or view only client.

For more information, refer to the CitectSCADA 2015 Installation and Configuration Guide, which
is available in the software installation package and shown during installation.
NOTE: To use runtime navigation services, you need to install on the same computer, a
Process Expert operation client (see page 24) in addition to the Supervision client.
An operation client requires the services of a virtual machine (see page 19). By default, it is
configured to use the virtual machine of the system server.

Installing Schneider Electric Licensing Software

The version of the licensing software that is installed by CitectSCADA 2015 is earlier than the
version installed by Process Expert 4.3. Therefore:
 Install CitectSCADA 2015 first and clear the Schneider Electric License Manager check box
when prompted to select the components to install (selected by default).
 Installing a Process Expert 4.3 component on this computer afterwards lets you install the
required Schneider Electric License Manager and/or Floating License Manager.
 If you do not need to install a Process Expert component on this computer but need the
Floating License Manager, you can install it by using the Process Expert installer. In the
Machine Role dialog box, clear all but the License Server check box. This installs only the
Floating License Manager.
 If Process Expert is already installed, when you install CitectSCADA 2015, clear the Schneider
Electric License Manager check box when prompted to select the components to install
(selected by default).
For configuration information, refer to Configuring an Enterprise License Server for Supervision
Software (see EcoStruxureTM Hybrid DCS, Licensing Guide).
NOTE: The License Manager is not required by the Supervision software.

Installing Drivers
When you install the operation server, in the Select Drivers screen, select the OFSOPC RELEASE
Driver option so that the software can communicate with the OPC Factory Server.
For more information, refer to the topic documenting the Protocol parameter in tag container
properties (see EcoStruxureTM Hybrid DCS, User Guide).

EIO0000001255 11/2017 65
Installing Process Expert

Installing OPC Factory Server

OPC Factory Server (LARGE configuration) is included in the CitectSCADA installation package
(see page 50).
Install Vijeo Citect before installing OPC Factory Server. If the latter is already installed, uninstall
it before installing Vijeo Citect.
To install OPC Factory Server, double-click [Link] in the CitectSCADA installation package
and the select OPC Factory Server vX.Y (where X.Y corresponds to the included version) in the
CitectSCADA Setup dialog box. This way, you do not need to enter a part number and serial
number for it.
Then, use the OPC Factory Server installation package of the required version (see page 50) to
update it.
For more information on how to install OPC Factory Server, refer to the OPC Factory Server help,
which is located in the Help folder inside the OPC Factory Server installation package.

66 EIO0000001255 11/2017
 Process Expert
Updating Process Expert
EIO0000001255 11/2017

Chapter 5
Updating Process Expert

Updating Process Expert

Overview
This chapter provides information on the update process and describes how to update an earlier
version of Process Expert.

What Is in This Chapter?

This chapter contains the following sections:
Section Topic Page
5.1 About Updating Process Expert 68
5.2 Migrating Process Expert Databases 80
5.3 Installing the Process Expert Update 82

EIO0000001255 11/2017 67
Updating Process Expert

Section 5.1
About Updating Process Expert

About Updating Process Expert

Overview
This section provides information about the various aspects related to updating an earlier version
of Process Expert.
NOTE: Refer also to the topic containing general installation information (see page 52).

What Is in This Section?

This section contains the following topics:
Topic Page
Overview 69
Using Templates Supplied with the Process Expert Update 73
Stopping and Starting Caché 78

68 EIO0000001255 11/2017
 Updating Process Expert

Overview

Update Process Description

An update consists in installing on top of an existing Process Expert installation either of the
following:
 A new major version, for example, Process Expert 4.x on top of V3.x. (also referred to as
upgrade).
 A new minor version, for example, Process Expert 4.3 on top of V4.2 (also referred to as
upgrade).
 A service pack of an existing version, for example, Process Expert 4.0 Service Pack 3 on top of
Process Expert 4.0.
When you update Process Expert, you need to install the update on all computers on which the
system server and any clients connecting to it are installed because you cannot mix versions within
the same Process Expert system infrastructure (see page 12).
The installer:
 Searches for already installed components on the computer.
 Uninstalls the version that is already installed. The database that contains data of the systems
that you have created is not removed.
 Installs an updated version of the Process Expert components that were installed on the
computer.
 Gives you the option to add and/or remove roles (see page 24).
 May install a new virtual machine or may give you the choice to keep the existing one.
 Updates the following if the version that is installed is earlier than the one included in the
Process Expert update:
 Schneider Electric licensing software.
 Third-party software components (see page 51) such as Caché or Oracle® VM Virtualbox
software.
You have the possibility to reuse databases of the earlier version (see page 80) of Process Expert.
NOTE: If updating your version of Process Expert is not supported, either uninstall it, or if you want
to reuse your database, migrate it to the next version as you need to migrate databases by
following the sequence of versions. For example, if Process Expert 4.1 is installed, migrate the
database to Process Expert 4.2 first, then to V4.3.

Updating a 32-Bit Process Expert System Infrastructure

Starting with Process Expert 4.2, on computers equipped with a 32-bit operating system, you can
only install the operation client. All other system infrastructure components (see page 53) need to
be installed on 64-bit operating systems.
The 32-bit installer allows updating only 32-bit operation clients. You need to uninstall other
Process Expert system infrastructure components manually first.

EIO0000001255 11/2017 69
Updating Process Expert

Updating Supervision Software

Supervision software requirements (see page 50) may have changed and as a result, you may
need to update installed Supervision components (see page 65) that are used in conjunction with
the Process Expert system infrastructure.

Reusing Process Expert Databases

Migrating Process Expert databases of a supported earlier version so that you can reuse them with
the current version of Process Expert is a single-step process. The migration is performed
automatically when you start the system server after installing the update.
It is possible to re-use the database of 32-bit Process Expert 4.1 or earlier but you need to migrate
it to Process Expert 4.2 first. Refer to the V4.2 Installation Guide, Updating Process Expert.
If you do not want to reuse your current Process Expert databases (this includes systems, segment
libraries, and any template you may have created), install the Process Expert update and start the
system server. In this case, to save disk space, you can remove the Db database folder
(see page 57) of the earlier version.
NOTE: You can still migrate your existing supported databases to reuse them after you have
started the Process Expert 4.3 system server.

Changes to the Virtual Machine

If you had made changes to virtual machines of your earlier version of Process Expert, you need
to make these changes again if the Process Expert update installs a new virtual machine
(see page 53).
These changes can be, for example, the installation of device type managers (DTMs) or an update
of the set of libraries (Libset) of the Control Participant.

Reusing Templates
If you want to reuse templates of Process Expert 4.2 (for example, templates that you have created
and exported), you need to Import (see EcoStruxureTM Hybrid DCS, User Guide) the
corresponding export files (.sbk) in the Global Templates library before installing
Process Expert 4.3.
This is because you must only import files (.sbk) into a version of Process Expert that is the same
as the one in which they were created.

70 EIO0000001255 11/2017
 Updating Process Expert

Reusing Application Export Files

If you want to reuse instances that you have exported from Process Expert 4.0 and later, you can
import the corresponding application export files (.xml) in the Application Explorer after installing
the update.
For more information on the export and import of the application, refer to the topic describing how
to manage application folders and instances (see EcoStruxureTM Hybrid DCS, User Guide).
NOTE: For application export files created with Process Expert earlier than version 4.0, you need
to import these into the version in which they have been created (for example, Process Expert 3.1),
migrate the database to version 4.0. From then on, you can export the application and import it into
later versions.

Reusing Project or Topology Export Files

If you want to reuse Control or Supervision Participant projects, or topological entities that you have
exported from the earlier version of Process Expert, you need to import the corresponding export
files (.sbk) into a system before installing Process Expert 4.3.
This is because you can only import files into a version of Process Expert that is the same as the
one in which they were created.

Licensing Requirements
When you install a new version of Process Expert (for example, when you update
Process Expert 4.2 to version 4.3), you need to update your licenses and possibly purchase
additional licenses.
For a description of the licensing mechanisms, licensing requirements, and available licenses,
refer to the Process Expert Licensing Guide (see page 7).
For more information on the update process, refer to the Schneider Electric Floating License
Manager user manual.
Before installing the Process Expert update, check the instance count of existing systems to verify
that your application size license is still of the appropriate size.
For more information, refer to Counting Instances (see EcoStruxureTM Hybrid DCS, User Guide).

EIO0000001255 11/2017 71
Updating Process Expert

Transferring License Rights to the Virtual Machine

When updating Process Expert requires installing a new virtual machine (VM), you may be able to
reuse the Microsoft® Windows® product key that you are using with the VM of the earlier version
to activate the operating system of the VM of the update (see page 22).
However, you need to stop using the VM of the earlier version if the Microsoft® Software License
Terms allow using only one VM per product key.
If the operating system of the VM of the update is the same and:
 If you are using volume licenses, just enter the same product key in the configuration wizard of
the new VM.
 If you are using a product key of a retail version of Microsoft® Windows®, you may need to use
the activation by phone if the activation by Internet does not work.
NOTE: In any case, you must comply with the Microsoft® Software License Terms for the operating
system of the VM, which were provided when you purchased the license.

72 EIO0000001255 11/2017
 Updating Process Expert

Using Templates Supplied with the Process Expert Update

Overview
Typically, a Process Expert update contains new and/or updated templates. Refer to the library
release notes for latest information.
To take advantage of the new functionalities provided by the latest version of templates, you need
to update systems if you are using a database of an earlier version of Process Expert that you have
migrated. This is because the templates of the Process Expert update do not appear (see page 52)
in the Global Templates library anymore after you migrate a database.
To be able to use new and/or updated templates to update the earlier versions of templates that
are used by the instances of systems, you need to import them into the Global Templates library
first.
After you update systems with new and/or updated templates, you need to build the executables
of the Control Participant projects, test, and deploy them to their respective engines.
NOTE: As a general rule, update a template only if it is required. This is, if the new version of the
template provides a new functionality that you need or fixes an issue that you may experience. This
applies in particular to systems that are already deployed.

Templates Supplied with the Process Expert Update

The new and/or updated topological and application Schneider Electric templates are provided in
the form of export files (.sbk) in one compressed archive file.
There is one export file (.sbk) per template category.
The archive file is in the FL and GPL Templates folder, which is located in the root of the installation
package of the Process Expert update.
For more information on the templates that are provided, refer to the corresponding template user
guides.
For information on the severity of the impact when updating a template, refer to the library release
notes.
For information on importing these templates into the Global Templates library, refer to Importing
Templates (see EcoStruxureTM Hybrid DCS, User Guide).

Updated Types Supplied With Process Expert

The FL and GPL Templates folder may contain updated versions of derived function block (DFB)
types and/or derived data types (DDTs) that are used in Global Templates supplied with the
Process Expert update.
The folder is located in the root of the Process Expert update installation package.
The types are supplied in .XDB format in a compressed archive file.

EIO0000001255 11/2017 73
Updating Process Expert

When to Import and Update Templates

The table describes several scenarios, which are possible after you migrate a database of
Process Expert 4.2 or V4.2 SP3 and indicates in which case you need to use templates provided
with the new version of the software.

Scenario Example Required and possible actions after

migrating the database
Migrated systems are not modified. Enduser whose existing systems Importing templates supplied with the new
Software is updated to benefit of are deployed and working fine. No version of the software is not required.
performance improvements and changes are planned in the
NOTE: You can modify migrated systems
possibility to create new systems in application or topology in the short
by using templates and functionalities of the
the future by using new term, which would use new
earlier version of the software. These
functionalities. functionalities (for example, using
templates are readily available in the Global
a new communication template).
Templates library.
Migrated systems are going to be Enduser who would like to use new  Importing templates supplied with the
updated to take advantage of the functionalities provided by a new new software version. These are used to
features of the new software version of an application template. create new instances.
version. The application already contains  Updating templates of existing instances
instances of the current template of the application.
version.
NOTE: Because earlier and current
versions of templates co-exist in the Global
Templates library, verify that you are using
the latest version to create new instances
and topological entities.
New systems are created, which System integrator who keeps  Importing templates supplied with the
contain application instances and supporting the installed base new software version. These are used to
topological entities using (without changes) while creating create new instances and topological
functionalities of the new software new systems within the same entities of new systems.
version. Application instances and database by using only the new  Updating templates of existing instances
topological entities of migrated software version and latest of the application and entities of the
systems remain unchanged. templates. topology is not required.
As a result, systems of both the
earlier version and the current NOTE:
software version co-exist in the Because earlier and current versions of
database. templates co-exist in the Global Templates
library, verify that you are using:
 The earlier version when modifying
migrated systems.
 The latest version when creating and
modifying new systems.

74 EIO0000001255 11/2017
 Updating Process Expert

Scenario Example Required and possible actions after

migrating the database
Within the same migrated system, System integrator who keeps  Importing templates supplied with the
new application instances are supporting the installed base but new software version. These are used to
created in the existing application who also wants to add new create new instances and/or topological
and new topological entities are instances to existing systems by entities.
created in the existing topology. using templates of the latest  Updating templates of existing instances
version. of the application and entities of the
This can be the case in a system topology is not required.
consisting of one tank farm created
with an earlier version of the NOTE:
software. The current functionality Because earlier and current versions of
is satisfactory and no changes are templates co-exist in the Global Templates
planned. A new tank farm needs to library, verify that you are using:
 The earlier version when modifying
be added to the application but by
using the latest available features. existing application instances and
topological entities.
 The latest version when creating and
modifying new application instances and
topological entities.
A Process Expert 4.1 database is Enduser is updating the topology  Importing templates supplied with the
migrated to V4.2 without making of the system, which was using a new software version. These are used to
changes, then to V4.3. controller of the Quantum platform create new topological entities.
Within the same migrated system, with an NOE communication  Updating templates of existing instances
the existing application remains module to now use an NOC of the application and other entities of the
unchanged while topological communication module. topology.
entities are replaced to use new The application remains the same.  Upgrading the CPU firmware version of
functionalities of the new software topological entities and of the
version. configuration of Control projects.
NOTE: Use only the latest version of
templates to modify the application
thereafter (if needed) so that it remains
compatible with the topology.

EIO0000001255 11/2017 75
Updating Process Expert

Updating Systems with the Latest Templates

After you import new templates into the Global Templates library, you can update instances of
systems with these new templates.
Migrated Control Participant projects may not function properly after a migration.

WARNING
UNINTENDED EQUIPMENT OPERATION
Verify that any built Control Participant projects that are contained in a migrated database
function properly before deploying them to controllers.
Failure to follow these instructions can result in death, serious injury, or equipment damage.

The table describes the workflow to update templates used by application instances and
topological entities with templates of the Process Expert update.

Step Description
1 Verify that the application size license that is activated for Process Expert is of the appropriate
size.
If the software displays a notification about the license size, refer to Licensing Conflicts
(see EcoStruxureTM Hybrid DCS, Licensing Guide).
For information on the size of systems, refer to Instance Count (see EcoStruxureTM Hybrid DCS,
User Guide).
2 Verify that you have imported Global Templates supplied with the Process Expert update.
3 If you had created your own templates, update these templates with any updated reference that
may be available with the Process Expert update.
Refer to Updating Global Templates (see EcoStruxureTM Hybrid DCS, User Guide).
4 Update the templates used by instances of the application.
Refer to Updating and Replacing Templates of Instances (see EcoStruxureTM Hybrid DCS, User
Guide).
NOTE: To maintain existing links, update instances that are linked at once.
5 Generate the Control and Supervision projects.
NOTE: If the software detects DFB version conflicts, it opens a dialog box, which allows you to
select the version you want to use. Select the version encapsulated in the new version of the
template. For details, refer to the topic describing the management of versions of types in
Control facets during generation (see EcoStruxureTM Hybrid DCS, User Guide).
NOTE: If generation detects that the controller does not support a new functionality or data type,
you need to upgrade the firmware version of the CPU of the default configuration used by the
Control Participant project.

76 EIO0000001255 11/2017
 Updating Process Expert

Step Description
6 Update the templates used by the topological entities of each system by using the Update
Templates command.
Refer to Updating Templates of Topological Entities (see EcoStruxureTM Hybrid DCS, User
Guide).
NOTE: You may need to upgrade the firmware of topological entities to a version that supports
new modules or data types (see Hybrid DCS, Control Participant Services, User Guide).
7 Build the Participant projects and verify that they function properly.
8 Deploy the built Participant projects to their respective engines.

EIO0000001255 11/2017 77
Updating Process Expert

Stopping and Starting Caché

Stopping Caché
To stop Caché, you need to stop the system server first.

NOTICE
LOSS OF COMMUNICATION
Stop the system server only when no client is running.
Failure to follow these instructions can result in unresponsive clients.

To stop Caché, proceed as follows.

Step Action
1 Quit any Process Expert clients that are connected to the system server that is running on the
computer on which Caché is installed (see EcoStruxureTM Hybrid DCS, User Guide).
2 Stop the system server (see EcoStruxureTM Hybrid DCS, User Guide).
3 Right-click the icon in the Microsoft® Windows® notification area representing the Caché
database.
Result: The Caché context menu opens.
4 Select Stop Caché.
Result: Caché opens the Caché Shutdown dialog box.
5 Select Shut down and click OK.
Result: Caché displays a splash screen while shutting down the database.
6 Wait until the Caché database icon turns gray, indicating that the database is shut down.

NOTE: Do not start the system server when Caché is stopped because the database needs to be
running for the system server to function properly.
NOTE: By default, Caché starts when you restart the computer.

78 EIO0000001255 11/2017
 Updating Process Expert

Starting Caché
To start Caché, proceed as follows.

Step Action
1 Right-click the icon in the Microsoft® Windows® notification area representing the Caché
database.
Result: The Caché context menu opens.
2 Select Start Caché.
Result: Caché displays a splash screen while the database starts.
3 Wait until the Caché database icon turns blue, indicating that the database is running.

NOTE: By default, Caché is configured to start when you start Microsoft® Windows®.

EIO0000001255 11/2017 79
Updating Process Expert

Section 5.2
Migrating Process Expert Databases

Migrating Process Expert Databases

Migrating Databases of Process Expert 4.2 or V4.2 SP3 to V4.3

Overview
After you install the V4.3 update, no database is mounted. To migrate a V4.2 or V4.2 SP3
database, you need to mount it first.
Starting the Process Expert 4.3 system server completes the migration process (see page 121).
NOTE: Once migrated, the database is not compatible with the previous version of Process Expert
anymore, including service packs. You cannot undo the migration process.

Prerequisites
The following are prerequisites for performing the migration process:
 Activate (see page 72) the operating system of the VM of the system server.
 Install in the VM of Process Expert 4.3 all the extensions (see page 105) that are used in
Control Participant projects of systems contained in the database that you are migrating.

Mounting the V4.2 or V4.2 SP3 Database

After you upgrade V4.2 or V4.2 SP3 to V4.3, no database is mounted.
You need to mount the database that you want to migrate by using the Restore Database
command in the system server console (see page 116).
Restoring a database (see page 118) does not migrate it. It mounts the database so that the
Process Expert system server can access it.
NOTE: If you had uninstalled Process Expert 4.2 or any of its service packs before installing the
update, you may still be able to mount their database, which remains on the computer
(see page 57).

Restoring Additional Process Expert 4.3 or V4.2 SP3 Database Backups

You can migrate more than one Process Expert 4.3 or V4.2 SP3 database if you had backed them
up previously. You need to restore (see page 118) each one by using the Restore Database
command (see page 116).
You can also migrate databases if you have already started the V4.3 system server without
restoring a database (see page 52).

80 EIO0000001255 11/2017
 Updating Process Expert

Status of Supervision Project Executables After Migration

After you migrate a database of Process Expert 4.2 to V4.3, the build status of Supervision project
executables changes to Not Built if before migration it was either:
 Built
 Out Of Date

This differs from the typical migration scenario and is the result of new functionalities and
enhancements implemented for Supervision projects since Process Expert 4.2 Service Pack 1.
Use the Build or Build All command to build the Supervision project executable.
For more information about the new functionalities and enhancements, refer to the platform release
notes.

Migration Log Files

Process Expert creates several log files when you migrate a database, which contain information
about the migrated objects and detected errors.
The name of the log files is migration_YYYY-MM-DD_HH-[Link] where YYYY-MM-
DD_HH-MM-SS represents the date and time when the log file was created.
The software creates log files at the following locations:
 For the database that you have migrated, in the GLOBAL folder located at the path
C:\ProgramData\Schneider Electric\Process Expert x.y\Db.
 For each system contained in the migrated database, in the System_n folder located at the path
C:\ProgramData\Schneider Electric\Process Expert x.y\Db.
x.y represents the version of Process Expert that you are using.
NOTE: Systems that appear in the Db database folder keep their default name (System_n) even
if you rename them in the Systems Explorer.

Managing Databases
Database backups that the software creates when you restore databases can use up a lot of disk
space. Manage these folders regularly to recover disk space.

EIO0000001255 11/2017 81
Updating Process Expert

Section 5.3
Installing the Process Expert Update

Installing the Process Expert Update

Overview
This section describes how to install 32-bit and 64-bit Process Expert to update an existing
Process Expert 4.2 or V4.2 SP3 system infrastructure.

What Is in This Section?

This section contains the following topics:
Topic Page
Installing the 32-Bit Process Expert Update 83
Installing the 64-Bit Process Expert Update 84

82 EIO0000001255 11/2017
 Updating Process Expert

Installing the 32-Bit Process Expert Update

Overview
The 32-bit Process Expert installation package allows only:
 Installing the operation client on a 32-bit operating system.
 Updating an existing 32-bit Process Expert 4.2 or V4.2 SP3 operation client.

A restart of the computer is required to complete the installation process.

NOTE: If required, a Process Expert 4.3 system infrastructure can contain one or more 32-bit PCs
hosting the operation client. This is because memory requirements of this component do not
exceed the 3 GB limit.

Installing The 32-Bit Process Expert Operation Client

NOTICE
LOSS OF DATA
Back up the installed Process Expert database before installing a software update.
Failure to follow these instructions can result in loss of database or unusable systems.

The procedure describes how to install the 32-bit Process Expert operation client on a computer.

Step Action
1 Verify that the system and installation requirements (see page 45) are fulfilled.
2 Quit other Schneider Electric applications that are running.
3 Temporarily disable antivirus services (real time, scripting, and so on) running on the PC.
4 Double-click the setup file (.exe) located in the root of the installation package of the
Process Expert update.
5 Accept the End User License Agreement (EULA).
6 Click Next.
7 Follow the instructions on screen.
8 Click Finish to exit the installer.
9 Restart the computer when prompted to do so to complete the installation process.

NOTE: For information on using the Process Expert operation client, refer to its user guide
(see EcoStruxureTM Hybrid DCS, Runtime Navigation Services, User Guide).

EIO0000001255 11/2017 83
Updating Process Expert

Installing the 64-Bit Process Expert Update

Overview
Install the update on computers that have the following roles (see page 24) because all
components of a same Process Expert infrastructure need to be of the same version:
 System server.
 Operation server: Only if a system server, engineering client, or operation client is installed.
 Engineering station.
 Operator station: Only if an operation and/or engineering client is installed.

You can add and/or remove roles during installation.

A restart of the computer is required to complete the installation process.

Identifying a Process Expert Component Version

Component Version identification Version location

System server V<Major>.<Minor>.<SP>.<Build>: In the console:
 For a Process Expert 4.2 installation:  When you start the system server, on the
V4.2.0.<Build> first line after the message Server is
For example, V4.2.0.1316. starting.
 For a Process Expert 4.2 Service Pack 3  When the server has started, next to the
installation: V4.2.3.<Build> message Server is ready.
For example, V4.2.3.1435.
Engineering V<Major>.<Minor>.<Build>: The Product Version is indicated in the
client  For a Process Expert 4.2 installation: V4.2.0 Details tab of the Properties dialog box of the
Operation client  For a Process Expert 4.2 Service Pack 3 [Link] or
installation: V4.2.3 [Link] file.
By default, the file is located at the path
C:\Program
Files\Schneider Electric\StruxureWare\
Process Expert\<type> Client (where <type>
is either Engineering or Operation)

NOTE: When the engineering client is running, you can verify its version in the General tab of the
About StruxureWare Process Expert dialog box.

84 EIO0000001255 11/2017
 Updating Process Expert

Installation Procedure
You can update an existing Process Expert installation only when the system server is not running.

NOTICE
LOSS OF COMMUNICATION
Stop the system server only when no client is running.
Failure to follow these instructions can result in unresponsive clients.

NOTICE
LOSS OF DATA
Back up the installed Process Expert database before installing a software update.
Failure to follow these instructions can result in loss of database or unusable systems.

The table describes the procedure to install Process Expert on the computer to update an earlier
version.

Step Action
1 Verify that the system and installation requirements (see page 45) are fulfilled.
2 Back up the mounted database (see page 118).
3 Verify that the Process Expert installation is not running.
4 Quit other Schneider Electric applications that are running.
5 Temporarily disable antivirus services (real time, scripting, and so on) running on the computer.
6 Double-click the setup file (.exe) located in the root of the installation package of the
Process Expert update.
Result: The installation procedure starts and looks for installed Process Expert components to
update and/or remove.
7 Accept the End User License Agreement (EULA).
8 In the Machine Role dialog box, the check boxes of components of the earlier version that are
installed on the computer are selected. These components (see page 53) are updated by the
installer.
Modify the component selection as needed:
 Clearing a selected check box uninstalls the component from the computer.
 Selecting a check box that is cleared installs the component on the computer.

NOTE: Clearing the License Server check box does not remove the installed version
(see page 53); it remains on the computer but it is not upgraded. If an earlier version of the
Floating License Manager is installed on the computer, you need to select the check box for the
installation process to complete successfully.
9 Click Next.

EIO0000001255 11/2017 85
Updating Process Expert

Step Action
10 Follow the instructions on screen.
11 Click Finish to exit the installer.
12 Restart the computer when prompted to do so to complete the installation process.
13 Repeat the installation procedure on each computer of the Process Expert system infrastructure
on which the update is required (see page 84).

NOTE: If messages about detected errors are displayed during the update, refer to the topic about
troubleshooting installation (see page 136).
NOTE: To disable the USB port monitoring service of Oracle® VM Virtualbox after installation, use
the registry entries file provided (see page 142).

86 EIO0000001255 11/2017
 Process Expert
Configuring Process Expert
EIO0000001255 11/2017

Chapter 6
Configuring Process Expert

Configuring Process Expert

Overview
This chapter describes how to configure the system server, clients, as well as virtual machines
before starting Process Expert for the first time and thereafter when changes are required.
The purpose is to:
 Verify and/or configure parameters of:
 The system server and clients.
 The virtual machine (VM) that is installed with the system server and/or engineering clients.
 Participants running inside the VM.

 Install in and/or remove from Participants running inside the VM extensions, such as:
 Device type managers (DTMs).
 Generic station description (GSD) files.
 Hotfixes or patches.

The configuration is performed by using configuration wizards.

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
Using Configuration Wizards 88
Configuring the System Server and Clients 93
Configuring the Virtual Machine 95
Managing Participant Extensions 105
Activating the Virtual Machine 114

EIO0000001255 11/2017 87
Configuring Process Expert

Using Configuration Wizards

Overview
The following configuration wizards are available to facilitate the configuration of Process Expert
components:
 System Server Configuration Wizard
 Engineering Client Configuration Wizard
 Operation Client Configuration Wizard

Each configuration wizard consists of several sections.

Configuration wizards are used for the initial configuration of the client/server architecture and later
to adjust your settings if required. Starting a component without using its configuration wizard
applies the default settings that are described in this chapter.
You can access the configuration wizards through the start menu of Microsoft® Windows®.
NOTE: Configure the system server first because Process Expert provides means to take over
server settings when configuring clients to speed up the configuration process.

Client/Server Configuration and User Accounts

The configuration of the system server and clients that is performed by using the corresponding
configuration wizard is tied to the user account that is used to log on to the operating system of the
computer. Configuration settings are stored in the local user folder.
When another user logs on to the computer for the first time, the person has to perform the
necessary configuration, including the activation of the VM.
If the configuration of the system server changes (for example, because another user has logged
on to the computer running the system server, which has loaded the account-specific system
server configuration), then the configuration of clients connecting to the server may change as well.

Configuration Wizard Sections

The sections of the System Server Configuration Wizard are:
 Hosting: Communication port settings for connections with clients.
 Virtual Machine: Settings to activate and configure the system server VM (saved states).
 Extensions: Provides the possibility to customize software participants hosted by the VM.

The sections of the Engineering Client Configuration Wizard and Operation Client Configuration
Wizard are:
 System Server: Communication settings for the connection with the system server.
 Virtual Machine: Settings to activate and configure the local VM (saved states).

88 EIO0000001255 11/2017
 Configuring Process Expert

Synchronization of Participants of System Server and Client VMs

The system server and client VMs can be configured differently. However, for client/server
communication to function properly, the software Participants hosted by the respective VMs need
to be synchronized.
For example, additional device type managers (DTMs) that you install in the Control Participant of
the system server VM also need to be installed in the Control Participant of any client VM.
Process Expert uses automated mechanisms that facilitate the configuration of VMs and the
synchronization of the software Participants.
NOTE: How to easily configure client VMs to be identical to the system server VM is described in
the topic documenting VM configuration (see page 95).

EIO0000001255 11/2017 89
Configuring Process Expert

The following figure illustrates the scenario where the VM configuration and the extensions of both
the system server and the client VM are identical. Starting the system server configures the VM
and generates the saved states. When a Process Expert client that uses a VM connects to the
system server, the saved states of the system server VM are automatically transferred to the client
computer. As a result, patches and/or extensions (for example, DTMs (see page 105)) that were
installed on the VM server-side are readily available client-side because they are part of the saved
states of the VM. You can disable automatic transfer of saved states (see page 96).

NOTE: If the VM was not able to start server-side, saved states cannot be transferred to clients
and VM services are not available client-side. Take the necessary corrective actions server-side
and start the system server again.

90 EIO0000001255 11/2017
 Configuring Process Expert

The following figure illustrates another scenario where the VM configuration and/or the extensions
of both the system server and the client VM are different. When a client that uses a VM connects
to the system server, Process Expert detects the difference, copies the server-side extensions to
the client computer, and generates the saved states locally to take into account the specific
configuration of the client VM. As a result, installation of patches and/or extensions (for example,
DTMs (see page 105)) that were performed on the VM server-side are repeated on the VM client-
side.

Differences that Process Expert detects between the system server and clients are, for example:
 A client VM configuration parameter (for example, a different timeout or language setting).
 A new DTM that is installed on the system server.
 A different VM activation key that is used for the client VM.
 VT-X/AM-V settings of Oracle® VM Virtualbox software.

EIO0000001255 11/2017 91
Configuring Process Expert

The following client configuration wizard parameters are not considered to check whether the
server and client VM configuration is identical:
 Folder shared with virtual machine
 Force saved states generation

NOTE: If an engineering client attempts to connect to the system server while the latter is still
starting, server-side extension files are copied to the client even if their VM configuration and
extension files are identical. This results in saved states being generated locally client-side.

Using the Configuration Wizards

When Process Expert is running and you make changes by using a configuration wizard, the
changes are applied only when you restart it.

NOTICE
LOSS OF COMMUNICATION
Stop the system server only when no client is running.
Failure to follow these instructions can result in unresponsive clients.

NOTE: Quit a Process Expert component before making changes by using its configuration wizard.
To use a configuration wizard, proceed as follows.

Step Action
1 From the Microsoft® Windows® start menu, click All Programs → Schneider Electric →
StruxureWare → Process Expert:
 System Server Configuration Wizard
 Engineering Client Configuration Wizard
 Operation Client Configuration Wizard

Result: The software opens the selected configuration wizard.

NOTE: You can also access the System Server Configuration Wizard from the system server
console by clicking Tools → Configure. The system server needs to be stopped.
2 Verify the settings and/or make necessary changes in the various sections of the configuration
wizard as described further in this chapter.
Clicking Back does not discard your changes.
3 Click Save & Close.
Result: The configuration wizard closes.
NOTE: Click Cancel to discard changes and close the configuration wizard.

92 EIO0000001255 11/2017
 Configuring Process Expert

Configuring the System Server and Clients

Overview
This topic describes the parameters that you can configure by using:
 The Hosting section for the system server:
 The client/server communication port.
 The file transfer port.

 The Server section for clients:

 The client/server communication port.
 The IP address of the system server.

This topic also describes the communication ports that are used by the VM and third-party software
installed with Process Expert.

Communication Port Availability

Before using the system server and its clients, you need to verify that the ports configured by
default are not already used on the computer on which the system server is installed.
In case one of these ports is used, you need to configure another port that is available.
To verify port usage on the computer, execute netstat -an at a command prompt. The
command returns a list of ports that are being used.

System Server Communication Port Description

The table describes the parameters that you can configure in the Hosting section of the System
Server Configuration Wizard window.

Parameter Description Default value

Port Main TCP port that is used by engineering and 9950
operation clients to communicate with the system
NOTE: The same value is configured
server to load data and execute user commands.
by default for engineering and
NOTE: If you modify this value, you need to modify it operation clients.
also for each engineering and operation client that
connects to the server.
File transfer port TCP port that is used to transfer files between clients, 9951
the system server, and software Participants of VMs.
The port is automatically transferred to VMs and clients.
CriticalMessaging Port that is used to maintain a continuous 9949
port communication link between the system server, clients,
NOTE: The same value is configured
and virtual machines. The port is used by the
by default for engineering and
[Link] and [Link] processes.
operation clients in the Virtual Machine
NOTE: If you modify this value, you need to modify it section of the corresponding
also for engineering and operation clients that connect configuration wizard.
to the server.

EIO0000001255 11/2017 93
Configuring Process Expert

Parameter Description Default value

Caché installation Installation path of the third-party software that C:\Program Files\InterSystems\STRU
path manages the Process Expert database. XUREWAREPEv43

NOTE: Both ports accept connections from any IP address.

The table describes additional ports used by the system server.

Protocol Port Description

UDP 18080 Logging/display
UDP 18081 Logging

Server Parameters for Process Expert Clients

The table describes the parameters that you can configure in the Server section of the Engineering
Client Configuration Wizard and Operation Client Configuration Wizard windows.

Parameter Description Default value

Address IP address of the computer on which the system server is Localhost
installed.
Port TCP port that is used for the client/server connection. 9950
NOTE: If you modify this value, you need to modify it NOTE: The same value is
also for the system server and any other engineering and configured by default for the
operation client that connects to the same server. system server.

Virtual Machine Communication Ports

Process Expert components bind VM services to the following ports.

Protocol Port Description

TCP 39081 One port by VM instance. For example, if two instances of the VM are
TCP 39181 used, ports 39081 and 39082 are used.

If you experience difficulties, verify if another program is using any of these ports.
NOTE: For engineering clients, ports used by the local VM are bound to IP address [Link]
(localhost) to accept only local connections.

94 EIO0000001255 11/2017
 Configuring Process Expert

Configuring the Virtual Machine

Overview
Before using the Process Expert system server or clients for the first time, you need to verify and/or
configure certain parameters of the VM by using the corresponding configuration wizard
(see page 88); otherwise the default settings that are described in this topic are applied.

VM to be configured Configuration wizard to be used Comment

System server VM System Server Configuration -
Wizard
Engineering client VM (local Engineering Client You can take over the system server VM
VM. Includes VM used by Configuration Wizard settings or customize the local VM.
operation client installed on the In addition, you need to use the
same PC) Operation Client Configuration Wizard to
allow the use of the local VM.
System server VM (used by System Server Configuration In addition, you need to use the
engineering clients and/or Wizard Engineering Client Configuration Wizard
operation clients) of each engineering client to configure it
so that it does not use its local VM.

Thereafter, use the wizards to adjust parameters of the VM if necessary.

NOTE: During the initial configuration you need to activate the VM (see page 114).

Configuration Priority
When the system server with a VM and an engineering client are installed on the same PC, and
you configure the VM by using the configuration wizard of both the system server and the
engineering client, the parameters that are applied to the VM are the ones you configure in the
system server configuration wizard.
When an engineering and an operation client are installed on the same PC, changes that you save
in the Virtual Machine section of one configuration wizard appear also in the configuration wizard
of the other client when you open it. Changes to either configuration wizard that you save last are
retained.

EIO0000001255 11/2017 95
Configuring Process Expert

Configurable Parameters
The following figure shows the Virtual Machine section of the system server configuration wizard,
which allows you to configure parameters of the VM of the system server.

96 EIO0000001255 11/2017
 Configuring Process Expert

The following figure shows the Virtual Machine section of the engineering client configuration
wizard, which allows you to configure parameters of the VM that is used by the engineering client.

EIO0000001255 11/2017 97
Configuring Process Expert

The following figure shows the Virtual Machine section of the operation client configuration wizard,
which allows you to configure parameters of the VM that is used by the operation client.

1 Set of parameters that are specific to the client and that you can configure if the client uses the
local VM; even if you select to use system server settings to configure the VM.
2 Click the button to view settings of the VM of the system server, which are configured in the
Virtual Machine section of the System Server Configuration Wizard. The execution of the local
VM needs to be allowed and the system server needs to be running.
3 Select either option to configure the VM of clients:
 Use server configuration: Default setting. Selecting this option configures the VM of the client
by using the same settings as those of the VM of the system server. The fields of the
configurable parameters are not visible.
Saved states of the client VM are transferred from the system server to the client
(see page 89).
 Use custom configuration: Selecting this option allows you to configure each parameter of
the VM of clients independently. Fields that you leave blank use the setting of the VM of the
system server.
Saved states of the client VM are generated locally (see page 89) if you customize a
parameter.
NOTE: You cannot customize the Folder for user extensions parameter.
NOTE: The functionality is enabled only if you have allowed the execution of the local virtual
machine.

98 EIO0000001255 11/2017
 Configuring Process Expert

The table describes the parameters of the Virtual machine section of the configuration wizard that
are related to the activation of the VM.

Parameter Description
Windows product The Microsoft® Windows® 7 Professional product key (see page 23) to activate the
key operating system of the VM with Microsoft.
Default value: TRIAL (see page 114)
NOTE:
If you enter a wrong product key, the operating system is not activated and the
Process Expert component displays a message in:
 The console for the system server.
 The Notification Panel for an engineering client.

Open the corresponding Configuration Wizard (see page 96), enter the correct product
key. The new value takes effect at the next restart of the component.
Key Management Name and/or port for the Key Management Server (KMS) that the host PC uses when
Server (KMS) you activate the operating system of the VM by using a Microsoft® Windows® 7
Professional product key under a volume license agreement (see page 23).
The format is hostname:port.
Default value: Blank
NOTE: Enter an IPv6 address in the format [hostname]:port.
Manual activation Select the check box (true) to start the manual activation procedure of the operating
system of the VM when it cannot connect to the Internet.
Default value: Cleared (false)
For information on the manual activation procedure over the phone, from the desktop,
click Start → Help and Support, and enter activate in the search field.
NOTE: When you are configuring the parameter on a client, by default, the check box
contains a black square. This indicates that the setting is inherited from the system
server. Select or clear the check box to customize the setting for the client.
Use Windows 30- Clicking the button sets the Windows product key to TRIAL and does not require
day trial period entering a Microsoft® Windows® 7 product key to use services of the VM. The 30-day
period starts when you first start the component that uses the VM. When the period is
elapsed, you need to activate the operating system of the VM.

EIO0000001255 11/2017 99
Configuring Process Expert

The table describes the parameters of the Virtual Machine section of the configuration wizard that
are related to the licensing of the VM.

Parameter Description
Port@Address of Floating Licence server port of the Floating License Manager where the
License Manager Process Expert system server license is activated and IP address of the
computer on which this FLM is installed.
This information is required by certain software Participants that are running
inside the VM for licensing purposes.
Default value: 27010@[Link] (corresponds to localhost).
If the FLM is installed on a different computer, enter the appropriate
information. Use the format port@IP address.
NOTE:
 This parameter is not a substitute for the License Manager.
 If you experience difficulties with Participant services, verify which license
server port is used by the FLM (see EcoStruxureTM Hybrid DCS, Licensing
Guide).

The table describes the parameters of the Virtual Machine section of the configuration wizard that
are related to the usage of the VM (see page 15).

Parameter Description
Allow execution of local Client parameter only.
virtual machine When the check box is:
 Selected (true): The client can use the local VM, which is the VM that is
installed on the PC. The settings of the configuration wizard apply to the local
VM. Does not apply to the 32-bit operation client.
 Cleared (false): The client uses the VM that is installed on the system server
PC, whose IP address you have configured in the Server section of this
wizard. You cannot change local VM settings by using the configuration
wizard. To change settings of the VM of the system server, use the System
Server Configuration Wizard.
If a client cannot access a VM, you cannot complete the system engineering life
cycle and/or use runtime navigation services.
Default values:
 Engineering client: Selected (true)
 Operation client: Cleared (false)

NOTE:
For the operation client, verify that:
 The system server is configured to allow clients to use its VM.
 If you set the parameter to true, an engineering client needs to be installed on
the same PC unless the operation client is installed on the system server PC
(64-bit version only).

100 EIO0000001255 11/2017

 Configuring Process Expert

Parameter Description
Maximum number of The maximum number of VM instances that users are allowed to use. The
virtual machine instances instances can be on the system server, on clients, or on both depending on the
running simultaneously parameter settings for VM usage.
If you change the setting, confirm that this number does not exceed the limit that
is defined by your Microsoft® VM licensing terms (see page 22) and the
performance of your PC is adequate (see page 15).
Default value:
 For the system server: 2
 For clients: 1

Process Expert starts a new instance automatically when the slots of the current
VM are already used and it receives the request for a new slot (see page 16).
Folder containing virtual Enter the path to the VM folder containing the virtual image file (.vdi) if you need
machine files (.vdi) to move the folder after installing Process Expert.
This could be necessary, for example, if the disk that contains the VM folder is
running out of space because the virtual machine file is a large file.
Default path: Path selected during the installation (see page 57) of
Process Expert. By default,
C:\ProgramData\Schneider Electric\Process Expertx.y\VM (where x.y
corresponds to the installed version).
CriticalMessaging Port Refer to the description of the parameter in the topic documenting the
configuration of server and clients (see page 93).
Allow clients to use virtual System server parameter only.
machine of system server When the check box is selected (true), allows engineering and operation clients
to use the VM (see page 15) that is installed on the PC on which the system
server is installed.
In this case, ports used by the VM (see page 94) are bound to IP address [Link]
to accept connections from remote PCs; otherwise ports are bound to IP address
[Link] (localhost).
Default value: Selected (true)

EIO0000001255 11/2017 101

Configuring Process Expert

Parameter Description
Folder shared with virtual Path to an existing folder on the local PC or network that becomes accessible
machine from the operating system of the VM and from its software Participants.
This folder appears in the VM and software Participants as drive Z:. The name of
the folder shared with the VM does not appear. For example, if you share folder
VM_Files, which contains subfolder Control, when you access drive Z: from a
software Participant, you see Z:\Control.
Default value: Blank
Configuring this parameter is required, for example, to access from the Unity Pro
Participant a file that you want to import or to open a file that is on the host PC in
the Supervision Participant.
NOTE: The folder that you specify needs to exist on the PC that hosts the VM or
to be a shared folder on the network that this PC can access. When sharing a
folder, restrict access by giving permissions only to the specific user who needs
to access this folder.
For example, if an engineering client installed on PC_1 is configured to use the
VM of the system server, which is installed on PC_2, entering C:\Temp in the
system server configuration wizard allows the VM that is displayed on the
engineering client to access this folder on PC_2. Also, any other engineering
client that is configured to use the VM of the system server can access this folder
as well.
On the opposite, if you are using two engineering clients that are configured to
use their local VM:
 To use the C:\Temp folder on the system server, enter the network path to the
folder in each engineering client configuration wizard and share the folder so
that the two engineering client PCs can access it (when sharing, give
permissions only to the user of each of the two engineering clients). Similarly,
you can configure any folder on the network to be shared with the VM of each
engineering client. The use of a shared folder on the network is recommended
to share a single folder with several VMs. When sharing, give permissions
only to specific users who need to access the folder.
 To use a local folder on each engineering client PC, enter its path in the
engineering client configuration wizard.
Memory allocated to Size of the paging file of the VM in MB.
virtual machine in MB Allocating more than 3000 MB requires a PC with a 64-bit operating system and
hardware virtualization capability enabled in the BIOS (see page 15). Usually, do
not allocate more than half of the memory available on the host computer.
Default value: 2048
NOTE: Modifying this parameter may cause the software to function incorrectly.

102 EIO0000001255 11/2017

 Configuring Process Expert

Parameter Description
Ratio to apply to timeouts Allows modifying the default timeouts that apply to the start of the VM (for
example, timeout applicable to the generation of saved states of the VM during
system server startup).
Enter values:
 From 1 to 14 to reduce timeouts.
 From 16 to 100 to increase timeouts.

Increasing the ratio may help when you experience difficulties during the start of
the VM because of low computer performance.
Range: From 1 to 100
Default value: 15
NOTE: Reducing timeouts excessively or entering a value that is outside of the
range may cause the software to function incorrectly.
Default keyboard layout Allows you to select the default keyboard layout to be used when you work inside
software Participants.
Default keyboard layout setting: US
For more information, refer to Language Settings (see EcoStruxureTM
Hybrid DCS, User Guide).
System locale Allows you to set the system locale setting of the operating system of the VM,
which controls the language used to display text in programs that do not support
Unicode. Applies to non-Unicode software Participants.
Change the setting if the language used by non-Unicode Participants to display
text contains characters that are not part of the Windows-1252 code page layout,
which corresponds to English and some Western languages.
Default value: US (en-US)
For more information, refer to Language Settings (see EcoStruxureTM
Hybrid DCS, User Guide).
NOTE: The setting does not affect time, date, and currency formats.
Update virtual machine When the check box is selected (true), generates the saved states of the VM
with latest extensions [Link] reinstalls any extensions that are listed in the Extensions section of
the configuration wizard.
The setting is helpful, for example, when a Participant has stopped working.
Restarting the system server and selecting this parameter restarts the
Participant.
Default value: Cleared (false)

EIO0000001255 11/2017 103

Configuring Process Expert

Parameter Description
Force re-activation of When the check box is selected (true), the software verifies if the operating
Windows system of the VM is activated with Microsoft®. If it is not, it starts the activation
procedure like for a first system server start. If the operating system is already
activated, it starts the system server normally.
Select the check box, for example, if:
 You move the VM file (.vdi) to a different computer. In such case,
Microsoft® Windows® 7 detects the hardware change and requires
reactivation.
 You are still using the 30-day trial period and want to activate the operating
system of the VM by using a product key.
Default value: Cleared (false)

104 EIO0000001255 11/2017

 Configuring Process Expert

Managing Participant Extensions

Overview
This topic describes how to use the Extensions section of the System Server Configuration Wizard
to install generic station description (GSD) files and device type managers (DTMs) in the Control
Participant of the system server VM. You can use these extensions to configure topological entities
in the Topology Explorer.
It also describes how to install other extensions such as libraries containing Control resources that
you need to refine Control Participant projects.
Process Expert provides silent and manual installation modes. For the installation of GSD files
(manual mode only), installation files are provided to facilitate the installation.
You can install extensions only in the VM of the system server. Each time you make a change in
the Virtual Machine or Extensions sections of the system server configuration wizard and you start
the system server, the extensions that appear in the Extensions section are reinstalled.
Process Expert transfers or installs automatically to clients that use a VM the extensions that are
installed in the VM of the system server.
If the installation of an extension does not complete successfully or if you cancel it, the VM does
not start.
NOTE: Use the Extensions section also to install hotfixes in software Participants (see page 112).

Transferring Extensions to Clients

When an engineering client connects to the system server once it is started, Process Expert
transfers or installs automatically to the VM client-side (see page 89) the extensions that are
installed in the system server VM.
If the generation of the saved states of the client VM is done locally, the silent and manual
installations are repeated client-side exactly like they were executed server-side. Installations in
manual mode require the same user intervention.
NOTE: If you have installed or removed an extension while an engineering client was still open,
the next time the engineering client queries a Participant, Process Expert detects the difference
and restarts the VM of the engineering client to synchronize it with the system server VM.

EIO0000001255 11/2017 105

Configuring Process Expert

Supported Installation File Types and Installation Methods

File type Installation mode Comment

.exe and .msi Silent or manual To install DTMs by using an InstallShield response file ([Link]),
Default mode: refer to the appendices (see page 151).
Manual.
.gsd The installation requires using the InstallGsd folder, which is a
subfolder of the VM Extensions folder located in the root of the
Process Expert installation package (.iso).
NOTE: Manual mode is the recommended installation method for
this file type.
.bat You can create your own batch file and have it executed.

Process Expert installs extensions one after the other in the order that is assigned to them
(see page 107).
The timeout for a silent installation is 10 min. If the installation is not completed within this period,
it is considered not successful.
If the installation in silent mode does not complete successfully, after the timeout is elapsed,
installation starts over in manual mode automatically. This can be the case, for example, if during
a silent installation user interaction is required for the installation to continue or complete.
The following restrictions apply:
 You can only install DTMs that create a [Link] file once installation is completed. Refer to the
alternate procedure (see page 151).
 You cannot use silent installation for nested installers.
 You cannot install an extension that requires a restart of the VM after installation.

NOTE: When you install DTMs, the DTM update dialog box of the Control Participant is displayed
even if the DTM is installed in silent mode.

Recommendations
To reduce the possibility of unsuccessful installation:
 Do not place installation files in the root directory of a drive or on the desktop of the PC before
selecting them for installation. Instead, place installation files of each extension in a separate
folder because the software copies the entire folder containing the setup file (see page 106) (for
example, [Link]) to another location to proceed with the installation.
 When possible, use the .msi file for the installation rather than the .exe file.
 Extract compressed installation files (.exe or .msi) and place them in a folder, which does not
contain the compressed archive.
 Close all clients before installing or removing extensions.

106 EIO0000001255 11/2017

 Configuring Process Expert

Extensions Section
The following figure shows an example of the Extensions section of the system server
configuration wizard, which lets you install and remove DTMs, GSD files, and other types of
extensions in the VM of the system server.

Item Description
1 Opens the Browse for extension dialog box, which allows you to browse to and select the .exe, .msi., or .bat
file of extensions that you want to install.
2 Once you have selected an extension, its path appears under Extension Name.
Extensions that are already installed or that you had added but that did not install successfully remain in the
list of extensions with the order they were assigned when you last saved the configuration wizard settings.
When you click Save & Close, the folder containing a newly selected extension file (.exe, .msi, or .bat) is
copied to the path C:\Users\<Username>\AppData\Local\Schneider Electric\Process Expert
4.2\VmExtensions\UserExtensions. This is the location from where the extension is installed. You cannot
install extensions by copying installation files to this folder manually.
Clicking Cancel in the System Server Configuration Wizard section removes from the list of extensions any
extensions, which have not yet been copied to the UserExtensions folder.
NOTE: Once the folder containing the extension file has been copied to the UserExtensions folder, the path
that appears under Extension Name is updated when you reopen the System Server Configuration Wizard.
It shows the name of the extension installation file and its parent folder. The full path appears in a tooltip.
3 Indicates the order in which extensions are installed.
You can change the order of installation by dragging an extension up or down to another row.

EIO0000001255 11/2017 107

Configuring Process Expert

Item Description
4 Lets you select the installation mode of the extension (see page 106).
NOTE: Selecting silent mode may not install the extension successfully if the extension does not support
silent mode because, for example, the user is required to provide information during installation.
5 Lets you remove extensions from the list of extensions:
 Not yet installed extensions are not installed.
 Already installed extensions are uninstalled from the VM.

You need to confirm the command.

Starting the system server uninstalls from the VM the extensions that you have removed.
NOTE: The extension is removed from the extensions list only after you click Save & Close. Until you do
so, clicking Cancel in the System Server Configuration Wizard section cancels the removal and restore the
extension to the list of extensions.
6 Lets you replace an extension by another one without changing the order. The installation mode is reset.
7 Resets the installation mode of all the extensions that appear in the list of extensions to Manual.

108 EIO0000001255 11/2017

 Configuring Process Expert

Installation of Extensions Window

Installations for which you select manual mode or that switch to this mode open the Installation of
Extensions window.
It displays dialog boxes pertaining to the verbose installation mode of extensions. You need to
interact with these dialog boxes to complete the installation of the extension.
The window closes automatically when installation is complete.
NOTE: Do not interact with elements of the Installation of Extensions window other than the dialog
boxes of the installer. Closing the window cancels the installation of the extension.

EIO0000001255 11/2017 109

Configuring Process Expert

Installing Extensions in Manual Mode

To install an extension by using the manual installation mode, proceed as follows.

Step Action
1 Open the Extensions section of the System Server Configuration Wizard.
2 Open the Browse for extension dialog box and select the installation file (.msi, .exe or, or .bat)
of the extension that you want to install.
NOTE:
If you want to install extensions by using .gsd files, first perform the following steps:
1. Copy the InstallGsd folder (see page 106) to disk. You can change the name of the folder.
2. Copy the extension files (.gsd) to the InstallGsd folder. You can create subfolders.
3. In the Browse for extension dialog box, browse to the InstallGsd folder and select the
[Link] file.
3 Modify the order if required.
4 Click Save & Close.
Result: Folders containing newly selected extension files are copied to the UserExtensions
folder. Once files and folders are copied, the System Server Configuration Wizard window
closes.
5 Starting the system server starts the VM and initiates the installation of the extensions that
appear in the list of extensions.
Result: The Installation of Extensions window opens.
6 Follow the instructions in the dialog boxes that appear in the Installation of Extensions window.
Result: Once you complete the installation of the extension, the Installation of Extensions
window closes.
NOTE: When you install extensions by using .gsd files, a command prompt window also opens
in the Installation of Extensions window. You need to close the command prompt window after
you have interacted with the installer dialog boxes for the Installation of Extensions window to
close.
NOTE: If you close the Installation of Extensions window manually or cancel the installation of
an extension, the system server starts but without starting the VM.
7 When the installation of DTMs is completed, the Installation of Extensions window opens again
and displays the FDT/DTM Catalog dialog box of the Control Participant.
If the FDT/DTM Catalog dialog box requires any interaction, follow the instructions on screen;
otherwise the dialog box and the Installation of Extensions window close automatically after the
DTM catalog has been updated with the newly installed DTMs.
NOTE: If you do not interact with the FDT/DTM Catalog dialog box when it is required before
the timeout elapses, the Installation of Extensions window closes and installation of the DTM is
considered not successful.
8 When the installation of extensions is completed, the result of the installation (see page 113) is
indicated in the system server console under Result of application of user extensions. Review
the entries.
Startup of the system server continues.

110 EIO0000001255 11/2017

 Configuring Process Expert

Installing Extensions in Silent Mode

To install an extension by using the silent installation mode, proceed as follows.

Step Action
1 Open the Extensions section of the System Server Configuration Wizard.
2 Open the Browse for extension dialog box and select the installation file (.msi, .exe or, or .bat)
of the extension that you want to install.
3 Modify the order if required.
4 Select Silent as installation mode.
5 Click Save & Close.
Result: Folders containing newly selected extension files are copied the UserExtensions folder.
Once files and folders are copied, the System Server Configuration Wizard window closes.
6 Starting the system server starts the VM and initiates the installation of the extensions that
appear in the list of extensions.
Result: When the installation of DTMs is completed, the Installation of Extensions window
opens and displays the FDT/DTM Catalog dialog box of the Control Participant.
NOTE: The installation of an extension may restart in manual mode.
7 If the FDT/DTM Catalog dialog box requires any interaction, follow the instructions on screen;
otherwise the dialog box and the Installation of Extensions window close automatically after the
DTM catalog has been updated with the newly installed DTMs.
NOTE: If you do not interact with the FDT/DTM Catalog dialog box when it is required before
the timeout elapses, the Installation of Extensions window closes and installation of the DTM is
considered not successful.
8 When the installation of extensions is completed, the result of the installation (see page 113) is
indicated in the system server console under Result of application of user extensions. Review
the entries.
Startup of the system server continues.
9 Once the system server is started and you have started an engineering client, if an extension
that you have added was installed in silent mode, confirm that it is installed correctly.
If not, open the System Server Configuration Wizard, change the installation mode to Manual,
and start the system server again.

EIO0000001255 11/2017 111

Configuring Process Expert

Installing Hotfixes in the Control Participant

The table describes the steps that you need to perform to install a hotfix in the Control Participant
by using the Extensions section of the system server configuration wizard.

Step Action
1 Create a folder on the PC on which the system server is installed and name it, for example,
MyHotFix.
2 In this folder, create a new text file and name it [Link].
3 Edit the file and enter the following two lines.
reg ADD "HKEY_LOCAL_MACHINE\Software\Schneider
Electric\Common\UnityProHotFix" /v SilentMode /t REG_SZ /d ON /f
[Link] /auto (where abc is the name of the hotfix executable file (for example,
UnityPro_V81_HF123))
4 Save the [Link] file.
5 Copy the hotfix executable file (.exe) to the same folder.
6 Select the [Link] file from the Extensions section of the system server configuration
wizard and follow the procedure describing how to install extensions in manual mode
(see page 105).

NOTE: If you are installing several hotfixes, you can add an entry for each (second line) in the
[Link] file and place all the hotfix executable files (.exe) in the same folder.

Changing the Time Zone of the VM Operating System

The table describes the steps that you need to perform to change the time zone of the operating
system of the VM..

Step Action
1 Create a folder on the PC on which the system server is installed and name it, for example,
MyTImeZone.
2 In this folder, create a new text file and name it [Link].
3 Edit the file and enter the following line.
[Link] /s "<time zone>"
Where <time zone> is the time zone that you want to use.
For example, [Link] /s "Pacific Standard time"
NOTE: You can obtain your current time zone by typing [Link] /g in a command
prompt. To obtain a list of valid time zones and their display name, use the /l option.
4 Save the [Link] file.
5 Select the [Link] file from the Extensions section of the system server configuration
wizard and follow the procedure described in this topic.

112 EIO0000001255 11/2017

 Configuring Process Expert

Confirming Extension Installation

You can verify which extensions are installed and the status of an installation:
 In the system server log (see EcoStruxure
TM Hybrid DCS, User Guide).
 In the system server console under Results of application of user extensions. This section also
lists system extensions that Process Expert installs in addition to those that you add in the
Extensions section. However, it does not list extensions that you have installed by using .gsd
files.
 By refining any Control Participant project and confirm the presence of the extensions in the
Participant.

Impact on Extensions when Connecting a Client to Different System Servers

When a client is connected to a remote system server on which extensions are installed, these
extensions are also installed in the VM of the engineering client (local computer).
If you connect this client to a local system server on which no extensions are installed, the
previously installed extensions remain in the VM, which is now shared by the engineering client
and the system server on the local computer.
These extensions may appear in the Extensions section of the local system server. In such case,
you can remove them from the local system server if they are not required. This does not remove
them from the remote system server.

EIO0000001255 11/2017 113

Configuring Process Expert

Activating the Virtual Machine

Activating the Virtual Machine

The first time you start a Process Expert component that uses a virtual machine (VM), you need to
activate the Microsoft® Windows® operating system of the VM by using the corresponding
configuration wizard (see page 95) and entering a suitable product key (see page 22).
You must purchase activation keys separately.
If you do not have an activation key yet, you can use the 30-day trial period.
The trial period is used by default when you start a component without using its configuration
wizard.
Thereafter, you need to use the configuration wizard again in the following cases:
 To activate the operating system of the VM after the 30-day trial period has expired.
 To activate the operating system of the VM if you replaced the VM file (.vdi).

NOTE: Process Expert components cannot provide Participant services if the trial period is expired
and the operating system of the VM is not activated.

Activating the Virtual Machine Manually

If an attempt to activate the operating system of the VM over the Internet does not complete
successfully, the manual activation procedure is started automatically, which allows you to activate
the operating system over the phone.
However, you can force the software to use manual activation by selecting the corresponding
parameter (see page 96).
The manual activation procedure still provides you with the option to activate over the Internet if
you want to make another attempt to activate it by using this method.

Using the 30-Day Trial Period

The first time you start a Process Expert component that uses a VM, the 30-day trial period of the
operating system of the VM begins unless you activate the operating system of the VM. During the
trial period, you can use the VM and its Participant services.
When you start a component, the expiry date of the trial period of its VM is indicated:
 In the console of the system server during startup.
 In the notification panel of clients.

114 EIO0000001255 11/2017

 Process Expert
Starting Process Expert
EIO0000001255 11/2017

Chapter 7
Starting Process Expert

Starting Process Expert

Overview
This section describes the system server console and the various actions that you can perform by
using its commands. It also describes how to start the system server and engineering clients for
the first time.
For information on how to start the operation client, refer to the topic describing how to set up
runtime navigation services (see EcoStruxureTM Hybrid DCS, Runtime Navigation Services, User
Guide).
For additional information on how to start and quit Process Expert, including logging in to clients
and client/server connection, refer to the topic that describes starting and quitting Process Expert
(see EcoStruxureTM Hybrid DCS, User Guide).

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
System Server Console 116
Backing Up and Restoring Process Expert Databases 118
Starting the System Server 121
Starting the Engineering Client 124

EIO0000001255 11/2017 115

Starting Process Expert

System Server Console

Overview
When you double-click the Process Expert system server icon, the system server console opens.
The console lets you:
 Start, stop, and configure the system server.
 Back up, restore, and delete databases of the current version of Process Expert.
 Back up databases of the current version of Process Expert to migrate them to a later version.

NOTE: To back up individual systems, use the corresponding command from the system context
menu in the Systems Explorer of the engineering client (see EcoStruxureTM Hybrid DCS, User
Guide).

System Server Console Menus

The table describes the commands of the Action menu in the system server console.

Command Description
Start Starts the system server.
NOTE: If you had restored a Process Expert database of a supported
earlier version, it migrates the database (see page 80).
Stop Stops the system server and closes the console after you confirm the
command (see EcoStruxureTM Hybrid DCS, User Guide).
Executing the command when the console is open and the system server
is stopped closes the console.

The table describes the commands of the Tools menu in the system server console. The
commands are disabled when the system server is running.

Command Description
Configure Opens the Server Configuration Wizard, which lets you configure the system server
and its virtual machine.
Back Up Database Opens a Save as dialog box, which lets you save (see page 118) the mounted
Process Expert database to disk as one file (.dbk).
Restore Database Opens an Open dialog box, which lets you mount a Process Expert database from
a backup file (.dbk) created by using the Back Up Database command.
You can only restore databases that have been created with the version of
Process Expert that is installed, its service packs, and supported earlier versions.
NOTE: The software creates a copy of the database folder (see page 118) before
restoring the one that you have selected.
(1) The command is available only when the system server is running. Clients need to be closed.

116 EIO0000001255 11/2017

 Starting Process Expert

Command Description
Delete Database Allows you to remove the Caché database entries pertaining to the installed
Process Expert databases.
The command is available only in either of the following cases:
 The Db folder on the computer on which the system server is installed is either
empty or missing.
 The [Link] file is missing in the GLOBAL and SCHEMA subfolders and no
System_n system exists in the Db folder.
For more information, refer to the troubleshooting section (see page 139).
Migrate Database (1) Opens a Save as dialog box, which lets you save the mounted database to disk as
one file (.mdbk).
The command lets you create a backup file of databases of the current version that
you can migrate to a later version of Process Expert once you have installed it.
Use this command on each database that you want to migrate before installing the
Process Expert upgrade.
If the database contains systems with password-protected Control projects
(see EcoStruxureTM Hybrid DCS, User Guide) deployed to topological entities, you
must provide the password for each one to be able to proceed with the creation of
the database backup file.
NOTE: You cannot restore this backup file (.mdbk) in the same version of
Process Expert. To do so, create a backup file by using the Back Up Database
command.
(1) The command is available only when the system server is running. Clients need to be closed.

EIO0000001255 11/2017 117

Starting Process Expert

Backing Up and Restoring Process Expert Databases

Overview
Data of systems that you create with Process Expert is stored in the database. It also contains the
templates of the General Purpose library.
You can back up a database as a file (.dbk) and restore a database from such a backup file by
using the corresponding commands in the system server console menu (see page 116).
Database backup files can only be used with the version of Process Expert that was used to
created them.
Exceptions apply for certain supported versions of databases that you can restore to migrate them
to the current version. This is the case, for example, for certain service packs or when Participants
are compatible from one version to the other.
NOTE: You can also back up and restore individual systems by using the corresponding
commands from the context menu in the Systems Explorer of the engineering client
(see EcoStruxureTM Hybrid DCS, User Guide). A system backup contains less data than a
database backup (for example, it does not contain templates) and is version dependent.

Backing Up and Restoring Databases for Migration

To create a database backup file of the current version of Process Expert in order to migrate and
reuse it in a later version, use the Migrate Database command (see page 116).

Control Project Password Management After Restoring a Database

After you restore a database that contains a controller and/or a station node for which password
protection (see EcoStruxureTM Hybrid DCS, User Guide) has been enabled, you need to do the
following to be able to deploy a Control Participant project:
 If no password was set, you need to set one.
 If a password was set, you need to enter the password when prompted.

For more information, refer to the topic describing how to manage passwords for Control
Participant projects (see EcoStruxureTM Hybrid DCS, User Guide).

Managing Database Backup Files

Database backup files that the software creates when you restore databases can use up a lot of
disk space. Manage these folders regularly to recover disk space.

118 EIO0000001255 11/2017

 Starting Process Expert

Backing Up a Database
You can back up databases only when the system server is stopped.

NOTICE
LOSS OF COMMUNICATION
Stop the system server only when no client is running.
Failure to follow these instructions can result in unresponsive clients.

To back up the Process Expert database, proceed as follows.

Step Action
1 Quit any Process Expert clients that connect to the system server whose database you want to
back up (see EcoStruxureTM Hybrid DCS, User Guide).
2 Stop the system server (see EcoStruxureTM Hybrid DCS, User Guide).
Result: The system server console closes.
3 Open the system server console by double-clicking the PES icon.
4 From the system server console menu, select Tools → Back Up Database.
Result: A Save as dialog box opens.
5 Select a file name and location for the database backup and click Save.
Result: Process Expert starts the back-up process and displays Done in the system server
console when the operation is completed.

Restoring a Database
When you restore a database, the software creates a copy of the existing database folder before
mounting the new database.
The name of the database folder copy is created by adding the suffix _YYYYMMDDHHMMSS to the
name of the database folder, where YYYYMMDD represents the date and HHMMSS the time when the
copy was created.
The copy of the database folder is stored at the path:
C:\ProgramData\Schneider Electric\Process Expert x.y, where x.y represents the version of
Process Expert that you are using.
You can restore databases only when the system server is stopped.

NOTICE
LOSS OF COMMUNICATION
Stop the system server only when no client is running.
Failure to follow these instructions can result in unresponsive clients.

EIO0000001255 11/2017 119

Starting Process Expert

To restore a Process Expert database, proceed as follows.

Step Action
1 Quit any Process Expert clients that connect to the system server (see EcoStruxureTM
Hybrid DCS, User Guide).
2 Stop the system server (see EcoStruxureTM Hybrid DCS, User Guide).
Result: The system server console closes.
3 Open the system server console by double-clicking the PES icon.
4 From the system server console menu, select Tools → Restore Database.
Result: An Open dialog box opens.
5 Select a database backup file (.dbk) and click Open.
Result: Process Expert:
 Creates a copy the existing database.
 Starts the restore process of the selected file.
 Displays Done in the system server console when the database is mounted.

NOTE: If the restore operation does not complete successfully, Process Expert restores the
previously mounted database.

120 EIO0000001255 11/2017

 Starting Process Expert

Starting the System Server

Overview
From the System Server console (see page 116), before starting the system server for the first
time, you need to configure (see page 82) server settings and the virtual machine (VM) if you have
installed it.
Start the Process Expert system server before starting any clients.
A first system server start may take several minutes because it:
 Installs extensions that you have added to the Extensions section of the configuration wizard.
 Starts one instance of the VM.
 Generates the saved states of the VM.
 Imports templates into the Global Templates, which creates the database.

If you have restored a database of an earlier version of Process Expert, this time is significantly
longer because of the additional steps that the software carries out to migrate it. Depending on the
size of the database, the process may take hours.
Once you start the system server, you cannot stop it until startup is completed.
Refer to Starting and Quitting Process Expert (see EcoStruxureTM Hybrid DCS, User Guide) for
more information on working with the system server and clients.
NOTE: Before you can start the system server, you must activate your Process Expert licenses on
the Floating License Manager.

Starting with Default Settings

If you start the system server without using its configuration wizard, default settings are applied to
the VM and server settings.
For information on default settings, refer to the topic describing the configuration of Process Expert
(see page 87).

Server Activity Log

The System Server console allows you to monitor and keep track of the server activity until you
stop it. The history of activity data is logged in a log file (see EcoStruxureTM Hybrid DCS, User
Guide).

EIO0000001255 11/2017 121

Starting Process Expert

Starting the System Server for the First Time

The Process Expert system server does not manage user rights.

NOTICE
LOSS OF DATA
Allow only authorized personnel to start or use the Process Expert system server.
Failure to follow these instructions can result in unusable systems or database.

To start the system server for the first time, proceed as follows.

Step Action
1 Configure (see page 87) the system server and its VM settings as needed.
2 Verify that Caché (see page 78) is running by checking the presence and the color of the Caché
notification area icon. When Caché is running, its notification area icon is blue.
3 From the Windows® start menu, click All Programs → Schneider Electric → StruxureWare →
Process Expert → System Server.
Result: The system server console opens.
NOTE: You can also double-click the PES icon on the desktop if it has been created during
software installation.
4 If you want to migrate a database, in the system server console (see page 116) click Tools →
Restore Database and select a database backup file (.dbk) that you had created with a
supported earlier version of Process Expert. Otherwise, proceed to step 5.
Result: The software mounts the database and prepares it for migration.
5 Click Action → Start.
Result: The system server starts up and creates a new, blank database (see page 52). If you
had restored a database backup file in the previous step, the system server migrates this
database instead to make it compatible with the installed version of Process Expert.
NOTE: If you have not activated the software license on the License Manager, the system
server displays a notification and stops.
6 If before starting the system server, you had entered a Microsoft® Windows® 7 product key, and
had selected the option to activate the VM manually in the System Server Configuration Wizard,
a Microsoft® Windows Activation dialog box opens. Otherwise, the system server activates the
VM over the Internet and resumes its startup; proceed to step 8.
NOTE: If you entered a wrong Microsoft® Windows® product key, the manual activation dialog
box does not open and the server displays a message in the console. Open the Server
Configuration Wizard (see page 96) and enter the correct product key. The new value takes
effect at the next restart of the system server.

122 EIO0000001255 11/2017

 Starting Process Expert

Step Action
7 In the Windows Activation dialog box, select See other ways to activate → Use the automated
phone system.
Follow the instructions on screen to complete the manual activation of the VM.
NOTE: If you cancel the manual activation process, the VM is not activated. You need to open
the Server Configuration Wizard and force re-activation of the VM.
8 Wait until the system server console displays the following message at the bottom of the window
to start the engineering client (see page 124): Server is ready.
9 Click the minimize button of the system server console.
Result: The system server console is minimized to an icon in the task bar.

Troubleshooting System Server Startup

If you experience difficulties during system server startup, refer to the troubleshooting topic
(see page 138).

EIO0000001255 11/2017 123

Starting Process Expert

Starting the Engineering Client

Overview
Start the Process Expert system server (see page 121) before starting any client.
Before you start the engineering client for the first time, you need to configure (see page 82) the
server settings and the virtual machine (VM) that the engineering client is using.
The complete start-up of an engineering client may take several minutes if the client uses its own
VM and generates the saved states of the virtual machine (see page 89) and/or installs extensions
(see page 105) locally.
Refer to Starting and Quitting Process Expert (see EcoStruxureTM Hybrid DCS, User Guide) for
more information on working with the system server and clients.

Starting with Default Settings

If you start the engineering client without using its configuration wizard, default parameters are
applied to the System Server and Virtual Machine settings of the VM.
For information on default settings of the VM, refer to the topic describing the configuration of
Process Expert (see page 87).

Client Activity Log

The Notification Panel allows you to monitor and keep track of the engineering client activity until
you stop the system server. To keep the history of data that is displayed in the notification panel,
you need to export the data (see EcoStruxureTM Hybrid DCS, User Guide).
Other client activity is logged in log files (see EcoStruxureTM Hybrid DCS, User Guide).

124 EIO0000001255 11/2017

 Starting Process Expert

Starting the Engineering Client

Process Expert clients authenticate users against Microsoft® Windows® Active Directory®
domain services or the Windows® user database of the local PC.

WARNING
UNINTENDED EQUIPMENT OPERATION
The application of this product requires expertise in the design and operation of control systems.
Allow only authorized personnel to start or use this software.
Failure to follow these instructions can result in death, serious injury, or equipment damage.

After an unexpected interruption of the client/server connection, the states of both the engineering
client and the system server may have become inconsistent. This can be the case, for example, if
at the time of the interruption an operation was in progress such as an import of several Participant
projects or pasting of many instances.

NOTICE
LOSS OF COMMUNICATION
After an interruption of the client/server connection, verify that the last operation executed by the
software was completed successfully, and if necessary, repeat the last operation.
Failure to follow these instructions can result in unresponsive clients.

NOTE: It is recommended to use the Notification Panel of the engineering client to verify the status
of each task executed through a task menu command. The history of other client-related activity
data is logged in log files (see EcoStruxureTM Hybrid DCS, User Guide).
To start the engineering client for the first time, proceed as follows.

Step Action
1 Configure the server and VM settings as needed by using the configuration wizard.
2 With the system server running, from the Windows® start menu, click All Programs → Schneider
Electric → StruxureWare → Process Expert → Engineering Client.
Result: Process Expert displays a splash screen to indicate that the engineering client is starting.
After a few moments, the Log In dialog box opens.
NOTE: You can also double-click the client icon on the desktop if it has been created during
software installation.
3 Log in by using your Microsoft® Windows® credentials (see EcoStruxureTM Hybrid DCS, User
Guide).
NOTE: Close the Log In dialog box to quit the engineering client.

EIO0000001255 11/2017 125

Starting Process Expert

Step Action
4 Click OK.
Result: The Systems Explorer opens and VM-related start-up tasks continue executing. Information
about these tasks is available in the notification panel. You can use the engineering client in the
meantime but Participant services are not available until the VM is fully started.
5 If you have configured the engineering client to use the local VM, selected to use a custom
configuration, and before starting the engineering client, you had entered a Microsoft® Windows® 7
product key, and selected the option to activate the VM manually in the Engineering Client
Configuration Wizard, a Microsoft Windows Activation dialog box opens. If you have not selected
manual activation, the VM is activated over the Internet (if applicable) and the VM continues starting
up.
NOTE: If you entered a wrong Microsoft® Windows® product key, the manual activation dialog box
does not open and the client displays a message in the Notification Panel. Open the Engineering
Client Configuration Wizard window (see page 96) and enter the correct product key. The new
value takes effect when you restart the client.
6 In the Windows Activation dialog box, select See other ways to activate → Use the automated
phone system.
Follow the instructions on screen to complete the manual activation of the VM.
NOTE: If you cancel the manual activation process, the VM is not activated. You need to open the
Engineering Client Configuration Wizard and force the reactivation of the VM.

NOTE:
If you start the engineering client:
 Before the system server, the client displays a notification that it cannot locate the server.
 While the system server is still starting up, the splash screen of the client is displayed until the
server is up and running.

126 EIO0000001255 11/2017

 Process Expert
Modifying, Repairing, and Removing Process Expert
EIO0000001255 11/2017

Chapter 8
Modifying, Repairing, and Removing Process Expert

Modifying, Repairing, and Removing Process Expert

Overview
This chapter describes how to modify, repair, and remove Process Expert.

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
Modifying The Process Expert Installation 128
Repairing Process Expert 130
Removing Process Expert 132

EIO0000001255 11/2017 127

Modifying, Repairing, and Removing Process Expert

Modifying The Process Expert Installation

Overview
By using the modify functionality of the installer, you can perform the following actions after you
have installed at least one Process Expert component on the computer:
 Install one or more additional components (for example, an engineering client).
 Uninstall one or more installed components.

You can access the functionality from either:

 The installation package.
 The Uninstall or change a program window of the Microsoft® Windows® Control Panel.

The functionality is available for 64-bit Process Expert system infrastructures only.
When you remove an installed component, the installer checks the integrity of the files of remaining
components.
NOTE: To remove Process Expert from the computer use the remove functionality (see page 132).

Third-Party Software Components

When you select to install a new Process Expert component on the computer, required third-party
components are installed as well. However, when you uninstall a Process Expert component,
associated third-party components (see page 53) are not uninstalled.

Process Expert Licenses

When you add and/or remove Process Expert components from the computer, verify that you:
 Return licenses that have become unnecessary through the Floating License Manager.
 Activate licenses for newly installed components as needed.

For information on the return process, refer to the Schneider Electric Floating License Manager
user manual.

128 EIO0000001255 11/2017

 Modifying, Repairing, and Removing Process Expert

Modifying the Process Expert Installation

You can modify a Process Expert installation only when the system server is stopped.

NOTICE
LOSS OF COMMUNICATION
Stop the system server only when no client is running.
Failure to follow these instructions can result in unresponsive clients.

NOTICE
LOSS OF DATA
Back up the database of the Process Expert installation before modifying the installation.
Failure to follow these instructions can result in loss of database or unusable systems.

NOTE: For more information, refer to the topic describing how to back up the database
(see page 118).
To modify the Process Expert installation of a computer by using the installation package, proceed
as follows.

Step Action
1 Quit any Process Expert clients connected to the system server (see EcoStruxureTM Hybrid DCS,
User Guide).
2 Stop the system server (see EcoStruxureTM Hybrid DCS, User Guide).
3 Back up the database (see page 118) of the Process Expert installation.
4 On the computer whose installation you want to modify, double-click the [Link] file that is
located in the root of the Process Expert installation package.
Result: The installer dialog box opens.
5 Select Modify and click Next.
6 The dialog box shows the different Process Expert components that you can install. Those that
are already installed are selected:
 Select the check box of other components that you want to install.
 Clear the check box of installed components that you want to uninstall.
 Leave the check box of installed components that you want to keep selected.

7 Click Next.
Result: The software proceeds with the removal and/or installation of components according to
your selection.
8 Click Finish to exit the installer.
9 Restart the computer when prompted to do so to complete the installation process.

EIO0000001255 11/2017 129

Modifying, Repairing, and Removing Process Expert

Repairing Process Expert

Overview
If a Process Expert component is not working properly, you may be able to repair it by using the
repair functionality of the installer.
The installer attempts to fix missing or corrupt files, shortcuts, and registry entries.
You can access the functionality from either:
 The installation package.
 The Uninstall or change a program window of the Microsoft® Windows® Control Panel. Select
the Change command.
NOTE: Third-party components are not repaired. If a third-party component that is required is not
installed (for example, because it has been uninstalled), the installer installs it.

Repairing the Process Expert Installation

You can repair a Process Expert installation only when the system server is stopped.

NOTICE
LOSS OF COMMUNICATION
Stop the system server only when no client is running.
Failure to follow these instructions can result in unresponsive clients.

NOTICE
LOSS OF DATA
Back up the database of the Process Expert installation before repairing the installation.
Failure to follow these instructions can result in loss of database or unusable systems.

NOTE: For more information, refer to the topic describing how to back up the database
(see page 118).

130 EIO0000001255 11/2017

 Modifying, Repairing, and Removing Process Expert

To repair the Process Expert installation on a computer by using the installation package, proceed
as follows.

Step Action
1 Quit any Process Expert clients connected to the system server (see EcoStruxureTM Hybrid DCS,
User Guide).
2 Stop the system server (see EcoStruxureTM Hybrid DCS, User Guide).
3 Back up the database (see page 118) of the Process Expert installation.
4 On the computer on which the component that you want to repair is installed, double-click the
[Link] file that is located in the root of the Process Expert installation package.
Result: The installer dialog box opens.
5 Select Repair and click Next.
Result: The software attempts to repair the installed Process Expert components.
6 Click Finish to exit the installer.
7 Restart the computer when prompted to do so to complete the repair process.

EIO0000001255 11/2017 131

Modifying, Repairing, and Removing Process Expert

Removing Process Expert

Overview
This operation removes Process Expert from the computer. The database that contains the data
of existing systems is not removed.
Nevertheless, consider backing up data of existing systems (see page 118).
You can access the functionality from either:
 The installation package.
 The Uninstall or change a program window of the Microsoft® Windows® Control Panel.

To remove Process Expert components individually, use the modify functionality (see page 128).
A restart is required to complete the process of uninstalling Process Expert from the computer.
NOTE: The process does not remove the Schneider Electric License Manager and Floating
License Manager.

Removing Third-Party Components

By default, when you remove Process Expert by using the installer or the Change command of the
Microsoft® Windows® Control Panel, the process also removes the following third-party
components if they are installed:
 Oracle® VM Virtualbox, the application managing the virtual machine.
 The virtual machine image file (.vdi).
 Caché, the application managing the database. However, the InterSystems folder is not
removed. You need to remove it manually. The folder is located at the path: C:\Program Files.
Clear the check box to keep these components on the computer.
When you remove Process Expert by using the Uninstall command from the
Microsoft® Windows® Control Panel, these third-party components are not removed.
When you remove the virtual machine, you lose any changes that you have made to it (for example,
updates of the Libset of the Control Participant or installed device type managers (DTMs)).
NOTE: When removing Oracle® VM Virtualbox software, you need to restart the computer;
otherwise, if you reinstall Process Expert without restarting the computer, it does not install
properly.

Removing Hotfixes
You can remove hotfixes that have been applied to Process Expert by using the Uninstall
command from the Microsoft® Windows® Control Panel. Navigate to the View Installed Updates
window under Programs and Features.
Applied hotfixes are listed in the Process Expert section.

132 EIO0000001255 11/2017

 Modifying, Repairing, and Removing Process Expert

Removing to Install an Earlier Version of Process Expert

If you are removing Process Expert to install an earlier version of it, you need to also remove these
third-party components (see page 132):
 Remove the InterSystems Caché and Oracle® VM Virtualbox applications.
 Delete the InterSystems folder, which is located at the path: C:\Program Files.

Returning Licenses
When you remove Process Expert from the computer, consider returning your licenses through the
Floating License Manager so that you may activate them again on a different computer.
For information on the return process, refer to the Schneider Electric Floating License Manager
user manual.

Removing Process Expert

You can remove Process Expert only when the system server is stopped.

NOTICE
LOSS OF COMMUNICATION
Stop the system server only when no client is running.
Failure to follow these instructions can result in unresponsive clients.

NOTICE
LOSS OF DATA
Back up the installed database before removing Process Expert.
Failure to follow these instructions can result in loss of database or unusable systems.

NOTE: For more information, refer to the topic describing how to back up the database
(see page 118).
The table describes the procedure to remove Process Expert from the computer by using the
installation package.

Step Action
1 Quit Schneider Electric applications that are running, Process Expert clients, and stop the
system server (see EcoStruxureTM Hybrid DCS, User Guide).
2 Back up the installed database (see page 118).
3 On the computer on which the component that you want to remove is installed, double-click the
[Link] file located in the root of the installation package.
Result: The installer dialog box opens.

EIO0000001255 11/2017 133

Modifying, Repairing, and Removing Process Expert

Step Action
4 Click Next.
5 Select Remove.
6 Follow the instructions on screen.
7 Click Finish to exit the installer.
8 Restart the computer when prompted to do so to complete the removal process.
NOTE: You can click No to restart the computer yourself later. However, a restart of the
computer is required before you start a new installation of Process Expert.

134 EIO0000001255 11/2017

 Process Expert
Troubleshooting
EIO0000001255 11/2017

Chapter 9
Troubleshooting

Troubleshooting

Overview
This chapter contains various troubleshooting information.

What Is in This Chapter?

This chapter contains the following topics:
Topic Page
Troubleshooting Installation 136
Troubleshooting the System Server 138
Troubleshooting the Virtual Machine 139
Troubleshooting Client/Server Communication 141
Troubleshooting USB Port Issues 142
Troubleshooting the Caché Database 145

EIO0000001255 11/2017 135

Troubleshooting

Troubleshooting Installation

Invalid Drive Notification During Installation

When you copy the installation package (ISO file) from the external hard drive to the PC and start
the installation from the PC when the copy is complete, you may receive a notification about an
invalid drive (1327) if you disconnect the external hard drive before the installation is finished.
Restart the installation and leave the external hard drive connected to the PC until the installation
of Process Expert is finished.

Notification During Installation of the Virtual Machine

The virtual machine file (.vdi) is included in the installation package as an archive file (.7z).
If the virtual machine file cannot be extracted during installation, the software displays a message
and cancels the installation of Process Expert. This may happen, for example, if the installation
package got corrupted during download.
In such case, you can verify the integrity of the installation package by using an MD5 checksum.
Follow the procedure that is available at [Link], Product Downloads
section.

Unable to Uninstall Process Expert by Using the Control Panel

If you are trying to remove Process Expert by using the Uninstall command in the
Microsoft® Windows® Control Panel and you receive a notification that the software cannot be
uninstalled because the installation log file cannot be opened, proceed as follows.

Step Action
1 Open Task Manager.
2 Stop the [Link] process.
3 Restart the [Link] process by clicking from the menu of the Task Manager, File → New
Task (Run...).
4 Enter [Link] and click OK.
5 Uninstall Process Expert again by using the Uninstall command.

136 EIO0000001255 11/2017

 Troubleshooting

Notification During Reinstallation Of Process Expert

Message from InterSystems Caché during the reinstallation of Process Expert.
The following figure shows the message that appears during the installation of Caché when
executed as part of the Process Expert Installation.

Reason: The temporary files in the %TEMP% folder of the PC exceed the limit of 65,535 files.
When the installation tries to create new temporary files, it cannot do so because the system limit
of 65,535 files has been reached. Therefore, the installation does not complete successfully and
an unrelated message is reported.
Solution: Delete no longer required files in the %TEMP% folder of the PC before installing
Process Expert.

EIO0000001255 11/2017 137

Troubleshooting

Troubleshooting the System Server

Delay Starting the System Server

If you experience delays of several minutes when starting the system server and you have
configured several Enterprise license servers in the LM, confirm that each IP address can be
reached from the PC on which the system server is installed.
For more information, refer to the topic describing the configuration of Enterprise license servers
(see EcoStruxureTM Hybrid DCS, Licensing Guide).

System Server Not Starting

If the system server console displays Cannot load Counter Name data because an invalid index “ ”
was read from the registry shortly after starting the system server, proceed as follows.

Step Action
1 Open a command prompt as administrator.
2 Change to C:\Windows\SysWOW64
3 Execute lodctr /r
4 Press Enter.
NOTE: You may see a message about a detected error: Unable to rebuild performance counter
setting from system backup restore, error code is 2
5 Restart the system server.

138 EIO0000001255 11/2017

 Troubleshooting

Troubleshooting the Virtual Machine

Virtual Machine Password Protection

During startup of the system server, a message appears in the server console with orange text
informing you of a VM password mismatch. This is not of concern as the VM of the system server
will automatically restart, which resolves the password mismatch. The VM may restart up to three
times.
The password mismatch happens in the following situation:
1. A system server and an engineering client are installed on computer A.
2. A system server is installed on computer B.
3. The engineering client of computer A is connected to the remote system server on computer B.
4. On computer A, you close the engineering client and start the local system server.
However, if the message still appears after three restarts or if in any other situation, the virtual
machine of the system server or a client is not starting and the server console or the client
notification panel displays either message, contact Schneider Electric technical support for
assistance:
 Password not matching
 Invalid length for a base-64 char array or string
 Bad credentials

Troubleshooting Virtual Machine Startup Difficulties

If the software displays notifications about the virtual machine not starting, you may have deleted
the Db folder, or all or part of its contents on the PC on which the system server is installed.
Notifications appear in:
 The system server console with text in red.
 The notification panel.

The Db folder contains the files of databases where Process Expert stores data of the Global
Templates library and of existing systems. The default path to the Db folder is
C:\ProgramData\Schneider Electric\Process Expert x.y (where x.y represents the version of
Process Expert).

EIO0000001255 11/2017 139

Troubleshooting

The figure shows an example of the contents of the Db folder for a healthy database with two
systems created. The right-hand section of the window shows the [Link] file that exists in
the GLOBAL and SCHEMA subfolders.

NOTE: Systems that appear in the Db folder keep their default name (System_n) even if you
rename them in the Systems Explorer.
Deleting the Db folder or some of its contents creates an inconsistency with the database entries
that exist in the Caché database.
In such case, you need to remove the Caché database entries pertaining to the installed
Process Expert databases to make them consistent with the file structure on the PC.
To remove Caché database entries, proceed as follows.

Step Action
1 In the Process Expert console menu (see page 116), click Tools → Delete database.
Result: The Delete Database dialog box opens.
2 Click Yes.
Result: The software removes Caché database entries.
NOTE: Click No to close the Delete Database dialog box without removing Caché database
entries.
3 Wait until the console displays Done to start the system server.

140 EIO0000001255 11/2017

 Troubleshooting

Troubleshooting Client/Server Communication

CPU-Intensive Operations
Performing CPU-intensive operations (for example, importing many instances or mapping many
interfaces) by using a Process Expert client on a PC on which the system server is installed may
lead to CPU starvation.
As a result, actions that you execute immediately after such CPU-intensive tasks may trigger
notifications about client/server communication interruptions.
Increase the priority of the [Link] or [Link] process to Above
Normal by using the Windows Task Manager.

Network Connections
The system server and its engineering stations need to be connected to the same Ethernet network
by a cable connection so that the system server, engineering, and operation clients are able to
communicate. This can be a network that is dedicated to client/server communication.
In case the PC on which the system server is installed is connected also to another network (for
example, an enterprise network providing access to the Internet), verify that an interruption of this
network connection does not block communication on the client/server network. This may happen,
for example, if a domain firewall is configured to disable all communication ports of the PC in case
the connection to the enterprise network is interrupted.

Communication Port Usage

Process Expert uses communication ports for client/server communication. If you experience
communication difficulties, verify if any of them are already used.
Refer to the topic describing how to configure the system server and clients (see page 93).

EIO0000001255 11/2017 141

Troubleshooting

Troubleshooting USB Port Issues

Problem Description
When you connect a USB drive to a PC on which the Process Expert system server and/or
engineering client is running, you may experience one or more of the following issues:
 You cannot eject the USB drive.
 The USB port stops responding.
 The PC does not hibernate anymore.
 The PC does not shut down anymore.
 The Microsoft® Windows® blue screen.

This is because the USB port monitoring service of the Oracle® VM Virtualbox application, the
third-party software managing the virtual machine (VM) of Process Expert, does not release the
USB port of the PC.

Recommendation
To transfer files between the host PC and the VM of the system server and/or the engineering
client, use the user-configurable folder that is shared with the VM (see page 95) rather than USB
drives.

Using USB Drives on Process Expert PCs

If you still need to use USB drives on the PC on which the system server and/or engineering client
is installed, two files are provided:
 [Link]: The file modifies registry settings to disable the USB port
monitoring service of the Oracle® VM Virtualbox application. This allows you to use USB drives
on the PC while the system server and/or engineering client is running. However, USB drives
are not recognized anymore by VMs run by the Oracle® VM Virtualbox application.
 [Link]: The file reverts registry settings to their original values to enable
the USB port monitoring service of the Oracle® VM Virtualbox application if you had disabled it.
This allows VMs run by the Oracle® VM Virtualbox application to recognize USB drives. Enable
the USB port monitoring service and use USB drives only when the system server and/or
engineering client is not running.
NOTE: Disable or enable USB port monitoring before connecting a USB drive to the PC.

Location of the Registry Entries Files

The registry entries (.reg) files are located in the VboxUSBMonitor folder, which is in the root of the
Process Expert installation package.

142 EIO0000001255 11/2017

 Troubleshooting

Disabling USB Port Monitoring

To disable the USB port monitoring service of the Oracle® VM Virtualbox application, you need to
stop the system server.

NOTICE
LOSS OF COMMUNICATION
Stop the system server only when no client is running.
Failure to follow these instructions can result in unresponsive clients.

To disable the USB port monitoring service of the Oracle® VM Virtualbox application, proceed as
follows.

Step Action
1 Close Process Expert engineering clients and the system server they connect to.
2 Restart the PC.
3 Copy the [Link] file to the PC on which you want to use USB drives.
4 Double-click the [Link] file.
Result: The Registry Editor dialog box opens.
5 Click Yes.
Result: The USB port monitoring service of the Oracle® VM Virtualbox application is disabled.

EIO0000001255 11/2017 143

Troubleshooting

Enabling USB Port Monitoring

To enable the USB port monitoring service of the Oracle® VM Virtualbox application, you need to
stop the system server.

NOTICE
LOSS OF COMMUNICATION
Stop the system server only when no client is running.
Failure to follow these instructions can result in unresponsive clients.

To enable the USB port monitoring service of Oracle® VM Virtualbox, proceed as follows.

Step Action
1 Close Process Expert engineering clients and the system server they connect to.
2 Restart the PC.
3 Copy the [Link] file to the PC on which you want to use USB drives.
4 Double-click the [Link] file.
Result: The Registry Editor dialog box opens.
5 Click Yes.
Result: The USB port monitoring service of the Oracle® VM Virtualbox application is enabled.

144 EIO0000001255 11/2017

 Troubleshooting

Troubleshooting the Caché Database

Problem Description
The Caché database does not start if you have changed the name of the computer while Caché
was running and have restarted the computer. The Caché icon in the notification area of
Microsoft® Windows® remains grey.
Attempting to start the Caché database manually opens a dialog box Cache Terminal could not
start (112).
Caché software stores the name of the computer in temporary files. When it starts, it compares the
name of the computer with the name stored in the files. If they do not match, the Caché database
does not start.

Recommendation
To change the name of the computer on which the Caché application is installed, first stop the
Caché application (see page 78).

Starting Caché
To get the Caché database to start again, proceed as follows.

Step Action
1 Browse to C:\Program Files\InterSystems\STRUXUREWAREPEv43\mgr.
2 Delete the following files:
 [Link]
 [Link]

3 Start the Caché (see page 79) database.

EIO0000001255 11/2017 145

Troubleshooting

146 EIO0000001255 11/2017

 Process Expert

EIO0000001255 11/2017

Appendices

What Is in This Appendix?

The appendix contains the following chapters:
Chapter Chapter Name Page
A Installing the Floating License Manager 149
B Installation of DTMs by Using a Response File 151

EIO0000001255 11/2017 147

148 EIO0000001255 11/2017
 Process Expert
Installing the Floating License Manager
EIO0000001255 11/2017

Appendix A
Installing the Floating License Manager

Installing the Floating License Manager

Installing the Floating License Manager

Overview
This topic describes how to install the Floating License Manager (FLM) on a PC that is to become
an enterprise license server, and on which no Process Expert nor Supervision components are
going to be installed.
For more information on how to use the FLM, refer to the topic describing licensing mechanisms
(see EcoStruxureTM Hybrid DCS, Licensing Guide).

Installation Procedure

Step Action
1 Double-click the FloatingLicenseManagerSetup_PE.exe file to extract the installation files.
The file is located inside the LicenseManagers folder of the Process Expert installation package.
2 Select a destination folder on the PC on which you want to install the FLM.
3 In this destination folder, double-click the [Link] file to start the installation.
4 Follow the instructions on screen.
NOTE:
Use the following values to configure parameters of the FLM (see EcoStruxureTM Hybrid DCS,
Licensing Guide):
 Server Port: 27010 (default value).
 Web Port: 8090 (default value).
 Startup Delay: 0 (default value).

5 Accept the End User License Agreement (EULA).

NOTE: To obtain the server port value that is used in other FLMs, refer to the topic describing how
to verify the license server port and Web port setting of the FLM (see EcoStruxureTM Hybrid DCS,
Licensing Guide).

EIO0000001255 11/2017 149

Installing the Floating License Manager

150 EIO0000001255 11/2017

 Process Expert
Installation of DTMs by Using a Response File
EIO0000001255 11/2017

Appendix B
Installation of DTMs by Using a Response File

Installation of DTMs by Using a Response File

Installing DTMs by Using a Response File

Overview
Use this procedure when the installation of a DTM in the Control Participant of the VM did not
succeed because the installation process does not generate the necessary log file (see page 106)
(silent and manual installation modes).
In this cases, the use of a response file ([Link]) allows completing the installation. The response
file records user entries and installation settings that are made during a temporary manual
installation from within the VM.
The response file is then added to the installation package of the DTM to be used during a silent
installation with the help of a batch file (.bat).

Copying the DTM Installation Files to a Folder

Step Action
1 On the computer on which the system server is installed, create a folder that you will be
accessing from the VM.
2 Copy the DTM installation files (.exe and any other required files) to this folder so that the
installation can be started from within the VM.

EIO0000001255 11/2017 151

Installation of DTMs by Using a Response File

Creating the [Link] Response File

To create the response file that you are going to include later on in the batch file, proceed as
follows.

Step Action
1 Confirm that the Process Expert system server is closed.
2 On the computer on which the system server is installed, from the Microsoft® Windows® start
menu, click All Programs → Oracle VM Virtualbox → Oracle VM Virtualbox.
Result: The Oracle VM Virtualbox Manager starts.
3 Verify that the [Link].x.y#0 VM is selected and click Settings → Shared Folders (x.y corresponds
to the version of Process Expert that is installed).
Click the folder icon with the + sign.
Result: The Add Share dialog box opens.

4 In the Folder Path menu, select Other... and browse to the folder that contains the DTM installation
file.
5 Click OK.

152 EIO0000001255 11/2017

 Installation of DTMs by Using a Response File

Step Action
6 Click OK to close the VM Settings window.
7 Verify that the [Link].x.y#0 VM is selected and click Start.
Result: The VM starts.
NOTE: The VM may start with a Windows Error Recovery message. In such case, press Enter to
start Microsoft® Windows® normally.

EIO0000001255 11/2017 153

Installation of DTMs by Using a Response File

Step Action
8 Select the Oracle Vm Virtualbox: 1 window and click the bottom left-hand corner of the screen to
make the Microsoft® Windows® task bar and start button appear. You may need to click several
times.

9 In the Oracle Vm Virtualbox: 1 window, click Start → Computer and browse to the shared folder
containing the DTM installation file.
To access the folder, expand Network, then VBOXSVR.
10 From the shared folder, copy the DTM installation file to the C: drive of the VM.
11 In the Oracle Vm Virtualbox: 1 window, click Start and enter cmd in the search field to open a
command prompt.
12 In the command prompt, type cd.. and press Enter until you are the C:\> prompt.

154 EIO0000001255 11/2017

 Installation of DTMs by Using a Response File

Step Action
13 Execute the DTM installation file with the /r option in order to generate the InstallShield response
file ([Link]).
The file is generated at the path C:\Windows.
Result: The DTM installation starts.
NOTE: This installation is only temporary and non-existing the next time you start the system
server.
The following example shows the SMARTSENS_PH_DTM_V1-1-3_Setup.exe DTM installation file,
which is executed from the command prompt with the /r option.

Your entries and settings are recorded in the response file.

14 Follow the steps on screen until the installation of the DTM is complete.

EIO0000001255 11/2017 155

Installation of DTMs by Using a Response File

Step Action
15 In the Oracle Vm Virtualbox: 1 window, copy the [Link] file to the folder shared with the VM so
that you can access it on the host computer.
16 Close all open windows inside the VM.
17 Close the VM by clicking from the menu of the Oracle Vm Virtualbox: 1 window, Machine →
Close → Power off the machine.
Result: The VM stops and the windows close.
18 Close the Oracle VM Virtualbox Manager.

Installing the DTM

To install the DTM by using the response file, proceed as follows.

Step Action
1 Confirm that the Process Expert system server is closed.
2 Locate the VM Extensions folder in the Process Expert installation package (.iso) and copy the
InstallGsd subfolder to the computer on which the system server is installed.
3 Open the InstallGsd folder and delete the [Link], which is not required.
4 Copy the uncompressed DTM installation file (.exe) and the response file ([Link]) to the
InstallGsd folder.
5 Edit the [Link] file inside the InstallGsd folder as follows.
@Echo off
echo installing DTM...
[Link] /s
echo Done
Where [Link] is the name of the DTM installation file.
(Remove the [Link] command.)
NOTE: The /s option installs the DTM in silent mode by using the data and installation settings
contained in the response file.
6 Save the changes to the [Link] file.
NOTE: If you want to install several DTMs, create the other entries ([Link] /s) in the
[Link] file and copy all the installation files and response files to the InstallGsd folder. You
can create subfolders inside the InstallGsd folder.
7 Open the Extensions section of the System Server Configuration Wizard.
8 Open the Browse for extension dialog box, browse to the InstallGsd folder, and select the
[Link] file.
9 Refer to the topic describing the installation of extensions in manual mode (see page 110) to
complete the procedure.

156 EIO0000001255 11/2017

 Process Expert
Index
EIO0000001255 11/2017

Index

Symbols BIOS
settings for virtual machines, 46
.NET Framework requirements
Windows 10, 58
Windows 8.1, 58 C
Windows Server 2012, 59
Cache
installed software components, 53
0-9 starting and stopping, 78
third-party software components, 51
32-bit databases
troubleshooting Cache not starting, 145
reusing, 70
client configuration wizards
32-bit Process Expert
activating virtual machines, 114
installing the update, 83
configuring virtual machines, 95
updating a 32-bit system infrastructure,
clients
69
configuring clients, 93
7-zip
configuring server settings, 94
unzipping the installation package, 49
connecting a client to different system
servers, 113
engineering client activity logs, 124
A service pack configuration information, 37
activating starting engineering clients, 124
virtual machine, 114 communication interruptions
activation client/server communication interrup-
using configuration wizards, 88 tions, 26
adding performance considerations, 26
adding a software component, 128 troubleshooting, 141
architectures communication ports
client/server communication interrup- settings and configuration, 93
tions, 26 troubleshooting, 141
physical architectures, 24 compatibility
physical VM architecture examples, 27 service pack database compatibility, 37
software architecture, 12 computers
hardware requirements, 46
configuration wizards
B activating virtual machines, 114
backing up parameters, 96
databases, 118 user accounts, 88
bad credentials using configuration wizards, 88
troubleshooting virtual machine password Configure
issues, 139 system server console commands, 116

EIO0000001255 11/2017 157

Index

configuring DFBs and DDTs

clients, 93 updated types supplied in the release, 73
system servers, 93 DTMs
using configuration wizards, 88 installing and removing, 105
connections installing DTMs with a response file, 151
network connections of servers and sta-
tions, 24
troubleshooting client-server connec- E
tions, 141 engineering clients
console engineering client activity logs, 124
system server console, 116 starting, 124
constraints extensions
firewall exceptions, 58 connecting a client to different system
Control Panel servers, 113
troubleshooting when uninstalling, 136 installing and removing, 105
Controller Simulator installing DTMs with a response file, 151
installing, 60

F
D files
database restoration sharing with the VM, 96
password information and settings, 118 firewall
databases firewall exceptions for Process Expert, 58
backing up, 118 Floating License Manager
migrating the database, 80 installed software components, 53
migrating to service packs, 42 installing, 149
migrating to the current version, 80 license server port setting, 55
overview of installation scenarios, 52 licensing software for service packs, 38
removing database of an earlier version, updating, 38
70 folders
restoring, 118 service pack destination folders, 39
reusing, 70
reusing 32-bit databases, 70
reusing service pack databases, 37 G
service pack database compatibility, 37 Global Templates
starting and stopping Cache, 78 supplied with Process Expert updates, 73
troubleshooting Cache not starting, 145 GSD files
troubleshooting database inconsisten- installing and removing, 105
cies, 139
Delete Database
system server console commands, 116 H
Delete database hardware
troubleshooting database inconsisten- hardware requirements, 46
cies, 139 service pack hardware requirements, 35

158 EIO0000001255 11/2017

 Index

host PC installing
sharing files with the VM, 96 32-bit Process Expert update, 83
hosting Floating License Manager, 149
system server configuration wizard, 93 installing an earlier version of Process Ex-
hotfixes pert, 133
installing control Participant hotfixes, 112 installing Process Expert service pack, 40
removing applied hotfixes, 132 removing applied hotfixes, 132
service pack hotfix compatibility, 36 supervision software, 65
service pack hotfixes, 36 virtual machines, 15
hypervisors invalid drive
compatibility with virtual machines, 15 troubleshooting installation, 136
invalid length message
troubleshooting virtual machine password
I issues, 139
installation ISO
general installation information, 52 verifying integrity of ISO file, 136
installation log files, 56
installed software components, 53
modifying the installation, 128 K
overview of installation scenarios, 52 keyboard layouts
PES service pack licenses, 34 configuration wizard for virtual machines,
service pack compatibility with Unity Pro, 96
35
service pack destination folders, 39
service pack installation log files, 39 L
troubleshooting, 136 languages
unable to extract the VM file, 136 default keyboard layout of virtual ma-
update installation procedure, 82 chines, 96
installation files user interface language, 36
unzipping, 49 License Manager
installation requirements installed software components, 53
hardware, 46 license server port setting, 55
installing Unity Pro, 50 licensing software for service packs, 38
operating systems, 48 updating, 38
other software requirements, 50 license server port
service pack general installation informa- changes for service packs, 38
tion, 36 licensing software installation, 55
service pack hardware requirements, 35 licenses
service pack machine roles, 34 requirements when updating Process Ex-
service pack prerequisites, 34 pert, 71
service pack software requirements, 34 service pack license requirements, 34
service pack supervision software re- VM licensing examples, 27
quirements, 35 licensing
supervision software requirements, 50 considerations for virtual machines, 22
installing the Floating License Manager,

EIO0000001255 11/2017 159

Index

149
using configuration wizards, 88
N
networks
licensing software
network connection examples, 27
changes for service packs, 38
network connections of servers and sta-
license server port setting, 55
tions, 24
updating Floating License Manager, 38
troubleshooting client-server connec-
updating License Manager, 38
tions, 141
user account requirements, 49
log files
database migration log files, 81
service pack installation log files, 39
O
logs OFS
engineering client activity log files, 124 service pack OFS software requirements,
installation log files, 56 35
system server activity log files, 121 operating systems
operating system requirements, 48
Oracle VM VirtualBox
M third-party software components, 51
memory
memory allocated to the VM, 15
Migrate Database
P
system server console commands, 116 password
migrating password information and settings when
databases, 80 restoring databases, 118
databases to service packs, 42 troubleshooting virtual machine password
migrating databases to the current ver- issues, 139
sion, 80 passwords
migrating databases default simulator password, 60
32-bit migration process overview, 70 performance
migration process overview, 70 virtual machine installation recommenda-
migration tions, 15
database migration log files, 81 performance considerations
service pack database management, 37 client/server communication interrup-
modifying tions, 26
modifying service pack installation, 44 physical architectures
Process Expert, 128 description, 24
modifying the installation PLC Simulator
licensing considerations, 128 installing, 60
mounting databases ports
restoring, 118 client configuration wizard, 94
client VM communication ports, 94
server VM communication ports, 94
settings and configuration of communica-
tion ports, 93
system server port configuration, 93
troubleshooting communication ports,

160 EIO0000001255 11/2017

 Index

141 restoring
prerequisites databases, 118
service pack installation, 34
Process Expert
configuring the system server and clients, S
87 saving files
first-time installation, 64 sharing files with the VM, 96
general update information, 68 server
physical architecture examples, 27 configuring the system server, 93
physical architectures, 24 server address for clients, 94
removing, 132 service pack configuration information, 37
repairing the installation, 130 starting the service pack system server,
software architecture, 12 43
starting the system server, 121
system server activity logs, 121
R troubleshooting system server startup de-
removing lay, 138
before installing an earlier version of Pro- server configuration wizard
cess Expert, 133 installing DTMs with a response file, 151
Process Expert, 132 server extensions
removing a software component, 128 connecting a client to different system
removing applied hotfixes, 132 servers, 113
uninstalling service packs, 44 server port
repairing changes for service packs, 38
Process Expert, 130 licensing software installation, 55
repairing the service pack installation, 44 service pack
requirements installation information, 33, 33
installing Unity Pro, 50 installing service packs, 40
service pack general installation informa- [Link]
tion, 36 installing DTMs with a response file, 151
service pack hardware requirements, 35 shared folder
service pack machine roles, 34 sharing files with the VM, 96
service pack OFS software requirements, sharing files
35 sharing with the VM, 96
service pack software requirements, 34 simulator
service pack supervision software re- default simulator password, 60
quirements, 35 default STA file for simulator, 60
response files installing the PLC Simulator, 60
installing DTMs with a response file, 151 slots
restore for Participant services, 15
password information and settings when software
restoring databases, 118 installed software components, 53
Restore Database licensing software for service packs, 38
system server console commands, 116, licensing software installation, 55
116 service pack machine role requirements,

EIO0000001255 11/2017 161

Index

34
service pack software requirements, 34
T
templates
software requirements, 49
overview of installation scenarios, 52
third-party software for service packs, 39
templates supplied as export files, 73
updating licensing software, 38
third-party software
software architectures
changes for service packs, 39
description, 12
time zones
software requirements
changing the time zone of the virtual ma-
service pack OFS software requirements,
chine, 112
35
virtual machine time zone, 21
service pack supervision software re-
Tools menu
quirements, 35
system server console menu, 116
STA file
troubleshooting
default STA file for simulator, 60
client/server communication interrup-
starting
tions, 141
engineering clients, 124
communication ports, 141
service pack system server, 43
database inconsistencies, 139
system server, 121
installation issues, 136
troubleshooting system server, 138
system server startup delay, 138
supervision software
troubleshooting Cache not starting, 145
installing, 65
troubleshooting USB port issues, 142
service pack supervision software re-
unable to extract the VM file, 136
quirements, 35
virtual machine password issues, 139
updating supervision software, 70
virtual machine startup, 139
system locale
types
configuration wizard for virtual machines,
updated DFBs and DDTs supplied in the
96
release, 73
system server
configuring the system server, 93
console, 116
console menu, 116
U
service pack configuration information, 37 uninstalling
starting the service pack system server, modifying the installation, 128
43 Process Expert, 132
starting the system server, 121 uninstalling service packs, 44
system server activity logs, 121 uninstalling Process Expert
troubleshooting system server startup de- troubleshooting, 136
lay, 138 Unity Pro
system server configuration wizard compatibility with service pack, 35
activating virtual machines, 114 installation requirements, 50
hosting, 93 installing control Participant hotfixes, 112
installing and removing extensions, 105 unzipping
system server configuration wizards unzipping the installation package, 49
configuring virtual machines, 95 updating
DFBs supplied as XDB files, 73
Global Templates supplied as export files,

162 EIO0000001255 11/2017

 Index

73 issues, 139
third-party software components, 51 troubleshooting virtual machine startup,
updating a 32-bit system infrastructure, 139
69 unable to extract the VM file, 136
updating supervision software, 70 using configuration wizards, 88
updating Process Expert Virtualbox
general information, 68 installed software components, 53
installation procedure, 82 VirtualBox
licensing, 71 third-party software components, 51
migrating the database, 80 VM
USB changing the time zone of the virtual ma-
troubleshooting USB port issues, 142 chine, 112
user accounts default time zone, 21
installing Process Expert, 49 memory allocated to the VM, 15
using configuration wizards, 88 unable to extract the VM file, 136
user interface
user interface language, 36
UserExtensions folder W
installing and removing extensions, 105 Windows 10
.NET Framework requirements, 58
Windows 8.1
V .NET Framework requirements, 58
vdi file Windows Server 2012
verifying integrity with checksum, 136 .NET Framework requirements, 59
version wizards
client/server compatibility, 84 using configuration wizards, 88
installing an earlier version of Process Ex-
pert, 133
Process Expert component version, 84 X
updating third-party software compo- XDB files
nents, 51 updated types supplied in the release, 73
virtual machine
activating, 96, 114
changing the time zone of the virtual ma- Z
chine, 112 zip utility
client communication ports, 94 unzipping the installation package, 49
default time zone, 21
installation recommendations, 15
licensing considerations, 22
performance considerations, 15
replacing during installation, 56
server communication ports, 94
service pack configuration information, 37
sharing files with the VM, 96
troubleshooting virtual machine password

EIO0000001255 11/2017 163

Index

164 EIO0000001255 11/2017