...
| Object in Gateway | Action | Explanation | Can it be undone automatically ? |
|---|---|---|---|
SOMA Configuration (Device Level) | Update | Upon user request from Web Console (when adding Monitor Device) the SOMA Configuration is aligned with the required manual step in the Prepare your Monitored Devices chapter. This request is explicitly accepted by the admin on the UI. If the SOMA configuration is not fully aligned, then DPOD will set it correctly and change in the XML Management Interface [Network->Management->XML Management Interface] as follows:
Firmware 6.X only - Disable (uncheck) SOAP Configuration Management (v2004) | No. In order to undo this changes, this checkbox needs be left unchecked when you install DPOD. If customer performed a backup, as requested in the installation procedure, then this data can be extracted from the backup by restoring it to a temporary Gateway instance and viewing the exact configuration. The specific scripts will then set appropriate values identified in the action above.. |
| Device Statistics | Update | Upon user request from Web Console, DPOD enables the device statistics if they were not enabled before. This request is explicitly accepted by the admin on the UI. | No. In order to undo this change, this checkbox needs be left unchecked when you install DPOD. If customer performed a backup, as requested in the installation procedure, then this data can be extracted from the backup by restoring it to a temporary Gateway instance and viewing the exact configuration. The specific scripts will then set appropriate values identified in the action above. |
Host Alias (Device Level) | Added | Upon Two host aliases will be created - montier-syslog and MonTier_LogTarget_Source upon user request from Web Console , one log target is added in default domain (MonTier-system-log)(Clicking the "Setup Syslog" on a device), . The alias montier-wsm will be created on the first creation of a WSM subscription. | Yes, it can be removed with a script. |
Log Target (Device Level) | Added | Upon user request from Web Console by click a button, One log target is added in default domain (MonTier-system-log). | Yes, it can be removed with this script Remove Log targets from Gateway |
Log Target (Domain Level) | Added | Upon user request from Web Console by click a button, Two log target are created for each existing domain in the time of running the action from DPOD web console. Adding new domains afterwards will not have this 2 DPOD log targets. | Yes, it can be removed with this script Remove Log targets from Gateway |
Certificate Monitor | Update | Upon user request from the Web Console, DPOD sets this object in the admin state to 'enabled' and changes the interval and Reminder time | No. In order to undo this changes, this checkbox needs be left unchecked when you install DPOD. If customer performed a backup, as requested in the installation procedure, then this data can be extracted from the backup by restoring it to a temporary Gateway instance and viewing the exact configuration. The specific scripts will then set appropriate values identified in the action above. |
Extended Transaction Device Level | Add | Upon user request from the Web, a user Log Category (montier-mon) is added to mark DPOD special logs. | It can be removed with a script. |
| Add | Upon user request from the Web Console, this action copies the following files to the Gateway store directory - store://Montier-LOG.xsl, store:///Montier-IDcheckSet.xsl: | It can be removed with a script. | |
Extended Transaction Service &
| Update | Create Checkpoint - Before adding a stylesheet to easy recover, DPOD creates a checkpoint and perform backup. | No, the checkpoint cannot be undone automatically. |
| Update | Since an Extended transaction is intrusive by nature, as documented, DPOD adds Transform Action rule to the end of each rule for each Processing Policy for each WSP, MPG exists in this domain. Since this is an Intrusive action, the appropriate alert will appear – see Appendix A for a reference to the documentation. | Partial. If no new Actions were added after the Action was added by DPOD then a customer script can remove it but we can not provide such functionality. | |
WS-M Agent definition Device Level | Update | For each domain in the device, DPOD modifies the Web Service Management Agent [Objects→Web Service Management Agent]:
DPOD doesn’t change the admin state of the objects, therefore DPOD changes the gateway configuration only if this feature is used. | In order to undo this changes, the state of this checkbox needs be kept before you install DPOD. If customer performed a backup, as requested in the installation procedure, then this data can be extracted from the backup by restoring it to a temporary Gateway instance and viewing the exact configuration. The specific scripts will then set appropriate values identified in the action above. |
WS-M Agent definition Domain Level | For selected domain in the device, DPOD modifies the Web Service Management Agent [Objects→Web Service Management Agent]:
DPOD doesn’t change the admin state of the objects, therefore DPOD changes the gateway configuration only if this feature is used. | In order to undo this changes, the state of this checkbox needs be kept before you install DPOD. If customer performed a backup, as requested in the installation procedure, then this data can be extracted from the backup by restoring it to a temporary Gateway instance and viewing the exact configuration. The specific scripts will then set appropriate values identified in the action above. | |
| WS-M subscription | Create | This is a temporary object that is used for a predefined amount of time (default is 60 minutes) and when expired it is deleted by Gateway automatically | Not Relevant |
...