Oracle Fusion Middleware Domain Template Reference, 11g Release 1 (10.3.6)

11g Release 1 (10.3.6)

E14138-11

Contents

Title and Copyright Information

Preface

- Documentation Accessibility

- Conventions

1 Introduction

- Types of Templates

- Location of Installed WebLogic Server Templates

- Template Tools

- Template Dependencies

- Files Typically Included in a Template

2 WebLogic Server Templates

- Basic WebLogic Server Domain Template

- Template Details

- Resources and Services Configured in a Basic WebLogic Server Domain

- Generated Domain Output

- WebLogic Server Starter Domain Template

- Template Details

- Resources and Services Configured in a WebLogic Server Starter Domain

- Generated Domain Output

- WebLogic Advanced Web Services Extension Template

- Template Details

- Resources and Services Configured

- Generated Domain Output

- WebLogic Advanced Web Services for JAX-WS Extension Template

- Template Details

- Resources and Services Configured

- Avitek Medical Records Sample Domain Template

- Template Details

- Resources and Services Configured

- Generated Domain Output

- Avitek Medical Records Sample Domain Template (Spring Version)

- Template Details

- Resources and Services Configured

- Generated Domain Output

- WebLogic Server Default Domain Extension Template

- Template Details

- Resources and Services Configured

- Generated Domain Output

- WebLogic Server Examples Extension Template

- Template Details

- Resources and Services Configured

- Generated Domain Output

3 Fusion Middleware Product Templates

- Enterprise Manager Templates

- Oracle Enterprise Manager

- Enterprise Content Management Templates

- Oracle WebCenter Content Core Template

- Oracle Universal Content Management - Content Server Template

- Oracle Universal Records Management Template

- Oracle Information Rights Management (IRM) Template

- Oracle WebCenter Content: Imaging Template

- Oracle Universal Content Management - Inbound Refinery Template

- Oracle SOA Suite Templates

- Oracle SOA Suite Template

- Oracle Business Activity Monitor Template

- Oracle Business Rules Extension Template

- Oracle User Messaging Service for SOA Template

- Oracle SOA Suite for Developers Template

- Oracle Web Service Manager (OWSM) Templates

- Oracle WSM Policy Manager Template

- Oracle Service Bus Templates

- Oracle Service Bus for developers Template (Admin-only Topology)

- Oracle Service Bus Template (Cluster and Managed Server Topologies)

- Oracle Service Bus OWSM Extension Template

- Oracle User Messaging Service Templates

- Oracle User Messaging Service Template

- Oracle User Messaging Service Drivers Template

- Oracle User Messaging Service Worklist Driver Template

- Oracle WebLogic Communications Service Client Library Extension Template

- Oracle WebCenter Portal Templates

- Oracle WebCenter Spaces Template

- Oracle Portlet Producers Template

- Oracle WebCenter Discussion Server Template

- Oracle WebCenter Custom Portal Template

- Oracle WebCenter Custom Services Producer Template

- Oracle WebCenter Analytics Template

- Oracle WebCenter Activity Graph Template

- Oracle WebCenter Pagelet Producer Template

- Oracle WebCenter Personalization Server Template

- Oracle WebCenter Services Portlets Template

- Oracle Identity Management Templates

- Oracle IDM Common Template

- Oracle Adaptive Access Manager Admin Server Template

- Oracle Adaptive Access Manager - Server Template

- Oracle Adaptive Access Manager Offline Template

- Oracle Access Manager with Database Policy Store Template

- Oracle Identity Manager Template

- Oracle Entitlements Server Template

- Oracle Authorization Policy Manager Template (Apache Derby)

- Oracle Entitlements Server WebLogic Security Module Template

- Oracle Identity Navigator Template

- Oracle Data Integrator Templates

- Oracle Data Integrator Agent Template

- Oracle Data Integrator Agent Libraries Template

- Oracle Data Integrator Console Template

- Oracle Data Integrator SDK Web Services Template

- Oracle Data Integrator SDK Shared Library Template

- Oracle Enterprise Manager Plugin for ODI Template

- Oracle JRF and JSF Templates

- Oracle JRF Template

- Oracle JRF Asynchronous Web Services Template

- JSFDomain Template

Oracle® Fusion Middleware

Domain Template Reference

11g Release 1 (10.3.6)

E14138-11

November 2011

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, 11g Release 1 (10.3.6)

E14138-11

Copyright © 2007, 2011, 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 RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

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

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

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

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

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:

Convention

Meaning

boldface

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

italic

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

monospace

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

1 Introduction

This 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

- Location of Installed WebLogic Server Templates

- Template Tools

- Template Dependencies

- Files Typically Included in a Template

Types of Templates

The types of template include:

- Domain template—defines the full set of resources within a domain, including infrastructure components, applications, services, security options, and general environment and operating system options.
The WebLogic Server product installation includes a predefined Basic WebLogic Server Domain template. This template defines the core set of resources within a WebLogic domain, including an Administration Server and basic configuration information. For more information on the Basic WebLogic Server Domain template, see Basic WebLogic Server Domain Template.

You can create a custom domain template from an existing domain by using the Domain Template Builder or the pack command. You can also create a domain template from an existing domain template by using the Domain Template Builder.

- Extension template—defines the applications and services that you can add to an existing domain, including product component functionality and resources such as JDBC or JMS.
The WebLogic Server product installation includes several predefined extension templates. The templates that are available to you in the Configuration Wizard depend on the product you are installing. WebLogic Server installations include the templates described in WebLogic Server Templates.

You can create a custom extension template from an existing domain or template by using the Domain Template Builder.

- Managed Server template – defines the subset of resources within a domain that are required to create a Managed Server domain directory on a remote machine.
You can create a custom Managed Server template by using the pack command. For more information, see Creating Templates and Domains Using the Pack and Unpack Commands.

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 Template

Directory Location

Domain

WL_HOME\common\templates\domains

Extension

WL_HOME\common\templates\applications

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

To

Use 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

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

Note:

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

- For information about using the Configuration Wizard, see Creating Domains Using the Configuration Wizard.

- For information about using the WLST Offline, see Oracle WebLogic Scripting Tool.

- For information about using the pack/unpack commands, see Creating Templates and Domains Using the Pack and Unpack Commands.

- For information about using the Domain Template Builder, see Creating Domain Templates Using the Domain Template Builder.

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.

When you select an extension template by selecting the associated product (if listed) on the Configuration Wizard Select Domain Source or Select Extension Source screens, the Configuration Wizard automatically selects all other products that configure resources required by the product you selected.

When you select a template by browsing to and selecting the JAR file, a Dependency warning is displayed if the template depends on resources that are provided by other domain or extension templates that have not yet been configured in the domain you are extending.

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 all domain and extension templates.

Table 1-3 Files Included in a Template

Filename

Description

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.

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.

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.

startmenu.xml

Used to create Windows Start menu entries.

startscript.xml

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

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.

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

Template

Description

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 Extension Template

Extends an existing WebLogic Server domain to add functionality required for advanced Web services, including WSRM, 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.

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 Detail

Information

Template type

Domain

Template name

Basic WebLogic Server Domain

Template JAR file and location

WL_HOME\common\templates\domain\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 Type

Name

Notes

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 Oracle 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_10.3/common/templates/domains/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.

Generated Domain Output

The Basic WebLogic Server Domain template enables you to create a simple WebLogic Server domain. By default, when using the Basic WebLogic Server Domain template, you generate a domain that contains only the required components: an Administration Server and a single administrative user. Any required applications must be created and configured within the domain.

The following table defines the default directory structure and files generated by the Basic WebLogic Server Domain template. Unless otherwise specified, by default, the Configuration Wizard framework creates the domain in the MW_HOME\user_projects\domains\base_domain directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table 2-4 Output Generated from the Basic WebLogic Server Domain Template

Directory

File/s

Description

user_projects\applications\base_domain\

n.a

Directory designated as the repository for any custom application files that you create.

user_projects\domains\base_domain\

fileRealm.properties

File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.

user_projects\domains\base_domain\

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\autodeploy\

readme.txt

File providing information about the directory, which initially serves as a placeholder for automatic deployments.

user_projects\domains\base_domain\bin\

setDomainEnv.cmd

setDomainEnv.sh

Scripts used to set up the development environment on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startManagedWebLogic.cmd

startManagedWebLogic.sh

Scripts used to start a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopManagedWebLogic.cmd

stopManagedWebLogic.sh

Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopWebLogic.cmd

stopWebLogic.sh

Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\config\

config.xml

File containing the configuration information used by the Administration Server. For more information, see "Domain Configuration Files" in Understanding Domain Configuration for Oracle WebLogic Server.

user_projects\domains\base_domain\config\deployments\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for staging an application when the application's staging mode is "staged."

user_projects\domains\base_domain\config\diagnostics\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing the system modules associated with instrumentation in the WebLogic Diagnostic Framework (WLDF).

