Oracle® Fusion Middleware

Creating Domain Templates Using the Domain Template Builder

Release 12.2.1.1

E74871-01

June 2016

This document describes how to use the Domain Template Builder to create WebLogic domain and extension templates.

Oracle Fusion Middleware Creating Domain Templates Using the Domain Template Builder, Release 12.2.1.1

E74871-01

Copyright © 2016, 2016, Oracle and/or its affiliates. All rights reserved.

Primary Authors: Geetha Savithriamma, Peter LaQuerre

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Documentation Accessibility

- Related Documents

- Conventions

1 Introduction

- 1.1 Overview of the Domain Template Builder

- 1.2 About Domain and Extension Templates

- 1.3 Additional Tools for Creating Templates

2 Using the Domain Template Builder to Create Domain Templates

- 2.1 Starting the Domain Template Builder

- 2.2 Creating Domain Templates Using the Domain Template Builder

- 2.3 Porting Security Provider Data to a New Domain

3 Creating Extension Templates by Using the Domain Template Builder

- 3.1 Starting the Domain Template Builder

- 3.2 Creating an Extension Template Using the Domain Template Builder

4 Domain Template Builder Screens

- 4.1 Template Type

- 4.1.1 Creating a Domain Template From an Existing Domain

- 4.1.2 Creating an Extension Template From an Existing Domain

- 4.1.3 Creating a Domain Template From an Existing Template

- 4.1.4 Creating an Extension Template From an Existing Template

- 4.2 Template Information

- 4.3 Services Selection

- 4.4 Topology Selection

- 4.5 Template Summary

- 4.6 Configuration Progress

- 4.7 End of Configuration

Preface

This preface describes the document accessibility features and conventions used in this guide–Creating Domain Templates Using the Domain Template Builder.

- Documentation Accessibility

- Related Documents

- Conventions

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

You can access the documents referenced in this guide on Oracle Technology Network at http://www.oracle.com/technology:

- Creating WebLogic Domains Using the Configuration Wizard

- Creating Templates and Domains Using the Pack and Unpack Commands

- Creating Domain Templates Using the Domain Template Builder

- Domain Template Reference

- WLST Command Reference for WebLogic Server

- Understanding the WebLogic Scripting Tool

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Introduction

This chapter provides an overview of how to create templates in WebLogic Server by using the Domain Template Builder.

This chapter includes the following sections:

- Overview of the Domain Template Builder

- About Domain and Extension Templates

- Additional Tools for Creating Templates

1.1 Overview of the Domain Template Builder

You can create WebLogic domains by using domain and extension templates that contain the key attributes and files required for building or extending a WebLogic domain. To create domain or extension templates, you use the Domain Template Builder, which is a standalone Java application that guides you through the process. This process is illustrated in Figure 1-1.

Figure 1-1 Domain Template Builder

The Domain Template Builder is designed to be used off-line in graphical mode. It is not supported in console mode. Therefore, the console attached to the machine on which you are using the Domain Template Builder must support Java-based GUIs. All consoles for Windows systems support Java-based GUIs; some UNIX-based consoles support Java-based GUIs.

Your product installation includes a set of predefined domain and extension templates. This set of templates includes the WebLogic Server Base Domain template, and various extension templates that allow you to add product features and samples to the base domain. For more information on the templates that are available for various products, see the Domain Template Reference.

After you create your domain and add new resources and applications to it, you can use the Domain Template Builder to create a domain and extension templates. To do so, select the existing domain or template as the source for your new domain or extension templates. When your custom domain templates are complete, you can use them to create domains by using the Configuration Wizard, WLST Offline, or the unpack command. For more information about these tools, see Additional Tools for Creating Templates.

1.2 About Domain and Extension Templates

In the context of the Domain Template Builder, the term template refers to a Java Archive (JAR) file. A template JAR contains the files and scripts that are needed to create or extend a WebLogic domain. The types of templates that can be used by the Configuration Wizard to create or extend domains include:

- Domain template—defines the full set of resources within a WebLogic domain, including infrastructure components, applications, services, security options, and general environment and operating system options. You can create this type of template from an existing domain by using the Domain Template Builder or the pack command. You can then create a domain based on the template.
The product distribution includes the WebLogic Server Base Domain template. This template defines the core set of resources within a domain, including an Administration Server and basic configuration information, infrastructure components, and general environment and operating system options. It does not include sample applications. You can use this template to create a basic WebLogic Server domain, which you can then extend with applications and services, or additional product component functionality.

- Extension template—defines applications and services that can provide additional features, such as applications, or JDBC resources, JMS components, or deployed libraries. This type of template can be used to update an existing WebLogic domain.

