In this blog, I installed the java based
Up until now, I have been performing the installations and modifications on my real machine, using VMware’s vCenter Converter to convert it to a virtual one, and then using Sun’s VirtualBox to read/run the VM, which has been very successful with no bad experiences to date.
With this confidence, all actions were performed in a VM. The main reason being, so that I can return to a good starting point, when I duff it up. Bit like playing Quake, and saving before every corner. I know it’s not very dareing, but I really don’t want to start from the beginning… again.
My VirtualBox VM has 128mb Video Memory, and, as i am running this on my mac, I have given it 2 processors and 2.6Gb RAM, guest OS Windows 7 32 bit (I tried rounding to 3Gb, but the VM is unstable above 2.6Gb). It has the Java 6 update to 20. Also installed is the SAP GUI 7.1, that came with the NSP installation.
I know my NSP is working fine, so there is no need for me to test it. Windows is booted up, with the default services running, including the following
The NSP is not started in the Microsoft Management Console (MMC). Only the one NSP node exists in the MMC.
I have “nspadm” & “SAPServiceNSP”, Windows 7, users. Note, my “nspadm” user MUST have a password, else, the MMC cannot start the Windows Services. This also applies installing the NSP.
So after downloading the “SAP NetWeaver CE 7.2 – Server (size on disc 2.044.489.728 bytes)” option, and decompressing, you should end up with a directory called “CE72_SDN-Evaluation”. The other download option, “SAP NetWeaver CE 7.2 – IDE (size on disc 878.383.104 bytes)”, is the Interactive Developer’s Environment (IDE), not an actual system, though it is available for install within the CE2 System download.
I also downloaded, from Sun’s website, the Java Cryptography Extension (JCE) file – “jce_policy-6.zip”, as the CE2 installation asks for it. Do not uncompress it, leave it as a zip file.
The install took 7gb of hard drive space, and 40 minutes to install, with another 40 mins for the initial startup of the CE2 system. Yes, 40 mins to start up the CE2 for the first time. Startups after that take around 15 mins.
I began by opening up the start html page – “C:CE72_SDN-Evaluationstart.htm”, allowing the blocked content IE8 told me to watch out for, and navigating through the help.
I noticed the CE2 System Requirements for RAM, 2-3Gb, wow!. My System Preparation steps were performed during my NSP install, e.g. loopback adaptor, & Java install. Reminder, watch out for the user you intend to use as it must have a password, else the MMC will not be able to start the installing Windows Services.
The CE2 will install and deploy the MAXDB version 7.8. It did not conflict with my my existing MAXDB 7.6, installed with the NSP.
Back to the CE2 help, on the “Installation” page, I clicked the “installer” link
from which it opens up a directory, where I executed the “sapinst.exe” file
My firewall reminded me I need to switch it off, because it gave me 2 alerts. A sapinst.exe and a java one.
I allowed the access, disabled the firewall, and continued to the beginning of the installation process, where I doubled click the “Server” option, when it appeared
and accepted the license.
Update: 25.06.10 Do not change the System ID (SID), as I have (see below), or else, you will not be able to update the trial license. I have tested this with leaving it as CE1, and changing it to CE2. Here is a great wiki, by
, that explains how to install a new license for CE1 or CE2 (so long as the SID is called CE1).
I did not like the default “CE1” SID, so I changed it to “CE2”, as this was, after all, a CE2 installation, plus I may try adding the CE1 later. (Do not change the SID, as I have)
I pointed to my JCE file
entered a master password
got the following pre-requisite message, of which I chose “No”
it just moans about the operating system, and the swap drive space. Always has done.
Then I get the following message about one of my environment variables. Namely the System PATH environment variable.
I left the installation where it is, and did what it said.
Opened up Windows Computer->Properties->Advanced System Settings->Environment Variables…(button)
Scrolled down to the “System variables”, and “Edit…” (button) to edit the “Path” entry
From the “System variables” section, I cut two locations (separated by the semi-colon) “C:sapdbprograms in;C:sapdbprogramspgm;”, and also took the last semi-colon, and pasted it to the beginning of the “User variable for nspadm”, “PATH” entry, “Edit…”. Careful not to delete what is already existing in the user path variables. Again, I pasted at the beginning of the existing entry.
I Ok’d all the way out, and continued back to the CE2 installation, by clicking “OK”, on the CE2 Environment Variable message hanging there, and then “Retry” on the following message displayed.
The installation then continues for about 10 minutes, doing it’s thing
I accepted the Post Installation options
as there is nothing to change in the parameter summary
I clicked “Next”, and off it went
Ended successfully with the following message
I clicked “OK”. The installation window closed. Note, it says “… will take a few minutes…”. (it did, around 40 mins)
The MMC soon opened, with the CE2 System starting for me.
Now, the trick here is to be patient, very patient, and not think that the sytem has failed.
Note: If you are playing around with the MMC for the first time, you may get a message saying “Configuration information has been saved by an older version of the SAP System Manager snapin…”. You can only “OK”. This is normal and fine.
if, after an hour, it has not gone all green, you may have to check the log file. You can do this by expanding the nodes in the MMC, until you get to a Process, e.g.”jstart.EXE”, then right click a process, and select “Developer Trace”. Here is mine, during the install.
If any process turned grey, like this (stops)
you will have to look at the trace to see what occurred. This would be a whole new topic, and a visit to SDN.
Eventually, at 16:53, or thereabouts, the CE2 turned green
Notice the CE2 nodes “pc 1”, and “pc 2”. They relate to my host and instance number. “pc 1” is my CE2 java stack, instance “01”, and “pc 2” is the locking mechanism (enqueue), and messaging service. I don’t know enough to go into any detail here.
The CE2 install did not prompt me for an instance number, and took the next available, so you install may look slightly different.
Likewise with the NSP “pc 0”. I know that is the NSP ABAP stack, instance “00” on my machine.
I HAVE NOT FINISHED. READ ON …
The CE2 installation process adds five extra Windows Services. Four of them are not set to start automatically. To be able to start the CE2 from within the MMC, we we need to configure the Windows Service’s Startup Types from “Manual” to “Automatic”. Why this was not configured in the installation, I don’t know!
Double click the relevant Windows Services to reconfigure the “Startup type”. The four Windows Services are shown below, inside the red box, after I set them to “Automatic”. The others each side, are from the NSP install.
Here is the other Windows Service installed. A new XServer – 7200, along side the NSP XServer.
After re-booting, and starting the CE2 System, 23 mins later, all systems green !
I have re-booted numerous times since, and the 23 mins, seems to be the average time. So do be patient.
I would recommend changing/checking the CE2 database log file setting, so it is in “Overwrite” mode, because when they are full, all problems can arise, and I don’t think it is actually installed as “Overwrite”.
I used the older MAX DB Manager 7.6, installed during my NSP installation, to connect and check the CE2 database. Only because, I have no idea how to with the newer 7.8 version. We must connect to the CE2 database, and put it in Admin mode to make the changes. There is more than one way to do this, but this is the way I did it.
I opened up the MAX DB program, and added the CE2 system
Connect by “Add…” link
I got the following window, without any entries, so I selected the “Add” button
Then I got what is installed on my local system, as above, so I simply left the default selections, and selected “Ok”.
At the Database Manager screen, I selected the CE2 node, and pressed the “Connect” button
I got the following error message, and still do each time I perform various initial activities. It does not stop the CE2 from starting up.
I simply clicked through it, every time it appears, to continue on to what I am doing. It does go away during the session.
Then, at the “Database Manager Connect” Window, the “User Name” is “control”, and I used the master database password entered during the CE2 installation. May as well store the user name and password too.
This puts the CE2 database into OffLine mode
Then I selected menu Instance->Configuration->Log Settings
and at the Log Settings screen, choose the “Overwrite Mode…” (middle option)
At the next screen, put the CE2 database into “Admin” mode. See arrow pointing to a light, which is actually a button.
Give it 20 seconds or so, then when in “Admin” mode
I chose “Next”. The CE2 database Log setting is now in “Overwrite” mode.
At the next screen I pressed the cancel button, as I was not interested in activating a normal backup mode.
CE2 Test</p><p>To really be sure, all was well with the CE2 install, I started it up, as usual with the MMC, and ran the following test.</p><p>To reach the J2EE start page, I entered the following URL into my browser</p><p>http://pc:50100 </p><p>The URL is made up from – http://<hostname>:5<J2EEinstance_number>00)</p><p>It took about 4 minutes to get to the following page, but after, things got better.</p><p>!https://weblogs.sdn.sap.com/weblogs/images/251778832/je22%20start.jpg|height=357|alt=image|width=405|src=https://weblogs.sdn.sap.com/weblogs/images/251778832/je22%20start.jpg|border=0!</p><p>I selected “SAP NetWeaver Administrator”, see above, logged on with “administrator” and password </p><p>!https://weblogs.sdn.sap.com/weblogs/images/251778832/j2eelogon.jpg|height=185|alt=image|width=268|src=https://weblogs.sdn.sap.com/weblogs/images/251778832/j2eelogon.jpg|border=0!</p><p>and</p><p>!https://weblogs.sdn.sap.com/weblogs/images/251778832/j2eeadmin.jpg|height=256|alt=image|width=625|src=https://weblogs.sdn.sap.com/weblogs/images/251778832/j2eeadmin.jpg|border=0!</body>