user_projects\domains\base_domain\config\jdbc\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JDBC modules that can be configured directly from JMX (as opposed to JSR-88).

user_projects\domains\base_domain\config\jms\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).

user_projects\domains\base_domain\config\lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.

user_projects\domains\base_domain\config\nodemanager\

nm_password.properties

File containing Node Manager password property values.

user_projects\domains\base_domain\config\security\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.

user_projects\domains\base_domain\console-ext\

readme.txt

File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.

user_projects\domains\base_domain\init-info\

domain-info.xml

File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.

user_projects\domains\base_domain\init-info\

security.xml

File used for creating user groups and roles that establish identity and access to domain resources.

user_projects\domains\base_domain\init-info\

startscript.xml

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

user_projects\domains\base_domain\init-info\

tokenValue.properties

File that contains the actual values to substitute for the tokens specified in the start scripts.

user_projects\domains\base_domain\lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder for the domain's libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.

user_projects\domains\base_domain\security\

DefaultAuthenticatorInit.ldift

DefaultRoleMapperInit.ldift

XACMLRoleMapperInit.ldift

Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.

Note: WebLogic domains created with this release use the XACML providers, by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see "WebLogic Security Providers" in Understanding Security for Oracle WebLogic Server.

user_projects\domains\base_domain\security\

SerializedSystemIni.dat

File containing encrypted security information.

user_projects\domains\base_domain\servers\AdminServer\security\

boot.properties

File containing server startup properties, including the user name and password required to start the server (in encrypted format). It is generated only when you select development startup mode.

This file enables you to bypass the prompt for user name and password during a server's startup cycle. For more information, see "Provide User Credentials to Start and Stop Servers" in Managing Server Startup and Shutdown for Oracle WebLogic Server.

user_projects\domains\base_domain\user_staged_config\

readme.txt

File providing information about the directory, which initially serves as a placeholder for configuration information optionally staged by an administrator to be copied to Managed Servers in the domain.

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-5 WebLogic Server Starter Domain Template Information

Template Detail

Information

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\domain\wls_starter.jar

Template Dependencies

None

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-6 Resources Configured in a WebLogic Server Starter Domain

Resource Type

Name

Notes

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 Oracle 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_10.3/common/templates/domains/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.

Generated Domain Output

The Starter WebLogic Server Domain template enables you to create a simple WebLogic Server domain. By default, when using the Basic WebLogic Server Domain template, you generate a domain that contains only the required components: an Administration Server and a single administrative user. Any required applications must be created and configured within the domain.

The following table defines the default directory structure and files generated by the Starter WebLogic Server Domain template. Unless otherwise specified, by default, the Configuration Wizard framework creates the domain in the MW_HOME\user_projects\domains\base_domain directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table 2-7 Output Generated from the WebLogic Server Starter Domain Template

Directory

File

Description

user_projects\applications\base_domain\

n.a

Directory designated as the repository for any custom application files that you create.

user_projects\applications\target\wl_starter\

wls_starter.war

The web application files deployed to the starter domain.

user_projects\domains\base_domain\

fileRealm.properties

File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.

user_projects\domains\base_domain\autodeploy\

readme.txt

File providing information about the directory, which initially serves as a placeholder for automatic deployments.

user_projects\domains\base_domain\bin\

setDomainEnv.cmd

setDomainEnv.sh

Scripts used to set up the development environment on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startManagedWebLogic.cmd

startManagedWebLogic.sh

Scripts used to start a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopManagedWebLogic.cmd

stopManagedWebLogic.sh

Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopWebLogic.cmd

stopWebLogic.sh

Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\config\

config.xml

File containing the configuration information used by the Administration Server. For more information, see "Domain Configuration Files" in Understanding Domain Configuration for Oracle WebLogic Server.

user_projects\domains\base_domain\config\deployments\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for staging an application when the application's staging mode is "staged."

user_projects\domains\base_domain\config\diagnostics\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing the system modules associated with instrumentation in the WebLogic Diagnostic Framework (WLDF).

user_projects\domains\base_domain\config\jdbc\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JDBC modules that can be configured directly from JMX (as opposed to JSR-88).

user_projects\domains\base_domain\config\jms\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).

user_projects\domains\base_domain\config\lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.

user_projects\domains\base_domain\config\nodemanager\

nm_password.properties

File containing Node Manager password property values.

user_projects\domains\base_domain\config\security\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.

user_projects\domains\base_domain\console-ext\

readme.txt

File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.

user_projects\domains\base_domain\init-info\

domain-info.xml

File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.

user_projects\domains\base_domain\init-info\

security.xml

File used for creating user groups and roles that establish identity and access to domain resources.

user_projects\domains\base_domain\init-info\

startscript.xml

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

user_projects\domains\base_domain\init-info\

tokenValue.properties

File that contains the actual values to substitute for the tokens specified in the start scripts.

user_projects\domains\base_domain\lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder for the domain's libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.

user_projects\domains\base_domain\security\

DefaultAuthenticatorInit.ldift

DefaultRoleMapperInit.ldift

XACMLRoleMapperInit.ldift

Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.

Note: WebLogic domains created with this release use the XACML providers, by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see "WebLogic Security Providers" in Understanding Security for Oracle WebLogic Server.

user_projects\domains\base_domain\security\

SerializedSystemIni.dat

File containing encrypted security information.

user_projects\domains\base_domain\servers\AdminServer\security\

boot.properties

File containing server startup properties, including the user name and password required to start the server (in encrypted format). It is generated only when you select development startup mode.

This file enables you to bypass the prompt for user name and password during a server's startup cycle. For more information, see "Provide User Credentials to Start and Stop Servers" in Managing Server Startup and Shutdown for Oracle WebLogic Server.

WebLogic Advanced Web Services 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 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 Advanced Web Services extension template.

Table 2-8 WebLogic Advanced Web Services Extension Template Information

Template Detail

Information

Template type

Extension

Template name in Configuration Wizard

WebLogic Advanced Web Services Extension

Template JAR file and location

WL_HOME\common\templates\applications\wls_webservice.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 Advanced Web Services extension template.

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

Resource Type

Name

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

Generated Domain Output

The following table defines the default directory structure and files generated after applying the WebLogic Advanced Web Services extension template to a base WebLogic Server domain. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the MW_HOME\user_projects\domains\base_domain directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table 2-10 Base Domain After Applying the WebLogic Advanced Web Services Extension Template

Directory

File

Description

user_projects\applications\base_domain\

Not applicable

Directory serving as a placeholder for any custom application files that you create.

user_projects\applications\base_domain\

fileRealm.properties

File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.

user_projects\applications\base_domain\

URLs.dat

File containing the URL for the JDBC database.

user_projects\applications\base_domain\autodeploy\

readme.txt

File providing information about the directory, which initially serves as a placeholder for automatic deployments.

user_projects\applications\base_domain\bin\

setDomainEnv.cmd

setDomainEnv.sh

Scripts used to set up the domain environment on Windows and UNIX systems, respectively.

user_projects\applications\base_domain\bin\

startManagedWebLogic.cmd

startManagedWebLogic.sh

Scripts used to start a Managed Server on Windows and UNIX systems, respectively.

user_projects\applications\base_domain\bin\

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

user_projects\applications\base_domain\bin\

stopManagedWebLogic.cmd

stopManagedWebLogic.sh

Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.

user_projects\applications\base_domain\bin\

stopWebLogic.cmd

stopWebLogic.sh

Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.

user_projects\applications\base_domain\config\

config.xml

File containing the configuration information used by the Administration Server. For more information, see "Domain Configuration Files" in Understanding Domain Configuration for Oracle WebLogic Server.

user_projects\applications\base_domain\config\deployments\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for staging an application when the application's staging mode is "staged."

user_projects\applications\base_domain\config\diagnostics\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing the system modules associated with instrumentation in the WebLogic Diagnostic Framework (WLDF).

user_projects\applications\base_domain\config\jms

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).

user_projects\applications\base_domain\config\jms

wseejmsmodule-jms.xml

Global JMS module for the domain configured for advanced Web services.

user_projects\applications\base_domain\config\lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.

user_projects\applications\base_domain\config\nodemanager\

nm_password.properties

File containing Node Manager password property values.

user_projects\applications\base_domain\config\security\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.

user_projects\applications\base_domain\console-ext\

readme.txt

File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.

user_projects\applications\base_domain\init-info\

domain-info.xml

File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.

user_projects\applications\base_domain\init-info\

security.xml

File used for creating user groups and roles that establish identity and access to domain resources.

user_projects\applications\base_domain\init-info\

startscript.xml

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

user_projects\applications\base_domain\init-info\

tokenValue.properties

File that contains the actual values to substitute for the tokens specified in the start scripts.

user_projects\applications\base_domain\lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder for the domain's libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.

user_projects\applications\base_domain\security\

