SAP GUI for Java Configuration Generator Scripts

This set of scripts is meant as an example how to convert an existing set of configuration files for SAP GUI for Windows for the use with SAP GUI for Java. The scripts should work for standard cases but are neither meant to be complete nor perfect. The following three scripts are provided:

All three scripts will return a short help page when started with the option -h or --help. The version of each script can be determined by starting the script in question with the option -v or --version.

generateMessageServers.pl

Syntax: generateMessageServers.pl [-m filename] [-s filename] [-j filename]
-m | --winmsg: (INPUT FILE, default: ./sapmsg.ini)
-s | --winservices: (INPUT FILE, default: ./services)
-j | --javamsg: (OUTPUT FILE, default: ./messageservers.txt)
-d | --javadesc: -o | --overwrite: Overwrites an existing output file without prompting.
-h | --help: Prints this help text.
-v | --version: Prints the version of this script.

generateConnections.pl

Syntax: generateConnections.pl [-w filename] [-j filename]
-w | --wincon: (INPUT FILE, default: ./saplogon.ini)
-j | --javacon: (OUTPUT FILE, default: ./javagui_connections.txt)
-o | --overwrite: Overwrites an existing output file without prompting.
-h | --help: Prints this help text.
-v | --version: Prints the version of this script.

generateRouters.pl

Syntax: generateRouters.pl [-w filename] [-j filename]
-w | --winrouters: (INPUT FILE, default: ./saproute.ini)
-j | --javarouters: (OUTPUT FILE, default: ./routers.txt)
-o | --overwrite: Overwrites an existing output file without prompting.
-h | --help: Prints this help text.
-v | --version: Prints the version of this script.

Limitations of all three scripts

Please note that these three scripts are provided as they are without any support or warranty. These scripts are not an official release. In case of questions or feedback, please use the SAP GUI Forum on SDN and do not submit an official support message. Also, please be aware that none of these scripts performs any checks concerning the correctness or sense of the input files. If you convert broken configuration files for SAP GUI for Windows then the result will be broken configuration files for SAP GUI for Java. If there are e.g. duplicate entries in the routers file for SAP GUI for Windows then the same duplicates will exist in the routers file for SAP GUI for Java. Also, only the standard types of connection strings are supported. This includes connection strings using an application server and a port number (/H/HOSTNAME/S/PORTNUMBER) and connection strings based on symbolic system names (/R/SID/G/GROUP). Both types of connection strings can make use of Secure Network Communication (SNC) as well as routers. Still you are urged to take a deep look into the resulting configuration files for SAP GUI for Java before using them.