TEC Workbook - IBM

TEC Workbook - IBM TEC Workbook - IBM

23.02.2013 Views

IBM Software Since there has been minimal activity in your student domain, your log will likely contain only one or two messages. The following image shows a more active log. For additional filtering, you can click a transaction id (tid), client IP address, or error code. Each of these opens a new window with messages related to the selected value; for example, clicking a transaction ID displays only messages from that transaction. 1.13.2 Log targets The logging subsystem on WebSphere DataPower SOA Appliances is based on the “publish-subscribe” paradigm that enables distribution of selected messages to various protocols and destinations. Publishers include the DataPower appliance itself as well as the various user-configured services and their supporting objects. For example, the DataPower appliance may log a message to indicate that a network connection is failing. Similarly, a user-configured MQ front side handler may log a message to indicate that the queue manager has become unresponsive. Log targets act as the subscribers to published messages. Log targets can: ● Capture messages and forward them to a variety of different logging server types such as syslog and syslog-ng. ● Save messages in DataPower’s flash memory or on the built-in logging hard drive. ● FTP saved log files off the appliance to an FTP server. ● Subscribe or suppress messages by event codes or category. ● Filter messages for a specific user-configured object. ● Filter messages associated with a specific IP address. Page 22 WebSphere Lab Jam

● Trigger a set of actions to occur when a specific log message is received. __1. Expand the navigation tree to expose the Manage Log Targets option. The path is: Administration � Miscellaneous � Manage Log Targets __2. Click Manage Log Targets. Click the Add button to create a new Log Target. __3. On the Main tab, Locate the Target Type field and click the dropdown to reveal the list of available log target types that you can create. You should see a list similar to the following image. IBM Software Lab 1 – Introduction WebSphere DataPower SOA Appliances Page 23

<strong>IBM</strong> Software<br />

Since there has been minimal activity in your student<br />

domain, your log will likely contain only one or two<br />

messages. The following image shows a more active log.<br />

For additional filtering, you can click a transaction id (tid), client IP address, or error code. Each of these<br />

opens a new window with messages related to the selected value; for example, clicking a transaction ID<br />

displays only messages from that transaction.<br />

1.13.2 Log targets<br />

The logging subsystem on WebSphere DataPower SOA Appliances is based on the “publish-subscribe”<br />

paradigm that enables distribution of selected messages to various protocols and destinations.<br />

Publishers include the DataPower appliance itself as well as the various user-configured services and<br />

their supporting objects. For example, the DataPower appliance may log a message to indicate that a<br />

network connection is failing. Similarly, a user-configured MQ front side handler may log a message to<br />

indicate that the queue manager has become unresponsive.<br />

Log targets act as the subscribers to published messages. Log targets can:<br />

● Capture messages and forward them to a variety of different logging server types such as<br />

syslog and syslog-ng.<br />

● Save messages in DataPower’s flash memory or on the built-in logging hard drive.<br />

● FTP saved log files off the appliance to an FTP server.<br />

● Subscribe or suppress messages by event codes or category.<br />

● Filter messages for a specific user-configured object.<br />

● Filter messages associated with a specific IP address.<br />

Page 22 WebSphere Lab Jam

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!