DefaultAuthenticatorInit.ldift

DefaultRoleMapperInit.ldift

XACMLRoleMapperInit.ldift

Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.

Note: WebLogic domains created with this release use the XACML providers by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see "WebLogic Security Providers" in Understanding Security for Oracle WebLogic Server.

user_projects\applications\base_domain\security\

SerializedSystemIni.dat

File containing encrypted security information.

user_projects\applications\base_domain\servers\AdminServer\security\

boot.properties

File containing server startup properties, including the user name and password required to start the server (in encrypted format). It is generated only when you select development startup mode.

This file enables you to bypass the prompt for user name and password during a server's startup cycle. For more information, see "Provide User Credentials to Start and Stop Servers" in Managing Server Startup and Shutdown for Oracle WebLogic Server.

user_projects\applications\base_domain\user_staged_config\

readme.txt

File providing information about the directory, which initially serves as a placeholder for configuration information optionally staged by an administrator to be copied to Managed Servers in the domain.

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:

- Web services atomic transactions

- Security using WS-SecureConversation

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 Getting Started With 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-11 WebLogic Advanced Web Services for JAX-WS Extension Template Details

Template Detail

Information

Template type

Extension

Template name in Configuration Wizard

WebLogic Advanced Web Services for JAX-WS Extension - 10.3.3.0

Template JAR file and location

WL_HOME\common\templates\applications\wls_webservice_jaxws.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 Advanced Web Services for JAX-WS extension template.

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

Resource Type

Name

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

For information about how to change the distributed destination type using Configuration Wizard, see "Select JMS Distributed Destination Type" in Creating Domains Using the Configuration Wizard

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.

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 Information Roadmap for Oracle WebLogic Server .

Template Details

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

Table 2-13 Avitek Medical Records Sample Domain Information

Template Detail

Information

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\applications\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-14 Resources Configured in an Avitek Medical Records Domain

Resource Type

Name

Extension 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 referenced in the extension template is MedRecServer.

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

JDBC Data Sources

MedRecGlobalDataSourceXA

Identifies the JDBC data source as a MedRecGlobalDataSourceXA system resource.

JMS Queues

com.bea.medrec.jms.RecordToCreateQueue

com.bea.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 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 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.1

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

Generated Domain Output

The following table defines the default directory structure and files generated after applying the Avitek Medical Records Sample Domain extension template to a base WebLogic Server domain. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the MW_HOME\user_projects\domains\base_domain directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table 2-15 Base Domain After Applying the Avitek Medical Records Sample Extension Template

Directory

File

Description

user_projects\applications\base_domain\dist\

Various

Includes sub-directories containing various distributions of the Avitek Medical Records applications.

user_projects\applications\base_domain\doc\

Various

Directory and files containing the Avitek Medical Records online documentation.

user_projects\applications\base_domain\lib\

Various

Includes subdirectories containing library files supporting the Avitek Medical Records sample.

user_projects\applications\base_domain\modules\

Various

Includes subdirectories containing Avitek Medical Records source code including various Java, XML, JSP, HTML files, and so on.

user_projects\applications\base_domain\

build.xml

Ant build file used with corresponding scripts to set up a database for the Avitek Medical Records sample.

user_projects\domains\base_domain\

fileRealm.properties

File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.

user_projects\domains\base_domain\

log4j.properties

Configures Avitek Medical Records Log4j implementation including the MedRecApp.log file.

user_projects\domains\base_domain\autodeploy\

readme.txt

File providing information about the directory, which initially serves as a placeholder for automatic deployments.

user_projects\domains\base_domain\bin\

setDomainEnv.cmd

setDomainEnv.sh

Scripts used to set up the development environment on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startManagedWebLogic.cmd

startManagedWebLogic.sh

Scripts used to start a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopManagedWebLogic.cmd

stopManagedWebLogic.sh

Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopWebLogic.cmd

stopWebLogic.sh

Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\config\

config.xml

File containing the configuration information used by the Administration Server. For more information, see "Domain Configuration Files" in Understanding Domain Configuration for Oracle WebLogic Server.

user_projects\domains\base_domain\config\deployments\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for staging an application when the application's staging mode is staged."

user_projects\domains\base_domain\config\diagnostics\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing the system modules associated with instrumentation in the WebLogic Diagnostic Framework (WLDF).

user_projects\domains\base_domain\config\diagnostics\

MedRecWLDF.xml

Diagnostic descriptor information for the Avitek Medical Records diagnostics instrumentation.

user_projects\domains\base_domain\config\jdbc\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JDBC modules that can be configured directly from JMX (as opposed to JSR-88).

user_projects\domains\base_domain\config\jdbc\

MedRec-jdbc.xml

Global XA JDBC Data Source module for the Avitek Medical Records domain.

user_projects\domains\base_domain\config\jms\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).

user_projects\domains\base_domain\config\jms\

MedRec-jms.xml

Global JMS module for the Avitek Medical Records domain.

user_projects\domains\base_domain\config\lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.

user_projects\domains\base_domain\config\nodemanager\

nm_password.properties

File containing Node Manager password property values.

user_projects\domains\base_domain\config\security\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.

user_projects\domains\base_domain\console-ext\

readme.txt

File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.

user_projects\domains\base_domain\console-ext\

diagnostics-console-extension.jar

File used to demonstrate an extension to the WebLogic Server Administration Console that shows diagnostics features.

user_projects\domains\base_domain\init-info\

domain-info.xml

File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.

user_projects\domains\base_domain\init-info\

security.xml

File used for creating user groups and roles that establish identity and access to domain resources.

user_projects\domains\base_domain\init-info\

startscript.xml

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

user_projects\domains\base_domain\init-info\

tokenValue.properties

File that contains the actual values to substitute for the tokens specified in the start scripts.

user_projects\domains\base_domain\lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder for the domain's libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.

user_projects\domains\base_domain\security\

DefaultAuthenticatorInit.ldift

DefaultAuthorizerInit.ldift

Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.

Note: WebLogic domains created with this release use the XACML providers, by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see "WebLogic Security Providers" in Understanding Security for Oracle WebLogic Server.

user_projects\domains\base_domain\servers\AdminServer\security\

boot.properties

File containing server startup properties, including the user name and password required to start the server (in encrypted format). It is generated only when you select development startup mode.

This file enables you to bypass the prompt for user name and password during a server's startup cycle. For more information, see "Provide User Credentials to Start and Stop Servers" in Managing Server Startup and Shutdown for Oracle WebLogic 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 Information Roadmap for 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-16 Avitek Medical Records Sample Domain (Spring) Information

Template Detail

Information

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\applications\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-17 Resources Configured in an Avitek Medical Records Domain for Spring

Resource Type

Name

Extension 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 referenced in the extension template is MedRecServer.

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.

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

Generated Domain Output

The following table defines the default directory structure and files generated after applying the Avitek Medical Records Sample Domain extension template for Spring to a base WebLogic Server domain. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the MW_HOME\user_projects\domains\base_domain directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table 2-18 Base Domain After Applying the Avitek Medical Records Sample Extension Template (Spring Version)

Directory

File

Description

user_projects\applications\base_domain\dist\

Various

Includes sub-directories containing various distributions of the Avitek Medical Records applications.

user_projects\applications\base_domain\doc\

Various

Directory and files containing the Avitek Medical Records online documentation.

user_projects\applications\base_domain\lib\

Various

Includes sub-directories containing library files supporting the Avitek Medical Records sample.

user_projects\applications\base_domain\modules\

Various

Includes sub-directories containing Avitek Medical Records source code including various Java, XML, JSP, HTML files, and so on.

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 Information Roadmap for 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-19 WebLogic Server Default Domain Information

Template Detail

Information

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\applications\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-20 Resources Configured in a WebLogic Server Default Domain

Resource Type

Name

Extension 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 referenced in the extension template is examplesServer.

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

ejb20BeanMgedEar

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

Application Deployment

ejb30

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

Application Deployment

stockEar

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

Application Deployment

asyncServletEar

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

Application Deployment

extServletAnnotationsEar

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

Application Deployment

jdbcRowSetsEar

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

Application Deployment

jspSimpleTagEar

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

Application Deployment

webservicesJwsSimpleEar

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

Application Deployment

xmlBeanEar

Adds the xmlBeanEar 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

pubsub#1.0@1.6.0.0

Adds the HTTP PublisherSubscriber Version 1.6.0.0 library and targets it to the examplesServer Administration Server.

Deployed library

weblogic-sca#1.0@1.1.0.0

Adds the WebLogic SCA Version 1.1.0.0 library and targets it to the examplesServer Administration Server.

Deployed library

apache-xbean.jar

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

Generated Domain Output

The following table defines the default directory structure and files generated after applying the WebLogic Server Default Domain extension template to a base WebLogic Server domain. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the MW_HOME\user_projects\domains\base_domain directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table 2-21 Base Domain After Applying the WebLogic Server Default Domain Extension Template

