WinPM Net Commissioning Guide

WinPM.Net 4.
0
Commissioning Guide
DANGER
Hazardous voltages and high-speed moving parts in electrical devices
communicating with WinPM.Net can cause death, serious injury or
property damage.
See safety instruction contained herein. Restrict use to qualified
personnel.
The use of unauthorized parts in the repair of the equipment or tampering by unqualified personnel
will result in dangerous conditions that can cause death, serious injury or property damage.
PLEASE READ
WinPM.Net can be configured to send commands to devices automatically. WinPM.Net can be used
to manually send commands to devices and to reconfigure the settings of devices.
IMPORTANT
The information contained herein is general in nature and not intended for specific application
purposes. It does not relieve the user of responsibility to use sound practices in application, installation,
operation, and maintenance of the equipment purchased. Siemens reserves the right to make changes
at any time without notice or obligations. Should conflict arise between the general information
contained in this publication and the contents of drawings or supplementary material or both, the latter
shall take precedence.
QUALIFIED PERSONNEL
For the purposes of this manual and product labels, "qualified personnel" is one who is familiar with
the installation, construction, or operation of the equipment and the hazards involved. In addition, s/
he has the following qualifications:
(a)is trained and authorized to energize, de-energize, clear, ground, and tag circuits and equipment
in accordance with established safety practices.
(b)is trained in the proper care and use of protective gear equipment such as rubber gloves, hard hat,
safety glasses or face shields, flash clothing, etc., in accordance with established safety procedures.
(c)is trained in rendering first aid.
SUMMARY
These instructions do not purport to cover all details or variations in equipment, nor to provide for every
possible contingency to be met in connection with installation, operation, or maintenance. Should
further information be desired or should particular problems arise which are not covered sufficiently
for the purchasers purposes, the matter should be referred to the local Siemens Industry, Inc. sales
office.
THE CONTENTS OF THIS INSTRUCTION MANUAL SHALL NOT BECOME PART OF OR MODIFY
ANY PRIOR OR EXISTING AGREEMENT, COMMITMENT OR RELATIONSHIP. THE SALES CONTRACT
CONTAINS ALL OBLIGATIONS OF SIEMENS INDUSTRY, INC. THE WARRANTY CONTAINED IN THE
CONTRACT BETWEEN THE PARTIES IS THE SOLE WARRANTY OF SIEMENS INDUSTRY, INC.
ACCESS, ISGS, Isolated Multi-Drop, S7-I/O, SBwin, SAMMS-LV, SAMMS-MV, SEAbus, SIEServe,
Static Trip III, Wisdom, and WinPM.Net are trademarks, Sensitrip and Sentron are registered
trademarks of Siemens Industry, Inc. SIEMENS is a registered trademark of Siemens AG. Windows is
a trademark of Microsoft Corporation. ION, Modbus and WebMeter are either trademarks or
registered trademarks of Schneider Electric in France, the USA and other countries. All other product
names mentioned herein are used for identification purposes only and may be the trademarks or
registered trademarks of their respective companies.
Contents
Introduction ..................................................... 7
Types
of Installation ............................................... 7
Primary Server ...........................................................

Database Server ........................................................
Client ........................................................................
Secondary Servers ......................................................
Determine
7
7
8
8
Your Network Needs .............................. 9
System Requirements .................................................. 9
Prepare the Workstation ................................... 9

Server
Naming and Partition Guidelines ................ 10
Operating
System Considerations ......................... 10
Server 2003 ............................................................

Server 2008 ............................................................
Windows XP .............................................................
Windows Vista .........................................................
Installing WinPM.Net on a Virtual Machine ................
WinPM.Net
10
10
11
11
11
Administrator Server Permissions ........ 12
Prepare
the Primary Server ................................... 13
Firewall
Configuration ......................................... 13
SQL Server Configuration ............................... 14

SQL Server 2005 Standard Edition Setup ................... 15
Update All SQL Server Instances ............................... 17
Install or Upgrade WinPM.Net ........................ 17

Installing
WinPM.Net ........................................... 17
Install WinPM.Net Database Server (Optional) ...........

Install WinPM.Net Primary Server ..............................
Install WinPM.Net Clients (Optional) .........................
Install WinPM.Net Service Packs (if available) .............
Upgrading
17
18
18
19
WinPM.Net ........................................ 19
Step 1: Upgrade System Hardware and Software .......

Step 2: Back Up Information .....................................
Step 3: Update and Upgrade SQL Server ..................
Step 4: Reboot your Computer ..................................
Step 5: Upgrade WinPM.Net ....................................
20
20
21
21
21
Step 6: Run the WinPM.Net Power Quality Aggregation

Service .................................................................... 22
Step 7: Update WebReach Bookmarks (optional) ....... 22
Post Installation Procedures .............................. 22

