Versions Compared

Version Old Version 10 New Version 11
Changes made by

Assaf Cohen (Deactivated)

Assaf Cohen (Deactivated)

Saved on

Key

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

...

This will activate the WS-M subscription for all the services on all the domains, 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 minutesBefore enabling this option, verify that you have sufficient storage on your DPOD device.
Task (OperationDetails

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 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 domain 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 domain, you MUST run "Setup Syslog" using the Domain Level procedure below.

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

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. 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. It can also be executed again , when a new domain is created .
(domains that were previously configured by DPOD for WS-M will be unaffected).To setup WS-M for all domains click the Setup WSM for all domains button 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 is does not enabling enable the WS-M Agent on IDG. This can be done only from IDG for security reasons.

Subscribe to WS-M for all domains

.

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

...

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 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 subscriptions.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, or after creating 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 is not enabling the WS-M Agent on IDG. This can be done only from IDG for security reasons.

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

...