You must deploy the manager Web archive (WAR) file to the
application server before you can use the manager. Use this task to
deploy the WAR file on the English version of WebSphere® Application Server Community
Edition.
When you deploy the WAR file to the application server,
the application server creates an Apache Derby database called optimConsoleDB.
The application server associates the optimConsoleDB database with
the OptimConsoleDB database pool.
The version of WebSphere Application Server Community
Edition that is delivered with the manager is available only in English.
You must configure this version of WebSphere Application
Server Community Edition by using an English user interface. However,
when you use the manager, the language setting of the browser determines
the language of the manager user interface. The language setting of
the browser also determines the language of the messages that are
received from the management server and proxy.
Use
the Administrative Console of WebSphere Application
Server Community Edition to deploy the WAR file. The default location
of the Administrative Console is http://hostname:8080/console,
where hostname is the host
name of the computer on which WebSphere Application
Server Community Edition is installed.
To deploy the manager
WAR file with the Administrative Console of WebSphere Application Server Community
Edition:
After you deploy the manager WAR file to the application
server, you can configure manager properties. To configure manager
properties, edit the script that you use to start the application
server. This script is located at the following location, where
shared_installation_directory is
the installation directory that you specified for the Optim Manager
installation package.
- Windows computers: shared_installation_directory\WebSphere\AppServerCommunityEdition\bin\startup.bat
- Linux or UNIX computers: shared_installation_directory/WebSphere/AppServerCommunityEdition/bin/startup.sh
If the WAR file fails to deploy because of
java.lang.OutOfMemoryError:
PermGen space errors, increase the amount of permanent generation
memory available for objects in the Java Virtual
Machine (VM) on the application server. To increase the available
amount of permanent generation memory, edit the application server
startup script. Open this script in a text editor and add the following
argument to the end of the
JAVA_OPTS parameter in
the script.
NNN is the initial
amount of permanent generation memory in MB and
MMM is
the maximum amount of permanent generation memory in MB. The entire
JAVA_OPTS parameter
must be either on a single line or on consecutive lines that are connected
with line-continuation characters. The line-continuation character
is the caret (
^) for Windows batch scripts or the backslash (
\)
for Linux or UNIX scripts.
-XX:PermSize=NNNm -XX:MaxPermSize=MMMm
For
example, the following
JAVA_OPTS parameter from a Windows batch script specifies
128 MB as the initial amount of permanent generation memory and 256
MB as the maximum amount of permanent generation memory.
@set JAVA_OPTS=%ADDITIONAL_JAVA_OPTS% %JAVA_OPTS% ^
-Djavax.net.ssl.keyStore="%GERONIMO_HOME%\var\security\keystores\optim-management-server.jks" ^
-Djavax.net.ssl.trustStore="%GERONIMO_HOME%\var\security\keystores\optim-management-server.jks" ^
-Djavax.net.ssl.keyStorePassword=manager -Djavax.net.ssl.trustStorePassword=manager ^
-XX:PermSize=128m -XX:MaxPermSize=256m
The
following
JAVA_OPTS parameter from a Linux or UNIX script
specifies 128 MB as the initial amount of permanent generation memory
and 256 MB as the maximum amount of permanent generation memory.
JAVA_OPTS=-Djavax.net.ssl.keyStore=$GHOME/../var/security/keystores/optim-management-server.jks \
-Djavax.net.ssl.trustStore=$GHOME/../var/security/keystores/optim-management-server.jks \
-Djavax.net.ssl.keyStorePassword=manager -Djavax.net.ssl.trustStorePassword=manager \
-XX:PermSize=128m -XX:MaxPermSize=256m \
$JAVA_OPTS
By
default, the manager uses 64 MB of permanent generation memory. Setting
memory sizes to a value larger than the amount of available physical
memory on your machine severely degrades performance.
If
the application server is on a computer that is set to a language
that requires the use of double-byte characters, configure the application
server to use UTF-8 encoding in its log files. To configure the application
server to use UTF-8 encoding, add the following argument to the end
of the
JAVA_OPTS parameter in the application server
startup script. The entire
JAVA_OPTS parameter must
be either on a single line or on consecutive lines that are connected
with line-continuation characters. The line-continuation character
is the caret (
^) for Windows batch scripts or the backslash (
\)
for Linux or UNIX scripts.
-Dfile.encoding=UTF-8
If the WAR file fails to deploy to a Linux computer because of
IOException:
too many open files errors, increase the maximum number of
open files on the computer. To increase the maximum number of open
files, sign on as superuser and complete the following steps.
- Enter the following command:
/sbin/sysctl -w fs.file-max=100000
- Add the following line to the /etc/sysctl.conf file
so that the setting remains as it is after system reboot.
fs.file-max = 100000
- Enter the following command so that the change to the /etc/sysctl.conf file
takes effect.
/sbin/sysctl -p
- Enter the following command to verify the settings.
/sbin/sysctl fs.file-max
- Enter the following command to increase the maximum number of
processes to 20,048.
ulimit -n 20048
- Add the following line to the beginning of the shared_installation_directory/WebSphere/AppServerCommunityEdition/bin/startup.sh script
so that the setting is set every time that you start the application
server.
ulimit -n 20048