You can use IBM® Installation Manager to install the management server and its associated databases and data files to an application server computer. However, installation is not complete until you deploy the management server Web archive (WAR) file to the application server. Use this task to deploy the management server WAR file on the English version of WebSphere® Application Server Community Edition.
When you deploy the management server WAR file to the application server, the application server creates an Apache Derby database called OptimServerDB.
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 management server 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 management server WAR file by using the Administrative Console of WebSphere Application Server Community Edition:
-XX:PermSize=NNNm -XX:MaxPermSize=MMMmFor 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=256mThe 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 management server 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.
-Dfile.encoding=UTF-8
/sbin/sysctl -w fs.file-max=100000
fs.file-max = 100000
/sbin/sysctl -p
/sbin/sysctl fs.file-max
ulimit -n 20048
ulimit -n 20048