Recipe Manager Plus Install Guide

Wonderware
Recipe Manager Plus

Installation Guide
6/20/14
All rights reserved. No part of this documentation shall be reproduced, stored in a retrieval system, or
transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise, without the
prior written permission of Invensys Systems, Inc. No copyright or patent liability is assumed with respect
to the use of the information contained herein. Although every precaution has been taken in the
preparation of this documentation, the publisher and the author assume no responsibility for errors or
omissions. Neither is any liability assumed for damages resulting from the use of the information
contained herein.
The information in this documentation is subject to change without notice and does not represent a
commitment on the part of Invensys Systems, Inc. The software described in this documentation is
furnished under a license or nondisclosure agreement. This software may be used or copied only in
accordance with the terms of these agreements.
© 2014 by Invensys Systems, Inc. All rights reserved.
Invensys Systems, Inc.

26561 Rancho Parkway South
Lake Forest, CA 92630 U.S.A.
(949) 727-3200
http://www.wonderware.com
For comments or suggestions about the product documentation, send an e-mail message to
ProductDocumentationComments@invensys.com.
All terms mentioned in this documentation that are known to be trademarks or service marks have been
appropriately capitalized. Invensys Systems, Inc. cannot attest to the accuracy of this information. Use of
a term in this documentation should not be regarded as affecting the validity of any trademark or service
mark.
Alarm Logger, ActiveFactory, ArchestrA, Avantis, DBDump, DBLoad, DT Analyst, Factelligence,
FactoryFocus, FactoryOffice, FactorySuite, FactorySuite A2, InBatch, InControl, IndustrialRAD,
IndustrialSQL Server, InTouch, MaintenanceSuite, MuniSuite, QI Analyst, SCADAlarm, SCADASuite,
SuiteLink, SuiteVoyager, WindowMaker, WindowViewer, Wonderware, Wonderware Factelligence, and
Wonderware Logger are trademarks of Invensys plc, its subsidiaries and affiliates. All other brands may
be trademarks of their respective owners.
3
Contents
Welcome .................................................... 5
Documentation Conventions ........................................................... 5
Technical Support ............................................................................ 6
Chapter 1 Introduction ................................................ 7

Recipe Manager Plus Architecture ................................................. 7
Installation Prerequisites ................................................................ 8
IIS and ASP.NET .......................................................................... 9
About Firewalls .............................................................................. 10
Chapter 2 Recipe Manager Plus Installation .................. 11

ArchestrA User Account ................................................................ 11
Installing Recipe Manager Plus .................................................... 12
Modifying the Recipe Manager Plus Installation ......................... 17
Repairing the Recipe Manager Plus Installation ......................... 18
Uninstalling Recipe Manager Plus ............................................... 19
Upgrading Previous Versions ........................................................ 19
Chapter 3 Recipe Manager Plus Configuration ............... 23

Starting the Configurator .............................................................. 23
Configuring the Core Server Components .................................... 25
Configuring Integration with Wonderware Application Server .. 27
Starting the Recipe Manager Plus Web Application .................... 27
Wonderware Recipe Manager Plus Installation Guide

4 Contents
Chapter 4 Configuring Server Components in

Standalone Mode ...................................... 29
Starting the Configure ArchestrA Services Utility ...................... 29
Creating a OPCUA Client Service Instance ................................. 31
Configuring the OPC UA Client Service ....................................... 32
Configuring the OPC UA Client Service Instance
Parameters .............................................................................. 33
Renaming the OPC UA Client Service Instance ....................... 37
Deleting the OPC UA Client Service Instance .......................... 37
Configuring the Namespace Aliases .......................................... 37
Modifying the Instance Parameters of
the OPC UA Client Service Configuration ............................ 40
Assigning the OPC UA Client Service to a Node ......................... 41
Deploying the OPC UA Client Service Instance .......................... 42
Exporting and Importing OPC UA Client Service
Configuration .............................................................................. 43
Exporting OPC UA Client Service Configuration ..................... 43
Importing OPC UA Client Service Configuration ..................... 44
Chapter 5 OPC UA Client Run Time.............................. 47

Item Syntax .................................................................................... 47
Syntax of OPC UA Items ............................................................ 47
Value, Timestamp, and Quality (VTQ) Data ................................ 50
Chapter 6 Managing Digital Certificates........................ 51

Generating a Self-Signed
OPC UA Compliant Certificate and Key Pair ........................... 52
Creating a Self-Signed
Using the Self-Signed
Appendix A SSL ......................................................... 59

Setting Up SSL ............................................................................... 59
Appendix B About OPC UA ........................................... 61

Understanding the OPC UA Standard ......................................... 61
About Classic OPC and OPC UA ................................................ 62
Comparing OPC UA with Classic OPC ...................................... 63
Understanding the OPC UA Connectivity ................................. 63

5
Welcome
The Wonderware Recipe Manager Plus Installation Guide describes

the installation and configuration options for Wonderware Recipe
Manager Plus components — Recipe Manager Plus Server, Recipe
Manager Plus Components for ArchestrA IDE, and Documentation. It
also explains how to modify, repair and uninstall the Recipe Manager
Plus software.
Documentation Conventions
This documentation uses the following conventions:
Convention Used for
Initial Capitals Paths and file names.

Bold Menus, commands, dialog box names,
and dialog box options.
Monospace Code samples and display text.

6  Welcome
Technical Support
Wonderware Technical Support offers a variety of support options to
answer any questions on Wonderware products and their
implementation.
Before you contact Technical Support, refer to the relevant section(s)
in this documentation for a possible solution to the problem. If you
need to contact technical support for help, have the following
information ready:
• The type and version of the operating system you are using.
• Details of how to recreate the problem.
• The exact wording of the error messages you saw.
• Any relevant output listing from the Log Viewer or any other
diagnostic applications.
• Details of what you did to try to solve the problem(s) and your
results.
• If known, the Wonderware Technical Support case number
assigned to your problem, if this is an ongoing problem.

7
Chapter 1
Introduction
This section describes the Recipe Manager Plus features,

prerequisites, and requirements for installing Recipe Manager Plus
software.
Recipe Manager Plus Architecture

