This chapter describes how to deploy AquaLogic Data Services Platform applications to an Administration Server, Managed Server, or to a cluster. The chapter also describes how to deploy AquaLogic Data Services Platform applications from development to production mode.
The chapter contains the following sections:
During development, you can deploy applications to a WebLogic Server directly from Workshop (or from other IDEs such as Eclipse with a WebLogic plug-in). Following development, however, applications are more typically deployed to production WebLogic Servers using the Administration Console.
In most production scenarios, there are multiple WebLogic instances in a given domain. Using the Administration Console, you can deploy applications to an Administration Server, a Managed WebLogic Server, or to a cluster.
Note: | You can deploy a AquaLogic Data Services Platform application to only a single target, which can be either a server or a cluster. |
The Administration Console further enables you to upgrade applications or shut down application modules on a WebLogic Server without interrupting other running applications. For general information about deploying applications, see Deploying WebLogic Platform Applications at:
http://download.oracle.com/docs/cd/E13196_01/platform/docs81/deploy/index.html
AquaLogic Data Services Platform-enabled applications can only run in a domain that has been provisioned for AquaLogic Data Services Platform. For information on such provisioning see Provisioning an Existing Domain for AquaLogic Data Services Platform.
The WebLogic Configuration Wizard automatically transfers the required items to the target server. These include the AquaLogic Data Services Platform project artifacts, including configuration files and binary files, as well as WebLogic components such as data source connections and pools.
You need to make sure, however, that any data sources configured in the development environment are available from the production environment.
Table 3-1 lists the contents of a compiled AquaLogic Data Services Platform project.
An Administration Server is the central configuration repository for the set of WebLogic Servers in a domain. Once the AquaLogic Data Services Platform application is deployed to the Administration Server, you can deploy it to all of the managed servers in the domain.
To deploy an application to WebLogic using the Administration Console:
For more information, see Using the WebLogic Server Console.
Figure 3-1 illustrates the Application node context-sensitive menu.
The deployment status of the application appears. Also, the application appears in the list of Applications in the Navigation pane. From there you can manage the application and deploy it to other servers in the domain.
You can deploy applications to Managed Servers in the WebLogic domain using the Administration Console.
To deployed applications to a Managed Server:
For more information, see Using the WebLogic Server Console.
The Administration Console displays the AquaLogic Data Services Platform Deploy tab.
The console shows the status of the redeploy action, and displays Success for each module when the redeploy operation has completed.
A cluster is multiple WebLogic Server instances running simultaneously and working together to provide increased scalability and reliability. A cluster appears to clients to be a single WebLogic Server instance.
To deploy a AquaLogic Data Services Platform application to a cluster:
For more information, see Using the WebLogic Server Console.
Figure 3-3 illustrates the screen for selecting an application to deploy to a cluster.
The console displays the available clusters, as illustrated in Figure 3-4.
AquaLogic Data Services Platform applications are typically developed and tested in development mode, which offers a relaxed security configuration and enables auto-deployment of applications. Once the application is available in its final form, you can deploy the application to production mode which offers full security and may use clusters or other advanced features.
This section describes the following methods for migrating AquaLogic Data Services Platform applications from development to production mode:
You can migrate AquaLogic Data Services Platform applications from development to production mode by creating a configuration template using the WebLogic Configuration Template Builder, and then choosing the template when creating a new domain using the WebLogic Configuration Wizard.
This section highlights steps specific to migrating AquaLogic Data Services Platform applications. For complete information about using the Configuration Template Builder and Configuration Wizard, see the following:
To migrate AquaLogic Data Services Platform applications using configuration templates:
liquiddata
folder to the <Domain Root Directory>
of the Current Template View, and click Next.Maintain the JDBC connection pool names unchanged.
By default, the Configuration Template Builder stores the new template in the <BEA_HOME>/user_templates
directory on the development server.
You can manually deploy AquaLogic Data Services Platform applications from development to production mode, if required.
To manually deploy an application from development to production mode:
liquiddata
folder which contains <
app_name
>LDconfig.xml
file from the development domain to the production domain.
The EAR file resides in the applications
folder of the domain.
config.xml
file of the production domain, and add application elements which belong to the AquaLogic Data Services Platform application and AquaLogic Data Services Platform Administration Console (ldconsole).
You can cut and paste this information from the config.xml
file in the development domain.
Export the security policies for the WebLogic Authorization provider, and import the policies into the new security realm. For more information about migrating WebLogic Security data, see the WebLogic documentation at:
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/secmanage/security_data_migration.html
Export the AquaLogic Data Services Platform security policies in the development domain and import them into the production domain. For more information about exporting AquaLogic Data Services Platform security policies, see Exporting Access Control Resources.
ldcontrol.properties
file from development to the production domain.Each domain that runs AquaLogic Data Services Platform Control applications has a single ldcontrol.properties file, which stores the connection information for all AquaLogic Data Services Platform Control applications running in the domain.
The ldcontrol.properties
file is located at the root directory of your domain where the application EAR file is deployed that uses a Data Service control. There is an entry in the ldcontrol.properties file for each control you have created in each of your applications.
The entries in the ldcontrol.properties
file are of the following form:
AppName.ProjectName.FolderName.jcxName=t3\://hostname\:port
Table 3-2 provides additional details.
Note: | The colons (: ) in the URL must be escaped with a backslash (\ ) character. |
If the URL value is missing, the AquaLogic Data Services Platform Control uses the connection information from the domain config.xml
file.
The following is a sample ldcontrol.properties
file.
#Fri Oct 31 15:30:36 PST 2003
myTest.myTestWeb.myFolder.Untitled=t3\:myLDServer\:7001
myTest.myTestWeb.myFolder.myControl=
SampleApp.LiquidDataSampleApp.Controls.RTLControl=t3\:myLDServer\:7001
SampleApp.Untitled.NewFolder.Untitled=t3\:yourLDServer\:7001
testnew.Untitled.NewFolder.ldc=
test.testWeb.NewFolder.Untitled=
You can determine which version of AquaLogic Data Services Platform you are through the WebLogic Administration Console.
To determine the version number (which appears associated with the name Liquid Data):
For more information, see Using the WebLogic Server Console.