Configuration settings | WebSphere Application Tutorial pdf free download

Configuration settings:

A deployment manager is created by creating a deployment manager profile. Once created, there usually is not much that you need to do. However, it is good to note that there are settings that you can modify from the administration tools. To view the deployment manager from the administrative console, select System Administration -> Deployment manager . You have two pages available, the Runtime page and the Configuration page .

Configuration tab

Because it is unlikely that you will need to change most of these settings we only give you a brief description here of the settings you can configure.
Java and Process Management
The Java and process management settings allow you to define how the deployment manager process is initialized. The only category of settings under this group is the process definition settings. These include:
=> JVM settings including heap size, class path and boot class path, and verbose settings for garbage collection, class loading, and JNI
=> Environment entries consisting of name/value pairs that define custom pro perties
=> Process execution properties (not used on Windows) that allow you to define process priority, run as settings, file permission mode mask, and process group assignment (for processor partitioning)
=> Process log settings for stdout and stderr logs
=> On the runtime panel to activate them immediately
=> The settings include whether to put the trace information in memory to file, and the trace output format. For more information about the diagnostic trace service settings
Logging and Tracing
Log settings are available for the following logs:
=> Diagnostic trace
=> JVM logs
=> Process logs
=> IBM Service logs
=> Change log detail levels
Web container transport chains
Transport chains represent network protocol stacks operating within a client or server. These settings give you access to transport chain definitions