Introduction

This document describes how to set up and maintain an SAP GUI Installation Server for the efficient distribution of SAP Front end Components across workstations in your organization.

Overview

SAP’s Front-End Software Deployment Tool – Netweaver SAPSetup not only allows direct installations from distribution media, but also an Installation Server based deployment mechanism that helps distribute SAP Front-End Software to workstations over a network and also using Microsoft SCCM  to deploy the large number of users.

General Features of SAP GUI Installation Server:

Fully-featured installation, uninstallation, update, repair, and patch functions for SAP front end components:

• Front end components are available from an installation server or a distribution medium such as a DVD.
• Install new SAP front end components, uninstall existing ones, and update the remaining components in one cycle.

Easier and more reliable handling of SAP front end components by using installation servers:

• Maintain nearly all Windows-based SAP front end components on a single installation server.
• Integrate additional SAP front end components into an existing installation server, such as Import Product.
• Deploy multiple SAP front end components on workstations using a single command.
• Easily manage the installation server with wizard-driven user interfaces.
• Local Security Handling (LSH), when configured, lets you deploy SAP front end components on workstations without requiring administrator privileges on all machines.
• Whenever installed SAP front end components or packages change on the installation server, the automatic workstation update service (AWUS) will, once configured, automatically update the workstations and reboot them if necessary.
• Easier handling of multiple SAP front end components by configuration of installation packages – by implementing script events, you can customize and extend the installation of such packages.
• Controlling workstations remotely helps you to remotely access and control workstations on which you have administrator privileges. You can collect remote log files, execute processes remotely, and list remote processes.
• The directory for the creation of the installation server is configured automatically. By default, it is made NULL-session accessible. It can be shared automatically on the network for everyone to read.
• If NwSapSetup.exe is started from a batch file, the return code can be caught by the environment variable %ErrorLevel%.

Important Notes for the SAP GUI

It is important that you read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information about the installation, as well as corrections to the installation documentation.

0000026417_SAP GUI Resources Hardware and software

0000038119_SAP Logon Administration of functions

0000066971_Supported SAP GUI platforms

0000147519_Maintenance strategy deadlines for SAP GUI

0000166130_SAP front end Delivery and compatibility

0000328723_GUI default settings during installation

0000508649_Diagnosis of frontend installation problems

0000535308_How to apply a SAP Front End patch

0001053737_Expected release dates for SAP GUI for Windows & ITS Patches

0001085218_NetWeaver 7.x BW Frontend Patch Delivery Schedule

0001144671_New SAP Installer for SAPGUI for Windows 7.10

0001169612_Cannot start NWSAPSetupAdmin over a network path

0001397000_SAP GUI for Windows Security Execution of SAP Shortcuts

0001414580_Jaws & SAP GUI configuration

0001426178_SAP Logon (Pad) create and distribute server configuration file

0001442028_SAP GUI for Windows No support for Office 2010 64bit

0001583967_Release Information Note for SAPSetup 9.0

0001587566_Installation problems with SAPSetup Version 9.0

0001588323_SAP GUI for HTML cannot be started (NW Basis 7.30)

0001652770_BI 7.x in 730 DVD1-BI client tools - contents & versions

0001669254_SAP GUI 7.30_Branding image in title bar

0001670678_730_New Features

0001685221_SAP Logon maintain system entry without sapmsg.ini and service file

0001702037_BW 7.x Frontend in GUI 730 - First Customer Shipment

0001710864_SAP Logon 7.30_possibility to disable views via registry

0001726742_SAPBWNews NW 7.x BW Add-On Frontend Patch 300 - GUI 7.30

0001796138_SAPBWNews NW 7.x BW Add-On Frontend Patch 201 - GUI 7.30

0001797599_RRMX for BEx Analyzer 3X is not supported with SAP GUI 730

SAP GUI Software Download

http://scn.sap.com/community/gui/blog/2013/05/29/sap-gui-730-download

Hardware and Software Requirements

Make sure in advance that your system meets the following requirements:

• The host for server-based installations must meet the following conditions:
  • Accessible to all users at all times, even after the installation is complete. This is required for maintenance purposes such as the distribution of patches.
  • Have broadband network connection for high throughput
  • Have sufficiently free disk space for all SAP front end components
  • Use a Windows server as operating system

Note:  Read SAP Note 26417 to check that all hardware and software requirements for the front-end workstations have been met.

How to Setup an Installation Server

The installation process from an installation server is flexible, easy, and customizable. It makes maintenance easier in any phase of the distribution process, for example, when applying patches.

When installing SAP front end components with server-based workstation installation, the following options are available:

• Without user interaction (unattended)
• With user interaction (attended), where the user has the following options:
  • Select from installation packages that the administrator has configured
  • Select from a complete list of SAP front end components available on the installation server

The following figure shows how the installation with an installation server works.

With an installation server, the administrator can group various SAP front end components together as installation packages relevant for certain employee roles. The administrator can also specify which package particular users should receive, or offer a variety of packages and allow the user to choose the most appropriate one.

To keep workstations up to date automatically, use the automatic workstation update service (AWUS). Whenever the installation server is patched, or packages are updated on the installation server, this service will update the workstation(s) and reboot them, if necessary. The AWUS works regardless of whether a user is logged on or not:

Creating an Installation Server

NWCreateInstServer is a wizard-driven tool that helps the administrator to create a new installation server. After the server is set up, NwUpdateInstServer imports SAP front end components from the source into the newly created installation server.

Start NwCreateInstServer.exe from the Setup directory.

Choose Next to continue.