- Managed Server template—defines the subset (within a domain) of resources that are required to create a Managed Server domain on a remote machine. This type of template can be created using the pack command.

Your product installation includes a set of predefined domain and extension templates. This set includes the WebLogic Server Base Domain template and various extension templates that allow you to add component features and samples to the base domain. For more information about these templates and how they relate to each other, see the Domain Template Reference.

1.3 Additional Tools for Creating Templates

As described earlier, you can create custom domain and extension templates by using the Domain Template Builder. You can also use the following tools to create templates:

- pack
This command enables you to create a template archive (JAR file) that contains a snapshot of either an entire WebLogic domain or a subset of a WebLogic domain. You can use a template that contains a subset of a domain to create a Managed Server domain directory hierarchy on a remote machine.

For more information, see Creating Templates and Domains Using the Pack and Unpack Commands.

- WebLogic Scripting Tool (WLST):
WLST is a command-line scripting interface, which you can use to interact with and configure WebLogic Server instances and domains. When WLST is offline, you can create a WebLogic domain or update an existing WebLogic domain without connecting to a running WebLogic Server—supporting the same functionality as the Configuration Wizard.

For more information, see Understanding the WebLogic Scripting Tool and WLST Command Reference for WebLogic Server.

2 Using the Domain Template Builder to Create Domain Templates

This chapter describes how to create a domain template using the Domain Template Builder.

- Starting the Domain Template Builder

- Creating Domain Templates Using the Domain Template Builder

- Porting Security Provider Data to a New Domain

2.1 Starting the Domain Template Builder

The console for the machine on which the product installation resides must support Java-based GUIs. All Windows-based consoles support Java-based GUIs; only a subset of UNIX-based consoles support Java-based GUIs.

You can start the Domain Template Builder in graphical mode from the command line.

1. Log in to the system on which the product is installed.

2. Open an MS-DOS command prompt window (on Windows) or a command shell (on UNIX).

3. Go to the following directory, where ORACLE_HOME is the Oracle home directory that you specified when installing WebLogic Server:

Windows: ORACLE_HOME\oracle_common\common\bin

UNIX: ORACLE_HOME/oracle_common/common/bin

4. Execute the following command:

Windows: config_builder.cmd

UNIX: config_builder.sh

Note:

When you run the config_builder.cmd or config_builder.sh command, the following error message might be displayed to indicate that the default cache directory is not valid:

*sys-package-mgr*: can't create package cache dir

You can change the cache directory by including the -Dpython.cachedir=valid_directory option in the command line.

The Template Type screen is displayed.

2.2 Creating Domain Templates Using the Domain Template Builder

To create a new domain template using the Domain Template Builder in graphical mode, start the Domain Template Builder as described in Starting the Domain Template Builder.

Note:

In situations where you cannot run the Domain Template Builder in GUI mode, Oracle recommends that you use a WLST script to create the domain template. For more information, see Creating and Using a Domain Template (Offline) in Understanding the WebLogic Scripting Tool.

The Domain Template Builder displays a sequence of screens, in the order listed in Table 2-1. For more information on each screen, refer to the related section in Domain Template Builder Screens, or click the link in the Screen column.

Table 2-1 summarizes the steps for creating a domain template by using the Domain Template Builder.

Table 2-1 Steps for Creating a Domain Template by Using the Domain Template Builder

Screen

When Does This Screen Appear?

You Perform This Action

Template Type

Always

Choose Create a Domain Template to create a domain template.

Specify the source for the domain template and the location of the source.

Specify the destination JAR file for the domain template.

Click Next to continue.

Template Information

Always

Fill in each template information field.

Click Next to continue.

Template Summary

Always

Review the template summary. You can use the View drop-down list to restrict the view to a specific part of the template.

If necessary, click Back to return to a previous screen and make changes.

Click Create to continue.

Configuration Progress

Always

Wait for the template to be generated, and then click Next.

End of Configuration

Always

Click Finish to exit the Domain Template Builder.

2.3 Porting Security Provider Data to a New Domain

Because it is an offline utility, the Template Builder does not export security provider data, such as embedded LDAP data, into a domain template. After using the domain template to create the new domain, you must manually port the security provider data to the new domain. To do so:

1. If necessary, start the Administration Server for the original domain and log in to the original domain's Administration Console.

2. Export the data from the original domain as described in Export data from a security provider in the Oracle WebLogic Server Administration Console Online Help.

3. If necessary, start the Administration Server for the new domain and log in to the new domain's Administration Console.

4. Import the data into the new domain as described in Import data into a security provider in the Oracle WebLogic Server Administration Console Online Help.

