Skip to Content

This is the fourth of a six-part series covering initial download, server installation, configuration of scripted packages for a fine level of workstation control, and distribution to clients.  We will also cover how to maintain central control of the SAP Logon configuration, and we’ll explore some options that may help ease the administrator’s burden.

As parts of this process are likely already familiar to many of you, I have broken it up into stages.  Please feel free to jump to the sections most relevant for you.  If you are setting up an Installation Server for the first time, however, I recommend you start with SAPGUI Installation Server Part 1 – Getting Started and move sequentially through the steps.

In Parts 1 through 3 we downloaded all our required files, installed our Installation Server, and brought it up-to-date with the latest patches.  Now we’ll setup our first Package that predefines the components to actually be installed on end user workstations, and we’ll set up the first SAPGUI, the administrator’s own.

  1. Getting Started
    1. Includes download of all required files
  2. Initial Installation
  3. Patching
  4. Package Creation (this document)
    1. Includes initial installation of the administrator’s SAPGUI
  5. Scripting
  6. LSH and Distribution

Package Creation

Create Package

If you are continuing on from the previous step (SAPGUI Installation Server Part 3 – Patching), you are already in the Installation Server Administration Tool.  If not, and you are returning at a later date, from your workstation execute:

  • \\server\sapgui\Setup\NwSapSetupAdmin.exe

The purpose of the Package is to bundle the appropriate SAP Frontend components required for your installation into a single choice, making it easy for users to select (or for you to push).  You can have multiple Packages on your Installation Server, and users can install multiple Packages on their workstations, if that is appropriate for them.  Packages can share components.  Packages can also have pre- and post-install scripts associated with them that allow you to control other aspects of the SAPGUI workstation environment, such as which SAP Logon connections will appear for the user to choose.

In this example, we want to distribute a basic set of commonly used SAP Frontend components, so we will call the package Basic.  In the Installation Server Administration Tool (NwSapSetupAdmin), switch to the Packages tab, and click the button New Package.

The Package Creation Wizard starts.

Click Next.  On the next screen, choose the components you require.  In this example, we are choosing:

  • SAP GUI
  • SAP Logon
  • GUI XT
  • SAP Automatic Workstation Update
  • SNC Client Encryption

You might choose alternative components, but at a minimum you should choose SAP GUI and either SAP Logon or SAP Logon Pad (the difference is that SAP Logon allows users to create and edit connection entries, whereas SAP Logon Pad does not — it is read-only.  In our example, we will distribute a predefined set of connection entries that will not be changeable for the user, but we will allow them to create their own additional entries as well, so we are not choosing the read-only SAP Logon Pad).

When you have made your selections, click Next.  On the next screen, enter the name for your Package.

Click Next.  On the next screen, you must give the value to be used in command-line switches for this Package.  By default, it will be the same as your Package name, minus any spaces, and it is usually best to leave it that way.

Click Next, and the Package will be quickly created.

Click Close and you will be returned to the Installation Server Administration Tool main page.  Under the Packages tab you will now see your Package listed, and if you expand it you will see the hierarchy of components.  To the right, under the Package Configuration tab (not ‘Configure Packages’ as mistakenly referenced in the wizard), you’ll see some general information about the Package, including that it’s currently at Version 0.  This is where you will add scripting to the Package later, but first you need another tool on your workstation:  your own SAPGUI.

Install Administrator SAPGUI

Besides defining which components will be installed on client workstations, another benefit of using Packages to distribute SAPGUI is including predefined SAP Logon Connection entries so that users will not need to know how to configure connections to your servers on their own.  Before you can set up those predefined connections, however, you need a tool to define your own connections as a template.  It is possible to manually edit INI and XML files to do this, but it’s much easier to use SAP Logon itself as the configuration editor.  That means you now need to install SAPGUI on your own workstation, and you might as well use the Package you just created to do it.

Close NwSapSetupAdmin, and from the same folder (\\server\sapgui\Setup) execute:

  • NwSapSetup.exe

The SAP Front End Installer opens.

Click Next.  The list of available individual components on your Installation Server appears.

Click the link for Predefined packages.  Now your Package will appear instead, and if you expand it you can verify the components included.

The checkbox for your Package will not be checked by default, so you must click to select it (ensure the checkmark appears in the box).  When you are ready, click Next.

The install will take a few minutes.  Look for the success message when complete.

You now have a working SAPGUI on your computer with the components you defined in your Package.  However, your SAP Logon Connections folder is still empty at this point.  You could manually addthe connections, but don’t do that just yet.  Instead, you are going to start SAP Logon with a special command-line switch that will allow you to create and save connections in a remote configuration file instead of your local file.  This, and writing scripts to configure other clients to use that central configuration file, will be the subject of the next part in the series.

<—>

Continue on to SAPGUI Installation Server Part 5 – Scripting.

To report this post you need to login first.

