This weblog is intended as a sequel on the infamous Blog Series of Craig Cmehil regarding the MiniWAS 620 (Mini Me of WAS 6.20, the Saga continues….) and his travels. I recently installed the NetWeaver 2004s Sneak Preview with ABAP Stack in order to play around with WebDynpro for ABAP (WDA) and therefore had to say goodbye to my good old MiniWAS. This blog assumes you have successfully installed the WAS 700 as outlined in the
. As a note on this installation I must say that the actual process is many, many times easier as its 620 counterpart. Craig, this installation looks like heaven compared to our MiniWas 620 endeavors ;-).
I also would recommend that you register your local installation as described in
. In order to complete this process, ensure you log on to your machine as user nspadm in order to avoid any issues during registration.
As seen in the picture above this weblog will contain the steps for all you out there that would like to upgrade their NetWeaver 2004s installation from Service Pack (SP) 5 to the most recent version SP8 and/or further when available. This since every SP upgrade adds new functionalities to your local installation this enables you to gain exposure to SAP’s most recent development efforts. During my previous experiences I had several more or less basic knowledge gaps regarding the actual upgrade process that I will try to fill in this blog. Also you might want to have a look at the blog Thomas Jung wrote on this subject: Apply Support Packages to the SDN ABAP-AS Sneak Preview
Step 1: Download SAP kernel patches -OPTIONAL-
Even tough given the current SP requirements do not require a kernel upgrade; I will execute this upgrade to complete the information in this weblog. Kernel upgrades are divided into database independent and database dependent portions. The sneak preview of SAP NetWeaver 2004s ABAP edition comes packed with Kernel version 23 and at the moment of writing this blog patch level 58 is available. First step is to download the newest kernel version located at on the SAP Support Portal. Here you select the Kernel version for WAS 700 32 bit, select your operating system (Windows Server on IA32 bit) and download the database independent file as well as the database dependent file for MaxDB.
Step 2: Download the latest SPAM/SAINT release
Download the possible SPAM/SAINT (SAPKD700*) updates that are available. Use transaction SPAM to determine your current version (download comes with release 19). Similar as the regular support packages ensure no additional import conditions are mentioned.
Step 3: Download the relevant support packages for BASIS and ABAP components
Download the Basis (SAPKB700) and ABAP (SAPKA700) SP’s that are available for WAS 700 higher then release 05 on the SAP Support Portal. Also check whether there are any additional conditions in place before applying the SP. Place the available SP’s in your download basket and assume downloading. In the situation additional requirements are identified also download these components, e.g. Kernel, TP.
Step 4: Unpack and installing the Kernel patch -OPTIONAL-</b>
<p>Locate your Kernal files and move them to a temporary directory. Unpack these files into this directory using the following command: sapcar.exe –xvf “<name>.CAR” –r “<destination_dir>”. Ensure the sapcar application is not located in the <destination.dir> since this will result in a partial unpacking process. After a successful unpacking stop the SAP NSP System and ensure all SAP related services, e.g. x-server, are stopped. Now make a back-up of your ‘usr’ directory just in case your need to return to the old kernel version. Execute the actual kernel upgrade by moving the <destination.dir> content to the following directory: ‘<drive>:usrsap<SAPSID><INSTANCE>exe’ and the non-unicode destination: ‘<drive>:usrsap<SAPSID>sysexe
uc<platform>’. Restart your system and compare your extended status information to the picture below.</p>