Before You Begin

Before adding new monitored devices to DPOD, you may backup the objects that the DPOD will alter during the configuration phase, such as the XML management interface, the WS-M agent etc.
For detailed information regarding IDG DPOD related objects backup and restore see : Backing up and Restoring DPODs IDG related configuration

Before you add a new monitored device to DPOD, ensure to perform the following:

Check routing and access from a monitored device:
The DataPower Gateway needs to route packets to DPOD Agents through the desired interface. Validate through the DataPower's [control panel->Troubleshooting->TCP Connection Test]
Log-in to DPOD Web Console

Device Level Configuration

Add The Device In DPOD

Adding a device with a locale other than EN may cause some DPOD features to not work as expected

Inside DPOD's Web Console, navigate to Monitored Devices [Manage->Devices->Monitored Devices] and click on “Add Device”
Enter the information required. (Consult Device Management for details)
Note that the device name must be identical to the System Identifier/Appliance Name of the DataPower Gateway as set in the IDG itself, and must meet the requirements detailed in http://www-01.ibm.com/support/docview.wss?uid=swg21668456.

If you wish to add a Tenant device, enter the landlord's name but use the tenant's SOMA port, DPOD will display the tenant's name as tenant@landlord
Click “Add”
DPOD will add the device. (Verify by locating the new device in the list of monitored devices)

When updating the "Log Target Source Address" after the device was added and syslog was setup for the device , the user must setup the syslog for device again in order for the change to take effect on the monitored device (see next item "Setup Syslog For The New Monitored Device" ).

Configure The New Monitored Device

Inside DPOD's Web Console, navigate to the devices list page [Manage->Devices->Monitored Devices]
Click the name of the device you added in the previous step
Click "Setup”s this do? how is this now 'configured'? are the following sections 'inside'?

Setup Syslog For The New Monitored Device

Under "Syslog Setup for Device", select the correct Syslog Agent according to the architecture design, click "Setup Syslog for device" and wait until the action completes successfully.

Syslog setup for all domains

Under "Syslog Setup for All Domains", select the correct Syslog Agent according to the architecture design, click "Setup Syslog for all domains" and wait until the action completes successfully.

diagram to new-name

Performance

Domains may be redirected to different Syslog agents according to the architecture design. If this is the case, set up each domain separately as documented below

Auto Setup Domains (Optional)

This feature will automatically detect and setup new domains created on the monitored device. This is especially useful for dynamically created API Connect domains.
Select a Syslog agent that the domains should report to, enter the domain pattern (use asterisk as wildcard) and click save.
DPOD will scan the monitored devices every 2 minutes and will setup the new domain. You may change the scan interval on the system parameters page. (A UI service restart is required after changing this interval)
For domains that match the auto setup pattern - DPOD will also try to detect if any domain was reset and setup it again.

Domains WS-M Setup (Optional)

Under "Domains WS-M Setup", select the correct WS-M Agent according to the architecture design. Click "Setup WS-M” and wait until the action completes successfully.
For supported WS-M payload capture services see IDG WS-M payload capture support.
Click on "Record Payload" to open the payload capture page where you can start capturing payloads

Extended Transaction setup (Optional)

Under "Extended Transaction Setup", click "Setup Extended Transaction for Device” and wait until the action completes successfully.

This step will MODIFY SERVICES PROCESSING POLICY. You must test and verify that the services are not affected by this change before setting this up on production environments.

This feature can be used at a service or domain level.

Certificate Monitor (Optional)

Under "Certificate Monitor", click "Setup Certificate Monitor for Device” and wait until the action completes successfully.
Consult the System Parameters List for information regarding the time interval parameter.

Domain Level Configuration

Configuring a specific domain (Optional)

Navigate to the domain setup page [Manage→ Devices→ Monitored Devices]
Click the device name
Click the domain name
Click "Setup”

Domains may be redirected to different Syslog agents according to the architecture design. Additionally, you may choose to enable WS-M on specific domains only etc. If this is required, follow the steps below to configure specific domains. Otherwise you may skip this section

Syslog setup (Optional)

Under "Syslog Setup", select the correct Syslog Agent according to the architecture design, click "Setup Syslog" and wait until the action completes successfully.

WS-M setup (Optional)

Select the correct WS-M Agent according to the architecture design. Click "Setup WS-M” and wait until the action completes successfully.
For supported WS-M payload capture services see IDG WS-M payload capture support.
Click on "Record Payload" to open the payload capture page where you can start capturing payloads

Extended Transaction setup for all services (Optional)

Under "Extended Transaction Setup for All Services", click "Setup Extended Transaction for all services” and wait until the action completes successfully.

This step will MODIFY SERVICES PROCESSING POLICY. You must test and verify that the services are not affected by this change before setting this up on production environments.

Browser not supported