Skip to Content
Having this server and being the fist Java EE 5 certified is really nice and I am sure it will run most of the time without any problems but from time to time you will have to administer it and maybe change something on it. And you need the tools to do it. These are described in the Administration Guide, so here I’ll just give you a quick preview of what’s new.   After you finish the installation you get the SAP MMC console and also the telnet interface to the engine. For simple administrative tasks they provide nice coverage of your needs and I use them in my everyday work.  What happens if you want to do more complex stuff like checking the logs your application have produced or change the severity of your location or category? If you remember the old days of NetWeaver04 and NetWeaver04s there was a standalone Swing tool called Visual Administrator (VA). Its purpose was to manage Java part of the NetWeaver stack and it was not always easy to use unless you were well trained for it and had deep knowledge of the architecture of the NetWeaver. As a web-based tool it only needs a browser to run and can easily go over firewalls.  Nowadays the standard is web-based tools, hence the standalone VA is gone. What you have now is a web based tool called the NetWeaver Administrator or shortly – NWA. image Each service in VA provided certain functionality and you needed to know the exact service in order to do what you need. You had to be a NetWeaver and Java expert. For instance if we take logging you need the LogConfigurator and LogViewer services but with them it is easy to guess what they do. With NWA you get task-oriented navigation and there is no need to know the architecture of the Java AS to do administration and you even do not have to know what Java AS service is. You only need to know what you want to do from administration perspective, i.e. start/stop, change configuration, view logs and so on. Functionality is grouped in work centers and work sets based on different tasks you have to do.  Also there are many new and cool things in NWA which you do not get in VA.   So let’s take logging as an example. Bellow you see a snapshot of the LogViewer. It is much easier to use it than the VA version, you can set different filters and define custom views and save them for future use.  Moreover – now Log Viewer merges all your log files into one data set and you can search and filter through all of them in one go. Over the web. Even connect to a system on which the Java engine is down. No files exchanged. There is also navigation between related functionality and from LogViewer you can access the LogConfigurator to change severities and go back to the LogViewer. Another big advantage is that there is common UI Look and Feel for all functionality exposed in NWA. image As a real preview only part of the functionality that will be available is present in NWA. Another big advantage of NWA over VA is that it can manage more than one system ay a time in case you have a landscape of systems but this is out of scope for the SDN preview installation.    NWA is available as an add-on in your installation of the SDN preview. You can install NWA by running the install.bat located in folder \JP1\JC00\j2ee\NWAdmin. In case you have made a custom installation it is possible that path differs.    NWA is located at http://localhost:5XX00/nwa where XX is the system number of your installation. For default installation it is 00 and the http port must be 50000.
To report this post you need to login first.


You must be Logged on to comment or reply to a post.

    1. Hi Michael,

      yes you are right that the first version of NWA was released in SP12 of NW04 but the one that we want to present here will be part of the new major release of the NW.

      In this version of NWA there will be more functionality than in NW04/NW04s and the most important thing that we want to stress here is that there will be no more VA and NWA will substitute it.

      As every preview not everithing is shown because we are still in development at the moment.

      greetings Georgi

    1. Hi Deepu,

      Sorry for not replying early but somehow the SDN did not send me a notification that there was an update on the blog.

      The next release will be in 2007 but I can not be more specific about a date about that you should contact our marketing department.

      greetings Georgi

  1. Former Member

    I found your blog is very helpful. But I have a question about those logs and trace files. Where are they stored in file directory? What will be the file names be? I checked defaultTrace, they are not there.


    1. Hi Natalie,

      logs by default should be located under folder \j2ee\cluster\server0\log as they were in NW04/04s and we haven’t change the location. The log folder is creted below the working directory witch usualy is the “serverX” folder.

      You can check the destions where logs and traces are written in the config tool (\j2ee\configtool\configtool.bat). When you open it you navigate “cluster-data -> template – … -> instance – ID… -> log-configuration -> destination” . For each destination there is a patern witch defines the file name and the location.

      On what OS have you isntalled the preview and have you changed anything with the config tool or the LogConfiguraton plugin from NWA ?

      greetings Georgi

  2. Former Member


    Thank you for this useful (and understandable)blog !

    I’m trying to activate some traces using the NWA (

    More particularly, we need to trace the users who connect to the portals and then lauch http requests.

    I’ve activated
    HttpAccess  ALL
    CommonLogFormat ALL

    Destination  : ./log/system/httpaccess/responses.trc

    The new configuration is then saved.
    the problem is the log file is not updated, (since december 2005 !) …

    I really don’t know why ?
    Any idea.
    Best Regards.


Leave a Reply