Logging in OSB

Hello,
Can I have separate log files for each project in OSB ?
If yes, then please give me the steps to do so.
thanks,
salil

Salil,
I have configured the same using below post :
http://www.yenlo.nl/nl/custom-logging-in-osb-using-java-call-out/
Separating logs in OSB based on project - is this possible?
http://www.javamonamour.org/2011/07/osb-and-log4j.html
Regards,
Abhinav Gupta

Similar Messages

Using Log4j2 in weblogic for logging in OSB

Hi All,
I was trying to use log4j2 logging in OSB. I did below mentioned steps:
Copied external jars "log4j-api-2.0-beta7" and "log4j-core-2.0-beta7" into %Domain_Home%\lib directory.
Placed wllog4j.jar into same location.
Created log4j2.xml and placed it into %Domain_Home% directory.
Modified setDomainEnv.cmd in %Domain_Home%\bin directory to include log4j2.xml location(set LOG4J_CONFIG_FILE=%DOMAIN_HOME%\log4j2.xml) and enable log4j logging by setting java option(-Dwlw.log.Log4jLoggingEnabled=true)
Content of log4j2.xml looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<configuration status="debug" name="MyApp" packages="">
   <appenders>
      <RollingFile name="RollingFile" fileName="C:/Oracle/MiddlewareNew/user_projects/domains/base_domain/servers/AdminServer/logs/services.log" filePattern="logs/$${date:yyyy-MM}/app-%d{yyyy-MM-dd-HH}-%i.log.gz">
         <PatternLayout>
            <pattern>%d %p %m%n</pattern>
         </PatternLayout>
         <Policies>
            <TimeBasedTriggeringPolicy/>
            <SizeBasedTriggeringPolicy size="10 MB"/>
         </Policies>
         <DefaultRolloverStrategy max="10"/>
      </RollingFile>
      <Async name="Async">
         <appender-ref ref="RollingFile"/>
      </Async>
   </appenders>
   <loggers>
      <root level="debug">
         <appender-ref ref="Async"/>
      </root>
   </loggers>
</configuration>
After setting all the above things, when i am starting weblogic server then i am getting parsing exception in console with error like below:
log4j:ERROR Parsing error on line 3 and column 44
log4j:ERROR Document root element "configuration", must match DOCTYPE root "null
log4j:ERROR Parsing error on line 3 and column 44
log4j:ERROR Document is invalid: no grammar found.
log4j:WARN The <configuration> element has been deprecated.
log4j:WARN Use the <log4j:configuration> element instead.
I am not able to figure out what is going wrong here. In my information log4j2 has done away with namespaces, schema/dtd references and looks like still weblogic is using log4j 1.2 reference. I would really appreciate of one can tell me what is going wrong here.
There was reference to log4j-1.2.8 in my setDomainEnv.cmd as
set POST_CLASSPATH=%POST_CLASSPATH%;%ALSB_HOME%\lib\version.jar;%ALSB_HOME%\lib\alsb.jar;%ALSB_HOME%\3rdparty\classes;%ALSB_HOME%\lib\external\log4j_1.2.8.jar;%DOMAIN_HOME%\config\osb
could this be causing issue? If yes then how can we remove old references of log4j 1.2(if i am removing this entry from here then log4j is giving error for classes not found).
Any input will be helpful.

The log4j:ERROR messages are not coming from Log4j 2 and are most likely from Log4j 1.x. Somehow Log4j 1.x must be getting the log4j2 configuration.

How to configure JCA DBAdapter logging in OSB 11.1.1.4.0?

