Skip to Content
Author's profile photo Former Member
Former Member
June 8, 2005 2 minute read

Netweaver Portal Log Configuration & Viewing (Part 3)

Welcome to the final part two of my weblog about Netweaver Portal Log Configuration & Viewing.
Part one: Netweaver Portal Log Configuration & Viewing (Part 1).
Part two: Netweaver Portal Log Configuration & Viewing (Part 2).

Configuring Log Destinations

If filtering is not powerful enough for your needs, there is still a way to log into dedicated files. SAP note 733903 explains how to accomplish that.
“Please, keep in mind that in productive environment the default settings should not be changed because of performance and supportability reasons.”
“ForceSingleTraceFile” must be set to “YES” on productive systems for supportability and performance reasons. Instead of setting the property to “NO”, I recommend to make use of the “SingleTraceFile_UnrestrictedLocations” property.
This property is not supported by SAP and therefore its usage is only allowed for development and integration systems!

  • open the Visual Administrator
  • in the tree to the left, browse to -> Server -> Kernel -> LogManager
  • add your log location to the property “SingleTraceFile_UnrestrictedLocations”. For the example, com.sap.portal.com.mycompany.portal.foo has to be entered. Multiple entries can be separated with an “;”
  • save and restart your server(s)

    image

    Now you are able to define a log destination (e.g. a file) for your log location.

  • browse the tree on the left to -> Server -> Services -> Log Configurator
  • click on the button “To advanced mode”
  • click on the tab “Destinations”
  • click “New”
  • enter the required information, for example:
    Name: com.mycompany.portal.foo
    Type: FileLog
    File Name Pattern: ./log/foo.log
    Maximum File Size: 1048576
    Number of Files: 3
  • click “OK”

    image

    Now, the new destination can be assigned to our location.

  • click on the tab “Locations”
  • expand the nodes com -> sap -> portal and then your location (com.mycompany.portal.foo in the example)
  • in the right window (“Destinations”), click “Add”
  • select your destination and click the button “Select”
  • save your changes

    Attention: A destination can only be assigned in the “Advanced mode” with the property “SingleTraceFile_UnrestrictedLocations” set accordingly.

    image

    Now, all log messages that refer to the specified location should be written into a dedicated file according to your file name pattern.
    This should enable every developer to debug his/her portal applications in a practical way.

    And the final question: “Where are my System.out.println messages???”
    Oh boy, did you really ask that? Go Directly to JAIL! And don’t pass “Go” 😉
    Cheers, Karsten

    • Assigned Tags

        4 Comments
        You must be Logged on to comment or reply to a post.
        Author's profile photo Former Member
        Former Member
        Karsten,
        Great work. One of the most basic must knows.
        One of the best in the recent days.
        Regards
        -Venkat Malempati
        Author's profile photo Former Member
        Former Member
        Thanks Karsten, I guess more than a few developer are very glad you wrote that excellent weblog.

        Cheers Martin

        Author's profile photo Former Member
        Former Member
        Essential info for anyone managing ep.

        Kudos

        Jeremy Baker

        Author's profile photo Former Member
        Former Member
        I was looking this weblog as we were migrating from EP 6 to NW, I must tell you this saved me lot of agony. Thanks

        Venkat