Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


IBM DataPower

The JSA DSM collects event logs from your IBM DataPower system.

IBM DataPower is formerly known as IBM WebSphere DataPower .

The following table identifies the specifications for the IBM DataPower DSM.

Table 1: IBM DataPower DSM Specifications





DSM Name


RPM file name


Supported versions

FirmwareV6 and V7



JSA recorded event types

All Events

Log source type in JSA UI

IBM DataPower

Auto discovered?


Includes identity?


Includes custom properties?


For more information

IBM website

To send events from IBM DataPower to JSA, complete the following steps:

  1. If automatic updates are not enabled, download and install the most recent version of the IBM DataPower DSM from the Juniper Downloads onto` your JSA console.

  2. For each instance of IBM DataPower, configure the IBM DataPower system to communicate with JSA.

  3. If JSA does not automatically discover IBM DataPower, create a log source for each instance of IBM DataPower on the JSA console. Use the following IBM DataPower specific values:



    Log Source Type

    IBM DataPower

    Protocol Configuration


Configuring IBM DataPower to Communicate with JSA

To collect IBM DataPower events, configure your third-party system to send events to JSA.

Review the DataPower logging documents to determine which logging configuration changes are appropriate for your deployment.

  1. Log in to your IBM DataPower system.

  2. In the search box on the left navigation menu, type Log Target.

  3. Select the matching result.

  4. Click Add.

  5. In the Main tab, type a name for the log target.

  6. From the Target Type list, select syslog.

  7. In the Local Identifier field, type an identifier to be displayed in the Syslog event payloads parameter on the JSA user interface.

  8. In the Remote Host field, type the IP address or host name of your JSA Console or Event Collector.

  9. In the Remote Port field, type 514.

  10. Under Event Subscriptions, add a base logging configuration with the following parameters:



    Event Category


    Minimum Event Priority



    To prevent a decrease in system performance, do not use more than one word for the Minimum Event Priority parameter.

  11. Apply the changes to the log target.

  12. Review and save the configuration changes.