ProcessHistorianPRHIenUS en US
ProcessHistorianPRHIenUS en US
ProcessHistorianPRHIenUS en US
Hardware configuration 2
Administration 3
SIMATIC
Redundant system 4
Process Historian 2014
Process Historian Administration 5
Migration
Connectivity 6
System Manual
Appendix 8
09/2014
A5E32988004-AA
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
Danger
indicates that death or severe personal injury will result if proper precautions are not taken.
Warning
indicates that death or severe personal injury may result if proper precautions are not taken.
Caution
indicates that minor personal injury can result if proper precautions are not taken.
Notice
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be
used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property
damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
Warning
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance
are required to ensure that the products operate safely and without any problems. The permissible ambient
conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in
this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
1 Basics...........................................................................................................................................................5
1.1 Overview..................................................................................................................................5
1.2 Data structures.........................................................................................................................9
1.3 Segmentation.........................................................................................................................11
2 Hardware configuration..............................................................................................................................15
3 Administration.............................................................................................................................................19
3.1 Administration - overview.......................................................................................................19
3.2 Process Historian Management dashboard...........................................................................21
3.3 Plant structure dashboard......................................................................................................23
3.4 I/O Systems dashboard..........................................................................................................25
3.5 Diagnostics dashboard...........................................................................................................27
3.6 Backup/Restore dashboard....................................................................................................28
3.6.1 Introduction............................................................................................................................28
3.6.2 Creating segment backups....................................................................................................29
3.6.3 Restoring a segment..............................................................................................................31
3.6.4 Deleting a segment................................................................................................................32
3.7 Compression dashboard........................................................................................................33
3.8 Segmentation dashboard.......................................................................................................34
3.9 Dashboard redundancy..........................................................................................................37
3.10 Licensing dashboard..............................................................................................................39
3.11 Database backup dashboard.................................................................................................40
4 Redundant system......................................................................................................................................45
4.1 Redundant system.................................................................................................................45
4.2 Redundancy scenarios...........................................................................................................47
4.3 Configuring Process Historian Redundancy Service.............................................................51
4.4 Setting up Process Historian redundancy..............................................................................52
5 Migration.....................................................................................................................................................55
5.1 Overview................................................................................................................................55
5.2 Migrating................................................................................................................................57
5.2.1 CAS project online.................................................................................................................57
5.2.2 CAS project backup...............................................................................................................62
5.2.3 WinCC project online.............................................................................................................66
5.2.4 WinCC project backup...........................................................................................................70
5.2.5 Process Historian project online.............................................................................................75
6 Connectivity................................................................................................................................................81
6.1 Optimized data transmission..................................................................................................81
6.2 Process Historian OPC-UA-Server........................................................................................83
6.2.1 PH OPC UA server - Overview..............................................................................................83
6.2.2 Installing the PH OPC UA server...........................................................................................84
6.2.3 Security concept of OPC UA..................................................................................................85
6.2.4 Configuring the security mechanisms....................................................................................89
6.2.5 Supported OPC UA services and profiles..............................................................................92
6.2.6 Configuration file....................................................................................................................93
6.2.7 How to configure the OPC UA server....................................................................................94
6.2.8 Information model of PH OPC UA server...............................................................................97
7 Process control messages.........................................................................................................................99
8 Appendix...................................................................................................................................................101
8.1 Database installation wizard................................................................................................101
8.1.1 Memory requirement............................................................................................................101
8.1.2 Creating a Process Historian database................................................................................103
8.1.3 Creating the Process Historian database in advanced mode..............................................110
8.1.4 Recovering a Process Historian database...........................................................................117
8.2 Segments Basics.................................................................................................................122
8.3 Aggregation..........................................................................................................................125
8.4 Firewall settings...................................................................................................................127
8.5 Integrating Process Historian in a domain...........................................................................128
Index.........................................................................................................................................................139
Introduction
SIMATIC Process Historian is a central archiving system for storing process data, such as
process values and alarms.
The Process Historian uses Microsoft SQL Server 2008 R2 SP1 64 Bit. The Process Historian
archives historical data originating from an PCS 7 operator station (OS) or a WinCC OS or
from SIMATIC BATCH. The data can belong to different PCS 7 or WinCC projects. Access to
the historical data is transparent for the OS clients.
Services
Process Historian employs four services for processing, storing and backing up data:
● SIMATIC Process Historian Server
This service implements all functions the server needs to process and store data.
● Process Historian Maintenance Service
This service implements all functions that are necessary to maintain the Process Historian
database. The Maintenance Service handles tasks such as starting mirroring, mirror
monitoring, restore functions, maintenance of the transaction log and suchlike.
● Process Historian Redundancy Service
This service implements functions that are necessary for data exchange between two
redundant server systems.
● Process Historian Discovery Service
This service supports the search for connected Process Historian systems. The Discovery
Service is essential for the functionality of the Process Historian.
Operating states
You can give the Process Historian the following commands by using the shortcut menu of the
icon in the system tray (information area):
● Start
● Shut down
● Start recovery
Notice
Disabling the Process Historian server before shutting down
You must disable the Process Historian server before shutting down the computer on which
the Process Historian server is running. There are two options available to you:
- In the start screen of the Process Historian Management Console, select the status "Shut
down".
- In the shortcut menu of the system tray of the Process Historian, select the "Shut down"
command.
The "Inactive" status is displayed.
Error The "Error" operating state occurs when an error has been
recognized or when no connection to the SIMATIC Proc‐
ess Historian service exists.
Inactive No data is archived in the "Inactive" operating state. In this
operating state, you can carry out updates, maintenance
work to the Process Historian PC or a restart of the PC.
Notice
Avoiding the "Locked" state
To ensure enough free space is available for the operation of the Process Historian, regularly
check the currently available space in the "I/O systems" dashboard.
Determine which automatic mechanisms for reducing the used space can be activated in the
dashboards.
Space monitoring
PH-Ready or the "Store & Forward" function on the OS monitors the space on the system drive
where the cache is located.
On the Process Historian server the maintenance service monitors the disk space on the
following drives:
● System drive
● Drive where the transaction log is located
● All data drives on which the Process Historian database or database segments are located
A warning is sent to WinCC if the following occurs:
● The free space falls below the limit of 100 GB and is less than 20 % of the drive capacity.
The Process Historian server switches to the "Locked" state when the following occurs:
● The free space falls below the limit of 50 GB and is less than 10 % of the drive capacity.
– Hard drive up to 500 GB: Free space < 10 %
– Hard drive larger than 500 GB: Free space < 50 GB
See also
Redundant system (Page 45)
Value sequences
The Process Historian stores each value sequence to be archived and its individual values at
certain points in time with a unique identifier (GUID). The physical location of the individual
values is determined with this identifier. This provides the user with easy access to the values.
To improve performance when archiving a large number of process values and alarms, the
value sequences in the Process Historian can be divided into data groups.
Each data group is assigned a storage location on a shared cluster of physical sources.
● Data group 1 on drive partition 1
● Data group 2 on drive partition 2
● etc.
Note
You can distribute the data groups among the available hard disks in order to influence the
performance and the scaling of the system used. Distribution is carried out using the Wizard
when creating the database.
Partition
The amount of runtime data of a single value sequence to be archived, such as an archive
tag, for example, is not limited and constantly increases.
The entire amount of data that is assigned to an individual value sequence must therefore be
divided into several "partitions" using the time axis.
Data groups are divided into partitions using the time axis.
The following conditions apply to partitions:
● Each partition has a high and low limit for the time period.
● but the high time limit must always be higher than the low one.
● The partitions of a data group should not overlap.
7LPHD[LVW
$UFKLYHWDJ
$UFKLYHWDJ 3 3DUWLWLRQ 3 3 3 3WQ
$UFKLYHWDJP 3 3 3 3 3 3 3 3WQ
6HJPHQW
A database segment consists of the sum of partitions of all data groups that share the same
high and low time limits. These groups correspond to the limits of the segment.
The difference between the high and low time limit is referred to as "time period" of the database
segment.
Each segment has a unique segment number.
● The start segment, the first segment created in a system, has the number 100,000.
● The segment whose low limit is equal to the high limit of segment n is referred to as segment
"n+1".
● The segment whose high limit is equal to the low limit of segment n is referred to as segment
"n-1".
1.3 Segmentation
Introduction
A Process Historian database can process and manage very large volumes of data. The saved
data is split up into segments so that performance is not impaired.
Segments are defined by a time period with a high and low time limit. A segment contains the
amount of data that was recorded during the defined time period.
By default, segments are created with a segment size of one week when the Process Historian
database is created. You can change this setting. You can find information on changing
segment configurations under 'Segmentation dashboard (Page 34)'.
The configuration of segments that contain data cannot be changed later.
Note
All settings can be set by adjusting the segmentation during the installation of the database.
The selection of the segment unit affects the required hard disk space.
The segment size is extrapolated proportionally to the estimated load of the data values
according to the user-defined settings.
Segmentation configuration
You can change the properties of segmentation on the "Segmentation" dashboard as
Process Historian administrator.
You can make the following settings:
● Anchor point of segmentation
● Time period of a segment
● Number of prepared segments
● Total number of runtime segments
The following table provides an overview of the basic segmentation parameters:
The Process Historian continuously creates segments with the defined time period. To ensure
that the entire period of possible times is covered, there is a high and a low "Catch-all" segment.
These special segments collect all incoming data that lies outside the current runtime segment.
These segments are called "Catch-all-upper" (CAU) and "Catch-all-lower" (CAL). The CAL
and CAU segments are permanently available and cannot be deleted, removed or set offline.
Anchor point
When you change the anchor point, it should refer to a time at or after the last time stamp of
all segments.
The anchor point of the segmentation does not have to be changed if the number of prepared
segments or the total number of runtime segments is to be changed. Any existing segments
are not deleted when the settings are changed (e.g. reducing the prepared segments).
This means the new settings are not reached when you reduce the prepared signals until the
surplus and prepared segments have been used.
If the number of prepared signals is increased, a segmentation with the new settings is initiated
immediately.
Note
If the last segment of the existing segmentation configuration ends before the anchor point of
the new segmentation, an intermediate segment must be created. This intermediate segment
starts with the end time of the last segment of the existing segmentation configuration and
ends with the start time of the new segmentation configuration. A suitable anchor point is
suggested to avoid the need for an intermediate segment. If you reject this suggestion, an
intermediate segment is created automatically.
Segments: Types
In the Process Historian, there is a difference between segments of the "Runtime" and
"Archive" types.
Runtime segments are displayed on the "Segmentation" dashboard. They have the following
properties:
Archive segments are displayed on the "Backup/Restore" dashboard. These are compressed
or uncompressed, depending on the setting.
The status of a segment is classified as "Online" or "Offline".
● Segments of the "Runtime" type always have the status "Online".
● Segments of the "Archive" type can have the status "Online" or the status "Offline".
You can only read the contents of segments that are online. In order to read the contents of
segments that are offline, you have to restore these segments.
Note
Information about restoring a segment is available under 'Restoring a segment (Page 31)'.
Segments: Status
The properties of segments are structured as follows:
Internet
Front-End Firewall
Office LAN
Process Historian
Information Server
Terminalbus
Hardware equipment
This configuration allows you to expand RAM, as well as the number of processors and HDDs.
The hardware configuration described is based on the use of internal hard disks for:
● Operating system, SQL server
● Process Historian database
● Transaction log
You can expand the scale in regard to database size and performance by using a
Storage Area Network (SAN).
You can also increase the performance by creating and distributing the database to several
symmetrical database groups on separate hardware RAID systems.
Note
Opening the Process Historian Management Console
In Internet Explorer under "Internet Options > Advanced > Security", deactivate the option
"Check for publisher's certificate revocation".
If this option is activated, it can slow down opening of the Process Historian and cause error
messages.
Dashboards - Overview
The following table shows the dashboards of the Management Console and their tasks:
Dashboard Description
Process Historian Manage‐ ● Display of fundamental hardware indicators and performance
ment indicators for the PC and operating system
● Display of basic indicators for the status and current activity of the
Process Historian server
● Display of the license status
● Redundancy status
● Changing the operating state
Plant structure ● Display of incorporated projects
● Display of the OS server systems
● Display of the PC name
I/O Systems ● Display of the available input and output devices
● Display of the memory space used
● Detailed information about the load
Diagnostics ● Diagnostic messages of the Process Historian
● Messages from the event display of the operating system
Backup/Restore ● Display of the segments of the "Runtime" type
● Display of the segments of the "Archive" type
● Creating segment backups
● Restoring backed-up segments
Dashboard Description
Compression ● Display of the compression state
● Configuration of the number of uncompressed archive segments
Segmentation ● Display of the current segmentation setting
● Changing the segmentation settings
Database backup ● Manual creation of full database backups
● Automatic (cyclic) creation of full database backups
Redundancy ● Display of the redundancy status
● Switchover / disconnection of principal (master) and mirror (standby)
● Redundancy configuration
Licensing ● Display of the current license status of server and project
Note
Process Historian does not archive data
If the Process Historian does not archive data, check the Microsoft Message Queueing
(MSMQ) and the databases.
Overview
The "Process Historian Management" dashboard includes information about:
● Basic indicators for monitoring the PC:
– Processor load (CPU)
– Available RAM
– Hard disk load (Disk I/O)
● Basic indicators on Process Historian:
– Number of connected data sources
– Stored tags per second
– Stored messages per second
● Operating state of the Process Historian server
● Redundancy status of the Process Historian
● Licensing status of the Process Historian
● Automatic backup Process Historian
Note
Display in percent
Percentage values displayed can exceed 100 % for a short time. These values are determined
by a statistical extrapolation from mean values. They do not correspond to the real values.
Status control
SQL-Server
WinCC
You can manually add, edit or remove the following expanded structure:
● Company Unternehmen
● Location
Standort
● Building
● Corridor Gebäude
● Room Flur
● PCS 7 Raum
PCS7
Merge
You use this functionality in case there are duplicate project entries in the structure tree.
Duplicate entries can be caused, for example, when an image of the OS server was installed
again after a hardware fault.
You use the 'Merge' function to combine the duplicate entries so that they from a single entry
again in the plant structure.
The "I/O Systems" dashboard displays the following information on the storage system:
● Name and drive letter of the hard drives
● File system
● Total storage space: Capacity
● Absolute available storage space
● Free storage space in percent
● Absolute storage space used
The states of the input and output devices are graphically monitored by the system. If you
select a drive, you receive the following detailed information on the selected drive:
● Idle time of the hard drive: Idle time
● Average duration per transfer
● Average length of queue for read access
● Byte per second with read access to data medium
● Average length of queue for write access
The upper area of the "Diagnostics" dashboard displays the last 1000 diagnostic messages
from the Process Historian event log.
The event log of the Process Historian contains the following information:
● Log entry ID
● Severity of the message
● Time stamp
● Name of application domain
● Process ID
● Message
The lower section of the dashboard includes the last 100 entries from the event log for Windows
applications. The following information is displayed:
● Time stamp
● Message
● Category
● Source
3.6.1 Introduction
Backup types
The Process Historian saves process values and alarms in segments. You back up the
contents of the Process Historian database by segment.
When an archive segment is backed up, the runtime data is stored in the backup file. The
stored data includes:
● Process values
● Messages
● Configuration data
You can plan the backup of data using the "Settings ..." button in the "Archive segments" area
of the 'Backup/Restore' dashboard.
You can make selected archive segments available as runtime data once again by using the
"Restore ..." button in the 'Restore segments' area.
Requirement
The segment to be backed up has the "Archive" status.
Backup planning
The storage space of the Process Historian is continuously filled with data. If the free space
falls below a threshold, the Process Historian is set to the "locked" state. Archiving is then
paused.
To put the Process Historian back into the "Enabled" state, you must make sufficient free
space available.
You have the following options for avoiding the "Locked" state:
● Backup segments manually and set them offline.
● Backup segments automatically and set them offline.
Note
Operating state during the segment backup
While the following functions are being performed, the Process Historian briefly changes to
the "Disabled" operating state for a short time:
● During the preparation of a segment
● During the backup of a segment
● During the restoration of a segment
● When the segment is set offline
You have no access to the database in this operating state.
Segment backup
Manual backup
1. Select the "Backup/Restore" dashboard in the navigation of the Management Console.
2. Select segment to be backed up in the "Archive segments" area.
3. Click the "Backup" button to launch backup.
4. Select the path for the backup file in the "Backup segment" dialog box that opens.
You can specify further identifiers and descriptions for the backup such as the name or
number of the data medium.
To set segments automatically offline after they are saved, select "Set offline".
5. Click "Backup".
Automated backup
In the "Backup/Restore" dashboard you can restore the backup and have the archive segments
set offline automatically.
To do this, select the option "Set segment offline after backup" via the "Settings" button in the
"Archive segments" area.
You can enable automatic backup by setting the "Planner is activated" option .
Delayed segments
Archive segments that are set offline with a delay if the option "Set segment offline after backup"
is set. The delayed segments remain available online.
In the counter, set the number of delayed segments to remain available online.
Note
Checking the storage space
To ensure enough free space for the Process Historian in operation, repeat these steps
regularly.
Result
A backup is created and the date of the backup entered.
The segment remains in the "Online" status and is not moved.
Requirement
● The corresponding backup file for the segment to be restored is available.
● The Process Historian is in the "Active" operating state.
Procedure
1. Select the "Backup/Restore" dashboard in the navigation of the management console.
2. Select the required segment in the "Restore segments" area.
3. Click on the "Restore" button.
4. In the "Backup segment" dialog, select the corresponding backup file for the segment that
is to be restored.
5. Click "Restore".
Result
You can access the data of the restored segment from the OS Server, OS Client or the
Information Server.
Requirement
You can only use the "Set offline" button if a backup of the selected segment has already been
created and this segment is marked as "valid". A segment is, for example, marked as "invalid"
if additional runtime data for the segment has accumulated after the creation of a backup. In
this case, create a backup of the relevant segment again.
Segments can only be deleted individually.
Procedure
1. Select the "Backup/Restore" dashboard in the navigation of the management console.
2. Select the segment you want to delete in the "Archive segments" area.
3. Click the "Set offline" button.
Result
The segment is deleted from the database.
Note
The archive segments are compressed automatically in the background.
Procedure
1. Select the "Compression" dashboard in the navigation of the management console.
2. Select the "Activate" option in the 'Configuration' area for 'Post compression'.
3. Specify the number of uncompressed segments you want to keep in the "Configuration"
area.
4. Click "Apply".
5. The "Current status" area indicates whether compression is enabled and, if so, as of which
segment.
Result
The settings for the compression of archive segments have been reconfigured.
You specify the following parameters for configuration of the segmentation in the "Settings"
area:
1. Segmentation anchor point:
– Hour
– Date
2. Time period for segments:
– Unit (period)
– Factor
3. Number of segments:
– Number of future segments
– Total number of runtime segments
The "Database Installation Wizard" supports you in the installation of the Process Historian
database. By default, the following presettings are made for the segmentation during
installation:
Note
Process Historian Installation Notes
Additional information on defaults of the Process Historian database is available in the
Installation Notes.
Depending on the quantity structure, the amount of data per segment can be very large. This
applies to all segments in runtime. When the segments are created, the estimated required
memory space is reserved for future segments.
If segments in the past are created, minimal space is allocated.
The optimum settings for the segmentation are a compromise between the memory space
used and the number of uncompressed data segments to be reserved.
Note
The Process Historian database is switched automatically to the "Deactivated" state to allow
changes to the segmentation to be carried out. After the settings have been accepted, the
database changes back to the "Active" state automatically.
Procedure
1. Select the "Segmentation" dashboard in the navigation of the Management Console.
2. In the "Number of segments" area, select the required number of segments to be prepared
continuously.
3. In the "Number of segments" area, select the required total number of runtime segments.
4. Click "Apply".
Result
The segmentation of the Process Historian database is configured.
To create a new redundant system, click the "Start redundancy configuration..." button in the
'Redundancy' area.
Follow the instructions of the "Process Historian Redundancy Wizard" to configure a new
redundant system.
Note
Process Historian Redundancy Wizard
You will find detailed information on redundancy configuration in the Process Historian
Installation Notes.
Note
Redundancy
More information on redundant systems can be found in the section 'Redundant system
(Page 45)'.
Dashboard
The "Licensing" dashboard gives you an overview of the licenses used and available in the
system.
The availability of the Process Historian licenses is displayed.
You also obtain detailed information about the states of the tag licenses:
● Available
● Required
● Free
The Process Historian does not require any archive tag licenses for the PCS 7/ WinCC sources.
When you select a project, you receive information on the project-specific license status with
the following information:
● Project name
● Project type
● Number of tags
Database backup
The "Current configuration and current status" displays the following information:
1. Configured backup type
2. Backup status: Progress of the backup copy:
3. Path to backup copies
4. Free disk space
5. Status
Settings
Three settings are available in the "Settings" area:
Storage types
Only one backup is defined with the "Manual" setting. Once the backup is complete
(status = 100%), the operation is terminated. A recovery from this backup restores the
database with data from the backup timestamp.
A full backup with the current timestamp is created with the "Automatic" setting. In addition,
the backup is repeated cyclically. The timestamp is updated with each backup. The backups
no longer needed are deleted. A backup always represents the current state of the database.
A recovery from this backup restores the database with the latest data from the backup
timestamp. The process is continued.
Storage path
The destination path for the backup is specified in the "Settings" window. The destination path
can be changed manually.
Storage structure
The structure of the storage depends on whether the backup type is set to "Automatic" or
"Manual".
Storage device
We recommend you store the database backup on a separate drive.
The following external drives can be used as a storage medium for database backups:
● USB hard disk
● Network drive via ISCSI. You can find information about ISCSI from Microsoft at:
– http://technet.microsoft.com/de-de/library/ee338476(v=ws.10).aspx (http://
technet.microsoft.com/de-de/library/ee338476(v=ws.10).aspx)
● Network shares using UNC paths: ( "\\<Server>\<Share>" ).
To do this, one of the following steps must be carried out:
– Share for full access must be configured for all users.
– The Historian SQL Server service must be running under a domain user with appropriate
rights.
Consult your network administrator about this.
Sufficient free space must be available on the selected storage medium in order to perform a
full backup.
Note
Required space
If less than 20 GB are free on the drive, a warning is displayed on the control system.
If less than 10 GB are free on the drive, a process control message is generated and the
creation of the backup is stopped.
Incomplete backups
If the backup type is changed during the creation of the backup, incomplete backups cannot
be resumed. Incomplete backups are unsuitable for recovery.
Redundant system
The "Database backup" function are used to save the entire database in the form of a backup.
In a redundant system, the mirror takes over this task.
The "Database backup" function is not possible in a redundant system.
Recovery
Recovery restores the state of the Process Historian that existed at the time the last backup
was started.
You import the recovery with Database Installation Wizard. Select the desired backup and start
the recovery.
Before the recovery process is started, the backup will be checked for completeness. The
recovery is only started when the backup is complete, i.e. the backup status is 100 %.
You can learn about the detailed steps for recovery in the section "Database Installation
Wizard (Page 117)".
See also
http://technet.microsoft.com/de-de/library/ee338476(v=ws.10).aspx (http://
technet.microsoft.com/de-de/library/ee338476(v=ws.10).aspx)
Redundancy
The redundant systems are based on Microsoft SQL Server mirroring.
Process Historian requires a third system to monitor the availability of redundancy: the Witness.
You can assign the Information Server the role of the 'Witness'.
Terminal bus
≥ 1 Gbit
Direct connection
Setting up redundancy
You start the Redundancy Wizard using the "Redundancy" dashboard of the Process Historian
Management Console.
You can find additional information in the section 'Dashboard redundancy (Page 37)' as well
as in the Installation Notes for the Process Historian describing how to set up redundancy.
Note
Providing sufficient disk space
To avoid data loss due to a lack of space, ensure sufficient disk space:
● Regularly check the current disk space in the "I/O systems" dashboard.
● Determine which automatic mechanisms for reducing the used space can be activated in
the dashboards.
See also
Dashboard redundancy (Page 37)
Overview (Page 5)
Short designations
The following designations are used for better legibility:
● Principal: Process Historian Master
● Mirror: Process Historian Standby
● Witness: Information Server or WinCC Server with Witness components
Note
Redundancy switchover
With a redundancy switchover, a time period of a few seconds is missing in the data
management of the Process Historian due to the switchover. This time period is transferred to
the Process Historian after the switch to "Active (Restore)" operating state.
If there is no prompt to restart the systems, the restart cannot be performed manually because
this would cause a loss of data.
Scenario 1
Scenario 2
Scenario 3
Scenario 4
The Mirror is decommissioned and too little memory space is available for the transaction log.
The Principal changes to the "Locked" state:
1. The Principal and the Mirror are active and synchronized.
2. The Mirror is separated from the network, for example, for maintenance work.
3. Data synchronization between the Principal and the Mirror does not take place.
4. The transaction log on the Principal is growing.
5. The low limit for free memory space for the transaction log is violated:
Less than 10% is free on hard disks with maximum 500 GB, or less than 50 GB is free on
hard disks with more than 500 GB.
6. The Principal changes to the "Locked" state.
The archive data of the OS are buffered in the cache. The cached time period depends on
the available memory space and the accumulating volume of data.
7. The Mirror becomes active once again.
8. The Principal is unlocked and changes to "Active" state.
9. The Principal and the Mirror are in the resynchronization status.
10.The transaction log is automatically reduced after completion of the synchronization.
11.The archive data buffered on the OS in the cache is transferred to the Principal.
Scenario 5
The Mirror is decommissioned and too little memory space is available for the transaction log.
The redundancy synchronization is deactivated to ensure operation of the Principal:
1. The Principal and the Mirror are active and synchronized.
2. The Mirror is separated from the network, for example, for maintenance work.
3. Data synchronization between the Principal and the Mirror does not take place.
4. The transaction log on the Principal is growing.
5. Redundancy synchronization (Mirroring) is deactivated to prevent an overflow of the
transaction log and a locking of the Principal.
– Manual: You disable the redundancy synchronization in the "Redundancy" dashboard
of the Process Historian Management Console.
– Automatic: The automatic shutdown function is activated in the "Redundancy"
dashboard of the Management Console.
6. The transaction log is automatically reduced.
7. The Principal is still available.
Scenario 6
The Mirror and the Principal are switched off and on in succession:
1. Both servers, Principal and Mirror, are synchronized.
2. The data is redundant and identical on both servers.
3. The Mirror is switched off.
4. The data is still saved on the Principal.
The data is no longer synchronized because the Mirror is switched off.
This means the database on both servers is not identical.
The transaction log of the Principal is growing.
5. The Principal is switched off.
6. No data can be saved.
7. The previous Mirror is switched on.
8. The Mirror works. However, the data of the Mirror cannot be synchronized with the Principal.
To prevent the risk of data loss, there is no automatic switchover from the Mirror for the
Principal in this case.
If you force a manual switchover, the previous Mirror takes over the role of the switched off
Principal.
If the original Principal is switched on once again, it takes over the role of 'Mirror'.
The previously saved data would be deleted in case of a synchronization with the new
'Principal' that is actually missing these databases.
These technical conflicts can be resolved in different ways with the Process Historian
Management Console.
Note
Process Historian status and licensing status
Before the restart, the status is shown as "Undefined" in the 'Process Historian status' area of
the Management Console.
The license is declared as "Invalid license" in the 'Licensing status' area.
After the restart, the status is synchronized again with the update.
For additional information, see the Installation Notes on the installation DVD and in the
Siemens portal.
Setting up redundancy
1. To open the Management Console on the principal (master), select "Start > Programs >
Siemens Automation > SIMATIC > Process Historian > Process Historian Management
Console".
2. Select the 'Redundancy' dashboard in the Explorer.
3. Click "Start redundancy configuration ..." in the 'Redundancy' area to launch the
configuration wizard.
4. In the 'Host configuration' dialog, configure the Process Historian server principal (master)
and mirror (standby), as well as the witness server.
The configuration includes the network adapters that are used by the principal (master) to
run the mirroring.
Configure the SQL server instance for each computer in the following format:
– <Computer name>\<SQLServer instance name>
Assign the following objects from the drop-down menus:
– SQL Server instance
– Network Adapter
Alternatively, you can enter the <Computer name>\<SQLServer instance name> manually.
Confirm your settings with "Next".
Configuration
Take the following configuration details into account when selecting the required settings.
Principal (master)
The wizard is launched on the Principal, so this is the default entry. This setting cannot be
changed.
– SQL Server instance:
<Computer name>\<SQLServer instance name>
The SQL Server instance for PH server is "HISTORIAN".
– Network adapter:
Selection of a dedicated redundancy link.
Mirror (standby)
– SQL Server instance:
Selection from the drop-down menu. If necessary, you can reload the list using the
"Refresh" button.
– Network adapter:
Selection similar to the dedicated redundancy link of the principal.
Witness server
– SQL Server instance:
Selection from the drop-down menu. If necessary, you can reload the list using the
"Refresh" button.
The instance depends on the base of the witness server, Information Server or WinCC.
The instance is named "INFSERVER" or "WINCC" respectively.
– Network adapter:
Selecting the terminal bus link.
5. Specify the ports and required firewall settings in the "TCP port settings" dialog.
Accept the Process Historian defaults. The firewall settings specified in the setup are now
taken into account.
Note
The default settings are edited if the proposed resources are already in use by a different
application.
You can find more detailed information on the firewall settings in the section Firewall
settings (Page 127).
6. A plausibility check of your configuration is performed in the 'Validation' dialog. This dialog
is also used to validate the connectivity of the configured servers and paths. The action
currently performed is indicated via a log in the "Validation" area.
Click "Rerun" to restart a possibly interrupted validation process.
Confirm the successful validation with "Next".
7. The "Overview" dialog displays a summary of the completed settings. Verify these settings.
Start the configuration process with "Next".
Click "Previous" to correct any incorrect entries.
8. The prepared configuration of redundancy on the principal, mirror, and witness servers is
executed in the "Execution" dialog.
The new configuration is set up in a step-by-step process. The log of actions is displayed
in the "Setup actions" area.
Certain setup actions may take a longer time depending on the size of the Process Historian
database.
We distinguish between the following processes:
– "Fast data backup and restore":
This process generates a complete backup copy of the principal database and
simultaneously restores it on the mirror.
– "Fast transmission of the transaction log":
This process generates and synchronously restores a backup of the transaction log.
Click "Rerun" to restart a possibly interrupted configuration process.
See also
Firewall settings (Page 127)
Introduction
This section describes the migration of the following projects to the current Process Historian:
● WinCC V7
● Central Archive Server (CAS)
● StoragePlus
● Process Historian
You can find a compilation of migratable data sources in the following graphic.
RQOLQH
:LQ&& VXSSRUWHGYHUVLRQV
3&69:LQ&&9DQGKLJKHU
UHODWHG6WRUDJH3OXV&$69DQGKLJKHU
:LQ&&%DFNXSV
RIIOLQH
'%0LJUDWLRQ:L]DUG
6W3OXV RQOLQH
&$6 3URFHVV+LVWRULDQ
6W3OXV&$6%DFNXSV
RIIOLQH
The data from the CAS and WinCC sources can be migrated online and offline. The data from
the Process Historian source can only be migrated online.
System requirements
The computer with which you perform the migration must meet the following conditions:
● The hardware requirements from the installation instructions must be met.
● The software requirements from the installation instructions must be met.
● The Process Historian must be enabled.
● The free space on the drive must be large enough to accommodate the new data.
● The latest version of the Process Historian must be installed.
● The required licenses must be available.
● Online segments can only be migrated if the corresponding output system is active.
● Backup segments can only be migrated if the backup files are available in the destination
path.
Note
Migration time
Depending on the data volume, the time needed for the migration may take from a few minutes
to several days.
5.2 Migrating
3. The dialog for the source path shows the available SQL instances in the network.
Select the required computer in the selection list.
The available projects are displayed. Two OS, OS(6) and OS(7), are in use in this example.
The data from the OS(6) are to be migrated.
Result
The selected data has been migrated to the current Process Historian database.
3. In the following dialog, select the "Add segments" or "Add folders" entry under "Add" in the
shortcut menu of the displayed field.
5. The Process Data Migrator indicates that the segment was found in the backups.
Click in the "Project in PH" column to assign the storage location for the migrated project.
Result
The selected data has been migrated to the current Process Historian database.
3. The dialog for the source path shows the available SQL instances in the network.
Select the PC with the required project from the selection list.
The selected WinCC project is displayed in the entry field.
Result
The selected data has been migrated to the current Process Historian database.
3. In the following dialog, select the "Add segments" or "Add folders" entry under "Add" in the
shortcut menu of the displayed field.
5. The Process Data Migrator indicates that the segment was found in the backups.
Click in the "Project in PH" column to assign the storage location for the migrated project.
Result
The selected data has been migrated to the current Process Historian database.
4. The dialog for the source path shows the available SQL instances in the network.
Select the source PC in the selection list.
8. On the destination PC, activate the Process Historian and connect the PCS 7 OS and
WinCC clients in the Process Historian system.
9. If you use Process Historian in the PCS 7 environment, perform the following additional
steps:
– Change the PC name of the Process Historian server in the PCS 7 project.
– Download the project to all participating operator stations (OS), which means to all
clients and servers on which Runtime is activated.
Result
The selected data has been migrated to the destination PC.
Note
Reduced performance
The transmission from the WinCC archive can be slower than from the cache of Process
Historian-Ready.
The result may be a reduction in performance.
Notice
Behavior with reduced memory
The available memory is monitored with Process Historian-Ready.
The cache can grow in the following cases:
● Loss of connection to the Process Historian server
● Reduced performance when processing the transmitted data on the Process Historian
server
The cache memory is freed up again once the buffered data is transmitted to the Process
Historian server.
Alarm to WinCC
An alarm is sent to WinCC when one of the following situations occurs:
● The available cache memory drops below the limit of 10 GB.
● The available cache memory is less than 13% of the reserved drive capacity.
Interruption of data transmission
Saving to cache and transmission of process data is interrupted when one of the following
situations occurs:
● The available cache memory drops below the limit of 5 GB.
● The available cache memory is less than 5% of the reserved drive capacity.
As of this time, the process data is only available in the WinCC archive.
Saving to cache automatically resumes when the available memory is increased.
Overview
OPC and OPC UA denote standardized, vendor-independent interfaces and information
models of the OPC Foundation.
OPC UA (Unified Architecture) is the successor technology of OPC, which was developed for
reliable data exchange in automation engineering and other areas of applications. OPC UA
has the following characteristics:
● Platform-independent
● Vendor-independent
● Use of standardized protocols as the communication medium (e.g. TCP, HTTP)
● Integrated security concept (authentication and authorization, encrypted communication
and data integrity using signing)
● Powerful information model and provision of all data in a single address space (DA, HDA,
A&CE)
You can find detailed information about OPC UA specifications on the OPC Foundation
website:
● http://www.opcfoundation.org (http://www.opcfoundation.org)
How it works
The PH-OPC-UA server is installed as a Windows service.
The server is started automatically when you start the computer. However, you can only use
the OPC UA server when the local Process Historian server is running.
Licensing
The PH-OPC-UA server runs with the following license:
Installation
Requirement
● The Process Historian is installed on the PC.
Procedure
1. Run the setup.
2. Carry out the installation.
Read the "Process Historian Installation Notes" for more on this.
3. Select under "Custom installation":
– "Options" > "Process Historian OPC UA 2014" program package
4. To complete the installation, reboot the system.
Configuration
The PH OPC UA server is pre-configured during installation.
If required, you can change the server configuration using the OpcUaServerPH.xml
configuration file. For additional information, refer to "How to configure the OPC UA server
(Page 94)".
You access the PH-OPC-UA server via the following URL:
● "opc.tcp://[HostName]:[Port]"
Parameter Description
HostName Placeholder for the computer name. Is used automatically
Port TCP/IP port number The default is "4852".
The PH-OPC-UA server only supports the binary OPC UA protocol for communication
(communication profile "UA-TCP UA-SC UA Binary"). The used port number is adjustable.
Discovery Server
The OPC UA Local Discovery Server (LDS) of the OPC Foundation is installed along with the
PH-OPC-UA server. The LDS allows OPC UA client applications to determine information
about available OPC UA servers.
Depending on its configuration, the PH-OPC-UA server registers itself with zero, one or
multiple Discovery servers. These servers can be installed either on the same PC or on another
PC.
See also
How to configure the OPC UA server (Page 94)
Certificates
Certificates are the method used for authentication of the OPC UA applications. Each
application has its own instance certificate with which it identifies itself in the public key
infrastructure (PKI).
The certificates used by the PH-OPC-UA server are stored in the settings in the
"OpcUaServerPH.xml" configuration file:
Notice
Access to the folder with the private key
For security reasons, no other users or applications apart from the server and the system
administrator may have access to the private key of the PH-OPC-UA server.
The instance certificate generated upon installation and the corresponding private key can be
replaced by the administrator of the system. In accordance with the applicable security concept
for the system, the new instance certificate can be either self-signed or issued by a certification
authority.
You specify the storage location for the instance certificate of the PH-OPC-UA server in the
configuration file of the server. If necessary, the storage location can be changed by the system
administration:
The instance certificate of the server in this case is in the directory "PKI\CA\Certs". The private
key is in the directory "PKI\CA\Private".
Parameter Meaning
StoreType Type of certificate storage. The storage location can be either "Directory" or "Windows".
StorePath The certificates of trusted clients are stored under this folder.
In this case, the PH-OPC-UA server trusts all clients whose instance certificates are located
in the "PKI\TrustList\Certs" folder.
For this storage option, the instance certificates of the clients must be located in the certificate
memory of the operating system under "<Local computer>\UA Applications".
Parameter Meaning
StoreType Type of certificate storage. The storage location can be either "Directory" or "Windows".
StorePath The certificates of trusted certification authorities are stored under this folder.
Note
Trustworthiness of CA certificates
Certificates from the memory of the certification authorities are not automatically trusted.
For a certification authority to be trusted, its certificate must be located in the memory for trusted
certificates.
The certificates of trusted certification authorities are in this case located in the "PKI\CA\Certs"
folder.
The "StorePath" parameter is not relevant. The certificates from certification authorities must
be stored in the Windows certificate memory in accordance with the operating system
requirements.
Certificates are trusted if they are located in one of these paths:
● <Local computer>\Trusted root certification authorities
● <Local computer>\Third-party root certification authorities
Note
CA certificates: Preconditions
● The storage location for the server certificate must be "Directory".
● The two storage locations for trusted client certificates and for certificates from certification
authorities must have the same StoreType, i.e. both must either be "Directory" or
"Windows".
Note
Only the StoreType "Directory" is supported.
To enable secured communication with this client, you need to move the rejected certificate
to the certificate memory for trusted certificates.
Introduction
The following is ensured at the communication level:
● UA application authenticity
● The confidentiality of messages exchanged
● The integrity of messages exchanged
The security mechanisms used, for example algorithms for encrypting and signing, are set in
standardized security policies. You can find technical details in the OPC UA specification under
"Part 2", "Part 4" and "Part 7".
The security policies supported by the PH-OPC-UA server are set using the server
configuration file in in "ServerConfiguration" and "SecuredApplication".
ServerConfiguration
The XML element "SecurityPolicies" under "ServerConfiguration" contains the list of all
available "Security Profile" and "Message Security Mode" combinations for the server.
Note
Secure communication
The following additional requirements apply to secure communication:
● Instance certificates for server and client
● Correct configuration of the certificate store
SecuredApplication
In accordance with the OPC UA specification, the security mechanisms and explicitly enabled
and disabled with the "SecurityProfileUris" element under "SecuredApplication".
The diagram below shows a SecuredApplication in which unsecured communication is
disabled:
The PH-OPC-UA server thereby supports the two security strategies "Basic128Rsa15" and
"Basic256" in runtime. "Message Security Modes Sign" and "SignAndEncrypt" are supported,
but unsecured communication is not ("None"). When communication is established, the UA
clients select the required Policy from this list.
Note
Unsecured communication between client and server
Use the "None" setting only for test and diagnostics purposes.
For a secure communication between client and server, use at least the following settings
during productive operation:
● SecurityPolicy: Basic 128Rsa15
● Message Security Mode: Sign
User identity
In addition to the security mechanisms of the communication level, the PH-OPC-UA server
also supports user authentication for the client applications using UserTokenPolicy
"UserName". The client application must provide a valid combination of user name and
password when communication is established. The PH-OPC-UA server verifies the
combination in the user management of the operating system.
You specify the UserTokenPolicy using the configuration file of the PH-OPC-UA server:
The PH-OPC-UA server uses this configuration to support both anonymous users and the
Policy "UserName"..
See also
How to configure the OPC UA server (Page 94)
OPC UA services
The following table sets out the functionality supported by OPC UA server 1.0.2:
Notice
Changing the server configuration
Changing the server configuration incorrectly can cause malfunctions and/or security
vulnerabilities
The server configuration may only be performed by qualified personnel.
<Secured Application>
<BaseAddresses> Configuration of the URL for the OPC UA server.
<...></...>
</BaseAddresses>.
<SecurityProfileUris> Configuration of the supported security policies
<SecurityProfile> Use the "none" setting only for test and diagnostics purposes
<...></...>
</SecurityProfile>
...
</SecurityProfileUris>
<ApplicationCertificate> Revision of the default certificate configuration according to OPC UA
<TrustedCertificateStore> Specification / Part 6.
<TrustedCertificates> (optional)
<...>
</Secured Application>
<Server Configuration>
<SecurityPolicies> Configuration of the message security modes.
<SecurityPolicy> Use the "none" setting only for test and diagnostics purposes
<...></...>
</SecurityPolicy>
...
</SecurityPolicies>
<UserTokenPolicies> Configuration of user identification
<UserTokenPolicy> Use the "Anonymous" setting only for test and diagnostics purposes
<...></...>
</UserTokenPolicy>
...
</UserTokenPolicies>
<Server Configuration
See also
How to configure the OPC UA server (Page 94)
You can find the configuration file in the installation folder under the following path:
● \Siemens\ProcessHistorian\bin
You can find additional information on the configuration file under "Configuration file
(Page 93)".
Notice
Changing the server configuration
Changing the server configuration incorrectly can cause malfunctions and/or security
vulnerabilities
The server configuration may only be performed by qualified personnel.
See also
Installing the PH OPC UA server (Page 84)
Configuring the security mechanisms (Page 89)
Configuration file (Page 93)
Firewall settings (Page 127)
Information model
The PH-OPC-UA server provides OPC UA clients with a hierarchical name area and access
to the following runtime data:
● Process Historian configuration data:
– Project structure: Organizational Structures, Data Sources, Tag/Message Configuration
Data
– Metadata: Additional Info / Tag Value Context
● Historical Process Historian data:
– Archived tag values (Historical Data Access)
– Archived messages (Historical Event Access)
The following messages are generated by the Process Historian and sent to all clients:
Note
The more measured values or messages archived per second, the smaller the segments
should be so that the individual segments do not get too large. 50,000 tags per second is the
high limit that should not be exceeded.
2. Enter a path for your new SQL Server instance or select an existing SQL Server instance.
The database installation wizard checks if the selected instance can be installed.
3. Confirm with "Next".
4. Use the slider to reserve the maximum work memory for the database.
5. Click "Next".
9. Click "Next".
17.Set the paths for the database files. Only local destination paths are permitted.
The database is now created. The progress of the database installation is documented in
a window.
Result
You have successfully installed a database.
Requirement
You have arrived at this point after installation according to the instruction in general mode.
You want to continue the installation in advanced mode.
9. Set the paths for the database files. Compared to standard mode, the database schema
can be much more finely structured in advanced mode.
Define the path for the transaction log in the text box.
You must define and create paths for the following types of values in the repository:
– General
– Messages
– Batches
– Process values
The database is now created. The progress of the database installation is documented in
a window.
12.Click "OK".
13.Shut down the computer and restart it so that all services can be installed.
Result
You have successfully installed a database.
Recovering a database
1. Start "DatabaseInstallationWizard.exe".
2. Click "Next".
The SQL Server instances are displayed. Usually there is one instance on the SQL Server.
9. Click "Next".
12.Click "Next".
Before recovery starts, a recovery overview of your information is displayed.
13.Check the information in the overview. If there is incorrect information in the overview, go
back with "Previous" the number of required steps and correct the information.
Successful completion of the database recovery is displayed at the end with the following
message:
"Database SUCCESSFULLY restored".
15.Close the database installation wizard with "Close".
16.You must shut down the computer and restart it for all services to be installed.
After restart, database backup is set to "Disable".
Result
You have successfully recovered a database.
Runtime segments
Runtime segments (RT segments) Runtime segments are segments which can be written and
are used for storing data. Each runtime segment has a sequential number, starting at 100 000.
Future runtime segments have the highest number.
RT segment Description
Future Runtime Segment (F-RTS) Segmentation is colored blue in the dashboard.
Current Runtime Segment (F-RTS) Segmentation is colored green in the dashboard.
Older Runtime Segment (O-RTS) Segmentation is colored gray in the dashboard.
Creation: The first time the Process Historian starts, the configured number of runtime
segments are created, see Segmentation dashboard.
Cyclic segmentation in operation:
1. A new future runtime segment is created.
2. If the configured number of runtime segments is available, the oldest runtime segment is
an archive segment.
Archive segments
It is not possible to write to archive segments.
Only archives segments can be saved and swapped out (set offline).
Saved Archive Created after saving an archive segment, a backup file (backup file) is created there‐
Segment by.
(S_AS) The date of the backup is shown in the 'Backup/Restore' dashboard', top list in the
'Backup created" column.
Offline (swap‐ Created after the setting a saved archive segment offline. The data of this segment
ped out) Ar‐ are only in the backup file.
chive Segment There is no data from this segment in the Process Historian database; only the in‐
(O_AS) formation about a backup and the offline setting is available.
All segments in the 'Backup/Restore' dashboard are included in the list below.
External Ar‐ Created by restoring (setting to online) a backup file for an offline archive segment.
chive Segment The data is not stored in the Process Historian database, but rather in an external
database.
Visible in the 'Backup/Restore' dashboard, top list 'Status' column = 'External'.
Repository segments
Repository segments contain the data from time periods outside of the runtime segments. This
includes data for all types of archive segments, since it is no longer possible to write to these
segments.
These segments are created by the Database Installation Wizard when the Process Historian
database is created.
Subtype Description
CAL segment Contains all data from time periods older than the oldest runtime segment.
This happens, for example, when an OS has not transfer data to the PH for a long
time, and then tries to catch up, and thereby sends data with a date outside the
runtime segments.
If values are stored in the CAL segment for an offline segment, this is indicated in the
'Backup/Restore' dashboard in the lower list where the 'New data' column = 'Yes'.
These offline segments must then be restored and backed up again. When you per‐
form the backup, data from the CAL segment are entered in the backup file of the
archive segment.
CAL segment Contains all data from time periods more recent than the most recent runtime seg‐
ment. For the segmentation, the data are transferred from the CAU segment into the
latest future runtime segment, which has the same time period.
This means that the data is always saved for a time period of 7 (= 5 – 1 + 3) weeks in the
Process Historian database.
8.3 Aggregation
A large volume of raw data is generated during operation. Due to the very large volume of raw
data, processing a query from raw data can take a very long time.
To speed up processing of queries, aggregates are used.
The aggregates combine raw data and process this raw data together. The aggregates are
saved in the database and are available for further processing. Aggregation speeds up further
processing of the entire data volume. The additional computing time required to process the
aggregates is lower than that for processing queries based on raw data. Approximately 3% to
6% additional space is required in the database to save the aggregates.
Aggregate methods
The following aggregates are used:
Aggregate intervals
The aggregates are calculated for the following time intervals:
● 1 minute
● 1 hour
● 1 day
Example
For a query, the MAX value over a period of one month is to be calculated and displayed.
Calculation
Without aggregation:
With a raw data cycle of 1 second, the query is calculated from the following volume of raw
data:
60 (sec) x 60 (min) x 24 (h) x 30 (d) = 2,592,000 values
The query is calculated from 2,592,000 raw data items.
With aggregation:
MAX (30 days)
The query is calculated from 30 aggregate time intervals.
See also
Setting up Process Historian redundancy (Page 52)
Note
Process Historian is generally enabled for operation in a domain or workgroup.
Operation in a domain must be agreed upon with the domain administrator. In the case of user-
specific guidelines, remove the PC from the domain before you install Microsoft Message
Queuing and Microsoft SQL Server 2008 R2. Log on to the computer concerned locally with
administrator rights. Perform the installation. You can reassign the WinCC computer to the
domain once the installation is successfully completed.
Note however that domain group policies and restrictions in the domain may also hinder
operation. If these restrictions cannot be overcome, operate the WinCC computer in a
workgroup.
Installation in a workgroup
Installation of the Process Historian in a workgroup is described in the FAQ "Installing and
Commissioning of Process Historian/ Information Server in a PCS 7 Environment":
● http://support.automation.siemens.com/WW/view/en/66579062 (http://
support.automation.siemens.com/WW/view/en/66579062)
Preparation
For the login information of the services on the OS to remain the same, these services must
be operated by a domain or workgroup whose password is not changed. This includes the
following services:
● CCCAPHServer Service
● Process Historian Redundancy Service
● Witness server
If the passwords are changed, however, the login information of these services must be
changed accordingly on the corresponding OS server; this server must then be restarted.
Note the following conditions:
● If you integrate an OS system in a domain, you must register the domain user who logs on
in additional local groups.
● To simplify administration and installation, create a domain user as local administrator on
the OS server and the Process Historian.
● The domain user who is logged on to the operating system must not be the same user who
starts the CCCAPHServer service.
● The domain user who starts the CCCAPHServer service must have the appropriate
authorizations in the SQL Server of the Process Historian. Add this user to the local
administrator group of the OS system.
Configuration example
The example below shows the transfer of a workgroup installation to a domain installation. For
security reasons, the operating system login for the OS server and the Process Historian
should only have local user authorizations.
3URFHVV+LVWRULDQ
,QIRUPDWLRQ6HUYHU
,QIRUPDWLRQ6HUYHU&OLHQW
066HUYHU5%LW
3+
7HUPLQDO%XV
266LQJOH6WDWLRQ
:LQGRZV%LW
(626
3ODQW%XV
$6
. Name Comment
Domain pcs7sv.local
OS server ESOS03
Process Historian / Information PH03 Process Historian and Information
Server Server are running on the same
physical PC
Operating system login for OS serv‐OSUserDom The login has local user authoriza‐
er and Process Historian tions.
CCCAPHServer login for OS serverPHReadyUserETest The login requires local administra‐
tor authorization on the OS server.
Result
A service window indicates the successful completion of the process.
Another service window indicates that the new entries will be activated with a restart of the
service.
Restart
1. Open the Computer Management again.
2. Open the shortcut menu of the CCCAPHServer.
3. Select "Restart".
The CCCAPHServer service restarts.
The new entries have been applied.
Note
Domain user logon
The domain user must not be logged on to the OS operating system during runtime.
12.Select the required domain path. Confirm your selection with "OK".
A window for selection of users, computers, service accounts and groups opens.
13.Enter the user name in the input box. Click "OK" to confirm your entries.
The selection window closes.
Result:
The new user name is displayed in the "Login Now" window.
The new login is entered in the login list of the computer management.
2. An SQL login with corresponding user assignment must be created for the domain user on
the Process Historian server as well as on the Process Historian Witness.
2. If the operating system login only has user authorization on the Process Historian, the
Process Historian Management console is not opened automatically at restart. A restart
with administrator authorization is necessary to open the Process Historian Management
console.
– Procedure:
– Go to "Start > Siemens Automation > SIMATIC > Process Historian > Process Historian
Management Console".
See also
http://support.automation.siemens.com/WW/view/en/66579062 (http://
support.automation.siemens.com/WW/view/en/66579062)
C
Changing the operating mode, 22
D
Diagnostic message, 27
E
Event log, 27
S
Segmentation
Anchor point, 12