Before You Begin
You will need to:
- Check routing and access from a monitored device:
The DataPower Gatweay needs to route packets to DPOD Agents through the desired interface. Validate through control panel->Troubleshooting->TCP Connection Test] - Log In To DPOD Web Console
Device Level Configuration
Add The Device In DPOD
- Inside DPOD's UI Console, open Monitored Devices [Manage->Devices->Monitored Devices] and click on “Add Device”
- Enter the information required. (Detailed description can be found in Device Management)
Note that the device name must be identical to the System Identifier/Appliance Name of the DataPower Gatweay as set in the The IDG.
- click “Add”
- DPOD will add the device, and it will be added to the list of monitored devices
Configure The New Monitored Device
- Inside DPOD's UI Console, open the devices list page [Manage->Devices->Monitored Devices]
- Click the name of the device you added in the previous step
- Click "Setup” and wait for an informative green message at the top todo:what does 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 proper Syslog Agent (according to the architecture design), click "Setup Syslog for device" and wait till the action completes successfully.
- Syslog setup for all domains
- Under "Syslog Setup for All Domains", select the proper Syslog Agent (according to the architecture design), click "Setup Syslog for all domains" and wait till the action completes successfully.
todo: change diagram to new-name
Performance
Different domains may be redirected to different Syslog agents according to the architecture design. If this is the case, please 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 till the action completes successfully.
- Note: You may choose to select which domains have WS-M enabled. If this is the case, please setup each domain separately as documented below.
WS-M Subscriptions for All Domains (Optional)
Under "WS-M Subscriptions for All Domains", select the proper WS-M Agent (according to the architecture design), click "Subscribe to WS-M for all domains” and wait till the action completes successfully.
For the time interval please read on the appropriate variable at System Parameters List.
This feature can be done on a service or domain level.
This step will start recording payloads of transactions for a specific amount of time (currently 1 hour). You may run this later when you need payloads recorded. You may choose to record payload on a specific domain. If this is the case, please subscribe on each domain separately as documented below.
Extended Transaction setup (Optional)
Under "Extended Transaction Setup", click "Setup Extended Transaction for Device” and wait till the action completes successfully.
This step will MODIFY SERVICES PROCESSING POLICY. You must test and make sure the services are not affected by this change before executing this on production environments.
This feature can be done on a service or domain level.
Certificate Monitor (Optional)
Under "Certificate Monitor", click "Setup Certificate Monitor for Device” and wait till the action completes successfully.
For the time interval please read on the appropriate variable at System Parameters List.
DOMAIN LEVEL CONFIGURATION
Configuring a specific domain (Optional)
Navigating to domain setup page [Manage→ Devices→ Monitored Devices]
Click the name of the device
Click the name of the domain
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 following steps to configure specific domains. If not – skip this section
Syslog setup (Optional)
Under "Syslog Setup", select the proper Syslog Agent (according to the architecture design), click "Setup Syslog" and wait till the action completes successfully.
WS-M setup (Optional)
Under "WS-M Setup", click "Setup WS-M" and wait till the action completes successfully.
WS-M Subscription (Optional)
Under "WS-M Subscription", select the proper WS-M Agent (according to the architecture design), click "Subscribe to WS-M” and wait till the action completes successfully.
This step will start recording payloads of transactions for a specific amount of time (currently 1 hour). 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 till the action completes successfully.
This step will MODIFY SERVICES PROCESSING POLICY. You must test and make sure the services are not affected by this change before executing this on production environments.