bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Configuration Wizard Template Reference

WebLogic Portal Domain Template

This section includes the following topics:

- Template Description

- Creating a Domain Based on the WLP Domain Template

- Configuration and Supporting Files

Template Description

The WLP Domain template is used by the Configuration Wizard to create a WebLogic Portal domain. The domain that is created is a foundation upon which you build portals. The domain includes the configuration files, database, and scripts that define and run your server environment, provides a default security realm and predefined system administrators, and provides a set of WebLogic Portal administration tools. The template also creates supporting files and services for building portals and developing personalization and commerce functionality.

The template, which is made up of a central template file and many directories and files, is located in a JAR file in the following directory:

>     <BEA_HOME>/weblogic700/common/templates/domains/portal.jar

Inside the portal.jar file, the central template file, template.xml, is located in the META-INF subdirectory.

Other files and directories used by the template, but not included in portal.jar, are located in <BEA_HOME>/weblogic700/common/templates/shared.

No sample application data is provided with this template.

Purpose

Use the WLP Domain template in the Configuration Wizard to create a new domain that lets you build portals, take advantage of portal functionality, and implement WebLogic Portal's standard set of powerful personalization and commerce services.

Creating a Domain Based on the WLP Domain Template

This section describes how to create a functional domain based on the WLP Domain template. It includes the following topics:

- Process Overview

- Completing the Configuration of a Clustered Domain

Process Overview

The following table provides an overview of the steps required to create a domain based on the WLP Domain template.

Task | Refer to...
--- | ---
1. Initiate the Configuration Wizard to create a new domain. | Using the Configuration Wizard at the following URL: http://edocs.bea.com/platform/docs70/confgwiz/index.html
2. Select the WLP Domain template and respond to the prompts to create a new domain. | Using the Configuration Wizard at the following URL: http://edocs.bea.com/platform/docs70/confgwiz/index.html
3. If you set created a clustered domain, additional steps are required. | Completing the Configuration of a Clustered Domain.
4. Start WebLogic Server. | "Starting and Stopping the Server" in the "System Administration" section of the BEA WebLogic Portal Administration Guide at the following URL: http://edocs.bea.com/wlp/docs70/admin/sysadmin.htm

Completing the Configuration of a Clustered Domain

When running a clustered WebLogic Portal domain, data that is synchronized from the E-Business Control Center to the admin server must be properly replicated across all managed servers. Perform the following steps to ensure a sound synchronization process.

Also, if you are using WebLogic Portal's default content management services, you must perform additional setup tasks.

This section includes the following topics:

- Targeting Resources to the Admin Server

- Configuring a Proxy Server

- Configuring WebLogic Portal Content Management

Targeting Resources to the Admin Server

1. Launch the WebLogic Server Console tool for the domain. With the admin server running, enter the following URL:

   >     http://<hostname>:<port>/console

   For example, if you are launching the console on the server machine, the default URL is http://localhost:7501/console.

2. Target the datasyncPool JDBC Connection Pool to the admin server. Choose domain > Services > JDBC > Connection Pools > dataSyncPool, and on the Targets > Servers tab, make sure the admin server is in the Chosen list (Figure 10-1), and click Apply.

   Figure 10-1 Targeting the datasyncPool Connection Pool

3. Target the datasyncPool Transactional DataSource to the admin server (in addition to the cluster). Choose domain > Services > JDBC > Tx Data Sources > dataSyncPool, and on the Targets > Servers tab, move all servers from the Available list to the Chosen list, and click Apply.

4. Target the datasync Web application to the admin server (in addition to the cluster). Choose domain > Deployments > Web Applications > datasync, and on the Targets > Servers tab, move all servers from the Available list to the Chosen list, and click Apply.

5. Restart the admin server and any managed servers. (The JDBC connection pool targeting requires a server restart.) You might receive errors in the console when attempting this. If so, try editing the config.xml file in your domain folder to add the admin server to the Targets attribute of the following elements:

   - <JDBCConnectionPool ... Name="datasyncPool" Targets=" ">

   - <JDBCTxDataSource ... Name="datasyncPool" Targets=" ">

   - <WebAppComponent ... Name="datasync" Targets=" ">

For information about configuring clusters, refer to Using WebLogic Server Clusters at http://edocs.bea.com/wls/docs70/cluster/index.html.

Configuring a Proxy Server

You will also need to configure a cluster proxy server. See Using WebLogic Server Clusters at http://e-docs.bea.com/wls/docs70/cluster/index.html.

