Best practices for installing application clients : WAS ND

Best practices for installing application clients

The following table offers tips for installing application clients on multiple platforms.

Operating environment Application client type Tip
Linux and UNIX systems All Spaces are not supported in the name of the installation directory on Linux and UNIX platforms.
UNIX systems All When client application installations are successful, the return code 1 is issued from the UNIX shell where you issued the /install command. Any other return code indicates an unsuccessful installation.
Solaris systems All Double-byte character set (DBCS) characters are not supported in the name of the installation directory on Solaris systems.
Windows NT systems All Spaces are not supported in the name of the installation directory.
Note:

If you select the Pluggable Client feature, upgrade to the Java Development Kit V1.4.2 by switching the Java Runtime Environment and Software Development Kit installation location, after you install the pluggable application client. To upgrade, see Installing application clients.

All platforms Reserve at least 4 to 5MB free space in the target platform temporary directory.
All platforms When specifying a different temporary directory while installing application clients, the following message is displayed if the target platform default temporary directory does not have enough free space to install application clients:

Error writing file = There may not be enough temporary disk space. Try using -is:tempdir to use a temporary directory on a partition with more disk space.
Use the -is:tempdir installation option to specify a different temporary directory. For example, the following command uses /swap as a temporary directory during installation:

./install -is:tempdir /swap

All platforms After the installation, when changing the installation settings for the WebSphere Application Server host name and the port number, edit the setupClient.bat for Windows or setupClient.sh for UNIX. Change the DEFAULTSERVERNAME and SERVERPORTNUMBER to the new WebSphere Application Server host name and port number, respectively. If the SERVERPORTNUMBER is not set, then the default is 2809. Review the following example:

set DEFAULTSERVERNAME=NDServerName set SERVERPORTNUMBER=9810
The setupClient.bat file or setupClient.sh file is located in the bin subdirectory under the application clients installation destination.

Using the Konqueror file in the K Desktop Environment

When starting the Launchpad program for WebSphere Application Server clients, V5.1 using the Konqueror file manager in the K Desktop Environment (KDE) on Linux systems, a "Could not find the program launchpad.sh" error occurs.

Because the launchpad.sh command uses a relative path to locate the Java program, run the launchpad.sh command from the directory where the launchpad.sh command is located. When using the Konqueror file manager to issue the launchpad.sh command, the current directory is your home directory, and therefore, the launchpad.sh command does not function.

Do not use the Konqueror file manger to issue the launchpad.sh command. Open a Konsole session in the KDE, change the current directory to where the launchpad.sh command is located, and then run the launchpad.sh command.

Installing application clients
Installing application clients silently

Operating environment	Application client type	Tip
Linux and UNIX systems	All	Spaces are not supported in the name of the installation directory on Linux and UNIX platforms.
UNIX systems	All	When client application installations are successful, the return code 1 is issued from the UNIX shell where you issued the /install command. Any other return code indicates an unsuccessful installation.
Solaris systems	All	Double-byte character set (DBCS) characters are not supported in the name of the installation directory on Solaris systems.
Windows NT systems	All	Spaces are not supported in the name of the installation directory. Note:
		If you select the Pluggable Client feature, upgrade to the Java Development Kit V1.4.2 by switching the Java Runtime Environment and Software Development Kit installation location, after you install the pluggable application client. To upgrade, see Installing application clients.
All platforms		Reserve at least 4 to 5MB free space in the target platform temporary directory.
All platforms		When specifying a different temporary directory while installing application clients, the following message is displayed if the target platform default temporary directory does not have enough free space to install application clients: Error writing file = There may not be enough temporary disk space. Try using -is:tempdir to use a temporary directory on a partition with more disk space. Use the -is:tempdir installation option to specify a different temporary directory. For example, the following command uses /swap as a temporary directory during installation: ./install -is:tempdir /swap
All platforms		After the installation, when changing the installation settings for the WebSphere Application Server host name and the port number, edit the setupClient.bat for Windows or setupClient.sh for UNIX. Change the DEFAULTSERVERNAME and SERVERPORTNUMBER to the new WebSphere Application Server host name and port number, respectively. If the SERVERPORTNUMBER is not set, then the default is 2809. Review the following example: set DEFAULTSERVERNAME=NDServerName set SERVERPORTNUMBER=9810 The setupClient.bat file or setupClient.sh file is located in the bin subdirectory under the application clients installation destination.