Powermanager –

Server- Client- Installation

Client A Server Client B

Server-Client functionality allows you to show and operate a central powermanager project on server from several
clients.

1.0 Requirements

1.1 On Server and all Clients a complete regular installation of Automation-License-Manager (ALM) and
Powermanager is required.

1.2 Installation of Microsoft Excel is required on all systems (Client and/or Server) which should be able to use
Excel reporting functions.

1.3 If updates or service packs for Powermanager are available, they must be complete installed in project on
server first. Afterwards on client machines the folder
„Client_Powermanager_Main_Installation_Folder\powermanagerLib” must be replaced with the
corresponding „Server_Powermanager_Main_Installation_Folder\powermanagerLib” folder from Server.

1.4 All licenses must be exclusive available in ALM on Server. It is not required to copy some licenses to clients,
because they will pick these automatically from server while running.

Example screenshot which shows licenses contained in ALM on Server:

Each User-Interface (UI) which is started on your Server and/or Clients requires 1 of the available validity of
Client-License.

Page 1 / 7
 Powermanager –
Server- Client- Installation

1.5 Time synchronization for Server and all Clients is required (NTP, NetTime). If time on not synchronously it
will not be possible to connect Clients to your Server!

For example, Windows 7 already includes a default internet time synchronization which could be used:

1.6 Server and all Clients must be reachable each other for IP and name. You can test this by ping commands
for all cases. Example:

Ping from client to server by IP: Ping from client to server by name:

1.7 Clients will open 2 TCP/IP connections to server on ports 4997 and 4998. Ensure that these ports are not
blocked by any network restrictions or firewalls.

1.8 The Powermanager project files on server must be read/write accessible for clients by network.

Client network view:

1.9 Powermanager project on server must be started.

If required the project could be started as Windows-Service on server. For details see available online FAQ:
http://support.automation.siemens.com/WW/view/en/60257744

Page 2 / 7
 Powermanager –
Server- Client- Installation

2.0 Configure Client PC’s

If server is successfully configured and runs your project start to configure all clients.

2.1 Start Project Administration, create a new project and select “Remote UI project”:

2.2 General settings:

Set name for client project

Define a general local project folder

Page 3 / 7
 Powermanager –
Server- Client- Installation

2.3 UI settings

For „Server project“ UNC network path to project folder on server is required (e.g.: //Servername/Project).

After clicking “Next” a warning for subprojects will appear:

Confirm it. The necessary steps for this are shown in point 0

2.4 Project has been created:

Page 4 / 7
 Powermanager –
Server- Client- Installation

2.5 It is necessary to integrate the “PowermanagerLib” as subproject. This can be done by “Edit project”:

Page 5 / 7
 Powermanager –
Server- Client- Installation

2.6 Copy the complete folder “xls_report” from server to local project folder of clients. This is required for using
Excel reporting functions.

2.7 Start client project

2.7.1 By Console:

2.7.2 By shortcut:
See point 4.0 of FAQ “Powermanager - Install as Windows-Service” for details:
http://support.automation.siemens.com/WW/view/en/60257744

If Expert-license is available it is also possible to add Expert mode by option “-extend” in your Client
User interface. But note that all expert changes (edit panels or scripts) will be stored in files on the local
project folder. Finally, changed files must always copy manual to server! Regarding this it is
recommended to use expert mode only direct on Server and not on Clients.

Page 6 / 7
 Powermanager –
Server- Client- Installation

3.0 Remarks for connection or fatal errors

If you get fatal errors while connecting Client to Server or connection is not possible, it’s mostly caused by:
- Server is not reachable
- Server project is not running
- Required ports are blocked by firewall (deactivate it for testing)
- Time on Server and Client is not synchronized
- More User Interfaces (UI) are running as validity is available in ALM on Server

Page 7 / 7