Check WinPM.Net Services .......................................
Create Local Primary Server Groups .........................
Review WinPM.Net Database Manager .....................
Review Security Highlights ........................................
Enabling WebReach or Web Reporter After Installation
22
22
22
23
23
WinPM.Net 4.0 Commissioning Guide
Introduction
This guide contains information to help you plan, design and build your
WinPM.Net system, incorporating best practices and factory-recommended
procedures to reduce the need for ongoing support and improve the
reliability of your installation.
A typical WinPM.Net system consists of a computer or network of computers
running WinPM.Net software, and one or more networks of devices (such as
basic energy meters, multi-function monitoring/analysis/control devices,
and/or intelligent relays).
NOTE
This WinPM.Net Commissioning Guide is for users who want to prepare and
configure their own WinPM.Net server. Services personnel and fullycommissioned WinPM.Net servers are also available please contact
Siemens Industry for details.
Additional Information
For additional information on installing and commissioning WinPM.Net (for
example, whats new or using the optional OPC Server Assistant), see the
Technical Documentation folder on the WinPM.Net installation DVD.
Types of Installation
The simplest type of WinPM.Net installation is a standalone Primary Server,
where one computer handles all the functions, data storage and interaction
with networked devices.
Primary Server
Each WinPM.Net network has one Primary Server. It
stores the system configuration and serves logged data
to Client computers. The Primary Server can host the
WinPM.Net databases, and typically aggregates data
from all Secondary Servers (if they exist). Terminal
Server connections are supported if your Primary Server
machine is set up with Terminal Services.
DB
Database Server
You can set up the WinPM.Net database using an
existing SQL database in your network (e.g., on a
remote computer hosting Microsoft SQL Server
2005). For this network configuration, you must first
complete the Database Server installation before
installing the WinPM.Net Primary Server on your network.
2009 Siemens Industry. All rights reserved.
DB
Client
For a Client installation, you can specify which
WinPM.Net programs you want to install on the
Client computer. A Client computer connects to the
Primary Server to access network system data for
display, analysis and control functions, as well as
reporting and system configuration. Most or all of the
processing functions occur at the WinPM.Net Client computer, while data
management and access is controlled by the Primary Server.
DB
WinPM.Net Client Licensing

One WinPM.Net Client License is required:
For each computer that accesses the Primary Server to use the WinPM.Net
programs installed on it. This applies to each Terminal Server or Remote
Desktop Connection.
For each WinPM.Net Client computer where the WinPM.Net programs
are installed locally.
Client Types
To determine what type of Client licenses you need, list your WinPM.Net users
or user groups and determine what support is needed for each. WinPM.Net
supports the following client types:
WebReach Client: A thin client that allows you to view preconfigured Vista
display screens through a Microsoft Internet Explorer browser window. No
other programs are needed. WinPM.Net Client Licenses are not required
for WebReach clients.
WinPM.Net Client: A rich client that connects to the Primary Server to
access data, but runs WinPM.Net programs installed on the local client
computer.
Terminal Services Client or Remote Desktop Connection: These clients use
a different computer to connect to the Primary Server. After establishing a
connection, the clients can then use the WinPM.Net programs installed on
the Primary Server.
Secondary Servers
Secondary Server installations are not common,
and are used only in exceptional circumstances.
For example, an intermediary Secondary Server
may be required when you have a large number of
devices that use software-based logging.
Secondary Server installations require advanced
network configuration. Contact Technical Support if you require a Secondary
Server.
DB
Determine Your Network Needs

WinPM.Net is fully scalable, so make allowances for future expansion when
selecting the Primary Server computer. In addition to the different types and
quantities of devices you plan to add to the WinPM.Net network, consider
also the amount of data storage required. For heavy data logging and
retrieval requirements, consider setting up a separate Database Server for
storing WinPM.Net data.
System Requirements
For minimum system requirements, visit www.usa.siemens.com/access.
The server should be equipped with a DVD drive and other standard
hardware, such as an Ethernet communications port.
Consider also a tape backup mechanism and UPS (uninterruptible power
supply) system for your server. Install a high-speed graphics adapter and use
a 17 or larger monitor to view the WinPM.Net interface.
Database Requirements
WinPM.Net requires either SQL Server 2005 Standard Edition or SQL Server
2005 Express.
WinPM.Net can install SQL Server 2005 Express on the Primary Server, and
automatically set up the WinPM.Net databases on that computer. However,
SQL Server 2005 Express has database size limitations (4 GB).
For larger database requirements, you need to set up SQL Server 2005
Standard Edition on the Primary Server or on a separate Database Server that
is optimized for database disk capacity and performance. Install SQL Server
2005 Standard Edition before you install WinPM.Net. See SQL Server
Configuration on page 15.
Secondary Server Requirements

Secondary server hardware and software requirements vary according to
different customer application needs. Contact Technical Support for
assistance when selecting the Secondary server computer.
Prepare the Workstation

The following sections outline considerations when installing WinPM.Net on
a particular operation system (OS) and steps for preparing the workstation
for installation of WinPM.Net.
Server Naming and Partition Guidelines

1.
Assign a computer name for the server.

Select a computer name that conforms to Windows conventions. A
computer name can be up to 15 alphanumeric characters with no blank
spaces and must not contain any prohibited characters or symbols such
as the following:
\*+=|:;<>?,_
For compatibility reasons, use only letters and numbers, assigning a letter
for the first character in the computer name.
2.
Partition the computers hard drive, if required.

Separating the operating system from data storage is a precautionary
step to help preserve data in case the operating system becomes
unstable.
Example
The following example shows how a Primary Server with two physical
hard drives (40 GB, 80 GB) can be partitioned. This serves only as an
example make adjustments to fit your needs:
Partition1, 2
Size
Description
System
(C:\)
15 GB
Contains the operating system and all the Windows system files.
This partition should have enough free space for operating system
upgrades and defragmentation tasks.
Application
(D:\)
25 GB
Contains WinPM.Net programs and other third-party applications.

Since this is not a system partition, you can increase its size when a
new physical drive is added.
Data
(E:\)
80 GB
Contains database files only. Since databases can grow

significantly over time, assign the Data partition to the entire
second physical hard drive.
All partitions are NTFS file system type
If necessary, use Disk Management (in the Computer Management

console) to remap the DVD drive to another drive letter.
Operating System Considerations

The following sections outline considerations and settings that are specific to
a particular operating system.
Server 2003
There are no special considerations or settings for Microsoft Server 2003.
Server 2008
It is recommended that your turn off User Account Control (UAC). Certain
components of WinPM.Net may not function correctly if UAC is left on.
If you plan to use Server 2008 in a distributed system, ensure that Password
protected sharing in Control Panel > Network and Sharing Center is set to
10
OFF on the Primary Server before you install WinPM.Net on a Secondary

Server or Client computer.
To view waveforms in WebReach on Microsoft Server 2008, you must enable
Download signed ActiveX controls, Download unsigned ActiveX controls
and Display Mixed Content in the Local Sites Security Settings in Internet
Explorer.
The WinPM.Net DDE Server does not function because the required NetDDE
service is not a component of Microsoft Server 2008.
Windows XP
If the workstation where you are installing WinPM.Net is part of a workgroup
rather than a domain, Simple File Sharing must be disabled in order for Web
Reporter report pack to be installed. The WinPM.Net Installer gives you the
option to disable Simple File Sharing. If you do not disable Simple File
Sharing, either before you install WinPM.Net or during the installation, you
can disable Simple File Sharing after you install WinPM.Net then upload the
report pack manually.
Windows Vista
It is recommended that you:
Turn off User Account Control (UAC). Certain components of WinPM.Net

may not function correctly if UAC is left on.
Turn off Sleep Mode. WinPM.Net Services may not restart when the
computer comes out of Sleep Mode.
The WinPM.Net DDE Server does not function because the required NetDDE
service is not a component of Microsoft Windows Vista.
Installing WinPM.Net on a Virtual Machine

If you install WinPM.Net on a virtual machine, please note the following
considerations:
Follow the virtualization best practices described by VMware.

The virtual machine, not the host machine, must meet the minimum
system requirements.
WinPM.Net requires network connectivity to communicate with client
machines and devices, and with SQL Server in a distributed system.
Follow the guidelines in Server Naming and Partition Guidelines on
page 10 for partitioning the virtual machines hard drive.
Follow the guidelines in Operating System Considerations on page 10
for the operating system installed on the virtual machine.
To set up a direct serial connection, the host machine must have a
physical serial port that can be dedicated to the virtual machine.
11
WinPM.Net Administrator Server Permissions

The WinPM.Net system administrator (WinPM.Net administrator) is the
person responsible for managing the WinPM.Net system, and therefore
requires certain administrative permissions on the WinPM.Net server. These
Microsoft Windows permissions are typically granted and set up by your IT
(Information Technology) Department. The administrative functions of the
WinPM.Net administrator include:
Install/uninstall software: Install software upgrades and service packs,

repair/modify/reinstall software, update operating system components.
Reboot the WinPM.Net server: A server reboot may be required after
installing or uninstalling Microsoft software or service packs.
SQL Server setup and maintenance: Set up and maintain the SQL Server
instance that hosts the WinPM.Net databases. Tasks include manual
backups, archives, and trims on live or archived ION databases.
NOTE
If the WinPM.Net databases are hosted on a multi-database server, the
database administrator can grant Administrator permissions only for specific
WinPM.Net databases, while restricting access to the other databases on the
server.
12
Start/stop/modify services:
WinPM.Net services (WinPM.Net <service name>) may need to be
stopped or started when commissioning the WinPM.Net server or
performing certain tasks in WinPM.Net. Some tasks that affect or are
affected by WinPM.Net services include: ACCESS meter firmware
upgrades; database creation/modification, database engine
upgrades, manual backup, or password changes; Virtual Processor
global operating parameter modification; adding to/modifying the
Modbus network; and troubleshooting communications.
Start/stop/modify SQL Server services (i.e., SQL Server (ION)) for

problem solving and troubleshooting.
Start/stop/modify other Windows services.
Modify/create/delete WinPM.Net files and folders: Read/write/modify/

remove permissions are required for the WinPM.Net file folders, for tasks
such as creating, customizing, or deleting Vista diagrams or Designer
frameworks.
FTP site upload/download: Install/uninstall troubleshooting tools (files)
from Technical Support. An FTP (file transfer protocol) site is the preferred
method for delivering these files.
Prepare the Primary Server

Depending on how you set up and implement your WinPM.Net network,
certain prerequisites must be met. You must complete the following (if not
already done) before proceeding with the Primary Server installation:
If you want to enable WebReach support, install and enable the Windows
IIS (Internet Information Services) 6.0 or later and ASP.NET components on
the server computer.
If you want to enable Web Reporter, Microsoft SQL Server Reporting
Services must be installed on the Primary Server:
If you are using the SQL Server Express provided with WinPM.Net,
Reporting Services is installed automatically if IIS is installed.
If you are using SQL Server 2005 Standard and want to enable Web
Reporter, install SQL Server Reporting Services before you install
WinPM.Net.
Install and configure the Terminal Server component if Terminal Server

connection to the WinPM.Net Primary Server is required. Refer to the
Terminal Server Licensing Overview topic in your Microsoft Windows
documentation to learn about Terminal Server Licence requirements.
Perform typical setup such as ending a disconnected or stale session and
installing programs.
Configure Remote Desktop Connection if you require remote connection
to the WinPM.Net Primary Server.
If you plan to use TAPI modem drivers for Windows (WinModems) in your
WinPM.Net network, install and configure the WinModems. Additional
WinModem information is available in the WinPM.Net Help.
Use Windows Update service to install the latest security patches and
hotfixes from Microsoft.
NOTE
If you plan to use WinPM.Net with an instance of SQL Server 2005 Express
that you have already installed (not the instance installed by the WinPM.Net
Installer), ensure that SQL Server backwards compatibility components are
installed on that computer.
Firewall Configuration
Use the Microsoft knowledgebase to learn about Well Known Ports and
Registered Ports required for certain networks.
WinPM.Net TCP Port Assignments

The following tables contain the TCP port assignments that WinPM.Net and
associated applications or services use to communicate with ACCESS devices,
WinPM.Net Clients, and other WinPM.Net servers.
13
TCP Ports for Device Communications

Port
Protocol
Port
Protocol
23
Telnet (used for meter diagnostics)
7701
Modbus RTU
25
SMTP (required for email

communications)
7800
EtherGate simultaneously through

available COM ports
502
Modbus TCP
7801
EtherGate through the meters

COM1
3721
Ethernet access for the 3720 ACM

meter
7802

COM2/COM4
7700
ION
7803

COM3
NOTE
Some networks may contain devices that require the use of alternate ports
(e.g., third-party Ethernet gateway devices).
Other Required Ports
Port
13666
Purpose
13670
WinPM.Net services use these ports. These ports are used if a client machine
needs to access the Designer and/or Vista components of WinPM.Net.
13668
This port is used when the WinPM.Net system contains a Secondary Server.
1433
Microsoft SQL Server uses this port.1
1434
Microsoft SQL Monitor uses this port to identify named database instances.
3389
Terminal Server uses this port.
139
NetBIOS and Windows File and Printer Sharing use this port.
80
HTTP (required for WebReach, Web Reporter and Internet access) uses this port.
57777
14
Real-time Data Service uses this port to transfer real-time data to WinPM.Net
clients.2
1
SQL Server uses this port if you use the default instance when you install
WinPM.Net. If you use a named instance when you install WinPM.Net, it is
recommended that you configure the named instance to use port 1433.
You can configure the WinPM.Net Real Time Data Service to use a different
port.
SQL Server Configuration

The following sections outline the required configuration of SQL Server for
complete WinPM.Net installation, including Web Reporter.
NOTE
Make sure the user credentials for the WinPM.Net administrator Windows
account are set up with Administrator permissions for the WinPM.Net
databases, as outlined in WinPM.Net Administrator Server Permissions on
page 12.
SQL Server Reporting Services and WinPM.Net
The Web Reporter component of WinPM.Net requires that Microsoft SQL
Server Reporting Services be installed on the Primary Server. If Reporting
Services is not installed and configured correctly, Web Reporter will not
function.
SQL Server 2005 Standard: If you want Web Reporter functionality,

Reporting Services must be installed on the Primary Server (even if you
have a distributed system with the databases on a database server). Install
the Reporting Services component when installing SQL Server or use Add/
Remove Programs to add Reporting Services to your SQL Server instance.
If Reporting Services is installed on the Primary Server before you install
WinPM.Net, it will be configured by the WinPM.Net Installer.
SQL Server 2005 Express:
New installation of WinPM.Net: SQL Server Reporting Services is
installed and configured with the SQL Server Express that is installed
by the WinPM.Net Installer.
Upgrade of WinPM.Net: Click Upgrade Express during the

installation of WinPM.Net to upgrade to SQL Server 2005 Express
with Advanced Services (including Reporting Services) then continue
with the WinPM.Net installation.
SQL Server 2005 Standard Edition Setup for WinPM.Net

NOTE
The following instructions do not apply to the SQL Server Standard Edition
DVD available from Siemens Industry for WinPM.Net. For instructions on
installing SQL Server using that DVD, refer to the Using the SQL Server DVD
document that came with the product.
Before you make any changes to SQL Server 2005 Standard Edition:
Shut down all services dependent on SQL Server. This includes any service
using ODBC, such as Microsoft Internet Information Services (IIS).
Shut down Microsoft Windows NT Event Viewer and registry viewers.
Remember to restart the services when you are done your configuration.
15
SQL Server 2005 Installation Wizard

The following list outlines which options to select or set up in the various
screens of the SQL Server 2005 Standard Edition installer when installing
SQL Server on a standalone Primary Server:
Components to Install: Select SQL Server Database Services, Reporting

Services and Workstation components, Books Online and development
tools. Click Advanced if you want to change the default installation
location for SQL Server 2005.
NOTE
If you are installing SQL Server 2005 Standard Edition on Windows Server
2008, it is recommended that you change the default installation location.
Otherwise, you may have problems installing SQL Server 2005 SP2 (which is
required for SQL Server 2005 Standard Edition to run on Windows Server
2008).
NOTE
If you change the default location, SQL Server also places a tempdb
database in your chosen location. This database can grow quite large.
Ensure that you have enough space in the new location to accommodate this
database along with the WinPM.Net databases. If necessary, this tempdb
database can be moved at a later date.
Instance Name: Select Named instance and type ION in the box.
Service Account: Select the Customize for each service account
checkbox. Select the first Service type in the Service dropdown list. Select
Use the built-in System account and select Local System from the
dropdown list. Select the second Service type and set it up the same way.
Repeat until all service types are configured to use the local system
account. Ensure the SQL Server Agent is selected in the Start services at
the end of setup section.
Authentication Mode: Select Mixed Mode. Enter a password in the
Enter password and Confirm password boxes (you can use any
password that meets the requirements of your organization and SQL
Server).
Collation Settings: These settings do not affect WinPM.Net; you can leave
the default settings or change them as you require.
Report Server Configuration Options: Select Install the default
configuration. The WinPM.Net Installer will change the Reporting
Services configuration as needed to allow Web Reporter to function.
Error and Usage Report Settings: These settings do not affect WinPM.Net;
you can leave the default settings or change them as you require.
Refer to your SQL Server 2005 documentation for more information.
SQL Server 2005 Standard Configuration

After you install SQL Server 2005, use the SQL Server Surface Area
Configuration Tool to configure SQL Server as follows:
16
Under Surface Area Configuration for Services and Connections, navigate

to Remote Connections > Local and remote connections then select
Using both TCP/IP and named pipes.
Under Surface Area Configuration for Features, do the following:

Navigate to OLE Automation then select Enable OLE Automation.
Navigate to xp_cmdshell then select Enable xp_cmdshell.
Update All SQL Server Instances

Apply the latest SQL Server service pack to all instances of SQL Server 2005
before installing WinPM.Net (WinPM.Net requires at least SQL Server service
pack 2 to function as intended and at least service pack 3 to print Web
Reporter reports on letter-sized paper).
Install or Upgrade WinPM.Net

The following sections outline installing and upgrading WinPM.Net. See
Installing WinPM.Net, below, if you are performing a new installation or
see Upgrading WinPM.Net on page 19 if you are upgrading an existing
installation.
Installing WinPM.Net
Make sure your computer meets the requirements and guidelines outlined in
the system requirements.
Perform the WinPM.Net installation on the local server computer. Remote
installation is not recommended.
The WinPM.Net Installer installs certain Microsoft components. Refer to the
Installer Help for a list of these prerequisite components.
Perform the WinPM.Net installation on the local server computer; remote
installation is not recommended.
Review the Installation Process

Some WinPM.Net components, features or options are dependent on others,
and must be installed in the correct sequence:
1.
Database Server (optional)
2.
Primary Server
3.
Secondary Server and/or Client (optional)
NOTE
During the installation of WinPM.Net, Internet Information Services (IIS)
reboots. Communication with any websites hosted on the computer where
you are installing WinPM.Net will be temporarily disrupted.
Install WinPM.Net Database Server (Optional)

To set up the WinPM.Net databases on a separate server on which you have
installed and configured SQL Server 2005 Standard Edition:
1.
If you have made any configuration changes to the operating system or

SQL Server (i.e., installed a service pack or upgraded), reboot the
computer before you install WinPM.Net.
17
2.
Insert the WinPM.Net DVD in the DVD drive. The auto-start program
begins.
If the autorun dialog does not appear, use Windows Explorer to navigate
to the DVD drive and double-click setup.exe.
3.
Select Run Setup > Install Server > Database Server.
4.
Follow the steps as directed by the installation wizard. If you need more
information regarding any screen in the wizard, click Help.
WinPM.Net installs three databases, creates three login accounts, and adds
numerous stored procedures to the databases attached to the WinPM.Net
SQL Server instance.
A SQL Server login is automatically set up on the database servers SQL
Server instance, named ION by default. This login has sysadmin
permissions to this SQL Server instance only. This login is used by all
WinPM.Net components.
Install WinPM.Net Primary Server

NOTE
If you plan to use the SQL Server 2005 Express that is installed by the
WinPM.Net Installer, make sure the Task Scheduler service is started before
you begin the WinPM.Net installation.
1.

computer before you install WinPM.Net. If you are performing the
primary server installation of a distributed system, ensure the primary
server has network access to the database server.
2.
begins.
3.
Select Run Setup > Install Server > Primary Server.
4.
Follow the steps as directed by the installation wizard. If you need more
information regarding any screen in the wizard, click Help.
Install WinPM.Net Clients (Optional)

NOTE
The WinPM.Net server computer must exist on the Local Area Network (LAN).
Use Windows Explorer to navigate to the WinPM.Net server. Make sure the
WinPMNet fileshare is visible on this server. Ensure File and Printer Sharing
for Microsoft Networks in the LAN properties on the Primary Server is
checked; otherwise the client machine will not be able to access the
WinPMNet fileshare on the primary server.
18
1.
Review the system requirements for client computers and make sure the
client computers meet the requirements.
2.
Follow the same guidelines for computer name and drive partitions, as
indicated in Server Naming and Partition Guidelines on page 10.
3.
Make sure the Primary Servers share folder (WinPMNet) permissions

are set to Full Control for the client username or group.
4.

computer before you install WinPM.Net.
5.
begins.
6.
Select Run Setup > Install Client, then follow steps as directed by the
installation wizard. Select which Primary Server to connect to when
prompted. If you need more information regarding any screen in the
wizard, click Help.
IMPORTANT
WinPM.Net 3.2 and later versions use .NET Remoting (a component of the
Microsoft .NET framework) to exchange real-time data between the server
and client machines. The server and client computers are identified by their
full computer namethe name of the machine with the domain appended
(e.g., MyComputerName.MyCompanyDomainName.com). Contact
Technical Support if you encounter problems displaying real-time data on
your client computers.
Install WinPM.Net Service Packs (if available)

Follow the instructions below to install any available service packs (if
required).
Installing from the DVD

Service packs (if available) are located in the ServicePack folder of your
WinPM.Net installation DVD.
1.
Start Windows Explorer, then select your DVD drive.
2.
Locate and open the ServicePack folder.
3.
Double-click the .exe file of the service pack you want to install.
4.
Follow the directions in the installation wizard.
Download version
Alternatively, you can download service packs from
www.usa.siemens.com/access.
Upgrading WinPM.Net
If you are performing a new installation, see Installing WinPM.Net on
page 17.
During the upgrade, the WinPM.Net 4.0 Installer creates the new installation
folder hierarchy, then copies and pastes all the configuration files and
customizations from the previous version. The installer then installs all the
new software components and files, without overwriting the custom files that
were copied from the previous version.
19
For diagnostic purposes, all registry entries from previous WinPM.Net

versions are preserved after the upgrade the setup log file contains a list
of registry settings that were copied from the previous version. All custom
registry settings are applied to the new installation. Custom Virtual Processor
and Log Inserter services are also preserved.
NOTE
Depending on the size of your database and the number of devices in your
network, it can take a significant amount of time to update the WinPM.Net
databases after the upgrade. During this time, data presented in WinPM.Net
will be incomplete.
Recommended Upgrade Scenarios

The instructions in the following sections apply to these upgrade scenarios:
Upgrading from WinPM.Net 3.2 Service Pack 3 (using either SQL Server
2005 Standard or Express) to WinPM.Net 4.0 on the same computer. If
you want to upgrade from WinPM.Net 3.2, WinPM.Net 3.2 Service Pack 1
or WinPM.Net 3.2 Service Pack 2, first upgrade to WinPM.Net 3.2 Service
Pack 3 then follow the instructions in the following sections.
Upgrading from WinPM.Net 3.1 Service Pack 2 (using SQL Server 2005
Standard or Express, or MSDE (Microsoft Data Engine)) on the same
computer.
For any other upgrade scenarios (such as upgrading from WinPM.Net 3.1
Service Pack 2 using SQL Server 2000, upgrading from a version of
WinPM.Net not listed, or performing an upgrade by migrating to a new
server), contact Technical Support before performing the upgrade.
To determine the version of WinPM.Net that you have installed, select Help
> About in Management Console.
Step 1: Upgrade System Hardware and Software

Before you upgrade, make sure that the minimum hardware and software
requirements for running WinPM.Net are still met, and upgrade your system
if necessary.
Step 2: Back Up Information

