00197725-12_GS_SE3.11_EN.pdf - 第25页
Getting Started SIPLACE Explorer 3 SIPLACE Explorer Runtime Envi ronment from 3.11 (R20-2) Edition 11/2020 EN 2 5 3.5.2 St arting Production Line Monitoring in SIPLACE Explorer 3 Fig. 3 - 7 S tarting production line moni…
3 SIPLACE Explorer Runtime Environment Getting Started SIPLACE Explorer
Edition 11/2020 EN from 3.11 (R20-2)
24
– Coordination of station names in OIS and SIPLACE Explorer
Station names have been changed in OIS. In this case, you will receive a message about
this change, in SIPLACE Explorer. If you want to synchronize the station names in OIS and
SIPLACE Explorer, proceed as described at “Manually Checking the SIPLACE Explorer
Configuration for Problems” on page 26. If you do not synchronize the station names, data
monitoring will be continued but the database data will not correspond to the line
configuration data. 3
In this case, a message of category 'notification' will be issued. 3
This check is also performed automatically, each time OIS data are called up. 3
– Coordination of IP address in OIS and SIPLACE Explorer
The station IP address has been changed in OIS but not in SIPLACE Explorer. In this case,
SIPLACE Explorer will not be able to monitor and provide new data for the station. 3
In this case, a message of category 'critical error' will be issued. 3
This check is also performed automatically, each time OIS data are called up. 3
– Coordination of machine ID (MID) in SIPLACE Explorer and OIS
The station MID is not the same in OIS and SIPLACE Explorer. In this case, you will receive
a message about this change, in SIPLACE Explorer. If you want to synchronize the MID in
OIS and SIPLACE Explorer, proceed as described at “Manually Checking the SIPLACE
Explorer Configuration for Problems” on page 26. If you do not synchronize the MID, data
monitoring will be continued but the data in the SE database will not correspond to the data
from the OIS. 3
In this case, a message of category 'notification' will be issued. 3
This check is also performed automatically, each time you restart the monitoring process
with SIPLACE Explorer. 3

Getting Started SIPLACE Explorer 3 SIPLACE Explorer Runtime Environment
from 3.11 (R20-2) Edition 11/2020 EN
25
3.5.2 Starting Production Line Monitoring in SIPLACE Explorer
3
Fig. 3 - 7 Starting production line monitoring in SIPLACE Explorer
SE Manager
Select the production line
Check setting with Check
There are no deviations in the line
configuration in OIS/SIS and in
SIPLACE Explorer
There are deviations in the line
configuration in OIS/SIS and in
SIPLACE Explorer
Line Configuration
Step 2:
Change configuration of the
production line accordingly
Re-check of the settings
Correction of the problem required
Step 7:
Rebuild the application
Starting Monitoring in SIPLACE Explorer
SE Manager
Start the monitoring procedure
with Start
Preconditions
MS SQL Server is started (Windows service)
Apache Tomcat is started (Windows service)
SIPLACE Explorer Runtime Environment is started
(Windows service )
Database must have been created in MS SQL Server and
the connection to the database must have been established
Production line must have been configured in SIPLACE Explorer

3 SIPLACE Explorer Runtime Environment Getting Started SIPLACE Explorer
Edition 11/2020 EN from 3.11 (R20-2)
26
3.5.3 Manually Checking the SIPLACE Explorer Configuration for Problems
The configuration check can be performed both when production line monitoring is running and
when it has been stopped. 3
NOTE
Before you begin to monitor a production line with SIPLACE Explorer, always perform a
configuration check with the SE Manager. 3
3
Select the production line for which you wish to perform a configuration check, from the Line
menu of the SE Manager.
NOTE
The system only displays those production lines which have already been configured with
Line Configuration. 3
Click on the Check icon. A configuration check will be performed for the selected
production line.
– Configuration of production line OK:
If no problems were detected during the configuration check, you will see the following
information:
3
Fig. 3 - 8 Check line results