SAP Plant Connectivity Overview
Applies to:
Plant Connectivity (PCo 2.3 SP4)
Summary
The following document provides an overview of the features and functionality of SAP Plant Connectivity,
Installation Pre-requisites, and detailed installation steps.
Author:
Company:
Created on:
Stephen Stubbs
SAP America
March 17, 2014
Author Bio
Stephen (Steve) Stubbs of SAP Labs has a Bachelor’s Degree in Electrical Engineering Technology from
Georgia Southern University. He is a member of the SAP I2P Organization in the Responsive Manufacturing
Solution Management group headed by Mike Lackey.
www.sap.com
TABLE OF CONTENTS
OVERVIEW ...................................................................................................................................................... 4
What is Plant Connectivity? ........................................................................................................................... 4
History ................................................................................................................................................................ 4
Core Technology ............................................................................................................................................... 4
PCO COMPONENTS ........................................................................................................................................ 5
Help and Detail Reference .............................................................................................................................. 5
Management Console...................................................................................................................................... 5
Source Systems ............................................................................................................................................... 6
OPC ................................................................................................................................................................... 6
OPCDA .............................................................................................................................................................. 7
OPCHDA ........................................................................................................................................................... 7
OPC A&E ........................................................................................................................................................... 7
OPC UA ............................................................................................................................................................. 7
Support Libraries ............................................................................................................................................... 7
OLEDB ............................................................................................................................................................... 8
ODBC ................................................................................................................................................................ 9
Proficy Historian............................................................................................................................................... 10
OSISoft PI Historian......................................................................................................................................... 11
Citect ................................................................................................................................................................ 12
IP21 Historian .................................................................................................................................................. 13
File Monitor ...................................................................................................................................................... 14
Socket .............................................................................................................................................................. 15
Agent Instance ............................................................................................................................................... 16
Subscription Items ........................................................................................................................................... 17
Notification ....................................................................................................................................................... 17
Trigger ............................................................................................................................................................. 17
Output .............................................................................................................................................................. 19
Destination ....................................................................................................................................................... 19
Consideration of Tag Deadband and Source Update Rate. ............................................................................ 19
Destination Systems ..................................................................................................................................... 20
2
SAP Plant Connectivity Overview
MII .................................................................................................................................................................... 20
Web Service .................................................................................................................................................... 22
RFC Destination .............................................................................................................................................. 24
ESP (Sybase Event Stream Processor) .......................................................................................................... 25
Simulation ........................................................................................................................................................ 26
Performance Monitoring ............................................................................................................................... 27
Windows Performance Counters ..................................................................................................................... 27
PCo Remote Client .......................................................................................................................................... 28
Source Agent SDK ......................................................................................................................................... 29
Custom Logic Interface ................................................................................................................................. 29
INSTALLATION .............................................................................................................................................. 30
Pre-Requisites................................................................................................................................................ 30
Execute the Installer ...................................................................................................................................... 30
3
SAP Plant Connectivity Overview
OVERVIEW
What is Plant Connectivity?
SAP Plant Connectivity (PCo) is a framework and set of services and management tools that allow the
creation of connectors that provide the communication paths between control systems, control devices, files,
historians, TCP Sockets, and SAP Manufacturing (SAP ME, SAP MII, SAP EWM, SAP ODA, etc.). PCo is a
Microsoft.Net-developed software component of SAP Manufacturing.
History
PCo is the 2nd generation of the SAP Manufacturing connector technology. It replaces the xMII UDS
(Universal Data Server) product that was originally developed by Lighthammer Corp. and brought into SAP
with the acquisition of Lighthammer by SAP in July of 2005.
The original release of PCo, version 2.0, was in December 2008. That release only supported the Real-Time
Event-Based Notifications, and provided the following Agents and Destinations:
 Agents:
o OPC DA Agent
 supports OPC DA 2.05a and 3.0 specifications
o OPC A&E Agent
o OPC UA Agent
 supports subscribing to OPC UA variable data-change events
 supports OPC UA v1.0 build 224 [and later] builds
o Socket Agent
 enables receiving stream-oriented socket messages
 Destinations:
o MII Destination
 supports delivering Notification Messages to MII 11.5, 12.0 and 12.1
o RFC Destination
 used for enabling bi-directional communication between EWM and the Socket Agent
 only used with the Socket Agent for the EWM scenario - does not provide general
RFC usage
Core Technology
PCo (through the current GA version 2.3) is built in C#, with some C++ for device drivers, on the .NET 3.5
Framework SP1. The core technologies used in this product include:





WCF (Windows Communication Foundation)
o WCF provides the industry's most robust WS (web service) stack, and enables MCS to
deliver a SOA architecture without the overhead of a web application server, like IIS. This is
accomplished through a technique called "self-hosting".
LINQ
SQL CE v3.5 (SQL Server Compact Edition) for configuration and log databases
WinForms
MSMQ (starting with PCo 2.3) for message queue handling
4
SAP Plant Connectivity Overview
PCO COMPONENTS
Help and Detail Reference
For the details of the PCo Components, please see the SAP PCo online help here.
Management Console
The PCo Management Console is the WinForms application that provides the configuration and
management of the PCo Source Agents, Destinations, Agent Instances, and Notifications.
Use of Management Console requires a Windows Administrative User account for configuration and
management. With PCo 2.3 and higher, a non-Administrative account may be used to open Management
Console in a “read-only” mode.
Figure 1: Management Console Application
Various System settings can be configured from the Management Console. Please refer to the help
documentation here.
5
SAP Plant Connectivity Overview
Source Systems
OPC
The OPC Source System Agents provide the connection to OPC Servers that expose various interfaces
identified in the following Source System Agents. OPC Server provide a common data and notification
interface to shop floor control systems and other devices without having to know the details of the
communication protocols or having to develop and maintain device drivers. Some widely used OPC Server
vendors:





