PK :zDoa,mimetypeapplication/epub+zipPK:zDiTunesMetadata.plistO artistName Oracle Corporation book-info cover-image-hash 498970722 cover-image-path OEBPS/dcommon/oracle-logo.jpg package-file-hash 530681591 publisher-unique-id E28064-01 unique-id 134505721 genre Oracle Documentation itemName Oracle® Fusion Middleware Domain Template Reference, 12c (12.1.2) releaseDate 2013-06-03T13:04:43Z year 2013 PKTOPK:zDMETA-INF/container.xml PKYuPK:zDOEBPS/cover.htm  Cover

Oracle Corporation

PK@t` PK:zDOEBPS/title.htmQ Oracle Fusion Middleware Domain Template Reference, 12c Release 1 (12.1.2)

Oracle® Fusion Middleware

Domain Template Reference

12c Release 1 (12.1.2)

E28064-01

June 2013

This document provides information about WebLogic domain and extension templates, which are Java archive (JAR) files that contain the files and scripts required to create or extend a WebLogic domain.


Oracle Fusion Middleware Domain Template Reference, 12c Release 1 (12.1.2)

E28064-01

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

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, 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 failsafe, 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 on 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. 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.

PKFPK:zDOEBPS/fmw_templates.htm Fusion Middleware Product Templates

3 Fusion Middleware Product Templates

This chapter describes the WebLogic domain and extension templates that are used to configure WebLogic domains for various Fusion Middleware product installations. For most of these templates, you can create or extend domains by selecting the template on the Templates screen of the Oracle Fusion Middleware Configuration Wizard. You can also use the WebLogic Scripting Tool (WLST) in offline mode to create or extend domains using these templates. See Template Tools, for more information.

Your product installation includes only those templates that are relevant to your product. Some templates in this chapter, such as the Oracle JRF template, apply to domains for multiple Fusion Middleware products. Other templates apply only to domains for a single Fusion Middleware product, and are therefore not included with any other Fusion Middleware product installations.

This chapter contains the following sections:

Each template section contains the following template information:

Oracle JRF and ADF Templates

This section describes templates that add necessary resources to many of the Fusion Middleware product domains. The following templates are described here:


Note:

The templates described in this section must be used as provided. Do not modify them in any way. Doing so can cause issues in your domain.


Oracle JRF Template

The Oracle Java Required Files (JRF) template configures components that are not included in the WebLogic Server installation. These components provide common functionality for Oracle business applications and application frameworks. The SOA Suite and WebCenter are examples of applications and frameworks that depend on the JRF template.

The JRF template is also used independently to configure domains that contain applications that are developed using Oracle ADF and other core components.

The following table provides key information about this template.

Table 3-1 Oracle JRF Template Details

Template DetailInformation

Template type

Extension

Category

Oracle

Template name and version

Oracle JRF - 12.1.2.0

Template Dependencies

  • Oracle Click History - 12.1.2

  • WebLogic Coherence Cluster Extension - 12.1.2.0

  • Oracle WSM Agent - 12.1.2.0

  • Oracle ADF and MDS Extensions for JRF - 12.1.2.0

  • Oracle OPSS Metadata for JRF - 12.1.2.0

  • Oracle User Messaging Service Client Extensions for JRF - 12.1.2.0

  • Common Infrastructure Engineering Runtime - 12.1.2.0

Template JAR file and location

ORACLE_HOME/oracle_common/common/templates/wls/oracle.jrf_template_12.1.2.jar


Oracle JRF Asynchronous Web Services Template

The Oracle JRF Asynchronous Web Services template creates default JMS resources that are required for JRF Asynchronous Web Services running on a WebLogic Server domain. This template does not create the JMS UDDs (Uniform Distributed Destinations) required for clusters in the domain. To create the default JMS UDDs, a separate WLST script, jrfws-async-createUDDs.py, is provided.

This template must be targeted to non-clustered servers in the domain.

The following table provides key information about this template.

Table 3-2 Oracle JRF Asynchronous Web Services Template Details

Template DetailInformation

Template type

Extension

Category

Oracle

Template name and version

Oracle JRF Web Services Asynchronous Services - 12.1.2.0

Template Dependencies

Oracle JRF - 12.1.2.0

Template JAR file and location

ORACLE_HOME/oracle_common/common/templates/wls/oracle.jrf.ws.async_template_12.1.2.jar


Oracle JRF SOAP/JMS Web Services Template

This template creates JMS queues for JRF SOAP/JMS Web services.

Table 3-3 Oracle JRF Asynchronous Web Services Template Details

Template DetailInformation

Template type

Extension

Category

Oracle

Template name and version

Oracle JRF SOAP/JMS Web Services - 12.1.2.0

Template Dependencies

Oracle JRF - 12.1.2.0

Template JAR file and location

ORACLE_HOME/oracle_common/common/templates/wls/oracle.jrf.ws.soapjms_template_12.1.2.jar


Oracle OPSS Extensions for JRF

This template is required for Fusion Middleware components and applications that were built using Oracle Application Development Framework.

The following table provides key information about this template.

Table 3-4 Oracle OPSS Extensions for JRF Template Details

Template DetailInformation

Template type

Extension

Template name and version

Oracle OPSS Extensions for JRF - 12.1.2.0

Template Dependencies

Oracle JRF - 12.1.2.0

Template JAR file and location

ORACLE_HOME/oracle_common/common/templates/wls/oracle.opss_template_12.1.2.jar


Oracle ADF Development Mode Logging

This template is included if Oracle JDeveloper is installed. It provides development mode logging for Oracle ADF. Fine logging for oracle.jbo is exposed.

The following table provides key information about this template.

Table 3-5 Oracle ADF Development Mode Logging Template Details

Template DetailInformation

Template type

Extension

Template name and version

Oracle ADF Development Mode Logging - 12.1.2.0.0

Template Dependencies

None

Template JAR file and location

ORACLE_HOME/jdeveloper/common/templates/jdeveloper/adf.fine.logging_12.1.2.jar


Enterprise Manager Templates

This section describes the Enterprise Manager templates that are used to add Enterprise Manager resources to the WebLogic domains for various Fusion Middleware products. There are currently three Enterprise Manager JAR files, all of which are installed when you select the product on the Templates screen of the Fusion Middleware Configuration Wizard.

Oracle Enterprise Manager

This template adds Oracle Enterprise Manager Fusion Middleware Control to your domain. Fusion Middleware Control is a Web browser-based, graphical user interface that you can use to monitor and administer Oracle Fusion Middleware.

Together with the Oracle WebLogic Server Administration Console, Fusion Middleware Control provides tools to help you manage the Oracle Fusion Middleware environment, including the Oracle WebLogic Server domain, the Oracle Fusion Middleware components you have installed and configured, and the applications you deploy.

For more complete information about Oracle Enterprise Manager Fusion Middleware Control, see "Getting Started Using Oracle Enterprise Manager Fusion Middleware Control" in the Administering Oracle Fusion Middleware.


Note:

This template must be used as provided. Do not modify it in any way. Doing so can cause issues in your domain.


The following table provides key information about this template.

Table 3-6 Oracle Enterprise Manager Template Details

Template DetailInformation

Template type

Extension

Template name and version

Oracle Enterprise Manager - 12.1.2.0

Template Dependencies

  • Basic WebLogic Server Domain

  • + Oracle JRF - 12.1.2.0

  • + Oracle WebCenter Composer

Template JAR file and location

This template consists of multiple template JAR files. These JAR files are located in the following directory after you install Oracle Fusion Middleware:

ORACLE_HOME/em/common/templates/wls

The template consists of the following JAR files in the templates directory:

  • oracle.em_wls_template_12.1.2.jar

  • oracle.emas_wls_template_12.1.2.jar


Coherence Template

This section describes the Coherence template that is provided when Coherence is installed with WebLogic Server.

WebLogic Coherence Cluster Extension Template

This template adds a default Coherence cluster, defaultCoherenceCluster, to the WebLogic domain and sets the listen port for the cluster to 8088.

Table 3-7 WebLogic Coherence Cluster Extension Template Details

Template DetailInformation

Template type

Extension Template

Template name and version

WebLogic Coherence Cluster Extension - 12.1.2.0

Template Dependencies

  • Basic WebLogic Server Domain

Template JAR file and location

WL_HOME/common/templates/applications/wls_coherence.jar


Oracle Web Service Manager (OWSM) Templates

This section describes the OWSM template that is provided for adding OWSM resources to various Fusion Middleware product domains. There is currently one OWSM template available, as described in Oracle WSM Policy Manager Template.


Note:

The templates described in this section must be used as provided. Do not modify them in any way. Doing so can cause issues in your domain.


Oracle WSM Policy Manager Template

The WSM PM template is used to deploy and configure the WSM Policy Manager Java EE application.

The following table provides key information about this template.

Table 3-8 Oracle WSM Policy Manager Template Details

Template DetailInformation

Template type

Extension

Template name and version

Oracle WSM Policy Manager - 12.1.2.0

Template Dependencies

  • Basic WebLogic Server Domain

  • + Oracle JRF - 12.1.2.0

Template JAR file and location

ORACLE_HOME/oracle_common/common/templates/wls/oracle.wsmpm_template_12.1.2.jar


Oracle Virtual Assembly Builder Templates

This section describes the following Oracle Identity Management (IDM) templates:

Oracle Virtual Assembly Builder Template

With the expanded domain topology profile, this template provides a domain type that supports the Oracle Virtual Assembly Builder Deployer cluster service, and allows you to configure an Oracle WebLogic Server cluster and a Coherence cluster and target the Oracle WebLogic Server cluster to use the Coherence cluster.

You can configure the Coherence cluster with either Well Known Addresses (WKA) or multicast communication. If you do not specify a communication type, WKA is set as for cluster communication.

Oracle Virtual Assembly Builder Deployer uses Coherence cluster data partitioning to distribute work. The deployerId is used as a key association, where all data specific to a particular deployment id is guaranteed to exists on the same node. When you initiate an asynchronous request (such as a deploy, undeploy, or scale operation), the request is handled by the node on which the data is partitioned at that time. The same node handles the request even if data gets repartitioned to another node.

If a node with running requests goes down or crashes, the requests are cancelled, because none of the Deployer asynchronous operations are idempotent. That is, if a request is initiated, it cannot be rolled back because the work is distributed amongst multiple tiers.

You must re-initiate such requests by cleaning up the previous state. For example: if a deploy operation gets cancelled, the corresponding deployment object is marked as 'Failed' with the reason as 'cancelled'. You must invoke an explicit cleanup operation by the to cleanup the deployment, then create another deployment object and start the deploy operation.

With the compact domain topology profile, this template provides for a standalone Oracle Virtual Assembly Builder Deployer.

The following table provides key information about this template.

Table 3-9 Oracle Virtual Assembly Builder Template Details

Template DetailInformation

Template type

Extension

Category

Uncategorized

Template name and version

Oracle Virtual Assembly Builder Deployer - 12.1.2.0

Template Dependencies

Oracle JRF - 12.1.2.0

Template JAR file and location

OVAB_HOME/common/templates/wls/oracle.ovab.deployer.template_12.1.2.jar

Domain topology profiles

Compact and Expanded


Oracle Data Integrator Templates

This section describes the following Oracle Data Integrator templates:


Note:

The ODI Master Datasource template, the ODI Base template, and the ODI Work Datatsource template, which are listed as dependencies for other Oracle Data Integrator templates, are internal templates. They are automatically called when you select other ODI templates in Configuration Wizard, or specify an ODI template in a WLST script. Therefore, they are not displayed as selectable components in Configuration Wizard, and you do not have to specify them in your WLST scripts.


Oracle Data Integrator Standalone Agent Template

Use the Oracle Data Integrator Standalone Agent when your ODI installation is not being managed by WebLogic Server.

The following table provides key information about this template.

Table 3-10 Oracle Data Integrator Standalone Agent Template Details

Template DetailInformation

Template type

Extension

Category

Oracle Data Integrator

Template name and version

Oracle Data Integrator Collocated Agent - 12.1.2.0

Template Dependencies

  • Common Infrastructure Engineering Runtime - 12.1.2.0

  • Oracle Data Integrator Standalone Agent Based - 12.1.2.0

Template JAR file and location

ORACLE_HOME/odi/common/templates/wls/odi_cam_unmanaged_template_12.1.2.jar


Oracle Data Integrator Standalone Collocated Agent Template

Use the Oracle Data Integrator Standalone Collocated Agent template when you install ODI collocated with WebLogic Server.

The following table provides key information about this template.

Table 3-11 Oracle Data Integrator Standalone Collocated Agent Template Details

Template DetailInformation

Template type

Extension

Category

Oracle Data Integrator

Template name and version

Oracle Data Integrator Standalone Collocated Agent - 12.1.2.0

Template Dependencies

  • Oracle JRF 12.1.2.0

Template JAR file and location

ORACLE_HOME/odi/common/templates/wls/odi_cam_managed_template_12.1.2.jar


Oracle Data Integrator Agent Template

The Oracle Data Integrator Agent template deploys the ODI Agent application, required libraries and the ODI Master repository data source.

The following table provides key information about this template.

Table 3-12 Oracle Data Integrator Agent Template Details

Template DetailInformation

Template type

Extension

Category

Oracle Data Integrator

Template name and version

Oracle Data Integrator Agent - 12.1.2.0

Template Dependencies

  • ODI Agent Libraries Template

  • ODI Master Datasource Template

Template JAR file and location

ORACLE_HOME/odi/common/templates/wls/odi_agent_template_12.1.2.jar


Oracle Data Integrator Agent Libraries Template

The Oracle Data Integrator Agent Libraries template deploys shared libraries required for the ODI Agent.

The following table provides key information about this template.

Table 3-13 Oracle Data Integrator Agent Libraries Template Details

Template DetailInformation

Template type

Extension

Category

Oracle Data Integrator

Template name and version

Oracle Data Integrator Agent Libraries - 12.1.2.0

Template Dependencies

  • ODI Base Template

  • Oracle Data Integrator SDK Shared Libraries Template

Template JAR file and location

ORACLE_HOME/odi/common/templates/wls/odi_agent_libraries_template_12.1.2.jar


Oracle Data Integrator Console Template

The Oracle Data Integrator Console template deploys the ODI Console application.

The following table provides key information about this template.

Table 3-14 Oracle Data Integrator Console Template Details

Template DetailInformation

Template type

Extension

Category

Oracle Data Integrator

Template name and version

Oracle Data Integrator Console - 12.1.2.0

Template Dependencies

  • ODI Work Datasource

  • Oracle Data Integrator SDK Shared Libraries Template

Template JAR file and location

ORACLE_HOME/odi/common/templates/wls/odi_repository_explorer_template_12.1.2.jar


Oracle Enterprise Manager Plugin for ODI Template

The Oracle Enterprise Manager Plugin for ODI template deploys the ODI Plugin for Oracle Enterprise Manager.

The following table provides key information about this template.

Table 3-15 Oracle Enterprise Manager Plugin for ODI Template Details

Template DetailInformation

Template type

Extension

Category

Oracle

Template name and version

Oracle Enterprise Manager Plugin for ODI - 12.1.2.0

Template Dependencies

  • Oracle Enterprise Manager 12.1.2.0

Template JAR file and location

ORACLE_HOME/em/common/templates/wls/oracle.em_odi_template_12.1.2.jar


Oracle HTTP Server Templates

The Oracle HTTP Server (OHS) domain templates are extension templates used to add OHS resources and services to a Basic WebLogic Server domain. OHS is the Web server component for Oracle Fusion Middleware. It provides a listener for Oracle WebLogic Server and the framework for hosting static pages, dynamic pages, and applications over the Web. The specific OHS template you will use depends on whether you are implementing OHS in a collocated or standalone environment.

This chapter contains these sections:

Oracle HTTP Server (Collocated)

Use the Oracle HTTP Server (Collocated) domain template when you want your OHS implementation to serve one or more FMW domains (for example, when you want OHS to front requests for a SOA domain) or when you want to take advantage of the advanced management capabilities provided by FMW Control.

Table 3-16 Oracle HTTP Server (Collocated) Domain Template Details

Template DetailInformation

Template type

Extension

Category

Uncategorized

Template name and version

Oracle HTTP Server (Collocated)—12.1.2.0

Template Dependencies

Oracle Enterprise Manager for WEBTIER—12.1.2.0

Template JAR file and location

MW_HOME/ohs/common/templates/wls/ohs_managed_template_12.1.2.jar

Domain topology profiles

Compact and Expanded.

Category

Undefined


Oracle HTTP Server (Standalone)

Use the Oracle HTTP Server (Standalone) domain template when you do not want your OHS implementation to front an FMW domain and do not need the management functionality provided by FMW Control or when you want to keep OHS in a DMZ and you do not want to open management ports used by the Node Manager.

Table 3-17 Oracle HTTP Server (Standalone) Domain Template Details

Template DetailInformation

Template type

Extension

Category

Oracle HTTP Server

Template name and version

Oracle HTTP Server (Standalone)—12.1.2.0

Template Dependencies

None

Template JAR file and location

MW_HOME/ohs/common/templates/wls/ohs_standalone_template_12.1.2.jar

Domain topology profiles

None defined.

Server groups

Undefined


PKIJV!-#PK:zDOEBPS/intro.htm Introduction

1 Introduction

This document provides information about Fusion Middleware domain and extension templates, which are Java Archive (JAR) files that contain the files and scripts required to create or extend a WebLogic domain.

This document contains the following topics:

Types of Templates

The types of template include:

Location of Installed WebLogic Server Templates

The following table identifies the location of the predefined template JAR files provided with the WebLogic Server installation, where WL_HOME represents the product installation directory.

Table 1-1 Location of Templates

Type of TemplateDirectory Location

WebLogic Server Domain, Extension, and Reconfiguration

WL_HOME\common\templates\wls

Fusion Middleware Extension and Reconfiguration

ORACLE_HOME\oracle _common\common\templates\wls

ORACLE_HOME\PRODUCT_HOME\common\templates\wls

Template Tools

The following table identifies the tools with which you can create templates and the tools with which you can use templates to create or extend a domain.

Table 1-2 Template Tools

ToUse this tool

Create a domain

  • Configuration Wizard

  • WLST Offline

  • unpack command

Extend an existing domain

  • Configuration Wizard

  • WLST Offline

Create a Managed Server domain on a remote machine

  • unpack command

  • WLST writeTemplate command (online)

Create a domain template

  • Domain Template Builder

  • pack command

  • WLST Offline

Create an extension template

Domain Template Builder

Create a Managed Server template

pack command

Upgrade a domain

Reconfiguration Wizard



Note:

All the tools used to create or extend a domain leverage a common underlying infrastructure, which is referred to as the configuration framework.


Template Dependencies

WebLogic Server resources must be set up in your domain before you can add resources from an extension template. This is known as a template dependency. For example, all extension templates provided with your product are dependent on, at the very least, the Administration Server and security realm resources that are configured by the Basic WebLogic Server Domain template. Other extension templates depend on resources from multiple templates. For example, to extend a domain to support the WebLogic Server Examples, the existing domain must already contain the resources from the Basic WebLogic Server Domain template and the WebLogic Server Default Domain extension template.

The template-info.xml file in a template JAR defines the template dependencies for a given template. Dependencies are chained. For example:

In this example, if you select Template A on the Configuration Wizard's Templates screen, templates B, C, D, E, and F are automatically included in the domain. If any of these templates are displayed on the Templates screen, you will see the check boxes for those template automatically selected. This ensures that when you select a product template on the Configuration Wizard Templates screen, the Configuration Wizard automatically includes in the domain all other product templates that configure resources required by the product you selected.

Similarly, if you specify a template JAR in a WLST script, all other templates that are dependencies of that template (either directly or indirectly) are included in the domain. Using the above example, if you specify Template A in a WLST script, templates B, C, D, E, and F are also included in the domain without you having to explicitly specify them in the script.

Files Typically Included in a Template

The basic files included in any template are config.xml and template-info.xml. A domain is created or extended based on these files, as well as additional files that are included in the template. The following table describes the files typically included in domain and extension templates.

Table 1-3 Files Included in a Template

FilenameDescription

product component files

Various files used to complete the domain setup for a specific Oracle product component. Such files may provide information for security and default database settings.

*-jdbc.xml

Sets up or extends a domain with JDBC system resources required by a product component. In a template, the *-jdbc.xml files must be located in the config\jdbc directory. There is one XML file for each JDBC resource in the domain. These files are present only if the domain includes JDBC resources.

*-jms.xml

Sets up or extends a domain with JMS system resources required by a product component. In a template, the *-jms.xml files must be located in the config\jms directory. This is applicable only if the domain requires JMS resources.

clusters.script

Used to modify the Configuration Wizard framework's default auto-configuration of a cluster. By default, resources are targeted to the cluster. You can unassign a resource from the cluster and then assign it to another component. To specify a target, you can use the following replacement variables:

  • %AManagedServer%—Any Managed Server

  • %AllManagedServers%—Comma-separated list of all Managed Servers

  • %AdminServer%—Administration Server name

  • %Cluster%—Cluster name

  • %ProxyServer%—Proxy server name

  • %HTTPProxyApp%—http proxy application definition

Note the following additional considerations:

  • You must use the name attribute of an object that is to be replaced.

  • You can use an asterisk (*) as a wildcard for "All."

This file is not required. When used, it must be located in the script directory. If it is not present, default targeting is used.

config.xml

Defines the resources that the template creates or adds to a domain. In a template, the config.xml file must be located in the config directory.

config-groups.xml

This file contains definitions of applications, services, servers, clusters, and mappings that create a relationship among these items. It enables movement of functionally related applications and services as a single operation when transitioning from one topology to another (for example, from a single server to multiple servers, or from a single server to a cluster). This ensures that all application and service dependencies are met when scaling a domain configuration.

Note: Do not modify this file in any way. It must be used as provided in the template.

An Application/Service group specifies a set of functionally related applications and services. The applications and services are grouped together on a particular server or cluster.

The Domain Topology section contains definitions of servers, as well as the targeting of applications and services to a specific server, group or servers or clusters. It contains the following definitions:

  • Server group definitions—Specifies a server or servers that can house functionally related sets of applications and services, thereby enabling automatic server creation.

  • Cluster group definitions—Specifies a cluster that can house functionally related sets of applications and services, thereby enabling automatic cluster creation.

  • Application/Service group mapping definitions—Specifies targeting of an Application/Service group to a specific server, group of servers, or cluster, via the name of the Application/Service group.

As of WebLogic Server 12.1.2, the domain topology section may define separate server groups, startup groups, and application/service group mapping definitions for compact and expanded domain profiles. For more information about domain profiles, see config-groups.xml and startup-plan.xml.

config-mapping.xml

This file is used to dynamically assign values to custom variables that are defined in a deployment plan, using name/value pairs.

database.xml

This file is included only in Fusion Middleware product templates that require JDBC data source definitions. It groups data sources into component schemas that are required to configure and load data into database objects via the Oracle Repository Creation Utility (RCU). It also contains the eligible database vendors and drivers, eliminating the possibility of selecting an unsupported database in the Fusion Middleware Configuration Wizard.

Note: Do not modify this file in any way. It must be used as provided in the template.

file-definition.xml

Applies only to Fusion Middleware product templates. It defines file copy and string substitution operations that are done during domain creation or extension. String substitution operations are supported only for WebLogic Server and not supported in a WebSphere environment.

jdbc.index

Identifies the locations of SQL scripts used to set up a database. The file lists the scripts in the order in which they must be run. If the scripts are not contained in the template, but are located in the product installation directory, that directory can be represented by a tilde ( ~ ) in the pathname for the scripts, as shown in the following example:

~/integration/common/dbscripts/oracle/reporting_runtime.sql

Specifically, the tilde represents the directory path identified by the $USER_INSTALL_DIR$ variable in the stringsubs.xml file.

In a template, a jdbc.index file must be located in the _jdbc_\dbtype\dbversion directory, where dbtype is the type of database, such as Oracle, and dbversion is the database version, such as 9i.

In addition to listing the SQL files related to a data source, the jdbc.index file contains information about the categories associated with the data source. The default dbCategories that are available are:

  • 'Drop/Create P13N Database Objects' category associated with the p13nDataSource data source, which is a part of the p13n.jar domain template.

  • 'Drop/Create Portal Database Objects' category associated with the "p13nDataSource" data source, which is a part of the wlp.jar domain template.

  • 'Drop/Create GroupSpace Database Objects' category associated with the appsGroupSpaceDataSource data source, which is a part of the wlp_groupspacedb.jar domain template.

All these template jar files are located in the WL_HOME\common\templates\applications directory.

jvm-config.xml

This file is specific to FMW product installations in a WebSphere environment, and can be ignored in a WebLogic Server environment.

security.xml

Used to create user groups and roles that establish identity and access to domain resources. You can create the default Admin user only through the security.xml file in a domain template. However, you can create user groups and roles through the security.xml file included in either a domain or an extension template.

startscript.xml

Used to create the *.cmd and *.sh files that are placed into a domain's root and bin directories.

startup-plan.xml

Defines startup parameters for WebLogic Server instances, at the domain level or server group level. One or more of the following startup parameters may be defined in this file:

  • Environmental variables

  • Java system properties

  • Java protocol handlers

  • WLS PRE_CLASSPATH

  • WLS POST_CLASSPATH

  • Java library path

  • WLS JVM initial heap size

  • WLS JVM maximum heap size

  • WLS JVM perm size

  • WLS JVM maximum perm size

  • Other java arguments

If the template defines both compact and expanded domain profiles, separate groups of startup parameter definitions are defined, one group for each profile type. The startup parameters used for your domain may differ depending on whether you create a compact or expanded domain. For more information about domain profiles and startup groups, see config-groups.xml and startup-plan.xml.

stringsubs.xml

Identifies string substitution values and files that will receive string substitutions during domain creation or extension. The files that will receive string substitutions must already be prepared with replacement variables. During domain creation or extension, the Configuration Wizard framework runs macros to replace variables with the appropriate string substitution, using information from WL_HOME\common\lib\macrorules.xml, where WL_HOME is the WebLogic Server installation directory.

template-info.xml

Provides template identification information, such as the template name, software version, type of template (domain or application), author, description, and so on. This file also includes template dependency information (if applicable).

was-variable.xml

This file is specific to FMW product installations in a WebSphere environment, and is ignored in a WebLogic Server environment.


config-groups.xml and startup-plan.xml

Many templates contain a config-groups.xml file. If present, it defines one or more of the following items:

Some templates also contain a startup-plan.xml file, which defines server startup parameters at a global (domain-wide) level or server group level.

When you create a domain using multiple templates, the config-group.xml files from all templates included in the domain are used to create the config-groups.xml file for the domain.

Similarly, the startup-plan.xml files from all templates included in the domain are merged to create the startup-plan.xml file for the domain. At domain creation, the merged startup plan is used to generate the appropriate scripts for the domain.

The merged config-groups.xml and startup-plan.xml files are stored in the domain's init-info directory.


Note:

Do not manually edit either the config-groups.xml or startup-plan.xml files in the init-info directory.


The following sections describe each of these items in detail and how they work together in a domain.

Domain Topology Profiles

When creating a domain, you specify the domain topology profile (Compact or Expanded) to use for that domain. Domain profiles are defined only in some Fusion Middleware product templates, and do not apply to domains in which no Fusion Middleware products are installed with WebLogic Server.


Note:

You can explicitly specify the domain topology profile only if you use WLST to create the domain. Graphical interfaces automatically configure the appropriate profile. For example, when creating a domain using the JDeveloper domain creation utility, the domain is created with a Compact profile; when creating a domain using the Fusion Middleware Configuration Wizard, the domain is created with an Expanded profile.


The config-groups.xml file in a Fusion Middleware product template may define the domain profiles for the domain, in the profile attribute of the <domain-topology> element. The domain profile can be either Compact (or single-instance) or Expanded (clustered). If the <domain-topology> does not define separate Custom and Expanded profiles, the configuration defined in <domain-topology> is used for both types of domains.

The domain profile defines:

  • The serK?ver groups for the profile.

  • Which server group is the Administration Server server group. The Administration Server group is not user-expandable.

  • Whether or not a server group is user-expandable, that is, whether or not you can assign Managed Servers to it. Note that if a server group is not user-expandable, you can still assign Managed Servers to it by cloning an existing server that is already assigned to the server group.


    Note:

    Use the WLST offline command listServerGroups() to list all user-expandable server groups in the domain.


  • The application service groups that are targeted to each defined server group. All servers that are assigned to a server group inherit its targets.

  • Whether or not a prefix is assigned to the name of any servers that are added to the server group. For example, if a prefix of 'xyz' is defined for the server group, and you add a server called 'server2' to the group, the server name is registered as 'xyz_server2'.

Table 1-4 describes the differences between Expanded and Compact domain profiles.

Table 1-4 Differences Between Expanded and Compact Domains

Expanded DomainCompact Domain

Also known as a clustered domain.

Also known as a single-instance domain.

Contains an Administration Server. Contains Managed Servers for the Fusion Middleware product(s) in the domain. Fusion Middleware Managed Servers can be assigned to clusters.

Contains only an Administration Server, with no Managed Servers or clusters for the Fusion Middleware product(s) in the domain. This domain type is uses primarily for development purposes.

Defines an Administration Server server group and one or more Managed Server server groups.

Defines an Administration Server server group. Although a Managed Server server group may be defined in config-groups.xml, it is not used.

All application service groups defined in config-groups.xml are targeted. Some application service groups are targeted to the Administration Server server group, other application service groups are targeted to the Managed Server server group(s).

All or a subset of the defined application service groups are targeted to the Administration Server server group. Some application service groups may not be targeted.


There are two ways to select the domain profile for a new domain:

  • When creating a domain using the FMW Configuration Wizard, you select the profile to use on the Configuration Type screen. See "Configuration Type" in Creating Domains Using the Configuration Wizard.

  • When creating a domain using WLST, you specify the profile to use in the readTemplate command. See "readTemplate" in WebLogic Scripting Tool Command Reference. The default profile type is Expanded.

Application Service Groups, Server Groups, and Application Service Mappings

The config-groups.xml file in Fusion Middleware templates may define application service groups, server groups, and application service mappings. This automates the assignment of applications and services to the appropriate servers in the domain.

  • Application service group—These are defined in the <app-svc-groups> element. Each <group> element defines a unique application service group, which contain various applications and services that will be included in the domain, such as application deployments, work managers, JMS system resources, libraries, and other items that are needed in the product domain. Application service groups are always the same for each domain profile, although some application service groups may not be used in a Compact domain. Application service groups may be mapped to multiple server groups.

  • Server Group—A named server group. Typically, there is at least one Administration Server group and at least one Managed Server group defined in a domain's config-groups.xml file. These are defined by a <server-group> element in the <domain-topology> element. Note that although a Compact profile may define both Administration Server and Managed Server server groups, only the Administration Server server group is used in a Compact domain.

    If a server group is defined as user-expandable, you can add Managed Servers to the server group. User-expandable servers are listed in the Server Groups drop-down list of the Managed Server screen of the Fusion Middleware Configuration Wizard. In WLST, you can determine which server groups are user-expandable by using the listServerGroups command.

  • Application Service Mappings—Define which application service groups are mapped to each defined server group. These mappings differ depending on the domain profile. They are defined in the <app-svc-group-mapping> elements in the <domain-topology> element of config-groups.xml.

Server groups target Fusion Middleware applications and services to one or more servers by mapping defined application service groups to each defined server group. A given application service group may be mapped to multiple server groups if needed. Any application services that are mapped to a given server group are automatically targeted to all servers that are assigned to that group.

For example, suppose that the following items are defined in config-groups.xml:

  • Server group ADMIN-SVR (the server group for the Administration Server)

  • Server group MGD-SVRS (the server group for Managed Servers)

  • Application service group ADMIN-APPS, which defines the application services that will run only on the Administration Server

  • Application service group MAIN-APPS, which defines applications that will run on Managed Servers

  • Application service group MAIN-LIBS, which defines libraries that need to be targeted to the Administration Server and Managed Servers

  • An application service mapping that maps MAIN-APPS to the MGD-SRVS server group

  • An application service mapping that maps ADMIN-APPS to the ADMIN-SVR server group

  • An application service mapping that maps MAIN-LIBS to the ADMIN-SVR server group

  • An application service mapping that maps MAIN-LIBS to the MGD-SVRS server group

In this example, all applications and other resources that are defined in ADMIN-APPS are targeted to the Administration Server. All applications and other resources that are defined in MAIN-APPS are targeted to all Managed Servers. All libraries that are defined in MAIN-LIBS are targeted to the Administration Server and all Managed Servers.

Add a Server To or Remove a Server From a Server Group

You can use the WLST setServerGroups() command to add a server to any user-expandable server group or any server group that you created. You can also remove a server from any server group. The following examples demonstrate this.

# add a server to a server group
setServerGroups('my_server4', 'XYZ-MAN-SRVS', '180000')

# remove a server from a server group by setting the group to null
serverGroup = []
setServerGroups('my_server3', serverGroup

Startup Groups

The startup-plan.xml file in a template defines the startup groups, which allow different startup parameters to be defined for different servers or groups of servers in a domain. A domain template may contain:

  • a global startup definition, which defines the domain-wide startup settings for all servers in the domain.

  • one or more server startup groups, which are associated with a server group. If present, these define the startup settings for all servers assigned to the server group. If a server startup group defines a setting that is already defined at the global level, the server-level setting takes precedence.

Different startup settings may be defined for Expanded and Compact domain profiles. In addition, when creating a domain, multiple templates may be applied to a domain. Therefore, all possible startup settings and startup groups are combined into a single startup-plan. xml file in the domain's /init-info directory. When you start a server, this file is referenced to determine:

  • The startup group (if any) to which a server is assigned, based on the server group to which the server is assigned and the startup group to which the server group is assigned.

  • The startup settings to use for the server, based on the startup group to which the server's server group is assigned.

If a server is not assigned to a server group, it is started using the global settings that are defined in startup-plan.xml.

startup-plan.xml in Table 1-3 lists the startup parameters that may be configured in this file.

Managing Server Startup Configuration

Although the merged startup-plan.xml file for a domain defines the startup parameters for the servers in the domain, in some situations, you may want to use offline WebLogic Scripting Tool (WLST) to:

  • Create your own startup groups to define unique startup parameters for one or more servers in the domain.

  • Adjust the startup parameters for a server group.

  • Add a server to or remove a server from a startup group. Note that although you can remove a server from a server group that is not user-modifiable, you can only add a server to either a user-modifiable server group or a server group that you have created.

The startup-plan.xml file for a domain is automatically updated with any changes you make to the startup configuration.

Creating and Modifying a Startup Group

You can create a new startup group from any existing server group in the domain. The new startup group inherits only the startup parameters from the server group you used to create the startup group. You can then change the startup parameter settings for the new startup group and assign individual servers to it.

There are two ways you can determine the server groups in a domain:

  • Enter the WLST command listServerGroups(). This displays only user-expandable server groups.

  • Open the domain's init-info/config-groups.xml file. Server group names are defined by the name attribute of each <server group> element in this file.

The following WLST example shows how to create a new startup group called XYZ-MGD-SVRS based on server group JRF-MAN-SVR, add a server to the group, and view and adjust the settings for the new group.

Example 1-1 Creating and Modifying a Startup Group

# Create a new startup group called XYZ-MGD-SVRS based on the startup settings 
# for server group JRF-MAN-SVR
addStartupGroup('XYZ-MGD-SRVS', 'JRF-MAN-SVR')

# Set the startup group for my_server1 to XYZ-MGD-SRVS
setStartupGroup('my_server1', 'XYZ-MGD-SRVS')
# select the XYZ-MGD-SRVS startup group for modification
cd('/StartupGroupConfig/XYZ-MGD-SRVS')

# display the setting for MaxHeapSize 
get('MaxHeapSize')
'1024'
# change the setting for MaxHeapSize
set('MaxHeapSize', '1536')

# get Java system properties for a startup group as a Python dictionary
dictionary = get('SystemProperties')

# set Java system properties for a startup group
dictionary['key.1'] = 'value.1'
dictionary['key.2'] = 'value.2'
set('SystemProperties',dictionary)

# get Java environment settings for a startup group as a Python dictionary
dictionary = get('EnvVars')

# set Java system properties for a startup group
dictionary['env.1'] = 'value.1'
dictionary['env.2'] = 'value.2'
set('EnvVars',dictionary)

Note:

Calling set('EnvVars',{}) resets all customizations, and environment variables for the startup group will revert back to the settings derived from the server groups associated with the startup group.


PK!zDUKPK:zDOEBPS/templates.htm WebLogic Server Templates

2 WebLogic Server Templates

This chapter describes the following WebLogic domain templates that are provided with your WebLogic Server installation. You can create or extend domains by selecting these templates on the Select Domain Source or Select Extension Source screens of the Oracle Fusion Middleware Configuration Wizard.

Table 2-1 Oracle WebLogic Server and Workshop for WebLogic Templates

TemplateDescription

Basic WebLogic Server Domain Template


Creates a base WebLogic Server domain.

WebLogic Server Starter Domain Template


Creates a WebLogic Server starter domain.

WebLogic Advanced Web Services for JAX-RPC Extension Template


Extends an existing WebLogic Server domain to add functionality required for advanced JAX-RPC Web services, including Web services reliable messaging, buffering, and JMS transport.

WebLogic Advanced Web Services for JAX-WS Extension Template


Extends a domain to add functional required for advanced Web services, including asynchronous messaging, Web services reliable messaging, message buffering, Web services atomic transactions, and security using WS-SecureConversation.

WebLogic JAX-WS SOAP/JMS Extension Template


Extends a domain to include the resources required to use SOAP over JMS transport for JAX-WS Web services.

Avitek Medical Records Sample Domain Template


Extends the Basic WebLogic Server domain to create the Avitek Medical Records sample domain. This domain is a WebLogic Server sample application suite that demonstrates all aspects of the J2EE platform.

Avitek Medical Records Sample Domain Template (Spring Version)


Extends the Basic WebLogic Server domain to create the Avitek Medical Records sample domain for Spring. This domain is a WebLogic Server sample application suite that demonstrates all aspects of the J2EE platform.

WebLogic Server Default Domain Extension Template


Extends the Basic WebLogic Server domain with a web application designed to guide new users through an introduction to WebLogic Server. When running the web application, users can review informative content on various topics, including highlights of WebLogic Server functionality. From the web application, users can also run several preconfigured, precompiled examples. Resources from this extension template are required for a WebLogic Server Examples domain.

WebLogic Server Examples Extension Template


Extends the WebLogic Server domain containing resources from the base WebLogic Server domain template and the WebLogic Server Default Domain extension template to create a complete WebLogic Server Examples domain. The WebLogic Server Examples domain contains a collection of examples that illustrate best practices for coding individual J2EE and WebLogic Server APIs.


Basic WebLogic Server Domain Template

Your product installation provides one predefined Basic WebLogic Server domain template. All other predefined templates are extension templates that you may use to add resources, services, and applications to a Basic WebLogic Server domain. You can easily create or extend a domain by using these predefined templates with the Configuration Wizard or WLST.

Template Details

The following table provides basic information about the Basic WebLogic Server Domain template. Template name is the name of the template as it is shown in the product list on the Configuration Wizard Select Domain Source and Select Extension Source screens.

Table 2-2 Basic WebLogic Server Domain Template Information

Template DetailInformation

Template type

Domain

Template name

Basic WebLogic Server Domain

Template JAR file and location

WL_HOME\common\templates\wls\wls.jar

Template Dependencies

None


Resources and Services Configured in a Basic WebLogic Server Domain

The following table identifies the resources and services configured in a domain created with the Basic WebLogic Server Domain template.

Table 2-3 Resources Configured in a Basic WebLogic Server Domain

Resource TypeNameNotes

Administration Server

AdminServer

The default configuration for the Administration Server is as follows:

  • Listen address: All Local Addresses

  • Listen port: 7001

  • SSL is disabled

When using the Configuration Wizard or WLST Offline to create a domain, if you want the Administration Server name to be different from the default name, AdminServer, you must configure the name manually. You cannot change the name later when applying an extension template.

For information about customizing the Administration Server name while creating a domain with the Configuration Wizard, see "Creating WebLogic Domains" Creating Domains Using the Configuration Wizard.

For information about customizing the Administration Server name while creating a domain with WLST Offline, see "Creating and Configuring WebLogic Domains Using WLST Offline" in Understanding the WebLogic Scripting Tool.

The following sample WLST Offline code snippet shows how to change the default Administration Server name, AdminServer, to MedRecServer.

#-----------------------------------#
Read the Basic WebLogic Server Domain template
readTemplate('d:/MW_HOME/wlserver/common/templates/wls/wls.jar')
#Change the Administration Server name.
cd('Servers/AdminServer')
set('Name', 'MedRecServer')
#-----------------------------------

Security realm

myrealm

This is the default (active) WebLogic Server security realm. The administration user account, weblogic, is configured in this security realm, as well as all default groups and roles.


WebLogic Server Starter Domain Template

Your product installation also provides one predefined WebLogic Server domain template. This template contains the default domain configuration settings and an application that provides a Welcome page to help you get started. You can easily create or extend a domain by using this predefined template with the Configuration Wizard or WLST.

Template Details

The following table provides basic information about the WebLogic Server Starter Domain template.

Table 2-4 WebLogic Server Starter Domain Template Information

Template DetailInformation

Template type

Domain

Template name in Configuration Wizard

This template is not available from the list of products in the Configuration Wizard. You can select it only by using the Browse option on the Select Domain Source or Select Extension Source screens, and navigating to the JAR file location.

Template JAR file and location

WL_HOME\common\templates\wls\wls_starter.jar

Template Dependencies

Base WebLogic Server domain template


Resources and Services Configured in a WebLogic Server Starter Domain

The following table identifies the resources and services configured in a domain created with the Basic WebLogic Server Starter Domain template.

Table 2-5 Resources Configured in a WebLogic Server Starter Domain

Resource TypeNameNotes

Administration Server

AdminServer

The default configuration for the Administration Server is as follows:

  • Listen address: All Local Addresses

  • Listen port: 7001

  • SSL is disabled

When using the Configuration Wizard or WLST Offline to create a domain, if you want the Administration Server name to be different from the default name, AdminServer, you must configure the name manually. You cannot change the name later when applying an extension template.

For information about customizing the Administration Server name while creating a domain with the Configuration Wizard, see "Creating WebLogic Domains" Creating Domains Using the Configuration Wizard.

For information about customizing the Administration Server name while creating a domain with WLST Offline, see "Creating WebLogic Domains Using WLST Offline" in Understanding the WebLogic Scripting Tool.

The following sample WLST Offline code snippet shows how to change the default Administration Server name, AdminServer, to MedRecServer.

#-----------------------------------#
Read the Basic WebLogic Server Domain template
readTemplate('d:/MW_HOME/wlserver/common/templates/wls/wls.jar')
#Change the Administration Server name.
cd('Servers/AdminServer')
set('Name', 'MedRecServer')
#-----------------------------------

Security realm

myrealm

The default (active) WebLogic Server security realm.

Application Deployments

wls_starter

A sample Web application deployed to the starter domain.


WebLogic Advanced Web Services for JAX-RPC Extension Template

By using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to include the resources required for advanced JAX-RPC Web services. You accomplish this by adding the resources and services provided in the WebLogic Advanced Web Services for JAX-RPC extension template to a base WebLogic Server domain.

Template Details

The following table provides basic information about the WebLogic Advanced Web Services for JAX-RPC extension template.

Table 2-6 WebLogic Advanced Web Services for JAX-RPC Extension Template Information

Template DetailInformation

Template type

Extension

Category

Uncategorized

Template name and version

WebLogic Advanced Web Services for JAX-RPC Extension—12.1.2.0

Template Dependencies

Base WebLogic Server domain template

Template JAR file and location

WL_HOME\common\templates\wls\wls_webservice.jar

Reconfiguration template JAR file and location

WL_HOME\common\templates\wls\wls_webservice_reconfig_version.jar

Domain topology profiles

None defined. The defined application service group is included for both Expanded and Compact domains.


Resources and Services Configured

The following table identifies the resources and services configured in a domain extended with the WebLogic Advanced Web Services for JAX-RPC extension template.

Table 2-7 Resources Configured in a WebLogic Advanced Web Services for JAX-RPC Domain

Resource TypeNameExtension Result

Administration Server

AdminServer

Uses the Administration Server provided in the Basic WebLogic Server domain. The default name is AdminServer, unless changed during domain creation. The Administration Server referenced in this extension template is cgServer.

The default configuration for the Administration Server is as follows:

  • Listen address: All Local Addresses

  • Listen port: 7001

  • SSL is enabled

  • SSL listen port: 7002

For information about naming the Administration Server during domain creation, see Resources and Services Configured in a Basic WebLogic Server Domain.

Security realm

myrealm

Uses the default security realm provided by the Basic WebLogic Server domain.

File Store

WseeFileStore

Adds the file store to be used as the persistent store for the WseeJmsServer JMS server. This file store is targeted to the Administration Server.

SAF Agent

ReliableWseeSAFAgent

Adds this store-and-forward agent, which uses the WseeFileStore, and targets it to the Administration Server. The SAF agent controls receipt and handling of reliable messages.

JMS Queues

WseeMessageQueue

Adds the JMS queue to the JMS server, WseeJmsServer.

Queues are under JMSModules/module name, these are under WseeJMSModule

JMS Queues

WseeCallbackQueue

Adds the JMS queue to the JMS server, WseeJmsServer.

JMS Server

WseeJmsServer

Adds the JMS server as a system resource and targets it to the Administration Server, AdminServer.

Work Manager

weblogic.wsee.mdb.DispatchPolicy

Add this Work Manager and targets it to the Administration Server, AdminServer.


WebLogic Advanced Web Services for JAX-WS Extension Template

The WebLogic Advanced Web Services for JAX-WS extension template automatically configures the resources required to support the following advanced Web services features:


Note:

Each of the two Advanced Web Services templates can be used individually or together in a domain. If, however, you apply this template to the same domain to which you applied the WebLogic Advanced Web Services extension template, you must apply the Advanced Web Services template before applying the Advanced Web Services for JAX-WS template.


For more information, see "Configuring Your Domain for Advanced Web Services Features" in Developing JAX-WS Web Services for Oracle WebLogic Server.

Template Details

The following table provides basic information about the WebLogic Advanced Web Services for JAX-WS extension template.

Table 2-8 WebLogic Advanced Web Services for JAX-WS Extension Template Details

Template DetailInformation

Template type

Extension

Category

Uncategorized

Template name and version

WebLogic Advanced Web Services for JAX-WS Extension - 12.1.2.0

Template Dependencies

Base WebLogic Server domain template

Template JAR file and location

WL_HOME\common\templates\wls\wls_webservice_jaxws.jar

Reconfiguration template JAR file and location

WL_HOME\common\templates\wls\wls_webservice_jaxws_reconfig_version.jar

Domain topology profiles

None defined. The defined application service group is included for both Expanded and Compact domains.


Resources and Services Configured

The following table identifies the resources and services configured in a domain extended with the WebLogic Advanced Web Services for JAX-WS extension template.

Table 2-9 Resources Configured in a WebLogic Advanced Web Services for JAX-WS Domain

Resource TypeNameExtension Result

Administration Server

AdminServer

Uses the Administration Server provided in the Basic WebLogic Server domain. The default name is AdminServer, unless changed during domain creation. The Administration Server referenced in this extension template is cgServer.

The default configuration for the Administration Server is as follows:

  • Listen address: All Local Addresses

  • Listen port: 7001

  • SSL is enabled

  • SSL listen port: 7002

For information about naming the Administration Server during domain creation, see Resources and Services Configured in a Basic WebLogic Server Domain.

Security realm

myrealm

Uses the default security realm provided by the Basic WebLogic Server domain.

JMS Server

WseeJaxwsJmsServer

Adds the JMS server as a system resource and targets it to the Administration Server.

File Store

WseeJaxwsFileStore

Adds the file store to be used as the persistent store for the WseeJaxwsJmsServer JMS server. This file store is targeted to the Administration Server.

JMS System Resource

WseeJaxwsJmsModule

Defines a distributed destination for the cluster. All associated targets will be used to support JAX-WS Web services. The subdeployment name is WseeJaxwsJmsServerSub.

Note: By default, a weighted distributed destination (WDD) is configured. In a clustered environment, Oracle strongly recommends that you upgrade the destination to a uniform distributed destination (UDD).

JMS Queues

weblogic.wsee.BufferedRequest Queue

weblogic.wsee.BufferedRequestErrorQueue

weblogic.wsee.BufferedResponseQueue

weblogic.wsee.BufferedResponseErrorQueue

Adds these JMS queues to the JMS server, and targets them to WseeJaxwsJmsServer.

These queues are reserved for future use.

SAF Agent

ReliableWseeJaxwsSAFAgent

Adds this store-and-forward agent, which uses the WseeJaxwsFileStore, and targets it to the Administration Server. The SAF agent controls receipt and handling of reliable messages.

Work Manager

weblogic.wsee.jaxws.mdb.DispatchPolicy

Adds this Work Manager and targets it to the Administration Server. The Work Manager defines the thread pool resources.


WebLogic JAX-WS SOAP/JMS Extension Template

By using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to include the resources required to use SOAP over JMS transport for JAX-WS Web services. You accomplish this by adding the resources and services provided in the WebLogic Advanced Web Services extension template to a base WebLogic Server domain.

Template Details

The following table provides basic information about the WebLogic JAX-WS SOAP/JMS extension template.

Table 2-10 WebLogic JAX-WS SOAP/JMS Extension Template Details

Template DetailInformation

Template type

Extension

Category

Uncategorized

Template name and version

WebLogic JAX-WS SOAP/JMS Extension—12.1.2.0

Template Dependencies

Base WebLogic Server domain template

Template JAR file and location

WL_HOME\common\templates\wls\wls_webservice_soapjms.jar

Reconfiguration template JAR file and location

WL_HOME\common\templates\wls\wls_webservice_soapjms_reconfig_version.jar

Domain topology profiles

None defined. The defined application service group is included for both Expanded and Compact domains.


Resources and Services Configured

The following table identifies the resources and services configured in a domain extended with the WebLogic JAX-WS SOAP/JMS extension template.

Table 2-11 Resources Configured in a WebLogic JAX-WS SOAP/JMS Domain

Resource TypeNameExtension Result

JMS server

WseeSoapjmsJmsServer

JMS server management container.

File store

WseeSoapjmsFileStore

File store, or physical store, used by the WebLogic Server to handle the I/O operations to save and retrieve data from the physical storage (such as file, DBMS, and so on).

JMS Module

WseeSoapjmsJmsModule

JMS module that defines the JMS resources needed for SOAP over JMS transport.

JMS subdeployment

WseeSoapjmsJmsServerSub

JMS subdeployment for targeting the JMS resources to the WseeSoapJmsServer.

JMS Connection Factory

com.oracle.webservices.jms.ConnectionFactory

Default JMS connection factory used to create connections for SOAP over JMS transport.

JMS Queue

com.oracle.webservices.api.jms.RequestQueue

Default JMS request queue.

JMS Queue

com.oracle.webservices.api.jms.ResponseQueue

Default JMS response queue.


Avitek Medical Records Sample Domain Template

By using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to create an Avitek Medical Records Sample domain. You accomplish this by adding the resources and services provided in the Avitek Medical Records Sample domain extension template to a base WebLogic Server domain.

For more information about the Avitek Medical Records sample application, see "Sample Application and Code Examples" in Understanding Oracle WebLogic Server.

Template Details

The following table provides basic information about the Avitek Medical Records Sample domain extension template.

Table 2-12 Avitek Medical Records Sample Domain Information

Template DetailInformation

Template type

Extension

Template name in Configuration Wizard

This template is not available from the list of products in the Configuration Wizard. You can select it only by using the Browse option on the Select Domain Source or Select Extension Source screens, and navigating to the JAR file location.

Template JAR file and location

WL_HOME\common\templates\wls\medrec.jar

Template Dependencies

Basic WebLogic Server Domain template


Resources and Services Configured

The following table identifies the resources and services configured in a domain extended with the Avitek Medical Records Sample extension template.

A Work Manager service (weblogic.wsee.mdb.DispatchPolicy) is also available, but it is not targeted to the Administration Server.

Table 2-13 Resources Configured in an Avitek Medical Records Domain

Resource TypeNameExtension Result

Administration Server

AdminServer

Uses the Administration Server provided in the Base WebLogic Server domain. The default name is AdminServer, unless changed during domain creation. The Administration Server is referenced in the template as @SERVER_NAME, and appears as AdminServer in the Administration Console.

The default configuration for the Administration Server is as follows:

  • Listen address: All Local Addresses

  • Listen port: 7001

  • SSL is enabled

  • SSL port: 7002

For information about naming the Administration Server during domain creation, see Resources and Services Configured in a Basic WebLogic Server Domain.

Security realm

myrealm

Uses the default security realm provided in the Basic WebLogic Server domain.

Application Deployments

browser-starter

Adds the browser-starter Web application and targets it to the Administration Server.

Application Deployments

medrec

Adds the sample medrec Enterprise application and targets it to the Administration Server.

Application Deployments

physician

Adds the sample physician Enterprise application and targets it to the Administration Server.

Application Deployment

SamplesSearchWebApp

Adds a sample search application and targets it to the Administration Server.

JDBC Data Sources

MedRecGlobalDataSourceXA

Identifies the JDBC data source as a MedRecGlobalDataSourceXA system resource.

JMS Queues

com.oracle.medrec.jms.RecordToCreateQueue

com.oracle.medrec.jms.PatientNotificationQueue

weblogic.wsee.DefaultQueue

Adds the JMS queue to the JMS server, MedRecWseeJMSServer.

JMS Server

MedRecJMSServer

Adds the JMS server as a MedRec-jms system resource and targets it to the Administration Server

JMS System Resources

MedRec-jms

Adds the JMS servers, connection factories, and queues to be used as JMS system resources, and targets the resources to the Administration Server.

Mail Session

mail/MedRecMailSession

Adds this mail session.

SAF Agent

WsrmAgent

Adds this store-and-forward agent, which uses the MedRecWseeFileStorfile store, and targets it to the MedRecServer.

Deployed library

jsf1.2@1.2.9.0

Adds the Java Server Faces Version 1.2 libraries.

Deployed library

jstl1.2.@1.2.0.2

Adds the Java standard tagging (JSTL) Version 1.2 libraries.

WLDF System Resource

MedRecWLDF

Adds the WLDF system resource and defined WLDF instrumentation monitors for dye injection, and targets them to the Administration Server.


Avitek Medical Records Sample Domain Template (Spring Version)

By using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to create an Avitek Medical Records Sample domain in Spring. You accomplish this by adding the resources and services provided in the Avitek Medical Records Sample domain extension template to a base WebLogic Server domain.

For more information about the Avitek Medical Records sample application, see "Sample Application and Code Examples" in Understanding Oracle WebLogic Server.

Template Details

The following table provides basic information about the WebLogic Advanced Web Services Extension template. Template name is the name of the template as it is shown in the product list on the Configuration Wizard Select Domain Source and Select Extension Source screens.

Table 2-14 Avitek Medical Records Sample Domain (Spring) Information

Template DetailInformation

Template type

Extension

Template name

This template is not available from the list of products in the Configuration Wizard. You can select it only by using the Browse option on the Select Domain Source or Select Extension Source screens, and navigating to the JAR file location.

Template JAR file and location

WL_HOME\common\templates\wls\medrec_spring.jar

Template Dependencies

Basic WebLogic Server Domain template


Resources and Services Configured

The following table identifies the resources and services configured in a domain extended with the Avitek Medical Records Sample extension template for Spring.

Table 2-15 Resources Configured in an Avitek Medical Records Domain for Spring

Resource TypeNameExtension Result

Administration Server

AdminServer

Uses the Administration Server provided in the base WebLogic Server domain. The default name is AdminServer, unless changed during domain creation. The Administration Server is referenced in the template as @SERVER_NAME, and appears as AdminServer in the Administration Console.

The default configuration for the Administration Server is as follows:

  • Listen address: All Local Addresses

  • Listen port: 7001

  • SSL is enabled

  • SSL port: 7002

For information about naming the Administration Server during domain creation, see Resources and Services Configured in a Basic WebLogic Server Domain.

Security realm

myrealm

Uses the security realm provided in the base WebLogic Server domain.

Application Deployments

browser-starter

Adds the browser-starter Web application and targets it to the MedRecServer.

Application Deployments

medrec

Adds the sample medrec Enterprise application and targets it to the MedRecServer.

Application Deployments

physician

Adds the sample physician Enterprise application and targets it to the MedRecServer.

Application Deployment

SamplesSearchWebApp

Adds a sample search application and targets it to the Administration Server.

JDBC Data Sources

MedRecGlobalDataSourceXA

Identifies the JDBC data source as a MedRecGlobalDataSourceXA system resource.

Pool capacity (initial): 2

Pool capacity (maximum): 10

Protocol: Two Phase Commit

JMS Queues

com.oracle.medrec.jms.RecordToCreateQueue

com.oracle.medrec.jms.PatientNotificationQueue

weblogic.wsee.DefaultQueue

Adds these JMS queues to the JMS server, MedRecWseeJMSServer.

JMS Servers

MedRecJMSServer

Adds the JMS server as a MedRec-jms system resource and targets it to the MedRecServer.

JMS System Resources

MedRec-jms

Adds the JMS servers, connection factories, and queues to be used as JMS system resources, and targets the resources to the MedRecServer.

Mail Session

mail/MedRecMailSession

Adds this mail session.

SAF Agent

WsrmAgent

Adds this store-and-forward agent, which uses the file store, MedRecWseeFileStore, and targets it to the MedRecServer.

Deployed library

jsf1.2@1.2.9.0

Adds the Java Server Faces Version 1.2 library and targets it to the MedRecServer.

Deployed library

jstl1.2.@1.2.0.1

Adds the Java standard tagging (JSTL) Version 1.2 library and targets it to the MedRecServer.

Deployed library

weblogic-spring#10.3.6.0@10.3.6.0

Adds the WebLogic Spring Version 10.3.6 library and targets it to the MedRecServer.

WLDF System Resource

MedRecWLDF

Adds this WLDF system resource, and targets it to the MedRecServer. The WLDF resource defines an instrumentation monitor for dye injection, and a harvester metric (com.oracle.medrec.admin.AdminReport).


WebLogic Server Default Domain Extension Template

Using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to include resources required for a default WebLogic Server domain. You accomplish this by adding the resources and services provided in the WebLogic Server Default Domain extension template to a base WebLogic Server domain.


Note:

Applying the WebLogic Server Default Domain extension template to a base WebLogic domain is a prerequisite to using the WebLogic Server Examples extension template.


For more information about the samples that are supported in the WebLogic Server Examples domain, see "Sample Application and Code Examples" in Understanding Oracle WebLogic Server.

Template Details

The following table provides basic information about the WebLogic Server Default Domain Extension template.

Template Dependencies lists all templates that provide resources required by the WebLogic Server Default Domain extension template.

Table 2-16 WebLogic Server Default Domain Information

Template DetailInformation

Template type

Extension

Template name in Configuration Wizard

This template is not available from the list of products in the Configuration Wizard. You can select it only by using the Browse option on the Select Domain Source or Select Extension Source screens, and navigating to the JAR file location.

Template JAR file and location

WL_HOME\common\templates\wls\wls_default.jar

Template Dependencies

Basic WebLogic Server Domain template


Resources and Services Configured

The following table identifies the resources and services configured in a domain extended with the WebLogic Server Default Domain extension template.

Table 2-17 Resources Configured in a WebLogic Server Default Domain

Resource TypeNameExtension Result

Administration Server

AdminServer

Uses the Administration Server provided in the base WebLogic Server domain. The default name is AdminServer, unless changed during domain creation. The Administration Server is referenced in the template as @SERVER_NAME, and appears as AdminServer in the Administration Console.

The default configuration for the Administration Server is as follows:

  • Listen address: All Local Addresses

  • Listen port: 7001

  • SSL is disabled

For information about naming the Administration Server during domain creation, see Resources and Services Configured in a Basic WebLogic Server Domain.

Security realm

myrealm

Uses the security realm provided by the base WebLogic Server domain.

Application Deployment

mainWebApp

Adds the mainWebApp application and targets it to the examplesServer Administration Server.

Application Deployment

examplesWebApp

Adds the examplesWebApp application and targets it to the examplesServer Administration Server.

Application Deployment

entityBeanValidation

Adds the entityBeanValidation application and targets it to the examplesServer Administration Server.

Application Deployment

jsfBeanValidation

Adds the jsfBeanValidation application and targets it to the examplesServer Administration Server.

Application Deployment

cdi

Adds the cdi application and targets it to the examplesServer Administration Server.

Application Deployment

asyncMethodOfEJB

Adds the asyncMethodOfEJB Enterprise application and targets it to the examplesServer Administration Server.

Application Deployment

calendarStyledTimer

Adds the calendarStyledTimer application and targets it to the examplesServer Administration Server.

Application Deployment

noInterfaceViewInWAR

Adds the noInterfaceViewInWAR application and targets it to the examplesServer Administration Server.

Application Deployment

portableGlobalJNDIName

Adds the portableGlobalJNDIName application and targets it to the examplesServer Administration Server.

Application Deployment

singletonBean

Adds the singletonBean application and targets it to the examplesServer Administration Server.

Application Deployment

jaxrs

Adds the jaxrs application and targets it to the examplesServer Administration Server.

Application Deployment

stockAdapter

Adds the stockAdapter application and targets it to the examplesServer Administration Server.

Application Deployment

stockFrontEnd

Adds the stockFrontEnd application and targets it to the examplesServer Administration Server.

Application Deployment

stockBackEnd

Adds the stockBackEnd application and targets it to the examplesServer Administration Server.

Application Deployment

jdbcDataSource.war

Adds the jdbcDataSource.war application and targets it to the examplesServer Administration Server.

Application Deployment

criteriaQuery

Adds the criteriaQuery application and targets it to the examplesServer Administration Server.

Application Deployment

elementCollection

Adds the elementCollection application and targets it to the examplesServer Administration Server.

Application Deployment

ajaxJSF

Adds the ajaxJSF application and targets it to the examplesServer Administration Server.

Application Deployment

bookmarkingJSF

Adds the bookmarkingJSF application and targets it to the examplesServer Administration Server.

Application Deployment

faceletsJSF

Adds the faceletsJSF application and targets it to the examplesServer Administration Server.

Application Deployment

annotation

Adds the annotation application and targets it to the examplesServer Administration Server.

Application Deployment

asyncServlet30

Adds the asyncServlet30 application and targets it to the examplesServer Administration Server.

Application Deployment

multipartFileHandling

Adds the multipartFileHandling application and targets it to the examplesServer Administration Server.

Application Deployment

apache_xbean.jar

Adds the apache_xbean.jar application and targets it to the examplesServer Administration Server.

Application Deployment

annotation

Adds the annotation application and targets it to the examplesServer Administration Server.

JDBC System Resource

examples-demo

Identifies this JDBC data source, which has the following configuration:

  • JNDI name: examples-dataSource-demoPool

  • Global transaction protocol: Two Phase Commit

The connection pool settings are:

  • Initial capacity: 1

  • Maximum capacity: 10

JDBC System Resource

examples-demoXA

Identifies this JDBC data source, which has the following configuration:

  • JNDI Name: examples-dataSource-demoXAPool

  • Global transaction protocol: Two Phase Commit

The connection pool settings are:

  • Initial capacity: 2

  • Maximum capacity: 10

Deployed library

apache-xbean.jar

Adds the apache-xbean.jar library dependency to this domain.


WebLogic Server Examples Extension Template

Using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to create a WebLogic Server Examples domain. You accomplish this by adding the resources and services provided in both the WebLogic Server Default and WebLogic Server Examples extension templates to a base WebLogic Server domain.

For more information about the samples that are supported in the WebLogic Server Examples domain, see "Sample Application and Code Examples" in Understanding Oracle WebLogic Server.

Template Details

The following table provides basic information about the WebLogic Server Default Domain Extension template.

Template Dependencies lists all templates that provide resources required by the WebLogic Server Examples extension template, in the order in which they must be configured in the domain.

Table 2-18 WebLogic Server Examples Extension Information

Template DetailInformation

Template type

Extension

Template name in Configuration Wizard

This template is not available from the list of products in the Configuration Wizard. You can select it only by using the Browse option on the Select Domain Source or Select Extension Source screens, and navigating to the JAR file location.

Template JAR file and location

WL_HOME\common\templates\wls\wls_examples.jar

Template Dependencies

  • Basic WebLogic Server Domain template

  • + WebLogic Server Default Domain Extension template


Resources and Services Configured

In addition to the resources configured by the WebLogic Server Default Domain extension template (see Table 2-17), the WebLogic Server Examples extension template configures the resources and services listed in the following table.

Table 2-19 Additional Resources Configured by the WebLogic Server Examples Domain

Resource TypeNameNotes

Administration Server

AdminServer

Uses the Administration Server provided in the Basic WebLogic Server domain. The default name is AdminServer, unless changed during domain creation. The Administration Server is referenced in the template as @SERVER_NAME, and appears as AdminServer in the Administration Console.

The default configuration for the Administration Server is as follows:

  • Listen address: All Local Addresses

  • Listen port: 7001

  • SSL is disabled

For information about naming the Administration Server during domain creation, see Resources and Services Configured in a Basic WebLogic Server Domain.

Security realm

myrealm

Uses the security realm provided by the base WebLogic Server domain.

Application Deployment

SamplesSearchWebApp

Adds the application and targets it to the Administration Server.

JMS Server

examplesJMSServer

Adds this JMS server as an examples-jms system resource and targets it to the Administration Server.

  • Persistent Store: exampleJDBCStore

  • JMS Message log file: examplesJMSServer

JMS Server

WseeJMSServer

Adds this JMS server as an examples-jms system resource and targets it to the Administration Server.

This server is configured to use the WSeeFileStore persistent store.

File Store

WseeFileStore

Adds the file store to be used as the persistent store for the WSEEJMSServer JMS server and the ReliableWseeSAFAgent SAF Agent. This file store is targeted to the examplesServer Administration Server.

JDBC Store

exampleJDBCStore

Adds the JDBC store to be used as the persistent store for the examples-demo JDBC data source and the examplesJMSServer JMS server, and targets the store to the examplesServer Administration Server.

JMS System Resources

examples-jms

Identifies the JMS servers, connection factories, queues, and topics to be used for JMS system resources.

JMS Connection Factories

exampleTopic

exampleTrader

weblogic.examples.jms.QueueConnectionFactory

weblogic.examples.ejb30.QueueConnectionFactory

Adds these connection factories as examples-jms system resources and targets them to the examplesServer server.

JMS Queues

exampleQueue

jms/MULTIDATASOURCE_MDB_QUEUE

weblogic.examples.ejb30.ExampleQueue

Adds these JMS queues to the examplesJMSServer JMS server.

JMS Queue

weblogic.wsee.wseeExamplesDestinationQueue

Adds this JMS queue to the WseeJMSServer JMS server.

JMS Topics

exampleTopic

quotes

stockTopic

Adds these JMS topics and targets them to the examplesJMSServer JMS server.

JDBC System Resource

examples-oracleXA

Identifies this JDBC data source, which has the following configuration:

  • JNDI name: examples-dataSource-oracleXAPool

  • Global transaction protocol: Two Phase Commit

The database driver is configured as oracle.jdbc.xa.client.OracleXADataSource.

This data source is mapped to the examples-multiDataSource-demoXAPool multi data source.

JDBC System Resource

examples-demoXA-2

Identifies this JDBC data source, which is targeted to the Administration Server and has the following configuration:

  • Connection pool maximum: 100

  • Global transaction protocol: Two Phase Commit

This data source is mapped to the examples-multiDataSource-demoXAPool multi data source.

JDBC System Resource

examples-multiDataSource-demoXAPool

Identifies this JDBC multi data source, which is targeted to the Administration Server. It is configured for failover, and maps to the examples-oracleXA and examples-demo-XA-2 data sources.

SAF Agent

ReliableWseeSAFAgent

Adds this store-and-forward agent, which uses the WseeFileStore file store, and targets it to the Administration Server.

Work Manager

weblogic.wsee.mdb.DispatchPolicy

Adds this Work Manager, but does not target it to any servers.


PKgvVBPK:zDOEBPS/preface.htmL Preface

Preface

This preface describes the document accessibility features and conventions used in this guide, Oracle Fusion Middleware Domain Template Reference.

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 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.

Conventions

The following text conventions are used in this document:

ConventionMeaning

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.


PK~*QLPK:zD OEBPS/toc.ncx! Oracle® Fusion Middleware Domain Template Reference, 12c (12.1.2) Cover Title and Copyright Information Contents Preface 1 Introduction 2 WebLogic Server Templates 3 Fusion Middleware Product Templates Copyright PK%39PK:zDOEBPS/content.opf M Oracle® Fusion Middleware Domain Template Reference, 12c (12.1.2) en-US E28064-01 Oracle Corporation Oracle Corporation Oracle® Fusion Middleware Domain Template Reference, 12c (12.1.2) 2013-06-03T13:04:43Z This document provides information about WebLogic domain and extension templates, which are Java archive (JAR) files that contain the files and scripts required to create or extend a WebLogic domain. PKܭ PK:zDOEBPS/dcommon/oracle-logo.jpgkzJFIFC    $.' ",#(7),01444'9=82<.342C  2!!22222222222222222222222222222222222222222222222222'7" }!1AQa"q2#BR$3br %&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz w!1AQaq"2B #3Rbr $4%&'()*56789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz ?( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( (QEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQE!KEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEzE7V%ȣOΏ9??:a"\fSrğjAsKJ:nOzO=}E1-I)3(QEQEQEQEQEQEQE֝Hza<["2"pO#f8M[RL(,?g93QSZ uy"lx4h`O!LŏʨXZvq& c՚]+: ǵ@+J]tQ]~[[eϸ (]6A&>ܫ~+כzmZ^(<57KsHf妬Ϧmnẁ&F!:-`b\/(tF*Bֳ ~V{WxxfCnMvF=;5_,6%S>}cQQjsOO5=)Ot [W9 /{^tyNg#ЄGsֿ1-4ooTZ?K Gc+oyڙoNuh^iSo5{\ܹ3Yos}$.nQ-~n,-zr~-|K4R"8a{]^;I<ȤL5"EԤP7_j>OoK;*U.at*K[fym3ii^#wcC'IIkIp$󿉵|CtĈpW¹l{9>⪦׺*ͯj.LfGߍԁw] |WW18>w.ӯ! VӃ :#1~ +މ=;5c__b@W@ +^]ևՃ7 n&g2I8Lw7uҭ$"&"b eZ":8)D'%{}5{; w]iu;_dLʳ4R-,2H6>½HLKܹR ~foZKZ࿷1[oZ7׫Z7R¢?«'y?A}C_iG5s_~^ J5?œ tp]X/c'r%eܺA|4ծ-Ե+ْe1M38Ǯ `|Kյ OVڅu;"d56, X5kYR<̭CiطXԮ];Oy)OcWj֩}=܅s۸QZ*<~%뺃ȶp f~Bðzb\ݳzW*y{=[ C/Ak oXCkt_s}{'y?AmCjޓ{ WRV7r. g~Q"7&͹+c<=,dJ1V߁=T)TR՜*N4 ^Bڥ%B+=@fE5ka}ędܤFH^i1k\Sgdk> ֤aOM\_\T)8靠㡮3ģR: jj,pk/K!t,=ϯZ6(((((((49 xn_kLk&f9sK`zx{{y8H 8b4>ÇНE|7v(z/]k7IxM}8!ycZRQ pKVr(RPEr?^}'ðh{x+ՀLW154cK@Ng C)rr9+c:׹b Жf*s^ fKS7^} *{zq_@8# pF~ [VPe(nw0MW=3#kȵz晨cy PpG#W:%drMh]3HH<\]ԁ|_W HHҡb}P>k {ZErxMX@8C&qskLۙOnO^sCk7ql2XCw5VG.S~H8=(s1~cV5z %v|U2QF=NoW]ո?<`~׮}=ӬfԵ,=;"~Iy7K#g{ñJ?5$y` zz@-~m7mG宝Gٱ>G&K#]؃y1$$t>wqjstX.b̐{Wej)Dxfc:8)=$y|L`xV8ߙ~E)HkwW$J0uʟk>6Sgp~;4֌W+חc"=|ř9bc5> *rg {~cj1rnI#G|8v4wĿhFb><^ pJLm[Dl1;Vx5IZ:1*p)إ1ZbAK(1ׅ|S&5{^ KG^5r>;X׻K^? s fk^8O/"J)3K]N)iL?5!ƾq:G_=X- i,vi2N3 |03Qas ! 7}kZU781M,->e;@Qz T(GK(ah(((((((Y[×j2F}o־oYYq $+]%$ v^rϭ`nax,ZEuWSܽ,g%~"MrsrY~Ҿ"Fت;8{ѰxYEfP^;WPwqbB:c?zp<7;SBfZ)dϛ; 7s^>}⍱x?Bix^#hf,*P9S{w[]GF?1Z_nG~]kk)9Sc5Ո<<6J-ϛ}xUi>ux#ţc'{ᛲq?Oo?x&mѱ'#^t)ϲbb0 F«kIVmVsv@}kҡ!ˍUTtxO̧]ORb|2yԵk܊{sPIc_?ħ:Ig)=Z~' "\M2VSSMyLsl⺿U~"C7\hz_ Rs$~? TAi<lO*>U}+'f>7_K N s8g1^CeКÿE ;{+Y\ O5|Y{/o+ LVcO;7Zx-Ek&dpzbӱ+TaB0gNy׭ 3^c T\$⫫?F33?t._Q~Nln:U/Ceb1-im WʸQM+VpafR3d׫é|Aү-q*I P7:y&]hX^Fbtpܩ?|Wu󭏤ʫxJ3ߴm"(uqA}j.+?S wV ~ [B&<^U?rϜ_OH\'.;|.%pw/ZZG'1j(#0UT` Wzw}>_*9m>󑓀F?EL3"zpubzΕ$+0܉&3zڶ+jyr1QE ( ( ( ( ( ( ( (UIdC0EZm+]Y6^![ ԯsmܶ捆?+me+ZE29)B[;я*wGxsK7;5w)}gH~.Ɣx?X\ߚ}A@tQ(:ͧ|Iq(CT?v[sKG+*רqҍck <#Ljα5݈`8cXP6T5i.K!xX*p&ќZǓϘ7 *oƽ:wlຈ:Q5yIEA/2*2jAҐe}k%K$N9R2?7ýKMV!{W9\PA+c4w` Wx=Ze\X{}yXI Ү!aOÎ{]Qx)#D@9E:*NJ}b|Z>_k7:d$z >&Vv󃏽WlR:RqJfGإd9Tm(ҝEtO}1O[xxEYt8,3v bFF )ǙrPNE8=O#V*Cc𹾾&l&cmCh<.P{ʦ&ۣY+Gxs~k5$> ӥPquŽўZt~Tl>Q.g> %k#ú:Kn'&{[yWQGqF}AЅ׮/}<;VYZa$wQg!$;_ $NKS}“_{MY|w7G!"\JtRy+贾d|o/;5jz_6fHwk<ѰJ#]kAȎ J =YNu%dxRwwbEQEQEQEQEQEQEQEQEQE'fLQZ(1F)hQ@X1KEQE-Q@ 1KE3h=iPb(((1GjZ(-ʹRPbR@ 1KE7`bڒyS0(-&)P+ ڎԴP11F)h&:LRmQ@Q@Š(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((?l:ϊw "{{-3j3%{+Zoi.{YUڪ1kcMմfݮ4Br%*8%I.QT-[MѭT-,`g]L)lXqjV4Ķ%ѡ')$r_Ĭ AVuoż9#`FApA+麶۵ƗZ_@QeP#8 Uh燮,/jXJ}9Q]рN:]dko-ıH^I$`I$$:[zޛ}:v%`$)' gVko-ıH^I$`I$$..3D ?+pcV4[MmK-/W(Z̲lTq(Q@'94 >SJJFCI'L~yᵷX$/$0UE$xs@U{=2K--cFI,٬|Cό<)a-8nQǰ_VBNM>rE+/uoż9#`FApA椬 eq-"mV89 Wcag]E7dt&i5j K%-p 3N=\o?:evjh$#b9#hɫirLiJ*+rcTY2K;iVQ|3@#*NFA7'u@yi}ŭim=춎if@NXr???6޽ +/R.\-3X&+2qF}\㼰L $0? ESVf&-P7h)Y3>e֍KVtku5 K,S,J[ g{EG[qo,sA*H2AG9z\][j3>˘]lNTC@(O]O+[U"ߌg2:zMմfݮ4Br%*8%I.QU9//വA.H,x$ƩxAn/u6 m$H2' 0zZԢxn⸷9$l]H #<4Ķ%ѡ')$r_Ĭ APQ@Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@'K|U].VCyCO#GUH~9Й>/CcaSm(߇-'-ZoDQ03u]W?O5 `!ºv__Avڄ3Agw?±kc+[O?o?DA9Oz炼+OF$}_FZQ*a6OOY?u98we2٬32xvwt'S-@䯖xl9qyVOeX{Mw:!Udf_wYߝFv()9OIaY?TU1?\8wjiP:ʹ4ږEHKH|TW7gnזZeݕď@H|I%Y 'mcxⷆ|?᫻ kM/g-)nNGs^yi0>Dx0sEn݂2(/ľ|M߬lVviuCpCo+2x[ŧq9ݑTh6>``8d;ς_Ht/x҉+%O`(x]|Y=c9o-hX YK'kdzjok$ZvdfCb +89?g'dQU}|OX)oVWo{ab]!۴NҩKyK55oP_yf.$s8⻏Huw҈%Oow:֥H.FBER 3+|8ߎd~&,rȉW*I!qjH RFHдzfy?nVn7ۅ݌9EpwHݻw@8ɠ#'h%ԮoIjڅ<1\DY@FFPT\fx?ڤq +0,. 9fʧR9+o\kSi2^ ^0-+0eh|,V4+Jj|1"d>wpp0';@=ow:oú_Ϫ_E(w Hc]O`HpzHuw҈' *E-yW췚=/T@n/n_ rF ݆j|K6NQ6dg cՠC񆯥Ϫz(Ǩ Cs}qe,7cᯀwPiI}Zh\`fB `(vqQ@{,Kk`@+(I"q+䳿LoxĈ  Eps}sq,Gs2($WGXYqZAikvCb4\Np2I?X17m:t-d漙r'.I·N{ ^ V2gi z`0օ <j)h%`$l DX0Ñ]E\^GZD̛܌a'X3MN \[bǖ$I[}d[7m`Õ @<Т+Xu~]I )<:?^U4H'fFxd 7g]Eǿ7 b+KH{Hn' (u . #" d"0QӰZ؋,5m" {Vi6@HNLztP>m^tNϺu*s QzlQEq:t.$;$a(f$֦xYt]7J[q #egzA[P{}ON̵7#OJ߅oXhvdS3'e'ʶ(UOukjv>_]1'kFڞ= Ff"tݱ'd@*7YFlVQ1TEwq)io|  ¡V׏Z?6j'o60b 1pG`d|t>4ռ x; "huKeL|k.0 _D>-o5+i*"3P6n۔`CtW/v>[ͣ^cj6&Ɠi,y+y\ -ī@MP9&lg%YK<HM{q~CIhc3dJ7oޛOM]kZ}TO4K#pi7H2&8;~!n(iEKQ8x-S!n<C! ;{% .x_y2jpX[Ť䈐UY#s(@Idƾ׼Q{RРKuCv y"tyg<5 xO,rro2yTt=GGnݛKܾ—qvܲ.A`'$zEg+_4}fLN+Mj@i}*GpveeO_D>-o5+i*"3P6n۔`CtW|:❅ejQ6բUݙAm9(c;pg ӟPе+G)d`<n0)" 1mE|b]nWyjpv90q[߳侰&|J1:^(.p-ĮschA%wGτ>(ּ?ykHpl B`0OՉٸCaQn((;5ϮxM#VG*&|pnARr|U!kբy7 qp*00b#M]KǞ5H-!+׷UFU*'s1\,>oEm}FY#nٝ]g'ik>|&|y[STԡ+׷UJF܌s=(+m|5WZE\| TvUf?w;p$Wa::έ:Ș30d`Q^Z%h}j{ {[KNs a$|_p((((((((((((((((%O`?_4`ֹ>gGEo\3%gW񕿌/+[`̑.PX)rC!;DDWi M7 I_,,(ǀҷ<7 xG:d4i$ +m(;s5P>#}Co$kwgun-AX8e]÷QT|M|?Lw6ca ꩒0I ZϥcMeUq9$DŽ~[{el|$1_.F3/CcaSm+'k:{=shX]BnFI#1u5P ;£FWAInQnxoZowTI\ΥQ;a0Rz ×zku{8:@OY?g?Ef_ #0o`#9Y9/ވlRRmNZ6T1rkPbi%I.)$c 9;ul7Jz0l`Esd%ݯi <%X1p:?t>T vk ]{y&[O_% ,Kji0{X[xW_( ۜ~ $O*Z k7ǚ4:^=0Ep ֮łVÞޕP{Nş A`nZm5E=/żTmvI PTz I7΅^w--PۑRHcMt/ Wݎ֗*Ԁ>SgВ8.i)M֬c.cXt*ASd#4~ WfTFAG5|/9/58f8n%yTWE(FpOXp~ξ )^Y4R\F?t}H<9x[K]7E9}KcԳ1%AOP ;£FWAInQnxoZowTI\ΥQ;a0Rz ×zku{8:@ $_ K^: *OSIaѴk.ݤh,㷍 TP3+Zm4K=,-ͼQTXmx?/_αgWEP9M@, N'KsKӴ95#!1 m*Fwg#rkmX럴oN;;D'm8 AZ> O>oO/9ٝ㏽GJ |cⵊHoS/f)W*#{cr Xv?P'TۊM+J}3L6EtQ'$$k~ |/뺥rO\}fu*  zPK?#L-"P (\J&wYͬB.| ^Ju+ODݦ2cj 'ܒ5~&uo]Z29 *A\899߀~ ӢW['InV0nVRd @_W77 xSYc3Z(’:J^o GÖkkc$:\_~C:g=ô-Fbz8#^j Z[4?d1tb8UxOKK^f%'9V8$s^5n4VX(PNz?jDnUXI!][o\ap(.|9^Կ\Ys4=TGnxc9" |+."ӬPԅp8E8r2;QEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQ^Wwľ(ѵ ~㱟WݚHQԶ ܬ@A߽Sg 6}Z?ϒ/^{5N?WeX/-~n { ܲ6d滊((#xT @drJ[ p9<)okin1GZ(((((((((Sqxr YA{ϳ9.K/EzlQ^}~!blm!#bI!Sqm%~i 5!A~u^o믉W!Ҽo>TRj2|"̙@UbK=@<ަ~6NMnWѵKDy.-4Fvd[9f=?^ZO+Mp pH R8 ( (+յ/i.epѭ$a*`_ܞrV?n5O](/uux' #6Ie軏Q?YK]wPE66JyL$ېǩ(7īi^ *)n5Q>FgJL* HOS?|'e&uͥ<#Ļ~2@p3^Y՚y^nRh hdSRGFpJ8tQ\ߍo|WcC/MCP7 EtTE. :Nm|s]GoW-TH,|CJ %~R6$r?6Q^gnZi>3.2SQ[\@ܤN܄-c,/=:O2$F` FAhQ@Q@Q@Q@Q@Q@Q@Q@Q@Q@/Lë<[]AKrJ/:I'q ;uU$t3A ׎KI]L+~7V,úm6,geu\zA"9?^ŗ_bZ Fx)p|J񾣠g}jUΣp[X u+;_>96pBrRNJȸ-stoxj]rOZ]YhdcdVYHE,HrshP+ug597maIP:SH\z.u=G\y@2O#ڿ(pVD[?럔~< o Ylޡ5d"% ̻ďܕ5oƥ>udū06cxN>F=}\\{ ~S5˔F`.cU8ӎpC'C?IUsA5bx8ex/g]߇L cBv+ RfWcZNj OwXm/TG;2.UK;fݍ}+ᯈu.S>176w )PM AAb>%е-kޤW-3e"FD-1+'|qk> }NB镡ڎApI#޴4~:}fZ׾"]G-ͅQ0ȸeQݎI4/CcaSm(]ŗ~ ڋ#SՙfR_2$>aRA\0S 9=O|6Owv\7%i%ve$nNp5$+;z/ \j%쒙 Xѐy둎+jEE@z橦j)nr :Uw$` \0x^֯#M#*q1+h'cRՏsA5bx8c>8E}Ȗ[K]8LYG@8*A%؂F+< szG R&_d3y*]^+?vZﵻeLJ窶 #<EhP:~(Km?~s+.dP2aO]oVxM޻nI1\ 8#,U\?mz}ۭΕl\S&RUVFqrygWV|TfT)$r$` 1@nkM`^[A pU< Ԯo:>F10DơVU@@ ~9]%QEx( *m{x( *m{Ŗ~ ֵxoiT1VF*7^/>^&kNaww5ݸD[sg<}vڔ7 Y\Mo)`0X+M( ^?J o^^?J o@E~yxU^^W=v8?$ i?x^ZO7Cp4p IHP_w4t߼ԥ70>DuPsEn݂2+dž5OZ>5V:FܡCw U>@Q@?: *O꽂?t>T {QQ<6\K0DF dOhxmm常8` $Q@$׏,c#?K]>t]>) 9 IHX~4ﯵO:V$ ^U!OgbdҴK4hdQ'E̒rIHpvfDv~:[{ PȡԌA8IExOn&]Kx>H,@ܮ qs][z姈5m{Uuh(/&;6%`3zy6۝ogvQ@_?  np~9/zg0|A{Ȍ#H \29X[z. KT*cnf$f'Ա'xqX< O붹|+D]s޻ (_X~ݭϛy:sO7VEJ$E `*J(~q7g2[ŹAbt%@lۈ瓚< OCssk/pLK +cn]9OQYHbRgqR A,`0e#mJ&Oj|l2z}r˞K VYROl,Q">y;WF6iė7E " 2}OQ@cG׼9wXj7Sl{wŇV8):Ex{P\hݡl&lʃ=+W5 3^8Եݢ[kQ)7H )?] &myûn1՟ Vuo?^Es~ ޥ}k-S7zpҭmȥTlRzsKmy>Ŵg\Y@`G$((+~jQk67 泭AcqU#w1`y;P^?ŶyׇK񏺋ڡ NyxrLէnٲ qSuk>kڅŭĝJ{Gm$ d3eNTA^Ep~ &}fkS۴Kmtj1e;d#k/?X!տ~-O78wm޿1ڽBT0~S<K4Zn[ۑJ7;#tPx5ohm?#^Cv}nnxz4hlS6:au8%#(V6/ĝISdWmnT^xWy_o~_ntvP4hm?#>fDv~}'GMG#n_9]?|IYga;U;!#E$D$ƺx^5K]%t25Q@_YӼ>uJ"}+p~fmrN ,gHM,Iluf9$I (((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((PKӧOߊkkPK:zDOEBPS/dcommon/cpyr.htmD Oracle Legal Notices

Oracle Legal Notices

Copyright Notice

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

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.

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, 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.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on 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. 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.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction 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.

Oracle Logo

PK0hPK:zDOEBPS/dcommon/oracle.gifJGIF87aiyDT2F'G;Q_oKTC[ 3-Bq{ttsoGc4I)GvmLZ).1)!ꑈ53=Z]'yuLG*)g^!8C?-6(29K"Ĩ0Яl;U+K9^u2,@@ (\Ȱ Ë $P`lj 8x I$4H *(@͉0dа8tA  DсSP v"TUH PhP"Y1bxDǕ̧_=$I /& .)+ 60D)bB~=0#'& *D+l1MG CL1&+D`.1qVG ( "D2QL,p.;u. |r$p+5qBNl<TzB"\9e0u )@D,¹ 2@C~KU 'L6a9 /;<`P!D#Tal6XTYhn[p]݅ 7}B a&AƮe{EɲƮiEp#G}D#xTIzGFǂEc^q}) Y# (tۮNeGL*@/%UB:&k0{ &SdDnBQ^("@q #` @1B4i@ aNȅ@[\B >e007V[N(vpyFe Gb/&|aHZj@""~ӎ)t ? $ EQ.սJ$C,l]A `8A o B C?8cyA @Nz|`:`~7-G|yQ AqA6OzPbZ`>~#8=./edGA2nrBYR@ W h'j4p'!k 00 MT RNF6̙ m` (7%ꑀ;PKl-OJPK:zDOEBPS/dcommon/doccd_epub.jsM /* Copyright 2006, 2012, Oracle and/or its affiliates. All rights reserved. Author: Robert Crews Version: 2012.3.17 */ function addLoadEvent(func) { var oldOnload = window.onload; if (typeof(window.onload) != "function") window.onload = func; else window.onload = function() { oldOnload(); func(); } } function compactLists() { var lists = []; var ul = document.getElementsByTagName("ul"); for (var i = 0; i < ul.length; i++) lists.push(ul[i]); var ol = document.getElementsByTagName("ol"); for (var i = 0; i < ol.length; i++) lists.push(ol[i]); for (var i = 0; i < lists.length; i++) { var collapsible = true, c = []; var li = lists[i].getElementsByTagName("li"); for (var j = 0; j < li.length; j++) { var p = li[j].getElementsByTagName("p"); if (p.length > 1) collapsible = false; for (var k = 0; k < p.length; k++) { if ( getTextContent(p[k]).split(" ").length > 12 ) collapsible = false; c.push(p[k]); } } if (collapsible) { for (var j = 0; j < c.length; j++) { c[j].style.margin = "0"; } } } function getTextContent(e) { if (e.textContent) return e.textContent; if (e.innerText) return e.innerText; } } addLoadEvent(compactLists); function processIndex() { try { if (!/\/index.htm(?:|#.*)$/.test(window.location.href)) return false; } catch(e) {} var shortcut = []; lastPrefix = ""; var dd = document.getElementsByTagName("dd"); for (var i = 0; i < dd.length; i++) { if (dd[i].className != 'l1ix') continue; var prefix = getTextContent(dd[i]).substring(0, 2).toUpperCase(); if (!prefix.match(/^([A-Z0-9]{2})/)) continue; if (prefix == lastPrefix) continue; dd[i].id = prefix; var s = document.createElement("a"); s.href = "#" + prefix; s.appendChild(document.createTextNode(prefix)); shortcut.push(s); lastPrefix = prefix; } var h2 = document.getElementsByTagName("h2"); for (var i = 0; i < h2.length; i++) { var nav = document.createElement("div"); nav.style.position = "relative"; nav.style.top = "-1.5ex"; nav.style.left = "1.5em"; nav.style.width = "90%"; while (shortcut[0] && shortcut[0].toString().charAt(shortcut[0].toString().length - 2) == getTextContent(h2[i])) { nav.appendChild(shortcut.shift()); nav.appendChild(document.createTextNode("\u00A0 ")); } h2[i].parentNode.insertBefore(nav, h2[i].nextSibling); } function getTextContent(e) { if (e.textContent) return e.textContent; if (e.innerText) return e.innerText; } } addLoadEvent(processIndex); PKo"nR M PK:zDOEBPS/dcommon/blafdoc.cssc@charset "utf-8"; /* Copyright 2002, 2011, Oracle and/or its affiliates. All rights reserved. Author: Robert Crews Version: 2011.10.7 */ body { font-family: Tahoma, sans-serif; /* line-height: 125%; */ color: black; background-color: white; font-size: small; } * html body { /* http://www.info.com.ph/~etan/w3pantheon/style/modifiedsbmh.html */ font-size: x-small; /* for IE5.x/win */ f\ont-size: small; /* for other IE versions */ } h1 { font-size: 165%; font-weight: bold; border-bottom: 1px solid #ddd; width: 100%; text-align: left; } h2 { font-size: 152%; font-weight: bold; text-align: left; } h3 { font-size: 139%; font-weight: bold; text-align: left; } h4 { font-size: 126%; font-weight: bold; text-align: left; } h5 { font-size: 113%; font-weight: bold; display: inline; text-align: left; } h6 { font-size: 100%; font-weight: bold; font-style: italic; display: inline; text-align: left; } a:link { color: #039; background: inherit; } a:visited { color: #72007C; background: inherit; } a:hover { text-decoration: underline; } a img, img[usemap] { border-style: none; } code, pre, samp, tt { font-family: monospace; font-size: 110%; } caption { text-align: center; font-weight: bold; width: auto; } dt { font-weight: bold; } table { font-size: small; /* for ICEBrowser */ } td { vertical-align: top; } th { font-weight: bold; text-align: left; vertical-align: bottom; } ol ol { list-style-type: lower-alpha; } ol ol ol { list-style-type: lower-roman; } li { text-align: left; } dd { text-align: left; } td p:first-child, td pre:first-child { margin-top: 0px; margin-bottom: 0px; } table.table-border { border-collapse: collapse; border-top: 1px solid #ccc; border-left: 1px solid #ccc; } table.table-border th { padding: 0.5ex 0.25em; color: black; background-color: #f7f7ea; border-right: 1px solid #ccc; border-bottom: 1px solid #ccc; } table.table-border td { padding: 0.5ex 0.25em; border-right: 1px solid #ccc; border-bottom: 1px solid #ccc; } span.gui-object, span.gui-object-action { font-weight: bold; } span.gui-object-title { } p.horizontal-rule { width: 100%; border: solid #cc9; border-width: 0px 0px 1px 0px; margin-bottom: 4ex; } div.zz-skip-header { display: none; } td.zz-nav-header-cell { text-align: left; font-size: 95%; width: 99%; color: black; background: inherit; font-weight: normal; vertical-align: top; margin-top: 0ex; padding-top: 0ex; } a.zz-nav-header-link { font-size: 95%; } td.zz-nav-button-cell { white-space: nowrap; text-align: center; width: 1%; vertical-align: top; padding-left: 4px; padding-right: 4px; margin-top: 0ex; padding-top: 0ex; } a.zz-nav-button-link { font-size: 90%; } div.zz-nav-footer-menu { width: 100%; text-align: center; margin-top: 2ex; margin-bottom: 4ex; } p.zz-legal-notice, a.zz-legal-notice-link { font-size: 85%; /* display: none; */ /* Uncomment to hide legal notice */ } /*************************************/ /* Begin DARB Formats */ /*************************************/ .bold, .codeinlinebold, .syntaxinlinebold, .term, .glossterm, .seghead, .glossaryterm, .keyword, .msg, .msgexplankw, .msgactionkw, .notep1, .xreftitlebold { font-weight: bold; } .italic, .codeinlineitalic, .syntaxinlineitalic, .variable, .xreftitleitalic { font-style: italic; } .bolditalic, .codeinlineboldital, .syntaxinlineboldital, .titleinfigure, .titleinexample, .titleintable, .titleinequation, .xreftitleboldital { font-weight: bold; font-style: italic; } .itemizedlisttitle, .orderedlisttitle, .segmentedlisttitle, .variablelisttitle { font-weight: bold; } .bridgehead, .titleinrefsubsect3 { font-weight: bold; } .titleinrefsubsect { font-size: 126%; font-weight: bold; } .titleinrefsubsect2 { font-size: 113%; font-weight: bold; } .subhead1 { display: block; font-size: 139%; font-weight: bold; } .subhead2 { display: block; font-weight: bold; } .subhead3 { font-weight: bold; } .underline { text-decoration: underline; } .superscript { vertical-align: super; } .subscript { vertical-align: sub; } .listofeft { border: none; } .betadraft, .alphabetanotice, .revenuerecognitionnotice { color: #e00; background: inherit; } .betadraftsubtitle { text-align: center; font-weight: bold; color: #e00; background: inherit; } .comment { color: #080; background: inherit; font-weight: bold; } .copyrightlogo { text-align: center; font-size: 85%; } .tocsubheader { list-style-type: none; } table.icons td { padding-left: 6px; padding-right: 6px; } .l1ix dd, dd dl.l2ix, dd dl.l3ix { margin-top: 0ex; margin-bottom: 0ex; } div.infoboxnote, div.infoboxnotewarn, div.infoboxnotealso { margin-top: 4ex; margin-right: 10%; margin-left: 10%; margin-bottom: 4ex; padding: 0.25em; border-top: 1pt solid gray; border-bottom: 1pt solid gray; } p.notep1 { margin-top: 0px; margin-bottom: 0px; } .tahiti-highlight-example { background: #ff9; text-decoration: inherit; } .tahiti-highlight-search { background: #9cf; text-decoration: inherit; } .tahiti-sidebar-heading { font-size: 110%; margin-bottom: 0px; padding-bottom: 0px; } /*************************************/ /* End DARB Formats */ /*************************************/ @media all { /* * * { line-height: 120%; } */ dd { margin-bottom: 2ex; } dl:first-child { margin-top: 2ex; } } @media print { body { font-size: 11pt; padding: 0px !important; } a:link, a:visited { color: black; background: inherit; } code, pre, samp, tt { font-size: 10pt; } #nav, #search_this_book, #comment_form, #comment_announcement, #flipNav, .noprint { display: none !important; } body#left-nav-present { overflow: visible !important; } } PKT' hcPK:zD OEBPS/toc.htm+ Table of Contents

Contents

Preface

1 Introduction

2 WebLogic Server Templates

3 Fusion Middleware Product Templates

PKknPK :zDoa,mimetypePK:zDTO:iTunesMetadata.plistPK:zDYuMETA-INF/container.xmlPK:zD@t` OEBPS/cover.htmPK:zDFHOEBPS/title.htmPK:zDIJV!-#8OEBPS/fmw_templates.htmPK:zD!zDUKOEBPS/intro.htmPK:zDgvVB<OEBPS/templates.htmPK:zD~*QLQOEBPS/preface.htmPK:zD%39 caOEBPS/toc.ncxPK:zDܭ hOEBPS/content.opfPK:zDӧOߊkkwsOEBPS/dcommon/oracle-logo.jpgPK:zD0hLOEBPS/dcommon/cpyr.htmPK:zDl-OJPOEBPS/dcommon/oracle.gifPK:zDo"nR M OEBPS/dcommon/doccd_epub.jsPK:zDT' hcOEBPS/dcommon/blafdoc.cssPK:zDkn /OEBPS/toc.htmPKRC: