Creating WebLogic Configurations Using the Configuration Wizard
|
 |
 |
|
 |
 |
The section includes the following topics:
A template is a Java Archive (JAR) file that contains the files and scripts required to create or update a domain. The Configuration Wizard uses two types of template:
WebLogic Platform provides predefined configuration templates that are installed with the product. You can easily create a WebLogic domain by running the Configuration Wizard in either Express mode or Custom mode, using one of the predefined configuration templates as your selection.
Note: Since the initial product release, there have been changes made to the Basic WebLogic Integration Domain, Basic WebLogic Platform Domain, and Basic WebLogic Portal Domain configuration templates. Because of these changes, when creating a domain using the Configuration Wizard, you should use a configuration template provided with your current installation or a custom template created from a domain or template in your current installation. You must upgrade the domains created using the configuration templates provided with an earlier service pack to the current service pack. For information about upgrading your domains, see the BEA WebLogic Platform Upgrade Planning Guide at http://download.oracle.com/docs/cd/E13196_01/platform/docs81/upgrade/index.html.
By default, all the predefined configuration templates provided with your WebLogic Platform installation are located in the following directory:
WL_HOME\common\templates\domains
The configuration templates are summarized in the following table.
Note: The availability of predefined configuration templates depends on which WebLogic Platform components are installed; the WebLogic Platform components required for each template are identified in the following table.
|
Creates the Avitek Medical Records domain outside the installed kit. This domain is a WebLogic Server sample application suite that concisely demonstrates all aspects of the J2EE platform. |
|||
|
Creates a domain that supports the development of WebLogic Integration solutions. Note: To create a domain that supports the development of WebLogic Server Process Edition solutions, use the Basic WebLogic Integration Domain template. If you have an existing WebLogic Server-based domain, you can extend it to include the resources required for WebLogic Server Process Edition by using the WebLogic Integration Extension Template. |
|||
|
Creates a domain that supports the development of applications using all WebLogic Platform components. |
|||
|
Creates a domain that supports the development of WebLogic Portal solutions. |
|||
|
Creates a simple WebLogic Server domain without any sample applications. |
|||
|
Creates a domain that supports the development of WebLogic Workshop solutions. |
|||
|
Creates the WebLogic Server Examples domain outside the installed kit. This domain contains a collection of examples that illustrate best practices for coding individual J2EE APIs. |
The following sections describe the default directory structure and files created by each configuration template.
Avitek Medical Records is a WebLogic Server sample application suite that concisely demonstrates all aspects of the J2EE platform. The Avitek Medical Records Sample Domain configuration template allows you to create an Avitek Medical Records domain outside the installed kit. This configuration template is available when you install WebLogic Server.
By default, the following applications and resources are defined in an Avitek Medical Records Sample Domain:
The following table defines the default directory structure and files generated by the Avitek Medical Records Sample Domain configuration template. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the BEA_HOME\user_projects\domains\medrec directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.
|
Directory containing files used by the Configuration Wizard in support of creating and extending the domain. |
|
|
Directory containing files for any custom applications that you create. |
|
|
Directory containing XML file to be used as input to the Avitek Medical Records example. |
|
|
File containing server startup properties, including the user name and password required to boot 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 "Providing Usernames and Passwords to Start and Stop a Server" in the WebLogic Server Administration Console Online Help at the following URL: |
|
|
File containing the configuration information used by the Administration Server. For more information, see the WebLogic Server Configuration Reference at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/config_xml/index.html |
|
|
Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information. |
|
|
File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used. |
|
|
File containing initialization information for a PointBase JDBC database. |
|
|
Scripts that set up the Avitek Medical Records development environment on Windows and UNIX systems, respectively. |
|
|
Scripts used to start a Managed Server on Windows and UNIX systems, respectively. |
|
|
Scripts used to start the MedRec Administration Server on Windows and UNIX systems, respectively. |
|
|
Scripts used internally for the domain. These files can be ignored. |
|
For more information about the Avitek Medical Records example, see WebLogic Server Application Examples and Tutorials at the following URL:
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/samples.html
The Basic WebLogic Integration Domain configuration template allows you to create a basic WebLogic Integration domain, without installing sample applications. Domains created from this template support the WebLogic Server, WebLogic Workshop, and WebLogic Integration run-time functionality, including support for J2EE applications, Web applications, Web Services, custom controls, and business processes. You use domains created from this configuration template as the foundations for development of WebLogic Integration applications. The Basic WebLogic Integration Domain configuration template is available when you install WebLogic Integration or when you install all the components of WebLogic Platform.
By default, when using the Basic WebLogic Integration Domain configuration 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.
Note: To create a domain that supports the development of WebLogic Server Process Edition solutions, use the Basic WebLogic Integration Domain template. If you have an existing WebLogic Server-based domain, you can extend it to include the resources required for WebLogic Server Process Edition by using the WebLogic Integration Extension Template.
The following table defines the default directory structure and files generated by the Basic WebLogic Integration Domain configuration template. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the BEA_HOME\user_projects\domains\integration directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.
|
Directory containing the files for the B2BDefaultWebApp application and any custom application files that you create. |
|
|
Directory containing files used by the Configuration Wizard in support of creating and extending the domain. |
|
|
Directory serving as a disk-based JMS file store to store persistent messages and durable subscribers. |
|
|
Directory containing a script that targets specified services and applications to the appropriate servers or clusters. This script supplements the Configuration Wizard's auto-targeting of services and applications to a cluster. |
|
|
Directory serving as a placeholder for information used by the Application View control. |
|
|
Directory containing the file used in support of application integration debugging. |
|
|
File containing server startup properties, including the user name and password required to boot 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 "Providing Usernames and Passwords to Start and Stop a Server" in the WebLogic Server Administration Console Online Help at the following URL: |
|
|
File containing the configuration information used by the Administration Server. For more information, see the WebLogic Server Configuration Reference at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/config_xml/index.html |
|
|
Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information. |
|
|
File containing administrative information about the domain, including version, type, name, author, description, and icon name. |
|
|
File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used. |
|
|
Script used to install Windows services. The script creates an entry for such services in the Windows Registry. As a result, the Windows system starts the specified service each time the system boots. This script can install the following services: |
|
|
File containing initialization information for a PointBase JDBC database. |
|
|
Scripts used to set up all the environment variables and Java options required to run WebLogic Server, in the WebLogic Integration domain, on Windows and UNIX systems, respectively. |
|
|
Scripts used to start a Managed Server on Windows and UNIX systems, respectively. |
|
|
Scripts used to start the PointBase Console on Windows and UNIX systems, respectively. |
|
|
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
|
|
Scripts used to stop a specified Managed Server on Windows and UNIX systems, respectively. |
|
|
Scripts used to stop the Administration Server on Windows and UNIX systems, respectively. |
|
|
File containing the project information used to build a Web application. |
|
|
Scripts used to compile a Web application into an EAR file on Windows and UNIX systems, respectively. |
|
|
File containing domain-specific parameters that are used by WebLogic Integration. |
|
|
File containing domain-specific PointBase database information for the default database named |
|
|
File containing domain-specific PointBase database information for the default database named |
|
|
File containing domain-specific parameters that are used by WebLogic Workshop. |
The Basic WebLogic Platform Domain configuration template allows you to create a domain that supports the development of applications using all WebLogic Platform components. This template is available when you install WebLogic Platform.
The following table defines the default directory structure and files generated by the Basic WebLogic Platform Domain configuration template. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the BEA_HOME\user_projects\domains\platform directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.
|
Directory containing the files for the B2BDefaultWebApp application and any custom application files that you create. |
|
|
Directory containing files used by the Configuration Wizard in support of creating and extending the domain. |
|
|
Directory serving as a disk-based JMS file store to store persistent messages and durable subscribers. |
|
|
Directory containing a script that targets specified services and applications to the appropriate servers or clusters. This script supplements the Configuration Wizard's auto-targeting of services and applications to a cluster. |
|
|
Directory containing information used by the Application View control. |
|
|
Directory containing the file used in support of application integration debugging. |
|
|
File containing server startup properties, including the user name and password required to boot 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 "Providing Usernames and Passwords to Start and Stop a Server" in the WebLogic Server Administration Console Online Help at the following URL: |
|
|
File containing the configuration information used by the Administration Server. For more information, see the WebLogic Server Configuration Reference at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/config_xml/index.html |
|
|
Scripts used to create database objects on Windows and UNIX systems, respectively. By default, |
|
|
File containing two types of data used by |
|
|
Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information. |
|
|
File containing administrative information about the domain, including version, type, name, author, description, and icon name. |
|
|
File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used. |
|
|
Script used to install Windows services. The script creates an entry for such services in the Windows Registry. As a result, the Windows system starts the specified service each time the system boots. This script can install the following services: |
|
|
File containing initialization information for a PointBase JDBC database. |
|
|
Scripts used by |
|
|
Scripts used to set up all the environment variables and Java options required to run WebLogic Server, in the WebLogic Platform domain, on Windows and UNIX systems, respectively. |
|
|
Scripts used to start a Managed Server on Windows and UNIX systems, respectively. |
|
|
Script used to start the console for the PointBase database. |
|
|
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
|
|
Script used to stop a specified Managed Server on Windows and UNIX systems, respectively. |
|
|
Scripts used to stop the Administration Server on Windows and UNIX systems, respectively. |
|
|
File containing the project information used to build a Web application. |
|
|
Scripts used to compile a Web application into an EAR file on Windows and UNIX systems, respectively. |
|
|
File containing domain-specific parameters that are used by WebLogic Integration. |
|
|
File containing domain-specific PointBase database information for the default database named |
|
|
File containing domain-specific PointBase database information for the default database named |
|
|
File containing domain-specific parameters that are used by WebLogic Workshop. |
|
The Basic WebLogic Portal Domain configuration template allows you to create a basic WebLogic Portal domain, without installing sample applications. Domains created from this template support the WebLogic Server, WebLogic Workshop, and WebLogic Portal run-time functionality, including support for J2EE applications, Web applications, Web Services, custom controls, and portals. You use domains created from this configuration template as the foundations for development of WebLogic Portal applications. The Basic WebLogic Portal Domain configuration template is available when you install WebLogic Portal or when you install all components of WebLogic Platform.
By default, when using the Basic WebLogic Portal Domain configuration 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 Portal Domain configuration template. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the BEA_HOME\user_projects\domains\portalDomain directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.
|
Directory containing files used by the Configuration Wizard in support of creating and extending the domain. |
|
|
Directory serving as a disk-based JMS file store to store persistent messages and durable subscribers. |
|
|
Directory containing a script that targets specified services and applications to the appropriate servers or clusters. This script supplements the Configuration Wizard's auto-targeting of services and applications to a cluster. |
|
|
File containing server startup properties, including the user name and password required to boot 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 "Providing Usernames and Passwords to Start and Stop a Server" in the WebLogic Server Administration Console Online Help at the following URL: |
|
|
File containing the configuration information used by the Administration Server. For more information, see the WebLogic Server Configuration Reference at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/config_xml/index.html |
|
|
Scripts used to create database objects on Windows and UNIX systems, respectively. By default, |
|
|
File containing two types of data used by |
|
|
Files used for bootstrapping including authentication (user and group) and role mapping. These files contain LDAP-specific information. |
|
|
File containing administrative information about the domain, including version, type, name, author, description, and icon name. |
|
|
File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used. |
|
|
Script used to install Windows services. The script creates an entry for such services in the Windows Registry. As a result, the Windows system starts the specified service each time the system boots. This script can install the following services: |
|
|
File containing initialization information for a PointBase JDBC database. |
|
|
Scripts used by |
|
|
Scripts used to set up all the environment variables and Java options required to run WebLogic Server, in the WebLogic Portal domain, on Windows and UNIX systems, respectively. |
|
|
Scripts used to start a Managed Server on Windows and UNIX systems, respectively. |
|
|
Scripts used to start the PointBase Console on Windows and UNIX systems, respectively. |
|
|
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
|
|
Script used to stop a specified Managed Server on Windows and UNIX systems, respectively. |
|
|
Scripts used to stop the Administration Server on Windows and UNIX systems, respectively. |
|
|
Scripts used to compile a Web application into an EAR file on Windows and UNIX systems, respectively. |
|
|
File containing domain-specific PointBase database information for the default database named |
|
|
File containing domain-specific PointBase database information for the default database named |
|
|
File containing domain-specific parameters that are used by WebLogic Workshop. |
|
The Basic WebLogic Server Domain configuration template allows you to create a simple WebLogic Server domain without installing any sample applications. This template is available when you install WebLogic Server.
By default, when using the Basic WebLogic Server Domain configuration 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 configuration template. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the BEA_HOME\user_projects\domains\mydomain directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.
|
Directory containing files used by the Configuration Wizard in support of creating and extending the domain. |
|
|
Directory serving as a placeholder for any custom application files that you create. |
|
|
Directory serving as a disk-based JMS file store to store persistent messages and durable subscribers. |
|
|
File containing server startup properties, including the user name and password required to boot 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 "Providing Usernames and Passwords to Start and Stop a Server" in the WebLogic Server Administration Console Online Help at the following URL: |
|
|
File containing the configuration information used by the Administration Server. For more information, see the WebLogic Server Configuration Reference at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/config_xml/index.html |
|
|
Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information. |
|
|
File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used. |
|
|
Script used to install the Administration Server as a Windows service. The script creates an entry for the service in the Windows Registry. As a result, the Windows system starts the service each time the system boots. |
|
|
Scripts that set up the development environment on Windows and UNIX systems, respectively. |
|
|
Scripts used to start a Managed Server on Windows and UNIX systems, respectively. |
|
|
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
|
|
Scripts used to stop the Administration Server on Windows and UNIX systems, respectively. |
|
|
Script used to uninstall the Administration Server as a Windows service. |
The Basic WebLogic Workshop Domain configuration template allows you to create a basic WebLogic Workshop domain, without installing sample applications. Domains created from this template support the WebLogic Server and WebLogic Workshop run-time functionality, including support for J2EE applications, Web applications, Web Services, and custom controls. Use domains created from this template as the foundations for development of WebLogic Workshop applications. This template is available when you install WebLogic Server, WebLogic Integration, WebLogic Portal, and WebLogic Platform.
By default, when using the Basic WebLogic Workshop Domain configuration 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.
By default, the following applications and resources are defined in a Basic WebLogic Workshop Domain:
The following table defines the default directory structure and files generated by the Basic WebLogic Workshop Domain configuration template. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the BEA_HOME\user_projects\domains\workshop directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.
|
Directory containing files used by the Configuration Wizard in support of creating and extending the domain. |
|
|
Directory serving as a disk-based JMS file store to store persistent messages and durable subscribers. |
|
|
Directory containing a script that targets specified services and applications to their appropriate servers or clusters. This script supplements the Configuration Wizard's auto-targeting of services and applications to a cluster. |
|
|
File containing server startup properties, including the user name and password required to boot 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 "Providing Usernames and Passwords to Start and Stop a Server" in the WebLogic Server Administration Console Online Help at the following URL: |
|
|
File containing the configuration information used by the Administration Server. For more information, see the WebLogic Server Configuration Reference at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/config_xml/index.html |
|
|
Files used for bootstrapping including authentication (user and group) and role mapping. These files contain LDAP-specific information. |
|
|
File containing administrative information about the domain, including version, type, name, author, description, and icon name. |
|
|
File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used. |
|
|
Script used to install Windows services. The script creates an entry for such services in the Windows Registry. As a result, the Windows system starts the specified service each time the system boots. This script can install the following services: |
|
|
File containing initialization information for a PointBase JDBC database. |
|
|
Scripts used to set up all the environment variables and Java options required to run WebLogic Server, in the WebLogic Workshop domain, on Windows and UNIX systems, respectively. |
|
|
Scripts used to start a Managed Server on Windows and UNIX systems, respectively. |
|
|
Scripts used to start the PointBase Console on Windows and UNIX systems, respectively. |
|
|
Script used to start the Administration Server on Windows and UNIX systems, respectively. |
|
|
Script used to stop a specified Managed Server on Windows and UNIX systems, respectively. |
|
|
Scripts used to stop the Administration Server on Windows and UNIX systems, respectively. |
|
|
File containing the project information used to build a Web application. |
|
|
Scripts used to compile a Web application into an EAR file on Windows and UNIX systems, respectively. |
|
|
File containing domain-specific PointBase database information for the default database named |
|
|
File containing domain-specific PointBase database information for the default database named |
|
|
File containing domain-specific parameters that are used by WebLogic Workshop. |
For more information about WebLogic Workshop, see the following URL:
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/index.html
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. The WebLogic Server Examples Domain configuration template allows you to create the WebLogic Server Examples domain outside the installed kit. This template is available when you install WebLogic Server.
By default, the following applications and resources are defined in a WebLogic Server Examples Domain:
After creating a domain with the template, you can start the server. When the server is started, the PointBase database server is also started.
The following table defines the default directory structure and files generated by the WebLogic Server Examples Domain configuration template. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the BEA_HOME\user_projects\domains\examples directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.
|
Directory containing files used by the Configuration Wizard in support of creating and extending the domain. |
|
|
Directory serving as a placeholder for any custom application files that you create. |
|
|
Directory containing the files for an example Web application. |
|
|
Directory containing the files for an example Web application. |
|
|
File containing server startup properties, including the user name and password required to boot 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 "Providing Usernames and Passwords to Start and Stop a Server" in the WebLogic Server Administration Console Online Help at the following URL: |
|
|
File containing the configuration information used by the Administration Server. For more information, see the WebLogic Server Configuration Reference at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/config_xml/index.html |
|
|
Files used for bootstrapping tasks, including authentication (user and group), authorization, credential mapping, and role mapping. These files contain LDAP-specific information. |
|
|
File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used. |
|
|
File containing initialization information for a PointBase JDBC database. |
|
|
Scripts that set up the WebLogic Server Examples development environment on Windows and UNIX systems, respectively. |
|
|
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
|
|
Scripts used to start a Managed Server on Windows and UNIX systems, respectively. |
|
For more information about the samples that are supported in the WebLogic Server Examples domain, see WebLogic Server Application Examples and Tutorial at the following URL:
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/samples.html
WebLogic Platform provides predefined extension templates that are installed with the product. You can easily extend an existing WebLogic domain by using the Configuration Wizard's Extend an existing WebLogic configuration option and selecting one or more of the predefined extension templates. For information about template dependencies, see Relationships Between Templates
By default, all the predefined extension templates provided with your WebLogic Platform installation are located in the following directory:
WL_HOME\common\templates\applications
The extension templates are summarized in the following table.
Note: The availability of predefined extension templates depends on which WebLogic Platform components are installed; the WebLogic Platform components required for each template are shown in the table.
|
Imports the static resources for a basic Web application, including an HTML file, image files, and required XML descriptors. Use the Default Web Application as a launching point from which to develop your own Web applications. |
|||
|
Imports the resources needed to support the development of WebLogic Integration applications. Support for WebLogic Integration application development is already provided in the following configuration templates: Note: To create a domain that supports the development of WebLogic Server Process Edition solutions, use the Basic WebLogic Integration Domain template. If you have an existing WebLogic Server-based domain, you can extend it to include the resources required for WebLogic Server Process Edition by using the WebLogic Integration Extension template. |
|||
|
Imports the resources needed to support the development of WebLogic Portal applications. Support for WebLogic Portal application development is already provided in the following configuration templates: |
|||
|
Imports the resources needed to support the development of WebLogic Workshop applications. Support for WebLogic Workshop application development is already provided in the following configuration templates: |
This section provides the following topics:
You can create a basic WebLogic domain using the predefined configuration templates or you can create a basic WebLogic domain and extend it incrementally using the extension templates. The following table shows the relationship between the templates and the domains created.
WebLogic Workshop resources must already be set up in your domain before you can start importing resources from the WebLogic Integration or WebLogic Portal extension template. When you select an extension template, the Configuration Wizard checks to make sure the required resources are available for you. If desired, the Configuration Wizard allows you to import the WebLogic Workshop, WebLogic Integration, and WebLogic Portal extensions simultaneously. (Note that there are no prerequisites for using the DefaultWebApp extension template.)
You can extend your domain to support a basic Web application quickly and easily by using the Configuration Wizard to import resources from the Default WebApp extension template. For more information about developing Web applications, see Developing Web Applications for WebLogic Server at the following URL:
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/webapp/index.html
The following table shows the application resources and services, provided by the Default WebApp extension template, that can be imported into an existing WebLogic domain. The information is based on the assumption that the existing WebLogic domain was created using the Basic WebLogic Server Domain template.
To extend your domain to support WebLogic Integration, use the Configuration Wizard to import resources and services from the WebLogic Integration extension template.
Note: WebLogic Workshop resources must already be set up in your domain before you can start importing the WebLogic Integration extension template, unless you import the WebLogic Workshop and WebLogic Integration extensions at the same time.
To create a domain that supports the development of WebLogic Server Process Edition solutions, use the Basic WebLogic Integration Domain template. If you have an existing WebLogic Server-based domain, you can extend it to include the resources required for WebLogic Server Process Edition by using the WebLogic Integration Extension template.
The following table shows the application resources and services provided by the WebLogic Integration extension template that can be imported into an existing domain. The information is based on the assumption that the existing WebLogic domain was created using the Basic WebLogic Server Domain template.
To extend your domain to support WebLogic Portal, use the Configuration Wizard to import resources and services from the WebLogic Portal extension template.
Note: WebLogic Workshop resources must already be set up in your domain before you can start importing the WebLogic Portal extension template, unless you import the WebLogic Workshop and WebLogic Portal extensions at the same time.
The following table shows the application resources and services provided by the WebLogic Portal extension template that can be imported into an existing WebLogic domain. The information is based on the assumption that the existing WebLogic domain was created using the Basic WebLogic Server Domain template.
To extend your domain to support WebLogic Workshop, use the Configuration Wizard to import resources and services from the WebLogic Workshop extension template. WebLogic Workshop resources are required before you can extend a domain to support WebLogic Integration, WebLogic Portal, or both (that is, a full Platform domain).
The following table shows the application resources and services provided by the WebLogic Workshop extension template that can be imported into an existing WebLogic domain. The information is based on the assumption that the existing WebLogic domain was created using the Basic WebLogic Server Domain template.
|
|
|