bea.com | products | dev2dev | support | askBEA
 Download Docs   Site Map   Glossary 
Search
e-docs > Liquid Data for WebLogic > Deploying Liquid Data > Deployment Tasks

Deploying Liquid Data

 Previous Next Contents Index View as PDF  

Deployment Tasks

This topic describes the tasks involved in deploying BEA Liquid Data for WebLogicTM in a production environment. It includes the following sections:

 

Defining Deployment Requirements

Defining deployment requirements is a critical first step in the process of deploying Liquid Data in a production environment.

When planning a deployment, consider the following issues:

Clarifying the specific requirements for your deployment provides the knowledge you will need to design your deployment.

 

Designing a Deployment

This topic describes how to design a Liquid Data deployment for the following types of domains:

The deployment architecture that you use depends on the requirements for your particular production environment, as described in Defining Deployment Requirements.

If you are installing Liquid Data into an new domain you can use the WebLogic Platform Domain Configuration Wizard.

Figure 2-1 Liquid Data Options in WebLogic Platform Domain Wizard


 

The Domain Configuration Wizard supports creation of the following Liquid Data-enabled domains:

For  more information, see Creating a New WebLogic Domain in Using the Configuration Wizard in the WebLogic Platform documentation.

Note: If you are installing Liquid Data into an existing WebLogic Platform domain of any type, you will not be able to use the Domain Configuration Wizard for that purpose. Specific instructions for such deployments to existing domains can be found in the following:

In the cases of new deployments, the Domain Configuration Wizard makes most of the steps described in the above articles unnessary. However the discussion appropriate to your deployment should be reviewed since in each case there are a few steps to follow after running the Domain Configuration Wizard.

Single Domain Deployments

The following sections describe single domain deployments:

Single Server Deployments

In a single server (standalone) deployment, the Liquid Data software is installed on a standalone WebLogic Server. This design is the simplest to set up and it is the one suggested for use in a development environment or in a production environment in which Liquid Data is the primary application and failover protection is not the top priority.

The following illustration shows Liquid Data and WebLogic Server deployed on a single server:

Figure 2-2 Liquid Data and WebLogic Platform Deployed on a Single Server


 

For instructions on how to deploy Liquid Data and other WebLogic Platform components on a single server (standalone) deployment, see the following sections:

Multi-Node Deployments

A multi-node deployment distributes Liquid Data and WebLogic Platform software components across multiple server machines. A multi-node deployment allows you to run the various software components on dedicated servers, distributing resource contention across machines and optimizing system performance.

In each multi-node WebLogic Server domain, one WebLogic Server instance acts as the Administration Server—the server instance that configures, manages, and monitors all other server instances and resources in the domain. In a multi-node deployment, the Administration Server has administrative control over the domain and hosts the server repository. All other servers in the domain are configured as Managed Servers—servers that are managed by the Administration Server.

The following illustration shows Liquid Data deployed in a sample multi-node domain with three dedicated servers, one each for Liquid Data, WebLogic Portal, and WebLogic Workshop:

Figure 2-3 Liquid Data Deployed in a Multi-Node Domain


 

To deploy this design, follow the steps described in Deploying Liquid Data on a Multi-Node WebLogic Domain.

Clustered Deployments

A clustered deployment distributes Liquid Data and WebLogic Platform software components across multiple server machines. A cluster is a group of servers that work together to provide an application platform that is more powerful and reliable than a single server. A cluster appears to its clients as a single server but it is, in fact, a group of servers acting as one. In contrast to a multi-node deployment (in which Liquid Data and WebLogic Platform software components are installed separately on dedicated machines), in a clustered deployment, all Liquid Data and WebLogic Platform software components are installed on every machine.

A Liquid Data cluster is a deployment in which multiple copies of Liquid Data, referred to as instances, run simultaneously and work together to provide increased scalability and reliability. A Liquid Data cluster appears to clients to be a single Liquid Data instance. The server instances that constitute a cluster can run on the same machine, or can be located on different machines. You can increase a cluster's capacity by adding additional server instances to the cluster on an existing machine, or you can add machines to the cluster to host the incremental server instances. Each server instance in a cluster must run the same version of WebLogic Server. For extensive information about clustering, see Using WebLogic Server Clusters in the WebLogic Server documentation.

In each WebLogic Server domain, one WebLogic Server instance acts as the Administration Server—the server instance that configures, manages, and monitors all other server instances and resources in the domain. In a clustered deployment, the Administration Server has administrative control over the domain and hosts the server repository. All other servers in the domain are configured as Managed Servers—servers that are managed by the Administration Server. In a single instance deployment, the sole WebLogic Server instance is the Administration Server by default.

Note: In general, avoid configuring the Administration Server as part of the cluster.

In a clustered Liquid Data deployment, you select the algorithm to use for load balancing (round robin, weight-based, or random). Once configured, the load balancing mechanism directs incoming XQuery query requests to available Liquid Data Server instances. For more information, see Load Balancing in a Cluster in Using WebLogic Server Clusters in the WebLogic Server documentation.

In a clustered Liquid Data deployment, if a server fails, the WebLogic cluster can redirect request processing to another Liquid Data Server instance in the cluster. For more information, see "Replication and Failover for EJBs and RMIs" in Failover and Replication in a Cluster in Using WebLogic Server Clusters in the WebLogic Server documentation.

The following illustration shows Liquid Data deployed in a clustered domain.

Figure 2-4 Liquid Data Deployed in a Clustered Domain


 

This design is suggested for a deployment environment in which:

Before proceeding to deploy Liquid Data in a cluster, you should determine whether running Liquid Data on a dedicated server machine, as configured in Multi-Node Deployments, meets the performance and availability requirements for your deployment. Using the single server as a baseline, you can monitor run-time performance, conduct capacity planning, and test to determine whether a single machine provides sufficient performance at high query request loads.

To deploy this design, follow the steps described in:

Multi-Domain Deployments

In a multi-domain deployment, Liquid Data and the WebLogic Platform component are installed on separate WebLogic domains. To deploy this design for WebLogic Portal, follow the steps described in Deploying Liquid Data and WebLogic Portal in Separate Domains.

 

Deploying Liquid Data in a WebLogic Platform Domain

The following topics describe how to deploy Liquid Data with WebLogic Platform:

Deploying Liquid Data on a Standalone WebLogic Platform Domain

This section describes how to deploy Liquid Data on a standalone (single server) WebLogic Platform domain. For more information about single server deployments, see Single Server Deployments.

To deploy Liquid Data on a standalone WebLogic Platform domain:

  1. Install the WebLogic Platform on the target server according to the instructions in Installing WebLogic Platform in the WebLogic Platform documentation.

    Note: Do not start up WebLogic Server until you are instructed to do so later in this section.

  2. Install the Liquid Data software on the target server according to the instructions in Installing Liquid Data.

    Note: If you are using Liquid Data 1.1 or later and you are deploying Liquid Data into a new WebLogic Platform domain, you can create the domain and configure Liquid Data at the same time using the WebLogic Domain Configuration Wizard. After using the wizard, complete the deployment by following instructions starting with step 10.

    Check the Liquid Data Release Notes for the most up-to-date deployment instructions regarding using the Configuration Wizard.

  3. Unless you are deploying onto an existing WebLogic Platform domain, start the WebLogic Platform Configuration Wizard on the target node and create a WebLogic Platform domain (referred to in this section as platform_domain_name):

    • For the server type, select Single Server (Standalone).

    • Later in this procedure, you use the Administrative user created in this step to configure the domain.

    For  instructions, see Creating a New WebLogic Domain in Using the Configuration Wizard in the WebLogic Platform documentation.

    Note: If  you want to deploy Liquid Data on an existing WebLogic Platform domain instead of creating a new one, then the existing domain must use a WebLogic Server compatibility security realm. For more information, see Using Compatibility Security in Managing WebLogic Security in the WebLogic Server documentation.

  4. Edit the server startup file in BEA_HOME/user_projects/platform_domain_name. You need to specify the Liquid Data home directory (ld_home_dir), such as WL_HOME\liquiddata (on Windows) or $WL_HOME/liquiddata (Unix).

    Note: If your deployment will use application views as data sources, you need to add the path to the Application Integration wlai-client.jar file (such as %WLI_HOME%\lib\wlai-client.jar) to the end of the Liquid Data classpath (LDCLASSPATH).

    • Windows: Edit the startweblogic.cmd file and add the following command lines before startWLS.cmd executes:

      • set LD_HOME=ld_home_dir
      set LDI_LIB=%LD_HOME%\server\lib
      set LDCLASSPATH=%LDI_LIB%\wlldi.jar;%LDI_LIB%\LDS-descriptions.jar;%LDI_LIB%\castor-0.9.3.9.jar;%LDI_LIB%\xercesImpl.jar
      set CLASSPATH=%CLASSPATH%;%LDCLASSPATH%

    • Unix: Edit the startweblogic.sh file and add the following command lines before startWLS.sh executes:

      • LD_HOME=ld_home_dir
      LDI_LIB=$LD_HOME/server/lib 
      LDCLASSPATH=$LDI_LIB/wlldi.jar:$LDI_LIB/LDS-descriptions.jar:$LDI_LIB/castor-0.9.3.9.jar:$LDI_LIB/xercesImpl.jar 
      CLASSPATH=$CLASSPATH:$LDCLASSPATH
      export CLASSPATH

      Note: The $LDCLASSPATH must follow the current CLASSPATH setting.

  5. Copy the following files from LD_HOME/server/lib to BEA_HOME/user_projects/platform_domain_name.

    • ConfigMap.xml

    • webapp.template

  6. Start WebLogic Server and wait until it is in running mode.

  7. Start the Administration Console on the WebLogic Platform domain, logging in with the username/password you had created when you configured your domain, and configure Liquid Data security according to the following steps:

    1. In the left pane, click on platform_domain_name->Compatibility Security->Users and add a new user: ldsystem.

    2. Click on platform_domain_name->Compatibility Security->Groups and add a new group: LDAdmin.

    3. Add the ldsystem user to the LDAdmin group.

    4. Add the ldsystem user to the Administrators group.

    5. Click on platform_domain_name->Compatibility Security->ACLs and add a new ACL: LD.

    6. Add the following new permission attributes to the LD ACL: execute, read, and modify, and then add the Administrators group to the grantee list of permissions.

  8. Deploy the LDS.ear file according to the following steps:

    1. In the left pane, click on platform_domain_name->Deployments->Applications, click on Configure a New Application, click on "Upload it through your browser," select LD_HOME/server/lib/LDS.ear, and upload it.

    2. Click on the Select link next to the LDS.ear file, and then click Upload.

    3. Select the target server on which to deploy Liquid Data, and then click Configure and Deploy.

  9. Logout of the Administration Console.

  10. Start or restart the Administration Console, logging in as ldsystem.

  11. Configure data sources, security, the repository, and other Liquid Data server settings, as needed, according to the instructions in the Liquid Data Administration Guide.

