Skip to Content

In part I of this series I was talking about an alternative architecture for the setup of the Developer Workplace to handle it in a smaller environment. Now we want to look into what you can improve to run the environment in the standard single machine mode.

Most of the changes I mention here will be part of Service Release 2 (SR2) which is planned for later this year. Service Release means there will be a complete new installation set that includes all SPs up to that time. Once you have this version and install it, no updating of former SP’s is needed (Yes, there are people who might not know this). This means also that once you got this SR2, this article becomes irrelevant! 


Installation Issues



There are a couple of minor issues that cannot really stop you if you’re tough enough, but my understanding of simplicity (one of our core values) is that these should not appear during the installation of a product.

  • There is a small bug in the JDK of Java 1.4.2_10 that unfortunately hits
  • The installation usually stops and tells you that your system does not meet recommended system values a.k.a. swap space. The value that the installation program expects is based on an erroneous calculation that asks for more then 7 GB of swap space. As you can imagine, this is impractical and can be ignored. Unfortunately the option to ignore this message is named “Cancel”. If you really read the message in the window (who does ever?), you will find out that pressing “Cancel” does continue the installation.

 
   
  (To the new users: J70 is the three letter system name that SAP uses everywhere for a reason that nobody remembers any longer and JC03 is a instance name, that may vary in your system). We will change a couple of values that are related with the Java Virtual Machine. I don’t want to go into the details what they do, but I wrote about this last year in my blog The -X Options: Secrets of Web AS Java

Once you have started the config tool, you have to connect to the database (if you haven’t answered the questions at startup to do so) by pressing the icon on the very left of the command menu. After the connection is established you will see the system tree in the navigation path and should go down to the instance level of your system. Here you could write down general values for all processes, but as we usually work with a single server we can be more specific. There are two leaves beyond this and this is your dispatcher and the actual server. Both have the tab “General”, which includes the Java parameters.

 
 

Here you can set your parameters to the values according to this table:

 Memory settings for dispatcher  Memory settings for server

MaxHeap: 32

Xms 15M

NewSize 5M

MaxNewSize 5M

MaxHeap 512

PermSize 64M

MaxPermSize 128M

Xms 50M

NewSize 15M

MaxNewSize 15M

 

As you are already there it is good advice to set your debug default mode ON. This can be done on the last tab of the server configuration called “Debug”. Click there on the “Enable Debug Mode” checkbox.

This way you save the turnaround for a debugging reboot of your local server.

Don’t forget to push the save button. To make your changes run, your server has to be restarted.


Some Profiling 



#—-



 
# Start internet graphics server

#—-



 
_IG = $(DIR_EXECUTABLE)igswd$(FT_EXE)

Start_Program_05 = local $(_IG) -mode=profile pf=$(_PF)

If you just place a #-sign into the last two lines, you have switched off the internet graphic server that builds graphics for browsers, based on data it gets from the server. Be aware that this means you won’t see nifty graphics in the NetWeaver Administrator nor in the graphics you build into your Web Dynpro applications. They will appear as empty space.


Some Servicing



At least one system service that is installed with the system is not needed at all in a development system. That is a service called “saposcol”. Usually it is collecting system data of a server to forward it to a central system for monitoring in CCMS. As we are not connecting a development system  to such monitoring it does not make sense that it runs. It can be easily deactivated in the  Windows system. To your convenience a short description:

    1. In the Start menu go to the icon of your system and right-click it
    2. chose “Manage”
    3. In the management tree go down to “Services and Applications” and Services

    4. Go down the list to the Service called “SAPoscol”
    5. Right-click the service and chose “Properties”
    6. Change the startup option there to “Manual”

You’re done.


Bare Necessities 



In addition there are a lot of services in your Java server that you do not need. Unfortunately services you switch off depend a lot on what you are doing. Detailed information on this can be found in note   871394 (link only works on access to service marketplace). The note has an attached Excel file that includes a link of all services with notes on importance of a service and effects in case of its switch off, along with other useful information.

The services can be switched off from Visual Administrator as this can be done with NetWeaver Administrator. As the latter is browser based I’ll describe this more convenient way.

    1. Start your browser.
    2. Type in the url for a local server. For a first installation this should be localhost:50000 (digit 2 and 3 are the instance number).
    3. Login as the Administrator (with the general password you have assigned during installation).
    4. The browser shows the Engine start page. Choose the link to the NetWeaver Administrator.
    5. From here you navigate through “System Management”-> “Administration”->”Systems”
    6. In the SAP Systems page choose your instance
    7. In the details list choose tab “Services”
    8. Here you can select services and stop them


 A Word On NetWeaver Developer Studio



 One small action on the NetWeaver Developer Studio can save you a lot of time. For some reason it seems that the installation misses a small file from eclipse that contains the build number. Without this file the Studio needs more then 5 minutes to start up. With it, this task is done in less then 30 seconds. The file should work, if you open Textpad write to the first line: “Build: 200511250257” and save the file with name “buildnum.txt” to the directory C:Program FilesSAPIDEIDE70eclipse.

 

This is it. If you have more suggestions, you’re welcome to post them or email to me. Meanwhile I will check to put all those goodies directly into the product.

 


Post Release Additions



A colleague added the following useful hint. There are two things to switch off on a local server because they make no sense there. That is compression and local caching of http output. As your communication is local, it should be obvious that this can be switched off.

To switch of the cache can be already done with the new NetWeaver Administrator. You can call it with your browser pointing to http://localhost:50000/nwa usually (digit 2 and 3 have to show the instance number of your dispatcher, which is the case if it is your only installation).   

Once the Administrator appears you click through to System Management->Configuration-> Virtual Hosts->default->Details. There, in the General tab you can deactivate the “Use Cache”-box.

More has to be done for the deactivation of compression. For this you need to start the Config-Tool, connect it to the database (it will ask to dothis for you when starting) and go in the tree there to the global server configuration->services->http. In the value list you can change the value for AlwaysCompressed to a blank and CacheSize to 0.  

To report this post you need to login first.

4 Comments

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

  1. stadlers stadlers
    Hi. Realy Nice Blog. But I couldn`t find information about system parameters (memory, cpu clock, OS and etc.) for witch was this memory parameters optimalized. I test this installation on Win2000, 1G Ram, 3GHz cpu) and starting with your parameters contains about 30min and installation on Win2000 was quite problematical. Last installation step (configuration minimal configuration for java) in sapinst wasn`t correct. I need manualy chanege memory paramaters, restart server and continue in installation.
    My configuration:

    dispatcher
    MaxHeap: 203M
    Xms:203M
    NewSize:68M
    MaxNewSize:68M

    Server
    MaxHeap: 512M
    Xms:256M
    NewSize:85M
    MaxNewSize:85M
    PermSize:192M
    MaxPermSize:192M

    This memory prameters I found in some SAPnote for NW04 (not s) but I couldn`t find parameters for message server. As I can see ther is strating size 256M. Isn`t that much ??

    (0) 
    1. Benny Schaich-Lebek Post author
      Hi stadlers,

      – we’re talking about Developer Workplace, that only exists for Windows.
      – I gave you a minimum memory configuration that should work. Why do you think this would change once your CPU or memory size changes? Of course, with more memory you can spend more for the server…
      – I don’t get your point about the last installation step. Could you be more specific here?

      – If those parameters work for you it’s ok

      – The message server program is not java but a native executable. To my information it is not possible to define it’s size.

      Regards,
      Benny

      (0) 

Leave a Reply