Recipe Manager Plus can be implemented in one of two modes:
standalone or integrated with Wonderware Application Server.
Standalone mode means that you use the Recipe Manager Plus web
client to configure and run all aspects of your application, including
mapping IO and running the execution.
If you are integrating Recipe Manager Plus with Wonderware
Application Server, you use ArchestrA software for IO reference
mapping and execution.
Recipe Manager Plus is made up of the following components:
• Server database. The configuration of your recipe model is stored
in a SQL Server database.
• Web client. You create and work with your recipe model using the
web client, which is supported by different browsers. The web
client is hosted on the same server as the database.

8  Chapter 1 Introduction
• Input/Outputs. You can use an OPC UA Server or Wonderware

Application Server to provide IO references and execution for
recipes.
• If you are using an OPC UA Server, you must configure the
OPC UA Client service on the Recipe Manager Plus server to
communicate with the OPC UA Server.
• If you will be using Wonderware Application Server, you must
install the components for the ArchestrA IDE on the
Wonderware Application Server node and then configure the
IO reference mapping using the Recipe Manager Plus
ApplicationObject within the IDE.
• Execution service. The execution service is only used by Recipe
Manager Plus in standalone mode.
You use the post-install Configurator to configure the server database
and web application. You can configure the OPC UA Client service
using the Configure ArchestrA Services application. You do not need to
configure the execution service.
For information about how to set up integration with Application
Server, see the Recipe Manager Plus User Guide.
Installation Prerequisites
The Recipe Manager Plus installation program analyzes the software
installed on your computer and lists any software that is required but
not currently installed. You do not need to exit the Recipe Manager
Plus installation program to install the prerequisite software.
Installing the Recipe Manager Plus product is a three-step process:
1 Installing and configuring prerequisite software, such as the
operating system components, Microsoft SQL components,
Internet Information Services (IIS), and so on.
2 Installing the Recipe Manager Plus product files.
3 Configuring the Recipe Manager Plus product so that it is ready for
use.
For details on hardware requirements and the specific versions of
required and supported software prerequisites, see the latest
Wonderware Recipe Manager Plus Readme.

Installation Prerequisites9
IIS and ASP.NET

The Recipe Manager Plus web application requires IIS and ASP.NET.
The Windows versions supported by Recipe Manager Plus include IIS,
but IIS is not enabled in the default installation. It is enabled as part
of the Recipe Manager Plus installation and configured automatically.
Should you have to manually configure IIS and ASP.NET, below are
the subcomponents you must select for Internet Information Services
(IIS), depending on the version of Windows you are using.
• Under IIS6 Management/Management Tools select:
• IIS 6 WMI Compatibility
• IIS 6 Metabase Compatibility
• IIS 6 Scripting Tools
• IIS 6 Management Console
• IIS Management Console
• Under Application Development Features select:
• .NET Extensibility
• ASP.NET
• ISAPI Extensions
• ISAPI Filters
• For IIS8.0
• ASP.NET 3.5
• .NET Extensibility 3.5
• ASP.NET 4.5
• .NET Extensibility 4.5
• WebSocket Protocol
• Under Common HTTP Features select:
• Default Document
• Directory Browsing
• HTTP Errors
• HTTP Redirection
• Static Content
• Under Security select:
• Request Filtering
• Windows Authentication

10  Chapter 1 Introduction
About Firewalls
If you have a corporate firewall, hardened device (appliance), or
software application on a dedicated hardened platform, you need not
implement a personal firewall on each computer.
Individual Recipe Manager Plus features have their own firewall
requirements and procedures.

11
Chapter 2
Recipe Manager Plus

Installation
This section describes how to install, modify, repair, uninstall and

upgrade the Recipe Manager Plus product.
ArchestrA User Account

The ArchestrA user account is used by the Recipe Manager Plus for:
• Execution services
• Importing the equipment into the ArchestrA IDE
The user you specify for this account must also be a user in Recipe
Manager Plus who can:
• View equipment
• Control execution
• Access all equipments
You set up execution and import privileges using the Recipe Manager
Plus web application.
You must specify the same user account each time you install the
Recipe Manager Plus features on computers.
WARNING! The ArchestrA user account is a Windows operating

system account located on the local computer or on a domain.
Do not delete this account with operating system account
management tools.

12  Chapter 2 Recipe Manager Plus Installation
If no other ArchestrA-enabled software is installed on the computer,

you are prompted to create a new ArchestrA user account or specify an
existing user account during the Recipe Manager Plus installation. If
you select an existing user account, it should meet the following
requirements:
• User account with a permanent password that does not expire.
• User account in which the password cannot be changed.
After you install the Recipe Manager Plus software, you can use the
ArchestrA Change Network Account utility to change or recreate the
ArchestrA user account. This utility is located in the Common folder
after you install the Recipe Manager Plus software. You must have
Administrator privileges on the computer to make changes with this
utility. For more information, see the Change Network Account utility
documentation.
Installing Recipe Manager Plus

You must be logged on to the computer as a user with administrative
privileges to install the Recipe Manager Plus software.
When UAC is enabled, a security prompt is shown when you start the
installation. If necessary, enter the administrative user credentials to
allow the installer to proceed.
To install Recipe Manager Plus features

1 Insert the Recipe Manager Plus CD into the CD-ROM drive. The
installation program runs automatically. If your network or
company security policy does not permit autorun, browse the root
directory of the CD and run setup.exe. The Recipe Manager Plus
Installation Wizard starts.
The installation program detects and installs the initial system
requirements. For more information on specific system
requirements, see the Wonderware Recipe Manager Plus Readme.

Installing Recipe Manager Plus13
2 Install the system-specific prerequisites. If your computer does not

meet the initial system prerequisites, the Prerequisites dialog box
appears.
3 Select the Show All Prerequisites check box to view all the
prerequisites. Double-click any item to see more information. Click
Install Prerequisites. The program installs the general system
prerequisites. The License Agreement dialog box appears.
4 Read the license agreement. You can print a copy of the license
agreement for your records using the Print icon.

5 Click I accept the license agreement and then click Next. The
Wonderware Recipe Manager Plus Installation dialog box
appears.
6 Select the check boxes to indicate which features you want to

install, and then click Next.
You can click Browse to change the destination folder where the
program will be installed.
Note: You can select multiple features and all the selected features
will be installed together if all the prerequisites are met.
If an ArchestrA user account is required, the user account dialog

box appears.

Installing Recipe Manager Plus15
7 Specify an ArchestrA user account. You can specify an existing