8 Comments

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

  1. NCCBMSICT NCCBMSICT

    Hi Matt

    As on part 5 – Thanks for this guide.  My question for this part is:   I created a test installation server on my PC and created a couple of packages (together with scripts) whilst waiting for the ‘real’ physical server to be built with server 2012.  Its now ready to go 🙂 .  Can I copy my new existing packages from my ‘PC’ server to the ‘Real’ server?

    Geoff

    (0) 
    1. Matt Fraser Post author

      Geoff,

      Yes, you should be able to just copy it wholesale, as long as your scripts don’t have anything hard-coded to reference the server hostname (and they shouldn’t — there’s a runtime environment variable for that, %SapSrcDir%). The only part that wouldn’t simply copy over is LSH configuration, but that’s easy enough to repeat on the target server, if you use it.

      Cheers,

      Matt

      (0) 
  2. Robin Day

    Matt,

    Is there a way to add the sappdfprint install into a package on the installation server?  I have searched for documentation on this and i’m not having any luck.  From my understanding, sappdfprint is needed to be able to print in the pdf format.  Do you know if this is correct?  We are wanting to roll out the 740 gui to our users and are just missing this function in our package.  Any help or direction to find the help would be greatly appreciated.  By the way, your documentation is fabulous!

    Thank you,

    Robin 🙂

    (0) 
    1. Matt Fraser Post author

      Hi Robin, and thank you for the kind comment!

       

      SAPPDFPRINT appears to be something of a special case. We don’t actually use it in our shop — it’s not required for old-fashioned SAPWIN frontend local printing, and PDF forms will still print if you create a different version of the type G frontend printer in SAP that uses POST2 as the device type. I think SAPPDFPRINT is normally intended to be installed on Windows print servers rather than actual workstations, though from the documentation you can do it that way — apparently in that case it needs to be installed before you install SAPGUI. I have not found any way to add this into a Package on a SAPGUI Installation Server, unfortunately.

       

      Normally, you can import a new product into your Installation Server by extracting it to somewhere local, then using the Import Products button to start the wizard that will do just that. Once it appears in the list of products, you can then select your existing Package, switch to the Package Configuration tab, and click on Change Package Content to start a wizard that will let you add (or remove) products from existing Packages.

       

      Unfortunately, there doesn’t appear to be a way to do this with SAPPDFPRINT. If you need to install this on your workstations, you’ll probably need to devise some sort of install script (perhaps in VBscript) that first installs SAPPDFPRINT, waits for it to complete, and then initiates your normal Package installation of SAPGUI.

       

      Sorry I don’t have a better answer.

       

      Cheers,
      Matt

      (0) 
  3. Robin Day

    Hi Matt,

    True, it may not be the answer I hoped for, but it was an answer and I do appreciate that!  I had a feeling it was not going to be possible.  I actually do have a frontend printer set up like that, I’ll just have to train the users to switch to it when needed.

    Thank you again for your help!

    Robin

    (0) 
  4. CJ van Rooyen

    Good day,

     

    I was able to add the SAPPDFPRINT product to the installation server by referring to the GUI 730 installation guide.

     

    “…

    A single-file installer must be extracted beforehand. Execute the single-file installer on the command line with parameter /extract:dest_dir in order to extract it to directory dest_dir. If the directory does not exist, it will be created. Then choose dest_dir in the product import wizard. …”

     

     

    Then proceed to add the “product”

     

    You’ll see the SAP PDFPRINT package:

     

    Regards,

    CJ

     

     

     

    (1) 
  5. Track Basis

    Hi Matt,

    We need to create a package for SAP GUI 7.40 which includes SAP GUI 7.40 PL08 installation and PL13 patch together.

    Is it possible to create this type of package ? Please suggest.

    Regards,

    Ashraf

     

     

     

    (0) 
    1. Matt Fraser Post author

      Hi Ashraf,

      No, you cannot do that within a single Installation Server. You will need two servers (on two different hosts, or VMs) to achieve that.

      My recommendation is to setup three (or even four) Installation Servers, much as you would have DEV, QAS, and PRD (and Sandbox) SAP systems, and apply patches to them in the same sequence, with progressive testing, as you would support packs to your SAP systems. We use four in my organization. The SBX Installation Server is used only for myself and the other Basis Admin, so we’re the guinea pigs. Once confirmed that a patch or change doesn’t hurt us, I move it onto the DEV Installation Server, which is used by the SAP Support Team (developers and business analysts). From there to QAS, which is used by volunteer power users within our key business units who assist with testing. And then, of course, PRD for the bulk of our users.

      Such a setup also makes it easy to have different saplogon.ini (or the SAPGUI 7.40 successors) configurations for the different groups. For instance, the PRD group gets only the PRD systems in their SAPLogon; the QAS group gets PRD and QAS; the DEV group gets PRD, QAS, and DEV (and SBX, in fact); while the SBX group gets all of the above plus systems only used by Basis, such as SolMan, etc.

      Cheers,
      Matt

      (0) 

Leave a Reply