How to configure JCA DBAdapter logging in OSB 11.1.1.4.0?
I have a project deployed to the new 11.1.1.4.0 version of OSB.
Under previous versions, a $DOMAIN-diagnostic.log file was maintained and contained a record of the activity of the various JCA DB pollers I had configured.
In the most recent version, this is not the case.
I'd like to know if I can restore the old behaviour...
The best solution I could come up with is to change a setting in $DOMAIN/alsbdebug.xml, thus:
<java:sb-debug-logger xmlns:java="java:com.bea.wli.debug">
<java:alsb-jca-framework-adapter-debug>true</java:alsb-jca-framework-adapter-debug>
</java:sb-debug-logger>
With this change the pollers put their logging output into the $DOMAIN.log file.
How can I get the output back into $DOMAIN-diagnostic.log?

Alex,
Oracle B2B does not support custom HTTP listening channels as of now. There are below two default HTTP listening channels for async Request-Response scenarios -
http://host:port/b2b/transportServlet or http://host:port/b2b/httpReceiver
and below one is used for synchronous request-response scenarios -
http://host:port/b2b/syncreceiver
where host - B2B server host and port is B2B server port.
Regards,
Anuj

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

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

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.

Custom logging in OSB

I want to create a common proxy service in OSB which can be called by other services for logging body, fault etc. I intend to log to three different channels : File, Queue & Database. Now the approach is
1. While executing any OSB process, accept a "logDestination" input from the user.
2. Within the OSB process, just do a service callout to the common OSB Logging proxy service.
3. Logging OSB proxy service will read the "logDestination" value and based on that route to a
file proxy service, queue proxy service etc to write logs to respective channels.
Will this work? I tried doing this but i am unable to create and read the "logDestination" value in my common OSB logging proxy service (its in a different project).
Need help in doing this. Thanks!

>
Can you please suggest a better approach ?
>
Well, I don't know your requirements, but concerning logging I'm quite sure that client can't (and shouldn't) decide where to log in service implementation. In other words, you should decide whether to log in file, queue or db in proxy service flow and without any explicit client input.
>
The problem I am facing is that I am unable to propogate the value of "logDestination" to my OSB logging proxy service. In addition to this variable value I also need to propogate the $body of the OSB process to my common logging service.
I hav a service callout (within the stage error handler) from the OSB process to my common service. How can i propogate all the above mentioned details to the common service at the same time ? I am pretty new to OSB, so plz excuse me if thats a basic question.
>
It seems you are not asking this question for the first time. :-)
How to call a OSB proxy service from a different OSB process?
I hope my answer in that thread should help you.

How to have project specific logs in OSB

Hi
I make log entry in osb using Log Action and it works, as i can see logs in Server's log file. But it contains other log entries also...
But i dnt know how do i have separate log file for my projects in OSB, ie how do have separate log file ,where only logs made through Log Action is tracked.
Thanks

Need help in logging the response in single file
Regards,
Anuj

Logging in OSB server keeps running

Do you guys happen to know what would cause the following to run constantly? This is running in my OSB server command prompt window. I want to turn that off.
to=C:\myMiddleware\user_projects\domains\LastDomain\servers\osb_server1\logs\osb_server1.log01000
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
[NewJMSMessagePoller] : Message polling started for MDB ReportingMDB poller 0
Thank you.

I have a project that write to some JMS queues but I don't remember adding that. I keep seeing the same message in the command prompt, looks like every second. Of course now I can't see the real messages that I need to see because this just keeps scrolling.
I need to turn that off I just can't figure out how. I tried everything from the logging tab in the console.
Any other advise?
Thank you.

OSB: Service execution logging/tracing

If I want to log all service (proxy service in my case) execution which way is best? If I enable execution tracing, where could I see execution log in OSB console?
Mainly interested on tracing who, when and which service executed.
Edited by: abobov on 15.05.2012 21:07

To see the message tracing log you have to go to the Weblogic Admin Console under Diagnostics/Log Files, then choose the Server Log for your osb server.I can see service calls (trace) from log file, but it's not very user friendly.
If you need control over service usage, for example I need to know which client use particular service and how often then needed to parse logs to get such statistics. I'm looking for simple table with date, service, client columns.
Maybe some additional Oracle products provide such monitoring features.