user account, or create a new ArchestrA user account if no other
ArchestrA-enabled software is installed on the computer.
For information on user account requirements, see "ArchestrA
User Account" on page 11.
If you create a new account, do the following:
a Type your User Name and Password.
b Select the Create Local Account check box, if not already
selected.
By default, this check box is selected and the Domain/Local
Machine box displays your computer name.
c Specify a different domain/local machine name, if necessary. If

you clear the check box, the Domain/Local Machine box
displays the default domain name. You can then modify it.
a Type the User Name and Password for the existing account.
b Clear the Create Local Account check box.
8 Click Next to complete the User Account setup.
9 When you select a Recipe Manager Plus feature to install, a list of
prerequisites that are required for installing the see lc ted Recipe
Manager Plus features is shown.
Any prerequisites you are missing will be identified as not met.

10 Click Install Prerequisites. The program installs the

prerequisites. When all prerequisites are installed, click Next. The
Ready to Install dialog box appears.
11 Review your installation options and then click Install. The

Updating the system dialog box appears which takes a couple of
minutes to copy the files on your computer.
After the files are copied, the complete installation dialog box
appears.
12 If the installed features require configuration, click Configure. For

more information on configuring Recipe Manager Plus, see
Chapter 3, "Recipe Manager Plus Configuration".

Modifying the Recipe Manager Plus Installation17
Modifying the Recipe Manager Plus Installation

You can add new Recipe Manager Plus features or remove the existing
Recipe Manager Plus features.
Note: You must have the installation CD inserted in the CD-ROM drive
before you modify a program.
To modify a Recipe Manager Plus installation

1 Click the Add or Remove Programs option in Windows Control
Panel. (In some operating systems, this is called Uninstall or
Change a Program.) The list of software installed on your
computer appears.
2 Double-click the Wonderware Recipe Manager Plus icon. The
Modify Repair or Remove Installation dialog box appears.
Note: The name of the Uninstall/Change button varies depending on

the Windows operating system installed on your computer.
3 Click Modify, and then click Next. The list of Recipe Manager Plus
features installed on your computer appears.
4 Select or clear the features that you want to add or remove, and
then click Next. The verify change dialog box appears.
5 Click Modify. The selected features are added or removed and the
complete modification dialog box appears.
6 Click Finish. The modification is complete.

Repairing the Recipe Manager Plus Installation

You can repair missing or corrupt files, the registry keys or shortcuts.
You can also reset the registry key to the default value.
Note: You must insert the installer CD in the CD-ROM drive before you
repair a program.
To repair an installation
computer appears.
2 Double-click the Wonderware Recipe Manager icon. The Modify
Repair or Remove Installation dialog box appears.

3 Click Repair, and then click Next. The Confirm Repair dialog box
appears.
4 Click Repair. The complete repair dialog box appears.
5 Click Finish. The installed Recipe Manager software is repaired.

Uninstalling Recipe Manager Plus19
Uninstalling Recipe Manager Plus

You can uninstall the Recipe Manager Plus product that is installed on
your computer.
To uninstall a Recipe Manager installation

computer appears.
2 Double-click the Wonderware Recipe Manager icon. The Modify
Repair or Remove Installation dialog box appears.

3 Click Remove, and then click Next. The Confirm Uninstall dialog
box appears.
4 Click Uninstall. The complete uninstall dialog box appears.
5 Click Finish. The uninstall process is complete.
Upgrading Previous Versions

When you install Recipe Manager Plus 1.5 on a system that already
has Recipe Manager Plus installed, the installation procedure
automatically detects the earlier version and upgrades it to Recipe
Manager Plus 1.5.
To upgrade a Recipe Manager Plus installation:

1 Insert the Recipe Manager Plus CD into the CD-ROM drive and
run setup.exe. The Recipe Manager Plus Installation Wizard
starts and then the License Agreement dialog box appears.

2 Read the license agreement, if you agree with the terms provided
and then click I accept the License Agreement.
3 Click Next. The Wonderware Recipe Manager Plus Installation

dialog box appears. The features that are installed in the previous
version of Recipe Manager Plus are automatically selected for
upgrade.
Note: You cannot change the feature selection during the upgrade.
4 Click Next. If your computer does not meet the prerequisites for
the Recipe Manager Plus features to be upgraded, the
Prerequisites dialog box appears.

Upgrading Previous Versions21
5 Click Install Prerequisites. When all the prerequisites are

installed, click Next. The Ready to Update dialog box appears.
6 Click Upgrade. The files from the previous version of Recipe

Manager Plus are uninstalled and the new files are copied.

7 After the upgrade process is complete, the Complete Installation

dialog box appears.
8 If the upgraded features require configuration, click Configure.

For more information on configuring Recipe Manager Plus, see
Chapter 3, "Recipe Manager Plus Configuration".
Note: After the upgrade process and before starting the latest version
of Recipe Manager Plus, make sure to clear the cache so that new
updates in the user interface is shown without any issues.

23
Chapter 3
Recipe Manager Plus

Configuration
You can configure Recipe Manager Plus features for both standalone
mode and integrated mode using the Configurator. You must configure
the features after you have installed them. Based on the features you
have installed, the Configurator creates a database, configures the
services, and sets other system settings required by the Wonderware
Recipe Manager Plus software.
Starting the Configurator

You can start the Configurator at the end of the Recipe Manager Plus
installation program. If the product is already installed, you can start
the Configurator from the Windows Start menu.

24  Chapter 3 Recipe Manager Plus Configuration
To start the Configurator

1 On the Start menu on the Windows Taskbar, point to Programs,
Wonderware, then to Common, and then select Configurator. The
Configurator main window appears.
2 In the left pane, expand Recipe Manager Plus, if not already

expanded. The list of Recipe Manager Plus features that you have
installed appear.

Configuring the Core Server Components25
When you click a feature name, the configuration options appear in

the right pane. If you click Refresh or select a Recipe Manager
Plus feature in the Configurator, after you have configured the
feature, the Configurator validates the settings. A warning
message appears if the settings are not valid and the state of the
selected feature changes to Warning.
You can view the status messages and error messages in the
Configuration Messages area, in the bottom right of the dialog
box. For more information about a message, including possible
actions you need to take, double-click the message text in the
window.
3 Click on each installed feature and configure the options.
• For more information on configuring the Server Components in
standalone mode, see "Configuring Server Components in
Standalone Mode" on page 29.
• For more information on configuring the Server Components
integrated with Wonderware Application Server, see
"Configuring Integration with Wonderware Application
Server" on page 27.
4 When you are done, click Close.
Configuring the Core Server Components

