Geekflare is supported by our audience. We may earn affiliate commissions from buying links on this site.
In WebSphere Last updated: September 6, 2022
Share on:
Invicti Web Application Security Scanner – the only solution that delivers automatic verification of vulnerabilities with Proof-Based Scanning™.

IBM WebSphere Deployment Manager Console Access Auditing

Keeping track of configuration changes is essential for a production environment. This helps you to audit the changes done by the team and restore if needed quickly.

Having this implementation also discourage team to perform unauthorized changes in production.

So you see its win-win situation for business and production management.

By default, WebSphere DMGR logs (SystemOut.log) doesn’t capture who has logged in changes made in DMGR. Hence it’s risky for a critical production application.

So let’s find out how to enable tracking of DMGR console login.

First thing first – you should take a backup of configuration as a best practice.

Backup is a lifesaver!

Now the implementation part…

  • Login into WAS DMGR
  • Click on System administration >> Deployment manager (at left navigation panel)


  • Click on Logging and tracing under Additional Properties


  • Click on NCSA access and HTTP error logging


If you are wondering NCSA abbreviation – National Center for Supercomputing Applications

  • Tick the checkbox for “Enable logging service at server start-up
  • Select Combined from drop-down under NCDA access log format


  • Click on Apply and OK to review and save the configuration
  • Restart the DMGR to reflect the change

Once DMGR is restarted, you will notice new file generated (http_access.log) under dmgr/logs


From now onwards, whoever login into DMGR, you will see their IP, browser, and action they perform. Ex:- - - [13/Aug/2015:04:25:16 -0700] "POST /ibm/console/j_security_check HTTP/1.1" 302 0 "" "Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0" " JSESSIONID:0000ScnHefKWkhUnULSnPzKZIRy:-1 TJE: TE3: sessionCode:738940671"

So you can see in above log, there is a login from at 13/Aug/2015:04:25:16.

Isn’t it cool to have this implemented, so you keep track of DMGR login?

Tip: by default, it will keep one file with maximum 500 MB. You may modify this to fit your capacity requirement.

Let’s say you want to allocate 1 GB for this logging then you can keep max ten files with 100 MB each so your configuration should be something like below.


I hope this helps you. Upgrade your skills in cloud computing.
Head here if you want to configure WebSphere Deployment Manager Console Identity.

  • Chandan Kumar
    Chandan Kumar is the founder of Geekflare. He’s helped millions to excel in the digital realm. Passionate about technology, He’s on a mission to explore the world and amplify growth for professionals and businesses.
Thanks to our Sponsors
More great readings on WebSphere
Power Your Business
Some of the tools and services to help your business grow.
  • Invicti uses the Proof-Based Scanning™ to automatically verify the identified vulnerabilities and generate actionable results within just hours.
    Try Invicti
  • Web scraping, residential proxy, proxy manager, web unlocker, search engine crawler, and all you need to collect web data.
    Try Brightdata
  • is an all-in-one work OS to help you manage projects, tasks, work, sales, CRM, operations, workflows, and more.
    Try Monday
  • Intruder is an online vulnerability scanner that finds cyber security weaknesses in your infrastructure, to avoid costly data breaches.
    Try Intruder