Directory

File

Description

user_projects\applications\base_domain\server\docs\

Various

Includes sub-directories containing the style sheet and graphics files to support the online documentation.

user_projects\applications\base_domain\server\examples\build\

Various

Includes WebLogic Server examples deployments.

user_projects\applications\base_domain\server\examples\src\

Various

Includes source code and instructions for WebLogic Server examples.

user_projects\domains\base_domain\

fileRealm.properties

File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.

user_projects\domains\base_domain\

setExamplesEnv.cmd

setExamplesEnv.sh

Scripts that set up the environment to use the WebLogic Server Examples on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\

startWebLogicEx.cmd

startWebLogicEx.sh

Scripts used to start the Administration Server for the WebLogic Server Examples domain on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\autodeploy\

readme.txt

File providing information about the directory, which initially serves as a placeholder for automatic deployments.

user_projects\domains\base_domain\bin\

setDomainEnv.cmd

setDomainEnv.sh

Scripts used to set up the development environment on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startManagedWebLogic.cmd

startManagedWebLogic.sh

Scripts used to start a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopManagedWebLogic.cmd

stopManagedWebLogic.sh

Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopWebLogic.cmd

stopWebLogic.sh

Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\config\

config.xml

File containing the configuration information used by the Administration Server. For more information, see "Domain Configuration Files" in Understanding Domain Configuration for Oracle WebLogic Server.

user_projects\domains\base_domain\config\deployments\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for staging an application when the application's staging mode is "staged."

user_projects\domains\base_domain\config\diagnostics\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing the system modules associated with instrumentation in the WebLogic Diagnostic Framework (WLDF).

user_projects\domains\base_domain\config\jdbc\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JDBC modules that can be configured directly from JMX (as opposed to JSR-88).

user_projects\domains\base_domain\config\jdbc\

examples-demo-jdbc.xml

Global non-XA JDBC Data Source module for the WebLogic Server default domain.

user_projects\domains\base_domain\config\jdbc\

examples-demoXA-jdbc.xml

Global XA JDBC Data Source module for the WebLogic Server default domain.

user_projects\domains\base_domain\config\jms\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).

user_projects\domains\base_domain\config\lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.

user_projects\domains\base_domain\config\nodemanager\

nm_password.properties

File containing Node Manager password property values.

user_projects\domains\base_domain\config\security\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.

user_projects\domains\base_domain\console-ext\

readme.txt

File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.

user_projects\domains\base_domain\init-info\

domain-info.xml

File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.

user_projects\domains\base_domain\init-info\

security.xml

File used for creating user groups and roles that establish identity and access to domain resources.

user_projects\domains\base_domain\init-info\

startscript.xml

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

user_projects\domains\base_domain\init-info\

tokenValue.properties

File that contains the actual values to substitute for the tokens specified in the start scripts.

user_projects\domains\base_domain\lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder for the domain's libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.

user_projects\domains\base_domain\security\

DefaultAuthenticatorInit.ldift

DefaultAuthorizerInit.ldift

DefaultRoleMapperInit.ldift

XACMLAuthorizerInit.ldift

XACMLRoleMapperInit.ldift

Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.

Note: WebLogic domains created with this release use the XACML providers by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see "WebLogic Security Providers" in Understanding Security for Oracle WebLogic Server.

user_projects\domains\base_domain\security\

SerializedSystemIni.dat

File containing encrypted security information.

user_projects\domains\base_domain\servers\AdminServer\security\

boot.properties

File containing server startup properties, including the user name and password required to start the server (in encrypted format). It is generated only when you select development startup mode.

This file enables you to bypass the prompt for user name and password during a server's startup cycle. For more information, see "Provide User Credentials to Start and Stop Servers" in Managing Server Startup and Shutdown for Oracle WebLogic Server.

user_projects\domains\base_domain\user_staged_config\

readme.txt

File providing information about the directory, which initially serves as a placeholder for configuration information optionally staged by an administrator to be copied to managed servers in the 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 Information Roadmap for 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-22 WebLogic Server Examples Extension Information

Template Detail

Information

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\applications\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-20), the WebLogic Server Examples extension template configures the resources and services listed in the following table.

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

Resource Type

Name

Notes

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 the extension template is examplesServer.

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.

Generated Domain Output

The WebLogic Server Examples domain contains a collection of examples that illustrate best practices for coding individual J2EE APIs, and a set of scripts to run those examples. Once the WebLogic Server Default extension template has been applied to a base domain, applying the WebLogic Server Examples extension template enables you to create the WebLogic Server Examples domain.

Table 2-24 Base Domain After Applying the WebLogic Server Default and WebLogic Server Examples Extension Templates

Directory

File

Description

user_projects\applications\base_domain\server\

wls_samples_overview.html

File that opens the WebLogic Server examples online documentation viewer.

user_projects\applications\base_domain\server\docs\

Various

Directory and files supporting the WebLogic Server examples online documentation viewer.

user_projects\applications\base_domain\server\examples\build\

Various

Includes sub-directories containing various Java and XML files used to build and work with WebLogic Server examples.

user_projects\applications\base_domain\server\examples\src\

Various

Includes sub-directories containing various Java, XML, and HTML files used to work with WebLogic Server examples.

user_projects\domains\base_domain\

client2certs.pem

clientkey.pem

Demo certificate and keystore files.

user_projects\domains\base_domain\

fileRealm.properties

File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.

user_projects\domains\base_domain\

setExamplesEnv.cmd

setExamplesEnv.sh

Scripts that set up the environment to use the WebLogic Server Examples on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\

startWebLogicEx.cmd

startWebLogicEx.sh

Scripts used to start the Administration Server for the WebLogic Server Examples domain on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\autodeploy\

readme.txt

File providing information about the directory, which initially serves as a placeholder for automatic deployments.

user_projects\domains\base_domain\bin\

setDomainEnv.cmd

setDomainEnv.sh

Scripts used to set up the development environment on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startManagedWebLogic.cmd

startManagedWebLogic.sh

Scripts used to start a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopManagedWebLogic.cmd

stopManagedWebLogic.sh

Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopWebLogic.cmd

stopWebLogic.sh

Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\config\

config.xml

File containing the configuration information used by the Administration Server. For more information, see "Domain Configuration Files" in Understanding Domain Configuration for Oracle WebLogic Server.

user_projects\domains\base_domain\config\deployments\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for staging an application when the application's staging mode is "staged."

user_projects\domains\base_domain\config\diagnostics\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing the system modules associated with instrumentation in the WebLogic Diagnostic Framework (WLDF).

user_projects\domains\base_domain\config\jdbc\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JDBC modules that can be configured directly from JMX (as opposed to JSR-88).

user_projects\domains\base_domain\config\jdbc\

examples-demo-jdbc.xml

Global non-XA JDBC Data Source module for the WebLogic Server Examples domain.

user_projects\domains\base_domain\config\jdbc\

examples-demoXA-2-jdbc.xml

examples-demoXA-jdbc.xml

examples-multiDataSource-demoXAPool-jdbc.xml

examples-oracleXA-jdbc.xml

Global XA JDBC Data Source modules for the WebLogic Server Examples domain.

user_projects\domains\base_domain\config\jms\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).

user_projects\domains\base_domain\config\jms\

examples-jms.xml

Global JMS module for the WebLogic Server Examples domain.

user_projects\domains\base_domain\config\lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java Virtual Machine starts.

user_projects\domains\base_domain\config\nodemanager\

nm_password.properties

File containing Node Manager password property values.

user_projects\domains\base_domain\config\security\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.

user_projects\domains\base_domain\console-ext\

readme.txt

File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.

user_projects\domains\base_domain\init-info\

domain-info.xml

File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.

user_projects\domains\base_domain\init-info\

security.xml

File used for creating user groups and roles that establish identity and access to domain resources.

user_projects\domains\base_domain\init-info\

startscript.xml

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

user_projects\domains\base_domain\init-info\

tokenValue.properties

File that contains the actual values to substitute for the tokens specified in the start scripts.

user_projects\domains\base_domain\lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder for the domain's libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.

user_projects\domains\base_domain\security\

DefaultAuthenticatorInit.ldift

DefaultAuthorizerInit.ldift

DefaultRoleMapperInit.ldift

XACMLAuthorizerInit.ldift

XACMLRoleMapperInit.ldift

Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.

Note: WebLogic domains created with this release use the XACML providers, by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see "WebLogic Security Providers" in Understanding Security for Oracle WebLogic Server.

user_projects\domains\base_domain\security\

SerializedSystemIni.dat

File containing encrypted security information.

user_projects\domains\base_domain\servers\AdminServer\security\

boot.properties

File containing server startup properties, including the user name and password required to start the server (in encrypted format). It is generated only when you select development startup mode.

