Skip navigation.
Downloads | Product Documentation | Support

Administration Guide

# Deploying Liquid Data Components

This chapter describes how you can deploy BEA Liquid Data for WebLogic components using the Deploy tab on the Liquid Data node in the Administration Console. It contains the following sections:

- Liquid Data Components to Deploy
- Navigating to the Deploy Tab

Administrators can use the Deploy tab to shut down applications (in the form of JAR, WAR, or EAR files) on a WebLogic Server without interrupting other running applications. Administrators can also upgrade an application by undeploying it, substituting an updated JAR, WAR, or EAR file, and then redeploying the updated application on target servers.

Note: This chapter describes how to deploy core Liquid Data software components only. In most if not all cases, however, the same results can be achieved automatically when creating a Liquid Data domain or extending an existing domain for Liquid Data through the BEA WebLogic Configuration Wizard. There may be additional tasks required to deploy other Liquid Data components. See Deployment Tasks in the Deployment Guide for details.

# Liquid Data Components to Deploy

The `LDS.ear` file contains the following deployable components:

Table 13-1 Contents of the LDS.ear file

Component | Description | Deployment Target
--- | --- | ---
`ejb_query.jar` | EJB that contains all query-related classes, including the Query Processor and stateless session bean. For more information, see the Liquid Data Javadoc. | For a multi-node and clustered deployment, deploy to each Managed Server.
`ejb_qbc.jar` | EJB for Data View Builder to obtain configuration information from the Liquid Data Server. | For a multi-node and clustered deployment, deploy to each Managed Server.
`XMediator.war` | Initializes the Liquid Data Server. | For a multi-node and clustered deployment, deploy to each Managed Server.
`ldconsole.war` | Liquid Data configuration tabs that appear in the WebLogic Server Administration Console. | Always deploy to an Administration Server.
`cacheEjb.jar` | EJB that manages results caching for stored queries that are configured for results caching. For more information, see Configuring the Query Results Cache on page 22-1. | For a multi-node and clustered deployment, deploy to each Managed Server.
`ldcacheListener.war` | Listener application that listens to notifications from the MBean for changes to the global cache status (enabled or disabled), changes to a stored query that is cached, and changes to the cache policy for a stored query. | For a multi-node and clustered deployment, deploy to each Managed Server.

# Navigating to the Deploy Tab

To navigate to the Deploy tab:

1. In the left pane of the Administration Console, click the Liquid Data node.
2. In the right pane, click the Deploy tab.

The Administration Console displays the Liquid Data Deploy tab.

3. Click on the link to go to Deployments > Applications > LDS.ear.

The Administration Console displays the WebLogic Server Deploy tab showing the deployment status of the Liquid Data enterprise archive file (`LDS.ear`) as deployed in WebLogic Server.

4. Select target servers and deploy or undeploy as needed. For instructions, see Deployment Tasks in the Deployment Guide.