IBM DataPower Operations Dashboard v1.0.13.0

A newer version of this product documentation is available.

You are viewing an older version. View latest at IBM DPOD Documentation.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 15 Next »

As DPOD was designed to be non-intrusive, there are only a few steps required to reverse its setup from the DataPower device.

This page describe how to manually remove DPOD's configuration from a monitored device. Alternatively, you can run a script to automatically remove the setup. See Backing up and Restoring DPODs IDG related configuration

Before you Start

You do not need to uninstall DPOD if you only want to disable it for investigation purposes.
Instead, from the "Manage" menu -  choose "Monitored Devices" and change the "Device Syslog Status" to disabled to stop the DataPower from sending syslogs to DPOD

 

To uninstall DPOD, perform these steps on your monitored DataPower device.

These steps can be done manually as describe below or a by using scripts as described in Backing up and Restoring DPODs IDG related configuration

Remove Syslog Targets

Go to the “Manage Log Targets” screen, select all log targets starting with “Montier*” and "DPOD-MSC*" and delete them.

Repeat for all domains:

 

Remove Log Categories

Go to the "Log Categories" screen and delete all the categories starting with "montier" or "msc-"

Remove Host Aliases

Go to the "Host Aliases" screen and delete all the aliases starting with "montier" or  "MSC-" 

(Optional) Change Web Services Management Capture Mode

Do not perform this step if you have WS-M Agent Subscribers other than DPOD, as they will stop working too.

Go to the “Web Services Management Agent” screen and change "Capture Mode" from “All” to “None” or “Faults only”

(Optional) Disable the Certificate Monitor

The certificate monitor writes a syslog record for each expired certificate.
Leaving it as is will not have much effect (except for writing a few syslog records from time to time). As its impact is low - this step may be skipped unless a specific reason to disable it exists.

Go to “Crypto Certificate Monitor” and change the Administrative state to “disabled”

(Optional) XSLT

Leaving the policies as they are and skipping this step will have no effect on the service(s)

In every webservice proxy, go into the processing policy and remove the Montier policy from all the processing rules

Review all the objects in this list are removed

Objects to remove

Decommission the DPOD machine

When all steps above are completed, the DPOD appliance may be decommissioned safely.

 

 


  • No labels