This file enables you to bypass the prompt for user name and password during a server's startup cycle. For more information, see "Provide User Credentials to Start and Stop Servers" in Managing Server Startup and Shutdown for Oracle WebLogic Server.

user_projects\domains\base_domain\user_staged_config\

readme.txt

File providing information about the directory, which initially serves as a placeholder for configuration information optionally staged by an administrator to be copied to managed servers in the domain.

user_projects\domains\base_domain\WseeFileStore\

Not applicable.

Directory to be used for the file store for system resources.

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 Select Domain Source or Select Extension Source screens 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:

- Enterprise Manager Templates

- Enterprise Content Management Templates

- Oracle SOA Suite Templates

- Oracle Web Service Manager (OWSM) Templates

- Oracle Service Bus Templates

- Oracle User Messaging Service Templates

- Oracle WebCenter Portal Templates

- Oracle Identity Management Templates

- Oracle Data Integrator Templates

- Oracle JRF and JSF Templates

Each template section contains the following template information:

- Template type—A template can be either a domain or an extension template.
A domain template defines the full set of resources within a WebLogic domain, including the Administration Server, clusters, servers, applications, services, security options, and other options. A given product installation is based on one domain template.

An extension template adds resources, such as applications, libraries, services, and other options, to an existing domain. A given product installation may require one or more extension templates to complete the domain.

A group template is a special XML file that is a collection of template dependencies. It simplifies the process of pulling in multiple dependent templates by the template that requires them.

When creating your product domain using the Configuration Wizard, you can select the domain and extension templates concurrently for the products you want to install.

- Template name and version—The template (product) name and template version. If the template is selectable on the Select Domain Source or Select Extension Source screen of the Configuration Wizard, this is the name as it is listed in the Configuration Wizard.

- Template dependencies—Prerequisite templates that provide resources required by the template being described in a given section, in the order in which they must be added to the domain. When you select a template from the Product List on the Configuration Wizard Select Domain Source or Select Extension Source screen, the Configuration Wizard automatically selects all prerequisite templates.

- Template JAR file and location—The JAR filename and its location in the Middleware home directory. You need this information only if you plan to use WLST scripts to set up a product domain.

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 Select Domain Source 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 Oracle Fusion Middleware Administrator's Guide.

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-1 Oracle Enterprise Manager Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Enterprise Manager - 11.1.1.0

Template Dependencies

- Basic WebLogic Server Domain

- + Oracle JRF - 11.1.1.0

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:

MW_HOME/oracle_common/common/applications/templates

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

- oracle.em_11_1_1_0_0_template.jar

- oracle.emai_template_11.1.1.jar

- oracle.emas_template_11.1.1.jar

Enterprise Content Management Templates

This section describes the Enterprise Content Management (ECM) templates that are used to extend (add resources to) WebLogic Server domains in which ECM products are installed. Templates for other products may also be required for an ECM domain. These are described elsewhere in this chapter.

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.
As of the Fusion Middleware 11.1.1.6.0 release, the product name of Oracle Universal Content Management (UCM) has been changed to Oracle WebCenter Content. The template names in the Configuration Wizard, however, are still labeled with the previous product name (UCM).

The following templates are described in this section:

- Oracle WebCenter Content Core Template

- Oracle Universal Content Management - Content Server Template

- Oracle Universal Records Management Template

- Oracle Information Rights Management (IRM) Template

- Oracle WebCenter Content: Imaging Template

- Oracle Universal Content Management - Inbound Refinery Template

Oracle WebCenter Content Core Template

The Oracle WebCenter Content Core Template is responsible for deploying Oracle WebCenter Content help, Oracle WebCenter Content Web services, Oracle WebCenter Content Native Web services, and Dav service. Along with these deployments, it also defines the ReportPublisher library and oracle.xdo.runtime shared libraries that are used by Oracle WebCenter Content: Records in both the Oracle WebCenter Content and ECM products.

The core template also updates the Managed Server's setDomainEnv script with the definition for the UCM_ORACLE_HOME environment variable, updates the CLASSPATH entry defined by this script to include idcloader.jar and nativeosutils.jar, and adds a line to source the ucm_oracle_home/ucm/idc/bin/idcCommEnv script. The core template is also responsible for defining the dependency on the JRF and Enterprise Manager templates.

Note:

The Oracle Enterprise Manager Plugin for UCM template, which is listed as a dependency for this template, is an internal template. It is automatically called when you select the Universal Content Management (UCM) Core template, or specify the UCM Core template in a WLST script. Therefore, it is not displayed as a selectable component in Configuration Wizard, and you do not have to specify it in your WLST scripts.

The following table provides key information about this template.

Table 3-2 Oracle UCM Core Template Details

Template Detail

Information

Template type

Extension Template

Template name and version

Oracle UCM Core - 11.1.1.0

Template Dependencies

- Basic WebLogic Server Domain

- + Oracle JRF - 11.1.1.0

- + Oracle Enterprise Manager - 11.1.1.0

- + Oracle Enterprise Manager Plugin for UCM

Template JAR file and location

ECM_HOME/common/templates/applications/oracle.ucm.core_template_11.1.1.jar

Oracle Universal Content Management - Content Server Template

The Oracle Universal Content Management - Content Server template depends upon the core template and extends it by defining the default Managed Server (UCM_server1) and port (16200). It also defines the CSDS data source and associates it with the default Managed Server.

Note:

The Oracle Enterprise Manager Plugin for UCM template, which is listed as a dependency for this template, is an internal template. It is automatically called when you select the Content Server template, or specify the Content Server template in a WLST script. Therefore, it is not displayed as a selectable component in Configuration Wizard, and you do not have to specify it in your WLST scripts.

The following table provides key information about this template.

Table 3-3 Oracle Universal Content Management - Content Server Template Details

Template Detail

Information

Template type

Extension Template

Template name and version

Oracle Universal Content Management - Content Server 11.1.1.0

Template Dependencies

- Basic WebLogic Server Domain

- + Oracle JRF - 11.1.1.0

- + Oracle Enterprise Manager - 11.1.1.0

- + Oracle Enterprise Manager Plugin for UCM

- + Oracle UCM Core - 11.1.1

Template JAR file and location

ECM_HOME/common/templates/applications/oracle.ucm.cs_template_11.1.1.jar

Oracle Universal Records Management Template

This template adds the Oracle Universal Records Management application to an existing domain.

Note:

The Oracle Enterprise Manager Plugin for UCM template, which is listed as a dependency for this template, is an internal template. It is automatically called when you select the Universal Content Management (UCM) Core Template, or specify the UCM Core template in a WLST script. Therefore, it is not displayed as a selectable component in Configuration Wizard, and you do not have to specify it in your WLST scripts.

The following table provides key information about this template.

Table 3-4 Oracle Universal Records Management Template Details

Template Detail

Information

Template type

Extension Template

Template name and version

Oracle Universal Records Management - 11.1.1.0

Template Dependencies

- Basic WebLogic Server Domain

- + Oracle JRF - 11.1.1.0

- + Oracle Enterprise Manager - 11.1.1.0

- + Oracle Enterprise Manager Plugin for UCM

- + Oracle UCM Core Template - 11.1.1.0

Template JAR file and location

ECM_HOME/common/templates/applications/oracle.ucm.urm_template_11.1.1.jar

Oracle Information Rights Management (IRM) Template

The Oracle Information Rights Management template adds the Oracle Information Rights server to an existing domain.

Note:

The Oracle Enterprise Manager Plugin for IRM template, which is listed as a dependency for this template, is an internal template. It is automatically called when you select the Information Rights Management template, or specify the Information Rights Management template in a WLST script. Therefore, it is not displayed as a selectable component in Configuration Wizard, and you do not have to specify it in your WLST scripts.

The following table provides key information about this template.

Table 3-5 Oracle Information Rights Management Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Information Rights Management - 11.1.1.0

Template dependencies

- Basic WebLogic Server Domain

- + Oracle JRF - 11.1.1.0

- + Oracle Enterprise Manager - 11.1.1.0

- + Oracle Enterprise Manager Plugin for IRM - 11.1.1.0

Template JAR file and location

ECM_HOME/common/templates/applications/oracle.irm_template_11.1.1.jar

Oracle WebCenter Content: Imaging Template

The Oracle WebCenter Content: Imaging template provides the ability to create or extend domains with the Oracle WebCenter Content: Imaging product.

The following table provides key information about this template.

Table 3-6 Oracle WebCenter Content: Imaging Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle WebCenter Content: Imaging - 11.1.1.0

Template Dependencies

- Basic WebLogic Server Domain

- + Oracle JRF - 11.1.1.0

- + Oracle Enterprise Manager - 11.1.1.0

Template JAR file and location

ECM_HOME/common/templates/applications/oracle.ipm_template_11.1.1.jar

Oracle Universal Content Management - Inbound Refinery Template

The Oracle Universal Content Management - Inbound Refinery template adds the Inbound Refinery server and UCM Inbound Refinery application to an existing domain.

Note:

The Oracle Enterprise Manager Plugin for UCM template, which is listed as a dependency for this template, is an internal template. It is automatically called when you select the Inbound Refinery template, or specify the Inbound Refinery template in a WLST script. Therefore, it is not displayed as a selectable component in Configuration Wizard, and you do not have to specify it in your WLST scripts.

The following table provides key information about this template.

Table 3-7 Oracle Universal Content Management - Inbound Refinery Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle WebCenter Content - Inbound Refinery - 11.1.1.0

Template Dependencies

- Basic WebLogic Server Domain

- + Oracle JRF - 11.1.1.0

- + Oracle Enterprise Manager 11.1.1.0

- + Oracle Enterprise Manager Plugin for UCM

- + Oracle UCM Core - 11.1.1.0

Template JAR file and location

ECM_HOME/common/templates/applications/oracle.ucm.ibr_template_11.1.1.jar

Oracle SOA Suite Templates

This section describes the following Oracle SOA Suite templates:

- Oracle SOA Suite Template

- Oracle Business Activity Monitor Template

- Oracle Business Rules Extension Template

- Oracle User Messaging Service for SOA Template

- Oracle SOA Suite for Developers Template

Oracle SOA Suite Template

The Oracle SOA Suite template configures the data sources, Java Messaging Service (JMS), applications (SOA Infrastructure, Oracle BPM Worklist, and the Oracle B2B user interface), and JCA adapters (file, FTP, socket, database, Advanced Queuing (AQ), JMS, Oracle Applications, and MQ Series).

The following table provides basic information about the Oracle SOA Suite template.

Table 3-8 Oracle SOA Suite Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle SOA Suite - 11.1.1.0

Template Dependencies

- Oracle JRF - 11.1.1.0

- + Oracle Business Rules Extension - 11.1.1

- + Oracle User Messaging Service for SOA - 11.1.1.0

- + Oracle WSM Policy Manager - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.soa_11.1.1_template.jar

Oracle Business Activity Monitor Template

The Oracle BAM template configures the Oracle BAM Server and Oracle BAM Web Applications tier.

The following table provides basic information about the Oracle BAM template.

Table 3-9 Oracle Business Activity Monitor Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Business Activity Monitor - 11.1.1.0

Template Dependencies

- Oracle JRF - 11.1.1.0

- + Oracle User Messaging Service - 11.1.1.0

- + Oracle Business Rules Extension - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.bam_11.1.1_template.jar

Oracle Business Rules Extension Template

The Oracle Business Rules Extension template configures Oracle Business Rules components and the oracle.rules library.

The following table provides basic information about the Oracle Business Rules Extension template.

Table 3-10 Oracle Business Rules Extension Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Business Rules Extension - 11.1.1.0

Template Dependencies

Oracle JRF - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.rules_template_11.1.1.jar

Oracle User Messaging Service for SOA Template

The Oracle User Messaging Service for SOA template is a group template that combines the Oracle User Messaging Service and Oracle User Messaging Service Drivers templates into one simplified dependency for SOA.

The following table provides key information about this template.

Table 3-11 Oracle User Messaging Service for SOA Template Details

Template Detail

Information

Template type

Group template

Template name and version

Oracle User Messaging Service for SOA - 11.1.1.0

Template Dependencies

- Oracle User Messaging Service - 11.1.1.0

- Oracle User Messaging Service Drivers - 11.1.1.0

Template group file and location

MW_HOME/oracle_common/templates/groups/oracle.ums.soa_group_11.1.1.xml

Oracle SOA Suite for Developers Template

The Oracle SOA Suite for Developers template is provided for use by developers with hosts that have lower memory capabilities (for example, laptops).

Note:

The Oracle SOA Suite for Developers runs on the Administration Server, and not on a Managed Server (for example, soa_server1).

The following table provides basic information about the Oracle SOA Suite for Developers template.

Table 3-12 Oracle SOA Suite for Developers Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle SOA Suite for developers - 11.1.1.0

Template Dependencies

- Oracle JRF - 11.1.1.0

- + Oracle Business Rules Extension - 11.1.1

- + Oracle User Messaging Service for SOA - 11.1.1.0

- + Oracle WSM Policy Manager - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.soa_template_developer_11.1.1.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-13 Oracle WSM Policy Manager Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle WSM Policy Manager - 11.1.1.0

Template Dependencies

- Basic WebLogic Server Domain

- + Oracle JRF - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.wsmpm_template_11.1.1.jar

Oracle Service Bus Templates

This section describes the Oracle Service Bus templates that are used to create or extend an existing domain with Oracle Service Bus.

For a description of the deployment topologies Oracle Service Bus supports, see "Oracle Service Bus Deployment Topology" in the Oracle Fusion Middleware Deployment Guide for Oracle Service Bus.

The following templates are described in this section:

- Oracle Service Bus for developers Template (Admin-only Topology)

- Oracle Service Bus Template (Cluster and Managed Server Topologies)

- Oracle Service Bus OWSM Extension Template

Oracle Service Bus for developers Template (Admin-only Topology)

This template, designed for development use, creates or extends an Oracle WebLogic Server domain and deploys Oracle Service Bus on only the Administration Server. The template includes, among other features, the Oracle Service Bus Administration console Web application and a default JMS reporting provider.

If you do not want to use the JMS reporting provider, see "How to Untarget a JMS Reporting Provider" in the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus.

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-14 Oracle Service Bus for developers Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Service Bus for developers - 11.1.1.4

Template Dependencies

- Basic WebLogic Server Domain

- + WebLogic Advanced Web Services for JAX-RPC Extension - 10.3.4.0

- + Oracle JRF - 11.1.1.0

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 Service Bus:

OSB_ORACLE_HOME/common/templates/applications

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

- wlsb_single_server.jar

- wlsb_base.jar

- oracle.soa.common.adapters_template_11.1.1.jar

Oracle Service Bus Template (Cluster and Managed Server Topologies)

This template, designed for testing and production use, creates or extends an Oracle WebLogic Server domain with Oracle Service Bus. The template deploys Oracle Service Bus management features on the Administration Server and run-time features on the cluster or managed server, depending on your domain topology. The template includes, among other features, the Oracle Service Bus Administration Console Web application and a default JMS reporting provider.

You cannot mix Managed Server and cluster topologies. You must use one or the other.

Oracle recommends a cluster topology for production use. The Managed Server topology does not provide a highly available configuration, so it is not recommended for production.

If you do not want to use the JMS reporting provider, see "How to Untarget a JMS Reporting Provider" in the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus.

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-15 Oracle Service Bus Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Service Bus - 11.1.1.4

Template Dependencies

- Basic WebLogic Server Domain

- + WebLogic Advanced Web Services for JAX-RPC Extension - 10.3.4.0

- + Oracle JRF - 11.1.1.0

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 Service Bus:

OSB_ORACLE_HOME/common/templates/applications

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

- wlsb.jar

- wlsb_base.jar

- oracle.soa.common.adapters_template_11.1.1.jar

Oracle Service Bus OWSM Extension Template

This template extends an Oracle Service Bus domain with support for using Oracle Web Services Manager policies in business and proxy services.

You must add this template to use OWSM security policies with Oracle Service Bus.

Important: If you use the Oracle Fusion Middleware Configuration Wizard to create an Oracle Service Bus domain that includes this template, it is important that you select this template only after you select either the "Oracle Service Bus for developers - 11.1.1.4" or the "Oracle Service Bus - 11.1.1.4" template to ensure the appropriate dependencies are satisfied.

If you want to author and manage OWSM policies

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-16 Oracle Service Bus OWSM Extension Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Service Bus OWSM Extension - 11.1.1.4

Template Dependencies

- Basic WebLogic Server Domain

- + Oracle Service Bus for developers 11.1.1.4
or

Oracle Service Bus - 11.1.1.4

- + Oracle WSM Policy Manager - 11.1.1.0

Note: If you want to create and manage OWSM security policies for use with Oracle Service Bus, you must also include the Oracle WSM Policy Manager Template in the domain.

Template JAR file and location

OSB_ORACLE_HOME/common/templates/applications/wlsb_owsm.jar

Oracle User Messaging Service Templates

This section describes the following Oracle User Messaging Service templates:

- Oracle User Messaging Service Template

- Oracle User Messaging Service Drivers Template

- Oracle User Messaging Service Worklist Driver Template

- Oracle WebLogic Communications Service Client Library Extension Template

Notes:

Oracle User Messaging Service templates are not visible or selectable from the list of products on the Configuration Wizard Select Domain Source and Select Extension Source screens.
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 User Messaging Service Template

The Oracle User Messaging Service template configures Oracle User Messaging Service. This component is part of the Oracle SOA Suite and provides services to send/receive alerts and notifications to/from end users using messaging channels such as Email, IM, SMS, and Voice.

