Hate slightly outdated docs which seem to be applicable at first sight but
then leave you out in the rain when it comes to the details? Okay, here comes
my quite popular blog on Installing and operating the SAP NetWeaver J2EE Preview (Installing and operating the SAP NetWeaver J2EE Preview)
updated and enhanced for the
SAP NetWeaver Application Server, Java(TM) EE 5 Edition.
</p>
Pre-Installation Considerations
If you already have the SAP NetWeaver J2EE Preview installed on your
machine please refer to the chapter Update Tips.
There's no need to search the installation prerequisites for a specific JDK
as the SAP NetWeaver Web Application Server (NWAS) comes with its own.
The NWAS is a little picky regarding its network environment, so if you
intend to run the server without an active network connection (plane, train,
...) be sure to:
Install the MS Loopback Adapter as described in the DOC folder
of the unpacked RAR file (DOC/html/loopback.htm).0.1.
0.2.
Disable VMware Virtual Ethernet Adapters (if any) as described in the
DOC folder of the unpacked RAR file (DOC/html/starting.htm
towards the end of the page).</li>
</ul></p>
Post-Installation Fixups
The installation program doesn't copy the docs mentioned above from the
unpacked RAR file to the installation folder, but especially the page on
authentication (DOC/html/authentication.htm) should be at hand later on
so I copied the whole DOC folder to C:SAP (I used the default
installation folder). Then I removed the R/O flags and created a shortcut to
C:SAPDOChtmlindex.htm at a convenient place inside my start menu.
</p>
Startup
After successful startup of the NWAS the URL http://localhost:50000 (http://localhost:50000)
brings up the welcome page below. You might be wondering why the icons are no
links to further information. In fact all the documentation is available from
within the NetWeaver Developer Studio. Open it from the start menu and
you'll see a kind of similiar welcome page having the icons work just the way
you expect it.
Operation Tips
The installation program configures the NWAS to provide an optimal first-time
usage experience. But this doesn't necessarily mean that it's optimal for a
machine intended to be used for something different beside running the NWAS :wink:
Obviously it depends on the individual scenario what is considered optimal.
So let's just assume that our goal is to reduce the impact of the installed
but not currently used NWAS while still being able to start using the
accompanying administration tools without additional preparation.
The SAP Management Console (SAPMMC) is the one-stop shopping when it
comes to operating the NWAS. When you drill down the two top-level nodes
you'll see three sibling nodes called <Computer Name>,
<Computer Name> 0 and <Computer Name> 1. The first
one corresponds to the NWAS database engine, the second to the application
server itself and the third one to the so-called Central Services.
</p>
Stop the Database Engine
When selecting the NWAS database engine without prior interaction with the
SAPMMC you'll get the unfriendly error page below making you believe that
something went wrong with the installation, but fortunately this isn't the
case.
Just start the Windows service SAP DB WWW and retry. Now You'll get a
login page. Using the installation password you should see the page below
showing you that the database engine is actually running (aka Online).
This means that the database web admin interface is not running by default
while the database engine itself IS running by default. For our goal it makes
much more sense to have it the other way round. Therefore we set the +SAP DB
WWW+ Windows service to Startup type Automatic and the Windows
service SAPDB: JP1 (which represents the database engine) to the
Startup type Manual.
The later does by no means imply that we now have to start the database
engine manually before starting the application server. Rather when we select
Start on the JP1 node the SAPMMC takes care of having the
database engine started before doing anything else.
The same is by the way true for the two scripts available in the start menu
as Start Application Server and Stop Application Server. The
only thing you have to change here is to keep them generally from dealing with
the database web admin interface:
0.1.
0.2.
C:SAPJP1SYSexe
unstartSystem.cmd: Comment out +net start
sapdbwww+ by prepending rem.0.1.
0.2.
C:SAPJP1SYSexe
unstopSystem.cmd: Comment out +net stop
sapdbwww+ by prepending rem.</li>
</ul>
Please note that the two scripts are formatted with UNIX style line endings so
be sure to use an editor capable of handling those.
</p>
Stop the Starters
To further reduce the impact of the NWAS it's reasonable to have a closer
look at the involved processes. A really great tool for doing so is the
Sysinternals ProcessExplorer (http://www.sysinternals.com/Files/ProcessExplorerNt.zip). It doesn't need to be
installed at all, instead you can run it directly from the opened zip file.
The screenshot below shows how the two Windows services SAPJP1_00 and
SAPJP1_01 map to the corresponding two nodes in the SAPMMC and
processes in the ProcessExplorer. Additionally it shows that the
SAPJP1_01 Windows service starts the processes making up the central
services from the SAPMMC's perspective.
With the application server itself there's even one more indirection as the
process started by the Windows service itself starts child processes doing the
real work. Inside the SAPMMC they show up in the J2EE Process Table.
The SAPMMC manages all those child processes while the two Windows services
have the Startup type Automatic. But fortunately this doesn't have to
be that way. Just close the SAPMMC and then stop the Windows services
SAPJP1_00 and SAPJP1_01. When you now open the SAPMMC again
you'll notice that it takes quite some time to come up. This is the time it
needs to start the two Windows services again. So if you (like me) can live
with that delay once after a reboot you can set safely set the the Startup
type of the two Windows services in question to Manual.
The Start Application Server script available in the start menu
doesn't take care of starting the two Windows services, but you can change
that in C:SAPJP1SYSexe
unstartSystem.cmd by inserting two extra
lines for the central services:
echo.
echo ============== Starting central services instance ...
echo.
net start SAPJP1_01
ping -n 2 127.0.0.1 > NUL
C:SAPJP1SYSexe
unsapcontrol -prot PIPE -nr 01 -host . -function StartWait 60 10
...and two extra lines for the application server:
echo.
echo ============== Starting java instance ...
echo.
net start SAPJP1_00
ping -n 2 127.0.0.1 > NUL
C:SAPJP1SYSexe
unsapcontrol -prot PIPE -nr 00 -host . -function StartWait 180 15
The ping statements are just a workaround for the by default
missing sleep or wait commands. Between two ICMP messages
ping waits for one second so sending two messages makes ping
wait for one second. This timeout is necessary to make sure the Windows
services are really ready to be used.
</p>
Web Admin Interface
The installation program copies the SAP NetWeaver Administrator from
the unpacked RAR file to the installation folder but doesn't deploy it right
away on the NWAS. You can make up for that by running C:SAPJP1JC00j2eeNWAdmininstall.bat.
This script will ask you for a User name and a Password. Enter
Administrator for the former and the password you entered during the
installation for the latter.
After successful deployment the script brings up the Internet Explorer with
the URL http://localhost:50000/nwa (http://localhost:50000/nwa).
Just logon with the same credentials used for deployment and choose the
desired management area and sub-area. The page below in example shows the
Java Class Loader Viewer which is located in the area Problem Management
and the sub-area Infrastructure Management.