SAP GUI installation on Mac OS

SAP GUI for Java Installation

System Requirements

Make sure you have installed a supported Java Virtual Machine (JVM) and the necessary run time libraries.

Installation

Download Package :  

PlatinGUI730MacOSX_2-20008876.JAR

The complete installation program is contained in the SAP GUI for Java package PlatinGUI-<Platform>-<Version>S.jar.
The package is signed and versioned. You can verify the integrity of the package with the jarsigner program included with your Java Virtual Machine to make sure the code is authentic and the package is not damaged.
jarsigner -verify -verbose PlatinGUI-<Platform>-<Version>S.jar

To verify the version and build details of the package you can ask for the version information:
java -jar PlatinGUI-<Platform>-<Version>S.jar version
To start the installation procedure just double click the installation package or if your environment does not provide direct support for starting jar packages invoke the installer from a command line interpreter.
java -jar PlatinGUI-<Platform>-<Version>S.jar [command] [options]
The installer knows three different commands install, uninstall and version.
The most important command is the install command, which is also the default if no command is specified.

The install command

java -jar PlatinGUI-<Platform>-<Version>S.jar install [options]
or equivalent
java -jar PlatinGUI-<Platform>-<Version>S.jar [options]
The install command can take several options.
General option syntax states that long option names start with two dashes and that boolean options are positive and denoted in lower case. Boolean options can be negated and the negative short option is denoted with an uppercase letter the long option name changes to --no<option>. Short options can not be clustered (so -fG is not correct but would be interpreted as a non existent option -f taking one parameter G). The space between an option and its parameter is not really required but recommended.

--help, -?

Print all installation options.

--force, -f, negated: --noforce, -F

Normally the installer will do nothing if it detects that this version of the SAP GUI for Java is already installed, -f forces a reinstallation.

--installdir <path>, -d <path>

Absolute path to installation directory if this option is omitted a reasonable platform dependent default location is used.

--verbose, -v, negated: --noverbose, -V

Provide verbose installation output on the console.

--standard, -s, negated: --nostandard, -S

Use standard options and install without user interaction. This is not a silent installation since progress indication and installation summary and all error dialogs are still displayed.This is well suited for automatic graphical installations.

--desktopicons, -m, negated: --nodesktopicons, -M

Install desktop menu and shortcuts. Per default this option is true so usually it is used as negated option -M, --nodesktopicons to prevent icons and menu entries to be created.

--gui, -g, negated: --nogui, -G

Use the graphical user interface for the installation. Per default this option is true so to turn off the graphical user interface use the negated form of the option -G, --nogui.If you turn off the graphical user interface you will get error messages and a short installation summary on the console.

--register, -r, negated: --noregister, -R

Centrally register the executable application as application path on Windows, as link into /usr/bin on Unix.

--inputfile <path>, -i <path>

Provide an installation response file to define installation parameters.

--logfile <path>, -l <path>

Write the installation log to the path.

--trace <tracekey1:tracekey2>, -t <tracekey1:tracekey>

Activate tracekey1 and tracekey2 during installation. Traces are always written to standard error.

The uninstall command

java -jar PlatinGUI-<Platform>-<Version>S.jar uninstall
The uninstall command removes an installed version of the SAP GUI for Java.

The version command

java -jar PlatinGUI-<Platform>-<Version>S.jar version
The version command just lists version information for the installation package.

Build date           : 2012-08-16 06:01:11 +0200
Build Info           : ldm046, 730_REL, 1353310
Product type         : 1
Numeric Version      : A073000020200
Short Version Number : 7.30beta2
Long Version Number  : 7.30 beta 2
Short Version        : SAPGUI7.30beta2
Long Version         : SAP GUI 7.30 beta 2
Full Version         : SAP GUI for Java 7.30 beta 2
Official Version     : SAP GUI for the Java Environment 7.30 beta 2

Installation Response File

You can automate the installation process by providing an installation response file using the -i <responsefile> option to the install command.
Available Properties:

installdir=<path> or installpath=<path>

