eP-
Satellite server
_
_________________
_
_
_________________
_
_
_________________
_
_
_________________
_
_
_________________
_
_
__________
_
_________________
_
_
_________________
_
SINUMERIK
SINUMERIK 840D sl/840D
eP-Satellite server
Operating Instructions
Valid for:
EP-Satellite server version V04.09.02.00
03/2011
Preface
Product information
1
Requirements for operation
2
Release management - eP-
Satellite server
3
Release management - ePS
Reporting Services
4
Release management -
Updating the eP-Satellite
server
5
Operation management -
System in operation
6
Appendix
A
Legal information
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
with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.
CAUTION
without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.
NOTICE
indicates that an unintended result or situation can occur if the corresponding information is not taken into
account.
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 for the specific task, 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 adhered to. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of the 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.
Siemens AG
Industry Sector
Postfach 48 48
90026 NÜRNBERG
GERMANY
Ⓟ 04/2011
Copyright © Siemens AG 2011.
Technical data subject to change
eP-Satellite server
Operating Instructions, 03/2011 3
Preface
SINUMERIK documentation
The SINUMERIK documentation is organized in the following categories:
● General documentation
● User documentation
● Manufacturer/service documentation
Additional information
You can find information on the following topics at www.siemens.com/motioncontrol/docu:
● Ordering documentation/overview of documentation
● Additional links to download documents
● Using documentation online (find and search in manuals/information)
Please send any questions about the technical documentation (e.g. suggestions for
improvement, corrections) to the following address:
docu.motioncontrol@siemens.com
My Documentation Manager (MDM)
Under the following link you will find information to individually compile OEM-specific
machine documentation based on the Siemens content:
www.siemens.com/mdm
Training
For information about the range of training courses, refer under:
● www.siemens.com/sitrain
SITRAIN - Siemens training for products, systems and solutions in automation technology
● www.siemens.com/sinutrain
SinuTrain - training software for SINUMERIK
FAQs
You can find Frequently Asked Questions in the Service&Support pages under Product
Support. http://support.automation.siemens.com
Preface
eP-Satellite server
4 Operating Instructions, 03/2011
SINUMERIK
You can find information on SINUMERIK under the following link:
www.siemens.com/sinumerik
Target group
This manual is intended for use by planners, configuration engineers, technicians,
installation personnel, programmers, commissioning personnel, operators, service and
maintenance personnel
Benefits
The operating instructions provide information on the components so that the target group is
capable of installing, setting up, testing, commissioning, operating, and troubleshooting the
products or system correctly and without danger.
Usage phase
Planning and configuration phase, implementation phase, setup and commissioning phase,
application phase, maintenance and service phase.
Standard version
This documentation only describes the functionality of the standard version. Extensions or
changes made by the machine manufacturer are documented by the machine manufacturer.
Other functions not described in this documentation might be executable in the control. This
does not, however, represent an obligation to supply such functions with a new control or
when servicing.
Further, for the sake of simplicity, this documentation does not contain all detailed
information about all types of the product and cannot cover every conceivable case of
installation, operation or maintenance.
Technical Support
You will find telephone numbers for other countries for technical support in the Internet under
http://www.siemens.com/automation/service&support
eP-Satellite server
Operating Instructions, 03/2011 5
Table of contents
Preface ...................................................................................................................................................... 3
1 Product information.................................................................................................................................... 7
1.1 eP-Satellite product overview ........................................................................................................7
1.2 Legal framework ............................................................................................................................7
2 Requirements for operation ....................................................................................................................... 9
2.1 Basic configuration: Server systems............................................................................................11
2.1.1 Installing the eP-Satellite database server ..................................................................................11
2.1.2 Installing the eP-Satellite external web server.............................................................................14
2.1.3 Installing the eP-Satellite internal web server..............................................................................15
2.1.4 Installing the eP-Satellite application render server.....................................................................16
2.1.5 Installing the eP-Satellite application reporting database server.................................................16
2.1.6 Installing the eP-Satellite application reporting web server .........................................................19
2.2 Change management - Basic ePS software and hardware.........................................................22
2.3 Change management - Software updates ...................................................................................22
2.4 Security management - Certificates.............................................................................................23
2.5 Configuration example: Server systems ......................................................................................23
2.6 Infrastructure engineering............................................................................................................25
2.7 Implementation example: IT infrastructure ..................................................................................26
3 Release management - eP-Satellite server ............................................................................................. 29
3.1 Preparing for installation ..............................................................................................................30
3.2 Installing the eP-Satellite server software....................................................................................33
3.3 Configuring the internal eP-Satellite web server..........................................................................41
3.4 Configuring the external eP-Satellite web server.........................................................................50
3.5 Database logging .........................................................................................................................55
3.6 Activating PKI login ......................................................................................................................61
3.7 First commissioning of the eP-Satellite and testing of its functions.............................................65
3.8 Configuring the connection ..........................................................................................................69
3.9 Installing Render Services ...........................................................................................................71
3.10 Installing and configuring the RANG server.................................................................................74
3.10.1 Installing the RANG Servers........................................................................................................74
3.10.2 Configuring the RANG server ......................................................................................................75
4 Release management - ePS Reporting Services..................................................................................... 79
4.1 Introduction ..................................................................................................................................79
4.2 Configuring Microsoft Reporting Services ...................................................................................79
Table of contents
eP-Satellite server
6 Operating Instructions, 03/2011
4.3 Installing ePS Reporting Services............................................................................................... 85
4.4 Final steps................................................................................................................................... 87
4.4.1 Settings in the virtual directories ................................................................................................. 87
4.4.2 Testing the ePS Reporting Services installation......................................................................... 88
5 Release management - Updating the eP-Satellite server ........................................................................91
5.1 Updating the eP-Satellite ............................................................................................................ 91
5.2 Installing the eP-Satellite server software................................................................................... 93
5.3 Configuring the external eP-Satellite web server........................................................................ 99
5.4 Database logging ...................................................................................................................... 100
5.5 Activating PKI login ................................................................................................................... 104
5.6 ePS Render Services................................................................................................................ 104
5.7 Reporting Services.................................................................................................................... 106
5.7.1 Installing ePS Reporting Services............................................................................................. 106
5.7.2 Testing the ePS Reporting Services installation....................................................................... 108
5.8 Installing and configuring the RANG server.............................................................................. 110
5.8.1 Installing the RANG Servers ..................................................................................................... 110
5.8.2 Configuring the RANG server ................................................................................................... 111
6 Operation management - System in operation....................................................................................... 115
6.1 Business Administration............................................................................................................ 115
6.2 Business Administration functions ............................................................................................ 116
6.3 Exporting/Importing a machine configuration............................................................................ 121
A Appendix................................................................................................................................................ 123
A.1 Abbreviations ............................................................................................................................ 123
Index...................................................................................................................................................... 125
eP-Satellite server
Operating Instructions, 03/2011 7
Product information 1
1.1 eP-Satellite product overview
Overview
eP-Satellite is part of the ePS Network Services product portfolio. It is chiefly intended for
use by customers who require a high level of data confidentiality and would, therefore, be
unwilling to store information in a location outside of their direct sphere of influence. The
customer is entirely responsible for the operation of the eP-Satellite product and the server
system required for this purpose. This scope of responsibility shall also include all aspects of
availability, data integrity, IT system administration, and the IT infrastructure. (Other persons
permitted to undertake these duties may be designated by the customer.)
This document describes aspects that are particularly associated with the IT-related tasks
required during the preparation phase and while the product is in use. The pictures shown in
this documentation serve for visualization purposes only. The values and texts shown in the
pictures must not be used during the installation!
1.2 Legal framework
Overview
A license agreement between Siemens AG and the user provides the legal framework
governing the use of eP-Satellite.
Product information
1.2 Legal framework
eP-Satellite server
8 Operating Instructions, 03/2011
eP-Satellite server
Operating Instructions, 03/2011 9
Requirements for operation 2
System overview
Currently, at least two physical servers are recommended for operating the eP-Satellite
product. Depending on the functions you require, up to six separate server systems may be
necessary. The servers used reflect the main eP-Satellite functions and are summarized in
the table below.
The tables below provide a summary of the basic software necessary for operating eP-
Satellite, depending on the product version being used. The use of other versions of the
basic software specified in the tables are not supported.
Server Function Minimum requirements
eP-Satellite
database server
Saving and managing all
machine data
MS Windows Server 2003 Enterprise Edition,
English
MS SQL Server 2005 Enterprise Edition,
English, incl. SP2
.NET Framework 2.0, English
.NET Framework 3.0, English
eP-Satellite External
Web Server
Communications with
the ASP server for
support cases
MS Windows Server 2003 Enterprise Edition,
English
MS IIS 6.0 (part of the OS)
.NET Framework 2.0, English
.NET Framework 3.0, English
.NET Framework 3.5, English
Internal eP-Satellite web
server
Making the eP-Satellite
websites available to
service PCs and
machine control systems
MS Windows Server 2003 Enterprise Edition,
English
MS IIS 6.0 (part of the OS)
.NET Framework 2.0, English
.NET Framework 3.0, English
.NET Framework 3.5, English
eP-Satellite application
render server (optional)
Machine control systems
for supporting
SINUMERIK
solution line
MS Windows Server 2003 Enterprise Edition,
English
MS IIS 6.0 (part of the OS)
Internet Explorer 6 (it is essential that this
version is used)
.NET Framework 2.0, English
.NET Framework 3.0, English
.NET Framework 3.5, English
Requirements for operation
eP-Satellite server
10 Operating Instructions, 03/2011
Server Function Minimum requirements
eP-Satellite application
reporting database
server
(optional)
Saving and managing
information relating to
reporting
MS Windows Server 2003 Enterprise Edition,
English
MS SQL Server 2005 Enterprise Edition,
English, incl. SP2
.NET Framework 2.0, English
eP-Satellite application
reporting web server
(optional)
Preparing and displaying
reporting information
with the aid of reports
MS Windows Server 2003 Enterprise Edition,
English
MS IIS 6.0 (part of the OS)
MS SQL Server 2005 Reporting Services (web
services) incl. SP2
.NET Framework 2.0, English
.NET Framework 3.0, English
.NET Framework 3.5, English
Note
The instructions that follow assume that all server systems are members of an active
directory domain.
In order to unzip each of the installation packages, a data compression program that
supports both .zip and .cab archives must be installed on all of the servers.
When calculating the size of the database, the following event sizes apply:
Event Size in KB
(estimation)
TE Trigger event (size dependent on optional file upload) 470
EH Event history entry 70
SC Service case (fault message) 65
AC Archive components (PLC archive, NC archive) 645
UAT Universal axis test 1.085
GLT Equability axis test 350
KFT Circularity test 450
MT Maintenance ticket 320
MTT Maintenance ticket template 350
Alarm model, 5 to 7 MB 6.000
Requirements for operation
2.1 Basic configuration: Server systems
eP-Satellite server
Operating Instructions, 03/2011 11
2.1 Basic configuration: Server systems
2.1.1 Installing the eP-Satellite database server
Installing the eP-Satellite database server
Relevant servers eP-Satellite database server
In order to install Microsoft SQL Server 2005, the operating system must be fully set up and
configured. The installation program checks the Microsoft Support and .Net files; it will
subsequently install them if required. The warning informing you that IIS is missing, which
appears during setup, can be ignored on this server.
Perform the setup procedure as follows:
Components to Install • SQL Server Database Services
• Workstation components, Books Online
and development tools
Instance Name • Default or Named instance
Requirements for operation
2.1 Basic configuration: Server systems
eP-Satellite server
12 Operating Instructions, 03/2011
Service Account • Use the built-in System account
Local system:
• SQL Server
• SQL Server Agent
• SQL Browser
Authentication Mode • Mixed Mode
• Enter the password from the data sheet
under "Enter password".
Collation settings • SQL collations:
Dictionary order, case-insensitive, for use
with 1252 Character Set
Installing the eP-Satellite database server
Once installation is complete, you will still need to install the Microsoft SQL Server service
packs described in the general system requirements, as well as the latest safety patches.
Requirements for operation
2.1 Basic configuration: Server systems
eP-Satellite server
Operating Instructions, 03/2011 13
Configuring the SQL Server following installation
Cross Database Ownership In the SQL Server Management Studio,
right-click the database instance, select
"Properties", and activate the "Cross
database ownership chaining" option
under the "Security" menu command.
Remote Connections In the SQL Server Management Studio,
right-click the database instance, select
"Properties", and activate the "Allow
remote connections to this server"
option under the "Connections" menu
command.
Installing the SQL server
Note
The eP-Satellite system consists of a total of six databases which - in general - can only be
saved at different times. To be able to restore all databases to the same level, it is necessary
that a "Point in Time Restore" can be executed. A prerequisite for this are transaction logs.
These should, therefore, also be saved separately.
Requirements for operation
2.1 Basic configuration: Server systems
eP-Satellite server
14 Operating Instructions, 03/2011
2.1.2 Installing the eP-Satellite external web server
Relevant servers eP-Satellite External Web Server
IIS must be installed on the web servers before the eP-Satellite can be installed.
To do this, add the Windows "Application Server" component. ASP.NET will also need to be
installed in order to carry out basic installation of the application server.
The diagrams below show all the components required:
Installing the EP-Satellite external server and web server
Requirements for operation
2.1 Basic configuration: Server systems
eP-Satellite server
Operating Instructions, 03/2011 15
2.1.3 Installing the eP-Satellite internal web server
Relevant servers eP-Satellite Internal Web Server
IIS must be installed on the web servers before the eP-Satellite can be installed.
To do this, add the Windows "Application Server" component. ASP.NET will also need to be
installed in order to carry out basic installation of the application server.
The diagrams below show all the components required:
Installing the eP-Satellite internal web server
Requirements for operation
2.1 Basic configuration: Server systems
eP-Satellite server
16 Operating Instructions, 03/2011
2.1.4 Installing the eP-Satellite application render server
Relevant servers eP-Satellite application render server
IIS must be installed on the web servers before the eP-Satellite can be installed.
To do this, add the Windows "Application Server" component. ASP.NET will also need to be
installed in order to carry out basic installation of the application server.
The diagrams below show all the components required:
Installing the eP-Satellite application render server
2.1.5 Installing the eP-Satellite application reporting database server
Relevant servers eP-Satellite application reporting database server
In order to install Microsoft SQL Server 2005, the operating system must be fully set up and
configured. The installation program checks the Microsoft Support and .Net files; it will
subsequently install them if required.
The warning informing you that IIS is missing, which appears during setup, can be ignored
on this server.
Requirements for operation
2.1 Basic configuration: Server systems
eP-Satellite server
Operating Instructions, 03/2011 17
Procedure
Perform the setup procedure as follows:
Components to Install • SQL Server Database Services
• Analysis Services
• Notification Services
• Integration Services
• Workstation components, Books Online
and development tools
Instance Name • Default or Named instance
Service Acount • Use the built-in System account
Local system:
• SQL Server
• Analysis Services
Requirements for operation
2.1 Basic configuration: Server systems
eP-Satellite server
18 Operating Instructions, 03/2011
Authentication Mode • Mixed Mode
• Enter the "sa" password from the data
sheet under "Enter password".
Collation settings • Accent-sensitive
• Dictionary order, case-insensitive, for
use with 1252 Character Set
Installing the eP-Satellite application reporting database server
Requirements for operation
2.1 Basic configuration: Server systems
eP-Satellite server
Operating Instructions, 03/2011 19
2.1.6 Installing the eP-Satellite application reporting web server
Relevant servers eP-Satellite application reporting web server
Installing IIS
IIS must be installed on the web servers before the eP-Satellite can be installed. To do this,
add the Windows "Application Server" component. ASP.NET will also need to be installed in
order to carry out basic installation of the application server.
The diagrams below show all the components required:
Components
Installing the database components
A few additional database server components are installed for the eP-Satellite reporting web
server. The settings for each are described below:
The installation program checks the Microsoft Support and .Net files and installs them if
required.
Requirements for operation
2.1 Basic configuration: Server systems
eP-Satellite server
20 Operating Instructions, 03/2011
Components to Install • SQL Server Database Services
• Reporting Services
• Workstation components, Books Online
and development tools
Instance Name • Default or Named instance
Service Account • Use the built-in System account
Local system:
• SQL Server
• Reporting Services
Requirements for operation
2.1 Basic configuration: Server systems
eP-Satellite server
Operating Instructions, 03/2011 21
Authentication Mode • Mixed Mode
• Enter the "sa" password from the data
sheet under "Enter password".
Collation Settings • Accent-sensitive
• Dictionary order, case-insensitive, for use
with 1252 Character Set
Installing the eP-Satellite application reporting web server
Following this, select the default configuration for the report server and deactivate "Error and
Usage Report Settings".
Requirements for operation
2.2 Change management - Basic ePS software and hardware
eP-Satellite server
22 Operating Instructions, 03/2011
2.2 Change management - Basic ePS software and hardware
Overview
Minimum requirements for the eP-Satellite server HW configuration are redefined at specific
intervals. The cycles for releasing the new minimum requirements are determined by ePS &
RTS. These are generally defined when a new version of eP-Satellite is released; they
should always be considered as a guide value.
2.3 Change management - Software updates
Overview
eP-Satellite users have sole responsibility for the availability and security of the servers
being operated. This is particularly pertinent if the service packs and security patches or
virus signatures provided by the basic software manufacturers have not been installed on the
eP-Satellite servers.
The security patches supplied monthly by Microsoft are checked by the ASP server operator
for compatibility with the current version of the ePS network services through an internal
system test and then released. An overview of the patch compatibility is generally given
shortly after the release of the security patch on the Service & Support Portal of Siemens
Industry Automation and Drive Technologies.
Users assume full responsibility for any consequences resulting from machine releases or
the sending of file attachments, etc., from an eP-Satellite server to a third-party organization.
Requirements for operation
2.4 Security management - Certificates
eP-Satellite server
Operating Instructions, 03/2011 23
2.4 Security management - Certificates
Internal and external eP-Satellite server: Certificate
The HTTPS protocol is used for internal communications between the eP-Satellite server
and machine controls. The operator himself is responsible for procurement and installation of
the required 128 bit certificates. An official SSL web server certificate of a worldwide
renowned certifier such as Verisign is required for save communications between the web
server and the machines.
Necessity of certificates for server/server communication
The HTTPS protocol is also used for communications between the eP-Satellite server and
the ePS Network Service server.
2.5 Configuration example: Server systems
Scope of functions
The tables below show an example of an eP-Satellite system's hardware configuration and
full scope of functions.
The exact service specifications for the servers mentioned above will depend on how eP-
Satellite is to be used (e.g. number of machines logged on, number of monitored states,
number of saved events); therefore, the tables have been provided solely as a guide. eP-
Satellite users define their own specific requirements for the servers used as appropriate for
their own environments.
eP-Satellite External Web Server
Component Number/Type
Processor 1 x Intel dual-core, 3 GHz
Memory 2 GB RAM
HDD memory OS 2 x 73 GB, 10,000 rpm (RAID1)
HDD memory log files 2 x 73 GB, 10,000 rpm (RAID1)
Internal eP-Satellite web server
Component Number/Type
Processor 1 x Intel dual-core, 3 GHz
Memory 2 GB RAM
HDD memory OS 2 x 73 GB, 10,000 rpm (RAID1)
HDD memory log files 2 x 73 GB, 10,000 rpm (RAID1)
Requirements for operation
2.5 Configuration example: Server systems
eP-Satellite server
24 Operating Instructions, 03/2011
eP-Satellite database server
Component Number/Type
Processor 1 x Intel dual-core, 3 GHz
Memory 4 GB RAM
HDD memory OS 2 x 73 GB, 10,000 rpm (RAID1)
SQL transaction logs 2 x 73 GB, 10,000 rpm (RAID1)
HDD memory SQL data 4 x 200 GB, 10,000 rpm (RAID10)
eP-Satellite application render server
Component Number/Type
Processor 1 x Intel dual-core, 3 GHz
Memory 2 GB RAM
HDD memory OS 2 x 73 GB, 10,000 rpm (RAID1)
HDD memory log files 2 x 73 GB, 10,000 rpm (RAID1)
eP-Satellite application reporting database server
Component Number/Type
Processor 1 x Intel dual-core, 3 GHz
Memory 2 GB RAM
HDD memory OS 2 x 73 GB, 10,000 rpm (RAID1)
SQL transaction logs 2 x 73 GB, 10,000 rpm (RAID1)
HDD memory log files 2 x 146 GB, 10,000 rpm (RAID1)
eP-Satellite application reporting web server
Component Number/Type
Processor 1 x Intel dual-core, 3 GHz
Memory 2 GB RAM
HDD memory OS 2 x 73 GB, 10,000 rpm (RAID1)
HDD memory log files 2 x 73 GB, 10,000 rpm (RAID1)
Requirements for operation
2.6 Infrastructure engineering
eP-Satellite server
Operating Instructions, 03/2011 25
2.6 Infrastructure engineering
Overview
Certain minimum requirements in respect of the IT infrastructure must be met in order to
operate the eP-Satellite server. These are outlined below.
Internet connection
A minimum requirement is that the eP-Satellite web server has an official IP address and can
be accessed by ePS Network Services servers via the Internet.
ePS Network Services servers communicate exclusively using port 443 and the HTTPS
protocol. ePS Network Services servers use a valid Class 3 certificate for SSL encryption,
which is mandatory.
Bandwidth required
The minimum Internet connection bandwidth required for communications between ePS
Network Services servers and the eP-Satellite server is 512 kbit/s.
Protocols used
The HTTPS and SOAP protocols are used for all communication taking place within the eP-
Satellite system architecture.
Requirements for operation
2.7 Implementation example: IT infrastructure
eP-Satellite server
26 Operating Instructions, 03/2011
2.7 Implementation example: IT infrastructure
Communication paths
The communication paths used are shown in the graphic below:
K1, K2
Communications between:
Protocol:
Type:
Purpose:
Specification:
eP-Satellite server and ePS Network Services server
HTTPS, SOAP over VPN
Permanent (mandatory)
E.g. for changes to organization data
WSDL 1, WSDL 2
K3
Communications between:
Protocol:
Type:
Purpose:
Specification:
eP-Satellite server and ePS Network Services server
HTTPS, SOAP over VPN
Dependent on requirements
Service case
WSDL 3, remote access
Requirements for operation
2.7 Implementation example: IT infrastructure
eP-Satellite server
Operating Instructions, 03/2011 27
K4
Communications between:
Protocol:
Type:
Purpose:
Specification:
ePS Network Services client (type 1) and eP-Satellite server
HTTPS, SOAP
Permanent
Using ePS Network Services
WSDL 4
K5
Communications between:
Protocol:
Type:
Purpose:
Specification:
ePS Network Services client (type 2) and eP-Satellite server
HTTPS, SOAP
Permanent
Using ePS Network Services
WSDL 5
K6, K7
Communications between:
Protocol:
Type:
Purpose:
Specification:
eP-Satellite application server and DC portal server
HTTPS, SOAP
Permanent
Making ePS Reports available
WSDL 6, 7
K8
Communications between:
Protocol:
Type:
Purpose:
Specification:
eP-Satellite external web server and
eP-Satellite database server
TCP, ADO.NET
Permanent
Using ePS Network Services for the support
---
Figure 2-1 Example: IT infrastructure
Requirements for operation
2.7 Implementation example: IT infrastructure
eP-Satellite server
28 Operating Instructions, 03/2011
eP-Satellite server
Operating Instructions, 03/2011 29
Release management - eP-Satellite server 3
Overview
The software to be installed comprises the following components:
Installation package Designation
Server installation package server_install_Satellite_x.x.x.x.cab
Extension services svc_install_x.x.x.x.cab
Patches (where applicable) E.g. MHScript_Patchxx_x.x.x.x.cab
Language packages server_install_lng_yy_x.x.x.x.cab
Render server package RenderServer_x.x.x.x.msi
Reporting server package Reporting_install_Satellite_x.x.x.x.cab
Genesis server package genesis_x.x.x.x.msi
Online help OH_YYY
RANG server installation package epsrang-x.x.x-x.i386.rpm
RANG client installation package RANGplSetup_x.x.x.x.exe
RANG client installation package RANGplslDownload_x.x.x.x.zip
RANG client installation package ServiceEngineerActiveXClient_Download_x.x.x.x.zip
Fonts ARIAlUNI.TTF, mssong.ttf
General preconditions
In order install the eP-Satellite, the servers must already have been installed as described in
Section Basic configuration: Server systems (Page 11). This includes installation of the latest
safety patches and updates.
NOTICE
Symbols in the text
In the instructions that follow, several areas of text are marked with % symbols. The values
that correspond to these can be found on the installation insert and must be inserted in the
areas of text accordingly (with the % symbols omitted).
Release management - eP-Satellite server
3.1 Preparing for installation
eP-Satellite server
30 Operating Instructions, 03/2011
3.1 Preparing for installation
Precondition
Table 3- 1 Installing the fonts
eP-Satellite External Web Server
eP-Satellite Internal Web Server
Relevant servers
eP-Satellite application reporting web server
Before installing the server software, the "Arial Unicode MS" and "MS Song Truetype" fonts
must be installed on the relevant servers. To do this, you need to copy files "ARIALUNI.TTF"
and "mssong.ttf" into the "C:\Windows\Fonts" directory.
Table 3- 2 Installing Dundas Web Chart
eP-Satellite Internal Web Server Relevant servers
In order that the PC user interface of the eP-Satellite functions error-free, the Dundas Web
Chart software, Version 3.1.0.1572 must be installed on the internal web server.
Any directory can be selected as installation path, as all DLLs, which are copied to the
system when installing, are registered in the GAC.
Creating the required users and groups
Global group bizAdmin
Users in bizAdmin group Any name and password
Configuring the .Net framework (aspnet.config)
eP-Satellite External Web Server
Relevant servers
eP-Satellite Internal Web Server
NOTICE
For multiprocessor systems only!
Release management - eP-Satellite server
3.1 Preparing for installation
eP-Satellite server
Operating Instructions, 03/2011 31
File aspnet.config can be found in the Windows installation directory under Microsoft.NET
(C:\WINDOWS\Microsoft.NET\Framework\v2.0.5072)
The workstation collector is used for the eP-Satellite. This is activated by entering the
following in file aspnet.config:
<configuration>
<runtime>
<gcServer enabled="false"/>
<gcConcurrent enabled="false"/>
</runtime>
</configuration>
Configuring the .Net framework (web.config)
eP-Satellite External Web Server
Relevant servers
eP-Satellite Internal Web Server
File web.config can be found in the Windows installation directory under Microsoft.NET
(C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG)
You need to adapt this (in the <httpHandlers> section): by adding .epdf as a file extension:
<add path="*.epdf"
verb="*" type="System.Web.UI.PageHandlerFactory" validate="True"/>
The entry should appear before or after the entry for .aspx and must in all cases appear
before any other entries that would also incorporate *.epdf, such as *.*.
The line below this also needs to be adapted or added.
Important! Pay attention to upper and lower cases.
The value for parameter minLocalRequestFreeThreads equals 64 * the number of logic
processors in the server. None of the other values take the number of processors into
account. If there is as yet no <httpRuntime> section in file web.config, this will need to be
inserted.
Release management - eP-Satellite server
3.1 Preparing for installation
eP-Satellite server
32 Operating Instructions, 03/2011
Example of a web server with a processor in the <system.web> section between
</httpHandlers> and <httpModules>:
<httpRuntime executionTimeout="600" maxRequestLength="128000"
minLocalRequestFreeThreads="64"/>
Adapting the settings file
eP-Satellite External Web Server
eP-Satellite Internal Web Server
eP-Satellite application reporting web server
Relevant servers
eP-Satellite application reporting database server
The settings file contains all the settings required for installation. This file, called
satellite.settings, can be found in the unzipped installation package under: tools\install\
<!-- Persistence settings -->
<<NAME=SqlInstanceMain; FILE=*.*; VALUE="%Database\(Instance)%"; >>
<<NAME=SqlInstanceReporting; FILE=*.*;
VALUE="%ReportingDatabase\(ReportingInstance)%"; >>
<<NAME=SqlInstanceLogging; FILE=*.*; VALUE="%Database\(Instance)%"; >>
<!-- Authorization -->
<<NAME=Authorization; FILE=\Webs\BA\Web.Config.tmpl; VALUE= <allow
roles="%Domain%\bizAdmin"/><deny users="*" />; >>
<!--------------------------------------------------------->
<!-- Settings for Reporting Application (V4.4 and later) -->
<!--------------------------------------------------------->
<< NAME=ReportingServerUrl; FILE=*.*; VALUE=localhost/ReportServer; >>
<< NAME=ReportServiceCommAvailable; FILE=*.*; VALUE=TRUE; >>
<< NAME=DeploymentDirectory; FILE=*.*;
VALUE=C:\ePS_Services\ePS_Reporting\epsReportingSSIS; >>
<< NAME=EpsReportingWebService; FILE=*.*; VALUE=https://%Reporting-
URL%/epsReportingServiceComm/epsReportingServiceV1.asmx; >>
<< NAME=MicrosoftReportingWebService; FILE=*.*; VALUE= https://%Reporting-
URL%/ReportServer/ReportService2005.asmx;>>
<< NAME=ssrsBinDir; FILE=*.*; VALUE=C:\Program Files\Microsoft SQL
Server\%MSSQL.2%\Reporting Services\ReportServer\bin;>>
<< NAME=vsReportingBinDir; FILE=*.*; VALUE=C:\Program Files\Microsoft Visual Studio
8\Common7\IDE\PrivateAssemblies;>>
<!-------------------------------------------------------------------->
Release management - eP-Satellite server
3.2 Installing the eP-Satellite server software
eP-Satellite server
Operating Instructions, 03/2011 33
<!-- Additional Settings for Reporting Application (V4.5 and later) -->
<!-------------------------------------------------------------------->
<< NAME=AcrobatReaderPath; FILE=*.*; VALUE=C:\Program Files\Adobe\Reader
8.0\Reader\AcroRd32.exe; >>
<<NAME=ShowOfflineSynchronization; FILE=\Webs\Web.Config.tmpl; VALUE=<add
key="ShowOfflineSynchronization" value="True" />; >>
3.2 Installing the eP-Satellite server software
Installing the database
Relevant servers eP-Satellite database server
Extract the archive "Server_Install_Satellite_x.x.x.x.cab": The installation package must be
located no more than one level below the drive letter; otherwise, installation problems
relating to the depth of the directory will arise. It must be ensured that none of the extracted
folders – including subfolders – has read-only access.
Example: C:\temp\server_install_Satellite_x.x.x.x
The following batch files can be found under \persistance\install in the unzipped installation
package, and must be run in the following order:
Start the database installation TsBuild.bat /s %Database\(Instance)%
Start the logging database installation LoggingBuild.bat /s %Database\(Instance)%
Check the database versions CheckDbVersion.bat %Database\(Instance)%
>> C:\CheckDBVersion.log
Installing web services
eP-Satellite Internal Web Server
Relevant servers
eP-Satellite External Web Server
The installation of the web service component is identical for the internal and the external
web server.
Release management - eP-Satellite server
3.2 Installing the eP-Satellite server software
eP-Satellite server
34 Operating Instructions, 03/2011
Creating the directory structure:
Figure 3-1 Directory structure
Extract the archive "Server_Install_Satellite_x.x.x.x.cab": The installation package must be
located no more than one level below the drive letter; otherwise, installation problems
relating to the depth of the directory will arise. It must be ensured that none of the extracted
folders – including subfolders – has read-only access.
Example: C:\temp\server_install_Satellite_x.x.x.x
Ensure that there is an adapted settings file in the extracted installation package under
\tools\install.
Then run "setup_Server_satellite.cmd ".
Enter the following directory paths and confirm the queries as indicated in the table below:
Query Input
Install ePS Trigger Agent YES
Installationspfad %Installpath%\ePS_Services\Services\Version4
Database for logging %Database\(Instance)%
Create directories YES
Load assemblys to GAC YES
Installing language packages
Extract Server_install_Ing_yy_x.x.x.x.cab (yy = language code for the relevant language).
Run each extracted package under \tools\install\setup_install_languages.bat.
Release management - eP-Satellite server
3.2 Installing the eP-Satellite server software
eP-Satellite server
Operating Instructions, 03/2011 35
Installation path %Installpath%\ePS_Services\Services\Version4
Load assemblies to GAC YES
This exact procedure must be followed for all language packages. It is possible to do this for
more than one package at the same time. Once you have completed this process, you
should be able to see folders with each of the relevant language codes in the following
directory: %Installpath%\ePS_Services\Services\Version4\PC\bin
Installing the RANG-Service Engineer ActiveX Client download component
Extract the"ServiceEngineerActiveXClient.msi" file, contained in the
"ServiceEngineerActiveXClient_Download_Download_x.x.x.x.zip" archive file, into the
directory C:\ePS_Services\Services\Version4\PC\RemoteAccessNG\RANG\Pages.
While unzipping, activate the following options:
● "Overwrite existing files"
● "use foldernames"
● "all files"
Installing RANG-PLSL Client download component
Extract the files contained in the "RANGplslDownload_x.x.x.x.zip " archive file into the
C:\ePS_Services\Services\Version4\DynamicDownload\RANG directory.
While unzipping, activate the following options:
● "Overwrite existing files"
● "use foldernames"
● "all files"
Installing MatLab
The operator must supply the MatLab component. The following steps must be carried out:
1. Install MatLab 2007a with MatLab Compiler on any Windows PC.
2. Once it has been successfully installed in directory:
C:\Program Files\MATLAB\R2007a\toolbox\compiler\deploy\win32
copy the "MCRInstaller.exe" file to the web server.
3. Close all service consoles (MMC services).
4. Run the copy of the "MCRInstaller.exe" file and install it with the settings below.
Release management - eP-Satellite server
3.2 Installing the eP-Satellite server software
eP-Satellite server
36 Operating Instructions, 03/2011
Installation path %Installpath%\ePS_Services\AppServer_V4\matlabruntime76
Language English
Restart the system.
Installing Genesis V2
Run installation package "genesis_x.x.x.x.msi".
Installation path %Installpath%\ePS_Services\AppServer_V4\Genesis_V2
Logging directory %Logpath%\ePS_Services\AppServer_V4\Genesis_V2\Log_Genesis
In the folder %Installpath%\ePS_Services\AppServer_V4\Genesis_V2\Genesis\UAT\ edit the
following entry in the file "GenesisProcessingUnit.exe.config":
Line:
<value> %Logpath%\ePS_Services\AppServer_V4\Genesis_V2\Log_Genesis </value>
Replace with:
<value> %Logpath%\ePS_Services\AppServer_V4\Genesis_V2\Log_UAT\ </value>
Now restart the "ePS Genesis 2 PU" service.
Installing the privacy policy
Relevant servers eP-Satellite Internal Web Server
Note
In the case of a redundant configuration of the web servers, the installation of the data
protection declaration need only be executed on one web server.
The operator must provide and install the privacy policy.
Release management - eP-Satellite server
3.2 Installing the eP-Satellite server software
eP-Satellite server
Operating Instructions, 03/2011 37
This requires an xml file to be generated and transferred to the database using the
"ePS.Business.CreateDpg.exe" tool:
Datenschutzdatei.xml
<?xml version="1.0" encoding="UTF-8"?>
<dpgs>
<dpg dpgversion="01.01.01" creationtime="YYYY-MM-DD" dpgtext="deutscher Text der Datenschutz
Erklaerung" languagecode="de-DE"/>
<dpg dpgversion="01.01.01" creationtime="YYYY-MM-DD" dpgtext="English text for privacy policy"
languagecode="en-US"/>
<dpg dpgversion="01.01.01" creationtime="YYYY-MM-DD" dpgtext="deutscher Text der Datenschutz
Erklaerung" languagecode="de"/>
<dpg dpgversion="01.01.01" creationtime="YYYY-MM-DD" dpgtext="English text for privacy policy"
languagecode="en"/>
</dpgs>
This also requires the operator to enter the language codes used by IE, such as "EN-US" for
English (United States) and "ES-AR" for Spanish (Argentina) under "languagecode". The
general language codes "EN" and "DE" are provided as a fallback in the event that the more
specific ones cannot be used.
In addition, for "CreationDate", enter the creation date for the privacy policy.
Note
The version numbers under "dpgversion" must be the same for all languages.
Following this, carry out the procedure described below under
\build\output\server\production\release\bin in the unzipped installation package:
ePS.Business.CreateDpg.exe /D:%Database\(Instance)% /F:%Path\Datenschutzdatei.xml%
Parameter /D specifies the database, /F the source file to be imported.
Release management - eP-Satellite server
3.2 Installing the eP-Satellite server software
eP-Satellite server
38 Operating Instructions, 03/2011
Installing online help
Table 3- 3 German
%Installpath%\ePS_Services\Services\Version4\Help\PC\de Create directory
Unzip archive OH_DEU.zip and copy the contents to the directory created
(shown above).
"HelpIndex.de-de.xml" %Installpath%\ePS_Services\Services\Version4\PC\Common\Help\
Edit HelpIndex.xml.
Replace "dummy.htm" with:
https://%Webservices-
URL%/Webservices/Version4/Help/PC/de/OnlineHilfe.htm
Save the file as "HelpIndex.de-de.xml".
Table 3- 4 For all other languages
%Installpath%\ePS_Services\Services\Version4\Help\PC\xx
Create directory
Unzip archive OH_YYY.zip and copy the contents to the directory created
(shown above).
"HelpIndex.yy-yy.xml" %Installpath%\ePS_Services\Services\Version4\PC\Common\Help\
Edit HelpIndex.xml.
Replace "dummy.htm" with:
https://%Webservices-
URL%/Webservices/Version4/Help/PC/yy/OnlineHilfe.htm
Save the file as "HelpIndex.yy-yy.xml".
"yy" must be replaced with the relevant language code in each case, such as EN-US for
English.
Installing the Authentication Service
1. Unzip "svc_install_Satellite_x.x.x.x.cab".
2. Run the "setup_svc_satellite.cmd" using the unchanged original settings file.
Note
Never specify the installation folder as version4.
Release management - eP-Satellite server
3.2 Installing the eP-Satellite server software
eP-Satellite server
Operating Instructions, 03/2011 39
3. Enter the following directory paths and confirm the queries as indicated in the table
below:
Query Input
Installationspfad %Installpath%\ePS_Services\Services\SVC
Database %Database\(Instance)%
Database for logging %Database\(Instance)%
Load assemblys to GAC YES
Configuring the Authentication Service
The configuration of the AuthService service is performed using 3 web.config files in the
main directory AuthService and the subdirectories Ign and Req.
1. In the AuthService main directory, please make the following changes in web.config.
– Search for the following line and replace the database server "SDEVSQL\V480" by the
correct database server "%Database\(Instance)%":
<logTarget name="dbTarget"
type="ePS.Infrastructure.Logging.LogTargets.DatabaseTarget,
ePS.Infrastructure.Logging" onDuty="false" timeSpanBetweenRetriesMinutes="5"
installationName="%Database\(Instance)%" dataSource="">
– Search for the following line and replace the log path "C:\Temp\" by the required log
path "%Logpath%\ePS_Services\Services\SVC\Logfiles\":
<logTarget name="fileTarget"
type="ePS.Infrastructure.Logging.LogTargets.FileTarget, ePS.Infrastructure.Logging"
formatterName="textFileFormatter" fileNamePrefix="V481-AuthService" onDuty="true"
outputPath="%Logpath%\ePS_Services\Services\SVC\Logfiles\" fileSize="10000">
2. In the directory \AuthService\Ign, please make the following changes in the web.config
file:
– Search for the following line and change parameter "mexHttpBinding" to
"mexHttpsBinding":
<endpoint address="mex" binding="mexHttpsBinding" name="mex"
contract="IMetadataExchange" />
– Search for the following line and comment this out with a preceding "<!--" and
a subsequent ">--":
<!--<endpoint address="basic" binding="basicHttpBinding" name="basic"
bindingConfiguration="noSsl"contract="ePS.Services.AuthService.Contracts.Service.I
Authenticate" />-->
Release management - eP-Satellite server
3.2 Installing the eP-Satellite server software
eP-Satellite server
40 Operating Instructions, 03/2011
– Search for the following line and change parameter "mexHttpBinding" to
"mexHttpsBinding":
<serviceMetadata httpsGetEnabled="true" />
3. In the directory \AuthService\Req, please make the following changes in the web.config
file:
– Search for the following line twice and change parameter "mexHttpBinding" to
"mexHttpsBinding":
<endpoint address="mex" binding="mexHttpsBinding" bindingConfiguration=""
name="mex" contract="IMetadataExchange" />
– Search for the following line and comment this out with a preceding "<!--" and
a subsequent ">--":
<!--<endpoint address="basic" binding="basicHttpBinding"
bindingConfiguration="basicConfigNoSsl" name="basic"
contract="ePS.Services.AuthService.Contracts.Service.IValidate" />-->
– Search for the following line and set parameter "httpGetEnabled="false"" to activate
this, and then additionally add parameter "httpsGetEnabled="true"":
<serviceMetadata httpGetEnabled="false" httpsGetEnabled="true" />
Release management - eP-Satellite server
3.3 Configuring the internal eP-Satellite web server
eP-Satellite server
Operating Instructions, 03/2011 41
3.3 Configuring the internal eP-Satellite web server
Relevant servers eP-Satellite Internal Web Server
Web service extension
The ASP.Net 2.0 extension must be explicitly activated under IIS 6. Under "Add new Web
service extension" in the IIS Manager, specify the name and path for the associated file.
Designation Path
ASP.NET v2.0.50727 C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
Creating application pools
Create the following application pools in the Internet Information Services (IIS) Manager:
Designation Settings
.Net 2.0 • Local System Account
• Deactivate rapid-fail protection
• Deactivate recycle worker process (in minutes)
• Maximum virtual Memory 1024
.Net 2.0 PC • Local System Account
• Deactivate rapid-fail protection
• Deactivate recycle worker process (in minutes)
• Maximum virtual Memory 1024
.Net 2.0
SystemServiceComm • Local System Account
• Deactivate rapid-fail protection
• Deactivate recycle worker process (in minutes)
• Maximum virtual Memory 1536
.Net 2.0 MHComm • Local System Account
• Deactivate rapid-fail protection
• Deactivate recycle worker process (in minutes)
• Maximum virtual Memory 1536
.Net 2.0 SVC • Local System Account
• Deactivate recycle worker process (in minutes)
• Maximum virtual Memory 1536
Release management - eP-Satellite server
3.3 Configuring the internal eP-Satellite web server
eP-Satellite server
42 Operating Instructions, 03/2011
Default website
Configure the default website in the Internet Information Services (IIS) Manager as follows:
Logging Activate all; any logging path can be selected.
Keepalive Activating
Indexing Deactivating
ASP.NET Changeover to version 2.0.50727.
Documents Add file Default.aspx under "Enable default content page".
Creating the Services virtual directory
In the Internet Information Services (IIS) Manager, under the default website, now create the
new virtual directory with the alias "Services", and the directory "Path:
%Installpath%\ePS_Services\Services\Version4" and the options "Read" and "Run scripts
(such as ASP)".
Then make the following configuration changes at this directory:
Services • Redirect to: https://URL/Services/PC
• Application pool: .NET 2.0
• Documents: Add default.aspx at the first position
• Activate anonymous access
• Activate SSL (incl. 128 bits)
• Ignore Client certificates
• ASP.NET Version 2.0.50727
Release management - eP-Satellite server
3.3 Configuring the internal eP-Satellite web server
eP-Satellite server
Operating Instructions, 03/2011 43
Creating virtual directories
Create the following virtual directories in the Internet Information Services (IIS) Manager:
/Services/APIServices • A directory located on this computer
• Local Path:
%Installpath%\ePS_Services\Services\Version
4\ApiServices
• Read, Log Visits
• Application Name APIServices
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Activate anonymous access
• Activate SSL (incl. 128 bits)
• Ignore Client certificates
• ASP.NET Version 2.0.50727
/Services/HMI • A directory located on this computer
• Local Path:
%Installpath%\ePS_Services\Services\Version
4\HPortal
• Read, Log Visits
• Application Name HMI
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Activate anonymous access
• Activate SSL (incl. 128 bits)
• Ignore Client certificates
• ASP.NET Version 2.0.50727
/Services/MHC • A directory located on this computer
• Local Path:
%Installpath%\ePS_Services\Services\Version
4\MHCProxy
• Read, Log Visits
• Application Name MHC
• Execute permissions: Scripts only
• Application pool: .NET 2.0 MHComm
• Activate anonymous access
• Activate SSL (incl. 128 bits)
• Ignore Client certificates
• ASP.NET Version 2.0.50727
Release management - eP-Satellite server
3.3 Configuring the internal eP-Satellite web server
eP-Satellite server
44 Operating Instructions, 03/2011
/Services/MHCProxy • A directory located on this computer
• Local Path:
%Installpath%\ePS_Services\Services\Version
4\MHCProxy
• Read, Log Visits
• Application Name MHCProxy
• Execute permissions: Scripts only
• Application pool: .NET 2.0 MHComm
• Activate anonymous access
• Denied Access, granted 127.0.0.1
• Ignore Client certificates
• ASP.NET Version 2.0.50727
/Services/PC • A directory located on this computer
• Local Path:
%Installpath%\ePS_Services\Services\Version
4\PPortal
• Read, Log Visits
• Application Name PC
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Activate anonymous access
• Activate SSL (incl. 128 bits)
• Ignore Client certificates
• ASP.NET Version 2.0.50727
/Services/SatelliteComm • A directory located on this computer
• Local Path:
%Installpath%\ePS_Services\Services\Version
4\SatelliteComm
• Read, Log Visits
• Application Name SatelliteComm
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Activate anonymous access
• Denied Access, granted 193.202.96.40 (ePS
Network Services ASPServer)
• Activate SSL (incl. 128 bits)
• Accept Client certificates
• ASP.NET Version 2.0.50727
Release management - eP-Satellite server
3.3 Configuring the internal eP-Satellite web server
eP-Satellite server
Operating Instructions, 03/2011 45
/Services/SatelliteOperatingComm • A directory located on this computer
• Local Path:
%Installpath%\ePS_Services\Services\Version
4\SatelliteOperatingComm
• Read, Log Visits
• Application Name SatelliteOperatingComm
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Activate anonymous access
• Denied Access, granted 193.202.96.40 (ePS
Network Services ASPServer)
• Activate SSL (incl. 128 bits)
• Accept Client certificates
• ASP.NET Version 2.0.50727
/SVC/ • A directory located on this computer
• Local Path:
%Installpath%\ePS_Services\Services\SVC
• Read, Log Visits
• Application Name SVC
• Execute permissions: Scripts only
• Application pool: .NET 2.0 SVC
• Activate anonymous access
• Activate SSL (incl. 128 bits)
• Ignore Client certificates
• ASP.NET Version 2.0.50727
/SVC/AuthService/ • A directory located on this computer
• Local Path:
%Installpath%\ePS_Services\Services\SVC\Au
thService
• Read, Log Visits
• Application Name AuthService
• Execute permissions: Scripts only
• Application pool: .NET 2.0 SVC
• Activate anonymous access
• Activate SSL (incl. 128 bits)
• Ignore Client certificates
• ASP.NET Version 2.0.50727
Release management - eP-Satellite server
3.3 Configuring the internal eP-Satellite web server
eP-Satellite server
46 Operating Instructions, 03/2011
/Webservices/ • A directory located on this computer
• Local Path:
%Installpath%\ePS_Services\Services
• Read, Log Visits
• Application Name Webservices
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Documents: Add default.aspx at the first
position
• Activate anonymous access
• Activate SSL (incl. 128 bits)
• Ignore Client certificates
• ASP.NET Version 2.0.50727
/Webservices/Version4 • The designated directory
• Read, Log Visits
• Application Name Version4
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Activate anonymous access
• Activate SSL (incl. 128 bits)
• Ignore Client certificates
• ASP.NET Version 2.0.50727
/WebServices/Version4/BA • The designated directory
• Read, Log Visits
• Application Name BA
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Integrated Windows authentication
• Activate SSL (incl. 128 bits)
• Ignore Client certificates
• ASP.NET Version 2.0.50727
Release management - eP-Satellite server
3.3 Configuring the internal eP-Satellite web server
eP-Satellite server
Operating Instructions, 03/2011 47
/Webservices/Version4/DynamicDownload • The designated directory
• Read, Log Visits
• Application Name DynamicDownload
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Activate anonymous access
• Activate SSL (incl. 128 bits)
• Ignore Client certificates
• ASP.NET Version 2.0.50727
• Select "Insert wildcard application map" and
add access to
C:\WINDOWS\Microsoft.NET\Framework\
v2.0.50727\aspnet_isapi.dll.
"Verify that file exists" must also be
deactivated:
/Webservices/ Version4/HMI • The designated directory
• Read, Log Visits
• Application Name HMI
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Activate anonymous access
• Activate SSL (incl. 128 bits)
• Ignore Client certificates
• ASP.NET Version 2.0.50727
/Webservices/Version4/HMIServiceComm • The designated directory
• Read, Log Visits
• Application Name HMIServiceComm
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Activate anonymous access
• Denied Access, granted 127.0.0.1
• Ignore Client certificates
• ASP.NET Version 2.0.50727
Release management - eP-Satellite server
3.3 Configuring the internal eP-Satellite web server
eP-Satellite server
48 Operating Instructions, 03/2011
/Webservices/Version4/MHC • A directory located on this computer
• Local Path:
%Installpath%\ePS_Services\Services\Version
4\MHComm
• Read, Log Visits
• Application Name MHC
• Execute permissions: Scripts only
• Application pool: .NET 2.0 MHComm
• Activate anonymous access
• Denied Access, granted 127.0.0.1
• Ignore Client certificates
• ASP.NET Version 2.0.50727
/Webservices/Version4/PC • The designated directory
• Read, Log Visits
• Application Name PC
• Execute permissions: Scripts only
• Application pool: .NET 2.0 PC
• Activate anonymous access
• Activate SSL (incl. 128 bits)
• Ignore Client certificates
• ASP.NET Version 2.0.50727
/Webservices/Version4/PCServiceComm • The designated directory
• Read, Log Visits
• Application Name PCServiceComm
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Activate anonymous access
• Denied Access, granted 127.0.0.1
• Ignore Client certificates
• ASP.NET Version 2.0.50727
Release management - eP-Satellite server
3.3 Configuring the internal eP-Satellite web server
eP-Satellite server
Operating Instructions, 03/2011 49
/Webservices/Version4/SystemServiceComm • The designated directory
• Read, Log Visits
• Application Name SystemServiceComm
• Execute permissions: Scripts only
• Application pool: .NET 2.0
SystemServiceComm
• Activate anonymous access
• Denied Access, granted 127.0.0.1
• Ignore Client certificates
• ASP.NET Version 2.0.50727
/Webservices/Version4/ServiceRegistryService • The designated directory
• Read, Log Visits
• Application Name ServiceRegistryService
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Activate anonymous access
• Ignore Client certificates
• ASP.NET Version 2.0.50727
Release management - eP-Satellite server
3.4 Configuring the external eP-Satellite web server
eP-Satellite server
50 Operating Instructions, 03/2011
3.4 Configuring the external eP-Satellite web server
Relevant servers eP-Satellite External Web Server
Web Service Extension
The ASP.Net 2.0 extension must be explicitly activated under IIS 6. In the Internet
Information Services (IIS) Manager, under "Add new Web service extension", specify the
name and path to the associated file.
Designation Path
ASP.NET v2.0.50727 C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
Creating application pools
Create the following application pools in the Internet Information Services (IIS) Manager:
Designation Settings
.Net 2.0 • Local System Account
• Deactivate rapid-fail protection
• Deactivate recycle worker process (in minutes)
• Maximum virtual memory 1024
.Net 2.0 SystemServiceComm • Local System Account
• Deactivate rapid-fail protection
• Deactivate recycle worker process (in minutes)
• Maximum virtual memory 1536
Default website
Configure the default website in the Internet Information Services (IIS) Manager as follows:
Logging Activate all; any logging path can be selected
Keepalive Activating
Indexing Deactivating
ASP.NET Changeover to version 2.0.50727.
Documents Add file Default.aspx under "Enable default content page".
Creating the Services virtual directory
In the Internet Information Services (IIS) Manager, under the default website, now create the
new virtual directory with the alias "Services", and the directory "Path:
%Installpath%\ePS_Services\Services\Version4" and the options "Read" and "Run scripts
(such as ASP)".
Release management - eP-Satellite server
3.4 Configuring the external eP-Satellite web server
eP-Satellite server
Operating Instructions, 03/2011 51
Then make the following configuration changes at this directory:
Services • Redirect to: https://URL/Services/PC
• Application pool: .NET 2.0
• Documents: Add default.aspx at the first position
• Activate anonymous access
• Activate SSL (incl. 128 bits)
• Ignore Client certificates
• ASP.NET Version 2.0.50727
Creating virtual directories
Create the following virtual directories in the Internet Information Services (IIS) Manager:
/Services/SatelliteComm • A directory located on this computer
• Local Path:
%Installpath%\ePS_Services\Services\Version4\Sa
telliteComm
• Read, Log Visits
• Application Name SatelliteComm
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Activate anonymous access
• Denied Access, granted 193.96.202.40 (ePS
Network Services ASP server)
• Activate SSL (incl. 128 bits)
• Accept Client certificates
• ASP.NET Version 2.0.50727
Release management - eP-Satellite server
3.4 Configuring the external eP-Satellite web server
eP-Satellite server
52 Operating Instructions, 03/2011
/Services/SatelliteOperatingComm • A directory located on this computer
• Local Path:
%Installpath%\ePS_Services\Services\Version4\Sa
telliteOperatingComm
• Read, Log Visits
• Application Name SatelliteOperatingComm
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Activate anonymous access
• Denied Access, granted 193.96.202.40 (ePS
Network Services ASP server)
• Activate SSL (incl. 128 bits)
• Accept Client certificates
• ASP.NET Version 2.0.50727ASP.NET Version
2.0.50727
/Webservices/ • A directory located on this computer
• Local Path: %Installpath%\ePS_Services\Services
• Read, Log Visits
• Application Name Webservices
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Activate anonymous access
• Activate SSL (incl. 128 bits)
• Ignore Client certificates
• ASP.NET Version 2.0.50727
/Webservices/Version4 • The designated directory
• Read, Log Visits
• Application Name Version4
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Activate anonymous access
• Activate SSL (incl. 128 bits)
• Ignore Client certificates
• ASP.NET Version 2.0.50727
Release management - eP-Satellite server
3.4 Configuring the external eP-Satellite web server
eP-Satellite server
Operating Instructions, 03/2011 53
/WebServices/Version4/BA • The designated directory
• Read, Log Visits
• Application Name BA
• Execute permissions: Scripts only
• Application pool: .NET 2.0
• Integrated Windows authentication
• Activate SSL (incl. 128 bits)
• Ignore Client certificates
• ASP.NET Version 2.0.50727
/Webservices/Version4/SystemServiceCom
m • The designated directory
• Read, Log Visits
• Application Name SystemServiceComm
• Execute permissions: Scripts only
• Application pool: .NET 2.0 SystemServiceComm
• Activate anonymous access
• Denied Access, granted 127.0.0.1
• Ignore Client certificates
• ASP.NET Version 2.0.50727
Configuring the SMTP service
If the web server is also used for sending e-mails, the default SMTP virtual server for IIS
must be configured in the Internet Information Services (IIS) Manager.
The most important settings for the SMTP virtual server are:
General • IP Address: All unassigned
• Enable Logging: W3C Extended
Access • Authentication: Anonymous Access
• Relay: Enter only the list below and %Internal Web Server-IP%, %External Web
Server-IP%, %Reporting Web Server-IP%.
Configuring "Server2Server" communication
Relevant servers eP-Satellite External Web Server
The eP-Satellite must have already been fully installed before the HASH value and coded
password can be generated for the first time. The values generated must then be entered in
the relevant configuration files.
A user who is a member of the bizAdmin group is required for authentication. The relevant
user must be added to the bizAdmin group for this purpose.
Release management - eP-Satellite server
3.4 Configuring the external eP-Satellite web server
eP-Satellite server
54 Operating Instructions, 03/2011
Generating the HASH value
On the web servers, open the following page in the browser:
https://localhost/Webservices/Version4/SystemServiceComm/Login/
Then select the following options:
Encryption SHA1
Password %HASH Password%
In the following folders - under password - enter the HASH value generated in the particular
web.config:
%Installpath%\ePS_Services\Services\Version4\SystemServiceComm
%Installpath%\ePS_Services\Services\Version4\PCServiceComm
%Installpath%\ePS_Services\Services\Version4\HMIServiceComm
%Installpath%\ePS_Services\Services\Version4\ServiceRegistryService
web.config
<user name="server2server" password="<HASH WERT>" />
Coding the password
Under \build\output\server\production\release\bin in the unzipped package, call file
ePS.Infrastructure.EncoderNT.exe as follows:
ePS.Infrastructure.EncoderNT.exe "%HASH Password%"
Copy the result to the central web.config file under
%Installpath%\ePS_Services\Services\Version4 in the Version Management area.
web.config
serverUserName="server2server" serverPassword="Codiertes Passwort">
Release management - eP-Satellite server
3.5 Database logging
eP-Satellite server
Operating Instructions, 03/2011 55
3.5 Database logging
Installing the logging service
Relevant servers eP-Satellite database server
You will find the files for the service in the unzipped installation package of the web server,
under:
build\output\server\production\release\bin
The following files must be copied to folder %Installpath%\ePS_services\DBLogging :
Figure 3-2 List of files
Using the prompt, switch to the installation directory and execute the following command:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe
ePS.Infrastructure.Logging.WindowsService.exe
Release management - eP-Satellite server
3.5 Database logging
eP-Satellite server
56 Operating Instructions, 03/2011
Starting the service
The service is started from the Services panel. The Startup Type setting for the service must
be changed to "Automatic".
Figure 3-3 Services
Setting up the "MessageQueue" Windows component
Installing MessageQueue:
eP-Satellite External Web Server
Internal eP-Satellite web server
eP-Satellite database server
Relevant servers
eP-Satellite application render server
MessageQueue is subsequently installed under Add or Remove Programs, in the Windows
Components area under Application Server.
Release management - eP-Satellite server
3.5 Database logging
eP-Satellite server
Operating Instructions, 03/2011 57
Figure 3-4 Message Queuing
Creating MessageQueue logging
Relevant servers eP-Satellite database server
In the Computer Management console, create a new private MessageQueue called
"logentryqueue".
NOTICE
It is absolutely essential that the MessageQueue is created as a transactional queue. It will
not be possible to change this later.
Release management - eP-Satellite server
3.5 Database logging
eP-Satellite server
58 Operating Instructions, 03/2011
Figure 3-5 Computer Management
The queue security must be adapted so that the user of the logging service has permission
to write to the queue. For example:
Release management - eP-Satellite server
3.5 Database logging
eP-Satellite server
Operating Instructions, 03/2011 59
Figure 3-6 Properties
Activating database logging
eP-Satellite External Web Server
Relevant servers
Internal eP-Satellite web server
In order to activate database logging, the names of the database server and the private
MessageQueue must be adapted in the web.config files of the web server and render server.
The corresponding configuration files can be found in the following directories:
%Installpath%\ePS_Services\Services\Version4 (eP-Satellite Web Server)
%RenderInstPath%\Service\RenderService (eP-Satellite Render Server)
The entry can be found in the web.config file in the wcfTarget section and must be adapted
as follows:
(<endpoint address="net.msmq://%Database\(Instance)%/private/logentryqueue")
Release management - eP-Satellite server
3.5 Database logging
eP-Satellite server
60 Operating Instructions, 03/2011
<logTarget
name="wcfTargetData"
type="ePS.Infrastructure.Logging.LogTargets.WcfTarget,
ePS.Infrastructure.Logging" onDuty="false"
endpointAdress="net.msmq://%Database\(Instance)%/private/logentryqueue">
<logFilters>
<logFilter name="wcfTargetDataSubsetSeverityFilter" />
</logFilters>
</logTarget>
The parameter preceding this line, "onDuty=false", will now need to be changed to
"onDuty=true". Once IIS has been restarted, database logging will be activated for the
relevant server.
Release management - eP-Satellite server
3.6 Activating PKI login
eP-Satellite server
Operating Instructions, 03/2011 61
3.6 Activating PKI login
1. Step
In the first step, the "PKI" directory must be configured in the IIS Manager below the virtual
"PC" directory as subsequently shown:
In order to use the PKI login, this must be activated in the files "web.config" of the web
applications PC and PPortal:
<ePS.Business>
<security …>
<allowCertificateLogin>true</allowCertificateLogin>
</security>
</ePS.Business>
The default setting is "false".
Release management - eP-Satellite server
3.6 Activating PKI login
eP-Satellite server
62 Operating Instructions, 03/2011
2. Step
In a second step, the certificates provided by the company operating the eP-Satellite must
be imported:
For this purpose, the issuing instances (CA) of all client X509 certificates, which confirm an
e-mail address saved in the ePS system and which should be used for a login, must be
saved under "Store Trusted Root Certification Authorities" of the web server using the "Snap-
in certificates of MMC".
1. In the dialog box, select "Add Standalone Snap-In" "Certificates" and confirm with "Add".
2. In the dialog box "Certificates snap-in" activate the option button "Computer account" and
confirm with "Next".
3. In the dialog box "Select Computer" activate the option button "Local computer" and
confirm with "Finish".
Then, in the left-hand window of "mmc", install the corresponding CA certificate in the folder
"Certificates" in the area of "Trusted Root Certification Authorities".
Press the right-hand mouse key and select "All Tasks > Import".
Release management - eP-Satellite server
3.6 Activating PKI login
eP-Satellite server
Operating Instructions, 03/2011 63
Figure 3-7 Importing "Intermediate Certificates"
Also carry out the steps above for the "Intermediate Certificates". However, these are then
imported under "Intermediate Certification Authorities".
Then, each of these certificates must also be specified in the "web.config" of the PPortal
application:
<security sessionTicketTimeoutMinutes…>
…
<trustedRootAuthorities>
<ra x509FindType="FindBySubjectName" key="%Name des Certification Authority
Zertifikats%" />
</trustedRootAuthorities>
…
</security>
Release management - eP-Satellite server
3.6 Activating PKI login
eP-Satellite server
64 Operating Instructions, 03/2011
3. Step
In a third step, the corresponding user must be created or selected in the PC-UI under
administration / user - and then a selection must be made under the menu item "Log on
with":
Figure 3-8 Creating users with authentication
Password: Authentication is only possible using a password
Password/certificate: Authentication is possible using a password as well as with a
certificate
Certificate: Authentication is only possible using a certificate
Release management - eP-Satellite server
3.7 First commissioning of the eP-Satellite and testing of its functions
eP-Satellite server
Operating Instructions, 03/2011 65
3.7 First commissioning of the eP-Satellite and testing of its functions
Configuration
To enable you to check the installations and carry out any other configurations, users and
organizations will now need to be created on the system. The following section describes the
web applications that are required for this.
Business Administration portal
The %BA-URL% is opened in a browser. The "bizAdmin" group user created in Section
Preparing for installation (Page 30) is used as the user.
Once they have successfully logged in, the following menu is displayed:
Figure 3-9 Managing eP-Satellite
An organization is now created in the "Manage organizations" section. In all cases, this has a
user administrator who is used when users in the respective organizations are logged in and
created for the first time.
Overview of organizations
This is where organizations can
be deleted, or new ones added.
Release management - eP-Satellite server
3.7 First commissioning of the eP-Satellite and testing of its functions
eP-Satellite server
66 Operating Instructions, 03/2011
Create an organization
This is where all the data relating
to the organization and its
administrator is entered.
Immediately after the organization has been created, a password generated for the
administrator is displayed.
PC portal
It is now possible to log into the PC portal (%PC-URL%) using the organizations created in
this way.
Figure 3-10 Login
Release management - eP-Satellite server
3.7 First commissioning of the eP-Satellite and testing of its functions
eP-Satellite server
Operating Instructions, 03/2011 67
Once you have successfully logged in, the password must be changed and the terms of the
privacy policy accepted. You will then see the following screen:
Figure 3-11 Register after successful login
A new user is created under the menu command "Administration" → "Users":
Overview of users
This is where users can be
deleted, or new ones added.
Release management - eP-Satellite server
3.7 First commissioning of the eP-Satellite and testing of its functions
eP-Satellite server
68 Operating Instructions, 03/2011
Create a user
This is where all the data relating
to the user is entered.
This user will now be able to work in the PC portal. Once they have successfully logged in,
their password must be changed again and the terms of the privacy policy accepted.
Release management - eP-Satellite server
3.8 Configuring the connection
eP-Satellite server
Operating Instructions, 03/2011 69
3.8 Configuring the connection
Communications link
Relevant servers eP-Satellite External Web Server
It must be possible for https communication to take place between the eP-Satellite
web server and the ePS Network Services ASP server in both directions. For this purpose,
both directions of communication require certificates, which are used in order to authenticate
both the server and the client.
Call %BA-URL% on the web server and set up communication under the menu command
"Manage eP-Satellite" as shown below.
Figure 3-12 eP-Satellite details
Settings on the eP-Satellite:
Parameter Entry
eP-Satellite name %SatelliteName%
eP-Satellite URL ePS Network Services
(https://www.epsnetwork.com/Services)
Method Certificate
Mapping type Many-to-1
Certificate field Subject
Subfield CN
Incoming authentication
(what is coming from the ASP
server to the satellite)
Criterion ASP domain (top level)
Release management - eP-Satellite server
3.8 Configuring the connection
eP-Satellite server
70 Operating Instructions, 03/2011
Parameter Entry
Method Certificate
Outgoing authentication
(what the satellite sends to the
ASP server) Certificate Select own official certificate
(check information on selected
certificate)
The settings under "Data layer" and "Transport layer" are identical.
It is also possible to activate the operating interface on the eP-Satellite. While it is possible to
create organizations while the interface is inactive, logging information cannot be fetched
from the ASP.
Revocation list
The system supports the use of the revocation list.
The default setting is "deactivated"; in other words, the certificate's validity and the name of
the party who issued it are checked, but it is not compared with the "revocation list". The
setting can be switched to "activated" using the central web.config file on both pages:
<certificates useCertificatesInternally="false" revocationMode="NoCheck">
change to:
<certificates useCertificatesInternally="false" revocationMode="Online">
or:
<certificates useCertificatesInternally="false" revocationMode="Offline">
Offline A revocation check is made using a cached certificate revocation list (CRL).
Online A revocation check is made using an online certificate revocation list (CRL).
NOTICE
"Online" assumes that the server has access to the server (Internet connection) which is
able to deliver the revocation list (e.g. verisign).
Release management - eP-Satellite server
3.9 Installing Render Services
eP-Satellite server
Operating Instructions, 03/2011 71
3.9 Installing Render Services
Precondition
ePS Render Services only needs to be installed if you are using solution line clients.
Installing ePS Render Services
Relevant servers eP-Satellite application render server
First stop the IIS web server service, then run file RenderServer_x.x.x.x.msi and carry out
the installation procedure as described below.
Enter the following information during the setup routine:
Query Input
Location %RenderInstPath%\Service\RenderService
Password Enter %RenderPassword% and then click CreateNewUser.
Hosts %WebServerDomain%
Logdirectory %RenderLogPath%\Service\RenderService\LOG
Figure 3-13 Render Services
Release management - eP-Satellite server
3.9 Installing Render Services
eP-Satellite server
72 Operating Instructions, 03/2011
The user created during the setup routine then needs to be assigned the following
authorizations:
Authorizations Access method
Directory C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ Temporary
ASP.NET files
Modify
C:\Windows\temp directory Read
Registry entry: Full control
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog
Web Service Extension
The ASP.Net 2.0 extension must be explicitly activated under IIS 6. Under "Add new Web
service extension" in the IIS Manager, specify the name and path for the associated file.
Designation Path
ASP.NET v2.0.50727 C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
The default webpage must then be changed over to ASP.NET 2.0.50727.
Adapting the web.config file
In directory %Installpath%\ePS_Services\Services\RenderServer, edit the web.config file and
add the colored entries.
<add key="renderer.defFntSize.800x600" value="20"/>
<add key="renderer.defFntSize.895x682" value="20"/>
<add key="renderer.defFntSize.1024x768" value="20"/>
<add key="handshake.renderServiceUrl" value=
"https://%RenderServiceURL%/IERenderService/IERenderService.asmx"/>
</appSettings>
<system.web>
Configuring Internet Explorer
If the eP-Satellite application render server does not have access to the Internet which it can
use to check the revocation list (CRL), the server's Internet configuration will need to be
adapted.
Log in to the Windows operating system with the "RenderService" user you have created,
then launch Internet Explorer.
Go to "Tools" → "Internet Options" → "Advanced", and deactivate options "Check for
publisher's certificate revocation" and "Check for server certificate revocation".
Release management - eP-Satellite server
3.9 Installing Render Services
eP-Satellite server
Operating Instructions, 03/2011 73
Figure 3-14 Internet Options
The %HMI-URL% is then added as a trusted site.
Release management - eP-Satellite server
3.10 Installing and configuring the RANG server
eP-Satellite server
74 Operating Instructions, 03/2011
3.10 Installing and configuring the RANG server
3.10.1 Installing the RANG Servers
Servers involved eP-Satellite RANG server
Precondition
In order to install the eP-Satellite RANG server, you require the "epsrang-x.x.x.i386.rpr"
installation package.
Hardware/Software
Operating system SuSE Linux Enterprise Server 10, 32Bit Version, Service Pack 2
RAM Minimum of 512 MB, 4 GB is recommended
Disk space Minimum,150 MB
Recommended 150 MB /opt and 100 MB /var
Processor Minimum,1.6 GHz, recommended, QuadCore 2 GHz
Packages required Minimum installation plus:
• openssl
• libjpeg
• libxml2
Installation
Note
The installation is made using the DOS shell!
1. Start the DOS shell via "Start" → "Run..." → "rpm-ivh epsrang-x.x.x. –x .i386.rpm".
2. Navigate to the installation path: opt/epsrang/
3. Navigate to the log files in the following directory: /var/epsrang/log/
The following log files are available:
– confsrv.log - Contains status messages of the server
– confsrv.stderr - Contains messages when starting/stopping the server
Release management - eP-Satellite server
3.10 Installing and configuring the RANG server
eP-Satellite server
Operating Instructions, 03/2011 75
Starting / stopping the service
Starting and stopping the service using the following DOS shell commands:
Start /etc/init.d/epsrang
Stop /etc/init.d/epsrang
The service runs as /opt/epsrang/bin/exes/confsrv (several instances).
3.10.2 Configuring the RANG server
Servers involved eP-Satellite RANG server
General configuration
● Call the page using the following address: https://%Remoteaccess-URL%/Web/config.
● Use the following standard access data:
– user: config
– PW: config
The server is configured using the "General configuration" input window.
1. For "Public address" enter the URL of the SSL certificate.
2. Select the appropriate certificate, the password file and the private key.
3. Press the "Apply changes" button in order to accept the settings.
4. Stop the RANG server using the DOS shell command: /etc/init.d/epsrang stop.
5. Then subsequently start the RANG server using the DOS shell command:
/etc/init.d/epsrang start.
Note
Properties of the password file
The password file must only include one line break (file size, 2 bytes), it must not be
absolutely empty or contain other characters.
Release management - eP-Satellite server
3.10 Installing and configuring the RANG server
eP-Satellite server
76 Operating Instructions, 03/2011
Figure 3-15 Configuring the RANG server
Configuring the security area
1. Open the "Authentication parameter" window.
2. Enter the URL for the "Authentication Service".
3. Change the port to 443.
4. Activate the use of SSL.
5. Change the access data under "General authorization" and under "Configuration
authorization".
6. Enter "mux" under "Username" - as well as a name that you have selected under "config".
7. Under "Password", allocate a new password and confirm this by repeating it in the entry
field below.
Release management - eP-Satellite server
3.10 Installing and configuring the RANG server
eP-Satellite server
Operating Instructions, 03/2011 77
8. To test the authorization, enter the new username and password under "Test
authentication".
9. Press the "Test" button to start the authorization test.
Figure 3-16 Configuring authentication
Release management - eP-Satellite server
3.10 Installing and configuring the RANG server
eP-Satellite server
78 Operating Instructions, 03/2011
eP-Satellite server
Operating Instructions, 03/2011 79
Release management - ePS Reporting Services 4
4.1 Introduction
Overview
ePS Reporting Services is an optional service used to generate customized reports. It is
installed on separate systems (a web server and a database server) and is an extension of
Microsoft SQL Reporting Services.
The installation instructions refer to this type of two-server configuration; it is not
recommended that you deviate from this.
4.2 Configuring Microsoft Reporting Services
Basic configuration of the eP-Satellite application reporting web server
Relevant servers eP-Satellite application reporting web server
Following successful installation, the report server will need to be configured. To do this,
open the Reporting Services Configuration Manager from Programs\Microsoft SQL Server
2005/Configuration Tools.
This is where you connect to the ePS application reporting web server.
Figure 4-1 Instance Selection
A new database now needs to be created in "Database Setup".
Release management - ePS Reporting Services
4.2 Configuring Microsoft Reporting Services
eP-Satellite server
80 Operating Instructions, 03/2011
The following window opens under "New":
Figure 4-2 SQL Server Connection
Here, please enter the relevant parameters from the installation insert.
Server Name %ReportingDatabase/(ReportingInstance)%
Database Name ReportServer
Confirm the window with "OK" and then accept the changes with "Apply".
Authorizations for the databases
Relevant servers eP-Satellite application reporting database server
In the SQL Server Management Studio, connect to the relevant
%ReportingDatabase/(ReportingInstance)% and create a new login under <Security> →
<Logins>:
Login Name ePSRepSQLServiceUser
SQL Server authentification
Password %ePSRepSQLServiceUserPassword
%
Enforce password policy Activate
General
Enforce password expiration Deactivate
Release management - ePS Reporting Services
4.2 Configuring Microsoft Reporting Services
eP-Satellite server
Operating Instructions, 03/2011 81
Default database master
Default language <default>
Master Public,RSExecRole
ReportServer Public,RSExecRole
User Mapping
(ePSRepSQLServiceUser)
ReportServer TempDB Public,RSExecRole
The image below shows the completed settings:
Figure 4-3 Login
Changing the credentials for connection
Relevant servers eP-Satellite application reporting web server
Change the values for the user you have just created under "Database Connection" to the
following:
Credentials Type SQL Server Credentials
Account Name ePSRepSQLServiceUser
Password %ePSRepSQLServiceUserPassword%
Release management - ePS Reporting Services
4.2 Configuring Microsoft Reporting Services
eP-Satellite server
82 Operating Instructions, 03/2011
Domain account
Reporting Web Services is normally configured in IIS using "Windows Authentication". Since
the eP-Satellite runs as a web application in IIS under user "Anonymous", the SQL Server
Reporting Web Services component used for redirection must also run under "Anonymous".
For this purpose, a domain account that is entered as "Anonymous" for the Report Viewer
must be created. In the SQL Server, this user must be assigned the role "RSExecRole" for
both the report server and the ReportServer TempDB database.
Create the user as follows:
First Name ePS Reporting
Last Name WebUser
Full Name ePSReporting WebUser
User Logon Name ePSReportingWebUser@%Domain%
User Logon Name (pre-Windows 2000) ePSReportingWebUser
Password ePSReportingWebUserPassword
User cannont change password Activated
Password never expires Activated
Figure 4-4 User
In the SQL Server Management Studio, connect to the relevant
%ReportingDatabase/(ReportingInstance)% and create a new login under <Security> →
<Logins>. Following this, search for the newly created user ("ePSReportingWebUser") using
"Search" and confirm them.
Release management - ePS Reporting Services
4.2 Configuring Microsoft Reporting Services
eP-Satellite server
Operating Instructions, 03/2011 83
Figure 4-5 Select User
Under "User Mappings", assign the following authorizations to this user again:
ReportServer Public,RSExecRole
User Mapping
(ePSRepSQLServiceUser) ReportServer TempDB Public,RSExecRole
Figure 4-6 Login
Release management - ePS Reporting Services
4.2 Configuring Microsoft Reporting Services
eP-Satellite server
84 Operating Instructions, 03/2011
Authorizations in the SQL Server Reporting Web Services
Relevant servers eP-Satellite application reporting web server
Call the URL https://localhost/reports in the browser window on the web server and switch to
"Properties". This is where you create a "New role assignment":
Group or user name ePSReportingWebUser
Role Browser, Content Manager
Figure 4-7 Role assignment
To check these settings, call the URL https://localhost/Reportserver in the browser window. If
the website is displayed without problems, Reporting Services has been configured correctly.
Authorizations for the web server
Relevant servers eP-Satellite application reporting web server
Under "Directory Security" of the virtual "Report Server" directory in the IIS Manager, you
now need to change the authentication methods.
Enable anonymous access Activate
User name Domain\ePSReportingWebUser
Password %ePSReportingWebUserPassword%
Integrated Windows authentication Activate
Then all .asmx files apart from ReportServer2005.asmx of the Anonymous Access must be
removed again from all subdirectories (exception: pages).
Release management - ePS Reporting Services
4.3 Installing ePS Reporting Services
eP-Satellite server
Operating Instructions, 03/2011 85
4.3 Installing ePS Reporting Services
Installing the database component
Relevant servers eP-Satellite application reporting database server
The satellite.settings file created in Section Preparing for installation (Page 30) is used for
installing ePS Reporting Services.
Extract the archive "Reporting_install _Satellite_x.x.x.x.cab": The installation package must
be located no more than one level below the drive letter; otherwise, installation problems
relating to the depth of the directory will arise. It must be ensured that none of the extracted
folders – including subfolders – has read-only access.
Example: C:\temp\server_install_ Satellite_x.x.x.x.
The adapted settings file must be copied to the \tools\UserSettings directory of the unzipped
installation package.
In the unzipped installation package, edit the setup_Reporting_production.bat script under
\tools\install, change parameter "production.settings" to "satellite.settings", then run the
script.
Install DatabaseServer for ePS Reporting YES
Install Web Server for ePS Reporting NO
Installing the web server component
Relevant servers eP-Satellite application reporting web server
The satellite.settings file created in Section Preparing for installation (Page 30) is used for
installing ePS Reporting Services.
Extract the archive "Reporting_install_Satellite_x.x.x.x.cab ": The installation package must
be located no more than one level below the drive letter; otherwise, installation problems
relating to the depth of the directory will arise. It must be ensured that none of the extracted
folders – including subfolders – has read-only access.
Example: C:\temp\server_install_ Satellite_x.x.x.x.
The adapted settings file must be copied to the \tools\UserSettings directory of the unzipped
installation package.
In the unzipped installation package, edit the setup_Reporting_production.bat script under
\tools\install, change parameter "production.settings" to "satellite.settings", then run the
script.
Release management - ePS Reporting Services
4.3 Installing ePS Reporting Services
eP-Satellite server
86 Operating Instructions, 03/2011
Install DatabaseServer for ePS Reporting NO
Install Web Server for ePS Reporting YES
Checking the reports delivery service
Checking the reports
To check whether the report delivery service is working, the reports which are available can
be viewed via the SQL Server Reporting Services web interface.
To do this, open the URL https://localhost/reports in the browser on the reporting web server.
Figure 4-8 SQL Server Reporting Services
Authorizations on the reporting database
Relevant servers eP-Satellite application reporting database server
Once ePS Reports has been installed, the user created prior to this
("ePSReportingWebUser") must also be allocated the appropriate authorizations on the
database.
In the SQL Server Management Studio, connect to the relevant
%ReportingDatabase/(ReportingInstance)%.
Open the properties of the ePSReportingWebUser user, and assign the "ReportingUsers"
role under "User Mapping" on the ePS reporting database.
Release management - ePS Reporting Services
4.4 Final steps
eP-Satellite server
Operating Instructions, 03/2011 87
4.4 Final steps
4.4.1 Settings in the virtual directories
Final steps
Relevant servers eP-Satellite application reporting web server
The final steps now involve making the following settings in the respective virtual directories.
/ePSReportingServiceComm A directory located on this computer
Local Path: C:\eps-services\EpsReportingServiceComm
Read, Log Visits, Index this resource
Application Name EpsReportingServiceComm
Execute permissions: Scripts only
Application pool: .ReportServer
Activate anonymous access (ePSReportingWebUser)
Denied Access
Granted:
Own internal IP address
Official IP address behind the DNS name
Official web server IP addresses
ASP.NET Version 2.0.50727
/Reports A directory located on this computer
Local Path: C:\Program Files\Microsoft SQL
Server\MSSQL.2\Reporting Services\ReportManager
Read, Log Visits
Application Name Report Server Interface
Execute permissions: Scripts and Executables
Application pool: ReportServer
Activate anonymous access (ePSReportingWebUser)
Denied Access
Granted:
Own internal IP address
Official IP address behind the DNS name
ASP.NET Version 2.0.50727
Release management - ePS Reporting Services
4.4 Final steps
eP-Satellite server
88 Operating Instructions, 03/2011
/ReportServer Only apply on asmx files
Denied Access
Granted:
Own internal IP address
Official IP address behind the DNS name
4.4.2 Testing the ePS Reporting Services installation
In order to perform a final function test, ePS Reporting Services is accessed from the
product:
● This is demonstrated using the Business Administration portal in the images below:
Figure 4-9 Managing reports
Release management - ePS Reporting Services
4.4 Final steps
eP-Satellite server
Operating Instructions, 03/2011 89
Figure 4-10 Report name
● Additionally, ePS Network Services is tested via the user interface on the PC:
Figure 4-11 ePS client – reports
Figure 4-12 Report – configuration
Release management - ePS Reporting Services
4.4 Final steps
eP-Satellite server
90 Operating Instructions, 03/2011
eP-Satellite server
Operating Instructions, 03/2011 91
Release management - Updating the eP-Satellite
server 5
5.1 Updating the eP-Satellite
Overview
This section describes how to update the eP-Satellite from Version 4.9 to Version 4.9.2
eP-Satellite External Web Server
eP-Satellite Internal Web Server
eP-Satellite reporting web server
Relevant servers:
eP-Satellite application reporting database server
Adapting the settings file
The settings file contains all the settings required for installation. This file, called
satellite.settings, can be found in the unzipped installation package under tools\install\
<!-- Persistence settings -->
<<NAME=SqlInstanceMain; FILE=*.*; VALUE="%Database\(Instance)%"; >>
<<NAME=SqlInstanceReporting; FILE=*.*;
VALUE="%ReportingDatabase\(ReportingInstance)%"; >>
<<NAME=SqlInstanceLogging; FILE=*.*; VALUE="%Database\(Instance)%"; >>
<!-- Authorization -->
<<NAME=Authorization; FILE=\Webs\BA\Web.Config.tmpl; VALUE= <allow
roles="%Domain%\bizAdmin"/><deny users="*" />; >>
<!--------------------------------------------------------->
<!-- Settings for Reporting Application (V4.4 and later) -->
<!--------------------------------------------------------->
<< NAME=ReportingServerUrl; FILE=*.*; VALUE=localhost/ReportServer; >>
<< NAME=ReportServiceCommAvailable; FILE=*.*; VALUE=TRUE; >>
<< NAME=DeploymentDirectory; FILE=*.*;
VALUE=C:\ePS_Services\ePS_Reporting\epsReportingSSIS; >>
<< NAME=EpsReportingWebService; FILE=*.*; VALUE=https://%Reporting-
URL%/epsReportingServiceComm/epsReportingServiceV1.asmx; >>
<< NAME=MicrosoftReportingWebService; FILE=*.*; VALUE= https://%Reporting-
URL%/ReportServer/ReportService2005.asmx;>>
<< NAME=ssrsBinDir; FILE=*.*; VALUE=C:\Program Files\Microsoft SQL
Release management - Updating the eP-Satellite server
5.1 Updating the eP-Satellite
eP-Satellite server
92 Operating Instructions, 03/2011
Server\%MSSQL.2%\Reporting Services\ReportServer\bin;>>
<< NAME=vsReportingBinDir; FILE=*.*; VALUE=C:\Program Files\Microsoft Visual Studio
8\Common7\IDE\PrivateAssemblies;>>
<!-------------------------------------------------------------------->
<!-- Additional Settings for Reporting Application (V4.5 and later) -->
<!-------------------------------------------------------------------->
<< NAME=AcrobatReaderPath; FILE=*.*; VALUE=C:\Program Files\
Adobe\Reader 8.0\Reader\AcroRd32.exe; >>
<<NAME=ShowOfflineSynchronization; FILE=\Webs\Web.Config.tmpl; VALUE=<add
key="ShowOfflineSynchronization" value="True" />; >>
Release management - Updating the eP-Satellite server
5.2 Installing the eP-Satellite server software
eP-Satellite server
Operating Instructions, 03/2011 93
5.2 Installing the eP-Satellite server software
Updating the database
Relevant servers eP-Satellite application database server
Extract the archive "Server_ Install_ Satellite _x.x.x.x.cab": The installation package must be
located no more than one level below the drive letter; otherwise, installation problems
relating to the depth of the directory will arise. It must be ensured that none of the extracted
folders – including subfolders – has read-only access.
Example: C:\temp\server_install__Satellite_x.x.x.x
The following batch files can be found under \persistance\install in the unzipped installation
package, and must be run in the following order:
Start the database installation TsBuild.bat /s %Database\(Instance)%
Start the logging database installation LoggingBuild.bat /s %Database\(Instance)%
Check the database versions CheckDbVersion.bat %Database\(Instance)%
>> C:\CheckDBVersion.log
Installing the web service
eP-Satellite Internal Web Server
Relevant servers
eP-Satellite External Web Server
Stop the IIS and Trigger Agent Service as for an update, the directory structure already
exists.
Rename the old directory "Version4" - for example Versionx.x.x.x - and then create a new
folder "Version4".
Extract the archive "Server_Install_Satellite_x.x.x.x.cab": The installation package must be
located no more than one level below the drive letter; otherwise, installation problems
relating to the depth of the directory will arise. It must be ensured that none of the extracted
folders – including subfolders – has read-only access.
Example: C:\temp\server_install_Satellite_x.x.x.x
Ensure that there is an adapted settings file in the extracted installation package under
\tools\install.
Then subsequently run "install satellite_install.cmd".
Enter the following directory paths and confirm the queries as indicated in the table below:
Query Input
Install ePS Trigger Agent YES
Installationspfad %Installpath%\ePS_Services\Services\Version4
Release management - Updating the eP-Satellite server
5.2 Installing the eP-Satellite server software
eP-Satellite server
94 Operating Instructions, 03/2011
Query Input
Database for logging %Database\(Instance)%
Create directories YES
Load assemblys to GAC YES
Installing language packages
Extract Server_install_Ing_yy_x.x.x.x.cab (yy = language code of the particular language),
run setup_install_languages.bat in the relevant extracted package under \tools\install\.
Installation path %Installpath%\ePS_Services\Services\Version4
Load assemblies to GAC YES
This exact procedure must be followed for all language packages. It is possible to do this for
more than one package at the same time. Once you have completed this process, you
should be able to see folders with each of the relevant language codes in directory
%Installpath%\ePS_Services\Services\Version4\PC\bin.
Installing the RANG-Service Engineer ActiveX Client download component
Extract the"ServiceEngineerActiveXClient.msi" file, contained in the
"ServiceEngineerActiveXClient_Download_Download_x.x.x.x.zip" archive file, into the
directory C:\ePS_Services\Services\Version4\PC\RemoteAccessNG\RANG\Pages.
While unzipping, activate the following options:
● "Overwrite existing files"
● "use foldernames"
● "all files"
Installing RANG-PLSL Client download component
Extract "RANG_SEClient_Download_x.x.x.x.zip" to C:\ePS_Services\Services\Version4.
While unzipping, activate the following options:
● Overwrite existing files
● use foldernames
● all files
Release management - Updating the eP-Satellite server
5.2 Installing the eP-Satellite server software
eP-Satellite server
Operating Instructions, 03/2011 95
Installing Genesis V2
In the Genesis directory, run file "genesis_x.x.x.x.msi"
Installation path %Installpath%\ePS_Services\AppServer_V4\Genesis_V2
Logging directory %Logpath%\ePS_Services\AppServer_V4\Genesis_V2\Log_Genesis
In the folder %Installpath%\ePS_Services\AppServer_V4\Genesis_V2\Genesis\UAT\ edit the
following entry in the file "GenesisProcessingUnit.exe.config":
Line:
<value> %Logpath%\ePS_Services\AppServer_V4\Genesis_V2\Log_Genesis </value>
Replace with:
<value> %Logpath%\ePS_Services\AppServer_V4\Genesis_V2\Log_UAT\ </value>
Now restart the "ePS Genesis 2 PU" service.
Installing online help
German:
Create directory %Installpath%\ePS_Services\Services\Version4\Help\PC\de
Extract archive "OH_DEU.zip" and copy the contents to the directory
created (shown above).
"HelpIndex.de-de.xml" %Installpath%\ePS_Services\Services\Version4\PC\Common\Help\
Edit HelpIndex.xml.
Replace "dummy.htm" with:
https://%Webservices-
URL%/Webservices/Version4/Help/PC/de/OnlineHilfe.htm
Save the file as "HelpIndex.de-de.xml".
For all other languages:
Create directory %Installpath%\ePS_Services\Services\Version4\Help\PC\xx
Unzip archive "OH_YYY.zip" and copy the contents to the directory created
(shown above).
"HelpIndex.yy-yy.xml" %Installpath%\ePS_Services\Services\Version4\PC\Common\Help\
Edit HelpIndex.xml.
Replace "dummy.htm" with:
https://%Webservices-
URL%/Webservices/Version4/Help/PC/yy/OnlineHilfe.htm
Save the file as "HelpIndex.yy-yy.xml".
Release management - Updating the eP-Satellite server
5.2 Installing the eP-Satellite server software
eP-Satellite server
96 Operating Instructions, 03/2011
"yy" must be replaced with the relevant language code in each case, such as EN-US for
English.
Installing the Authentication Service
1. Unzip "svc_install_Satellite_x.x.x.x.cab".
2. Run the "setup_svc_satellite.cmd" using the unchanged original settings file.
Note
Never specify the installation folder as version4.
3. Enter the following directory paths and confirm the queries as indicated in the table
below:
Query Input
Installationspfad %Installpath%\ePS_Services\Services\SVC
Database %Database\(Instance)%
Database for logging %Database\(Instance)%
Load assemblys to GAC YES
Release management - Updating the eP-Satellite server
5.2 Installing the eP-Satellite server software
eP-Satellite server
Operating Instructions, 03/2011 97
Configuring the Authentication Service
The configuration of the AuthService service is performed using 3 web.config files in the
main directory AuthService and the subdirectories Ign and Req.
1. In the AuthService – main directory, please make the following changes in web.config:
– Search for the following line and replace the database server "SDEVSQL\V480" by the
correct database server "%Database\(Instance)% :
<logTarget name="dbTarget"
type="ePS.Infrastructure.Logging.LogTargets.DatabaseTarget,
ePS.Infrastructure.Logging" onDuty="false" timeSpanBetweenRetriesMinutes="5"
installationName="%Database\(Instance)%" dataSource="">
– Search for the following line and replace the log path "C:\Temp\" by the required log
path %Logpath%\ePS_Services\Services\SVC\Logfiles\":
<logTarget name="fileTarget"
type="ePS.Infrastructure.Logging.LogTargets.FileTarget, ePS.Infrastructure.Logging"
formatterName="textFileFormatter" fileNamePrefix="V481-AuthService" onDuty="true"
outputPath="%Logpath%\ePS_Services\Services\SVC\Logfiles\" fileSize="10000">
2. In the directory \AuthService\Ign, please make the following changes in the web.config
file:
– Search for the following line and change parameter "mexHttpBinding" to
"mexHttpsBinding":
<endpoint address="mex" binding="mexHttpsBinding" name="mex"
contract="IMetadataExchange" />
– Search for the following line and comment this out with a preceding "<!--" and
a subsequent ">--":
<!--<endpoint address="basic" binding="basicHttpBinding" name="basic"
bindingConfiguration="noSsl"contract="ePS.Services.AuthService.Contracts.Service.I
Authenticate" />-->
– Search for the following line and change parameter "mexHttpBinding" to
"mexHttpsBinding":
<serviceMetadata httpsGetEnabled="true" />
3. In the directory \AuthService\Req, please make the following changes in the web.config
file:
– Search for the following line twice and change parameter "mexHttpBinding" to
"mexHttpsBinding":
<endpoint address="mex" binding="mexHttpsBinding" bindingConfiguration=""
name="mex" contract="IMetadataExchange" />
Release management - Updating the eP-Satellite server
5.2 Installing the eP-Satellite server software
eP-Satellite server
98 Operating Instructions, 03/2011
– Search for the following line and comment this out with a preceding "<!--" and
a subsequent ">--":
<!--<endpoint address="basic" binding="basicHttpBinding"
bindingConfiguration="basicConfigNoSsl" name="basic"
contract="ePS.Services.AuthService.Contracts.Service.IValidate" />-->
– Search for the following line and set parameter "httpGetEnabled="false"" to deactivate
this, then in addition, add parameter "httpsGetEnabled="true"" :
<serviceMetadata httpGetEnabled="false" httpsGetEnabled="true" />
Release management - Updating the eP-Satellite server
5.3 Configuring the external eP-Satellite web server
eP-Satellite server
Operating Instructions, 03/2011 99
5.3 Configuring the external eP-Satellite web server
Configuring "Server2Server" communication
Relevant servers eP-Satellite External Web Server
The eP-Satellite must have already been fully installed before the HASH value and coded
password can be generated for the first time. The values generated must then be entered in
the relevant configuration files.
A user who is a member of the "bizAdmin" group is required for authentication. The relevant
user must be added to the "bizAdmin" group for this purpose.
Generating the HASH value
On the web servers, open the following page in the browser:
https://localhost/Webservices/Version4/SystemServiceComm/Login/
Then select the following options:
Encryption SHA1
Password %HASH Password%
In the following folders - under password - enter the HASH value generated in the particular
web.config:
%Installpath%\ePS_Services\Services\Version4\SystemServiceComm
%Installpath%\ePS_Services\Services\Version4\PCServiceComm
%Installpath%\ePS_Services\Services\Version4\HMIServiceComm
%Installpath%\ePS_Services\Services\Version4\ServiceRegistryService
Web.config
<user name="server2server" password="<HASH WERT>" />
Coding the password
Under \build\output\server\production\release\bin in the unzipped package, call file
ePS.Infrastructure.EncoderNT.exe as follows:
ePS.Infrastructure.EncoderNT.exe "%HASH Password%"
Copy the result to the central web.config file under
%Installpath%\ePS_Services\Services\Version4 in the Version Management area.
Web.config
serverUserName="server2server" serverPassword="coded password">
Release management - Updating the eP-Satellite server
5.4 Database logging
eP-Satellite server
100 Operating Instructions, 03/2011
5.4 Database logging
Uninstalling the current service
Relevant servers eP-Satellite database server
The service that is already installed can be uninstalled using the following call in the prompt:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe /u
ePS.Infrastructure.Logging.WindowsService.exe
Installing logging services
The files for the service are located in the unzipped installation package of the web server,
under build\output\server\production\release\bin.
The following files must be copied to the following folder:
%Installpath%\ePS_services\DBLogging
Figure 5-1 List of files
Using the prompt, switch to the installation directory and execute the following command:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe
ePS.Infrastructure.Logging.WindowsService.exe
Release management - Updating the eP-Satellite server
5.4 Database logging
eP-Satellite server
Operating Instructions, 03/2011 101
Configuring database logging
The following changes must be made in the
ePS.Infrastructure.Logging.WindowsService.exe.config:
<logTarget name="dbTarget"
type="ePS.Infrastructure.Logging.LogTargets.DatabaseTarget,
ePS.Infrastructure.Logging"
onDuty="true"
dataSource="%Database\Instance%\"
timeSpanBetweenRetriesMinutes="5"
installationName="ePSLoggingServiceV451">
<logFilters>
<logFilter name="defaultSubsetSeverityFilter" />
</logFilters>
</logTarget>
<logTarget name="fileTarget"
type="ePS.Infrastructure.Logging.LogTargets.FileTarget,
ePS.Infrastructure.Logging"
fileNamePrefix="V49_wcfLogger"
onDuty="true"
outputPath="%LogDirectory%"
fileSize="1000">
<logFilters>
<logFilter name="defaultSubsetSeverityFilter" />
</logFilters>
</logTarget>
</logTargets>
<logFilters>e
Release management - Updating the eP-Satellite server
5.4 Database logging
eP-Satellite server
102 Operating Instructions, 03/2011
Starting the service
The service is started from the Services panel. The Startup Type setting for the service must
be changed to "Automatic".
Figure 5-2 Services
Activating database logging
eP-Satellite External Web Server
eP-Satellite Internal Web Server
Relevant servers:
eP-Satellite application render server
In order to activate database logging, the names of the database server and the private
MessageQueue must be adapted in the web.config files of the web server and render server.
The corresponding configuration files can be found in the following directories:
%Installpath%\ePS_Services\Services\Version4 (eP-Satellite Web Server)
%RenderInstPath%\Service\RenderService (eP-Satellite Render Server
Release management - Updating the eP-Satellite server
5.4 Database logging
eP-Satellite server
Operating Instructions, 03/2011 103
The entry can be found in the web.config file in the wcfTarget section and must be adapted
as follows:
(<endpoint address="net.msmq://%Database\(Instance)%/private/logentryqueue")
<logTarget
name="wcfTargetData"
type="ePS.Infrastructure.Logging.LogTargets.WcfTarget, ePS.Infrastructure.Logging"
onDuty="false"
endpointAdress="net.msmq://%Database\(Instance)%/private/logentryqueue"
<logFilters>
<logFilter name="wcfTargetDataSubsetSeverityFilter" />
</logFilters>
</logTarget>
The parameter preceding this line, "onDuty=false", is then changed to "onDuty=true". Once
IIS has been restarted, database logging will be activated for the relevant server.
Release management - Updating the eP-Satellite server
5.5 Activating PKI login
eP-Satellite server
104 Operating Instructions, 03/2011
5.5 Activating PKI login
To activate the PKI login, read the handling steps in the following chapter:
Activating PKI login (Page 61)
5.6 ePS Render Services
Relevant servers eP-Satellite application render server
Note
ePS Render Services only needs to be installed if you are using solution line clients.
Installing ePS Render Services
First stop the IIS web server service, then uninstall the previously installed Render Services
version. Use Add or Remove Programs in the Control Panel to do this. Following this, run file
RenderServer_x.x.x.x.msi and carry out the installation procedure as described below.
Enter the following information during the setup routine:
Query Input
Location %RenderInstPath%
Password Enter %RenderPasswort%
Hosts %WebServerDomain%
Log directory %RenderLogPath%
Release management - Updating the eP-Satellite server
5.6 ePS Render Services
eP-Satellite server
Operating Instructions, 03/2011 105
Figure 5-3 Render Services
Adapting the web.config file
In directory %Installpath%\ePS_Services\Services\RenderServer, edit the web.config file and
add the colored entries.
<add key="renderer.defFntSize.800x600" value="20"/>
<add key="renderer.defFntSize.895x682" value="20"/>
<add key="renderer.defFntSize.1024x768" value="20"/>
<add key="handshake.renderServiceUrl"
value="https://%RenderServiceURL%/IERenderService/IERenderService.asmx"/>
</appSettings>
<system.web
Release management - Updating the eP-Satellite server
5.7 Reporting Services
eP-Satellite server
106 Operating Instructions, 03/2011
5.7 Reporting Services
5.7.1 Installing ePS Reporting Services
Installing the database component
Relevant servers eP-Satellite application reporting database server
The satellite.settings file created in Section Preparing for installation (Page 30) is used for
installing ePS Reporting Services.
Extract the archive "Reporting_install_Satellite_x.x.x.x.cab ": The installation package must
be located no more than one level below the drive letter; otherwise, installation problems
relating to the depth of the directory will arise. It must be ensured that none of the extracted
folders – including subfolders – has read-only access.
Example: C:\temp\server_install_Satellite_x.x.x.x.
The adapted settings file must be copied to the \tools\UserSettings directory of the unzipped
installation package.
In the unzipped installation package, edit the setup_Reporting_production.bat script under
\tools\install, change parameter "production.settings" to "satellite.settings", then run the
script.
Install DatabaseServer for ePS Reporting YES
Install Web Server for ePS Reporting NO
Installing the web server component
Relevant servers eP-Satellite reporting web server
The satellite.settings file created in Section Preparing for installation (Page 30) is used for
installing ePS Reporting Services.
Extract the archive "Reporting_install_Satellite_x.x.x.x.cab ": The installation package must
be located no more than one level below the drive letter; otherwise, installation problems
relating to the depth of the directory will arise. It must be ensured that none of the extracted
folders – including subfolders – has read-only access.
Example: C:\temp\server_install_Satellite_x.x.x.x.
The adapted settings file must be copied to the \tools\UserSettings directory of the unzipped
installation package.
Release management - Updating the eP-Satellite server
5.7 Reporting Services
eP-Satellite server
Operating Instructions, 03/2011 107
In the unzipped installation package, edit the setup_Reporting_production.bat script under
\tools\install, change parameter "production.settings" to "satellite.settings", then run the
script.
Install DatabaseServer for ePS Reporting NO
Install Web Server for ePS Reporting YES
Checking the reports delivery service
To check whether the report delivery service is working, the reports which are available can
be viewed via the SQL Server Reporting Services web interface.
To do this, open the URL https://localhost/reports in the browser on the reporting web server.
Figure 5-4 SQL Server Reporting Services
Release management - Updating the eP-Satellite server
5.7 Reporting Services
eP-Satellite server
108 Operating Instructions, 03/2011
5.7.2 Testing the ePS Reporting Services installation
In order to perform a final function test, ePS Reporting Services is accessed from the
product:
● This is demonstrated using the Business Administration portal in the images below:
Figure 5-5 Managing reports
Figure 5-6 Report name
Release management - Updating the eP-Satellite server
5.7 Reporting Services
eP-Satellite server
Operating Instructions, 03/2011 109
● Additionally, ePS Network Services is tested via the user interface on the PC:
Figure 5-7 ePS client – reports
Figure 5-8 Report – configuration
Release management - Updating the eP-Satellite server
5.8 Installing and configuring the RANG server
eP-Satellite server
110 Operating Instructions, 03/2011
5.8 Installing and configuring the RANG server
5.8.1 Installing the RANG Servers
Precondition
Relevant servers eP-Satellite RANG server
In order to install the eP-Satellite RANG server, you require the "epsrang-x.x.x.i386.rpr"
installation package.
Hardware/Software
Operating system SuSE Linux Enterprise Server 10, 32 Bit Version, Service Pack 2
RAM Minimum of 512 MB, 4 GB is recommended
Disk space Minimum,150 MB
Recommended 150 MB /opt and 100 MB /var
Processor Minimum,1.6 GHz, recommended, QuadCore 2 GHz
Packages required Minimum installation plus:
• openssl
• libjpeg
• libxml2
Check the version
Check the version of the RANG server that has been installed using the following command:
rpm –q epsrang.
Uninstalling the RANG server
First, you must uninstall the already installed RANG server using the command:
rpm –e epsrang.
Release management - Updating the eP-Satellite server
5.8 Installing and configuring the RANG server
eP-Satellite server
Operating Instructions, 03/2011 111
Installing the RANG server
Note
The installation is made using the DOS shell!
1. Start the DOS shell via "Start" → "Run..." → "rpm-ivh epsrang-x.x.x. –x .i386.rpm".
2. Navigate to the installation path: opt/epsrang/
3. Navigate to the log files in the following directory: /var/epsrang/log/
The following log files are available:
– confsrv.log - Contains status messages of the server
– confsrv.stderr - Contains messages when starting/stopping the server
Starting / stopping the service
Starting and stopping the service using the following DOS shell commands:
Start /etc/init.d/epsrang
Stop /etc/init.d/epsrang
The service runs as /opt/epsrang/bin/exes/confsrv (several instances).
5.8.2 Configuring the RANG server
Servers involved eP-Satellite RANG server
General configuration
● Call the page using the following address: https://%Remoteaccess-URL%/Web/config.
● Use the following standard access data:
– user: config
– PW: config
The server is configured using the "General configuration" input window.
1. For "Public address" enter the URL of the SSL certificate.
2. Select the appropriate certificate, the password file and the private key.
3. Press the "Apply changes" button in order to accept the settings.
Release management - Updating the eP-Satellite server
5.8 Installing and configuring the RANG server
eP-Satellite server
112 Operating Instructions, 03/2011
4. Stop the RANG server using the DOS shell command: /etc/init.d/epsrang stop.
5. Then subsequently start the RANG server using the DOS shell command:
/etc/init.d/epsrang start.
Note
Properties of the password file
The password file must only include one line break (file size, 2 bytes), it must not be
absolutely empty or contain other characters.
Figure 5-9 Configuring the RANG server
Configuring the security area
1. Open the "Authentication parameter" window.
2. Enter the URL for the "Authentication Service".
3. Change the port to 443.
4. Activate the use of SSL.
5. Change the access data under "General authorization" and under "Configuration
authorization".
6. Enter "mux" under "Username" - as well as a name that you have selected under "config".
7. Under "Password", allocate a new password and confirm this by repeating it in the entry
field below.
Release management - Updating the eP-Satellite server
5.8 Installing and configuring the RANG server
eP-Satellite server
Operating Instructions, 03/2011 113
8. To test the authorization, enter the new username and password under "Test
authentication".
9. Press the "Test" button to start the authorization test.
Figure 5-10 Configuring authentication
Release management - Updating the eP-Satellite server
5.8 Installing and configuring the RANG server
eP-Satellite server
114 Operating Instructions, 03/2011
eP-Satellite server
Operating Instructions, 03/2011 115
Operation management - System in operation 6
6.1 Business Administration
Using Business Administration
Business Administration is used to set parameters for a secure connection between the ePS
Network Services server and the eP-Satellite server. Business Administration is available on
both the ePS Network Services server and the eP-Satellite server.
Business Administration provides the following services:
● Manage organizations
● Application administration (inactive)
● Service Request Monitor
● Manage eP-Satellite
● Manage reporting settings
Figure 6-1 Overview of tasks
See also
The services that are available from each of the individual menus are described under:
Configuring the connection (Page 69)
Exporting/Importing a machine configuration (Page 121)
Operation management - System in operation
6.2 Business Administration functions
eP-Satellite server
116 Operating Instructions, 03/2011
6.2 Business Administration functions
Manage organizations
Under "Manage organizations", you can create new organizations or change and update the
data for the organizations that are already listed:
Figure 6-2 List of organizations
The following information is provided for each organization in the list:
Name/Icon Display
Sales Information Displays information and comments on the organization
ePS version Version of ePS Network Services that this organization uses
MUser FLC This logs how often a user (admin) attempts to log in, but fails. If too
many failed attempts are made, the organization is locked (see below).
The organization is active.
Only an administrator can access the organization data.
The organization is locked.
Deletes organization
For each organization, the address and contact details of the organization administrator are
entered and saved:
Operation management - System in operation
6.2 Business Administration functions
eP-Satellite server
Operating Instructions, 03/2011 117
Figure 6-3 Organization details
Service Request Monitor
The Service Request Monitor is a display function that may also be used for diagnostic
purposes. It displays all active background jobs along with their current status.
Managing eP-Satellite
On an eP-Satellite server, organizations to which several machines at different locations can
be assigned are created.
The following parameters must be specified for an eP-Satellite server:
● A unique name for the eP-Satellite server: %SatelliteName%
● The corresponding URL for the ePS Network Services ASP server: ePS Network
Services (https://www.epsnetwork.com/Services)
Operation management - System in operation
6.2 Business Administration functions
eP-Satellite server
118 Operating Instructions, 03/2011
Synchronization
In order to test the connection, the option "Operating interface active" must be selected.
The "Sync test" button, which is used to test the connection between the eP-Satellite server
and ePS Network Services server, is present on the ePS Network Services server, but not
on the eP-Satellite server.
Setting parameters
The following parameters must be set in order to ensure secure transfer of data when the
eP-Satellite server and ePS Network Services server communicate with one another:
Data layer:
Figure 6-4 Data layer tab
Operation management - System in operation
6.2 Business Administration functions
eP-Satellite server
Operating Instructions, 03/2011 119
Transport layer:
Figure 6-5 Transport layer tab
Manage reporting settings
Eight different report forms are available on the eP-Satellite server.
● Some reports can be saved as PDF files for documentation purposes.
● A report form can only be viewed by and is only made available to an organization if it
has been entered under "Enabled organizations".
In order to enable a report for an organization, left-click the "Open" icon.
Figure 6-6 Reports list
The dialog below opens, in which you can use the arrows to enter the organization with
permission to access and use this report form in the "Enabled organizations" list. Click "OK"
to save.
Operation management - System in operation
6.3 Exporting/Importing a machine configuration
eP-Satellite server
Operating Instructions, 03/2011 121
6.3 Exporting/Importing a machine configuration
Overview
Machine configuration data is always exported to the ePS Network Services server, and is
always imported from the ePS Network Services server.
Example: Exporting/Importing a machine
If a machine tool is moved from one location to another, for example, the administration and
configuration data for the machine will also need to be adapted to the new environment. The
machine will then belong to a different production site and/or a different organization.
The central path taken by the machine data is always via the ePS Network Services server:
● Export the data from the eP-Satellite server ⇒ to the ePS Network Services server
● Import the data from the ePS Network Services server ⇒ to the eP-Satellite server (to a
different organization or a different eP-Satellite server)
Note
The duration of the export and import procedure is highly dependent on the amount and
scope of the machine's configuration data, and may last several minutes.
Exporting the machine's configuration data
Procedure on the eP-Satellite server:
1. Select the machine from which data is to be exported: "mach_1_Laptop_ORG"
2. On the "Administration" tab, select "Machines" → "Export and import machines".
Even if the export is to take place via the ePS Network Services server, enter the future
organization on the eP-Satellite server as the destination.
Operation management - System in operation
6.3 Exporting/Importing a machine configuration
eP-Satellite server
122 Operating Instructions, 03/2011
3. Start the export process. This may take some time.
– In the "State" column, "Transfer is busy" appears.
– In Business Administration, the jobs that are active during the export procedure are
displayed under "Service Request Monitor".
4. Once the export is complete, "Transfer complete" appears.
Figure 6-8 Exporting the configuration data
Importing the machine's configuration data
Following the import to the eP-Satellite server:
Figure 6-9 Importing the configuration data
eP-Satellite server
Operating Instructions, 03/2011 123
Appendix A
A.1 Abbreviations
Admin Administrator (user role)
ASP Application Service Providing
CNC Computerized Numerical Control: Computerized numerical control
EH Event History
FTP File Transfer Protocol
FQDN Full Qualified Domain Name
GAC Global Assembly Cache
GLT Equability axis test
HDD Hard Disk Drive
HMI Human Machine Interface
IB Commissioning engineer (user role)
KFT Circularity test
MT Maintenance Ticket
MO Machine Operator (user role)
NC Numerical Control
NCK Numerical Control Kernel: NC kernel with block preparation, traversing range, etc.
NCU Numerical Control Unit: NCK hardware unit
OEM Original Equipment Manufacturer
OS Operating System
PCU Programmable Control Unit
PG Programming device
PLC Programmable Logic Control:
RANG Remote Access Next Generation
SE Service engineer: Service engineer (user role)
SLA Service Level Agreement
SOAP Simple Object Access Protocol
SW Software
TE Trigger Event
UAT Universal axis test
VPN Virtual Private Network
WSDL Web Services Description Language
Appendix
A.1 Abbreviations
eP-Satellite server
124 Operating Instructions, 03/2011
eP-Satellite server
Operating Instructions, 03/2011 125
Index
A
Application pools, 41
Application server, 9
B
Business Administration, 115
C
Communication paths, 26
Communications link, 115
Credentials, 81
D
Database logging, 59
Database server, 9
Domain account, 82
E
ePS Render Services, 71
H
HASH value, 54
M
Machine
Exporting, 121
Importing, 122
P
Password, 54
R
RANG server
Authorization, 76, 112
Configuring, 75, 111
Installing, 74, 111
Precondition, 74, 110
Uninstalling, 110
Report, 119
Reports, 86, 107
Revocation list, 70
S
SMTP, 53
System overview, 9
W
Web server, 10
web.config, 59
Index
eP-Satellite server
126 Operating Instructions, 03/2011
