- Windows 2000 Server English, SP4
- 1.5 GB RAM
- 1 GHz Pentium mobile
and it took about 2 days (there are still time assumptions of between 4 to 8 hours, for example in the SP6-Preview-Installation-How-to. But I think this is not possible, even for experienced users).
At the end we’ll have a standalone Enterprise Portal 6.0SP7 on MSSQL-DB with[/b] Collaboration & Content Management. Using KMC (is this the proper abbreviation for Collaboration & Content Management? At least, it was) is an important decision, since it complicates the installation process.
Since the installation order is described in detail in the delievered installation guide, I’ll just give some quick hints and what happened during intstallation.
Preparing the Installation
You can find details in the installation guide. So, just some quick points:
- Installation of MSSQL 2000 Server
- Installation of Patch3a for MSSQL2000
Installation of Hotfix 919 (download)
Installation of collation-patch (download) from note 600027
Installation of J2SDK1.4.2_05 (download )
- Setting the JAVA_HOME environment variable
Grant authorizations for the user doing the installation in Local Security Settings</li>
Installation of SAP Web Application Server
I’ve copied the Master-Installation CD (CD51030196) & WAS640-DVD (D51030277) (at least directories J2EE1 & IGS) temporary to the hard drive.
Additionally extract the 4 SAR-files from Stack05 (CTRLMSS08_0, J2EERT08_0, J2EERTOS08_0, SAPINST08_0) to an extra directory.
If you decide not to use KMC you just have to install EPSP3 and upgrade it to EP60SP7 in two steps. Otherwise, follow the instructions provided below:
Installation of SAP Enterprise Portal
I’ve copied the EP1 & KMC1 directories from D51030276 to the harddrive
- Install EP60SP3 (run sapinst.exe from \EP1\SAPINST\NT\I386)
- Choose “Portal Platform”
After installation I was not able to log on to the portal. There was just a blank page indicating “Loading portal…”.
In the Log-/Trace-files there were entries regarding acl-issues. I suppose the cause was the (new) WASSP8. So, I decided to upgrade to EP60SP6 immediately:
- Extract 4 SARs (EP6CTL06_0, EP6PORTAL06_0, EP6TOOLS06_0, SAPINST06_0) from Stack04
- Upgrade to EP60SP6 (run \SAPINST-CD\SAPINST\NT from the directory used above
After that, I was able to log on as Administrator with the password I defined during installation.
Installation of SAP Collaboration & Content Management
- Install KMCSP4 (run sapinst.exe from \KMC1\SAPINST\NT\I386)
- Choose “Content Management and Collaboration”
After that, you’ll get new entries in the navigation menues in the portal, but you’ll receive error-messages, because KMCSP4 doesn’t fit to the earlier installed EP60SP6.
So, we have to
- Extract 4 SARs from Stack04 (EP6CTRL06_0, EP6KMC06_0, EP6TOOLS06_0, SAPINST06_0)
- Upgrade to KMCSP6 (run sapinst.exe from \SAPINST-CD\SAPINST\NT\ from the directory used above
At the end, you’ll receive an error that com.sap.workflow.logging.ear couldn’t be deployed. that’s OK
- Delete logging-files & logging.properties according to the Stack04-Upgrade-Guide
- Deploy Patch2 for KMCSP6 (extract the SAR and replace com.sap.workflow.portal.sda with the one from note 763825
- Deploy all the files with SDM
- Restart server
- Correct the collaboration.version.txt
Upgrading EP & KMC to SP7
I’ve upgraded EP and KMC to SP7 consecutively, but I suppose it could be also possible to extract the files from Stack05 in the same directory-structure and then run sapinst.exe, since they use the same sapinst-sar and put the used patch-files in different directories (KMC and PORTAL).
- Extract 4 EP60SP7-SARs (EP6CTRL07_0, EP6PORTAL07_0, EP6TOOLS07_0, SAPINST07_0) from Stack05
- upgrade to EP60SP7 (run sapinst.exe from \SAPINST-CD\SAPINST\NT\I386 from the directory used above)
At this point, I ran into a deployment error, saying my server wasn’t available during deployment. Because I received this message also in an upgrade in a grown installtion and now again in a fresh installation, I guess it’s a known problem (…;-). I suppose it could be a memory problem?
But after stopping / restarting sapinst with the option “Continue”, the upgrade finished successfully.
- Extract the 4 KMCSP7-SARs (EP6CTL07_0, EP6KMC07_0, EP6TOOLS07_0, SAPINST07_0) from Stack05
- Upgrade to KMCSP7 (run sapinst.exe from \SAPINST-CD\SAPINST\NT\I386 from the directory used above)
Now, we’ve finished the installation, though there are some errors left:
- The Logging Console in System Administration / Monitoring / Portal / Logging Console raises exceptions in com.sap.portal.runtime.admin.logadmin.default. This error occured at two different installations of mine since EP60SP6. Note 741847 says, Logging in the portal is no more supported… and we should use the standalone log-viewer ;-(
- Different errors in config.trc and defaultTrace.trc. But I think, that’s pretty normal. We won’t get these files error-free… 😉
Now, before you go on with:
- creating super_user
- installing license
- initial configuration
- create your own themes
- content creation
you should do a full backup of your installtion.
As I mentioned already above, it took me nearly 2 days to do the whole installation, so don’t be frustrated if you need more than the proposed 4-8 hours… 😉
By the way, note 739788 (Template Configuratiopn Tool) isn’t released yet.
Furthermore, I’m wondering why SAP doesn’t deliver full installation-versions of all stack-releases, so you don’t have to do this upgrade-story. Isn’t it possible to put all current versions of deployable objects (.sda, .ear, etc.) in one installation version?