NwCreateInstServer.exe prompts you to supply the path to the directory in which you want to create the installation server.

Choose Browse to navigate to the directory in which you want to create the installation server. Ensure that the directory is empty.

Choose Verify to ensure that the chosen directory meets the prerequisites:

Choose Share to maintain the file-sharing properties of the selected directory for distributing using logon scripts and automatic workstation update service

Choose Next to continue.

Processing is recorded in the file NwCreateInstServer.log located in the SAPSetup log file directory.

The wizard confirms the successful installation of the installation server.

You now have a valid but empty SAPSetup installation server.

If you want to set up an empty installation server, you can skip the update by calling NwCreateInstServer.exe with the parameter /NoServerUpdate on the command line. In this case, the procedure ends here.

To update the installation server, reboot the Installation Server and execute NwUpdateInstServer.exe to transfer SAP front end components to your installation server.

Navigate to the Installation Server folder and Click verify to start the Update

The wizard displays the progress of the installation server update.

NwUpdateInstServer.exe transfers all SAP front end components available in the downloaded objects to the installation server.

If you have .NET Framework version 4 installed, choosing Finish Automatically starts NwSapSetupAdmin.exe from the recently updated installation server.

Administering an Installation Server

After you have successfully set up the installation server, you can find admin tools in the SETUP directory of the installation server.

• NWCreateInstServer: Installation Server Creation Wizard Driven Tool that helps in creating a basic Installation Server and configures.NET Security to administer it over a network path.
• NWUpdateInstServer: Installation Server Update Wizard Driven Tool is used to update an Installation Server with SAP Front-End Components. This utility will also automatically update older versions existing on an Installation Server by newer ones.
• NWSAPSetupAdmin: Installation Server Administration Wizard Driven Tool that helps in maintaining and configuring an Installation Server, creating packages, importing products, apply patches etc.  Administrators can create a Package Definition File to deploy the package using like Microsoft SCCM.
• NWSAPSetup: Front-End Installation Tool is used to install SAP Front-End Components available on the Installation Server on a Workstation, to update an installation or to perform un-installations.  Administrator can install manually or using command lines to perform the installation silently and unattended deployments
• NWCheckWorkstation: This utility is used to diagnose the health of the Workstation containing installed SAP front-end components. It creates a CAB-file with the error information. If required, you supply the logs to the SAP Primary Support.
• NWSAPSetupDS: This tool allows you to configure (Local Security Handling) that helps administrators to allow domain users with non-administrative privileges to install software locally on their workstations.

Import Product: Use this feature to add new products (for example, SAP front-end components) to an existing installation server for distribution over the network.

Export Product: Use this feature to export front-end components available on one installation server to another.

Delete Product: Use this feature to delete a product from an installation server.

Create Package: Use this feature to create packages for deployment. Packages can contain many components and their installation parameters can also be customized.

Create Package Definition File (PDF): You can create a package definition file (PDF) for an installation server package. PDF is a package description format that simplifies the interoperability and information exchange between the SAP Installer and system management products like the System Management Server from Microsoft.

Configure Package: Use this feature to change the attributes or the content of your packages.

Patch: Use this feature to patch components that are available on the installation server.

Local Security Handling: This feature allows workstation users to install SAP components from the installation server without requiring administrative privileges.

Automatic Workstation Update: Whenever the installation server is patched, or the packages installed are updated, this service will update the workstation and reboot them if necessary.  The workstation updater works in two modes - one in the presence of a logged-on user and another in his or her absence:

When a user is logged on, the user is informed of update availability and the update happens on the user's assent. The user is also informed if a reboot is necessary and the reboot is also only executed on the user's assent.

If no user is logged on, the update is done automatically and the reboot (if necessary) is done automatically, too.

Control Remote Workstations: This functionality uses the Windows Management Instrumentation (WMI) to help you remotely access and control workstations on which you have administration privileges. You access this feature via the Remote menu, where you find the options to:

Collect remote log files

Execute processes remotely

Enumerate remote processes

You find detailed information in section Controlling Remote Workstations.

Adding New SAP Front End Components to an Existing Installation Server

Click on Import Products

Click Next and follow the wizard instructions

Navigate to the product download location and select the “Setup” Folder

Product import completed

Updating Products on the Installation Server with a Newer Version

Start “NwUpdateInstServer” from the setup directory and follow the wizard instructions

Navigate to the Installation Server folder you want to update and “Verify” the Installation

Click Next to continue the installation

Check the logs for information if the Installation Server update fails for any reason.

Installation Server has been updated successfully

Deleting Products from the Installation Server

Right click on the product and choose “Delete product….” to delete the product.

Click Next to continue product deletion

Choose Close to finish the product deletion.

Creating a New Installation Package

Navigate to the Packages tab and Click on “New Package” to create a new Package.

Configuring Packages and Event Scripts

Switch to the Packages tab page. In the left window pane, you can see a tree listing the existing packages.

The (X) cross indicator next to a package indicates that the package is incomplete. This typically occurs when a product that the package contains has been deleted from the installation server. You can either delete this package or re-import the missing product.

Select the package that you want to customize and navigate to “Package Configuration”

• Verify the Package Parameters (Variable Name, Package Value and Variable Description)

Add event-scripting to perform custom actions on the user’s workstation during the installation of the package (for example, copying additional files). You can insert scripting samples delivered by SAP via Insert Script and adapt them to your requirements. The scripts are executed at the following events:

• On Begin Install: executed before the installation of a selected package
• On End Install: executed after the completion of package installation
• On Begin Uninstall: executed before the uninstallation of a selected package
• On End Uninstall: executed after the completion of package uninstallation
• On Begin Update: Executed before the update of a selected Package.
• On End Update: Executed after the completion of the Package update.

Example:  If you want to check a file for existence on the workstation, navigate to “On Installation End” tab and insert a script sample and modify according to your requirements.

Changing the Package Content

• Switch to the Packagestab. In the left window pane, you can see a tree listing the existing packages.
• Select the package for which you want to update the content, and choose Change Package Content.

You can now select or deselect components. Components added will be newly installed on the workstations. Those removed will be uninstalled from the workstations, if they are not part of any other package marked for installation. When updating a package, the package installation parameters are also refreshed and include new variables or delete those that belong to components that are no longer part of this package.

Follow on screen instructions and Save the package when you are finished.

Deleting an Installation Package

• Navigate to Packagesview.
• Right-click the package you want to delete.
• From the context menu, choose Delete Package.
• The package is deleted. It is removed from the Packages view.

Creating and Deploying a Single-File Installer for Packages

You can create single-file self-installing .exe-packages via NWSAPSetupAdmin.exe.

Such a package contains only those files that belong to the components that are a part of the package. Thus, it reduces your network load in certain distribution scenarios where you previously had to make local copies of your installation source before installing.

This single-file self-installer can also install silently without user interaction.

Creating a Self-Installing Package

In the Packages tree, right-click the package you want to create a self-installing file from, and choose Compress To Single-File Installer

Following the wizard instructions, you will get a single exe-self-extractor at the end of the process.

Deploying a Self-Installing Package

• The self-installing file created above can be executed on any workstation to install your package.
• Follow the installation wizard.
• This self-installing package can be installed silently (i.e. without user-interaction) when invoked with the command-line parameter /silent.
• This self-installing package can be installed with no dialog (i.e. user can see the installation progress) when invoked with the command-line parameter /nodlg.

Creating a Package Definition File (PDF)

You can create a package definition file (PDF) for an installation server package. PDF is a package description format that simplifies the interoperability and information exchange between the SAP Installer and system management products like the System Management Server from Microsoft.

On the Packages tab, right-click the package for which you want to create a PDF file and choose Create Package Definition File.

Choose the directory where you want to save the file, enter a file name, and choose Save.

Patching the Installation Server

Patching products on the installation server keeps them up-to-date with the most recent correction and enhancements from SAP.

Choose Patch Server.

Choose Next to continue.

Browse to a valid SAP patch file and choose Next to continue.

NWSAPSetupAdmin.exe now validates the patch, which takes a few minutes.

If the patch is valid, you are prompted to proceed with it.

To ensure that the installation server is not in use, the patch now closes NWSAPSetupAdmin.exe before continuing. It restarts NWSAPSetupAdmin.exe after completing the patch.

Choose Next to continue.

NWUpdateInstServer.exe starts patching the installation server.

Follow the patch wizard, choosing Next as required.

At the end of the process, you see a message indicating that the patch was successful.

Choose Close.

NWSAPSetupAdmin.exe now restarts.

Check Update Log Files:

%ProgramFiles%\SAP\SapSetup\Logs\NWUpdateInstServer.log.

If there are errors, you see a link to an Error Report. Any errors are recorded in the following file, which you can view using your normal web browser:

%ProgramFiles%\SAP\SapSetup\Errors\ NWUpdateInstServerErrors_<CurrentDateTime>.xml.

If you have a problem, create a problem message on component BC-FES-INS and attach these files to the message.

Configuring the Local Security Handling (LSH)

Local security handling (LSH) lets users on the network deploy SAP front-end components on their front ends using NetWeaver SAPSetup without requiring administrative privileges on each workstation.

Choose Services and select Configure local security handling.

The LSH configuration wizard starts.

Choose Next.

The wizard prompts you for the credentials of an account that has administrative privileges for all front ends on the network.

Enter the account name with domain qualifiers.

Choose Verify and Next

The wizard will be prompted to enter details for the installation service (IS) account, Verify, and choose Next to complete the process.

The wizard displays the success state in starting the distribution service and the status bar at the bottom of NWSAPSetupAdmin.exe displays the service state as Active.

Test the functioning of the LSH feature by starting NWSAPSetup.exe from this installation server on a front end where the logged-on user has ordinary user privileges (that is, the user does not have administrative privileges).

If the front-end installer starts successfully and is able to install components available on the installation server, the configuration is successful. If not, you need to reconfigure LSH.

LSH Related Notes

Note 1288344 - NwSapSetupAdmin: Could not store IS user data

Note 593486 - Installing the DS installation service (analysis notes)

Local Security Handling broken on patch level 6

7.xx Installing the DS installation service (analysis notes)

Note 1587566 - Installation problems with SapSetup Version 9.0

Configuring the Automatic Workstation Update Service (AWUS)

The SAP Automatic Workstation Update works only when installed on the workstation. Whenever the installation server is patched, or the packages installed are updated, this service will update the workstation(s) and reboot them if necessary. The workstation updater works in two modes - one in the presence of a logged-on user and another in his or her absence:

• When a user is logged on, the user is informed of update availability and the update happens on the user's assent. The user is also informed if a reboot is necessary and the reboot is also only executed on the user's assent.
• If no user is logged on, the update is done automatically and the reboot (if necessary) is done automatically, too.

Note: This service updates itself, when a patch of automatic workstation update is available.

Choose Services -> Configure automatic update.

The screen Automatic Workstation Update Configurations appears as shown in the following picture:

You have now several options:

