Installation Guide

Plant Connectivity 2.2

Target Audience
M System administrators
M Technology consultants

PUBLIC
M )KyH(wA)MgE^,oTdURH -"mb
Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.
You can find the latest version at the following location: https://service.sap.com/
instguides.

Version Date Description

1.0 2011-06-06 Initial version
1.1 2012-03-30 Information added to Introduction section and Preparation section

2/22 PUBLIC 2012-03-30

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1 Microsoft Preparation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2 PCo Agent Preparation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.3 Upgrade Preparation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1 Initial Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.2 Upgrade Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.1 License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.2 Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.3 Checking the Upgrade Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2012-03-30 PUBLIC 3/22

This page is left blank for documents
that are printed on both sides.
1 Introduction
1.1 About this Document

1 Introduction

1.1 About this Document

This installation guide describes the steps required to install or upgrade Plant Connectivity (PCo) Rel.
2.2. It specifies the sequence of installation activities and their dependencies.

NOTE

The term Installation in this guide is also valid for an upgrade of Plant Connectivity. If there are
additional steps to be taken into consideration, or steps that differ from the initial installation
procedure, this will be mentioned separately in this guide.

The target groups are:

o5L System administrators
o5L Technical consultants
o5L Application consultants
o5L Project team members
PCo is delivered as an installation package that enables you to perform a complete or custom installation.
o5L The complete installation includes all PCo components.
o5L The custom installation allows you to choose the specific components that you want to install,
for example, selected agents or destinations.
The installation includes the following components:
o5L PCo core components
o5# Management Console
o5# Management Service
o5# Connectivity Framework
o5# Remote Client (for MMC - Microsoft Management Console)
o5L PCo agents
o5# CitectSCADA (Schneider Electric)
o5# File Monitor
o5# IP21 - InfoPlus.21 (AspenTech)
o5# ODBC
o5# OLE DB
o5# OPC A&E
o5# OPC DA
o5# OPC HDA

2012-03-30 PUBLIC 5/22

1 Introduction
1.2 Before You Start

<j OPC-UA
<j PI Historian (OSIsoft)
<j Proficy Historian (General Electric)
<j Socket
<j PCo destinations
<j MII
<j RFC (EWM, Business Suite, SAP ODA Replacement)
<j Simulation
<j Web Service Destination (SAP ME)

1.2 Before You Start

The following information must be taken into consideration before starting the installation.

1.3 SAP Notes for the Installation

SAP Note Number Title Description
SAP Note Number1551065 Release Installation Note for PCo 2.2 Up-to date information on PCo 2.2
Service Pack 00 installation
SAP Note Number1658810 Release Installation Note for PCo 2.2 Up-to date information on PCo 2.2 (SP03)
Service Pack 03 installation

1.4 Naming Conventions