3 Creating Extension Templates by Using the Domain Template Builder

This chapter describes how to create an extension template using the Domain Template Builder.

The process for creating an extension template is similar to the process for creating a domain template. The resulting template does not configure the Administration Server, administrator username and password, security realm, and Node Manager, or specify Start menu entries. These domain settings are already defined in the domain you are extending.

This chapter includes the following sections:

- Starting the Domain Template Builder

- Creating an Extension Template Using the Domain Template Builder

3.1 Starting the Domain Template Builder

The console for the machine on which the product installation resides must support Java-based GUIs. All Windows-based consoles support Java-based GUIs; only a subset of UNIX-based consoles support Java-based GUIs.

You can start the Domain Template Builder in graphical mode from the command line.

1. Log in to the system on which the product is installed.

2. Open an MS-DOS command prompt window (on Windows) or a command shell (on UNIX).

3. Go to the following directory:

On Windows: ORACLE_HOME\oracle_common\common\bin

On UNIX: ORACLE_HOME/oracle_common/common/bin

4. Execute the following command:

On Windows: config_builder.cmd

On UNIX: config_builder.sh

Note:

When you run the config_builder.cmd or config_builder.sh command, the following error message might be displayed to indicate that the default cache directory is not valid:

*sys-package-mgr*: can't create package cache dir

You can change the cache directory by including the -Dpython.cachedir=valid_directory option in the command line.

The Template Type screen is displayed.

3.2 Creating an Extension Template Using the Domain Template Builder

To create a new extension template using the Domain Template Builder in graphical mode, start the Domain Template Builder as described in Starting the Domain Template Builder. Then select the Create Extension Template option to display the Create Extension Template screen (similar to the Template Type screen).

Note:

In situations where you cannot run the Domain Template Builder in GUI mode, Oracle recommends that you use a WLST script to create the extension template. For more information, see Creating and Using a Domain Template (Offline) in Understanding the WebLogic Scripting Tool.

The Domain Template Builder displays a sequence of screens, in the order listed in Table 3-1. For more information on each screen, refer to the related section in Domain Template Builder Screens, or click the link in the Screen column.

Table 3-1 Steps for Creating an Extension Template by Using the Domain Template Builder

Screen

When Does This Screen Appear?

You Perform This Action

Template Type

Always

Choose Create Extension Template to create an extension template.

Specify the source for the extension template and location of the source.

Specify the destination JAR file for the extension template.

Click Next to continue.

Template Information

Always

Update each template information field as needed.

Click Next to continue.

Services Selection

Only if you create an extension template

Select the custom applications and services that you want to include in the extension template.

Click Next to continue.

Topology Selection

Only if you create an extension template and the selected source (domain or template) has topology information

From the topology elements listed for the configuration, select the elements you want to include in the extension template.

Template Summary

Always

Review the template summary. You can use the View drop-down list to restrict the view to a specific part of the template.

If necessary, click Prev to return to a previous screen and make any changes that are needed.

Click Create to continue.

Configuration Progress

Always

Wait for the template to be generated, then click Next.

End of Configuration

Always

Click Finish to exit the Domain Template Builder.

4 Domain Template Builder Screens

This chapter describes each of the Domain Template Builder screens.

This chapter includes the following sections:

- Template Type

- Template Information

- Services Selection

- Topology Selection

- Template Summary

- Configuration Progress

- End of Configuration

4.1 Template Type

Use this page to specify whether or not you want to create a domain template or an extension template, and then specify the source and destination for the new template.

Option

Description

Create Domain Template

Select this option to create a new domain template that defines the full set of resources within a WebLogic domain, including infrastructure components, applications, services, security options, and general environment and operating system parameters.

You can use the template that you create as the basis for creating a WebLogic domain, by specifying the template in the Configuration Wizard, WLST, or the unpack command.

Create Extension Template

Select this option to create a template that defines applications and services that can be used to extend existing WebLogic domains.

You can import applications and services stored in extension templates into an existing WebLogic domain by using the Configuration Wizard.

For information about the Configuration Wizard, see Creating WebLogic Domains Using the Configuration Wizard

- Creating a Domain Template From an Existing Domain

- Creating an Extension Template From an Existing Domain

- Creating a Domain Template From an Existing Template

- Creating an Extension Template From an Existing Template

4.1.1 Creating a Domain Template From an Existing Domain

To create a domain template from an existing domain directory:

1. Select Create Domain Template.

2. Select Use Domain as a Source.

3. Enter the full path of the source domain directory in the Source Location field, or use the Browse button to navigate to the domain directory (for example, C:\domains\mydomain).