You can specify to run Recipe Manager Plus in standalone mode or
integrated with Wonderware Application Server.
Note: Make sure that the current logged on OS user has 'sysadmin'
privileges in SQL Server before configuring the Recipe Manager Plus
Core Server Components in the Standalone mode.
To configure the server components

1 Open the Configurator.

2 Click Core Server Components in the left pane. The configuration

options appear in the right pane.
3 In the SQL Administrator Login area, specify the account that will
be used to log on to the SQL Server and create the Recipe Manager
Plus model database.
Note: It is recommended to use Windows Authentication for accessing

the database as a best practice.
4 In the Application Pool Identity area, specify the user account

that the web application will use to access the recipe model
database. This account should not have a password that expires.
The Application Pool identity account should have the least
privileges possible, but needs enough privileges to access Active
Directory to look up users and groups (if Active Directory is being
used). If you are using Active Directory, then this user will most
likely need to be a domain user. It is also a best practice to not add
this user in the Recipe Manager Plus user configuration.
5 In the Execution mode area, specify which application should be
used for IO mapping and execution.
• Click Standalone for Recipe Manager Plus to use the OPC UA
Client service. You will then need to configure the OPC UA
Client service. For more information, refer to "Configuring
Server Components in Standalone Mode" on page 29.
• Click Integrated with Wonderware Application Server for
Recipe Manager Plus to use Wonderware Application Server.
For more information, see the Recipe Manager Plus User Guide
or Help.
6 In the SSL Configuration area, select Use secure connection
(HTTPS) to have HTTPS access to the web application. You must
manually set up SSL in IIS. For more information, see Appendix A,
"SSL."

Configuring Integration with Wonderware Application Server27
7 Click Configure.
Configuring Integration with Wonderware

Application Server
For information on setting up Wonderware Recipe Manager Plus
integration with Wonderware Application Server, see “Using Recipe
Manager Plus with Wonderware Application Server” in the Recipe
Manager Plus User Guide or Help.
Starting the Recipe Manager Plus Web

Application
Recipe Manager Plus is accessed using the Start menu shortcut
created during installation or by typing the following URL:
http://<hostname>/RecipeManagerPlus
If you are using SSL, then type:
https://<hostname>/RecipeManagerPlus


Starting the Configure ArchestrA Services Utility29
Chapter 4
Configuring Server
Components in Standalone
Mode
This chapter provides information about configuring and deploying the

OPC UA Client using the standalone application. A standalone
application “Configuring ArchestrA Services” is installed when you
configure the core components in the Standalone mode.
Starting the Configure ArchestrA Services

Utility
You can start the Configure ArchestrA Services Utility from the
Windows Start menu.

30  Chapter 4 Configuring Server Components in Standalone Mode
To start the ArchestrA Services Utility

1 On the Start menu on the Windows Taskbar, point to Programs,
Wonderware, then to Recipe Manager Plus, and then click
Configure ArchestrA Services. The Configure ArchestrA Services
main window appears.
2 In the left pane, expand ASB service repository, if not already

expanded. The default OPCUA Client service appears.

Creating a OPCUA Client Service Instance31
Creating a OPCUA Client Service Instance

You must create an instance of the OPC UA Client and then configure
the OPC UA Client.
To create an instance of the OPC UA Client

1 Expand the ASB tree structure o view the list of installed services
and their instances.

2 Right-click ASBOPCUAClientService, and then click Create. You

can also click ASBOPCUAClientService, and then press CTRL+N.
The new instance appears in the tree structure.
Configuring the OPC UA Client Service

After you have created the instance of the OPC UA Client, you can
configure its parameters in the General tab.

Configuring the OPC UA Client Service33
Configuring the OPC UA Client Service Instance

Parameters
To configure or modify the OPC UA Client instance
parameters
1 Right-click the OPC UA Client configuration instance name, and
click Check-out.
Note: Click the Refresh button to view configuration information

previously stored in the database.

2 Configure or modify the instance parameters in the General tab as

follows:
a In Scope Name box, type the name of the OPC UA Server. The
maximum length of the scope name is 32 characters. You can
use alphanumeric characters, however, the initial character
must be an alphabet. The only valid special character is the
underscore (_). This field is case insensitive. If you enter
invalid characters, the background of the Scope Name box is
highlighted in red as shown below:
b In the OPC UA Server Details area, do the following:

• In the OPC UA Server Node box, type the computer name
(Node name) or the IP address of the OPC UA Server.
The endpoint URL(s) of that Node or Server is
automatically displayed in the Endpoint URL box. If you do
not have the Node name information, you can manually
enter the OPC UA Server endpoint.
Note: You can also click the Browse button to browse, and then select
the computer name or IP address of the OPC UA Server.
• In the Endpoint URL box, type the OPC UA Server

endpoint, if you have not already entered the details of the
OPC UA Server in the Discovery Server Node box.
You can also select an endpoint URL from the Endpoint
URL drop-down, if the Node selected in the OPC UA Node
box has more than one endpoint URLs.
Note: Click the Refresh button to refresh the endpoint list, if you want
to view the list of the latest sever endpoint URIs.
• In the Application URI box, type the name of the OPC UA

Server. This is an optional field and is required only if you
have not provided the endpoint URL.

• Select the Security Message Mode. This field is set to None

by default.The description of each mode is given in the
below table:
Option Description
None Indicates that no security is applied.
Sign and Encrypt Indicates that all messages are signed and
encrypted.
Sign Indicates that all messages are signed but not

encrypted.
Note: If the Security Message Mode option is not None, the OPC UA
Server’s digital certificate must be trusted and be made available on the UA
Client computer. For more information on digital certificates, see "Creating a
Self-Signed OPC UA Compliant Certificate and Key Pair" on page 69.
• Select the Security Policy. This field is set to None by

default. The description of each mode is given in the below
table:
Option Description
None Indicates that no security is applied.
Basic 256 Indicates that Basic 256 security policy is

applied.
Basic128Rsa15 Indicates that Basic128Rsa15 security policy is

applied.
Note: If the Security Policy option is not None, the OPC UA Server’s
digital certificate must be trusted and be made available on the UA Client
computer.

