[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-developers] Tomcat custom policy file usage
- Subject: [cobalt-developers] Tomcat custom policy file usage
- From: Jay Nelson <jay@xxxxxxxxxxx>
- Date: Fri Nov 16 15:46:53 2001
- List-id: Discussion Forum for developers on Sun Cobalt Networks products <cobalt-developers.list.cobalt.com>
There have been a few questions and answers about the
tomcat policy file and customizing for specific sites.
For the real scoop look in
/usr/java/jakarta-3.2.3/bin/cobalt-config.pl
This PERL script is run every time you start tomcat. If
you are fiddling with custom policies, your best bet is
to create a tomcat.policy.custom file or a
tomcat.policy.www.specificsite.com file as you need.
These files go in /usr/java/jakarta-3.2.3/conf
You have to edit tomcat.policy.master to grant privileges
outside of a site (e.g., I put a mm.mysql directory in
a global location outside the doctree and grant
privileges to access it so that I don't have to replicate
the mysql driver to each host website directory).
Then run cobalt_config.pl script and view the file
/usr/java/jakarta-3.2.3/conf/tomcat.policy to see
the result without impacting the webserver.
Once the tomcat.policy file looks fine, you can restart
tomcat to try the effect. Tweak the cobalt_config.pl
if you want the policy file generated differently (e.g.,
I currently only support tomcat on one site rather than
all sites).
---------------------------------------------------
DuoMark International, Inc.
6523 Colgate Avenue, Suite 325
Los Angeles, CA 90048-4410 / USA
Voice: +1 323 381-0002
FAX: +1 323 549 0172
Email: jay@xxxxxxxxxxx
WWW: http://www.duomark.com/