4. In the Template Location field, enter the full path and JAR file name for the new template, or use the Browse button to navigate to an existing directory. Ensure that you include the JAR file name, for example, C:\templates\domains\mynewtemplate.jar.

5. Click Next to continue.

4.1.2 Creating an Extension Template From an Existing Domain

To create an extension template from an existing domain directory:

1. Select Create Extension Template.

2. Select Use Domain as a Source.

3. Enter the full path of the source domain directory in the Source Location field, or use the Browse button to navigate to the domain directory (for example, C:\domains\mydomain).

4. In the Template Location field, enter the full path and JAR file name for the new template, or use the Browse button to navigate to an existing directory. Ensure that you include the JAR file name, for example, C:\templates\domains\mynewtemplate.jar.

5. Click Next to continue.

4.1.3 Creating a Domain Template From an Existing Template

To create a domain template from an existing template:

1. Select Create Domain Template.

2. Select Use Template as a Source.

3. Enter the full path of the source domain JAR file in the Source Location field, or use the Browse button to navigate to the domain directory and select the JAR file (for example, C:\domains\mydomain.jar).

4. In the Template Location field, enter the full path and JAR file name for the new template, or use the Browse button to navigate to an existing directory. Ensure that you include the JAR file name, for example, C:\templates\domains\mynewtemplate.jar.

5. Click Next to continue.

4.1.4 Creating an Extension Template From an Existing Template

To create an extension template from an existing template:

1. Select Create Extension Template.

2. Select Select Template Source.

3. Enter the full path of the source application JAR file in the Select Source Location field, or use the Browse button to navigate to the application directory and select the jar file (for example, C:\applications\myapplication.jar).

4. In the Select Template Location field, enter the full path and JAR file name for the new template, or use the Browse button to navigate to an existing directory. Ensure that you include the JAR file name, for example, C:\templates\applications\mynewapplication.jar.

5. Click Next to continue.

4.2 Template Information

Use this screen to provide basic information about the template. The information you enter here is stored in the template-info.xml file that is generated for the domain or extension template. It is also stored in the config.xml file for the domain.

When you select a domain or a template as the source for the new or extension template, information about the selected template is displayed. Review the information, and, if necessary, change it to suit the requirements of your domain or extension template. When done, click Next

Field

Description

Name

Required. Enter a valid name for the template. The name must be a string of characters, and can include spaces.

Version

Required. Enter a version number for the template. The version number can be anything you want, as long as it contains four or five digits, for example, 12.1.2.0 or 12.1.2.0.0.

Author

Optional. Enter the name of the author of the template.

Description

Optional. Enter a detailed description of the template. The description must be a string of characters, and can include spaces.

4.3 Services Selection

The Services Selection screen is available only if you are creating an extension template. Use this screen to review the custom applications and services in the configuration, and then select the ones you want to include in the extension template.

By default, the Domain Template Builder includes only the custom applications and services from the WebLogic domain or template you specified as the source for the extension template.

Expand each application or service to view its contents. Select an item from the list and review the associated details on the Description pane on the right. After reviewing, select the elements you want to include in the extension template.

When done, click Next to continue.

4.4 Topology Selection

The Topology Selection screen is available only if you are creating an extension template. Use this screen to review the topology elements in the configuration and select the elements you want to include in the extension template.

By default, the Domain Template Builder includes all the topology elements from the WebLogic domain or template you specified as the source for the extension template.

Expand each topology element to view its contents. Select an element from the list and review the associated details on the Description pane on the right. After reviewing, select the files you want to include in the extension template.

When done, click Next to continue.

4.5 Template Summary

Use the Template Summary screen to review the settings for the new template before it is created.

1. Select an item in the Template Summary pane on the left and review the associated details in the Details pane on the right. If you need to change any settings that you defined in previous windows, click Back to return to the required configuration window.

Note:

You can limit the type of information displayed in the Template Summary screen by using the View drop-down list.

2. Click Create.

The Configuration Progress screen is displayed.

4.6 Configuration Progress

The Configuration Progress screen displays status messages during the template creation process. The Domain Template Builder generates a JAR file that contains all the components required to generate a new WebLogic domain, including the template settings that you provided.

When the process completes, click Finish.

The files included in a template vary, depending on the WebLogic domain or template on which the template is based.

For more information, see Files Typically Included in a Template in the Domain Template Reference.

4.7 End of Configuration

This screen displays the final configuration status.

- If the template was created successfully, a link to the template JAR file is provided under Template Location.

- If the template was not created successfully, an error message and an error code are displayed. In this case, try to determine the cause of the failure from the message and correct the issue.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2018, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.