• Update check frequency
  • The workstations that will have this feature installed, will poll the installation server at this interval to check for update availability. The default is 24 hours and the Maximum can be 744 hours.
• Enforce reboot after every update
  • When this flag is not set, the user is asked to reboot only if it is required to complete the deployment process. When the flag is set, a reboot is enforced, which means that the user is always asked to reboot.
• Additional Update Sources (optional)
  • You can index additional servers. The update service will then look up the indexed servers per line in the given order for available updates.

Save your entries and close the program.

To make the automatic workstation update service available on workstations, you should create a package using NWSapSetupAdmin.exe on the installation server. This package should consist of SAP GUI for Windows and SAP Automatic Workstation Update. Once automatic workstation update is installed, then the following programs will run on the workstation in the background: NWSAPSetupUserNotificationTool.exe and NWSAPAutoWorkstationUpdateService.exe.

Note: The front-end side will query the last 10 installation sources that are network paths.

You have configured the SAP Automatic Workstation Update and made it available on the workstations.

To disable the service, activate the option ‘Disable Automatic Workstation Updates’ in the configuration tool on the installation server (see picture above). This configuration change is propagated as an update to the workstations at the time of the next update check.

Note: Once disabled, this action cannot be undone until the Automatic Workstation Update Service is reinstalled.

AWUS Notes

Note 1584270 - AWUS & SapSrvSetup.xml

Note 1624251 - Moving an Installation Server to a new machine

Controlling Remote Workstations

The remote workstation control functionality helps you to remotely access and control workstations on which you have administration privileges.

Choose Remote.

You have now several options:

Collect Log Files

With this option, you can collect log files from remote workstations. For this, you just have to enter the workstation name. In case you want to collect log files from several machines, you have to separate the different names by a comma.

Look at the remote workstation log files on your local pc after download.

Execute Process Remotely (WMI)

With this option, you execute processes on a remote workstation. You just have to enter the workstation name as well as the application name in the appropriate field. Also, you can supply the application with the appropriate command line parameter, for example: c:\program files\sap\sapsetup\setup\nwsapsetup.exe /uninstall /all /silent. Then choose Execute to run the process on the remote machine.

Remote Task Manager (WMI)

With this option, you get a list of processes running on a remote workstation. Just enter the workstation name and choose Display. If you want to terminate a process, select the process and choose Terminate.

Note: Be careful with the Terminate option, because the user may lose unsaved date.

Troubleshooting

If you encounter problems with the WMI feature, diagnose WMI connectivity to a remote workstation using the Microsoft tool wbemtest.exe. Note, that you have to supply the connection namespace as \\WorkstationName\root\cimv2.

Delegation

In order to start an installation on a remote workstation that is located on an installation server, delegation is required to be activated for the client machine(s) in question. Please, refer to the Microsoft TechNet article at http://technet.microsoft.com/en-us/library/ee692772.aspx, question 10 for further details.

Installation Process

Installing SAP Front End Components from an Installation Server

This procedure tells you how to install Front end Components from an installation server

Start NWSAPSetup.exe from the SETUP folder on the installation server.

The SAPSetup installation wizard appears.

Choose Next.

The product list is displayed. Products that have already been installed are pre-selected as shown in the following picture:

Select the products or SAP front-end components that you want to install or deselect the ones you want to remove.

Yellow dots indicate changes in the selection list. The Green plus next to a product name indicates that “This item will be installed” when the user installs the package on his or her workstation.

The checkbox with no additional symbols indicates that “This item is already installed” Uncheck the product if you don’t want to reinstall.

If you deselect a product in this list that has already been installed, a Red minus appears to indicate that “This item will be uninstalled”

Follow the wizard instructions to finish the GUI installation.

Installing Packages Configured by the Administrator

This procedure lets you install or remove packages on your front end that have been configured by the administrator on the installation server.

Note: Be careful when removing packages. Make sure you do not mistakenly remove shared components that are used by other packages you want to keep.

Start NWSAPSetup.exe /package from the SETUP folder of the installation server.

A list of the packages that the user is authorized to install or uninstall is displayed. Packages that have already been installed are pre-selected.

In this case, the BW Package has been selected for installation. The yellow dot indicates a change in the selection list. The green plus next to the product name indicates that this object will be installed when the user installs the package on his or her workstation. If you deselected a package, you would see a red minus next to the object selected for de-installation.

Select the components or packages that you want to install or deselect the ones you want to remove.

Note: If errors occur during the installation, SAPSetup displays a link to a document in which the errors have been logged. Contact the administrator of the installation server or the network and pass on the information given in this document.

Installing Packages Using the Logon Script

Since the front-end software is normally installed on a large number of computers, NWSAPSetup lets you automate this task.

By inserting a command line into the logon scripts of the computers on which the front-end software is to be installed, you can start a package installation each time the user logs on.

Enter the following command (both the path and either the package name or unique package identifier must be used):

\\<server>\<shared folder>\setup\NWSAPSetup.exe /package:“<package command-line name>“ /silent

You can also call NWSAPSetupAdmin.exe in the same way to perform this task.

When you start this command for the first time on a computer, NWSAPSetup installs the specified package.

Updating a Workstation from an Installation Server

You can update the front end from an installation server.

Updating the front end basically involves the same steps as an installation; see section Installation of the SAP Front End from an Installation Server

You have the possibility to have the update run unattendedly or automatically:

For unattended update, use the following command line: \\<server_path>\setup\NWSAPSETUP.exe /UPDATE /silent

To update a specific package or product, add:

/package="package command-line name"

Or

/product="product command-line name"

You will find the command-line name of the package or product in the administrative console NWSAPSetupAdmin.exe.

