Skip to Content
author's profile photo Former Member
Former Member

How to automatically redirect the cds logs to SAP NetWeaver log in ORG MODELLER.

Hi Experts,

We have encountered one issue with CDS.LOG file where in log file is not automatically rolled off.

We manually do the roll log for this file via admin console after every 2 GB of file size.

We raised an OSS message for the same. We were suggested to redirect the cds logs to SAP netweaver logs in ORG MODELLER.

Following is the suggession which we received:

Navigate to following Path - [application directory]/.system/application/log and open provider.properties file.

  • Uncomment the following line :

  1. com.nakisa.log.provider=com.nakisa.framework.utility.log.SAPLogprovider
  2. sap.logger.location=com.nakisa.application
  3. sap.logger.category=Nakisa

  • Comment the following lines:

  1. Com.nakisa.log.provider=com.nakisa.framework.utility.log.log4jlogprovider

On doing so we did not get the logs redirected to NAKISA Net weaver from CDS instead we were able to see the logs in CDS.log file itself.

Further we found that provider.properties file is present in 3 different locations on server we made the above changes in file provider.properties in all the 3 different locations.

After performing these changes IDOC listener was turned off.

Please suggest an appropriate approach so as to automatically roll log the cds.log file or redirect the logs onto Nakisa net weaver.

Thanks and regards,

Rakesh Chilveri

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on Jul 08, 2014 at 05:27 PM

    Rakesh.

    Try setting the following files in the [application directory]/.system/application/log directory and the [application directory]/.system/application/WEB-INF/lib/log/ (forgive any case inaccuracies in the file path).

    FILE: provider.properties

    com.nakisa.log.provider=com.nakisa.framework.utility.log.Log4JLogProvider
    
    ! To support SAP Logging:
    ! com.nakisa.log.provider=com.nakisa.framework.utility.log.SAPLogProvider
    ! sap.logger.location=com.nakisa.application
    ! sap.logger.category=Nakisa
    

    i.e. you're just undoing the change you were given.


    FILE: log.properties

    log4j.rootLogger=INFO, A1
    
    log4j.appender.A1=org.apache.log4j.DailyRollingFileAppender
    log4j.appender.A1.File={home}/Log/cds.log
    
    log4j.appender.A1.DatePattern='.'yyyy-MM-dd
    
    log4j.appender.A1.layout=org.apache.log4j.PatternLayout
    log4j.appender.A1.layout.ConversionPattern=%d{dd MMM yyyy HH:mm:ss} %-5p %c %x - %m%n
    

    Once changed, restart NetWeaver to force the changes to be picked up by the logger.

    This should thenset the logging to roll daily for both user/AdminConsole use and the automated extract job use.

    I'm sure it goes without saying, but I'll say it anyway ... please backup these files before making any changes so that you can return to your original position just in case this doesn't work.

    I would also suggest giving some consideration to adding the log.properties file to your OrgModeler build .delta so that if you have an update and load in the build, the reverted log.properties file will be updated when you publish the build (and picked up at next restart).

    Regards,

    Stephen.

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Rakesh.

      By "cds.log file was not automatically generated for us" are you saying that the log entries were written to an existing log file? If that's the case did you restart NetWeaver?

      I guess there's a chance a file handle could still be linked back to it so you could also try a post-restart log roll and then see if a new log is generated the following day.

      I've had success with this set of amendments and beyond piping the log to SAP logging (as presented in the commented out lines in the log configuration files; which I've never actually opted to do), I'm afraid I don't have any alternate suggestions at this time. These files are THE way to control what happens to your log so amending them should have some effect ... but it sounds like you aren't seeing any effect at all.

      If the above additional suggestions do not work and no one else can offer up any further suggestions I would suggest you raise the issue via OSS.

      Regards,

      Stephen.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.