Versions Compared

Version Old Version 7 New Version Current
Changes made by

Hanan Kenan

Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

Warning

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

...

This screen displays a table containing information on all the monitored devices connected to DPOD's console, and lets the 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:

...

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

  1. 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.
  2. 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.

...

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

  1. 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.
  2. 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.
  3. 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 devicedomain. Consult the tables at the end of this page to find details about the available tasks.

...

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

  1. 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.
  2. 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.
  3. Click on one of the services.
    The system displays the service's details and a list of all endpoints in the service
  4.  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 deviceservice. Consult the tables at the end of this page to find details about the available tasks.

...

Warning

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

...

The following tasks are available for devices setup.

Subscribe to This will activate the WS-M subscription services on all the domains, so that message payloads are recorded and sent DPOD WS-M . whenever there is need to inspect the payload of transactions.
This option may affect service performance of both of your monitored device and DPOD, and WS-M subscriptions are therefore only active for 60 minutes.
Before enabling this option, verify that you have sufficient storage on your DPOD device.
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.

Setup WS-M for all domains

Sets up WS-M configuration in all domains, so that it can later be activated by WS-M subscriptions.
This configuration should be executed once after installing the system. It can also be executed again when a new domain is created.
(domains that were previously configured for WS-M will be unaffected)
To setup WS-M for all domains click the Setup WSM for all domains button.

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

Setup Extended Transaction 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 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 .


Warning

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

...

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 you need to redirect 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 WS-M configuration in this domain, so that it can later be activated by WS-M subscriptionsthe necessary configuration for all the domains to send payload data to the selected agent.
This configuration should be executed once after installing the system, or after creating when a new domain .

Subscribe to WS-M

This will activate the WS-M subscription for all the services on this domain, so that message payloads are recorded and sent to the selected DPOD WS-M agent.
This configuration should be executed whenever there is need to inspect the payload of transactions.
This option may affect service performance of both of your monitored device and DPOD, and WS-M subscriptions are therefore only active for 60 minutes.
Before enabling this option, verify that you have sufficient storage on your DPOD device.

Setup Extended Transaction 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 .


Warning

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

...

Task (Operation)Details
Setup Extended TransactionTransactions

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 domainthe service. This is performed by adding a new step to all the servicesservice, 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 .