Before upgrading, back up the ..\config and ..\Database folders in your
WinPM.Net directory (e.g., copy them to another folder on your network or
to a removable storage device). To copy the ..\Database folder, you must first
stop SQL Server services related to WinPM.Net (i.e., SQL Server (ION)).
Backup any custom Windows Registry settings you have made in relation to
WinPM.Net since these may not be preserved during the upgrade.
If you are upgrading from MSDE (Microsoft Data Engine) to SQL Server 2005
Express with Advanced Services, make note of any changes you have made
to the scheduled tasks in Database Manager for the WinPM.Net databases
these changes are not preserved during the upgrade. After you finish
upgrading WinPM.Net, you will need to re-enter those changes to the
scheduled tasks in Database Manager.
20
You can save your custom shortcuts from a previous WinPM.Net installation.
Custom arguments can be used for automatic logon or to open a specific
Vista diagram upon startup. Copy the custom shortcuts to a safe location
before upgrading. Then after the upgrade, you can copy them back.
Step 3: Update and Upgrade SQL Server

Update All SQL Server 2005 Standard Edition Instances
Apply the latest SQL Server service pack from Microsoft to all instances of SQL
Server in your network before upgrading WinPM.Net (WinPM.Net requires at
least SQL Server service pack 2 to function as intended and at least service
pack 3 to print Web Reporter reports on letter-sized paper).
Upgrade SQL Server 2005 Express

To upgrade from SQL Server 2005 Express or MSDE (Microsoft Data Engine)
to SQL Server 2005 Express with Advanced Services Service Pack 3 (including
Reporting Services, required for Web Reporter), click Upgrade Express on the
Select the Installation Type screen of the WinPM.Net Installer before you
upgrade WinPM.Net.
NOTE
Do not click Cancel during the SQL Server 2005 upgrade process. This can
cause problems with the installation that will require the assistance of
Technical Support to resolve.
Step 4: Reboot your Computer

If you have made any configuration changes to the operating system or SQL
Server (i.e., installed a service pack or upgraded), reboot your computer
before you upgrade WinPM.Net.
Step 5: Upgrade WinPM.Net

After you have performed the tasks in the previous sections, click Upgrade on
the Select the Installation Type screen of the WinPM.Net Installer to upgrade
WinPM.Net.
If you need more information regarding any screen in the wizard, click Help.
NOTE
If you are using a Database Server, upgrade it before you upgrade the
Primary Server. If you are using a Secondary Server or Client computer,
upgrade these after you upgrade the Primary Server.
21
Step 6: Run the WinPM.Net Power Quality Aggregation Service

In order to generate Power Quality reports in Web Reporter on power quality
data collected prior to the upgrade, you need to manually run the WinPM.Net
Power Quality Aggregation Service on the pre-existing data.
For instructions on running this service manually, see the Running the
WinPM.Net Power Quality Aggregation Service Manually topic in the Web
Reporter section of the WinPM.Net Help.
Step 7: Update WebReach Bookmarks (optional)

If you have bookmarks to WebReach on a computer other than the Primary
Server, you need to update the bookmarks to point to
http://ComputerName/Web rather than http://ComputerName/ION (where
ComputerName is the servers computer name or IP address).
Post Installation Procedures

Perform the following procedures after you install WinPM.Net.
Check WinPM.Net Services

Open the Windows Services dialog and ensure that all the necessary
WinPM.Net services are started. See The WinPM.Net Services topic in the
WinPM.Net Help for more information.
Create Local Primary Server Groups

Create the following Microsoft Windows local user groups on the WinPM.Net
Primary Server and grant access as follows:
Access to
WinPM.Net\SYSTEM
Group Name
Access to
WinPM.Net\CONFIG
WinPM.Net_Administrators
Full Control
Full Control
WinPM.Net_Users
Read
Change
NOTE
The LocalSystem account must belong to the WinPM.Net Administrators
group; the LocalSystem account requires read/write access to the system and
config directories in order to run the WinPM.Net services.
Review WinPM.Net Database Manager

Database Manager has preconfigured schedules for performing archives
(disabled by default), backups, and trims on your WinPM.Net databases.
Review these schedules and make any modifications that you require. You
can also configure alarming to notify you when you are reaching your
database or hard disk space limits. Refer to the Database Manager section
in the online WinPM.Net Help for more information.
22
Review Security Highlights

This section outlines specific security considerations after the WinPM.Net
installation.
Default passwords for SQL Server

The default user identification and password for some of the database
accounts need to be preserved for the proper operation of WinPM.Net.
Contact Technical Support for details before you attempt to modify user IDs
and passwords.
NTFS and Share permissions on the WinPM.Net directory

All share permissions are automatically set to Read permissions for the
Everyone group; this includes the WinPM.Net share (WinPMNet).
Change the WinPMNet share permission to Read/Write for users (WinPM.Net
Clients) who need to modify files, such as Vista diagrams.
WinPM.Net software security

Two software user accounts are created by default when WinPM.Net is first
installed: guest and supervisor. The default password is 0 (zero) for
both users. These accounts have an access level of Supervisor (the highest
level with full access). The WinPM.Net administrator should use User
Manager to delete these accounts or change the password for both accounts
before deploying the WinPM.Net system to users.
Refer to the Management Console Tools > User Manager section of the
online WinPM.Net Help for more information.
WinPM.Net services
WinPM.Net services run under the Local System account, by default. You can
change the Log On As attribute of a service by specifying the account and
password. This is done from the Log On tab when viewing the properties of
that service. The Log On As account must have read/write permissions in
the WinPM.Net network.
Restrict WebReach /ION virtual root access (optional)

