bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Deploying Liquid Data

Introduction

Deployment is the process of setting up BEA Liquid Data for WebLogicTM in a production environment. This topic introduces Liquid Data deployment. It contains the following sections:

- WebLogic Platform Deployment Documentation

- Resources to Deploy

- Resources to Configure

- Overview of Deployment Steps

WebLogic Platform Deployment Documentation

In addition to this document, the BEA WebLogic PlatformTM provides a comprehensive deployment documentation page at the following URL: http://download.oracle.com/docs/cd/E13196_01/platform/docs70/interm/deploy.html

For specific WebLogic Platform components, see the following URLs:

Table 1-1 Deployment Documentation

Resource | Documentation
--- | ---
BEA WebLogic ServerTM | http://download.oracle.com/docs/cd/E13222_01/wls/docs70/deployment.html
BEA WebLogic IntegrationTM | http://download.oracle.com/docs/cd/E13214_01/wli/docs70/deploy/index.htm
BEA WebLogic PortalTM | http://download.oracle.com/docs/cd/E13218_01/wlp/docs70/dev/deploy.htm
BEA WebLogic WorkshopTM | http://download.oracle.com/docs/cd/E13226_01/workshop/docs70/help/index.html#guide/howdoi/navHowDoITopics.html

Resources to Deploy

The following table summarizes the primary resources involved in a Liquid Data deployment:

Table 1-2 Resources to Deploy in a Liquid Data Deployment

Resource | Description
--- | ---
WebLogic Platform | The WebLogic Platform includes the following components: WebLogic Server WebLogic Workshop WebLogic Integration WebLogic Portal Note: At a minimum, WebLogic Server must be deployed. Other components are deployed as needed.
Liquid Data software | Liquid Data is deployed in an enterprise archive (LDS.ear) file on a single WebLogic Server instance or, in a clustered deployment, across all servers in the cluster.
Liquid Data configuration | The following settings must be configured: Liquid Data server configuration data source descriptions server repository results cache configuration security, if used custom function descriptions, if used For more information, see Resources to Configure.
Data sources | Data sources used in Liquid Data queries must be deployed and accessible to the Liquid Data Server.

Resources to Configure

You need to configure the following resources as applicable for your deployment:

Table 1-3 Liquid Data Resources to Configure

Resource | Description
--- | ---
Liquid Data server settings | You need to configure server settings on the General tab in the Liquid Data node in the Administration Console, especially the repository location. For instructions, see Configuring Liquid Data Server Settings in the Liquid Data Administration Guide.
Data source descriptions | For each data source accessed in a Liquid Data query, you need to add a data source description using the Data Sources tab in the Liquid Data node in the Administration Console. Additional configuration tasks are required for certain data source types. For instructions, see the following topics in the Liquid Data Administration Guide: Configuring Access to Relational Databases Configuring Access to XML Files Configuring Access to Web Services Configuring Access to Application Views Configuring Access to Data Views
Server repository | You need to configure the location of the server repository on the General tab in the Liquid Data node in the Administration Console. You also need to populate and configure the repository on the Repository tab in the Liquid Data node in the Administration Console. For instructions, see Managing the Liquid Data Server Repository in the Liquid Data Administration Guide.
Results caching | If you want to cache results for stored queries in this deployment, you must explicitly enable results caching on the General tab in the Liquid Data node in the Administration Console. In addition, for each stored query that you want cached, you need to explicitly configure the caching policy. For instructions, see Configuring the Query Results Cache in the Liquid Data Administration Guide.
Security | If you want to use security in this deployment, you must enable secure mode on the General tab in the Liquid Data node in the Administration Console. In addition, you need to explicitly configure secure access to the Data View Builder, data source descriptions, custom function descriptions, the server repository, and stored queries. For instructions, see Implementing Security in the Liquid Data Administration Guide.
Custom functions | If custom functions are used in this deployment, you need to create a custom function description for each custom function and add certain files to the server repository. For instructions, see Configuring Access to Custom Functions in the Liquid Data Administration Guide.

Note: Alternatively, you can copy configuration information from another, fully configured Liquid Data Server according to the instructions in Copying a Server Configuration to Another Server.

Overview of Deployment Steps

The process of deploying Liquid Data involves the following basic steps:

1. Plan the deployment according to the instructions in Defining Deployment Requirements and Designing a Deployment. Completing these tasks is necessary to ensure that your deployment architecture best suits your business requirements.

2. Install the WebLogic Platform and Liquid Data software on the target server(s) according to the instructions in Installing Liquid Data.

3. On the target server(s), create a domain and deploy Liquid Data to that domain, as described in Deployment Tasks.

4. If it is not already up and running, start WebLogic Server in the domain according to the instructions in Starting and Stopping the Server in the Liquid Data Administration Guide.

5. Start the Administration Console and configure the resources described in Resources to Configure as applicable to your deployment.

6. Monitor the ongoing operation of the Liquid Data Server according to the instructions in Monitoring the Server in the Liquid Data Administration Guide.

7. Tune performance on the Liquid Data Server, as necessary, according to the instructions in Tuning Performance.

These steps provide only a summary of the steps required to deploy Liquid Data in a production environment. For example, multi-node and clustered deployments involve additional steps. For detailed deployment instructions based on the deployment architecture you are using, see Deployment Tasks.