IBM DataPower Operations Dashboard v1.0.7.1
A newer version of this product documentation is available.
You are viewing an older version. View latest at IBM DPOD Documentation.
Gateway changes performed by DPOD
- Amit Munwes
- Hanan Kenan
- Former user (Deleted)
- Assaf Cohen (Deactivated)
I order for DPOD to be able to gather the information it requires, it enables various features and creates several objects in DataPower.
The table below details the objects and the methods you can use to undo these changes.
| Object in Gateway | Action | Explanation | Can it be undone automatically ? |
|---|---|---|---|
SOMA Configuration (Device Level) | Update | 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
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. |
| Device Statistics | Update | Upon a user request from the 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. 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) | Add | Upon a user request from the Web Console, two host aliases will be created - "MSC-(env name)" (or montier-syslog in older DPOD versions) and MonTier_LogTarget_Source. 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) | Add | 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 ). | Yes, it can be removed with a script. |
Log Target (Domain Level) | Add | 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. Domains added subsequently will not have these 2 DPOD log targets configured automatically. | Yes, it can be removed with a script. |
| Log Category (Device Level) | Add | Upon a user request from the Web Console (by clicking the "Setup Syslog" on a device) a new log category, msc-mon, is added. | Yes, it can be removed with a script. |
Certificate Monitor | Update | 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. In order 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. |
Extended Transaction Device Level | Add | Upon a user request from the Web Console, a user Log Category (montier-mon) is added to mark DPOD special logs. | Yes, it can be removed with a script. |
| Add | 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: | Yes, 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 performs a 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 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 | 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. | 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]:
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 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 |
This documentation ignores irrelevant changes such as entry to log files and similar.