00197725-12_GS_SE3.11_EN.pdf - 第23页

Getting Started SIPLACE Explorer 3 SIPLACE Explorer Runtime Envi ronment from 3.11 (R20-2) Edition 11/2020 EN 2 3 All currently existing warnings and all warnings for which the problem has been fixed are shown on t he SM…

3 SIPLACE Explorer Runtime Environment Getting Started SIPLACE Explorer

Edition 11/2020 EN from 3.11 (R20-2)

 Yes

This initializes all application objects and deletes non-appendable tables. The initial bean

values are set as a default. 3

 No

The process will be canceled. 3

 Advanced ...

The Initialize application dialog box opens. This is where you can reset the system state,

i.e. initialize database tables and the state for all beans. 3

Fig. 3 - 6 Initialize application

– Reset initial values for all beans

Resets all beans in the application back to their original (initial) state.

– Preserve data in all tables

The database data will not be changed.

– Clear non-appendable DB tables

If checked, the database tables not marked as appendable (refer to System Database) will

be cleared.

– Clear all tables

All existing tables will be deleted from the system database.

 Check ...

The system checks, if there are any deviations in the line configuration in OIS/SIS and in

SIPLACE Explorer. 3

The message shown to the user differs according to the gravity of the problem. It can belong

to one of three categories: 3

If you receive a message about incorrect settings, while you are operating the SIPLACE

Explorer, a warning symbol will be shown on the SMA pages at line level. This warning

symbol will be displayed until the problem has been fixed. 3

Getting Started SIPLACE Explorer 3 SIPLACE Explorer Runtime Environment

from 3.11 (R20-2) Edition 11/2020 EN

All currently existing warnings and all warnings for which the problem has been fixed are

shown on the SMA page Warnings. For a detailed description of this page, please refer to

SIPLACE Explorer SMA User Guide. 3

The following information categories exist: 3

– Critical error

The problem must be fixed before data monitoring can continue.

– Data loss

The problem must be fixed. Data monitoring will continue before the problem is fixed but

the data will not be complete.

– Notification

The problem must be fixed. However, if you ignore this problem, there may be

inconsistencies between the data in the SIPLACE Explorer and the OIS/SIS databases.

NOTE

To fix a problem, perform the following steps:

- Stop the monitoring procedure

- Correct the data accordingly

- Rebuild the application

- Start the monitoring procedure

For a detailed description of this procedure, refer to Section “Manually Checking the

SIPLACE Explorer Configuration for Problems” on page 26. 3

The following settings will be checked for possible problems: 3

– Coordination of line names in SIS and OIS:

The station or line name was changed in SIS but not in OIS. In this case, SIPLACE Explorer

can not receive information about the current setup data and will therefore be unable to

supply the user with information about component names and component shapes. 3

In this case, a message of category 'data loss' will be issued. 3

This check is performed automatically, when setup data are altered in the OIS. SIPLACE

Explorer will try to locate the new setup data in SIS. 3

3 SIPLACE Explorer Runtime Environment Getting Started SIPLACE Explorer

Edition 11/2020 EN from 3.11 (R20-2)

– 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