Skip to Content

For my demos, I prefer to have everything running locally on my machine. You never know what might happen on-site. Having no connectivity is more common than one might think. 🙂

Although I’m quite experienced with SAP NetWeaver Gateway, I’ve never set up my own instance. So why not combine necessity with fun and get my own local instance up and running? My host machine is, by the way, a Mac Book Air with Mac OS X 10.7.4 and VMWare Fusion 4.1.1, so I assume something might surely be different.

So, let’s see what I did to get my local SAP NetWeaver Gateway instance up and running: I installed the 90-day trial version (I went for the preconfigured trial version for Linux SAP NetWeaver Gateway 2.0 SP4), by following the instructions given here. However, there were some minor issues; Mac-related ones … but overall not a big deal. 😉

Fun aside, to get it running, follow the instructions provided: Download SLES11 VM and the Gateway ISO-File, and pay special attention to the README file mentioned in step “3. Install SAP NetWeaver Gateway”. Don’t just press ( i ) -> “3. Continue installation by typing i. (See diagram below)”. Instead, first press ( R ) to read the README file.  You’ll learn more about the host configuration, especially your host file. I didn’t read the README the first time and failed to get the message server up and running… and as a consequence SAP NetWeaver Gateway.

So, what did I do differently?

I adjusted step “2. SAP NetWeaver Gateway on VMWare” slightly. Under “VMWare Fusion -> Configuring the Network Connection”, I selected “Host-only” to have as little pain as possible. When using the standard configuration, I had a problem with the network detection. Setting up a private virtual network fixed this issue for me.

/wp-content/uploads/2012/11/network_adaptor_158165.png

Next, I added an extra step and installed the VMware tools. I find them quite helpful since they make things easier, i.e. you can drag and drop files, and you can use the clipboard. For more background on how to install them, continue reading here. Note that you have to switch to the root user for the installation: the password is “saptestdrive”. If you have more questions on how to install the VMware tools, just post a comment and I’ll explain the necessary steps in more detail.

Besides step 2, I also had to modify step “3. Install SAP NetWeaver Gateway” slightly. First, press ( R ) to read the README file. As mentioned above, you’ll learn more on how to set up your host system, and especially the network configuration. It’s highly recommended using a static IP-address. So let’s do it:

  1. Get the IP address:
    1. Open the terminal.
    2. Execute “su -“.
    3. Enter password “saptestdrive”.
    4. Execute “ifconfig”.
    5. Copy your ip address (i.e., 196.168.x.x).
      /wp-content/uploads/2012/11/ifconfig_158166.png
  2. Next, edit /etc/hosts: Execute in the same terminal “gedit /etc/hosts”.
  3. Update the host file according to the README file (see “prerequisites”).

Now we can go back to the proposed procedure: restart the installation and press ( i ), as suggested. Since the described command-line approach didn’t work for me, I installed SAP GUI for Java on my Mac. You can download it from the service marketplace. If you’ve problems, e.g. no access, please let me know and I’ll do my best to help you.

Have in mind that SAP GUI for Java looks a little bit different than the screenshots in the how-to document, but you can perform all the necessary steps as well; i.e. instead of the buttons, you must use the menu. Next, let’s configure SAP GUI for Java: create a new connection and go to the advanced tab. Selected “Expert Mode” and add the following string: “conn=/H/<IP-ADDRESS>/S/3242″. We got the <IP-ADDRESS> from executing “ifconfig” (see step above).

/wp-content/uploads/2012/11/sapgui_158167.png

Next, we have to do some guessing. This issue should be fixed soon. In the process of generating a license for your trial system, the how-to doc proposes to choose the following as the system id: “NPL – SAP NetWeaver 7.02 (MaxDB)”. Unfortunately for me, there are three options called “NPL –”, all without any further information. The second “NPL –” entry in the list worked for me (so I chose it) and I got a *ADA license (generating a license file for all three options and the screen-shot posted here gave me the final hint 😉 ).

That’s it! If you perform all the steps mentioned in the how-to doc, along with my small modifications, you should have now a local SAP NetWeaver Gateway instance up and running on your Mac. So let’s test it:

As a reminder:

System 001
Username DEVELOPER
Password ch4ngeme

On the image, call in the browser:

From your host machine (you must deactivate your proxy if you’ve set one), call in the browser:

To report this post you need to login first.

2 Comments

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

  1. Matthias Steiner

    Great tutorial! I actually did the exercise myself a couple of weeks back and I have to say you did a great job on describing all the steps and pitfalls that may come up!

    BTW, if you want to set the network connection to bridge mode that’s also possible. At least it worked for me, after I deleted the default (eth0) network connection on SLES and manually re-creating it (using DHCP.)

    So, folks… what are you waiting for… give it a try! 😉

    (0) 

Leave a Reply