Separating logs in OSB based on project - is this possible?

Question

Hi,
I'm using OSB 11.1.1.3.0 and I'd like log messages generated from the log action to go to a different log file based on OSB project. I've found messages on the forum that discuss this, for example:
alsb logging
These posts only explain how to log messages from ALL OSB projects in a domain to a SINGLE log file, which I already have working using a LogFilter, but I'd like to take it a step further and log messages to a different log file depending on the specific project where the log action was invoked.
I want to use a method that involves LogFilters rather than explicit OSB Reporting or File business services, to keep it unobtrusive from the perspective of the application developer.
I've checked the output of the LogRecord methods and I don't see anything that will let me get a handle on the specific project a log originates from, but I've noticed that at the start of each log message information is logged inside [], for example:
[raiseEvent Operation, raiseEvent Operation_request, stage1, REQUEST]
This looks promising but unfortunately it doesn't always contain the OSB project name (sometimes it does, but not in this example).
So my questions are:
1. Has anyone successfully split logs based on OSB project using the WLS/JDK logging system?
2. Is there a way to specify what is logged in the [] at the start of each log message?
Any help is much appreciated.
Thanks,
Jason

Answer 1

It has been done in a previous client by the then BEA in a different manner. Instead of using any java callouts or log4j code within osb, that task has been shifted to a weblogic startup class. So this is how it works:
At OSB
Use Log action to record log messages. Put appropriate annotation based on the project to categorize the log messages into different files later.
Example: Log : Request Message Processed succesfully. Annotation: OSB_LOG: <Project_Name> Severity: Info. Note Annotation has 2 parts : a hard coded OSB_LOG and a variable +<Project_Name> part+
This log message gets recorded in the manged server log file as : Info: OSB_LOG:<Project_Name> Request Message Processed successfully
At WLS
You have to configure the logging settings of the server so that this log message reaches the domain logger. For e.g. server should be configured to broadcast to domain logger at severity info and above if you want to get the above message
Startup class
This startup class will be deployed to the admin server. What it does is in the startup method gets the domain logger and registers a custom handler to it. The custom handler is implemented to inspect each LogRecord it gets from domain logger to check for the presence of hard coded string (OSB_LOG) . If the record has this string then it understands this log record has come from OSB application and not from any WLS subsystem and hence this message is important to it. Next step is to determine the logger name by getting the <Project_Name> from the Log Record. It creates a new logger with the same name as that of Project_Name and logs the message with the same severity as in the original message.
One key advantage of this is that is if your OSB is deployed to a cluster, you will get log messages from all managed servers for that particular project ( or a proxy service) at one location.