For automatic update, you can use the SAP Automatic Workstation Update. Whenever the installation server is patched, or the packages installed are updated, this service will update the workstation(s) and reboot them if necessary. The workstation updater works in two modes - one in the presence of a logged-on user and another in his or her absence

• When a user is logged on, the user is informed of update availability and the update happens on the user's assent. The user is also informed if a reboot is necessary and the reboot is also only executed on the user's assent.
• If no user is logged on, the update is done automatically and the reboot (if necessary) is done automatically, too.

The SAP Automatic Workstation Update is not SAP GUI-specific, it works with all components available on the installation server. For details, see section 3.9 Configuring SAP Automatic Workstation Update.

Log Files

All the installation tools described in this document maintain an activity record in log files that you can find here:

%ProgramFiles%\SAP\SAPSetup\Logs

Each tool stores the last ten log files.

Error Files

Errors are stored in an XML format in files that you can view in any browser and you can find in the following folder:

%ProgramFiles%\SAP\SAPSetup\Errors

If you have a problem, create a problem message in BC-FES-INS and attach the relevant log files to the message.

Return Codes

The following table describes the return codes for NwSapSetup.exe

Additional Information

Troubleshooting

Note 508649 - Diagnosis of frontend installation problems

References

http://scn.sap.com/docs/DOC-25456

http://scn.sap.com/community/gui/blog/2013/05/08/sap-gui-730-installation-errors

http://scn.sap.com/docs/DOC-42976

http://scn.sap.com/community/gui/blog/2013/05/02/sap-gui-730-patches-and-relevant-notes

http://scn.sap.com/community/gui/blog/2013/05/10/sap-gui-branding

***********

Hi all,

SAP GUI for Java 7.40 rev 3 is now available for download.

Enhancements and New Features

• Enhanced Search:
  • Support for limiting the search text to the field length has been implemented.
  • It is now possible to continuously type also while a search request is currently in process.
• DropDown Listbox:
  • The feature to navigate and select an item by typing multiple characters has been implemented.
  • Navigating in the list using the keyboard is now consistent with SAP GUI for Windows.
• Calendar Control:
  • Calendar Control now is based on the Date and Time API introduced in Java SE 8. This has not only greatly simplified the implementation but also added the possibility to support different calendaring systems.
• SAPInfo Control (ABAP class CL_GUI_FRONTEND_SERVICES):
  • For Linux and OS X, the handling of paths has been made more robust regarding ABAP coding using the wrong path separator.
  • In method EXECUTE the parameter DEFAULT_DIRECTORY now is honored in case the document or application path is relative.
• Display of PDF based Content:
  • A new version of the component to display PDFs is improving font management for some languages.
• OS X only:
  • The rendering performance has been improved by using imaging API, that is hardware accelerated also on OS X. This also reduces resource consumption.

  Bugfixes

• Table Control:
  • The rendering of disabled line selection buttons has been corrected.
• Html Control:
  • The query for the background color has returned a wrong value, which in some cases resulted in unreadable text.
  • When running embedded in Eclipse, problems with URLStreamHandlers resulted in showing empty areas instead of html content.
• Tree Control:
  • An issue where calling CL_GUI_COLUMN_TREE->ADJUST_COLUMN_WIDTH has calculated an incorrect column width has been solved.
• Display of PDF based Content:
  • Running with de-CH locale, the EURO sign has not been displayed.

For details please refer to the manual (chapter "6.2 Release Notes and System Requirements" and "2. Installation") of the PlatinManual and SAP note 2059424.

Please use Java 8 Update 40 or newer, because some known issues related to the Html control component have been addressed.

Planning information

SAP GUI for Java 7.30 is no longer supported. Therefore please upgrade to SAP GUI for Java 7.40.

For migrating your landscape configuration, please refer to the SAP UI Landscape Configuration Guide.

Best regards

Rolf-Martin Wörsinger

P.S. For feedback and questions, please post a new thread.

In case you want to report an issue, preferably create a support message on component BC-FES-JAV.

Recently, I was doing some RnD on SAP GUI for JAVA, and thought to share some knowledge and experience on same.

As we know Microsoft Windows has dominated over the past decades in the field of desktop OS. We use this OS in our daily work in offices or in home. However Windows in not only the desktop OS on market, but also there are other OSes available such as Mac OS X, Ubuntu, Red Hat, Fedora etc. All these OSes are of Linux variants.

By looking into this SAP has developed SAP GUI for JAVA specially meant for Linux OS. However the best thing is, one can install in Windows OS also.

Before using SAP GUI for JAVA let me remind you that, there are few drawbacks or limitations assiciated with it. Such as below. For more details you can refer to SAP note 454939

• Office Integration with regard to embedding Office documents inside the SAP GUI screen or controling Office programs by automation is not supported (note 509690). However downloading and opening documents is possible, opening of course depends on the installed Office products on the client.
• Search help control is not supported (the old style F4 help window is used instead, offering the same functionality).
• Graphical Screen Painter is not available. The alphanumeric layout editor is supported.
• Front-End Printing needs to be done using access method 'G', the new printing architecture for all platforms supported by SAP GUI for Java.
• eCATT is not supported.
• Chart control : copy/paste is not available yet.

In this document I am going to demonstrate how to install and configure SAP GUI for JAVA 7.40 in Windows and Linux desktops.

Before installing, we need to download the installation files and manage some pre-requisites.

Pre-requisites are as follows

Hardware:

Hardware according to the requirements of the Linux/Windows distribution

RAM: 4GB recommended for better performance

Software:

Oracle Java SE 8 32- or 64-bit (update 40 or newer)

Visual C++ Libraries VS 2012 11.0.60610 (x86 resp. x86_x64) - for Windows

Supported Windows OS:

Windows 7 32- or 64-bit (Professional, Ultimate and Enterprise Edition)

Windows 8 32- or 64-bit (Professional, Ultimate and Enterprise Edition)

Windows 8.1 32- or 64-bit (Professional, Ultimate and Enterprise Edition)

Supported Linux distributions:

SUSE Linux Enterprise Desktop 11 and 12

SUSE Linux Enterprise Server 11 and 12

openSUSE 13.1 and 13.2

Fedora 20 and 21

Red Hat Enterprise Linux 7

Ubuntu 14.04

A) Downloading required softwares from SMP.

1. The latest version avaiable in SMP is SAP GUI for JAVA 7.40. Go to the link and click on "SAP GUI FOR JAVA".
2. Now click the link based on your OS
3. Click on link with the latest patch (here patch 3). The patch files are cumulative in nature. This will download the installation files.

B) Installation Procedure in Linux OS

1. Type the command to install SAP GUI for JAVA.

        java -jar PlatinGUI-<Platform>-<Version>S.jar install

        For uninstallation type the below command

        java -jar PlatinGUI-<Platform>-<Version>S.jar uninstall

  2. Go to the installation directory and type ./guilogon to open logon pad. 

C) Installation Procedure in Windows OS

1. Double Click on the .jar file or type the command to install SAP GUI for JAVA.

        java -jar PlatinGUI-<Platform>-<Version>S.jar install

        For uninstallation type the below command or run the uninstall.bat batch file present in installation directory

        java -jar PlatinGUI-<Platform>-<Version>S.jar uninstall

   2. Go to the installation directory and under bin directory run guilogon.batto open logon pad or double click on the shortcut created.

D) Configuring for Connection settings (valid for Windows & Linux)

1. On the logon pad click on new connection
2. Give description and click on "Advanced" tab. Here we have to set the connection string.
3. Check the "Expert Mode" and put the string in the following syntax

        conn=/H/<HOSTNAME>/S/32<INSTANCENo>

That's it. All done.

Queries edited by SAP GUI 7.4 is not editable in lower versions of SAP GUI such as 7.3 .

There may be some solutions like reinstall lower versions or apply some patch .But these are not quick ones and also not feasbile .

Developer may be in peril sometimes about this and so below workaround will help you to resolve this and make the query again editable with lower versions .

So please follow the attached doc to resolve this .

Note: This Article is about SAP Screen Personas 2.0.

This document explains how to assign Flavors to a Group of Users.

A Flavor is created through SAP Personas 2.0 by the Developer or Consultant.This Flavor needs to be assigned to a list of Users.

Following are the steps with Screenshots.

Step1 : Login into SAP ECC system and go to transaction code /PERSOS/ADMIN_UI

Step2: Select Group Maintenance.

           Give a Group Name and select the system(in which the flavors are created) and assign list of users to the Group.

Step3: In the Above Screen, click on 'Assign Flavors'.

            Select the Flavors which should be assigned to the users.

Step4: Next select 'Mass User Maintenance'.

            Select the Group and click on List Users Button.

            Select all or required users.

            Select System where the Flavors are created.

            Select Personas Role and generally for End users, we use 'RENDER_ROLE'.

            Click on Apply.

Now the End user when he logs in through SAP Personas system, he can view the Flavor.

As announced earlier this month, SAP Screen Personas 3.0 is now General Available (GA):

http://scn.sap.com/community/gui/blog/2015/07/06/sap-screen-personas-30-is-generally-available-including-service-pack-1.

This undoubtedly represents a great achievement for SAP's overall UX strategy, as SAP Screen Personas 3.0 is an incredibly powerful toolkit that enables organizations to simplify their Dynpro screens (SAP GUI for HTML) and to improve productivity through personalization. The easier-than-ever editing and the very straightforward look and feel will transform the way companies do business. Our primary goal is to run simple, and SAP Screen Personas 3.0 fits smoothly into this framework.

We would never have reached such an important goal without the fundamental contribution from you, our customers and partners, who have accepted to use the product during ramp-up phase and during our usability tests. Your feedback helped us understand the users' needs while having them work with the product first hand. You have given us precious feedback to further improve SAP Screen Personas. This is why we are constantly asking you for your opinions and feedback on our product - your ideas really matter to us, as they allow us to grow mature and be a bit better every single day.

As we had announced a couple of months ago: http://scn.sap.com/community/gui/blog/2015/04/16/3-reasons-why-to-sign-up-now-for-testing-sap-screen-personas-30, we held usability test sessions at ASUG in Orlando, Florida from May 5 to May 7. Now we want to share what we have obtained and the consequent actions that we have taken.

Study Goals

As already mentioned, we wanted to get feedback from testers about the usability of the SAP Screen Personas 3.0 HTML with the new Slim Editor version. The new Slim Editor has changes included that we made based on the test feedback we got from the TechEd usability testing in Berlin in Nov 2014.

Test Setup and Preparation

Each test session was one hour long, with one tester, one observer, the moderator and a note taker.

We had a total of 13 testers and 8 observers. They came from very diverse backgrounds and had different business roles. Their knowledge about SAP Screen Personas was also very diverse: some had taken the openSAP course on SAP Screen Personas,

https://open.sap.com/courses/sps1/items/5qylb83IuK9YM8QvWk00O4/quiz_submission/291GF4q7QLywM34fYGXXfZ