Deploying Liquid Data on a Multi-Node WebLogic Domain

This section describes how to deploy Liquid Data on a WebLogic domain with an Administration Server and Managed Servers in a multi-node, non-clustered environment. For more information about multi-node domains, see Multi-Node Deployments.

Notes: Due to limitations with WebLogic Integration, do not configure WebLogic Integration on a WebLogic domain in a multi-node environment.

Before you begin, verify that your BEA software license is appropriate for your deployment.

To deploy Liquid Data on a multi-node WebLogic Platform domain:

  1. Install the WebLogic Platform on the machines that will host the Administration Server and the target Managed Servers, according to the instructions in Installing WebLogic Platform in the WebLogic Platform documentation.

    Note: Do not start up WebLogic Server until you are instructed to do so later in this section.

  2. Install the Liquid Data software on the machines that will host the Administration Server and the target server, according to the instructions in Installing Liquid Data.

    Note: If you are using Liquid Data 1.1 or later and you are deploying Liquid Data into a new WebLogic Platform domain, you can also configure Liquid Data using the WebLogic Platform Domain Configuration Wizard. After using the Wizard, complete the deployment by following instructions starting with step 15.

    Check the Liquid Data Release Notes for the most up-to-date deployment instructions regarding using the Configuration Wizard.

  3. Unless you are deploying onto an existing WebLogic domain, start the WebLogic Platform Configuration Wizard on the Administration Server and create a WebLogic domain (referred to in this section as wls_domain_name):

    • For the server type, select Admin Server with Managed Servers.

    • Later in this procedure, you use the Administrative user created in this step to configure the domain.

    For instructions, see Creating a New WebLogic Domain in Using the Configuration Wizard in the WebLogic Platform documentation.

    Note: If  you want to deploy Liquid Data on an existing WebLogic Platform domain instead of creating a new one, then the existing domain must use a WebLogic Server compatibility security realm. For more information, see Using Compatibility Security in Managing WebLogic Security in the WebLogic Server documentation.

  4. Unless you are deploying onto an existing WebLogic Platform domain, start the WebLogic Platform Configuration Wizard on each Managed Server in the domain, create a WebLogic Platform domain with same name as the one created on the Administration Server, and, for the server type, select Managed Server (with Owning Admin Server Configuration).

  5. Edit the server startup files in BEA_HOME/user_projects/wls_domain_name. You need to specify the Liquid Data home directory (ld_home_dir), such as WL_HOME\liquiddata (on Windows) or $WL_HOME/liquiddata (Unix).

    Note: If your deployment will use application views as data sources, you need to add the path to the Application Integration wlai-client.jar file (such as %WLI_HOME%\lib\wlai-client.jar) to the end of the Liquid Data classpath (LDCLASSPATH).

    • Windows: Edit the startweblogic.cmd file (on the Administration Server and startManagedWeblogic.cmd file (on Managed Servers) and add the following command lines before startWLS.cmd executes:

      • set LD_HOME=ld_home_dir
      set LDI_LIB=%LD_HOME%\server\lib
      set LDCLASSPATH=%LDI_LIB%\wlldi.jar;%LDI_LIB%\LDS-descriptions.jar;%LDI_LIB%\castor-0.9.3.9.jar;%LDI_LIB%\xercesImpl.jar
      set CLASSPATH=%CLASSPATH%;%LDCLASSPATH%

    • Unix: Edit the startweblogic.sh file (on the Administration Server and startManagedWeblogic.sh file (on Managed Servers) and add the following command lines before startWLS.sh executes:

      • LD_HOME=ld_home_dir
      LDI_LIB=$LD_HOME/server/lib 
      LDCLASSPATH=$LDI_LIB/wlldi.jar:$LDI_LIB/LDS-descriptions.jar:$LDI_LIB/castor-0.9.3.9.jar:$LDI_LIB/xercesImpl.jar 
      CLASSPATH=$CLASSPATH:$LDCLASSPATH
      export CLASSPATH

      Note: The $LDCLASSPATH must follow the current CLASSPATH setting.

  6. On the Administration Server, copy the following files from LD_HOME/server/lib to BEA_HOME/user_projects/platform_domain_name.

    • ConfigMap.xml

    • webapp.template

  7. Start the Administration Server and wait until it is in running mode.

  8. On the Administration Server, start the Administration Console on the WebLogic domain, logging in as an administrator, and configure Liquid Data security according to the following steps:

    1. In the left pane, click on wls_domain_name->Compatibility Security->Users and add a new user: ldsystem.

    2. Click on wls_domain_name->Compatibility Security->Groups and add a new group: LDAdmin.

    3. Add the ldsystem user to the LDAdmin group.

    4. Add the ldsystem user to the Administrators group.

    5. Click on wls_domain_name->Compatibility Security->ACLs and add a new ACL: LD.

    6. Add the following new permission attributes to the LD ACL: execute, read, and modify, and then add the Administrators group to the grantee list of permissions.

  9. Start all Managed Servers in the domain and wait until they are all in running mode.

  10. Deploy the LDS.ear file according to the following steps:

    1. In the left pane, click on wls_domain_name->Deployments->Applications, click on Configure a New Application, click on "Upload it through your browser," select LD_HOME/server/lib/LDS.ear, and upload it.

    2. Click on the Select link next to the LDS.ear file, and then click Upload.

    3. Select one or more target Managed Servers on which to deploy Liquid Data, and then click Configure and Deploy.

      Note: Do not deploy the LDS.ear file on the Administration Server.

  11. Verify that the following files are deployed successfully:

    • ldconsole.war

    • ldcacheListener.war

    • cacheEjb.jar

    • ejb_query.jar

    • XMediator.war

    • ejb_qbc.jar

  12. In the left pane, click on wls_domain_name->Deployments->Applications->LDS->ldconsole.war, click the Targets tab, select the Administration Server from the list of available servers, and then click Apply.

  13. Click on the Deploy tab and then click the Deploy button to deploy ldconsole.war to the Administration Server.

  14. Exit the Administration Console.

  15. Start or restart the Administration Console, logging in as ldsystem.

  16. Configure data sources, security, the repository, and other Liquid Data server settings, as needed, according to the instructions in the Liquid Data Administration Guide.

Deploying a Liquid Data Cluster on a WebLogic Platform Domain

This section describes how to deploy a Liquid Data cluster on a WebLogic domain with an Administration Server and Managed Servers. Clustering is typically used to provide scalability in deployments with high volumes of query requests and to provide fail-over protection in deployments with high availability requirements. For more information about clustered deployments, see Clustered Deployments.

Note: Before you begin, verify that your BEA software license is appropriate for your deployment.

To deploy a Liquid Data cluster on a WebLogic Platform domain:

  1. Install the WebLogic Platform on the machines that will host the Administration Server and all target Managed Servers, according to the instructions in Installing WebLogic Platform in the WebLogic Platform documentation.

    Note: Do not start up WebLogic Server until you are instructed to do so later in this section.

  2. Install the Liquid Data software on the machines that will host the Administration Server and all target Managed Servers, according to the instructions in Installing Liquid Data.

    Note: If you are using Liquid Data 1.1 or later and you are deploying Liquid Data into a new WebLogic Platform domain, you can also configure Liquid Data using the WebLogic Platform Domain Configuration Wizard. After using the Wizard, complete the deployment by following instructions starting with step 16.

    Check the Liquid Data Release Notes for the most up-to-date deployment instructions regarding using the Configuration Wizard.

  3. Unless you are deploying onto an existing WebLogic domain, start the WebLogic Platform Configuration Wizard on the Administration Server and create a clustered WebLogic domain (referred to in this section as platform_domain_name):

    • For the server type, select Admin Server with Clustered Managed Server(s).

    • Later in this procedure, you use the Administrative user created in this step to configure the domain.

    For instructions, see Creating a New WebLogic Domain in Using the Configuration Wizard in the WebLogic Platform documentation.

    Note: If  you want to deploy Liquid Data on an existing WebLogic Platform domain instead of creating a new one, then the existing domain must use a WebLogic Server compatibility security realm. For more information, see Using Compatibility Security in Managing WebLogic Security in the WebLogic Server documentation.

  4. Unless you are deploying onto an existing WebLogic Platform domain, start the WebLogic Platform Configuration Wizard on each Managed Server in the cluster, create a WebLogic Platform domain with same name as the one created on the Administration Server, and, for the server type, select Managed Server (with Owning Admin Server Configuration).

  5. Edit the server startup files in BEA_HOME/user_projects/platform_domain_name. You need to specify the Liquid Data home directory (ld_home_dir), such as WL_HOME\liquiddata (on Windows) or $WL_HOME/liquiddata (Unix).

    Note: If your deployment will use application views as data sources, you need to add the path to the Application Integration wlai-client.jar file (such as %WLI_HOME%\lib\wlai-client.jar) to the end of the Liquid Data classpath (LDCLASSPATH).

    • Windows: Edit the startweblogic.cmd file (on the Administration Server and startManagedWeblogic.cmd file (on Managed Servers) and add the following command lines before startWLS.cmd executes:

      • set LD_HOME=ld_home_dir
      set LDI_LIB=%LD_HOME%\server\lib
      set LDCLASSPATH=%LDI_LIB%\wlldi.jar;%LDI_LIB%\LDS-descriptions.jar;%LDI_LIB%\castor-0.9.3.9.jar;%LDI_LIB%\xercesImpl.jar
      set CLASSPATH=%CLASSPATH%;%LDCLASSPATH%

    • Unix: Edit the startweblogic.sh file (on the Administration Server and startManagedWeblogic.sh file (on Managed Servers) and add the following command lines before startWLS.sh executes:

      • LD_HOME=ld_home_dir
      LDI_LIB=$LD_HOME/server/lib 
      LDCLASSPATH=$LDI_LIB/wlldi.jar:$LDI_LIB/LDS-descriptions.jar:$LDI_LIB/castor-0.9.3.9.jar:$LDI_LIB/xercesImpl.jar 
      CLASSPATH=$CLASSPATH:$LDCLASSPATH
      export CLASSPATH

      Note: The $LDCLASSPATH must follow the current CLASSPATH setting.

  6. On the Administration Server, copy the following files from LD_HOME/server/lib to BEA_HOME/user_projects/platform_domain_name.

    • ConfigMap.xml

    • webapp.template

  7. Start the Administration Server and wait until it is in running mode.

  8. On the Administration Server, start the Administration Console on the WebLogic Platform domain, logging in with the username/password you had created when you configured your domain, and configure Liquid Data security according to the following steps:

    1. In the left pane, click on platform_domain_name->Compatibility Security->Users and add a new user: ldsystem.

    2. Click on platform_domain_name->Compatibility Security->Groups and add a new group: LDAdmin.

    3. Add the ldsystem user to the LDAdmin group.

    4. Add the ldsystem user to the Administrators group.

    5. Click on platform_domain_name->Compatibility Security->ACLs and add a new ACL: LD.

    6. Add the following new permission attributes to the LD ACL: execute, read, and modify, and then add the Administrators group to the grantee list of permissions.

  9. By default, WebLogic Server uses the round-robin algorithm as the default load balancing strategy for clustered object stubs. If you want to use weight-based or random load balancing for EJBs and RMI objects instead, complete the following steps:

    1. In the left pane of the Administration Console, select the Clusters node.

    2. Select your cluster.

    3. Click the drop-down arrow next to the Default Load Algorithm to display load balancing algorithms.

    4. In the item list, select the load balancing algorithm you want to use in the cluster.

    5. Enter the desired value in the Service Age Threshold field (see the Administration Console Online Help for more information).

    6. Click Apply to save your changes.

    For more information about load balancing algorithms, see "Load Balancing for EJBs and RMI Objects" in Load Balancing in a Cluster in Using WebLogic Server Clusters in the WebLogic Server documentation.

  10. Start all Managed Servers in the domain and wait until they are all in running mode.

  11. Deploy the LDS.ear file according to the following steps:

    1. In the left pane, click on platform_domain_name->Deployments->Applications, click on Configure a New Application, click on "Upload it through your browser," select LD_HOME/server/lib/LDS.ear, and upload it.

    2. Click on the Select link next to the LDS.ear file, and then click Upload.

    3. Select the cluster on which to deploy Liquid Data, and then click Configure and Deploy.

      Note: Do not deploy the LDS.ear file on the Administration Server.

  12. Verify that the following files are deployed successfully:

    • ldconsole.war

    • ldcacheListener.war

    • cacheEjb.jar

    • ejb_query.jar

    • XMediator.war

    • ejb_qbc.jar

  13. In the left pane, click on platform_domain_name->Deployments->Applications->LDS->ldconsole.war, click the Targets tab, select the Administration Server from the list of available servers, and then click Apply.

  14. Click on the Deploy tab, click the Deploy button to deploy ldconsole.war to the Administration Server.

  15. Exit the Administration Console.

  16. Start or restart the Administration Console, logging in as ldsystem.

  17. In the left pane, click on the Liquid Data node, then click the General tab. The default repository directory is ldrepository in the BEA_HOME/user_projects/platform_domain_name directory.

    You need to change the repository directory path so that it points to a shared volume to which all Managed Servers have access. On Windows, for example, you would point to a shared network drive mapped to a specific drive letter (such as R:\ldrepos).

  18. On each Managed Server, you need configure the repository location by mounting (Unix NFS) or mapping (Windows) logical drives to point to the configured repository root on the Administration Server. The directory must be shared and mapped to a virtual disk name. The path must be identical to the value specified in the Repository Root Directory field on the General tab in the Liquid Data node.

    • On Unix, use NFS to mount the exported directory in the respective BEA_HOME/user_projects/platform_domain_name. Make a short cut of the mapped drive in the managed domain and name it the same as in the admin domain.

    • On Windows, map to the drive using the exact same drive letter and path (such as R:\ldrepos).

  19. Configure data sources, security, the repository, and other Liquid Data server settings, as needed, according to the instructions in the Liquid Data Administration Guide.

  20. Test the clustered deployment by verifying the operation of each machine—individually and in combination with other machines. Under a given query request load, you should see performance increase as you bring additional Managed Servers online.

 

Deploying Liquid Data in a WebLogic Integration Domain

The following sections describe how to deploy Liquid Data with WebLogic Integration.

Note: Due to limitations with WebLogic Integration, do not configure WebLogic Integration on a WebLogic domain in a multi-node environment.

Deploying Liquid Data On a Standalone WebLogic Integration Domain

This section describes how to deploy Liquid Data on a standalone (single server) WebLogic Integration domain. For more information about single server deployments, see Single Server Deployments.

To deploy Liquid Data on a standalone WebLogic Integration domain:

  1. Install the WebLogic Platform, which includes WebLogic Integration, on the target server according to the instructions in Installing WebLogic Platform in the WebLogic Platform documentation.

    Note: Do not start up WebLogic Server until you are instructed to do so later in this section.

  2. Install the Liquid Data software on the target server according to the instructions in Installing Liquid Data.

    Note: If you are using Liquid Data 1.1 or later and you are deploying Liquid Data into a new WebLogic Integration (WLI) domain, you can create the domain and configure Liquid Data at the same time using the WebLogic Domain Configuration Wizard. After using the Wizard, complete the deployment by following instructions starting with step 13.

    Check the Liquid Data Release Notes for the most up-to-date deployment instructions regarding using the Configuration Wizard.

  3. Unless you are deploying onto an existing WebLogic Integration domain, start the WebLogic Platform Configuration Wizard on the target server and create a WebLogic Integration domain (referred to in this section as wli_domain_name):

    • For the server type, select Single Server (Standalone Server).

    • Later in this procedure, you use the Administrative user created in this step to configure the domain.

    For  instructions, see Creating a New WebLogic Domain in Using the Configuration Wizard in the WebLogic Platform documentation.

    Note: If  you want to deploy Liquid Data on an existing WebLogic Integration domain instead of creating a new one, then the existing domain must use a WebLogic Server compatibility security realm. For more information, see Using Compatibility Security in Managing WebLogic Security in the WebLogic Server documentation.

  4. Edit the server startup file in BEA_HOME/user_projects/wli_domain_name. You need to specify the Liquid Data home directory (ld_home_dir), such as WL_HOME\liquiddata (on Windows) or $WL_HOME/liquiddata (Unix).

    Note: If your deployment will use application views as data sources, you need to add the path to the Application Integration wlai-client.jar file (such as %WLI_HOME%\lib\wlai-client.jar) to the end of the Liquid Data classpath (LDCLASSPATH).

    • Windows: Edit the startweblogic.cmd file. Immediately before the line in which WebLogic Server gets started, add the following command lines:

      • set LD_HOME=%BEA_HOME%\weblogic700\liquiddata
      set LDI_LIB=%LD_HOME%\server\lib
      set LDCLASSPATH=%LDI_LIB%\wlldi.jar;%LDI_LIB%\LDS-descriptions.jar;%LDI_LIB%\castor-0.9.3.9.jar;%LDI_LIB%\xercesImple.jar
      set SVRCP=%SVRCP%;%LDCLASSPATH%

    • Unix: Edit the startweblogic.sh file. Immediately before the line in which WebLogic Server gets started, add the following command lines:

      • LD_HOME=$BEA_HOME/weblogic700/liquiddata
      LDI_LIB=$LD_HOME/server/lib
      LDCLASSPATH=$LDI_LIB/wlldi.jar:$LDI_LIB/LDS-descriptions.jar:$LDI_LIB/castor-0.9.3.9.jar:$LDI_LIB/xercesImpl.jar
      SVRCP=$SVRCP:$LDCLASSPATH

  5. Copy the following files from LD_HOME/server/lib to BEA_HOME/user_projects/wli_domain_name.

    • ConfigMap.xml

    • webapp.template

  6. Use the WebLogic Integration Database Wizard (wliconfig) to switch to—and populate—the database you want to use for your deployment. For instructions, see "Using the Database Wizard" in Customizing WebLogic Integration in Starting, Stopping, and Customizing in the WebLogic Integration documentation.

  7. Start WebLogic Server and wait until it is in running mode.

  8. Start the Administration Console on the WebLogic Platform domain, logging in with administrator privileges, and configure Liquid Data security according to the following steps:

    1. In the left pane, click on wli_domain_name->Compatibility Security->Users and add a new user: ldsystem.

    2. Click on wli_domain_name->Compatibility Security->Groups and add a new group: LDAdmin.

    3. Add the ldsystem user to the LDAdmin group.

    4. Add the ldsystem user to the Administrators group.

    5. Click on wli_domain_name->Compatibility Security->ACLs and add a new ACL: LD.

    6. Add the following new permission attributes to the LD ACL: execute, read, and modify, and then add the Administrators group to the grantee list of permissions.

  9. Verify that the ACL for the weblogic.jdbc.connectionPool resource has the following permissions: admin, reserve, shrink, reset, and modify. The  grantee needs to be the Administrators group.

  10. Deploy the LDS.ear file according to the following steps:

    1. In the left pane, click on wli_domain_name->Deployments->Applications, click on Configure a New Application, click on "Upload it through your browser," select LD_HOME/server/lib/LDS.ear, and upload it.

    2. Click on the Select link next to the LDS.ear file, and then click Upload.

    3. Select the target server on which to deploy Liquid Data, and then click Configure and Deploy.

  11. Verify that the following files are deployed successfully:

    • ldconsole.war

    • ldcacheListener.war

    • cacheEjb.jar

    • ejb_query.jar

    • XMediator.war

    • ejb_qbc.jar

  12. Exit the Administration Console.

  13. Start or restart the Administration Console, logging in as ldsystem.

  14. Configure data sources, security, the repository, and other Liquid Data server settings, as needed, according to the instructions in the Liquid Data Administration Guide.

Deploying Liquid Data in a Clustered WebLogic Integration Domain

This section describes how to deploy Liquid Data in a clustered WebLogic domain. Clustering is typically used to provide scalability in deployments with high volumes of query requests and to provide fail-over protection in deployments with high availability requirements. For more information about clustered deployments, see Clustered Deployments.

Note: Before you begin, verify that your BEA software license is appropriate for your deployment.

To deploy Liquid Data in a clustered WebLogic Integration domain:

  1. Install the WebLogic Platform, which includes WebLogic Integration, on the machines that will host the Administration Server and all target Managed Servers, according to the instructions in Installing WebLogic Platform in the WebLogic Platform documentation.

    Note: Do not start up WebLogic Server until you are instructed to do so later in this section.

  2. Install the Liquid Data software on the machines that will host the Administration Server and all target Managed Servers, according to the instructions in Installing Liquid Data.

    Note: If you are using Liquid Data 1.1 or later and you are deploying Liquid Data into a new WebLogic Integration (WLI) domain, you can create the domain and configure Liquid Data at the same time using the WebLogic Domain Configuration Wizard. After using the Wizard, complete the deployment by following instructions starting with step 18.

    Check the Liquid Data Release Notes for the most up-to-date deployment instructions regarding using the Configuration Wizard.

  3. Unless you are deploying onto an existing WebLogic Integration domain, start the WebLogic Platform Configuration Wizard on the target Administration Server and create a WebLogic Integration domain (referred to in this section as wli_domain_name):

    • For the server type, select Admin Server with Clustered Managed Server(s).

    • Later in this procedure, you use the Administrative user created in this step to configure the domain.

    For instructions, see Creating a New WebLogic Domain in Using the Configuration Wizard in the WebLogic Platform documentation.

    Note: If  you want to deploy Liquid Data on an existing WebLogic Integration domain instead of creating a new one, then the existing domain must use a WebLogic Server compatibility security realm. For more information, see Using Compatibility Security in Managing WebLogic Security in the WebLogic Server documentation.

  4. Unless you are deploying onto an existing WebLogic Integration domain, start the WebLogic Platform Configuration Wizard on each Managed Server in the cluster, create a WebLogic Integration domain with same name as the one created on the Administration Server, and, for the server type, select Managed Server (with Owning Admin Server Configuration).

  5. From inside the domain in which the Administration Server was configured, use the WebLogic Integration Database Wizard (wliconfig) to switch to the database you want to use to configure the wlaiPool. For instructions, see "Using the Database Wizard" in Customizing WebLogic Integration in Starting, Stopping, and Customizing in the WebLogic Integration documentation.

    Note: If you use any database other than PointBase, then after you exit wliconfig, you need to create and load the database. Copy any applicable scripts from the respective database directory to the database server machine, and then run the scripts on the database.

  6. On the Administration Server, copy the following files from LD_HOME/server/lib to BEA_HOME/user_projects/wli_domain_name.

    • ConfigMap.xml

    • webapp.template

  7. Edit the server startup file in BEA_HOME/user_projects/wli_domain_name. You need to specify the Liquid Data home directory (ld_home_dir), such as WL_HOME\liquiddata (on Windows) or $WL_HOME/liquiddata (Unix).

    Note: If your deployment will use application views as data sources, you need to add the path to the Application Integration wlai-client.jar file (such as %WLI_HOME%\lib\wlai-client.jar) to the end of the Liquid Data classpath (LDCLASSPATH).

    • Windows: Edit the startweblogic.cmd file (on the Administration Server and startManagedWeblogic.cmd file (on Managed Servers). Immediately before the line in which WebLogic Server gets started, add the following command lines:

      • set LD_HOME=%BEA_HOME%\weblogic700\liquiddata
      set LDI_LIB=%LD_HOME%\server\lib
      set LDCLASSPATH=%LDI_LIB%\wlldi.jar;%LDI_LIB%\LDS-descriptions.jar;%LDI_LIB%\castor-0.9.3.9.jar;%LDI_LIB%\xercesImple.jar

      On the Administration Server, specify the following command:

      set SVRCP=%SVRCP%;%LDCLASSPATH%

      On any Managed Servers, specify the following command:

      set CLASSPATH=%CLASSPATH%;%LDCLASSPATH%

      In the startup script, verify that the following information about the Administration Server is correct:

      set ADMIN_URL=admin_server_name:admin_server_listening_port

    • Unix: Edit the startweblogic.sh file (on the Administration Server and startManagedWeblogic.sh file (on Managed Servers). Immediately before the line in which WebLogic Server gets started, add the following command lines:

      • LD_HOME=$BEA_HOME/weblogic700/liquiddata
      LDI_LIB=$LD_HOME/server/lib
      LDCLASSPATH=$LDI_LIB/wlldi.jar:$LDI_LIB/LDS-descriptions.jar:$LDI_LIB/castor-0.9.3.9.jar:$LDI_LIB/xercesImpl.jar

      On the Administration Server (only), specify the following command:

      SVRCP=$SVRCP:$LDCLASSPATH

      On any Managed Servers (only), specify the following command:

      CLASSPATH=$CLASSPATH:$LDCLASSPATH

      Note: The $LDCLASSPATH must follow the current CLASSPATH setting.

      In the startup script, verify that the JAVA_OPTIONS environment variable has the following entry with the correct information about the Administration Server: " -Dweblogic.management.server=admin_server_hostname:admin_server_listening_port"

  8. Start the Administration Server and wait until it is in running mode.

  9. On the Administration Server, start the Administration Console on the WebLogic Platform domain, logging in with the username/password you had created when you configured the domain, and configure Liquid Data security according to the following steps:

    1. In the left pane, click on platform_domain_name->Compatibility Security->Users add a new user: ldsystem.

    2. Click on platform_domain_name->Compatibility Security->Groups and add a new group: LDAdmin.

    3. Add the ldsystem user to the LDAdmin group.

    4. Add the ldsystem user to the Administrators group.

    5. Click on platform_domain_name->Compatibility Security->ACLs and add a new ACL: LD.

    6. Add the following new permission attributes to the LD ACL: execute, read, and modify, and then add the Administrators group to the grantee list of permissions.

  10. By default, WebLogic Server uses the round-robin algorithm as the default load balancing strategy for clustered object stubs. If you want to use weight-based or random load balancing for EJBs and RMI objects instead, complete the following steps:

    1. In the left pane of the Administration Console, select the Clusters node.

    2. Select your cluster.

    3. Click the drop-down arrow next to the Default Load Algorithm to display load balancing algorithms.

    4. In the item list, select the load balancing algorithm you want to use in the cluster.

    5. Enter the desired value in the Service Age Threshold field (see the Administration Console Online Help for more information).

    6. Click Apply to save your changes.

    For more information about load balancing algorithms, see "Load Balancing for EJBs and RMI Objects" in Load Balancing in a Cluster in Using WebLogic Server Clusters in the WebLogic Server documentation.

  11. Verify that the ACL for the weblogic.jdbc.connectionPool resource has the following permissions: admin, reserve, shrink, reset, and modify. The  grantee needs to be the Administrators group.

  12. Shut down the Administration Server, start it up again, and wait until it is in running mode.

  13. Start all Managed Servers and wait until they are all in running mode.

  14. Deploy the LDS.ear file according to the following steps:

    1. In the left pane, click on wli_domain_name->Deployments->Applications, click on Configure a New Application, click on "Upload it through your browser," select LD_HOME/server/lib/LDS.ear, and upload it.

    2. Click on the Select link next to the LDS.ear file, and then click Upload.

    3. Select the <LD_cluster_name> from the list of Available Clusters to the Target Clusters, and then click Configure and Deploy.

  15. Verify that the following files are deployed successfully:

    • ldconsole.war

    • ldcacheListener.war

    • cacheEjb.jar

    • ejb_query.jar

    • XMediator.war

    • ejb_qbc.jar

  16. In the left pane, click on wli_domain_name->Deployments->Applications->LDS->ldconsole.war, click the Deploy tab, click the Targets tab, select the Administration Server from the list of available servers, and then click Apply.

  17. Exit the Administration Console.

  18. Start or restart the Administration Console, logging in as ldsystem.

  19. In the left pane, click on the Liquid Data node, then click the General tab. The default repository directory is ldrepository in the BEA_HOME/user_projects/wli_domain_name directory.

    You need to change the repository directory path so that it points to a shared volume to which all Managed Servers have access. On Windows, for example, you would point to a shared network drive mapped to a specific drive letter (such as R:\ldrepos).

  20. On each Managed Server, you need configure the repository location by mounting (Unix NFS) or mapping (Windows) logical drives to point to the configured repository root on the Administration Server. The directory must be shared and mapped to a virtual disk name. The path must be identical to the value specified in the Repository Root Directory field on the General tab in the Liquid Data node.

    • On Unix, use NFS to mount the exported directory in the respective BEA_HOME/user_projects/wli_domain_name. Make a short cut of the mapped drive in the managed domain and name it the same as in the admin domain.

    • On Windows, map to the drive using the exact same drive letter and path (such as R:\ldrepos).

  21. Configure data sources, security, and other Liquid Data server settings, as needed, according to the instructions in the Liquid Data Administration Guide.

  22. Test the clustered deployment by verifying the operation of each machine—individually and in combination with other machines. Under a given query request load, you should see performance increase as you bring additional Managed Servers online.

 

Deploying Liquid Data in a WebLogic Server Domain

The following sections describe how to deploy Liquid Data in a WebLogic Server domain:

Deploying Liquid Data in a Standalone WebLogic Server Domain

This section describes how to deploy Liquid Data in a standalone (single server) WebLogic Server domain. For more information about single server deployments, see Single Server Deployments.

To deploy Liquid Data in a standalone WebLogic Server domain:

  1. Install the WebLogic Platform, which includes WebLogic Server, on the target server according to the instructions in Installing WebLogic Platform in the WebLogic Platform documentation.

    Note: Do not start up WebLogic Server until you are instructed to do so later in this section.

  2. Install the Liquid Data software on the target server according to the instructions in Installing Liquid Data.

    Note: If you are using Liquid Data 1.1 or later and you are deploying Liquid Data into a new WebLogic Server (WLS) domain, you can create the domain and configure Liquid Data at the same time using the WebLogic Domain Configuration Wizard. After using the Wizard, complete the deployment by following instructions starting with step 12.

    Check the Liquid Data Release Notes for the most up-to-date deployment instructions regarding using the Configuration Wizard.

  3. Unless you are deploying onto an existing WebLogic Server domain, start the WebLogic Platform Configuration Wizard on the target server and create a WebLogic Server domain (referred to in this section as wls_domain_name):

    • For the server type, select Single Server (Standalone Server).

    • Later in this procedure, you use the Administrative user created in this step to configure the domain.

    For  instructions, see Creating a New WebLogic Domain in Using the Configuration Wizard in the WebLogic Platform documentation.

    Note: If  you want to deploy Liquid Data on an existing WebLogic Server domain instead of creating a new one, then the existing domain must use a WebLogic Server compatibility security realm. For more information, see Using Compatibility Security in Managing WebLogic Security in the WebLogic Server documentation.

  4. Edit the config.xml file in BEA_HOME/user_projects/wls_domain_name and make the following changes:

    • Modify the <Security> element so that it includes all of the following attribute settings:

      • <Security CompatibilityMode="true" GuestDisabled="false" Name="wls_domain_name" Realm="myRealm" RealmSetup="true"/>

      Be sure to set CompatibilityMode to true and to specify the domain name in wls_domain_name.

    • Add the following elements and attributes:

      • <Realm FileRealm="myFileRealm" Name="myRealm"/>
      <FileRealm Name="myFileRealm"/>

      This example assumes that you are using a file realm for the compatibility security realm. For other types of security realms, see "Specifying a Security Realm" in Using Compatibility Security in Managing WebLogic Security in the WebLogic Server documentation.

    • Modify the <SSL> element and replace or add the following attributes and settings:

      • ServerCertificateFileName="democert.pem"
      ServerKeyFileName="demokey.pem" TrustedCAFileName="ca.pem"

    • Remove the following attributes from the <SSL> section:

      • ServerPrivateKeyAlias="demokey"
      ServerPrivateKeyPassPhrase="WhatEverHere"

  5. Copy the following files from LD_HOME/server/lib to BEA_HOME/user_projects/wls_domain_name.

    • ConfigMap.xml

    • webapp.template

  6. Edit the server startup file in BEA_HOME/user_projects/wls_domain_name. You need to specify the Liquid Data home directory (ld_home_dir), such as WL_HOME\liquiddata (on Windows) or $WL_HOME/liquiddata (Unix).

    Note: If your deployment will use application views as data sources, you need to add the path to the Application Integration wlai-client.jar file (such as %WLI_HOME%\lib\wlai-client.jar) to the end of the Liquid Data classpath (LDCLASSPATH).

    • Windows: Edit the startweblogic.cmd file and add the following command lines before startWLS.cmd executes:

      • set LD_HOME=ld_home_dir
      set LDI_LIB=%LD_HOME%\server\lib
      set LDCLASSPATH=%LDI_LIB%\wlldi.jar;%LDI_LIB%\LDS-descriptions.jar;%LDI_LIB%\castor-0.9.3.9.jar;%LDI_LIB%\xercesImpl.jar;
      set CLASSPATH=%CLASSPATH%;%LDCLASSPATH%

    • Unix: Edit the startweblogic.sh file and add the following command lines before startWLS.sh executes:

      • LD_HOME=ld_home_dir
      LDI_LIB=$LD_HOME/server/lib 
      LDCLASSPATH=$LDI_LIB/wlldi.jar:$LDI_LIB/LDS-descriptions.jar:$LDI_LIB/castor-0.9.3.9.jar:$LDI_LIB/xercesImpl.jar 
      CLASSPATH=$CLASSPATH:$LDCLASSPATH
      export CLASSPATH

      Note: The $LDCLASSPATH must follow the current CLASSPATH setting.

  7. Start WebLogic Server and wait until it is in running mode.

  8. Start the Administration Console on the WebLogic Server domain, logging in with the username / password you created when you configured the domain, and configure Liquid Data security according to the following steps:

    1. In the left pane, click on wls_domain_name->Compatibility Security->Users and add a new user: ldsystem.

    2. Click on wls_domain_name->Compatibility Security->Groups and add a new group: LDAdmin.

    3. Add the ldsystem user to the LDAdmin group.

    4. Add the ldsystem user to the Administrators group.

    5. Click on wls_domain_name->Compatibility Security->ACLs and add a new ACL: LD.

    6. Add the following new permission attributes to the LD ACL: execute, read, and modify, and then add the Administrators group to the grantee list of permissions.

  9. Deploy the LDS.ear file according to the following steps:

    1. In the left pane, click on wls_domain_name->Deployments->Applications, click on Configure a New Application, click on "Upload it through your browser," select LD_HOME/server/lib/LDS.ear, and upload it.

    2. Click on the Select link next to the LDS.ear file, and then click Upload.

    3. Select the server on which to deploy Liquid Data, and then click Configure and Deploy.

  10. Verify that the following files are deployed successfully:

    • ldconsole.war

    • ldcacheListener.war

    • cacheEjb.jar

    • ejb_query.jar

    • XMediator.war

    • ejb_qbc.jar

  11. Exit the Administration Console.

  12. Start or restart the Administration Console, logging in as ldsystem.

  13. Configure data sources, security, the repository, and other Liquid Data server settings, as needed, according to the instructions in the Liquid Data Administration Guide.

Deploying Liquid Data in a Clustered WebLogic Server Domain

This section describes how to deploy Liquid Data in a clustered WebLogic Server domain. Clustering is typically used to provide scalability in deployments with high volumes of query requests and to provide fail-over protection in deployments with high availability requirements. For more information about clustered deployments, see Clustered Deployments.

Note: Before you begin, verify that your BEA software license is appropriate for your deployment.

To deploy Liquid Data in a clustered WebLogic Server domain:

  1. Install the WebLogic Platform, which includes WebLogic Server, on the machines that will host the Administration Server and all target Managed Servers, according to the instructions in Installing WebLogic Platform in the WebLogic Platform documentation.

    Note: Do not start up WebLogic Server until you are instructed to do so later in this section.

  2. Install the Liquid Data software on the machines that will host the Administration Server and all target Managed Servers, according to the instructions in Installing Liquid Data.

    Note: If you are using Liquid Data 1.1 or later and you are deploying Liquid Data into a new WebLogic Server (WLS) domain, you can create the domain and configure Liquid Data at the same time using the WebLogic Domain Configuration Wizard. After using Domain Configuration Wizard, complete the deployment by following instructions starting at step 21.

    Check the Liquid Data Release Notes for the most up-to-date deployment instructions regarding using the Configuration Wizard.

  3. Unless you are deploying onto an existing WebLogic Server domain, start the WebLogic Platform Configuration Wizard on the target server and create a WebLogic Server domain (referred to in this section as wls_domain_name):

    • For the server type, select Admin Server with Clustered Managed Server(s).

    • Later in this procedure, you use the Administrative user created in this step to configure the domain.

    For instructions, see Creating a New WebLogic Domain in Using the Configuration Wizard in the WebLogic Platform documentation.

    Note: If  you want to deploy Liquid Data on an existing WebLogic Server domain instead of creating a new one, then the existing domain must use a WebLogic Server compatibility security realm. For more information, see Using Compatibility Security in Managing WebLogic Security in the WebLogic Server documentation.

  4. Unless you are deploying onto an existing WebLogic Server domain, start the WebLogic Platform Configuration Wizard on each Managed Server in the cluster, create a WebLogic Server domain with same name as the one created on the Administration Server, and, for the server type, select Managed Server (with Owning Admin Server Configuration).

  5. Edit the config.xml file in BEA_HOME/user_projects/wls_domain_name and make the following changes:

    • Modify the <Security> element so that it includes all of the following attribute settings:

      • <Security CompatibilityMode="true" GuestDisabled="false" Name="wls_domain_name" Realm="myRealm" RealmSetup="true"/>

      Be sure to set CompatibilityMode to true and to specify the domain name in wls_domain_name.

    • Add the following elements and attributes:

      • <Realm FileRealm="myFileRealm" Name="myRealm"/>
      <FileRealm Name="myFileRealm"/>

      This example assumes that you are using a file realm for the compatibility security realm. For other types of security realms, see "Specifying a Security Realm" in Using Compatibility Security in Managing WebLogic Security in the WebLogic Server documentation.

    • Modify the <SSL> element and replace or add the following attributes and settings:

      • ServerCertificateFileName="democert.pem"
      ServerKeyFileName="demokey.pem" TrustedCAFileName="ca.pem"

    • Remove the following attributes from the <SSL> section:

      • ServerPrivateKeyAlias="demokey"
      ServerPrivateKeyPassPhrase="WhatEverHere"

  6. Edit the server startup files in BEA_HOME/user_projects/wls_domain_name. You need to specify the Liquid Data home directory (ld_home_dir), such as WL_HOME\liquiddata (on Windows) or $WL_HOME/liquiddata (Unix).

    Note: If your deployment will use application views as data sources, you need to add the path to the Application Integration wlai-client.jar file (such as %WLI_HOME%\lib\wlai-client.jar) to the end of the Liquid Data classpath (LDCLASSPATH).

    • Windows: Edit the startweblogic.cmd file (on the Administration Server and startManagedWeblogic.cmd file (on Managed Servers) and add the following command lines before startWLS.cmd executes:

      • set LD_HOME=ld_home_dir
      set LD_LIB=%LD_HOME%\server\lib
      set LDCLASSPATH=%LD_LIB%\wlldi.jar;%LD_LIB%\LDS-descriptions.jar;%LD_LIB%\castor-0.9.3.9.jar;%LD_LIB%\xercesImpl.jar
      set CLASSPATH=%CLASSPATH%;%LDCLASSPATH%

    • Unix: Edit the startweblogic.sh file (on the Administration Server and startManagedWeblogic.sh file (on Managed Servers) and add the following command lines before startWLS.sh executes:

      • LD_HOME=ld_home_dir
      LDI_LIB=$LD_HOME/server/lib
      LDCLASSPATH=$LDI_LIB/wlldi.jar:$LDI_LIB/LDS-descriptions.jar:$LDI_LIB/castor-0.9.3.9.jar:$LDI_LIB/xercesImpl.jar 
      CLASSPATH=$CLASSPATH:$LDCLASSPATH
      export CLASSPATH

      Note: The $LDCLASSPATH must follow the current CLASSPATH setting.

  7. On the Administration Server, copy the following files from LD_HOME/server/lib to BEA_HOME/user_projects/platform_domain_name.

    • ConfigMap.xml

    • webapp.template

  8. On the Administration Server, copy the following files from LD_HOME/server/lib to BEA_HOME/user_projects/wls_domain_name.

    • ConfigMap.xml

    • webapp.template

  9. Start the Administration Server and wait until it is in running mode.

  10. On the Administration Server, start the Administration Console on the WebLogic domain, logging in as an administrator, and configure Liquid Data security according to the following steps:

    1. In the left pane, click on wls_domain_name->Compatibility Security->Users and add a new user: ldsystem.

    2. Click on wls_domain_name->Compatibility Security->Groups and add a new group: LDAdmin.

    3. Add the ldsystem user to the LDAdmin group.

    4. Add the ldsystem user to the Administrators group.

    5. Click on wls_domain_name->Compatibility Security->ACLs and add a new ACL: LD.

    6. Add the following new permission attributes to the LD ACL: execute, read, and modify, and then add the Administrators group to the grantee list of permissions.

  11. By default, WebLogic Server uses the round-robin algorithm as the default load balancing strategy for clustered object stubs. If you want to use weight-based or random load balancing for EJBs and RMI objects instead, complete the following steps:

    1. In the left pane of the Administration Console, select the Clusters node.

    2. Select your cluster.

    3. Click the drop-down arrow next to the Default Load Algorithm to display load balancing algorithms.

    4. In the item list, select the load balancing algorithm you want to use in the cluster.

    5. Enter the desired value in the Service Age Threshold field (see the Administration Console Online Help for more information).

    6. Click Apply to save your changes.

    For more information about load balancing algorithms, see "Load Balancing for EJBs and RMI Objects" in Load Balancing in a Cluster in Using WebLogic Server Clusters in the WebLogic Server documentation.

  12. Verify that the ACL for the weblogic.jdbc.connectionPool resource has the following permissions: admin, reserve, shrink, reset, and modify. The  grantee needs to be the Administrators group.

  13. Shut down the Administration Server, start it up again, and wait until it is in running mode.

  14. Start all Managed Servers and wait until they are all in running mode.

  15. Deploy the LDS.ear file according to the following steps:

    1. In the left pane, click on wls_domain_name->Deployments->Applications, click on Configure a New Application, click on "Upload it through your browser," select LD_HOME/server/lib/LDS.ear, and upload it.

    2. Click on the Select link next to the LDS.ear file, and then click Upload.

    3. Select the <LD_cluster_name> from the list of Available Clusters to the Target Clusters, and then click Configure and Deploy.

  16. Verify that the following files are deployed successfully:

    • ldconsole.war

    • ldcacheListener.war

    • cacheEjb.jar

    • ejb_query.jar

    • XMediator.war

    • ejb_qbc.jar

  17. In the left pane, click on wls_domain_name->Deployments->Applications->LDS->ldconsole.war, click the Targets tab, click servers, select the Administration Server from the list of available servers, and then click Apply.

  18. Click on the Cluster tab, click on the cluster to move it to the left, and then click Apply.

  19. Click on the Deploy tab, click the Undeploy button to undeploy ldconsole.war from the cluster, and then click Deploy to deploy it to the Administration Server.

    The Liquid Data node appears at the bottom of the left pane.

  20. Exit the Administration Console.

  21. Start or restart the Administration Console, logging in as ldsystem.

  22. In the left pane, click on the Liquid Data node, then click the General tab. The default repository directory is ldrepository in the BEA_HOME/user_projects/wls_domain_name directory.

    You need to change the repository directory path so that it points to a shared volume to which all Managed Servers have access. On Windows, for example, you would point to a shared network drive mapped to a specific drive letter (such as R:\ldrepos).

  23. On each Managed Server, you need configure the repository location by mounting (Unix NFS) or mapping (Windows) logical drives to point to the configured repository root on the Administration Server. The directory must be shared and mapped to a virtual disk name. The path must be identical to the value specified in the Repository Root Directory field on the General tab in the Liquid Data node.

    • On Unix, use NFS to mount the exported directory in the respective BEA_HOME/user_projects/wls_domain_name. Make a short cut of the mapped drive in the managed domain and name it the same as in the admin domain.

    • On Windows, map to the drive using the exact same drive letter and path (such as R:\ldrepos).

  24. Configure data sources, security, and other Liquid Data server settings, as needed, according to the instructions in the Liquid Data Administration Guide.

  25. Test the clustered deployment by verifying the operation of each machine—individually and in combination with other machines. Under a given query request load, you should see performance increase as you bring additional Managed Servers online.

 

Deploying Liquid Data in a WebLogic Portal Domain

The following topics describe how to deploy Liquid Data with WebLogic Portal:

For general information about managing WebLogic Portal in a production environment, see System Administration in the WebLogic Portal Administration Guide.

Deploying Liquid Data in a Standalone WebLogic Portal Domain

This section describes how to deploy Liquid Data in a standalone (single server) WebLogic Portal domain. For more information about single server deployments, see Single Server Deployments.

To deploy Liquid Data in a standalone WebLogic Portal domain:

  1. Install the WebLogic Platform, which includes WebLogic Server, on the target server according to the instructions in Installing WebLogic Platform in the WebLogic Platform documentation.

    Note: Do not start up WebLogic Server until you are instructed to do so later in this section.

  2. Install the Liquid Data software on the target server according to the instructions in Installing Liquid Data.

    Note: If you are using Liquid Data 1.1 or later and you are deploying Liquid Data into a new WebLogic Portal domain, you can create the domain and configure Liquid Data at the same time using the WebLogic Domain Configuration Wizard. After using the Wizard, complete the deployment by following instructions starting with step 12.

    Check the Liquid Data Release Notes for the most up-to-date deployment instructions regarding using the Configuration Wizard.

  3. Unless you are deploying onto an existing WebLogic Portal domain, start the WebLogic Platform Configuration Wizard on the target server and create a WebLogic Portal domain (referred to in this section as portal_domain_name):

    • For the server type, select Single Server (Standalone Server).

    • Later in this procedure, you use the Administrative user created in this step to configure the domain.

    For  instructions, see Developing Portals—Tutorials in the Development Guide in the WebLogic Portal documentation.

    Note: If  you want to deploy Liquid Data on an existing WebLogic Portal domain instead of creating a new one, then the existing domain must use a WebLogic Server compatibility security realm. For more information, see Using Compatibility Security in Managing WebLogic Security in the WebLogic Server documentation.

  4. Edit the Portal server startup file in the portal_domain_name directory. You  need to specify the Liquid Data home directory (ld_home_dir).

    Note: If your deployment will use application views as data sources, you need to add the path to the Application Integration wlai-client.jar file (such as %WLI_HOME%\lib\wlai-client.jar) to the end of the Liquid Data classpath (LDCLASSPATH).

    • Windows: Edit the startPortal.bat file and, at the end of the section in which environment variables are set, add the following commands:

      • set LD_HOME=ld_home_dir
      set LDI_LIB=%LD_HOME%\server\lib
      set LDCLASSPATH=%LDI_LIB%\wlldi.jar;%LDI_LIB%\LDS-descriptions.jar;%LDI_LIB%\castor-0.9.3.9.jar;%LDI_LIB%\xercesImpl.jar;
      set CLASSPATH=%CLASSPATH%;%LDCLASSPATH%

    • Unix: Edit the startPortal.sh file and, at the end of the section in which environment variables are set, add the following commands:

      • LD_HOME=ld_home_dir
      LDI_LIB=$LD_HOME/server/lib 
      LDCLASSPATH=$LDI_LIB/wlldi.jar:$LDI_LIB/LDS-descriptions.jar:$LDI_LIB/castor-0.9.3.9.jar:$LDI_LIB/xercesImpl.jar 
      CLASSPATH=$CLASSPATH:$LDCLASSPATH
      export CLASSPATH

      Note: The $LDCLASSPATH must follow the current CLASSPATH setting.

  5. Copy the following files from LD_HOME/server/lib to BEA_HOME/user_projects/platform_domain_name.

    • ConfigMap.xml

    • webapp.template

  6. Start WebLogic Server and WebLogic Portal.

  7. Start the Administration Console on the WebLogic Portal domain, logging in as Administrator, and configure Liquid Data security according to the following steps:

    1. In the left pane, click on portal_domain_name->Compatibility Security->Users and add a new user: ldsystem.

    2. Click on portal_domain_name->Compatibility Security->Groups and add a new group: LDAdmin.

    3. Add the ldsystem user to the LDAdmin group.

    4. Add the ldsystem user to the Administrators group.

    5. Click on portal_domain_name->Compatibility Security->ACLs and add a new ACL: LD.

    6. Add the following new permission attributes to the LD ACL: execute, read, and modify, and then add the Administrators group to the grantee list of permissions.

  8. Verify that the ACL for the weblogic.jdbc.connectionPool resource has the following permissions: admin, reserve, shrink, reset, and modify. The  grantee needs to be the Administrators group.

  9. Deploy the LDS.ear file according to the following steps:

    1. In the left pane, click on portal_domain_name->Deployments->Applications, click on Configure a New Application, click on "Upload it through your browser," select LD_HOME/server/lib/LDS.ear, and upload it.

    2. Click on the Select link next to the LDS.ear file, and then click Upload.

    3. Select the WebLogic Portal server on which to deploy Liquid Data, and then click Configure and Deploy.

  10. Verify that the following files are deployed successfully:

    • ldconsole.war

    • ldcacheListener.war

    • cacheEjb.jar

    • ejb_query.jar

    • XMediator.war

    • ejb_qbc.jar

  11. Exit the Administration Console.

  12. Start or restart the Administration Console, logging in as ldsystem.

  13. Configure data sources, security, the repository, and other Liquid Data server settings, as needed, according to the instructions in the Liquid Data Administration Guide.

Deploying Liquid Data and WebLogic Portal in Separate Domains

To deploy Liquid Data and WebLogic Portal in separate domains:

  1. Create two separate domains: the WebLogic Portal domain and the WebLogic domain in which Liquid Data runs.

    From the Liquid Data server, copy the LDS-client.jar and LDS-taglib.jar files from:

LD_HOME/server/lib

to

portal_domain/beaApps/portalApp/PortalWebApp/WEB-INF/lib

on the WebLogic Portal server.

  1. On the WebLogic Portal server, add the following code to the:

    <!-- Portal tag libraries -->

    section in:

    portal_domain/beaApps/portalApp/PortalWebApp/WEB-INF/web.xml:

<taglib>
      <taglib-uri>LDSTLD</taglib-uri>
      <taglib-location>/WEB-INF/lib/LDS-taglib.jar</taglib-location>
</taglib>

 

Deploying Liquid Data in a Standalone WebLogic Workshop Domain

This section describes how to deploy Liquid Data in a standalone (single server) WebLogic Workshop domain. For more information about single server deployments, see Single Server Deployments.

To deploy Liquid Data in a WebLogic Workshop domain:

  1. Install the WebLogic Platform, which includes WebLogic Workshop, on the target server according to the instructions in Installing WebLogic Platform in the WebLogic Platform documentation.

    Note: Do not start up WebLogic Server until you are instructed to do so later in this section.

  2. Install the Liquid Data software on the target server according to the instructions in Installing Liquid Data.

    Note: If you are using Liquid Data 1.1 or later and you are deploying Liquid Data into a new WebLogic Portal domain, you can create the domain and configure Liquid Data at the same time using the WebLogic Domain Configuration Wizard. After using the Wizard, complete the deployment by following instructions beginning with step 12.

    Check the Liquid Data Release Notes for the most up-to-date deployment instructions regarding using the Configuration Wizard.

  3. Unless you are deploying onto an existing WebLogic Workshop domain, start the WebLogic Platform Configuration Wizard on the target server and create a WebLogic Workshop domain (referred to in this section as workshop_domain_name):

    • For the server type, select Single Server (Standalone Server).

    • Later in this procedure, you use the Administrative user created in this step to configure the domain.

    For  instructions, see Creating a New WebLogic Domain in Using the Configuration Wizard in the WebLogic Platform documentation.

    Note: If  you want to deploy Liquid Data on an existing WebLogic Workshop domain instead of creating a new one, then the existing domain must use a WebLogic Server compatibility security realm. For more information, see Using Compatibility Security in Managing WebLogic Security in the WebLogic Server documentation.

  4. Edit the config.xml file in BEA_HOME/user_projects/workshop_domain_name and add the following lines inside the <domain> tag:
    <Realm FileRealm="myFileRealm" Name="myRealm"/>
    <FileRealm Name="myFileRealm"/>
    <Security CompatibilityMode="true" GuestDisabled="false" Name="<workshop_domain_name>" Realm="myRealm" RealmSetup="true"/>

  5. Edit the server startup file in BEA_HOME/user_projects/workshop_domain_name. You need to specify the Liquid Data home directory (ld_home_dir), such as WL_HOME\liquiddata (on Windows) or $WL_HOME/liquiddata (Unix).

    Note: If your deployment will use application views as data sources, you need to add the path to the Application Integration wlai-client.jar file (such as %WLI_HOME%\lib\wlai-client.jar) to the end of the Liquid Data classpath (LDCLASSPATH).

    • Windows: Edit the startweblogic.cmd file and add the following command lines before startWLS.cmd executes:

      • set LD_HOME=ld_home_dir
      set LDI_LIB=%LD_HOME%\server\lib
      set LDCLASSPATH=%LDI_LIB%\wlldi.jar;%LDI_LIB%\LDS-descriptions.jar;%LDI_LIB%\castor-0.9.3.9.jar;%LDI_LIB%\xercesImpl.jar;
      set CLASSPATH=%CLASSPATH%;%LDCLASSPATH%

    • Unix: Edit the startweblogic.sh file and add the following command lines before startWLS.sh executes:

      • LD_HOME=ld_home_dir
      LDI_LIB=$LD_HOME/server/lib 
      LDCLASSPATH=$LDI_LIB/wlldi.jar:$LDI_LIB/LDS-descriptions.jar:$LDI_LIB/castor-0.9.3.9.jar:$LDI_LIB/xercesImpl.jar 
      CLASSPATH=$CLASSPATH:$LDCLASSPATH
      export CLASSPATH

      Note: The $LDCLASSPATH must follow the current CLASSPATH setting.

  6. Make a backup copy of the fileRealm.properties file. Edit the fileRealm.properties file and add the following commands at the end of the file, specifying the domain_user_name you created when you configured the domain:
    group.Administrators=system,domain_user_name
    acl.lookup.weblogic.jndi=everyone
    acl.modify.weblogic.jndi.weblogic.fileSystem=Administrators
    acl.admin.weblogic.jdbc=Administrators, guest
    acl.lookup.weblogic.jndi.weblogic.fileSystem=Administrators
    acl.lookup.weblogic.jndi.weblogic.ejb=Administrators
    acl.list.weblogic.jndi.weblogic.rmi=Administrators
    acl.shrink.weblogic.jdbc=Administrators, guest
    acl.create.weblogic.jms.ConnectionConsumer=Administrators
    acl.lockServer.weblogic.admin=Administrators
    acl.shutdown.weblogic.admin=Administrators
    acl.boot.weblogic.server=Administrators
    acl.list.weblogic.jndi.weblogic.fileSystem=Administrators
    acl.lookup.weblogic.jndi.weblogic=Administrators
    acl.modify.weblogic.jndi.weblogic.rmi=Administrators
    acl.modify.weblogic.jndi.weblogic=Administrators
    acl.list.weblogic.jndi.weblogic=Administrators
    acl.send.weblogic.jms=Administrators
    acl.lookup.weblogic.management=Administrators
    acl.receive.weblogic.jms=Administrators
    acl.reserve.weblogic.jdbc=Administrators, guest
    acl.modify.weblogic.management=Administrators
    acl.lookup.weblogic.jndi.weblogic.rmi=Administrators
    acl.list.weblogic.jndi=Administrators
    acl.modify.weblogic.jdbc=Administrators, guest
    acl.modify.weblogic.admin.acl=Administrators
    acl.list.weblogic.jndi.weblogic.ejb=Administrators
    acl.modify.weblogic.jndi=Administrators
    acl.write.managedObject=Administrators
    acl.reset.weblogic.jdbc=Administrators, guest
    acl.read.managedObject=Administrators
    acl.admin.weblogic.jdbc.connectionPoolcreate=Administrators,
    guest acl.unlockServer.weblogic.admin=Administrators
    acl.execute.weblogic.servlet=Administrators
    acl.modify.weblogic.jndi.weblogic.ejb=Administrators

  7. Copy the following files from LD_HOME/server/lib to BEA_HOME/user_projects/platform_domain_name.

    • ConfigMap.xml

    • webapp.template

  8. Start WebLogic Server and wait until it is in running mode.

  9. Start the Administration Console on the WebLogic Workshop domain, logging in as platform/platform, and configure Liquid Data security according to the following steps:

    1. In the left pane, click on workshop_domain_name->Compatibility Security->Users and add a new user: ldsystem.

    2. Click on workshop_domain_name->Compatibility Security->Groups and add a new group: LDAdmin.

    3. Add the ldsystem user to the LDAdmin group.

    4. Add the ldsystem user to the Administrators group.

    5. Click on workshop_domain_name->Compatibility Security->ACLs and add a new ACL: LD.

    6. Add the following new permission attributes to the LD ACL: execute, read, and modify, and then add the Administrators group to the grantee list of permissions.

  10. Deploy the LDS.ear file according to the following steps:

    1. In the left pane, click on workshop_domain_name->Deployments->Applications, click on Configure a New Application, click on "Upload it through your browser," select LD_HOME/server/lib/LDS.ear, and upload it.

    2. Click on the Select link next to the LDS.ear file, and then click Upload.

    3. Select the WebLogic Workshop server on which to deploy Liquid Data, and then click Configure and Deploy.

  11. Exit the Administration Console.

  12. Start or restart the Administration Console, logging in as ldsystem.

  13. Configure data sources, security, the repository, and other Liquid Data server settings, as needed, according to the instructions in the Liquid Data Administration Guide.

 

Copying a Server Configuration to Another Server

This topic describes the steps involved in copying Liquid Data server configuration information from one server to another, such as from a development environment to a production environment. Rather than configuring the production server manually, you can transfer settings already configured in the development environment.

The following illustration shows the Liquid Data components that you need to transfer to the production server:

Figure 2-5 Migrating From a Development to a Production Server


 

To migrate from a development environment to a production environment, you need to migrate the following configuration information:

Table 2-1 Liquid Data Configuration Information to Migrate  

Problem / Symptom

Description

config.xml file

Contains the WebLogic Server configuration, including the domain configuration and, if applicable, the JDBC database configuration. Open the config.xml file on the target server and edit any machine-specific parameters.

startup script (startWebLogic.cmd or startWebLogic.sh)

Contains the Liquid Data server startup script. Open the startup script on the target server and edit any machine-specific parameters. Also, for a production environment, change the STARTMODE variable to true.

configMap.xml and webapp.template files

Copy from the WL_HOME/user_projects/domain_name directory on the source server to the corresponding directory on the target server.

security realm

Replicate the security realm configuration on the production server. The Liquid Data security configuration includes the compatibility security realm, groups, users, and ACL configurations.

How you copy the configuration depends on the type of compatibility security realm that you have set up according to the instructions in "Defining a Compatibility Security Realm" in Implementing Security in the Liquid Data Administration Guide. In general, copy the filerealm.properties file to the target machine and, if you have used any other type of compatibility security realm, use the appropriate import/export utility. For example, for an LDAP realm, use the LDAP import/export features. For more information, see "Specifying a Security Realm" in Using Compatibility Security in Managing WebLogic Security in the WebLogic Server documentation.

server repository

On the development server, create a compressed image of the complete server repository, including all sub-folders, using a TAR or ZIP file for the Unix and Windows platforms, respectively. Copy this compressed file to the production server and expand it. On the production server, start the Administration Console and configure the repository root directory on the General tab in the Liquid Data node.

Liquid Data configuration settings

On the development server, export the Liquid Data configuration information to an export file. On the production server, import the contents of the export file. For instructions, see Importing and Exporting Liquid Data Configurations in the Liquid Data Administration Guide.

 

Back to Top Previous Next