Skip navigation.
Downloads | Product Documentation | Support

Policy Managers Guide

# About this Document

This section covers the following topics:

- Audience for this Guide
- Prerequisites for this Guide
- How this Document is Organized
- Product Documentation on the dev2dev Web Site
- Related Information
- Contact Us!

# Audience for this Guide

This document is intended for application developers who are tasked with developing security policies using the BEA WebLogic Enterprise Security products and security administrators who are implementing the policy. The reader should also be familiar with the policy model used by BEA WebLogic Enterprise Security and described in the Introduction to BEA WebLogic Enterprise Security.

The audiences for this document include:

- Application developers—Application developers should be familiar with the business policies for their company, including access rules and privileges granted or denied to users of the applications and resources.
- Security administrators—Security Administrators have a general knowledge of security concepts. They can identify security events in server and audit logs. They are tasked with implementing security policy, configuring security providers, and implementing authentication, authorization, role mapping, credential mapping, auditing and failover policies.

# Prerequisites for this Guide

Prior to reading this guide, you should read the Introduction to BEA WebLogic Enterprise Security. This document describes how the product works and provides conceptual information that is helpful to understanding the necessary installation components.

Additionally, BEA WebLogic Enterprise Security includes many unique terms and concepts that you need to understand. These terms and concepts—which you will encounter throughout the documentation—are defined in the Glossary.

# How this Document is Organized

This document is organized as follows:

- This chapter provides general information about audiences and available information.
- Modeling Policies,discusses what a policy is and describes how to design your policies.
- Defining Rules, describes how to write rules to enforce your policy.
- Creating Policy Data Files, describes how to write your policy data.
- Importing Policy Data, details how to import policy data into the database.
- Exporting Policy Data, details how to export policy data from the database.

# Product Documentation on the dev2dev Web Site

BEA product documentation, along with other information about BEA software, is available from the BEA dev2dev web site:

http://dev2dev.bea.com

To view the documentation for a particular product, select that product from the Product Centers menu on the left side of the screen on the dev2dev page. Select More Product Centers. From the BEA Products list, choose WebLogic Enterprise Security 4.2. The home page for this product is displayed. From the Resources menu, choose Documentation 4.2. The home page for the complete documentation set for the product and release you have selected is displayed.

# Related Information

The BEA corporate web site provides all documentation for BEA WebLogic Enterprise Security. Other BEA WebLogic Enterprise Security documents that may be of interest to the reader include:

- Introduction to BEA WebLogic Enterprise Security—This document provides an overview, and conceptual and architectural information for the BEA WEbLogic Enterprise Security products.
- BEA WebLogic Enterprise Security Administration Guide—This document provides a complete overview of the product and includes step-by-step instructions on how to perform various administrative tasks.
- Programming Security for Java Applications—This document describes how to implement security in Java applications. It include descriptions of the security service Application Programming Interfaces (API) and programming instructions for implementing security in Java applications.
- Programming Security for Web Services—This document describes how to implement security in web server applications. It include descriptions of the Web Services Application Programming Interfaces (API) and programming instructions for implementing security in web server applications.
- Developing Security Providers for BEA WebLogic Enterprise Security —This document provides security vendors and security and application developers with the information needed to develop custom security providers.
- Javadocs for Java API—The Javadocs provide reference material for the Java Application Programming Interfaces (API) that are provided with and supported by this release of BEA WebLogic Enterprise Security.
- Wsdldocs for Web Services API—The Wsdldocs provide reference material for the Web Services API that are provided with and supported by this release of BEA WebLogic Enterprise Security.
- Javadocs for the Business Logic Manager API—The javadocs for the Business Logic Manager (BLM) provide reference material for the BLM API. The BLM can be used to define security policy which can then be deployed using the Administration Console.
- Javadocs for Security Service Provider Interfaces—The Javadocs provide reference material for the Security Service Provider Interfaces (SSPI) that are provided with and supported by this release of BEA WebLogic Enterprise Security.

# Contact Us!

Your feedback on BEA documentation is important to us. Send us e-mail at docsupport@bea.com if you have questions or comments. Your comments will be reviewed directly by the BEA professionals who create and update the documentation.

In your e-mail message, please indicate the software name and version you are using, as well as the title and document date of your documentation. If you have any questions about this version of BEA WebLogic Enterprise Security, or if you have problems installing and running BEA WebLogic Enterprise Security, contact BEA Customer Support through BEA WebSupport at http://www.bea.com. You can also contact Customer Support by using the contact information provided on the Customer Support Card, which is included in the product package.

When contacting Customer Support, be prepared to provide the following information:

- Your name, e-mail address, phone number, and fax number
- Your company name and company address
- Your machine type and authorization codes
- The name and version of the product you are using
- A description of the problem and the content of pertinent error messages