The easiest way to configure a cluster proxy for your domain is to use the weblogic.servlet.proxy.HttpClusterServlet. See "Configure Proxy Plug-Ins" in Setting up WebLogic Clusters at the following URL: http://e-docs.bea.com/wls/docs70/cluster/setup.html.

You can deploy a Web application with the HttpClusterServlet for your cluster to the admin server of the cluster and make it the admin server's default Web application. In this situation, be sure to map only the Web applications that are available through the cluster (for example, the WebLogic Portal Administration Tools at /portalAppTools/* and any portals or Web applications you add). In particular, be sure that /p13nConsole/* and /portalAppDataSync/* are not mapped by the HttpClusterServlet (if datasync is configured for the cluster).

Configuring WebLogic Portal Content Management

If you use WebLogic Portal's standard content management services, do one of the following:

- Target the commercePool to the admin server (domain > Services > JDBC > Connection Pools > commercePool), (since the loaddocs.properties file will be pointing to the admin server host and port), or

- Modify the loaddocs.properties file (in the domain directory) to point to a node in the cluster which has the commercePool deployed, or

- Modify the loaddocs.properties file to set the directToDB JDBC information to point to the appropriate database. By default, loaddocs.properties points to the included PointBase database. Then pass -conPool directToDB on the command line when invoking loaddocs.bat(sh) and loadads.bat(sh).

Configuration and Supporting Files

The WLP Domain template will create various directories and scripts under the new domain. The following table is a list of some of the directories and files that are installed with the domain.

Note: The following table is not a complete list of all directories and files.

Directory | Files | Purpose
--- | --- | ---
<domain> | config.xml | Defines your server configuration.
create_db*, db_settings.properties | Database creation script and properties file (for storing database server name, location, and so on).
loadads*, loaddocs* | Scripts for loading content metadata into the database when using WebLogic Portal's standard content management services.
start*, stop* | Scripts for starting and stopping the server(s).
demokey.pem, democert.pem | Provide sample SSL protocol support for servers in the domain.
<domain>/beaApps |  | Contains the directories of all enterprise applications and enterprise-level services in the domain, as explained in the following rows.
<domain>/beaApps/ paymentWSApp | payment.jar | Provides services for creating or connecting to a third-party payment Web service for commerce transactions.
<domain>/beaApps/ portalApp | campaign.jar, catalogws.jar, commerce_campaign_bridge_ util.jar, commerce_util.jar, customer.jar, document.jar, ebusiness.jar, ejbadvisor.jar, events.jar, ldapprofile.jar, mail.jar, p13n_util.jar, payment.jar, pipeline.jar, placeholder.jar, portal.jar, portal_util.jar, property.jar, rules.jar, tax.jar, usermgmt.jar | The default portal enterprise application under which you can build portals. These JARs enable the portal framework and provide such services as personalization, campaigns, commerce, and LDAP integration. The enterprise application also includes Web applications for: E-Business Control Center data synchronization to the server (datasync/). The WebLogic Portal Administration Tools (tools/) that let you create and manage users, manage portals, and manage commerce features.
<domain>/beaApps/ portalApp-project | portalApp-project.eaprj | This directory contains the infrastructure for creating and managing E-Business Control Center data for the enterprise application. The project file (portalApp-project.eaprj) manages all E-Business Control Center data and stores the information necessary to synchronize data to the server and retrieve server-side properties for defining queries. Also included are sets of predefined portal skins and layouts (/application-sync/library/ portal/).
<domain>/beaApps/ taxWSApp | tax.jar | Provides services for creating or connecting to a third-party tax Web service for commerce transactions.
<domain>/dmsBase |  | Contains placeholder directories for WebLogic Portal's standard content management services. Contains the following: /Ads - Placeholder directory for storing Web content and its metadata that is loaded into the database with the loadads script. /doc-schemas - Placeholder directory for storing metadata schemas. Schemas provide drop-down list functionality for defining queries against the content in the E-Business Control Center.
<domain>/pointbase | pointbase.ini, wlportal.dbn, wlportal$1.wal | pointbase.ini contains the default configuration for the PointBase database to run when the server is started. wlportal.dbn is the database node file used to store the actual data and metadata associated with the database. wlportal$1.wal is a write ahead log file and is used to maintain a record of all transactions against the database. If the system were to crash, this file aids in the recovery of information by performing a rollback to the last consistent state.

You can see examples of the pieces in a domain by viewing the WebLogic Portal examples, especially the Example Portal. The Example Portal domain is in <BEA_HOME>/weblogic700/samples/portal/sampleportalDomain.

For additional information about configuring your domain, refer to Creating and Configuring WebLogic Domains at http://edocs.bea.com/wls/docs70/admin_domain/index.html