Este contenido no está disponible en el idioma seleccionado.
Chapter 22. System Auditing
22.1. Message Store Copiar enlaceEnlace copiado en el portapapeles!
Note
22.2. Service Route Filter Copiar enlaceEnlace copiado en el portapapeles!
org.jboss.internal.soa.esb.message.filter.ServiceRouteFilter
) is an auditing mechanism that allows you to track a message's path through different services. Like any other filter, you need to enable it from within the jbossesb-properties.xml
file.
22.3. Audit the Data in the Message Store Copiar enlaceEnlace copiado en el portapapeles!
Procedure 22.1. Task
- Open
jbossesb-properties.xml
in a text editor:vi jbossesb-properties.xml
- Go to the section called filters and edit it as per the following code sample:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Save the file and exit.it will now check messages and services for whether or not service route information should be recorded. On either a per-service or a per-message level, you can tell the filter to add the route information into the context.
- To configure it on a service level, add recordRoute="true" in your service definition.
<service category="FirstServiceESB" name="SimpleListener" description="Hello World" recordRoute="true">
<service category="FirstServiceESB" name="SimpleListener" description="Hello World" recordRoute="true">
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - To configure it on a message level, add a service-record-route property to the message properties and set it to
true
.
22.4. TraceFilter Copiar enlaceEnlace copiado en el portapapeles!
org.jboss.internal.soa.esb.message.filter.TraceFilter
) is the JBoss Enterprise SOA Platform's meta-data filter. Its role is to record entries in the log whenever a message interacts with a component. It enables you to trace an event and have information on it returned to you. For example, you can set it to trace certain kinds of messages and display their movements to make it easier to monitor them.
22.5. Log Message Copiar enlaceEnlace copiado en el portapapeles!
22.6. Identify a Log Message Copiar enlaceEnlace copiado en el portapapeles!
Procedure 22.2. Task
Determining if a Message is a Log Messages
To identify a log message, open it up and see if it adheres to the following format:header: [ To: EPR: PortReference < <wsa:Address ftp://foo.bar/> >, From: null, ReplyTo: EPR: PortReference < <wsa:Address http://bar. foo/> >, FaultTo: null, Action: urn:dowork, MessageID: urn:foo/bar /1234, RelatesTo: null ]
header: [ To: EPR: PortReference < <wsa:Address ftp://foo.bar/> >, From: null, ReplyTo: EPR: PortReference < <wsa:Address http://bar. foo/> >, FaultTo: null, Action: urn:dowork, MessageID: urn:foo/bar /1234, RelatesTo: null ]
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
22.7. Filter for Log Messages Copiar enlaceEnlace copiado en el portapapeles!
Procedure 22.3. Task
Open the jbossesb-properties.xml File
Open thejbossesb-properties.xml
in a text editor:vi SOA_ROOT/jboss-as/server/PROFILE/deployers/esb.deployers/jbossesb-properties.xml
.- Scroll down to the "Filter" section of the file.
- Set the org.jboss.soa.esb.messagetrace property to on. Now that it is enabled, every message that passes through it is logged.
- To gain more precise control over which messages are logged and which are ignored, set the org.jboss.soa.esb.permessagetrace property to on as well. This causes the filter to ignore those messages for which the org.jboss.soa.esb.message.unloggable property is set to yes.
Save
Save the file and exit.
The TraceFilter is switched on. Whenever a message passes through this filter, you will see the following at the information level:
Note