Send HTML email using OSB email transport

Hi all
The client we are working for has a specific email template (HTML based) in which emails need to be send. I have tried using the HTML tags to frame this email string, but when I open the email in outlook, I can see the tags as it is. Tags like <p> <br> are not recognised as HTML rather taken as normal strings.
Pls help in framing an HTML based email message using OSB. Thanks

Hi Anuj
Thanks again! You are a life savior. Actually i did check the blog, but the author was modifying http headers in the blog using $outbound variable directly using xpath. So, i just wanted to clarify, if using transport headers for outbound request for email protocol would do the job.
I will check and post back the results. I am currently struggling with OSB and Log4j java callout. I am getting weird logs from OSB server in my interface specific log.

IllegalCharsetNameException: UTF-8 Error OSB

Him,
When i am testing a OSB PS from SOAP ui i am finding the below mentioned error in the logs of OSB server.
<BEA-381304> <Exception in HttpInboundMessageContext.close: java.nio.charset.IllegalCharsetNameException: UTF-8"
java.nio.charset.IllegalCharsetNameException: UTF-8"
But the same OSB ProxyService when tested from test console of OSB works fine with out any error.I tried giving the request and response encoding values of PS,BS as UTF-8..but still it didn't worked from SOAP UI
does some body has any idea about why the error is happening.

the content type header under response meta data is as below
<http:Content-Type>
multipart/related; boundary=MIME_Boundary;
start="<e9e78234904746798a84877ceed04670>";
type="application/xop+xml"; start-info="application/soap+xml"
</http:Content-Type>
And the backend service returns response message along with attachements, the content type of attachments seen in the test console is as below.
Content-Type : application/octet-stream
I am not sure,how to verify if it is set as per RFC format,can you kindly elaborate please
Edited by: 860272 on Jul 6, 2011 12:51 AM

Some questions with respect to OSB 11g

Hi,
I am quite new to OSB 11g and have some queries.
1. If a SOA Composite transaction has been rolled back, how would be reflected in OSB. Would there be any retries?
2. For a composite to use a proxy service, is it a must to use a direct binding reference of OSB? Can't SOA composite simply consider a proxy service a generic web service?
3. Where are the debugging information written to? Can you control what is written to the debugging file? Can you specify filters,level of severity? Can you specify what context variables?
4. Does OSB only runs on WLS and is therefore not hot pluggable on other app servers?
5. One can create, attach WS-policies to my WSDL web services and enforce them on WLS all without using OWSM. If this is possible then what is the role of OWSM?
I would really appreciate any help with these queries.
Regards
Priya.

1. If a SOA Composite transaction has been rolled back, how would be reflected in OSB. Would there be any retries?
If you are calling an OSB Proxy from a SOA Composite and the transaction is terminated and rolled back from SOA Composite then OSB transaction will also be terminated and an error will be logged on OSB side. For retrying I am not sure but there should be an option in the SOA suite composite to retry.
2. For a composite to use a proxy service, is it a must to use a direct binding reference of OSB? Can't SOA composite simply consider a proxy service a generic web service?
SOA Suite composite can directly call a WSDL based Proxy Service as a generic web service. I believe it It should also be possible to invoke an XML/HTTP (Any XML Proxy Service) from SOA Suite composite. Although Direct Binding is the preferred option because of performance and security reasons.
3. Where are the debugging information written to? Can you control what is written to the debugging file? Can you specify filters,level of severity? Can you specify what context variables?
Debug information will be written into the WLS log files by default. You can log any information you want (context variables or custom data) from a Proxy Service message flow using Log action. You can control the severity of log in the Log Action.
You can define what level of Logs will be actually written to the log file and set any custom filters on Logs in the WLS Console (Home>Servers>{Your server Name}>Logging>Advanced).
If you want to enable specific debug logging at the server level(for ex if you want to log transaction details by default), you can do so by enabling needed debug logging at (Home>Servers>{Your server Name}>Debug)
4. Does OSB only runs on WLS and is therefore not hot pluggable on other app servers?
Yes OSB is only certified for WLS.
5. One can create, attach WS-policies to my WSDL web services and enforce them on WLS all without using OWSM. If this is possible then what is the role of OWSM?
Biggest difference is of Scope. You can very well attach WS Policies to services in OSB but their scope will only be of OSB. OWSM can do so at an enterprise level across various applications. OWSM also provides end to end security and SLA monitoring, easier update of Policies across enterprise etc. For more details on OWSM check out this white paper:
http://www.oracle.com/technetwork/middleware/webservices-manager/owsm-11g-tech-wp-134065.pdf

