Tekla EPM Remote Server and Tekla EPM Remote Monitor
Tekla EPM Remote Server
A Windows service that installed on the server for Tekla EPM. It listens for and responds to traffic from EPM GO. In addition this service is required in order to execute automated events and should be installed during the initial program installation.
Tekla EPM Remote Monitor
A graphical interface to the Tekla EPM Remote Server service.
Using Tekla EPM Remote Monitor
TEKLA EPM Remote Monitor is accessed by double-clicking the icon on the desktop found on the Tekla EPM Server:
Tekla EPM Remote Monitor reports the following details in real-time:
Tekla EPM Remote Server Service Status
If the service is currently active, you will see a message that states that the service is running as well as the TCP port that the service is listening for connections. For example:
THE SERVICE IS RUNNING.
Running - Port 9154
If the service is not active, you will see a message that states that the service is not running. For example:
THE SERVICE IS NOT RUNNING.
The status of the service is changed with the button in the upper right-hand corner of the window:
If you wish to start the service: Press the Start Service button to start it. If you wish to stop the service: Press the Stop
Service button to stop it.
If you have attempted to start the service and it does not start, please contact support and send us your service log file.
The time (in hours: minutes: seconds) that the service has been active.
Indicates fundamental program status.
Connection SSL Cipher
Indicates whether Tekla EPM Remote Server is connected to the MySQL database via an encrypted connection.
If Tekla EPM doesn't use encryption for its ODBC connection, this will be blank.
Total Remote Connections
The total count of connections that have been made during the time that the service has been active.
Current Remote Connections
The count of connections that are currently active.
The total count of XML/JSON commands that transacted during the time that the service has been active.
The count of TCP sockets that are currently active.
The total count of TCP sockets that have been created during the time that the service has been active.
Tekla EPM Remote Server Settings
Tekla EPM Remote Server is controlled by the settings seen in Tekla EPM Remote Monitor's Settings window. To access the settings window, click Settings.
If you change a setting in Remote Server Monitor, you must restart the service before the new settings will be applied.
The settings window is divided into four main areas.
Database Connection Section
The Database Connection section controls how Tekla EPM Remote Server connects to the MySQL database.
This is the hostname or IP address to the computer on your network where the Tekla EPM MySQL database resides. If the database resides on the same computer as Tekla EPM Remote Service (and Remote Monitor), the value should read either localhost or 127.0.0.1.
This is the TCP port used for MySQL database traffic.
• The default port is 3306.
• The value should be the same as the port that Tekla EPM uses.
Username and Password
Do not use these unless absolutely necessary. There is a built in user for this purpose that we recommend you enable and these should be left blank.
Note that the password will never be shown and is stored in an encrypted fashion. Be super careful when entering these values – They are Case Sensitive.
SSL Cert & Key Paths and SSL Cipher
These fields set the path to the TLS/SSL certificates and keys that are used to encrypt the traffic between Tekla EPM
Remote Server and the MySQL database.
If Tekla EPM doesn't use encryption for its ODBC connection, these fields should be blank.
If using the latest licensing the Trimble Identity sign in must be used.
The Socket section controls the low-level parameters used with the TCP socket that Tekla EPM Remote Server uses to listen and respond to requests.
This is the TCP port that the service uses to communicate with the web server where Tekla EPM GO resides.
• The default value is 9154
• The TCP port must match the port that is set in Tekla EPM GO (the web program).
• Your network firewall must allow connections on this port and forward them to the computer on your network where Tekla EPM Remote Server resides.
Traffic transacting over the TCP socket can be logged at varying levels of detail.
Info level - Logs connection time, connection source, success or failure, and errors.
Debug level - Logs info level plus XML or JSON of request and response. Passwords will never be logged. If experiencing problems with the EPM Go this would be changed to debug in order to increase the detail in the socket log file.
SSL Cert Path
This is the path to the SSL certificates and ciphers that are used to encrypt traffic between Tekla EPM GO (the website application) and Tekla EPM Remote Server service over the TCP Socket. This cert is installed during the main program installation.
• All traffic between the website application and the local network is encrypted.
• The value should point to the SSL subfolder in the Tekla EPM program folder e.g.: C:\Program Files (x86)\Tekla
EPM LLC\Tekla EPM\SSL
Remote Connection Section
The Remote Connection section controls connection time out for users logged onto the EPM Go application.
Idle Connection Timeout
This setting controls how long a user can stay logged in through Remote Link.
• Default value: 720 minutes (12 hours).
Port Forwarding (UPnP) Section
This allows Remote Server to attempt to configure your network firewall using Universal_Plug_and_Play.
We strongly suggest that you not rely upon UPnP for EPM GO, but to properly and permanently setup port forwarding on your network router/firewall.
Error 111 (Connection Refused), and Error 110 Connection Timeout Errors
This problem can occur for one of several reasons:
• Tekla EPM Remote Server service is not running. (see starting the service)
• The network router firewall at the fabricator is blocking connections on the TCP port used by Tekla EPM Remote Server service and Tekla EPM GO.
• Windows Firewall on the computer where Tekla EPM Remote Server service is running is blocking connections on the TCP port used by Tekla EPM Remote Server service and Tekla EPM GO.
This technote from Microsoft may be of assistance
Tekla EPM Remote Server Service Will Not Start
• This could be the username and password if used by Tekla EPM Remote Server service. Note we recommend leaving these blank.
• This could also be due to the Trimble Identity not being signed in.
Restarting Tekla EPM Remote Server
To restart Tekla EPM Remote Server:
1. Open Tekla EPM Remote Monitor.
2. Click Stop Service (this stops the service).
3. Click Start Service.
If you would like to adjust settings:
1. Stop the service.
2. Click Settings.
3. Make adjustments in the Settings window.
4. Click Save Settings to save your changes and close the Settings window.
5. Click Start Service.
Requesting Help with Tekla EPM Remote Server
If you still need assistance with Tekla EPM Remote Server, please contact support. For speedier assistance, send along your service and socket log files.