Normally this information is not needed to end users, using panels described in other chapters of this document shall be enough for normal operation of CMWServer manager. However, sometimes knowing a bit on 'how does it work' can help in debugging of unexpected problems.
Many WinCC OA functionalities are built around DPs, so it shall not be a surprise that CMWServer manager uses some internal datapoints. The most important DP types and datapoints are mentioned in the following sections.
The configuration for every CMWServer manager in the system, as well as the state and diagnostics for this manager, is stored in dedicated DP of DP type _Un_CMWServer_Manager. DP with configuration for manager number N is named CMWServer_Manager_N. The following picture illustrates such DP for manager with number 5:
The rule for generating DP names is hardcoded.
Default configuration , that will be used for new added managers, is also stored in internal DP of type _Un_CMWServer_Config. There is only one DP of such type in the system, it is created and DPE values are set during CMWServer component installation.
If system Integrity was configured for CMWServer manager, then dedicated DP is created in the system where resulting alarm state for this manager is written:
In principle, CMWServer manager accepts all command line arguments, common to all WinCC OA managers (see WinCC OA help for details).
However, there are 2 argumnets which must be present in command line for such manager:
There is strong (hardcoded) relation between manager number and name of configuration DP, so it is not evident why do we need supply both in command line? Anyway, this was required for previous version of CMWServer manager, and still two these arguments are required.