The following table provides key information about this template.

Table 3-17 Oracle User Messaging Service Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle User Messaging Service - 11.1.1.0

Template Dependencies

- Oracle JRF - 11.1.1.0

- + Oracle Business Rules Extension - 11.1.1.0

- + Oracle WSM Policy Manager - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.ums_template_11.1.1.jar

Oracle User Messaging Service Drivers Template

The Oracle User Messaging Service Drivers template configures the Oracle User Messaging Service drivers for IM (XMPP), SMS (SMPP), and Voice (VoiceXML).

The following table provides key information about this template.

Table 3-18 Oracle User Messaging Service Drivers Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle User Messaging Service Drivers - 11.1.1.0

Template Dependencies

- Oracle JRF - 11.1.1.0

- + Oracle User Messaging Service - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.ums.drivers_template_11.1.1.jar

Oracle User Messaging Service Worklist Driver Template

The Oracle User Messaging Service Driver template configures the Oracle User Messaging Service Worklist driver.

The following table provides key information about this template.

Table 3-19 Oracle User Messaging Service Worklist Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle User Messaging Service Worklist Driver - 11.1.1.0

Template Dependencies

- Oracle JRF - 11.1.1.0

- Oracle User Messaging Service - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.ums.driver.worklist_template_11.1.1.jar

Oracle WebLogic Communications Service Client Library Extension Template

The Oracle WebLogic Communications Service Client Library Extension template configures the Oracle WebLogic Communications Service Client Library. This library provides Web Service clients for Oracle WebLogic Communications Service's presence, messaging, contact management and third party call services.

The following table provides key information about this template.

Table 3-20 Oracle WebLogic Communications Service Client Library Extension Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle WebLogic Communications Service Client Library Extension - 11.1.1.0

Template Dependencies

Oracle JRF - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.communications.client_template_11.1.1.jar

Oracle WebCenter Portal Templates

This section describes the following Oracle WebCenter Portal templates:

- Oracle WebCenter Spaces Template

- Oracle Portlet Producers Template

- Oracle WebCenter Discussion Server Template

- Oracle WebCenter Custom Portal Template

- Oracle WebCenter Custom Services Producer Template

- Oracle WebCenter Analytics Template

- Oracle WebCenter Activity Graph Template

- Oracle WebCenter Pagelet Producer Template

- Oracle WebCenter Personalization Server Template

- Oracle WebCenter Services Portlets Template

Oracle WebCenter Spaces Template

The Oracle WebCenter Spaces template adds the WC_Spaces Managed Server, and deploys the Oracle WebCenter Portal: Spaces application and required libraries. It also deploys the WebCenter Portal Help application and adds JDBC data sources for accessing MDS and WebCenter Portal's schema.

The following table provides key information about this template.

Table 3-21 Oracle WebCenter Spaces Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle WebCenter Spaces - 11.1.1.0

Template Dependencies

- Oracle WebCenter Framework

- + Oracle Enterprise Manager - 11.1.1.0

- + Oracle WSM Policy Manager - 11.1.1.0

- + Oracle WebCenter Spaces Applications - 11.1.1.0

Template JAR file and location

WC_ORACLE_HOME/common/templates/applications/oracle.wc_spaces_template_11.1.1.jar

Oracle Portlet Producers Template

The Oracle Portlet Producers template adds the WC_Portlet Managed Server, and deploys Oracle WebCenter Portal's Portlet Producer applications (Portal Tools and WSRP Tools) and required libraries. It also adds a JDBC data source for accessing the Portlet schema.

The following table provides key information about this template.

Table 3-22 Oracle Portlet Producers Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Portlet Producers - 11.1.1.0

Template Dependencies

- Oracle Portlet Producers Applications - 11.1.1.0

- Oracle WSM Policy Manager - 11.1.1.0

Template JAR file and location

WC_ORACLE_HOME/common/templates/applications/oracle.producer_apps_template_11.1.1.jar

Oracle WebCenter Discussion Server Template

The Oracle WebCenter Discussion Server template adds the WC_Collaboration Managed Server and deploys Oracle WebCenter Portal's Discussion application. It also adds a JDBC data source for accessing the Discussions schema.

The following table provides key information about this template.

Table 3-23 Oracle WebCenter Discussion Server Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle WebCenter Discussion Server - 11.1.1.0

Template Dependencies

- Oracle JRF - 11.1.1.0

- Oracle Enterprise Manager - 11.1.1.0

Template JAR file and location

WC_ORACLE_HOME/common/templates/applications/oracle.owc_discussions_template_11.1.1.jar

Oracle WebCenter Custom Portal Template

The Oracle WebCenter Custom Portal template adds the WC_CustomPortal Managed Server. It also adds a JDBC data source for accessing the WebCenter Portal, Portlet, Activities, and MDS schemas.

The following table provides key information about this template.

Table 3-24 Oracle WebCenter Custom Portal Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle WebCenter Custom Portal - 11.1.1.0

Template Dependencies

- Oracle WebCenter Framework

- Oracle WSM Policy Manager

Template JAR file and location

WC_ORACLE_HOME/common/templates/applications/oracle.wc_custom_portal_template_11.1.1.jar

Oracle WebCenter Custom Services Producer Template

The Oracle WebCenter Custom Services Producer template adds the WC_CustomServicesProducer Managed Server. It also adds a JDBC data source for accessing the WebCenter Portal, Activities, and MDS schemas.

The following table provides key information about this template.

Table 3-25 Oracle WebCenter Custom Producer Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle WebCenter Custom Services Producer - 11.1.1.0

Template Dependencies

- Oracle WebCenter Services Producer Component

- Oracle WSM Policy Manager

Template JAR file and location

WC_ORACLE_HOME/common/templates/applications/oracle.wc_custom_services_producer_template_11.1.1.jar

Oracle WebCenter Analytics Template

The Oracle WebCenter Analytics template adds the WC_Utilities server and the Activities Data Source, and configures the Oracle WebCenter Portal's Analytics application and dependent templates.

The following table provides key information about this template.

Table 3-26 Oracle WebCenter Analytics Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle WebCenter Analytics Collector - 11.1.1.0

Template Dependencies

Oracle JRF - 11.1.1.0

Template JAR file and location

WC_ORACLE_HOME/common/templates/applications/oracle.analyticscollector_template_11.1.1.jar

Oracle WebCenter Activity Graph Template

The Oracle WebCenter Activity Graph template configures Oracle WebCenter Portal's Activity Graph application and dependent templates.

The following table provides key information about this template.

Table 3-27 Oracle WebCenter Activity Graph Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle WebCenter Activity Graph Engines - 11.1.1.0

Template Dependencies

Oracle WebCenter Analytics Collector - 11.1.1.0

Template JAR file and location

WC_ORACLE_HOME/common/templates/applications/oracle.activitygraph_template_11.1.1.jar

Oracle WebCenter Pagelet Producer Template

The Oracle WebCenter Pagelet Producer template configures the WC_Portlet server and MDS schema for Pagelets.

The following table provides key information about this template.

Table 3-28 Oracle WebCenter Pagelet Producer Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle WebCenter Pagelet Producer - 11.1.1.0

Template Dependencies

Oracle JRF - 11.1.1.0

Template JAR file and location

WC_ORACLE_HOME/common/templates/applications/oracle.pagelet-producer_template_11.1.1.jar

Oracle WebCenter Personalization Server Template

The Oracle WebCenter Personalization Server template configures Oracle WebCenter Portal's Personalization application, the WC_Utilities server, the Personalization Data Source (uses the WebCenter schema), MDS for Personalization, and dependent templates.

The following table provides key information about this template.

Table 3-29 Oracle WebCenter Personalization Server Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle WebCenter Personalization - 11.1.1.0

Template Dependencies

Oracle JRF - 11.1.1.0

Template JAR file and location

WC_ORACLE_HOME/common/templates/applications/oracle.wcps_template_11.1.1.jar

Oracle WebCenter Services Portlets Template

The Oracle WebCenter Services Portlets templates adds WC_Portlet and deploys the Services Producer application.

The following table provides key information about this template:

Table 3-30 Oracle WebCenter Services Portlets Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle WebCenter Services Portlets - 11.1.1.0

Template Dependencies

- Oracle WSM Policy Manager - 11.1.1.0

- Oracle WebCenter Services Producer Component - 11.1.1.0

Template JAR file and location

WC_ORACLE_HOME/common/templates/applications/oracle.wc_services_producer_template_11.1.1.jar

Oracle Identity Management Templates

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

- Oracle IDM Common Template

- Oracle Adaptive Access Manager Admin Server Template

- Oracle Adaptive Access Manager - Server Template

- Oracle Adaptive Access Manager Offline Template

- Oracle Access Manager with Database Policy Store Template

- Oracle Identity Manager Template

- Oracle Entitlements Server Template

- Oracle Authorization Policy Manager Template (Apache Derby)