OIM 11gR2 provisioning with GTC

Hello,
We are curently implementing Oracle Identity Manager 11gR2, and we are having difficulties with the implementation of the provisioning from OIM to the Target Systems exposed through a webservice on Oracle Service Bus.
We are using the Generic Technology Connectors as a basis of working. And initially we have created a GTC with only reconciliation Transport & Format Providers:
Connector Name TargetSystem1
Transport Provider (Provisioning):
Format Provider (Provisioning):
Transport Provider (Reconciliation): Database Application Tables Reconciliation
Format Provider (Reconciliation): Database Application Tables Reconciliation
We have configured the Process Definition of TargetSystem1 with all the operations (Create User, Update User, Enable User, Disable User, Delete User, etc.) connected with custom Java implementations, that are working just fine is we trigger them form Eclipse. The “Create User” task has only “Required for Completion”, “Allow Cancelation while Pending” and “Allow multiple instances” check boxes set to CHECKED; it also has all the fields in Integration TAB mapped, Responses mapped, but when we create a User in OIM and provision it with an account on the TargetSystem1_GTC Application Instance, the provisioning process in not accessing the “Create User” task to make the provisioning in the target system. The user that we are trying to provision has the account Status set to “Provisioning” and the Account Type set to “Unknown”. We have also checked the logs of OSB, but there is no activity there, because no request from OIM is being received.
After we investigated more closely the Oracle documentation for the Generic Technology Connectors we discovered that if we do not select Transport & Format Providers during the GTC creation, then the corresponding steps are not performed and they are not initialized, thus the provisioning cannot be done. The documentation also states that if we need to create custom providers in order to make the Provisioning with the GTC, but unfortunately we have no knowledge or any examples on how to do such custom providers for the provisioning of Users from OIM on the target systems via the Oracle Service Bus.
We have installed a second GTC with both provisioning and reconciliation Transport & Format Providers:
Connector Name: TargetSystem2
Transport Provider (Provisioning): Web Services
Format Provider (Provisioning): SPML
Transport Provider (Reconciliation): Database Application Tables Reconciliation
Format Provider (Reconciliation): Database Application Tables Reconciliation
The Web Services and SPML options were the only options that we could select from the out of the box connectors that are installed, and we did not find any other connectors in the download section of Oracle for this product, that can accommodate such communication. So, we configured the provisioning accordingly, and modified the “Create User” task from the TargetSystem2_GTC Process Definition, in order to use our custom adaptor instead of the adpTargetSystem2_GTC adapter that was preset when the TargetSystem2_GTC is created. But this does not help us, because the provisioning is not done, and the “Create User” task is not used. The user that we are trying to provision has the account Status set to “Provisioning” and the Account Type set to “Unknown”.
Next we tried to see if the GTC can be used to communicate directly with the OSB, using the Web Services Transport Provider and SPML Format Provider, and we did not make any modifications to the after the normal installation of the TargetSystem2 GTC. In this case the we can see that the OSB is being accessed by OIM, but unfortunately this case does not help us also, because the operations implemented on the OSB webservice have a different structure then the one SPML expects as default:
Caused by: com.thortech.xl.gc.exception.XSDValidationException: The SOAP response does not contain a valid SPML response type. Should be one of these -->addResponse modifyResponse deleteResponse resumeResponse suspendResponse setPasswordResponse
Do you have any suggestion on how to make the provisioning process work?
Edited by: user1717356 on 22.10.2012 03:22

