Skip to Content
First, the hard facts. I was doing the installation on

    • 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.


I’ve used the NW_SP_STACK04_104.pdf and NW_SP_STACK05_100.pdf available at http://service.sap.com/instguidesnw04
and the downloaded files from http://service.sap.com/patches for Stack04 and Stack05.


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.


Let’s start:

Preparing the Installation


You can find details in the installation guide. So, just some quick points:

    1. Installation of MSSQL 2000 Server
    2. 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 )

    1. Setting the JAVA_HOME environment variable

Grant authorizations for the user doing the installation in Local Security Settings</li>
</ul>


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

    1. Install EP60SP3 (run sapinst.exe from \EP1\SAPINST\NT\I386)
    2. Choose “Portal Platform”

I’ve used strong cryptography, therefore I needed jce_policy-1_4_2.zip (download ) and tc_sec_java_crypto_signed_fs_lib.sda (download)

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:

    1. Extract 4 SARs (EP6CTL06_0, EP6PORTAL06_0, EP6TOOLS06_0, SAPINST06_0) from Stack04
    2. 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


    1. Install KMCSP4 (run sapinst.exe from \KMC1\SAPINST\NT\I386)
    2. 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

    1. Extract 4 SARs from Stack04 (EP6CTRL06_0, EP6KMC06_0, EP6TOOLS06_0, SAPINST06_0)
    2. 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

    1. Delete logging-files & logging.properties according to the Stack04-Upgrade-Guide
    2. Deploy Patch2 for KMCSP6 (extract the SAR and replace com.sap.workflow.portal.sda with the one from note 763825
    3. Deploy all the files with SDM
    4. Restart server
    5. 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).

    1. Extract 4 EP60SP7-SARs (EP6CTRL07_0, EP6PORTAL07_0, EP6TOOLS07_0, SAPINST07_0) from Stack05
    2. 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.

    1. Extract the 4 KMCSP7-SARs (EP6CTL07_0, EP6KMC07_0, EP6TOOLS07_0, SAPINST07_0) from Stack05
    2. 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:

    1. 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 ;-(
    2. 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:

    1. creating super_user
    2. installing license
    3. initial configuration
    4. create your own themes
    5. content creation
    6. etc…


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?

To report this post you need to login first.

8 Comments

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

  1. Gregor Wolf
    Hello Achim,

    great description of the installation process. We also had the same problems. Have you read my Weblog about Install SAP EP 6.0 on Web AS 6.40 https://weblogs.sdn.sap.com/pub/wlg/862? [original link is broken] [original link is broken] We did install directly upgraded the Web AS and the portal to the latest avaliable Support Package Stack. What I’ve learned from the TechEd Administrator Session is that you must first update your Web AS and then the Portal.

    We also had a problem with KM. Here you have to install also the latest Patch.

    But now to my main toppic: Use Rapid Installer. At Teched I get the information that Rapid Installer is general avaliable for EP 6.0 on Web AS 6.40 and for the CRM Server installation. You have to contact your SAP Sales representative to order it.

    Regards
    Gregor

    (0) 
    1. Former Member Post author
      Hi Gregor,

      thanks. what do you mean with “directly upgraded”? does it mean, you directly upgraded from EP60SP3 (CD-version) to EP60SP7 (without the KM-Patch-at-SP6-step?). Notes / Guides tell, that it’s important to include the patch at this time. But I’m wondering, why this should be so important and why the patch isn’t included in later patch-releases, too.

      I’ve never heard of Rapid Installer, yet. What kind of product/wizard is it? A one-click-installation-tool? I’ll do some search at SAPs homepages…

      kr, achim

      (0) 
      1. Former Member
        The initial install will take much time(2-4 days).If you do couple of installs, you can do all 2-4 hrs.
        Reg rapid installer , we can do installs in an hour with it as per the article :>).I did not try yet….. but any way, having fun with new tools,technologies 🙂

        thanks for your information to all.

        (0) 
      2. Gregor Wolf
        Hi Achim,

        yes we did upgrad directly from EP60SP3 to EP60SP7. But thank’s for the tip that there can by problems. But we havn’t used KM mutch till now.

        Rapid Installer: As I said you have to contact youre SAP Sales Representative to order it.

        Regards
        Gregor

        (0) 
  2. Former Member
    Hi,

    In the installation of the portal, why did you upgrade first to SP6 and then SP7?  Is this a required step or could you have upgraded directly to SP7?  I am not installing KMC, is this a factor?

    I’m also wondering how this will change with Stack 9.  Will we be able to go directly from SP3 to SP9?

    Thanks,

    Andrew

    (0) 
    1. Former Member Post author
      Hi Andrew,

      you only have to do the SP6 step, if you’re using KMC, because at this SP-Level you have to implement a patch for KMC.
      I don’t know if it’s required or just a recommendation of SAP. I haven’t tried to go directly to SP7 with KMC.

      Anyway, if you don’t want to use KMC, you can upgrade direct to SP7. (But what would happen if you decide afterwards to install KMC…?)

      I hope, there will be a full installation source for stack 09.

      kind regards, achim

      (0) 
      1. Former Member
        Achim,
        Thanks for your guide. It guided me to a successful install of EP60(SP6) and now on WAS (SP7). Clarification – are you saying that if we upgrade EP to SP07, we cannot install KMC?, which means to say that KMC can only be installed once the portal is on EP(SP06)?

        Regards,
        James

        (0) 
  3. Former Member
    SP9 will come as a one-shot installation. One WebAS, one Portal, one KMC. It also uses an improved installer based partly on OpenSQL and lowers the use of SDM during installation (which lowers potential problems).

    One note regarding the Rapid Installer – currently this is a tool for EP6 SP2 systems and is built around a different paradigm for the J2EE. I suppose there will be something similar for SP9, but it will likely be very different under the hood as the fundamental architecture has changed significantly.

    (0) 

Leave a Reply