c In the User Credentials area, do the following:

• Select the Anonymous User check box to allow login
without the user credentials. This field is selected by
default.
Or,
• Clear the Anonymous User check box, type a user name
and a password in the User Name box and the Password
box respectively.
• User Credentials: You can create a secure connection with the

OPC UA Server depending on how the server accepts the
connection.
For example, if an OPC UA Client wants to connect to an OPC
UA Server that does not support anonymous connections, the
OPC UA client must provide a valid User Name and Password.
d In the Service Details area, under the Port Configuration
area, do the following:
• Select the Auto-assign port numbers check box. When the
service is deployed, the port numbers are auto selected for
the IData and the IBrowse endpoint configuration.
By default, the Auto-assign port numbers check box is
selected; the IData Port box and the IBrowse Port box are
disabled.
Or,
• Clear the Auto-assign port numbers check box, and then
type port numbers of the IData and IBrowse service
providers in IData Port box and IBrowse Port box
respectively.

• Auto-assigning port numbers: You can automatically

assign port numbers to the IData and IBrowse service
providers, whenever you create an OPC UA Client
instance. The ArchestrA framework identifies the ports
that are not used by other services, and then assigns those
ports to the OPC UA Client. These ports are in the range
10000 to 15000.
3 Right-click the instance, and then click Save And Check-in.
Renaming the OPC UA Client Service Instance

You can rename an instance of the OPC UA Client Service.
To rename the OPC UA Client Service instance

1 Right-click the configuration instance that you want to rename
and then click Rename.
2 Specify the new name and then press Enter.
Deleting the OPC UA Client Service Instance

You can delete an instance of the OPC UA Client Service.
To delete the OPC UA Client Service instance

1 Right-click the configuration instance that you want to delete and
then click Delete. A confirmation message appears.
2 Click Yes.
Configuring the Namespace Aliases

The OPC UA Namespaces are defined and exposed by the OPC UA
Servers. Each namespace is identified by an ID. For more information,
see "Item Syntax" on page 47. You can define an alias name for a
namespace, based on the following:
• The alias name must be defined and exposed by the OPC UA
Servers.
• The alias name must be identified with a Namespace ID data
structure.
• The alias name must be in accordance with the ArchestrA naming
constraint.
• The alias name must be in string format, such that it works well in
the ArchestrA IData namespace.
• There is at most one alias for each namespace.

• The same alias name is not given to two OPC UA Clients.

• The alias name must not conflict with any other namespace
display name.
The OPC UA Namespace tab displays the Namespace alias table for
the Namespace URI’s present in the OPC UA Server, that the UA
Client connects to.
If you have configured the endpoint URL in the General tab, and then
switch to the OPC UA Namespace tab, one of the following happens:
• If the server URL or Application URL is available, the Namespaces
are retrieved from the server and displayed in the table.
• If the server URL is unavailable or invalid, an empty Namespace
alias table is displayed.
When the OPC UA Server is running, if you want to view the
Namespace list in the Namespace alias table, you must checkout the
UA Client service instance and then click the Refresh button.
Tip: You can resize the rows in the Namespace alias table.

The OPC UA Namespace tab displays information retrieved from the

OPC UA Server, as shown below:
Column Name Description
Index Displays the Namespace index for the Namespace URI present in the
OPC UA Server. The default Namespace is appended with * after the
Index.
The items configured in the default Namespace need not be subscribed
in the syntax using the alias or the Namespace name.
Alias Displays the alias name for the Namespace URI available in the OPC
UA Server.
You can change this name during configuration. The Alias box cannot be
blank. You can use the "_" and “#” special characters in the alias name.
You cannot create duplicate alias names.
Node ID Type Displays the Node ID type of the Namespace in the OPC UA Server.
Node Id type can be of String, or Integer data type. This information is
obtained from the OPC UA Server and cannot be edited. For more
information on overriding the Node Id, see "Editing the Namespace Alias
Table" on page 39.
Namespace URI Displays the Namespace URI imported from the OPC UA Server.
This information cannot be edited.
Editing the Namespace Alias Table

You can use the Context menu in the Namespace Alias table to do the
following:
• Edit the default namespace,
• Edit the alias names, and
• Override the Node ID type
To edit the Namespace

1 Right-click on Namespace URI you want to set as default, and
then select Set as Default Namespace. The Index is appended
with a * to indicate the default Namespace URI.
2 In the Alias box of the selected Namespace, type an alias name for
the Namespace URI.

3 Right-click on Node Id Type you want to edit, and then select

Override Node ID type as String or Override Node Id type as
Integer. The data type of that Node ID is changed accordingly.
4 Right-click the instance, and then click Save And Check-in.
Modifying the Instance Parameters of

the OPC UA Client Service Configuration
After you have created the instance of the OPC UA Client, you can
configure modify its parameters in the General tab. For information on
modifying the UA Client service instance parameters, see "Configuring
the OPC UA Client Service" on page 32. For information on modifying
the Namespace alias table, see "Editing the Namespace Alias Table"
on page 39.

Assigning the OPC UA Client Service to a Node41
Assigning the OPC UA Client Service to a Node

You must assign a node to the OPC UA Client service configuration
instance before deploying it.
Note: You can assign a OPC UA Client Service to local node only.
To assign the OPC UA Client Service Instance

1 Select the configuration instance that you want to assign. The
available node appear in the Assignments area on the right pane.
2 In the Assignments area, select the node you want to assign to the
configuration instance, and then click Update. A message appears
in the status bar, indicating whether the node is assigned or not.
Note: The Update button is enabled only when you select a node. You
cannot delete a node that is already assigned to a service instance. To
delete such a node, you must first un assign the node from the service
instance.

Deploying the OPC UA Client Service Instance

After configuring the OPC UA Client service instance, you can deploy
it.
To deploy the OPC UA Client Service instance

1 Select the configuration instance that you want to deploy. The
configured instance parameters and the available nodes appear on
the right pane.
2 Assign the OPC UA Client service to a node. For more information,
see "Assigning the OPC UA Client Service to a Node" on page 41.
3 On the left pane, right-click the instance, and then click Deploy. A
message appears in the status bar, indicating whether the
configuration instance has been successfully deployed or not. If
deployment is unsuccessful, you can refer to the Invensys logger.
Note: You cannot assign a OPC UA Client service instance on a remote

