SOMA Configuration

(Device Level)

Upon a user request from the Web Console (when adding a Monitored Device) the SOMA Configuration is aligned with the required manual step detailed 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 make the following changes to the XML Management Interface
[Network → Management → XML Management Interface] 

1. Enable SOAP Configuration Management
2. Enable AMP Endpoint
3. Enable SLM Endpoint
4. Enable WS-Management Endpoint
5. Firmware 6.X only - Disable (uncheck) SOAP Management URI

Firmware 6.X only - Disable (uncheck) SOAP Configuration Management (v2004)

No.

To undo these changes, leave this checkbox unchecked when you install DPOD.

If a backup is performed 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.

No.

To undo this change, leave this checkbox unchecked when you install DPOD.

If a backup is performed 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)

Log Target

(Device Level)

Upon a user request from the Web Console (by clicking a button), One log target called DPOD-MSC-<env name>-system will be added in default domain (if the setup was done before DPOD v1.0.5 the log target name will be MonTier-system-log ).

Log Target

(Domain Level)

Upon a user request from the Web Console (by clicking a button), Two log target are created for each existing domain at the time of running the action from DPOD's web console.
The log target names are DPOD-MSC-<env name>-1 and DPOD-MSC-<env name>-2 (or montier-syslog-1 and montier-syslog-2 if the setup was done before DPOD v1.0.5)
For API Connect domains, there may be a third log target called DPOD-MSC-<env-name>-3

Domains added subsequently may not have these 2 DPOD log targets (unless they were setup via "Auto setup domains")

Yes, it can be removed with a script.
Or, when deleting a monitored device via Manage→Devices>Monitored Devices→Delete Device, check the box "Delete Syslog logs targets from device" in the confirmation window.

Upon a user request from the Web Console, DPOD sets this object in the admin state to 'enabled' and changes the interval and Reminder time.

No.

If a backup is performed 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

Upon a user request from the Web Console, a user Log Category (montier-mon) is added to mark DPOD special logs.

Upon a user request from the Web Console, this action copies the following files to the Gateway store directory  - store://Montier-LOG.xsl, and store:///Montier-IDcheckSet.xsl:

Extended Transaction

Service & Domain Level

No, the checkpoint cannot be undone automatically.

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 that exists in this domain. Since this is an Intrusive action, the appropriate alert will appear – see Appendix A for a reference to the documentation.

Partially.

If no new Actions were added after the Action was added by DPOD then a customer script can remove it but Support can not provide such functionality.

WS-M Agent definition

Device Level

For each domain in the device, DPOD modifies the Web Service Management Agent [Objects→Web Service Management Agent]:

1. Change attribute "Maximum Memory Usage" to 102400
2. Change attribute "Capture Mode" to All

DPOD doesn’t change the admin state of the objects, therefore DPOD changes the gateway configuration only if this feature is used.

To undo these changes, the state of this checkbox needs be kept before you install DPOD.

If a backup is performed 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 a selected domain in the device, DPOD modifies the Web Service Management Agent [Objects→Web Service Management Agent]:

1. Change attribute "Maximum Memory Usage" to 102400
2. Change attribute "Capture Mode" to All

DPOD doesn’t change the admin state of the objects, therefore DPOD changes the gateway configuration only if this feature is used.

To undo these changes, the state of this checkbox needs be kept before you install DPOD.

If a backup is performed 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.

This is a temporary object that is used for a predefined amount of time (usually for a few minutes) and when expired it is deleted by Gateway automatically