Kepware KepServerEX
MatrikonOPC
Rockwell Software FactoryTalk Gateway
Rockwell Software RSLinx Classic
Siemens Simatic.Net OPC
All of the OPC Agents listed below are based on and require Microsoft COM for in-process or Distributed
COM (DCOM) for Remote access, except for OPC UA, which uses a TCP Binary or http transport for the
interface.
Figure 2: Management Console OPC Source System (OPCDA Source shown)
You can find the OPC Source systems help here,
6
SAP Plant Connectivity Overview
For more information about OPC, please visit the OPC Foundation. SAP is an active corporate member of
this foundation.
OPCDA
The OPCDA Source Agent provides connectivity to OPC Data Access (DA) Servers that expose either the
DA 2.05a or DA 3.00 interfaces. Only one OPC Server Interface can be defined per Source System Agent;
multiple Source Agents can be defined. This Source Agent supports both Query and Notification processes.
You can find the Help documentation here.
OPCHDA
The OPCHDA Source Agent provides connectivity to OPC Historical Data Access (HDA) Servers that
expose the HDA 1.20 interface Only one OPC Server can be defined per Source System Agent; multiple
Source Agents can be defined. This Source Agent supports both Query (Current and Aggregate) and
Notification processes.
Help documentation here.
OPC A&E
The OPC A&E Source Agent provides connectivity to OPC Alarms & Events (AE) Servers that expose the
AE 1.10 interface Only one OPC Server can be defined per Source System Agent; multiple Source Agents
can be defined. This Source Agent supports both Query and Notification processes.
OPC UA
The OPC UA Source Agent provides connectivity to OPC Unified Access (UA) Servers that expose the OPC
UA Interface. Only one OPC Server can be defined per Source System Agent; multiple Source Agents can
be defined. This Source Agent supports both Query (Current and Historical) and Notification processes.
Support Libraries
Depending on the OPC Source System to be configured, and other installation scenarios, additional OPC
support libraries may need to be obtained and installed.
1. Scenario 1: OPC COM Server Installed on PCo Server
a. Install the OPC Server first, and it should install any support libraries needed for OPC DA,
OPC HDA, or OPC A&E Source systems to work with OPC COM (or DCOM) servers.
2. Scenario 2: OPC COM Server NOT Installed on PCo Server
a. Download and install the OPC Core Components 3.00 Redistributable (x86) from this
OPC Foundation link before installing PCo.
3. Scenario 3: OPC UA Source System to be Used
a. Download and install the OPC UA Local Discovery Server 1.00 from this OPC Foundation
link before installing PCo.
i. Check the Release Notes for the specific version and SP of PCo to make sure you
download the correct version. For PCo 2.3 SP3, the correct version is OPC UA
Local Discovery Server 1.00 [250.8 Stable]. This is in the file name of the download.
Note: You may be required to register with the OPC Foundation Site before you can download files.
Help documentation is here for Session, Security and Subscription settings.
7
SAP Plant Connectivity Overview
OLEDB
The OLEDB Source Agent provides connectivity to Microsoft OLEDB providers. The available providers list
is dependent on what other software is installed on the PCo Server (Microsoft Office, SQL Server, etc.). Only
one Provider can be defined per Source System Agent; multiple Source Agents can be defined. This Source
Agent supports only the Query process.
Figure 3: Management Console OLEDB Source System
The Configure Connection String button opens a Microsoft Data Link dialog, which offers the list of
installed OLEDB providers, and provides a means to configure security, impersonation, and advanced
provider settings.
You can find the Help documentation here.
8
SAP Plant Connectivity Overview
ODBC
The ODBC Source Agent provides connectivity to Microsoft 32-bit ODBC providers. The available providers
list is dependent on what other software may be installed on the PCo Server. Only one Provide can be
defined per Source System Agent; multiple Source Agents can be defined. This Source Agent supports only
the Query process.
Figure 4: Management Console ODBC Source System
Note: On 64-bit OS, the 32-bit odbc administrator tool MUST be used. This tool is located at
\Windows\SysWOW64\ odbcad32.exe.
You can find the Help documentation here.
9
SAP Plant Connectivity Overview
Proficy Historian
The Proficy Historian Source Agent provides connectivity to the GE FANUC Proficy Historian via native
connectivity. Only one connection can be defined per Source System Agent; multiple Source Agents can be
defined. This Source Agent supports both Query and Notification processes.
Figure 5: Management Console Proficy Historian Source System
In Order to use this Source Agent, the Proficy Historian SDK, specific to the Proficy Historian Version, must
be installed prior to installing PCo.
You can find the Help documentation here.
10
SAP Plant Connectivity Overview
OSISoft PI Historian
The OSISoft PI Historian Source Agent provides connectivity to the OSISoft PI Historian via native
connectivity. Only one connection can be defined per Source System Agent; multiple Source Agents can be
defined. This Source Agent supports both Query and Notification processes.
Figure 6: Management Console OSISoft PI Historian Source System
In Order to use this Source Agent, the PI SDK, version 1.3.6 or later (may depend on the version of PI being
connected), must be installed prior to installing PCo. The versions of the SDK can be found here. A
registration is required before the SDK can be downloaded.
You can find the Help documentation here.
11
SAP Plant Connectivity Overview
Citect
The CiTect Source Agent provides a connection to a CiTect SCADA system via native connectivity. Only
one connection can be defined per Source System Agent; multiple Source Agents can be defined. This
Source Agent supports both Query and Notification processes.
Figure 7: Management Console CiTect Source System
In order to use the CiTect Source Agent, it will be necessary to copy some CiTect files into the PCo System
directory. The specifics are documented here.
You can find the Help documentation here.
12
SAP Plant Connectivity Overview
IP21 Historian
The IP21 Historian Source Agent provides a connection to an AspenTech IP21 Historian via native
connectivity. Only one connection can be defined per Source System Agent; multiple Source Agents can be
defined. This Source Agent supports only the Query process.
Figure 8: Management Console IP21 Historian Source System
In order to use the CiTect Source Agent, it will be necessary to copy some IP21 files into the PCo System
directory. The specifics are documented here.
You can find the Help documentation here.
13
SAP Plant Connectivity Overview
File Monitor
The File Monitor Source Agent provides the means to monitor a Windows directory, (either locally or in a
remote Share), detect a file creation change, and act on that change. Only one Source Agent can be defined
per directory; Multiple Source Agents can be defined. This Source Agent supports both Query and
Notification processes. Both ASCII text and binary file contents are supported for the file contents; however,
proper binary content handling must be provided by the recipient (Destination) of the content.
Figure 9: Management Console File Monitor Source System
The Source Agent can retrieve the full path\file name of the file(s) detected as well as the file contents, and
can be configured to Rename/Move/Copy/Delete/DoNothing upon file detection.
Note: since the Agent detects a file existing in a folder or share, use of the DoNothing File Handling Action
will cause any File Monitor Agent Instance Notification to execute at the Monitoring Frequency of the Source
System.
14
SAP Plant Connectivity Overview
The agent also exposes the following Custom Functions, which can be accessed and executed from an
upcoming patch to MII 14 SP4:




APPENDFILE
DELETEFILE
RENAMEFILE
COPYFILE
These functions can be executed on any path\file to which the PCo Agent Instance has path access and
permissions for the user permissions for the Agent.
You can find the Help documentation here
.
Socket
The Socket Source Agent provides the means to connect to a host Socket and interact with the socket.
Multiple Named Socket connections can be defined per Source Agent, and multiple Source Agents can be
defined. Each connection supports IPV4 and IPV6, and can define either a fixed-length stream or delimited
stream for monitoring. This Source Agent supports only the Notification process. The Agent can accept
either a text or binary stream; however, proper binary stream content handling will need to be provided by
the recipient (Destination).
Figure 10: Management Console Socket Source System
15
SAP Plant Connectivity Overview
The agent also exposes the following Custom Functions, which can be accessed and executed from an
upcoming patch to MII 14 SP4:




GET_AGENT_STATE
START (opens a specified IP address and Port)
SEND (sends a stream of text data to an open IP/Port)
STOP (closes the IP Address and Port START’ed above)
You can find the Help documentation here.
Agent Instance
The Plant Connectivity Agent Instance is the object that does the actual work. Each Agent Instance defined
in Management Console consists of the following PCo Components:
 One Source Agent
 Agent Instance
 Zero or More Notifications. See Notification below for the Notification details.
An Agent Instance without any defined Notification objects is only a Query Instance. It is then used as a data
connector between the defined Source Agent and MII as follows:
 Agent Instance Listens on an MII (V12.2 or later) and/or MII Before 12.1 (Legacy) Port defined for
each Instance
 MII Data Servers are defined for each Agent Instance’s Port
o Data Server Type PCoConnector for MII port
o Data Server Type UDC for MII Legacy Port
 MII Query Template object to query the source system data store
o PCo Query Template via the PCoConnector
o Tag Query Template via the UDC Connector
If a Notification is defined in an Agent Instance, that Instance can still be used as a Query instance by MII.
Both the Query and Notification objects in PCo are multi-threaded and can support concurrent queries and
notifications.
You can find the Help documentation here.
16
SAP Plant Connectivity Overview
Subscription Items
An Agent Instance that will have defined Notifications will also require that Subscription items (Tags) be
defined that can be used in the Notification Trigger and Output definitions. These tags can be browsed and
selected from the Subscription Items tab of the Agent Instance configuration:
Figure 11: Management Console Agent Instance Subscription Items Tab
Notification
The Notification object in PCo is the entity that can detect events, collect additional Tag Data at event time,
and send the event data to a Destination. Each Agent Instance can instantiate multiple Notifications.
The Notification object consists of the following:
Trigger
The Notification Trigger is a logical expression that evaluates an Agent Instance Subscription Tag or other
defined value (i.e., Datetime, etc.) to resolve a Boolean result. The result is then evaluated by the Trigger
Type Definition, which has 5 options:
 Always – Notification Output is executed when any of the Agent Instance Subscription Tags changes
value.
 OnTrue – Notification Output is executed when the Trigger expression changes from False to True
after a Trigger Tag Value change. The expression must be evaluated to False before another On
True event can be detected. This is sometimes referred to as a Rising Edge Trigger.
 WhileTrue – Notification Output is executed when The Trigger expression evaluates to True after a
Trigger Tag Value change. The expression does not have to evaluate False before another While
True event can be detected.
17
SAP Plant Connectivity Overview
 OnFalse – Notification Output is executed when the Trigger expression changes from True to False
after a Trigger Tag Value change. The expression must be evaluated to True before another On
False event can be detected. This is sometimes referred to as a Falling Edge Trigger.
 WhileFalse – Notification Output is executed when The Trigger expression evaluates to False after a
Trigger Tag Value change. The expression does not have to evaluate True before another While
False event can be detected.
18
SAP Plant Connectivity Overview
Output
The Output object consists of one or More Tag or Constant Expressions that are evaluated at the time the
Trigger is executed. The evaluated value of each Output is packaged into an Output Notification Message
for consumption by the Destination.
Destination
The Destination is an Instance of a Defined Destination System. Depending on the Destination, the data in
the Output Notification Message is mapped to parameters of the Destination. The Destination is then
contacted and the data is passed. See Destination Systems below for details.
Consideration of Tag Deadband and Source Update Rate.
When creating the OPC Source Agent, one of the configuration items on the Details tab is the Update Rate.
This tells the OPC Server how frequently to read the subscribed tags and get change updates sent back to
PCo. This is effectively the data sample rate. With Subscription and Trigger tags it is important to recognize
that data that changes at the source at a rate faster than the update rate will not be detected by the OPC
Server: For example, if you have the Update Rate set to 1 second, and a tag that is subscribed is changing
value every 500 mSec, only every other value will be updated to PCo. If a Boolean value is changing from
false to true and false within the update rate, that data change event will NOT be detected by PCo.
It is possible to define a Deadband for each Agent Instance Subscription Tag. This is a value in Percent that
defines the minimum change in value of a tag before the tag value is updated in the Agent Instance. This is
usually used with tag values that contain some “noise”, such as Analog process measurement values like
flow rate or pressure. The intent of the deadband is to minimize the noise updates in value but capture the
valid process change values. Unless there is a valid reason to set the deadband value to minimize noise,
always set this value to 0.
You can find more information on the Deadband here.
For Help on the Agent Instance please look here.
19
SAP Plant Connectivity Overview
Destination Systems
Destination Systems provide a mechanism to send data assembled or defined in an Agent Instance
Notification Output to a destination that can process the data. All Destinations are defined as One-Way: the
Notification can send the data to the destination and determine if the transmission was successful, but
cannot process any response, other than to log it for the agent instance, from the destination and act on that
response.
MII
The MII Destination Agent provides a means to send the Plant Connectivity Notification data to MII for
subsequent processing by an MII Transaction. The entire contents of the PCo Agent Instance Notification
Output message is mapped to a single MII Transaction Input Parameter of type XML. A single Destination
can be referenced by multiple Notification Destinations, and can reference the same Transaction from
different Notification Destinations.
The connection between PCo and MII is via http to the MII listener port. Once the connection is
authenticated, a session is maintained between the PCo Agent Instance and MII. This session is validated
periodically (the Keepalive value in Advanced Settings) and renewed automatically when it expires, or until
the Agent Instance is stopped.
Figure 12: Management Console MII Destination Configuration
20
SAP Plant Connectivity Overview
Figure 13: Management Console MII Destination Instance Configuration from Notification Destination Tab
Destination Transactions can be executed in either of two modes:
 Synchronous – MII sends a response back to the Destination with the results of the Transaction
execution (success or failure). This event closes the Notification event. Transaction failures are
logged to the Agent instance log as Errors.
 Asynchronous – once MII has successfully received the MII Transaction request, the Notification event
is closed. The transaction must handle all exceptions and error notifications.
Transaction Persistence controls wow the Transaction results are stored internally in MII. ONERROR is
recommended for production as it only logs any transaction detail when the transaction terminates with error.
You can find the Help documentation here.
21
SAP Plant Connectivity Overview
Web Service
The Web Service Destination Agent provides a means to send the Plant Connectivity Notification data to
Web Service for subsequent processing by the web service.
Figure 14: Management Console Web Service Destination Settings
22
SAP Plant Connectivity Overview
Web Service Request element values can be defined statically within the Destination, or as Variables.
Figure 15: Management Console Web Service Destination Operation Mapping
The Notification Output values can be mapped to specific Web Service request Variables. The Web Service
destination can only map single Web Service WSDL per defined destination. Multiple instances of the
destination can be defined, but any Notifications that instantiate the Destination must map an Output value to
each Web Service Request Variable.
Both DOC and RFC Web Service types are supported. Note that MII Transactions can also be called as a
Web Service from this destination type using the MII WSDLGen method to define the transaction WSDL:
Ex: http://usphlvmxxxx.phl.sap.corp:50400/XMII/WSDLGen/i822004/ME_API/TestTagWrite
You can find the Help Documentation here.
23
SAP Plant Connectivity Overview
RFC Destination
The RFC Destination provides a means for PCo to execute an SAP RFC call to one of 3 types:
 SAP EWM
 SAP ODA
 SAP NW
Figure 16: Management Console RFC Destination
For more information, please see the Implementation Guide for the Connection of External Data
Sources to SAP Business Suite Applications here.
You can find the Help documentation here.
24
SAP Plant Connectivity Overview
ESP (Sybase Event Stream Processor)
The Sybase ESP Destination can be used to send Notification Output data to the destination to be inserted
as a new row in the Defined ESP Project Stream.
Figure 17: Management Console Sybase ESP Destination
You can find the Help documentation here.
25
SAP Plant Connectivity Overview
Simulation
The Simulation Destination is primarily used for testing. It provides a means to capture the Notification
Output XML message and store it in a unique file name, with the option of providing a pre-define percent
response failure, and a sleep time delay in the response.
Multiple Simulation Destinations can be defined, and a defined Destination can be instantiated by multiple
Notifications.
Figure 18: Management Console Simulation Destination
You can find the Help documentation here.
26
SAP Plant Connectivity Overview
Performance Monitoring
Windows Performance Counters
SAP Plant Connectivity includes a set of Windows Performance Counters that can be used with the Windows
Performance Monitor in real time, or in Performance Monitor Data Collector Sets, which can record and
persist the Performance Monitor Counters for later playback and analysis.
The Counters are defined per Agent Instance, as shown here:
For Agents that support the Query Process:
For Agents that support the Notification Process:
In addition, the standard Performance Counters (for Memory, CPU, etc.) can be assigned as well for
performance monitoring.
For help with the Windows Performance Monitor, please refer to this Microsoft Reference.
27
SAP Plant Connectivity Overview
PCo Remote Client
The PCo Remote Client is a tool that can be used to remotely monitor and control a PCo Server. From a
connection from Remote Client to the remote PCo server, you can:





Browse the list of configured Agent Instances
Start/Stop Agent Instances
Retrieve Agent Instance Configurations
Retrieve Agent Instance Logs
Enable/Disable Active Monitoring
o Configure an MII Transaction that is executed when the Agent State changes
Figure 19: Remote Client
PCo systems can be retrieved either from the SAP System Landscape Directory if PCo is registered there, or
directly from the Server.
Note: PCo ManagementHost Service must be Started on the PCo Server in order for Remote Client to
connect and monitor system.
You can find the Help documentation here.
28
SAP Plant Connectivity Overview
Source Agent SDK
For the customer or SAP Partner interested in extending PCo Source Agent capability, SAP provides the
Source Agent SDK installer as part of the PCo install. This installer is located in the PCo install path, typically
here:
C:\Program Files (x86)\SAP\Plant Connectivity\AgentSDK
The installer provides a development framework that can be used with Microsoft Visual Studio and C# to
develop a custom Source Agent. Additional information can be found here.
Custom Logic Interface
For the customer or SAP Partner interested in extending the functionality of the Web Service Destination, or
to build a Custom Destination, SAP provides a set of interfaces to create a Custom Logic interface. This
interface is used with Visual Studio and C# to build a plugin dll that can provide some of the following
capability:
 Execute Web Service Destinations in Sequence
 Receive the response from a Web Service request and act on the response data,
 Map Web Service response and other data from within the DLL to PCo Tags that can then be written
to the same or different Agent Instance.
Additional information can be found here.
29
SAP Plant Connectivity Overview
INSTALLATION
PCo is installed by downloading an installer from SAP Service Marketplace and executing that installer
executable. To obtain the latest version of PCo, visit SAP Service Marketplace as follows (You will need to
have access to navigate!):
http://service.sap.com Support PortalSoftware DownloadsSupport Packages and PatchesA-Z
IndexPSAP Plant ConnectivitySAP Plant Connectivity 2.3  SAP Plant Connectivity 2.3Win32.
At this point you will see a list of all the patches and Service Packs for the product, simply pick the most
recent one by date (dd.mm.yyyy date format) and start downloading.
If you intend to install PCo in a different directory than the default C:\Program Files (x86)\SAP\Plant
Connectivity, you will need to create that directory path prior to executing the installer.
Pre-Requisites
 Review Master Guide here.
 Review Installation Guide for installation requirements here.
 Review the Support Libraries to make sure all required downloads are installed.Validated OS from the
Plant Connectivity Product Availability Matrix PAM here:
http://service.sap.com/pam Application Filters(enter SAP Plant Connectivity 2.3)
SearchPlant SAP Plant Connectivity 2.3Technical Release InformationOperating
SystemsDetails
 Support software if using OPC DA/HDA/A&E or UA, Native Historians, etc.
 Set the Windows Service Net TCP Port Sharing to Automatic or Automatic (Delayed Start), and Start
the service:
Execute the Installer
Execution of the installer is straightforward. You will be presented with a list of options to install; it is OK to
install all of them. The full install of PCo is < 100 MB so it should not be an issue.
Note: If you attempt to install some of the Source Agents that require some prerequisite support software,
you be presented with an installer error. In most cases it is OK to acknowledge the error and continue, but
the Source Agent will likely NOT be installed.
30
www.sap.com
© 2014 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP
products and services mentioned herein as well as their respective
logos are trademarks or registered trademarks of SAP AG in Germany
and other countries.
Business Objects and the Business Objects logo, BusinessObjects,
Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP
company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL
Anywhere, and other Sybase products and services mentioned herein
as well as their respective logos are trademarks or registered
trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are
registered trademarks of Crossgate AG in Germany and other
countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of
their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials
are provided by SAP AG and its affiliated companies ("SAP Group")
for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express
warranty statements accompanying such products and services, if
any. Nothing herein should be construed as constituting an additional
warranty.