node, and hence, deploying the instance on the remote node is not
possible.

Exporting and Importing OPC UA Client Service Configuration43
Exporting and Importing OPC UA Client Service

Configuration
You can minimize the configuration errors when creating a duplicate
OPC UA Client service configuration, by importing the deployable
OPC UA Client service configuration. You can save the configuration
as a backup file and can use it, for example, if the ASB Repository
database is under maintenance. The configuration file is a .aaSCfg
file, which you can import from one Repository to the other. The
exported configuration file contains information of the OPC UA Client
instance parameters, the Namespace aliases, except the Node details.
Exporting OPC UA Client Service Configuration

You can export the OPC UA Client service configuration to another
Respository.
To export OPC UA Client Services

1 Right-click on a configured OPC UA Client service instance, and
then click Export.

2 In the Select a Service Configuration File dialog box, name the file
and then save it with .aaSCfg extension.
Importing OPC UA Client Service Configuration

You can import the OPC UA Client Service configuration to another
Repository.
To import OPC UA Client Services

1 Right-click on the Repository menu, and then click Import.

Exporting and Importing OPC UA Client Service Configuration45
2 In the Select a Service Configuration File dialog box, browse the

.aaSCfg file.
3 Click Open. A new OPC UA Client service instance is created with

the imported parameters.


47
Chapter 5
OPC UA Client Run Time
Item Syntax
Item syntax is the standard format, by which you can use the OPC UA
items or diagnostic items, to obtain information from the OPC UA
Server.
Syntax of OPC UA Items

This section describes various options for using the UA Client syntax.
For more information on OPC UA, see The Archestra OPC UA Client
Service Guide.
The IData services are deployable services that implement the IData
interface. These services interact with a variety of data sources, while
exposing the data sources within the framework of an IData standard
protocol. So, in order to provide a regular experience, a common item
name syntax was agreed upon across all the IData providers.

48  Chapter 5 OPC UA Client Run Time
You can use the UA Client syntax options defined in the following
table, based on your requirement:
Scenario Syntax
To access the data <domain>:UAItemReference

for items in the
Or
default Namespace
<domain>://UAItemReference
where:
• domain is the Scope Name defined in the UA Client Editor. This is
case insensitive.
• UAItemReference is the identifier of the item (the complete path of
the OPCUA Server item, followed by the NodeId) in the OPC UA
Server. UAItemReference is resolved by the OPC UA Server, and the
case is preserved. This is case sensitive.
For example: Topserver:PLCport.PlCobject.N40:0

Item Syntax49
Scenario Syntax
To access the data <domain>:UANS(UANamespaceURI)UAItemRef(UAItemReference)

for items with the
where:
complete
Namespace URI • domain is the Scope Name defined in the UA Client Editor. This is
case insensitive.
• UANS stands for UANamespace, and is a keyword.
• UANamespaceURI is the true namespace URI in OPC UA Server.
This is case sensitive.
• UAItemRef stands for UAItemReference, and is a keyword.
the OPCUA Server item, follwed by the NodeId) in the OPC UA
For example:
Sampleserver:UANS(http://test.org/UA/Data/)UAItemRef(10847)
To access the data <domain>:/UANamespaceAlias/UAItemReference

for items with the
Or
Namespace alias
<domain>:UANS(UANameSpaceAlias)UAItemRef(UAItemReference)
where:
• domain is the Scope Name defined in the UA Client Editor. This is
case insensitive.
• UANS stands for UANamespace, and is a keyword.
• UANamespaceAlias is the Namespace alias name used to identify
the namespace in the OPC UA Server. This is configured on the UA
Client Editor. UANameSpaceAlias is replaced by the true
namespace URI in UA Client service, before it is sent to the server.
This is case insensitive. For more information on defining the
Namespace Aliases, see "Configuring the Namespace Aliases" on
page 37.
• UAItemRef stands for UAItemReference, and is a keyword.
the OPCUA Server item, followed by the NodeId) in the OPC UA
For example: Sampleserver:UANS(Data)UAItemRef(10847)

50  Chapter 5 OPC UA Client Run Time
Value, Timestamp, and Quality (VTQ) Data

Each data point, that the UA Client returns, carries the VTQ data to
the ArchestrA Service Bus (ASB) client.
The Value, Timestamp, and Quality data is based on the following:
• Value
• Data value depends on the item type and is coerced to the
appropriate ArchestrA data type.
• Timestamp
• Device timestamp in UTC is forwarded to the ASB client.
• Server timestamp in UTC is ignored. If the Device timestamp
is not available, the Server timestamp is forwarded to the ASB
client.
• The UA Client stamps the data if both Device and Server
timestamps are not available.
• Quality
• Based on OPC UA Specification Part 4. of the Unified
Architecture Specifications, Quality is termed as Status Code,
which is a numerical value used to report the outcome of an
operation performed by an OPC UA Server. The quality is
forwarded as is to the other ASB clients.
• Quality generated by the UA Client due to connection failure
has a value of 0x80050000 (BadCommunicationError).
• The StatusCode is a 32-bit unsigned integer. The top 16 bits
represent the numeric value of the code that are used for
detecting specific errors or conditions. The bottom 16 bits are
bit flags that contain additional information but do not affect
the meaning of the StatusCode.
OPC UA Servers return good/success StatusCodes if the operation is
completed normally and the result is always valid. Whereas, different
StatusCode values are used to provide the Client with additional
information. OPC UA Servers use uncertain/warning Status Codes if
they could not complete the operation in the manner requested by the
Client, however, the operation did not fail entirely.

51
Chapter 6
Managing Digital Certificates
You can generate and use a self-signed OPC UA compliant digital

certificate and a key pair. This digitial certificate can be associated to
the UA Client service for exchange data with any OPC UA compliant
server.
The UA Configuration utility is used for illustration purpose in this
chapter. You can also use other means to generate and manage the
digital certificate, if you are familiar with the OPC UA standard and
digital certificate management. A self-signed digital certificate is used
in this example.
Note: In a secured environment where the digital certificate is

required to be signed by a Certificate Authority, please consult your IT
department for the procedure.

52  Chapter 6 Managing Digital Certificates
Generating a Self-Signed
OPC UA Compliant Certificate and Key Pair
To install self-signed OPC UA compliant certificate/key pair
1 Download “OPC UA SDK 1.01 Test Applications Setup [331.0
Stable]” from OPC UA Foundation.
You can download the package from the OPC UA Foundation web
site, at: http://www.opcfoundation.org/
Note: You may need to register for an account to download the

package.

Generating a Self-Signed OPC UA Compliant Certificate and Key Pair53
2 Install the setup, as given below:

a Unzip the zip file and double-click the run setup.exe file. The
Open File - Security Warning dialog box appears.
b Click Run. The License Agreement dialog box appears.
c Read the License Agreement, and then click I Agree to

continue. The Select Installation Folder dialog box appears.

d Accept the default settings and continue. The installation

process is complete, and the Installation Complete dialog box
appears.
3 Click Close to exit.

Creating a Self-Signed OPC UA Compliant Certificate and Key Pair55
Creating a Self-Signed
To create self-signed OPC UA compliant certificate/key pair
1 Start the UA Configuration Utility by clicking the Start button on
the Windows task bar and pointing to Programs. Point to the OPC
Foundation folder that contains the UA Configuration Utility, click
UA, and then click on UA Configuration Tool.
2 Click the Manage Application tab, and then click Create

Application Certificate. The Create Certificate dialog box appears.
Note: You can use the default server in Application To Manage box.
3 In Create Certificate dialog box, do the following:

a Store Type: From the Store Type drop-down list, select
Directory if your UA Client is running on the local computer.
b Store Path: It is recommended to create a temporary directory

to store and copy the certificate and the private key. For
example, C:\Tmp\TestUACert
c CA Key File: This field is optional if you are creating a
self-signed certificate.
d CA Password: This field is optional, if you are creating a
self-signed certificate.

e Application Name: This field contains the name of your UA

Client service. Enter ASB OPC UA Client Service that matches
the name used in Subject Name and Application URI.
f Application URI: Select the Application URI box, and enter the
application URI in the below format:
urn:localhost:ASB OPC UA Client Service
g Subject Name: Select the Subject Name box and enter the
subject name in the below format:
CN=ASB OPC UA Client Service
h Domains: Select the Domains box and enter “localhost” in the
Domains box.
i Key Format: Select PFX from the drop-down list.
Important: Items f, g, and h need to be compliant with the OPC UA

standard.

Creating a Self-Signed OPC UA Compliant Certificate and Key Pair57
4 Click OK. The certificate and the private key files are generated
under “certs” and “private” subdirectories in the
C:\Tmp\TestUACert directory.
Note: To rename the certificate file, and the private key files, do the
following:
In C:\Tmp\TestUACert\certs directory, rename the certificate file as
aaUAClient.der.
In C:\Tmp\TestUACert\private directory, rename the private key file as
aaUAClient.pfx.

Using the Self-Signed

To use the self-signed OPC UA Compliant Certificate and
Key Pair
1 Install the UA Client on every computer on which you want to
deploy the UA Client service instance.
2 Create the UA Client service configuration.
3 Copy the certificate file aaUAClient.der from
C:\Tmp\TestUACert\certs directory into the path
%CommonApplicationData%\ArchestrA\CertificateStores\OPCU
AClient\certs, on every computer on which you want to deploy the
UA Client service instance.
By doing this, you have replaced the file with same name in that
directory.
Note: The path to store program data is %CommonApplicationData%.

By default, this location is C:\ProgramData\.
4 Copy the private key file aaUAClient.pfx from

C:\Tmp\TestUACert\private directory into the path
%CommonApplicationData%\
ArchestrA\CertificateStores\OPCUAClient \private, on every
computer on which you want to deploy the UA Client service
instance.
By doing this, you have replaced the file with the same name in
that directory
Note: The path to store program data is %CommonApplicationData%.

By default this location is C:\ProgramData\.
5 On the computer where the targeted OPC UA Server may be

running, copy the certificate file aaUAClient.der from
C:\Tmp\TestUACert\certs directory into the directory where you
want to add the trusted cert for the OPC UA Server.
6 Deploy the UA Client service instance to the node.

59
Appendix A
SSL
If you want to secure the communication between your Recipe

Manager Plus server and client, you can set up SSL. Using SSL keeps
sensitive formula data hidden from potential attackers. More
information is available in Microsoft IIS documentation.
SSL itself is not set up automatically by Recipe Manager Plus; you
must set it up manually. After you have completed your setup, support
for https:// is available.
Setting Up SSL
Important: The steps below describe the SSL setup with a
self-signed certificate. As a best practice, we recommend you obtain a
certificate from a Certificate Authority to avoid warning message when
accessing Recipe Manager Plus.
To set up SSL
1 If you have not done so already, select the SSL option in the
Configurator and the Import Utility in the IDE.
2 Open inetmgr.exe.
3 Select the root node that specifies the machine name.
4 From the IIS section, double click Server Certificates.
5 From the Actions pane, click the Create Self-Signed Certificate…
link (self-signed certificate are for testing purpose).
6 On Create Self-Signed Certificate window, enter a name for the
certificate (e.g., RecipeManagerPlus).

60  Appendix A SSL
7 Select WebHosting from Select a certificate store for the new

certificate drop-down.
Note: If you are working with IIS 7.5, you need not perform step 7.
8 Click the OK button.

