This was something that I was meaning to do a long time ago – installing my own local SAP Portal, so I can deploy and test my applications whenever I want, without having to go through the NWDI server. I finally had the time and resources to do it, so let me share this experience with you. Even though the steps are pretty comprehensive and straightforward, things might get messy if you fail some requirements or initial preparation tasks. I highly recommend the reading of the installation information in https://websmp201.sap-ag.de/nw04installation. You should also take a deeper look into the Master Guide and the Technical Infrastructure Guide.

Assuming that you have the necessary hardware requirements to install a local SAP Portal, there are also some prerequisites that you must comply to be able to finish it successfully:

• You must have the Developer Workplace source files (typically it will contain a sub-directory named IM_WINDOWS_I386, in case you intend to install it in a Windows based PC as I did);
• You must have all the necessary files for the Netweaver 2004s SR2 Kernel for Windows. You can get these files in http://service.sap.com/swdc. Note that your OSS User must have privileges to be able to download them;
• You also need a full version of the Max DB database 7.6.xx. You can also use SQL Server as your database;
• I recommend that you have a separate copy of the Netweaver Developer Studio (NWDS) on the same stack level on which you intend to upgrade your Developer Workplace and the ESS/MSS Business Packages (in case you install them);
• You must install the Java Software Development Kit 1.4.2_xx (I installed 1.4.2_09). After installing, do not forget to disable automatic updates right upon installation. There are known issues with versions 1.5.x.
• A local instance ID must be obtained from your basis team. For this purpose, the instance ID referenced in this post is N21.

Installing the Netweaver Developer Workplace

1. Start by installing the Java Software Development Kit 1.4.2_xx (I installed 1.4.2_09). Typically, Java will be installed in a new directory called, e.g., c:\j2sdk1.4.2_09;

2. Create a new system variable called JAVA_HOME and set it’s value as c:\j2sdk1.4.2_09\bin;

3. You should create a new administrator user for your local PC, called [Instance Number]adm. In this case, N21ADM;

4. I had some issues with the anti-virus, so I disabled it during the installation;

5. If you use a VPN to connect to your ERP backend system, be sure to connect to it so that you have a valid IP address during the process;

6. Run file sapinst.exe, which should be located in the developer workplace installation directory – ..\IM_WINDOWS_I386;

7. Follow the steps described on the following screenshots:

8. You must specify a Police Archive, which can be downloaded from the locations below

9. Specify the instance ID and the installation drive

10. Define a master password. This will be the portal user “Administrator” password, as well as the Visual Administrator password

11. Define a password for the windows account users. This will be the windows user “[InstanceID]adm” password

12. Define the Database parameters. In this case, it’s the same ID as defined for the Instance ID (N21)

13. Enter the locations of the necessary software packages. First the RDMS MaxDB

14. Next the UC Kernel, for the Netweaver 2004s SR2

15. For the time being, select “No SLD destination”. The SLD configuration will be done later.

16. Select the location for the Netweaver Developer Studio (NWDS) installation

17. Hit Start

18. If no errors occur, hopefully your installation will end with lots of green checks and a message of success confirming it. you can now check if your local Portal is working.

19. To test your local Portal, first you must start the J2EE engine. You should have the SAP Management Console (MMC) icon on your desktop

20. Start your instance and verify that all processes are running – all green

21. Access the Portal on http://localhost:50000/irj/portal

22. Logon using user “Administrator” and the same password you’ve defined in step 10. You should be able to login and view the Portal running.

So I have my local SAP Portal running! What’s next?

Right now you have an almost standalone local SAP Portal. In order to use it properly, you still have several configurations to perform. Here are some of the most important

1. Get your license key

2. Configure the System Landscape Directory (SLD)

3. Configure the Single Sign-On

4. Create the necessary Java Connectors (JCO)

5. Deploy any existing custom applications (Web Dynpro)

6. Install the ESS and MSS Business Packages

After you performed these steps, you will be able to run ESS and MSS applications on your local Portal, provided that the user credentials are valid and that you’re connected to the backend system when you run it.