The Devices section under [Manage→Devices] provides access to the set of devices monitored by DPOD.

This step changes or add some of you monitored device objects. Please review the list of changes before you continue too perform this actions.

Monitored Devices

This screen displays a table containing information on all the monitored devices connected to DPOD's console, and lets an administrator perform several configuration tasks, at a device, domain or service level.
Each row in the table contains the following details about a single device:

Column	Description
Name	The device's name in DPOD
Host	IP Address of the device
SOMA port	The SOMA port configured on this device
Log Target Source	IP Address of the device's log target source
Device Resources Monitoring	Whether Device resources monitoring is enabled on this device
Service Resources Monitoring	Whether Service resources monitoring is enabled on this device

(This information relates the information entered when Adding Monitored Devices)

Device Level Configuration

The following steps let an administrator perform device-level configuration tasks:

Click on one of the monitored devices in the Monitored Devices table.
The system displays the device details, and a list of all the domains on that device.
Click the Setup link (found at the top of the table, next to the label ‘Domains’)
The system displays a list of administrator tasks available for this device. Consult the tables at the end of this page to find details about the available tasks.

Domain Level Configuration

The following steps let an administrator perform domain-level configuration tasks:

Click on one of the monitored devices in the Monitored Devices table.
The system displays the device details, and a list of all the domains on that device.
Click on one of the domains to select it.
The system displays the domain's details and a list of all services running on the selected domain.
Click the Setup link (found at the top of the table, next to the label ‘Services’)
The system displays a list of administrator tasks available for this domain. Consult the tables at the end of this page to find details about the available tasks.

Service Level Configuration

The following steps let an administrator perform service-level configuration tasks:

Click on one of the monitored devices in the Monitored Devices table.
The system displays the device details, and a list of all the domains on that device.
Click on one of the domains to select it.
The system displays the domain's details and a list of all services running on the selected domain.
Click on one of the services.
The system displays the service's details and a list of all endpoints in the service
Click the Setup link (found at the top of the table, next to the label ‘Endpoints’)
The system displays a list of administrator tasks available for this service. Consult the tables at the end of this page to find details about the available tasks.

This step changes or adds some of your monitored device objects. Please review the list of changes before you continue too perform this actions.

Available Tasks (Operations)

Device Level Operation Details

The following tasks are available for devices setup.

Task (Operation)	Details
Setup Syslog for device	Sets up the necessary configuration for the device to send device-level Syslog records to the selected agent. This configuration should be executed once after installing the system or when you need to redirect the device-level Syslog messages to a different agent. To setup the Syslog for a device, select a Syslog Agent from the drop-down list, and click the Setup Syslog for device button. You can disable/enable this Syslog target by clicking on the "Device Syslog Status" Enabled/Disabled buttons. Limitation: DPOD does not support transactions in the default domain. See /wiki/spaces/MS/pages/9306256. Note: This action changes your device configuration - please review changes .
Setup Syslog for all domains	Sets up the necessary configuration for all the domains to send domain-level Syslog records to the selected agent. This configuration should be executed once after installing the system, when a new domain is created or when you need to redirect the device-level Syslog messages to a different agent. To setup the Syslog for all domains, select a Syslog Agent from the drop-down list, and click the Setup Syslog for all domains button. You can disable/enable all these Syslog targets by clicking on the "Domains Syslog Status" Enabled/Disabled buttons. Limitation: DPOD does not support more than 125 domains per device. See /wiki/spaces/MS/pages/9306256 . Trying to run this action on more than 125 domains can be unpredictable. If you have more than 125 domains, you MUST run "Setup Syslog" using the Domain Level procedure below. Note: This action changes your device configuration - please review changes .
Auto Setup Domains	This feature will automatically detect and setup new domains created on the monitored device, this is especially useful for dynamically created API Connect domains. Choose 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 device every 2 minutes and will setup the new domain (you can change the interval from the system parameters page. A UI service restart is required after changing this interval)
Setup WS-M for all domains	Sets up the necessary configuration for all the domains to send payload data to the selected agent This configuration should be executed once after installing the system, when a new domain is created or when you need to redirect the payloads to a different agent Clicking the "Record Payload" link will take you to the Payload Capture page, where you can start a WS-M subscription. Note: This action changes your device configuration - please review changes . Note: This action does not enable the WS-M Agent on IDG. For security reasons, this can only be done from IDG.
Setup Extended Transactions for device	Extended Transactions are used to track cross-machine transactions, i.e. messages which are forwarded from one monitored DataPower Gateway to another. To use Extended Transactions, the devices must be configured (at device level). Extended transactions can be configured through the Web Console. Note: This action changes your device configuration - please review changes .
Setup Certificate Monitor for device	The Certificate Monitor is used to provide alerts before certificate expiration. Each device must be configured (at the device level) to enable certificate expiry alerts. This configuration should be executed once after installing the system. Note: This action changes your device configuration - please review changes .

This step changes or adds some of your monitored device objects. Please review the list of changes before you continue too perform this actions.

Domain Level Operation Details

The following tasks are available for domains setup.

Task (Operation)

Details

Setup Syslog

Sets up the necessary configuration for this domain to send domain-level Syslog records to the selected agent.
This configuration should be executed once after installing the system, or when the domain-level Syslog messages need to be redirected to a different agent.
To setup the Syslog for a domain, select a Syslog Agent from the drop-down list, and click the Setup Syslog button.

You can disable/enable this Syslog target by clicking on the "Domain Syslog Status" Enabled/Disabled buttons.

Note: This action changes your device configuration - please review changes .

Setup WS-M

Sets up the necessary configuration for all the domains to send payload data to the selected agent.
This configuration should be executed once after installing the system, when a new domain is created or when the payloads need to be redirected to a different agent.

Clicking the "Record Payload" link will take you to the Payload Capture page, where you can start a WS-M subscription.

Note: This action changes your device configuration - please review changes .

Note: This action does not enable the WS-M Agent on IDG. This can be done only from IDG for security reasons.

Setup Extended Transactions for all services

Extended Transactions are used to track cross-machine transactions, i.e. messages which are forwarded from one monitored DataPower Gateway to another.
Choosing this option will enable support for extended transactions for services on this domain. This is performed by adding a new step to all the services, which inserts the Extended Transaction correlation ID into the message header. DPOD uses this correlation ID to track the extended transactions.

This configuration should be executed once after installing the system (either at a service or a domain level), or when you need to add extended transaction support for services in the domain. If extended transactions were previously enabled for some of the services in this domain, executing this will add the new step to new services only - the previously configured services will be unaffected.

Note: This action is intrusive and changes your service configuration and may require manual rollback - please review changes .

This step changes or adds some of your monitored device objects. Please review the list of changes before you continue too perform this actions.

Service Level Operation Details

The following task is available for services setup.

Task (Operation)

Details

Setup Extended Transactions

Extended Transactions are used to track cross-machine transactions, i.e. messages which are forwarded from one monitored DataPower Gateway to another.
Choosing this option will enable support for extended transactions for the service. This is performed by adding a new step to the service, which inserts the Extended Transaction correlation ID into the message header. DPOD uses this correlation ID to track the extended transactions.

This configuration should be executed once after installing the system (either at a service or a domain level), or when you need to add extended transaction support for services in the domain. Executing this again for a service that has already been enabled for extended transactions will not change its state.

Note: This action is intrusive and changes your service configuration and may require manual rollback - please review changes .

Browser not supported