9 A RecipeManagerPlus certificate should be displayed in the
Server Certificates grid. The Issued To and Issued By fields
should display the current machine name along with the domain
name.
10 Select Default Web Site from the Connections pane at the left
side.
11 Click the Bindings… link from the Actions pane at the right side.
12 In the Site Bindings window, click the Add button.
13 In the Add Site Binding window, provide the data below on the
Site Bindings modal window:
Type = https
IP address = All Unassigned
Port = 443 (this is the default port for https)
Host name = <Blank>
Require Server Name Indication = <Unchecked>
SSL Certificate = RecipeManagerPlusCert (or the one that you
created).
We recommend that you turn off the http:// binding. However, you
may have other web applications running on the site that still
require http://
14 Click OK in the Add Site Binding window.
15 The added site bindings should be listed in the Site Bindings
modal window.
16 Close the Site Bindings window.
17 Start the Recipe Manager Plus site using the https (that is:
https://<localhost>/recipemanagerplus).

61
Appendix B
About OPC UA
The Unified Architecture (UA) from the OPC Foundation is the next
generation OPC standard that provides a cohesive, secure and reliable
cross-platform framework for access to real time data. The OPC UA
Services implement the UA standard as a client service.
Understanding the OPC UA Standard

OPC UA defines a common infrastructure model to facilitate the
exchange of data between OPC UA-supported systems and devices,
using OPC UA-defined and vendor-defined data types. The OPC UA
Service uses OPC UA to exchange data.

62  Appendix B About OPC UA
About Classic OPC and OPC UA

OPC UA is a parallel standard to the classic OPC standard. It does not
replace the classic OPC standard, but complements it by addressing
its limitations.
Classic OPC
OPC originally stood for OLE (Object Linking and Embedding) for
Process Control. Later, the OPC Foundation dropped the acronym and
identified “OPC” as a word in its own right.
OLE is a Microsoft technology that allows an application to export
content in the form of an object to another application, and then
import it with additional content. Typically, the changes in the master
file automatically update the application or document that references
it. With OLE, the visual display of data from other applications is
possible within a host application, even when the host application
cannot generate such content by itself.
OPC provides a common interface for real-time communication
between different control devices and related software products from
different technology vendors.
There are several different OPC specifications for different
communication functions, the primary specifications being Data
Access (OPC DA), Historical Data Access (OPC HDA), and Alarms and
Events (OPC AE).
OPC UA
OPC UA unifies the different classic OPC specifications by means of a
unified architecture. It retains all the classic OPC functionalities while
leveraging the services technology. It also provides robust, reliable,
high-performance communication, suitable for automation.
OPC UA supports binary encoding for high-performance data
exchange, and incorporates a number of other improvements.

Understanding the OPC UA Standard63
Comparing OPC UA with Classic OPC

OPC UA differs significantly from its predecessor, OPC. The table
below explains the key differences between classic OPC and OPC UA.
Classic OPC OPC UA
Uses the COM/DCOM technology of Uses a services architecture to export

Microsoft to communicate. It does not data, which improves the ease of
have configurable time-outs. It depends communication and connectivity.
on the DCOM time-out, which is
configured in the system.
Is dependent on Windows operating Is platform independent and can connect

systems. to a wide variety of devices and platforms.
Has limited security. Has built-in security.
No built-in capabilities to handle Has built-in capabilities to handle

problems, such as lost messages. problems, such as lost messages.
For more information on OPC UA, see http://www.opcfoundation.org.
Understanding the OPC UA Connectivity

OPC UA provides connectivity to a variety of servers, clients, and
devices across various operating systems to exchange data. It connects
to third-party data sources.
An OPC UA Server is a discoverable software resource with a
well-defined service description. Any OPC UA Client can search, bind,
and connect to the OPC UA Server service. The Service Oriented
Architecture (SOA) is a set of patterns for creating loosely-coupled
services that provide flexibility and responsiveness for software
components to leverage the functionalities of one another.

64  Appendix B About OPC UA
About OPC UA Connectivity Capabilities

OPC UA connects to data sources at every level of the industrial
automation hierarchy. It connects to controllers, sensors, HMI
products, manufacturing systems, and planning systems. The diagram
below illustrates the levels to which OPC UA servers and clients can
connect.

Recipe Manager Plus Install Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Recipe Manager Plus Install Guide

Uploaded by

Copyright:

Available Formats

Wonderware

Recipe Manager Plus

© 2014 by Invensys Systems, Inc. All rights reserved.

Invensys Systems, Inc.

Chapter 1 Introduction ................................................ 7

Chapter 2 Recipe Manager Plus Installation .................. 11

Chapter 3 Recipe Manager Plus Configuration ............... 23

Wonderware Recipe Manager Plus Installation Guide

Chapter 4 Configuring Server Components in

Chapter 5 OPC UA Client Run Time.............................. 47

Chapter 6 Managing Digital Certificates........................ 51

Appendix A SSL ......................................................... 59

Appendix B About OPC UA ........................................... 61

Wonderware Recipe Manager Plus Installation Guide

The Wonderware Recipe Manager Plus Installation Guide describes

Convention Used for

Initial Capitals Paths and file names.

Wonderware Recipe Manager Plus Installation Guide

Wonderware Recipe Manager Plus Installation Guide

This section describes the Recipe Manager Plus features,

Recipe Manager Plus Architecture

Wonderware Recipe Manager Plus Installation Guide

• Input/Outputs. You can use an OPC UA Server or Wonderware

Wonderware Recipe Manager Plus Installation Guide

IIS and ASP.NET

Wonderware Recipe Manager Plus Installation Guide

Wonderware Recipe Manager Plus Installation Guide

Recipe Manager Plus

This section describes how to install, modify, repair, uninstall and

ArchestrA User Account

WARNING! The ArchestrA user account is a Windows operating

Wonderware Recipe Manager Plus Installation Guide

If no other ArchestrA-enabled software is installed on the computer,

Installing Recipe Manager Plus

To install Recipe Manager Plus features

Wonderware Recipe Manager Plus Installation Guide

2 Install the system-specific prerequisites. If your computer does not

Wonderware Recipe Manager Plus Installation Guide

6 Select the check boxes to indicate which features you want to

If an ArchestrA user account is required, the user account dialog

Wonderware Recipe Manager Plus Installation Guide

7 Specify an ArchestrA user account. You can specify an existing

c Specify a different domain/local machine name, if necessary. If

Any prerequisites you are missing will be identified as not met.

Wonderware Recipe Manager Plus Installation Guide

10 Click Install Prerequisites. The program installs the

11 Review your installation options and then click Install. The

12 If the installed features require configuration, click Configure. For

Wonderware Recipe Manager Plus Installation Guide

Modifying the Recipe Manager Plus Installation

To modify a Recipe Manager Plus installation

Note: The name of the Uninstall/Change button varies depending on

Wonderware Recipe Manager Plus Installation Guide

Repairing the Recipe Manager Plus Installation

Note: The name of the Uninstall/Change button varies depending on

Wonderware Recipe Manager Plus Installation Guide

Uninstalling Recipe Manager Plus

To uninstall a Recipe Manager installation

Note: The name of the Uninstall/Change button varies depending on

Upgrading Previous Versions

To upgrade a Recipe Manager Plus installation:

Wonderware Recipe Manager Plus Installation Guide

3 Click Next. The Wonderware Recipe Manager Plus Installation

Wonderware Recipe Manager Plus Installation Guide