This week's book giveaway is in the HTML Pages with CSS and JavaScript forum.
We're giving away four copies of Testing JavaScript Applications and have Lucas da Costa on-line!
See this thread for details.
Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

How to restrict access to the servlet IBMTrackerDebug in websphere version 6.0.2?

 
Ranch Hand
Posts: 136
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,
In my project I need to block access for the servlet com.ibm.ws.webcontainer.httpsession.IBMTrackerDebug. After searching for a while I saw that I have to add serveServletsByClassnameEnabled="false" in the ibm-web-ext.xmi file. Now my question is that do I need to manually create the .xmi file and edit the field? I have tried that but the deployment fails and gives the error that "EAR fire is corrupted". Then I deploy it without creating the .xmi file and checked the installApp folder of websphere and inside <myproject.war>/WEB-INF I saw ibm-web-bnd.xmi file created but not the ibm-web-ext.xmi.
I am using Websphere 6.0.2 for deployment.

Please help.
 
It's just a flesh wound! Or a tiny ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
    Bookmark Topic Watch Topic
  • New Topic