Hi,
I think you need to put this check only for few attributes?
If Yes, then lets suppose you want to have a check for Country Field in Database which once modified by target Admin, then OIM should know.
1) Create one dummy field CountryDummy (Hidden) in OIM TargetProcess form and dont map it to any target attributes. This dummy field will only store values populated from OIM user profile to -> DB Connector Process Form.
2) On success of "Reconcilation Update Recievced", Put a custom process task which does a comparison with "CountryDummy" & "Country" and inform Admin using email notifications that this mismatch has been found.
HTH,
~J

Publish action not working with JCA based Business Service

Hi All,
I have created one BS in OSB that publish the message in AQ. Its working fine as expected when tested from test console.
I have made one proxy service which after transformation will publish the message to this BS, but the publish action is not invoking.
I have added log action inside request action of my publish action and log is getting generated for that with correct request.However, I cant see message in DB neither can i see any exception/error logs in OSB.
I tried replacing publish with route action and its working fine , message is getting published in AQ.Did any one face this type of issue before ???
Or publish action works only with jms based Business services.
Appreciate your help.
Regards,
Karan

Bingo !!!
Setting QOS helped me to find out the exact error. Was passing complete soap envelope to BS instead of passing body part only.
Thanks a lot for your help mate .
One more query can you please enlighten me on the use of QOS in OSB, such as in what scenarios we should use QOS.
Regards,
Karan
Edited by: Karan Mann on Mar 14, 2013 3:37 AM

OSB file logging settings configuration

Dear Experts,
I need to know if it is possible to log on file all messages of error (i.e $fault variable) during a flow execution without using in the flow neither logs neither report. Is it possible ? If it is, which the correct WLS settings configuration ?
Regards,
Mike
Edited by: Mike.Di on 3-dic-2009 5.55
Edited by: Mike.Di on 3-dic-2009 5.57

I can only think of one solution: using the debugging/tracing facilities of OSB. You could enable execution tracing for a particular proxy service, or you could enable debugging of pipelines in the alsbdebug.xml file in your domain's home. For this WLS's log should have a severity level of debug. Of course this would mean you'd have a lot more messages in the log files, not just the errors. I would not recommend this for a production environment.
Why can't you use the Log action that's specially designed for sending messages to WLS's log file?

OSB Log file

OSB logging using message flow logs the messages to domain admin server log file.
is it possible to route the OSB logs to a central logging system such as sys logs?

You will need to create some Java classes that implement the log4j framework and expose some static methods that will have logger statements.
For ex: Create One java class call SBLogger. This should have the implementation for a log4j logger by reading a log4j.xml or log4j.properties file. And create one static method like logMessage(str LoggerName, strLogMessage, strLogLevel). Inside this method create a logger with the strLoggerName and then have the corresponding logger.debug() or logger.info() type statements based on the log level. Or you can create different methods one each for debug, info , etc... log levels like logDebugMessage(message).
Once you have tested this externally, create a jar file (with the *.class of the log4j implementation) and upload this to the osb console are jar. Ensure that you place the log4j properties file in the config folder of the osb domain, so that osb will be able to load it when it starts up. [After placing the log4j.xml file, you will need to restart the domain for it take effect]
Now using java callout, you can invoke the corresponding logging methods, which will log into the files depending on the log4j.properties appender configuration.
For changing the loglevels on the fly you can refer to a solution given by Ananth @ http://ananthkannan.blogspot.com/2009/10/how-to-change-log-levels-on-fly-using.html
Hope this information will help you to proceed with the implementation. Do let me know in case you run into issues.
Thanks,
Patrick

Logging in OSB

Similar Messages

Maybe you are looking for