some were ramp-up customers and were more familiar with it, while others had barely heard its name. Therefore all testers were asked whether they knew what SAP Screen Personas is, and those who had no experience with the tool got a short verbal description, but no demo was shown.

How the Test worked

We assigned the testers a fictional organizational role to give them context and simulate a real life situation. We explained that their goal was to implement SAP Screen Personas in their organization.

Each tester got 9 test tasks with increasing level of complexity. A description of what to do with the Slim Editor was provided, but no indications on how to do it. The tasks ranged from building a flavor– a specific personalization for a particular SAP transaction in a specific system – and choosing a theme for the flavor, to modifying dashboards and merging tabs.

Testers were asked to “think aloud” as they went through the test and were closely watched as they proceeded step by step. Their reactions to the tasks and their behavior during the test were recorded.

At the end of each test we asked them a few wrap-up questions about what they had liked, what they had not liked or understood, what they would have done differently, what they would have liked to see in the future and whether they were planning to use SAP Screen Personas. We also handed out a post-test survey.

Results

All testers demonstrated great interest in the product, and were enthusiastic to participate in the test. The demand was so high that we offered an additional test session. All testers answered our wrap-up questions and 11 of them filled out the survey.

What is good: the Strengths of SAP Screen Personas

We received extremely positive feedback on SAP Screen Personas, and all testers declared to be very satisfied with the tool:

• They were amazed by the ease of use, even if they had no experience with the product beforehand;
• They all understood that profound knowledge of what to change is required before starting to build flavors, but were pleased with the fact that the tool has everything to modify SAP GUI for HTML transactions;
• They appreciated the possibility to create flavors for specific user groups, for example new employees, leading to a very fast learning curve with less data on the screen.

What is even better: the Weaknesses that no longer exist

What has proved really important for us to grow is critical feedback, as it gives us an idea of what to improve on SAP Screen Personas to make it work even better. Testers raised a few minor usability issues with the tool, together with suggestions on how to solve them. We took their statements and started working from there to improve the product. We took immediate action and solved most difficulties so that they no longer exist. Some examples are:

• There was a confusing and superfluous checkbox when creating a new flavor asking to base it on the original screen, which was the only available option --> we have eliminated the checkbox (see Picture 4);
• There was no tooltip on the “Flavor Gallery” icon and most users did not understand the meaning of the icon --> we have added a tooltip;
• The “Pin” Icon was not intuitive enough --> we made more clear and helpful also for the visually impaired

Constantly working for you

As customer satisfaction with an easy and pleasant user experience is our primary goal, we keep working on improving SAP Screen Personas 3.0. More advancements based on customer feedback are to come in the near future, aiming to an even more powerful and efficient simplification tool.

For example, we are planning to add two important modifications very soon:

• Objects on the screen would no longer overlay each other and will appear as stacked (Picture 5);
• The “Save”, “Exit” and “Save and Exit” icons would be accompanied by explanatory text

We are planning to offer further usability testing sessions in the future and take customers’ suggestions like we have already done. We will keep you posted and you will be informed of any upcoming sessions.

We can be proud of our successes, but we are always ready to learn and grow. This is the best way we can be there for you and allow you to really run simple.

Keep following us!

For the SAP Screen Personas product team, Sylvia Barnard and Giulia Savino (Intern at SAP Screen Personas Product Team)

You find the release information in SAP Note 2157163.

Hi all,

SAP GUI for Java 7.40 rev 4 is now available for download.

Enhancements and New Features

• Support for New OS Versions:
  • Fedora 22
  • Windows 10
• Localization: Texts in dialogs coming from the Java runtime like confirmation and options dialogs are now translated the supported languages.
• Modal Dialogs:
  • Sometimes the buttons in the toolbar of modal dialogs do not fit into the modal dialog with the size set by the backend. As a result buttons are cut off. Now the width of the dialog is increased to no longer truncate the toolbar content (except in those cases, where changing the dialog size would cause side effects).
• Table Control:
  • It is now possible to open a context menu on the title and header area.

  Bugfixes

• Rendering:
  • The usage of a faster drawing API of Java introduced in 7.40 rev 3 has caused some artefacts in various environments depending on the OS resp. Linux distribution, graphics card and driver. A workaround has been implemented without falling back to the slower performance of previous releases.
• Enhanced Search:
  • While using the enhanced search, it could happen that the same text typed before was filled into another input field as well.
• Signature Design:
  • Highlighted text in some places was hard to read because of using a wrong foreground color when a scheme other then the default was used.
• TextEdit Control:
  • The sequence of ABAP calls SET_TEXT_AS_R3TABLE, GET_TEXT_AS_R3TABLE and again SET_TEXT_AS_R3TABLE in DEFINE code for the control CL_GUI_TEXTEDIT resulted in displaying an empty text.
• Tree Control:
  • In a special situation, an exception has caused the control to no longer repaint and react to user input.
• Blue Crystal:
  • Checkmark icons in menues have not been displayed.
  • Menu separators have been missing.

For details please refer to the manual (chapter "6.2 Release Notes and System Requirements" and "2. Installation") of the PlatinManual and SAP note 2059424.

Please use Java 8 Update 40 or newer, because some known issues related to the Html control component have been addressed.

Planning information

SAP GUI for Java 7.30 is no longer supported. Therefore please upgrade to SAP GUI for Java 7.40.

For migrating your landscape configuration, please refer to the SAP UI Landscape Configuration Guide.

Best regards

Rolf-Martin Wörsinger

P.S. For feedback and questions, please post a new thread.

In case you want to report an issue, preferably create a support message on component BC-FES-JAV.

Hi ,

Let us check how to create theme in screen Personas 3.0.

Click On P icon

Now -> Click on the themes as show in snap shot

Enter the Theme name and description

Select the general option from drop down list as highlighted.

Now to set the background image for theme -> Click on the icon highlighted.

Now select the image form the Image gallery and click on Done.

Now if you see then the background image will appear in your transaction.

Let us now set some size of user area in our screen.

Click on save and now your theme is ready to use.

Regards,

Vipul

How to insert image in the image gallery in screen personas 3.0

Hi,

In this document we will see how to insert image in the image gallery so that we can use as in place of Logo/Background of theme.

Goto Transaction -> /n/personas/resources

Click on create for selecting a single image from the Application tool bar.

Select the image from the destination path where the image is stored.

The following extension are valid: .png , .jpg , .jpeg , .gif , .zip .

Now you will be navigated to resource maintenance detail screen.

Click on Change -> Enter description of the image -> Save.

If we now check Personas, The image will be displayed in Image gallery and we can make use of the image either for background/Header/Logo.

Regards,

Vipul

Take an active part in testing SAP Screen Personas 3 with Web Dynpro Applications at DSAG in Bremen, Germany from Sept. 29 to Oct. 1, 2015.

1. This is an exclusive opportunity for SAP customers, partners and prospects to test new and existing products and solutions, and this time SAP Screen Personas 3 with Web Dynpro ABAP!
2. It allows you to give on-the-spot feedback directly to the product team who is designing the solution.
3. These sessions are one-on-one sessions with you where you will be working directly with the product.
4. There are 2 convenient ways to register:
   • Onsite at our Usability Testing Registration Desk – detailed location will be specified asap.
   • Right here below online where you have the best opportunity to get the topics and times you want before they get booked onsite
5. Spaces fill up quickly so don’t let this opportunity pass you by, sign up today!
   

For more information and online registration, please go to https://experience.sap.com/dsag/, get a user for 2015 DSAG User Conference, and then choose topic n° 9:“Personalization of Web-Dynpro ABAP applications with SAP Screen Personas” as your test topic, and secure one of the eleven available test sessions. The session language is German, and we can also offer sessions in English if required.

Available Time Slots for Usability Tests: (status: August 19^th.)

If you cannot join us in Bremen, then come to TechEd 2015 in Barcelona, Spain from Nov 10 to Nov 12, where we will offer SAP Screen Personas 3.2 usability tests. More information will come soon.

Looking forward to seeing you onsite in Bremen.

For the SAP Screen Personas product team, Sylvia Barnard

Hi,

Let’s check how to create F4 help in Screen Persona 3.0

• Goto transaction /n/personas/admin.

• Now click on the Goto-->F4 Help Whitelist

• Click on edit-->New entries-->Add table name, field name & counter and save the values.

• Now check on persona, click on ‘P’ icon-->click on a edit  flavour.

• Goto insert tab-->expand the Text field-->Click on F4 Help and add table name and field name on it and click on Done. And click on save and exit button.

• if you exit It will display like this:

Regards,

Chaitali Shah

Hi,

Let’s check how to upload icon in Screen Persona 3.0

• Go to Transaction /n/personas/admin

• Now click on the Goto--> Icon Maintenance

• Enter a name for Icon and click on Upload button, it will ask for choosing an icon from system. The file type are .png, .jpg, .jpeg, .gif, .zip.  

      Note:  The icon’s name should always start with Z.

• Now check on persona, click on ‘P’ icon-->click on edit flavor.

• Select any button and give its name and transaction code.Select that button and click on assign an icon.Now select an icon which you uploaded and click on DONE. we can align our icon here by choosing given options as Left of Label,Centre, Right of Label, No icon .

• The output will be shown like this:

Thanks and Regards,

Chaitali Shah

This Document gives instructions to avoid SAP GUI Security Pop Up when Download/Upload Attachments/Files from/to SAP.

Example Pop UP:

If you want to authorize to avoid this Pop Up, Please follow below steps.

On top of SAP screen, press customize local layout button

Then select Options

Below Pop Up appears

Select Security settings

Status appears as Customized like below

Change status customized to disabled

Press Apply

Now Security Pop Up will be disappeared when you try to Upload or Download to SAP.

Queries edited by SAP GUI 7.4 is not editable in lower versions of SAP GUI such as 7.3 .

There may be some solutions like reinstall lower versions or apply some patch .But these are not quick ones and also not feasbile .

Developer may be in peril sometimes about this and so below workaround will help you to resolve this and make the query again editable with lower versions .

So please follow the attached doc to resolve this .

Note: This Article is about SAP Screen Personas 2.0.

This document explains how to assign Flavors to a Group of Users.

A Flavor is created through SAP Personas 2.0 by the Developer or Consultant.This Flavor needs to be assigned to a list of Users.

Following are the steps with Screenshots.

Step1 : Login into SAP ECC system and go to transaction code /PERSOS/ADMIN_UI

Step2: Select Group Maintenance.

           Give a Group Name and select the system(in which the flavors are created) and assign list of users to the Group.

Step3: In the Above Screen, click on 'Assign Flavors'.

            Select the Flavors which should be assigned to the users.

Step4: Next select 'Mass User Maintenance'.

            Select the Group and click on List Users Button.

            Select all or required users.

            Select System where the Flavors are created.

            Select Personas Role and generally for End users, we use 'RENDER_ROLE'.

            Click on Apply.

Now the End user when he logs in through SAP Personas system, he can view the Flavor.

You find the release information in SAP Note 2157163.