- Oracle Entitlements Server WebLogic Security Module Template

- Oracle Identity Navigator Template

Note:

The Oracle IDM Common template, which is listed as a dependency for other IDM templates, is an internal template. It is automatically called when you select other IDM templates in Configuration Wizard, or specify an IDM template in a WLST script. Therefore, it is not displayed as a selectable component in Configuration Wizard, and you do not have to specify it in your WLST scripts.

Oracle IDM Common Template

This template provides IDM Shell and other common IDM-wide infrastructure components that are not present in JRF.

The following table provides key information about this template.

Table 3-31 Oracle IDM Common Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle IDM Common Template - 11.1.1.1

Template Dependencies

Oracle JRF - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/idm_common_template_11.1.1.jar

Oracle Adaptive Access Manager Admin Server Template

The Oracle Adaptive Access Manager Admin Server template adds the Oracle Adaptive Access Manager (OAAM) Administration Server application to an existing domain.

The following table provides key information about this template.

Table 3-32 Oracle Adaptive Access Manager Admin Server Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Adaptive Access Manager Admin Server - 11.1.1.3.0

Template Dependencies

- Oracle JRF - 11.1.1.0

- + Oracle Identity Navigator - 11.1.1.3.0

- + Oracle IDM Common Template - 11.1.1.0

- + Oracle Enterprise Manager - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.oaam_admin_11.1.1.3.0_template.jar

Oracle Adaptive Access Manager - Server Template

The Oracle Adaptive Access Manager - Server template adds the Oracle Adaptive Access Manager (OAAM) Server application to an existing domain.

The following table provides key information about this template.

Table 3-33 Oracle Adaptive Access Manager - Server Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Adaptive Access Manager - Server 11.1.1.3.0

Template Dependencies

- Oracle JRF - 11.1.1.0

- + Oracle Identity Navigator - 11.1.1.3.0

- + Oracle IDM Common Template - 11.1.1.2.0

- + Oracle WSM Policy Manager - 11.1.1.0

- + Oracle Enterprise Manager - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.oaam_server_11.1.1.3.0_template.jar

Oracle Adaptive Access Manager Offline Template

The Oracle Adaptive Access Manager Offline template adds the Oracle Adaptive Access Manager (OAAM) Offline application to an existing domain.

The following table provides key information about this template.

Table 3-34 Oracle Adaptive Access Manager - Server Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Adaptive Access Manager Offline 11.1.1.3.0

Template Dependencies

- Oracle JRF - 11.1.1.0

- + Oracle Identity Navigator - 11.1.1.3.0

- + Oracle IDM Common Template - 11.1.1.2.0

- + Oracle WSM Policy Manager - 11.1.1.0

- + Oracle Enterprise Manager - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.oaam_offline_11.1.1.3.0_template.jar

Oracle Access Manager with Database Policy Store Template

The Oracle Access Manager with Database Policy Store template adds an Oracle Access Manager (OAM) server to an existing domain. It also adds OAM applications and authentication providers to the domain. It includes a JDBC data source and the associated JDBC component schema.

The following table provides key information about this template.

Table 3-35 Oracle Access Manager with Database Policy Store Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Access Manager with File Policy Store 11.1.1.3.0

Template Dependencies

- Oracle JRF - 11.1.1.0

- + Oracle IDM Common - 11.1.1.2.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.oam_ds_11.1.1.3.0_template.jar

Oracle Identity Manager Template

The Oracle Identity Manager template adds Oracle Identity Management (OIM) applications, as well as required JDBC and JMS resources, to an existing domain.

The following table provides key information about this template.

Table 3-36 Oracle Identity Manager Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Identity Manager - 11.1.1.3.0

Template Dependencies

- Oracle JRF - 11.1.1.0

- + Oracle IDM Common - 11.1.1.2.0

- + Oracle SOA Suite - 11.1.1.0

- + Oracle WSM Policy Manager - 11.1.1.0

- + Oracle Enterprise Manager - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.oim_11.1.1.3.0_template.jar

Oracle Entitlements Server Template

The Oracle Entitlements Server template deploys and configures Oracle Entitlements Server.

The following table provides key information about this template.

Table 3-37 Oracle Authorization Policy Manager Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Entitlements Server - 11.1.1.0

Template Dependencies

- Oracle JRF - 11.1.1.0

- + Oracle IDM Common - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.apm_11.1.1.3.0_template.jar

Oracle Authorization Policy Manager Template (Apache Derby)

If you using Apache Derby, an evaluation database included in your Oracle WebLogic Server installation, then you must use the Oracle Authorization Policy Manager (Apache Derby) template to deploy and configure Oracle Entitlements Server.

The following table provides key information about this template.

Table 3-38 Oracle Authorization Policy Manager Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Entitlements Server Security Module - 11.1.1.0

Template Dependencies

- Oracle JRF - 11.1.1.0

- + Oracle IDM Common - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.apm_11.1.1.3.0_template_derby.jar

Oracle Entitlements Server WebLogic Security Module Template

The Oracle Entitlements Server WebLogic Security Module template deploys and configures Oracle Entitlements Server Client.

The following table provides key information about this template.

Table 3-39 Oracle Entitlements Server Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Entitlements Server WebLogic Security Module - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.oes.sm.wls_template_11.1.1.jar

Oracle Identity Navigator Template

The Oracle Identity Navigator template adds the Oracle Identity Navigator application to an existing domain.

The following table provides key information about this template.

Table 3-40 Oracle Identity Navigator Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Identity Navigator - 11.1.1.3.0

Template Dependencies

- Oracle JRF - 11.1.1.0

- + Oracle IDM Common - 11.1.1.2.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.oinav_11.1.1.3.0_template.jar

Oracle Data Integrator Templates

This section describes the following Oracle Data Integrator templates:

- Oracle Data Integrator Agent Template

- Oracle Data Integrator Agent Libraries Template

- Oracle Data Integrator Console Template

- Oracle Data Integrator SDK Web Services Template

- Oracle Data Integrator SDK Shared Library Template

- Oracle Enterprise Manager Plugin for ODI Template

Note:

he 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 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-41 Oracle Data Integrator Agent Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Data Integrator Agent - 11.1.1.5.0

Template Dependencies

- ODI Agent Libraries Template

- ODI Master Datasource Template

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/agent_template.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-42 Oracle Data Integrator Agent Libraries Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Data Integrator Agent Libraries - 11.1.1.5.0

Template Dependencies

- ODI Base Template

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/agent_libraries_template.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-43 Oracle Data Integrator Console Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Data Integrator Console - 11.1.1.5.0

Template Dependencies

- ODI Work Datasource

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/repository_explorer_template.jar

Oracle Data Integrator SDK Web Services Template

The Oracle Data Integrator SDK Web Services template deploys the ODI SDK Web Services application.

The following table provides key information about this template.

Table 3-44 Oracle Data Integrator SDK Web Services Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Data Integrator SDK Web Services - 11.1.1.5.0

Template Dependencies

- ODI Work Datasource

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/odi_webservices_template.jar

Oracle Data Integrator SDK Shared Library Template

The Oracle Data Integrator SDK Shared Library template deploys the ODI SDK shared library.

The following table provides key information about this template.

Table 3-45 Oracle Data Integrator SDK Shared Library Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Data Integrator SDK Shared Library - 11.1.1.5.0

Template Dependencies

None

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/odi_sdk_template.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-46 Oracle Enterprise Manager Plugin for ODI Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle Enterprise Manager Plugin for ODI - 11.1.1.5.0

Template Dependencies

- Oracle Enterprise Manager

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.emai_odi_template_11.1.1.jar

Oracle JRF and JSF Templates

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

- Oracle JRF Template

- Oracle JRF Asynchronous Web Services Template

- JSFDomain 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 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-47 Oracle JRF Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle JRF - 11.1.1.0

Template Dependencies

None

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/jrf_template_11.1.1.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-48 Oracle JRF Asynchronous Web Services Template Details

Template Detail

Information

Template type

Extension

Template name and version

Oracle JRF Web Services Asynchronous Services - 11.1.1.0

Template Dependencies

Oracle JRF - 11.1.1.0

Template JAR file and location

MW_HOME/oracle_common/common/templates/applications/oracle.jrf.ws.async_template_11.1.1.jar

JSFDomain Template

If you start JDeveloper in the Java EE role, the JSFDomain template provides the shared libraries that are needed to run JSF applications in Java EE role. If JDeveloper is in the Default role (studio edition), JRF provides the shared libraries to run ADFFaces Richclient, and the JSFDomain Template is not needed.

The following table provides key information about this template.

Table 3-49 JSF Domain Template Details

Template Detail

Information

Template type

Domain

Template name and version

JSFDomain 9.0.0.0

Template Dependencies

None

Template JAR file and location

ORACLE_HOME/jdeveloper/common/templates/domains/jsf_template_1.2.9.0.jar

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