In this documentation, the following naming conventions apply:
Variable Name Description
<INSTDIR> Installation directory for the PCo installation (for example, C:\Program Files SAP Plant
Connectivity
<Date> Date (for example, 2011.01.17 or 2011_Jan_20)
<Time> Time (for example, 08:00:00 or 08.00.00 - used in file names)

6/22 PUBLIC 2012-03-30

2 Planning

2 Planning

PCo runs on the following operating systems:

<w Microsoft Windows XP Professional, Service Pack 2 or later (32-bit)
<w Microsoft Windows Vista (32-bit)
<w Microsoft Windows 7 (32-bit)
<w Microsoft Windows Server 2003 Service Pack 1 or higher (32-bit or 64-bit) with PCo running in 32-
bit mode on 64-bit operating systems
<w Microsoft Windows Server 2008 (32-bit or 64-bit), with PCo running in 32-bit mode on 64-bit
operating systems

NOTE

When installing PCo on Windows XP or Server 2003, you must be logged on as a local administrator.
When installing PCo on Windows 7, Vista or Server 2008, you must not only be logged on as a
local administrator, but you must also carry out the installation using an elevated privilege or a
Run as Administrator privilege. These requirements ensure proper software installation.

NOTE

For more information, see the PCo Security Guide at https://service.sap.com/instguides.

If you are carrying out an upgrade, the following applies:

<w You can upgrade from any previous version of PCo directly to PCo 2.2.
<w All existing agent instances and settings remain intact and will be migrated automatically if
necessary.
<w Because all agent instances need to be stopped for the upgrade, it is recommended to plan some
downtime for each PCo upgrade (minimum 15-30 minutes).

2012-03-30 PUBLIC 7/22

This page is left blank for documents
that are printed on both sides.
3 Preparation
3.1 Microsoft Preparation Steps

3 Preparation

Before installing PCo, you must carry out the following preparatory steps for the operating system you
are installing on and the type of agents you want to install. Please also check these steps if you are
carrying out an upgrade.

3.1 Microsoft Preparation Steps

You must observe the following installation steps for Microsoft operating systems:
-( .NET Installation
Before installing PCo, you must install Microsoft .NET Framework Version 3.5 SP1 (or any higher
release). For more information, see http://www.microsoft.com. In Windows 7 and Windows 2008
Server, the .NET Framework is already included.
-( Windows Services
The following Windows Services can be used:
-( Net.Tcp Port Sharing Service
You have to set the Microsoft Windows Net.TCP Port Sharing Service to be able to use the
Automatic startup type.
CAUTION

By default, this is disabled and makes PCo inoperable.

-( OPCEnum
If you are installing PCo on Windows 7, the service settings of OPCEnum also have to be set to
Automatic. If it has not already started, you must start the service manually.
-( Remote Client (Microsoft Management Console, MMC)
If you want to use the remote client MMC snap-in, you must install MMC Version 3.0. MMC 3.0
is included with Windows Server 2003 R2, Windows Server 2003 SP2, Windows Vista, Windows
Server 2008 and Windows XP SP3. It is downloadable for Windows XP SP2 and Windows Server 2003
SP1.
-( Windows 7 Security Options
If you are installing PCo on Windows 7, you need to set the security option Network Access: Let
everyone permissions apply to anonymous users to enabled under the following path: Control Panel System
and Security Administrative Tools Local Security Policy Local Policies Security Options .

2012-03-30 PUBLIC 9/22

3 Preparation
3.2 PCo Agent Preparation Steps

3.2 PCo Agent Preparation Steps

You must observe the following steps for the Plant Connectivity agents before installing the program.
y<n Citect agent
1. Copy the files for the CtApi interface from the Citect installation directory into the PCo system
directory (for example, to c:\Program Files\SAP\Plant Connectivity\System):
y<n ctapi.dll
y<n ct_ipc.dll
y<n cteng32.dll
y<n ctres32.dll
y<n ctutil32.dll
2. If PCo is not installed on the same machine as Citect you have to set the following in the
CitectSCADA configuration file (citect.ini):
[CTAPI]
Remote=1

y<n IP21 Agent: To use the IP21 agent, carry out the following steps:
1. Ensure that a valid Windows user exists at the PCo machine and the IP21 database machine.
2. Copy the following files for the DBApi interface from the IP21 installation directory into the
PCo system directory (for example, c:\Program Files\SAP\Plant Connectivity\System):
y<n cimsrvapi.dll
y<n CimWin32Util.dll
y<n infoplus21_api.dll
y<n ip21admin_client.dll
y<n ip21ezrpcw32.dll
y<n ip21winrpc32.dll
y<n libc21.dll
3. Every tag in IP21 that you want to use with PCo needs to have the following fields:
y<n IP_VALUE
y<n IP_VALUE_TIME
y<n IP_VALUE_QUALITY
y<n IP_#_OF_TREND_VALUES
y<n IP_TREND_VALUE
y<n IP_TREND_QSTATUS
y<n IP_TREND_QLEVEL
y<n IP_DESCRIPTION
y<n IP_GRAPH_MINIMUM
y<n IP_GRAPH_MAXIMUM
y<n ODBC Agent

10/22 PUBLIC 2012-03-30

3 Preparation
3.3 Upgrade Preparation Steps

If you want to use the ODBC agent, you first have to install and configure the ODBC driver for
your data source using the Windows tool ODBC Data Source Administrator. For more information about
the ODBC Data Source Administrator, see the PCo documentation under SAP Help Portal SAP Business
Suite SAP Manufacturing SAP Plant Connectivity PCo 2.2 .
 OLE DB Agent: If you want to use the OLE DB agent, you must install MDAC 2.8.
 OPC Agents
 If you want to use the OPC A&E agent, you must install the following:
 OPC A&E server compliant with Version 1.10 of the OPC A&E specifications
 OPC core components 3.0 redistributable
 If you want to use the OPC DA agent, you must install the following:
 OPC DA server compliant with Version 2.05a or 3.0 of the OPC DA specifications
 OPC core components 3.0 redistributable
 If you want to use the OPC HDA agent, you must install the following:
 OPC HDA server compliant with Version 1.20 of the OPC HDA specifications
 OPC core components 3.0 redistributable
 If you want to use the OPC-UA agent, you must install the following:
 OPC-UA server compliant with Version 1.0 of the OPC-UA specifications
 OPC-UA SDK 1.00 redistributable (build 250 or later)
NOTE

If the respective OPC server has automatically installed the OPC core components, you
do not have to reinstall them.
 PI Agent: If you want to use the OSIsoft PI agent, you must install PI SDK Version 1.3.6 or later.
 Proficy Agent: If you want to use the Proficy Historian agent, you must install Proficy Historian
SDK.

3.3 Upgrade Preparation Steps

Before starting an upgrade, you must stop all agent instances and close the PCo Management Console.
Then carry out the upgrade installation as described below.

2012-03-30 PUBLIC 11/22

This page is left blank for documents
that are printed on both sides.
4 Installation
4.1 Initial Installation

4 Installation

The installation procedure differs, depending on whether you are carrying out an initial installation
or an upgrade. If PCo is already installed, and you want to carry out an upgrade, please follow the
instructions in the next section (Upgrade Installation).

4.1 Initial Installation

To install Plant Connectivity (PCo), proceed as follows:
1. Run the PCo installation program.
The SAP NetWeaver Front-End Installer Welcome dialog appears.
2. Choose Next.
3. Choose Select All to install all components.
To select or deselect specific components, expand the PCo node and choose only the components
that you want to install.
4. Choose Next.
5. Confirm the installation directory or change it using the Browse pushbutton.
6. Choose Next. Product installation starts.
7. After installation has finished, choose Done.

4.2 Upgrade Installation

To install Plant Connectivity (PCo), proceed as follows:
1. Run the PCo installation program.
The SAP NetWeaver Front-End Installer Welcome dialog appears.
2. Choose Next.
3. Choose Select All to install all components. This will also flag newly available PCo components for
installation. To select or deselect specific components, expand the PCo node and choose only the
components that you want to install.
4. Choose Next. Product installation starts.
5. After installation has finished, choose Done.

2012-03-30 PUBLIC 13/22

This page is left blank for documents
that are printed on both sides.
5 Post-Installation
5.1 License

5 Post-Installation

5.1 License
Starting with version 2.2, you need a license key for the productive use of PCo. Without installing a
license key, all running agent instances will automatically stop after 30 minutes. You will also see a red
message in the menu bar of the Management Console if you run PCo without a license.
For more information on license handling in PCo please refer to the documentation under Plant
Connectivity System Settings License Key .

5.2 Checks
To check your PCo installation, proceed as follows:
1. Start the PCo Management Console in the Windows menu: Start All Programs SAP Plant
Connectivity Management Console .
2. The Plant Connectivity Management Console screen appears.
3. To check whether all installed agents (source systems) are available, proceed as follows.
1. Start creating a new source system under the PCo menu: File New Source System .
2. Open the drop-down list of source system types.
3. Check whether all the source system types that you had flagged for installation are available.
4. Click Cancel (close the popup).
4. Check whether all installed destinations are available:
1. Start by creating a new destination system under the PCo Menu: File New Destination
System .
2. Open the drop-down list of destination system types.
3. Check whether all destination system types that you had flagged for installation are available.
4. Click Cancel (close the popup)
5. Optionally (or in case of problems) check the installer log in the PCo root install directory:
<INSTDIR>\PCoInstallUtility_<Date>_<Time>.csv

5.3 Checking the Upgrade Installation

If you are carrying out an upgrade, you must perform the following additional steps:
1. Restart all agent instances that were stopped before the upgrade.

2012-03-30 PUBLIC 15/22

5 Post-Installation
5.3 Checking the Upgrade Installation

2. Optionally (or in case of problems) check the migration log in <INSTDIR>

\PCoMigrationUtility_<Date>_<Time>.csv.

16/22 PUBLIC 2012-03-30

6 Additional Information

6 Additional Information

To allow remote communication between an agent instance in PCo OPC A&E (Alarms and Events),
OPC DA, or OPC HDA and an OPC A&E, OPC DA, or OPC HDA server respectively, you must correctly
configure DCOM security.
For more information, see http://www.opcfoundation.org Downloads White Papers OPC, DCOM
and Security and see thePlant Connectivity 2.2 Security Guide on the SAP Service Marketplace.

2012-03-30 PUBLIC 17/22

Typographic Conventions

Example Description
<Example> Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, Enter your <User Name>.
Example Arrows separating the parts of a navigation path, for example, menu options
Example
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the
documentation
http://www.sap.com Textual cross-references to an internet address
/example Quicklinks added to the internet address of a homepage to enable quick access to specific
content on the Web
123456 Hyperlink to an SAP Note, for example, SAP Note 123456
Example . Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
. Cross-references to other documentation or published works
Example . Output on the screen following a user action, for example, messages
. Source code or syntax quoted directly from a program
. File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, database table names, and key concepts of a programming language
when they are surrounded by body text, for example, SELECT and INCLUDE
EXAMPLE Keys on the keyboard

18/22 PUBLIC 2012-03-30

 SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com

Copyright 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft
Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/
OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA,
pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks,
OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of
IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the United States and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and other countries.
Oracle and Java are registered trademarks of Oracle and its affiliates.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems Inc.
HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium,
Massachusetts Institute of Technology.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are
trademarks or registered trademarks of Apple Inc.
IOS is a registered trademark of Cisco Systems Inc.
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm,
BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research
in Motion Limited.
Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile
Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik
and Android are trademarks or registered trademarks of Google Inc.
INTERMEC is a registered trademark of Intermec Technologies Corporation.
Wi-Fi is a registered trademark of Wi-Fi Alliance.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
Motorola is a registered trademark of Motorola Trademark Holdings LLC.
Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
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.

2012-03-30 PUBLIC 19/22

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.

Disclaimer
Some components of this product are based on Java. Any code change in these components may cause unpredictable and
severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.
Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified or
altered in any way.

Documentation in the SAP Service Marketplace

You can find this document at the following address: http://service.sap.com/instguides

20/22 PUBLIC 2012-03-30

 SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com

Copyright 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained
herein may be changed without prior notice.