Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Karen Lilly Creations

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 79 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here






       The  policy  for  a Java runtime (specifying which permis­
       sions are available for code from  various  sources,  when
       executing  as various principals) is represented by a Pol­
       icy object. The default Policy implementation obtains  its
       information  from static ASCII policy configuration files.

       A policy file can be composed via a simple text editor, or
       via  the  graphical  Policy  Tool  utility described here.
       Using the Policy Tool saves typing and eliminates the need
       for  you  to  know  the  required  policy file syntax thus
       reducing errors.

   Starting Policy Tool
       To start Policy Tool, simply type  the  following  at  the
       command line.


       This brings up the "Policy Tool" window.

       Whenever  Policy Tool is started, it tries to fill in this
       window with policy  information  from  what  is  sometimes
       referred  to  as  the  "user policy file". The user policy
       file is by default a file named .java.policy in your  home
       directory.  If  Policy  Tool  cannot  find the user policy
       file, it reports the situation and displays a blank  "Pol­
       icy Tool" window (that is, a window with headings and but­
       tons but no data in it).

       You can then proceed to either open whatever  policy  file
       you want to work on or create a new policy file, by adding
       policy entries, optionally specifying a keystore, and sav­
       ing the file).

       The  first time you run the Policy Tool, there will not be
       a user policy file (unless you created one manually).

   Creating a new Policy File
       To create a new policy file, start by simply selecting the
       New  command  from the File menu. This will close the cur­
       rently open policy file (if any, after first prompting you
       to  save it if needed) and bring up a new policy tool win­
       dow, that is, a window with headings and  buttons  but  no
       data in it.

       Please  Note: this is not necessary the first time you run
       the Policy Tool. Since the tool tries  to  open  the  user
       This will close the currently open policy  file  (if  any,
       after  first  prompting you to save it if needed) and will
       present you with an Open dialog, which you can use to nav­
       igate  the directory structure until you get to the direc­
       tory containing the policy  file  you  want  to  work  on.
       Select that file, then select the OK button.

       The  "Policy  Tool"  window  will  then  be filled in with
       information from the policy  file,  including  the  policy
       file  name,  the  keystore URL (if any), and the CodeBase,
       SignedBy and Principal parts of each policy entry  in  the
       policy file.

   Specifying the Keystore
       To specify the keystore containing the key information for
       the aliases specified in  the  SignedBy  parts  of  policy
       entries,  select  the  Change Keystore command in the Edit

       This brings up a dialog box in which you specify  the  new
       keystore URL and optionally the keystore type.

       As  an example, to specify the keystore named "mykeystore"
       in the /tests/ directory, type  the  following  file:  URL
       into the text box labeled "New KeyStore URL".


       To  also specify that the keystore type is "JKS" (the pro­
       prietary keystore type  supported  by  Sun  Microsystems),
       type the following into the text box labeled "New KeyStore


       When you are done specifying the keystore URL and type (if
       any),  select  OK  (or you can select Cancel to cancel the
       operation). If you didn't cancel,  the  text  box  labeled
       "Keystore:"  is  now  filled  in with the keystore URL and

   Adding a New Policy Entry
       To add a new policy entry, select  the  Add  Policy  Entry
       button  in the main "Policy Tool" window. This brings up a
       "Policy Entry" dialog box.

       Using this dialog box, you specify

       ·      an optional CodeBase entry indicating the URL loca­
              tion  where  the code originates from. For example,
              to indicate code from  the  local  /JavaSoft/TESTS/
              directory,  type  the  following  file URL into the
              order for the  permission(s)  to  be  granted.  See
              Adding a New Principal.

       ·      one  or  more  permission  entries indicating which
              permissions are granted to the code from the source
              indicated  by  the CodeBase and SignedBy values (or
              to any code if no such values are  specified)  when
              running  as the specified principals in the Princi­
              pals list. See Adding a New Permission.

   Editing a Policy Entry
       To edit an existing policy entry, select the line for that
       entry  in  the  main "Policy Tool" window, then select the
       Edit Policy Entry button. Alternatively,  you  can  simply
       double-click the line for that entry.

       This  brings up the same type of "Policy Entry" dialog box
       as appears when you are adding a new policy entry,  except
       in this case the dialog box is filled in with the existing
       policy entry information. To change the information,  sim­
       ply  retype  it  (for the CodeBase and SignedBy values) or
       use the buttons (for the Principals and  Permissions  val­

       When  you  are  done, select the Done button (or Cancel to

   Removing a Policy Entry
       To delete a policy entry from the policy file, select  the
       line for that entry in the main "Policy Tool" window, then
       select the Remove Policy Entry button.

       The complete policy entry is displayed, and you  can  then
       either  select  OK  to remove the entry, or Cancel to keep

   Saving the Policy File
       To save changes to an existing policy file, simply  select
       the Save command in the File menu.

       To save a new policy file you've been creating, or to copy
       an existing policy file to a new policy file with  a  dif­
       ferent  name,  select  the  Save  As command from the File
       menu. This brings up the Save As dialog box.

       Navigate the directory structure to get to  the  directory
       in  which  you  want  to  save  the  policy file. Type the
       desired file name, then select the OK button.  The  policy
       file  is now saved, and its name and path are shown in the
       text box labeled "Policy File:"


       More  extensive  documentation for PolicyTool is available
       online                                                  at

                           17 July 2001             policytool(1)



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
The Linux Tutorial can use your help.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.10 Seconds