Oracle BEA WebLogic sample event messages

Use these sample event messages to verify a successful integration with IBM QRadar.

Important: Due to formatting issues, paste the message format into a text editor and then remove any carriage return or line feed characters.

Oracle BEA WebLogic sample messages when you use the Log File protocol

Sample 1: The following sample event shows that the server has successfully established a connection with the domain level diagnostic service.

####<Oct 15, 2012 4:27:41 PM MST> <Notice> <Log Management> <qradarTesting.qradar.test> <sgss_ManagedServer_1> <[STANDBY] ExecuteThread: &apos;1&apos; for queue: &apos;weblogic.kernel.Default (self-tuning)&apos;> <<WLS Kernel>> <> <> <1350343661416> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>

Sample 2: The following sample event shows that the NetUIx container is initializing.

####<Dec 17, 2012 1:51:34 PM MST> <Info> <netuix> <qradarTesting.qradar.test> <AdminServer> <[ACTIVE] ExecuteThread: &apos;0&apos; for queue: &apos;weblogic.kernel.Default (self-tuning)&apos;> <<anonymous>> <> <> <1355777494726> <BEA-423101> <[consolehelp] Initializing the NetUIx container>

Sample 3: The following sample event shows that a node manager command has failed.

####<Oct 15, 2012 4:19:42 PM MST> <Error> <NodeManager> <qradarTesting.qradar.test> <AdminServer> <[ACTIVE] ExecuteThread: &apos;0&apos; for queue: &apos;weblogic.kernel.Default (self-tuning)&apos;> <weblogic> <> <> <1350343182323> <BEA-300033> <Could not execute command "getVersion" on the node manager. Reason: "Connection refused. Could not connect to NodeManager. Check that it is running at localhost:5556.".>