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
- 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.
- Click “Add”
- DPOD will add the device. (Verify by locating the new device in the list of monitored devices)
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.
todo:change 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
WS-M setup for device (Optional)
- Under "WS-M Setup for Device", click "Setup WS-M for all domains" and wait until the action completes successfully.
- Note: You may elect to only enable WS-M for specific domains. If this is the case, setup each domain separately as documented below.
WS-M Subscriptions for All Domains (Optional)
Under "WS-M Subscriptions for All Domains", select the correct WS-M Agent according to the architecture design, click "Subscribe to WS-M for all domains” and wait until the action completes successfully.
A WS-M subscription will be created for each domain where one is not already created by DPOD.
For supported WS-M payload capture services see IDG WS-M payload capture support
Consult System Parameters List for information regarding the time interval parameter.
This feature can be used at a service or domain level.
This step will start recording payloads of transactions for a specific amount of time (1 hour is the default configuration). You may run this later when you need payloads recorded. You may choose to record payload for a specific domain. If this is the case, please subscribe each domain separately as documented below.
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 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 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”
Different domains may be redirected to different Syslog agents according to the architecture design. Also, you may choose to enable WS-M on specific domains only etc. If this is the case, 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)
Under "WS-M Setup", click "Setup WS-M" and wait until the action completes successfully.
WS-M Subscription (Optional)
Under "WS-M Subscription", select the correct WS-M Agent according to the architecture design, click "Subscribe to WS-M” and wait until the action completes successfully.
Only one subscription from DPOD can be enabled per domain at a time.
For supported WS-M payload capture services see IDG WS-M payload capture support
This step will start recording payloads of transactions for a specific amount of time (1 hour is the default configuration). You may run this later when you need payloads recorded.
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 the services are not affected by this change before setting this up on production environments.