WebSphere® Application Server settings for VersionVault WAN server
Review IBM® WebSphere® Application Server settings for the application server profile for the VersionVault WAN server. If you installed VersionVault into a new profile, the settings in the profile created during installation have been optimized for best performance. If you installed VersionVault into an existing profile or if the server has performance problems, the parameter values might require adjustment.
- Tuning performance in the WebSphere® Application Server documentation: V8.5.
WebSphere® Application Server setting | Default value |
---|---|
Web container > customer properties | com.ibm.ws.webcontainer.channelwriteType=sync |
Web container transport chains > WSInboundDefault > Http inbound channel | Write timeout=300 seconds Persistent timeout=120 seconds |
Process definition > Java Virtual Machine | Initial heap size=1024 MB Maximum heap size=1024MB |
Thread pools | Web Container=300 Default=300 |
Troubleshooting > Logging and Tracing > Diagnostic trace service | Maximum File Size=20MBMaximum number of Historical files=20 |
Modifying application server profile settings for WebSphere® Application Server for VersionVault WAN server
If the VersionVault WAN server is deployed in an existing profile, modify the application server profile settings for WebSphere® Application Server to match the default values.
Before you begin
About this task
In a WebSphere® Application Server, you can modify tuning parameter values for the application server profile from the WebSphere® Application Server administrative console, or use the Wsadmin tool.
These instructions explain how to update the parameter values to the default settings at one time by using the Wsadmin tool commandsetCMdefaultDefaults
. You can also run
commands to change specific parameters. For example, use this Wsadmin tool
command to change the JVM Heap Size
to the default value:
setJvmMaxHeapSize 1024
For more information about using the WebSphere® Application Server administrative console and the Wsadmin tool, see the WebSphere® Application Server documentation: V8.5.
Procedure
-
Modify the application server profile settings for WebSphere® Application Server for the
VersionVault WAN
server:
- Run the
setCMdefaultDefaults
command to apply the default values to the profile hosting the VersionVault WAN server.- Open a command window or shell and go to the WebSphere® Application Server
bin directory.
- Windows™:
cd C:\Program Files\HCL\WebSphere\bin\
- UNIX or Linux:
cd /opt/HCL/WebSphere/bin/
- Windows™:
- Run the following WebSphere® command to set the
WebSphere® Application Server
settings to the default values:
- Windows™:
wsadmin.bat -profile -profileName ccrcwebprofile "C:\Program Files\HCL\CCM\VersionVault\web\ccrcAdminUtils.jacl" -c "setCMdefaultDefaults"
- UNIX or Linux:
./wsadmin.sh -profile -profileName ccrcwebprofile "/opt/hcl/CCM/versionvault/web/ccrcAdminUtils.jacl" -c "setCMdefaultDefaults"
- Windows™:
- Open a command window or shell and go to the WebSphere® Application Server
bin directory.
- Use the WebSphere® Application Server administrative console to change the settings:
- Start the WebSphere® Application Server administrative console. The default location for the console is
http://server:port/hcl/console.Tip: The port for the console is listed in <profile home>/logs/server1/AboutThisProfile.txt, where profile home is the home directory from the VersionVault Remote Client profile.
- In the administrative console, click
- Update the settings to the default values listed in Table 1.
If the profile is shared with other applications, consider the requirements for all applications before changing the values.
- Start the WebSphere® Application Server administrative console. The default location for the console is
http://server:port/hcl/console.
- Run the
-
Restart the WebSphere® Application Server profile for the change to take effect.
- Windows™:
stopServer.bat server1 -profileName cqwebprofilestartServer.bat server1 -profileName cqwebprofile
- UNIX or Linux:
./stopServer.sh server1 -profileName cqwebprofile./startServer.sh server1 -profileName cqwebprofile
- Windows™: