We earn commission when you buy through affiliate links.

This does not influence our reviews or recommendations.Learn more.

However, there are specific configurations you must be aware as a WebSphere administrator.

core-group-services

The following 15 configurations are often touched or asked in an interview.

If you are a beginner, I strongly you recommend you go through my previous two articles.

WebSphere tool Server ND Installation Guide

Useful WebSphere tool Server Administration Scripts

So lets get it started.

was-logging-tracing

This will help you in housekeeping of SystemOut.log & SystemErr.log files.

To configure themaximum single log file size,you’re able to enter the value in Maximum Size.

In this ex, I have given 100 MB (by default its configured with 1 MB).

jvm-development-mode

In this ex, I have left it to default 24 hours.

The number in a range of 1 through 200.

In this ex, I have given 30, which will keep 30 log files all the time.

jvm-session-cookie-name

Repeat the same configuration for SystemErr.log.

Here is the screenshot of above configuration.

As usual, press OK to Sync and Save the configuration.

jvm-heap-size

These all three configurations are done on a single page by:

6.

In this ex I have configured 2 GB as min and max.

You may also refer to my detailed article on how to modify WAS JVM memory.

jvm-verbose-gc

By default its disabled.

Mostly development team would recommend it.

Dont forget to Sync & Save the configuration and restart the JVM to see the effects.

jvm-classpath

This is good and bad both.

Bad: you dont know why JVM was stopped you may overlook potential production issue.

In this ex I have configured 50 MB as file size and ten maximum numbers of files.

disable-jvm-autorestart

Change JVM logging level

By default, JVM logging level is configured in info mode.

This must be configured on individual JVM level.

Change Context Root for system

you could change the context root for deployed system without re-deploying it.

dmgr-ncsa-log

The procedure is straightforward and very useful if you decide to change the context root.

JVM must be restarted to take effects.

Well, it’s possible for you to quickly change the virtual host by following:

15.

was-log-level

Create Virtual host

WAS comes with three virtual hosts (admin, default & proxy).

If you are using WAS environment for the single software, then the default should be sufficient.

Take your career to the next level bylearning cloud computing.

thread-pool

context-root-was