Absolute path to installation directory, the special value default installs into the platform dependent default location (same as -d <path>).

disableui=true

Disables the interactive graphic installation program. All installation parameters have to be supplied using an installation response file or as command line options. All installation messages are written to standard output and standard error (same as -G).

automatic=true

If all necessary parameters are specified only show progress indication and error dialogs (same as -s).

reinstall=true

If this version of the SAP GUI for Java is already installed it is silently reinstalled and the installation proceeds as normal (same as -f).

uninstall=true

Remove the SAP GUI for Java installation if this version is installed, then exit (corresponds to the uninstall command).

logfile=<path>

Absolute path to installation log file including file name (same as -l <path>).

noshortcuts=true

Do not create desktop menus and desktop shortcuts (same as -M).

registerapplication=true

Centrally register executable application as application path on Windows, as link into /usr/bin on Unix (same as -r).

The file format is a list of lines with each one describing a property as a key value pair. Key names are delimited by "=" and ":". These characters can be escaped in key names and in the value text using "\" as escape character. Therefore a literal "\" also has to be escaped.
Complete lines can be commented with "#".
Example of a Typical Response File:

# Example of a typical installation response file
# suppress user interaction
disableui=true
# install to the default path
installidir=default
# reinstall gui if already present
reinstall=true

Web Deployment

Web installation is triggered by the content of a web page that was set up by the system administrator. If there is currently no SAP GUI for the Java Environment installed on the front-end computer, or if the version does not meet the requirements specified on the web page, the automatic installation is triggered. In order for this to work, your web browser security settings must be set to enable download and installation of controls and executable files.
The SAP GUI for the Java Environment applet will be downloaded and started from the website provided.
In order to run the applet with the required privileges, its signature has to be verified. Click 'Grant always' or 'Grant this session' on the certificate verification dialog. This will ensure that the GUI applet code can run as a trusted applet (this dialog only appears if the certificate has not been generally accepted by clicking 'Grant always'). See Background Information: Signed Applets for more information)
If there is no SAP GUI for the Java Environment installed or if the installed version is older than the version requested on the web page, the installation will be started.
When the installation has finished, the SAP GUI for Java is started.

Browser Default Version

Several versions of SAP GUI for the Java Environment can be installed and run on a single front-end computer in parallel. However, only one of the installed versions can be used within the web browser at any one time. This dedicated version is called the "browser default version".
By default, the browser default version is always the most recent version installed.
You can configure the current browser default version by using the 'Version Options' dialog. Start SAP GUI for the Java Environment as a standalone application and choose 'Options/Version' from the logon window menu to open this dialog. Use the 'Default version' drop down list box to choose the default browser version.

Installation Log File

Each installation of SAP GUI for the Java Environment writes a detailed protocol of all installation activities to the 'sapgui.log' log file.  Please consult this file if you encounter any installation problems.The file is located in a place that is platform-specific:

Windows and UNIX platforms:

<home directory>/sapgui.log

Mac OS X:

<home directory>/Library/Logs/sapgui.log

Remove a SAP GUI for Java installation

If the installation user interface detects that this version of the SAP GUI for Java is already installed it allows to remove the installation or to reinstall.
On all platforms you can also use the command line installer to remove a installed version by calling
java -jar PlatinGUI-<Platform>-<Version>S.jar uninstall
On Win32 platforms you can remove a centrally-installed SAP GUI for the Java Environment using the Software control panel. User installations are not centrally-registered under Windows and can just be deleted (for Windows Vista specific information please see "Windows Vista Deinstallation").

PATH and Environment

By default, the GUI start scripts use the Java Runtime Environment found in PATH (see requirements) or the application registration. If you want to use a different Java Runtime Environment, you may specify it using the PLATIN_JAVA environment variable which points to the Java executable to be used for example: /usr/bin/java. You can also use PLATIN_JAVA to provide the Java Runtime Environment with additional options.

You can add the bin directory of the SAP GUI installation to your PATH in order to allow the invocation of the SAP GUI for Java from everywhere.