If you do not want users to be able to access WebReach without
authentication, you can restrict access to the /ION virtual root to the primary
server only. For more information, contact Technical Support.
Enabling WebReach or Web Reporter After Installation

WebReach
WebReach is automatically installed if the WinPM.Net Installer detects IIS on
the computer. If you want to install WebReach after the primary installation
of WinPM.Net, see the WebReach section of the online WinPM.Net Help for
information.
Web Reporter
Web Reporter is automatically installed and Microsoft SQL Server Reporting
Services is configured by the WinPM.Net Installer if it detects Reporting
23
Services on the Primary Server. If you want to configure Web Reporter after
the primary installation of WinPM.Net:
1.
24
Use Add or Remove Programs and your SQL Server installation media
to add Reporting Services to the Microsoft SQL Server installation (IIS
needs to be installed before you can install Reporting Services).
2.
Reboot the computer.
3.
Select WinPM.Net in Add or Remove Programs, click Change, select

Modify in the WinPM.Net Installer, then click Next. Reporting Services is
configured and the default report packs are installed.
www.usa.siemens.com
Contact the Industry Automation and Drive Technologies
Service and Support at:
Operating hours: 8.00 am5.00 pm EST MondayFriday
Phone: 1-800-333-7421
http://www.siemens.com/automation/support-request
Siemens Industry, Inc.
Building Technologies Division
5400 Triangle Parkway
Norcross, GA 30092
Siemens Industry, Inc.
Siemens is a registered trademark of
Siemens AG. Specifications are subject to
change without notice.
For Nearest Sales Office

1.800.964.4114
www.usa.siemens.com
sales/salesoffices.html
For More Information Visit
Windows is a trademark and

Microsoft is a registered trademark
of Microsoft Corporation.
All others are of Siemens AG.
Order No. 70005-0299-00

PDF 12/2009 Printed in the U.S.A.
www.usa.siemens.com/access

WinPM Net Commissioning Guide

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

WinPM Net Commissioning Guide

Hochgeladen von

Copyright:

Verfügbare Formate

WinPM.Net 4.

Primary Server ...........................................................

Your Network Needs .............................. 9

System Requirements .................................................. 9

Prepare the Workstation ................................... 9

Naming and Partition Guidelines ................ 10

System Considerations ......................... 10

Server 2003 ............................................................

Administrator Server Permissions ........ 12

the Primary Server ................................... 13

SQL Server Configuration ............................... 14

Install or Upgrade WinPM.Net ........................ 17

Install WinPM.Net Database Server (Optional) ...........

Step 1: Upgrade System Hardware and Software .......

Step 6: Run the WinPM.Net Power Quality Aggregation

Post Installation Procedures .............................. 22

WinPM.Net 4.0 Commissioning Guide

2009 Siemens Industry. All rights reserved.

WinPM.Net 4.0 Commissioning Guide

WinPM.Net Client Licensing

2009 Siemens Industry. All rights reserved.

WinPM.Net 4.0 Commissioning Guide

Determine Your Network Needs

Secondary Server Requirements

Prepare the Workstation

2009 Siemens Industry. All rights reserved.

WinPM.Net 4.0 Commissioning Guide

Server Naming and Partition Guidelines

Assign a computer name for the server.

Partition the computers hard drive, if required.

Contains WinPM.Net programs and other third-party applications.

Contains database files only. Since databases can grow

All partitions are NTFS file system type

If necessary, use Disk Management (in the Computer Management

Operating System Considerations

2009 Siemens Industry. All rights reserved.

WinPM.Net 4.0 Commissioning Guide

OFF on the Primary Server before you install WinPM.Net on a Secondary

Turn off User Account Control (UAC). Certain components of WinPM.Net

Installing WinPM.Net on a Virtual Machine

Follow the virtualization best practices described by VMware.

2009 Siemens Industry. All rights reserved.

WinPM.Net 4.0 Commissioning Guide

WinPM.Net Administrator Server Permissions

Install/uninstall software: Install software upgrades and service packs,

Start/stop/modify SQL Server services (i.e., SQL Server (ION)) for

Start/stop/modify other Windows services.

Modify/create/delete WinPM.Net files and folders: Read/write/modify/

2009 Siemens Industry. All rights reserved.

WinPM.Net 4.0 Commissioning Guide

Prepare the Primary Server

Install and configure the Terminal Server component if Terminal Server

WinPM.Net TCP Port Assignments

2009 Siemens Industry. All rights reserved.

WinPM.Net 4.0 Commissioning Guide

TCP Ports for Device Communications

Telnet (used for meter diagnostics)

SMTP (required for email

EtherGate simultaneously through

EtherGate through the meters

Ethernet access for the 3720 ACM

EtherGate through the meters

EtherGate through the meters

Microsoft SQL Server uses this port.1