Deployment Guide
You can easily deploy Liquid Data into new or existing domain using the WebLogic Configuration Wizard. On Windows you can access the WebLogic Configuration Wizard from the Start menu:
Start —> BEA WebLogic Platform 8.1 —> Configuration Wizard
Alternatively, you can access the WebLogic Configuration Wizard directly.
When deploying a Liquid Data-enabled domain through the WebLogic Configuration Wizard, deployment of Liquid Data components is automated. This includes distributing contents of the LDS.ear
file to the appropriate server. (In a multi-module deployment the ldconsole.jar
should only be deployed on the Administration Server; all other modules should only deployed on Managed Servers. See Deployable Liquid Data Components for details.)
When you start the WebLogic Configuration Wizard, you are first asked whether you want to create a new WebLogic platform domain or extend an existing domain. If you choose to import into an existing domain, you will be able to navigate to the domain you wish to extend and set deployment configurations appropriately.
This chapter describes tasks involved in deploying BEA Liquid Data for WebLogic. In addition to deploying Liquid Data to new and existing domains, some special cases are described in detail. The following sections are included:
When Liquid Data is installed, it adds several configuration templates to the WebLogic Configuration Wizard.
Figure 3-1 Liquid Data Options in WebLogic Platform Configuration Wizard
The Domain Configuration Wizard supports creation of the following Liquid Data-enabled domains:
When creating a new, Liquid Data-enabled domain, you have a choice between Express and Custom configuration. As the name implies, Express auto-selects most options to allow you to create a Liquid Data-enabled domain very quickly.
If you choose the Custom option, the WebLogic Configuration Wizard guides you through a series of dialog boxes that allow you to set or select:
After using the WebLogic Configuration Wizard, follow these steps to complete the deployment process:
ldrepository
directory. ldrepository
directory structure in the Liquid Data node of the WebLogic Administration Console (Configuration —> General —> Repository Directory) to a specific location and then copy the ldrepository
directory and its contents to the same exact location on each managed server. /opt/prod/bea_81/user_domains/ld_domain/ldrepository
/opt/prod/bea_81/user_domains/ld_domain/ldrepository
ldrepository
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
).In both cases you set the Liquid Data repository path using the Liquid Data node of the WebLogic Administration Console as follows:
BEAHOME/user_projects/domains/workshop/ldrepository
On each Managed Server, you need to 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 ldrepository
root directory field on the General tab in the Liquid Data node.
R:\ldrepos
).For detailed information on using the WebLogic Configuration Wizard as well as deployment concepts see Overview of WebLogic Platform Configuration in Configuring WebLogic Platform. Also see WebLogic Configuration Wizard on-line help.
You can also use the WebLogic Configuration Wizard to import a Liquid Data configuration template into an existing WebLogic Platform domain.
Note: You cannot use the WebLogic Configuration Wizard to extend a clustered domain for Liquid Data + Samples.
Figure 3-2 Dialog Box Used to Extend an Existing Domain Configuration to Support Liquid Data
After you have extended a domain, the domain's startWebLogic.cmd
script needs some minor editing. If you are extending a domain that includes WebLogic Workshop data from two versions of a workshop.properties file may need to be merged. Details are provided in Required Changes to Server Files.
Here are the general steps required to extend an existing WebLogic Server domain:
workshop
, see Figure 3-3) you wish to extend. Then click Next.Figure 3-3 Selecting a Domain in the WebLogic Configuration Wizard
When extending a domain, you can accept default settings or customize the domain. Customization includes:
ldconsole.jar
is only deployed on the Administration Server; all other modules are deployed on Managed Servers. See Deployable Liquid Data Components for details.)For detailed information on using the WebLogic Configuration Wizard as well as deployment concepts see Overview of WebLogic Platform Configuration in Configuring WebLogic Platform. See also WebLogic Configuration Wizard on-line Help.
Configure or reconfigure data sources, security, the repository, and other Liquid Data server settings, as needed, through WebLogic Administration Console, as described in the Liquid Data Administration Guide.
The following table shows Liquid Data-enabled deployment options and identifies scripts that need to be changed for the particular option.
Figure 3-4 Command Files Requiring Editing When Extending a Domain for Liquid Data or Liquid Data + WebLogic Application Integration (WLAI)
For example, if you have an existing WebLogic Workshop 8.1 domain and want to import a Liquid Data template, you would:
ldrepository
directory. ldrepository
directory structure in the Liquid Data node of the WebLogic Administration Console (Configuration —> General —> Repository Directory) to a specific location and then copy the ldrepository
directory and its contents to the same exact location on each managed server. /opt/prod/bea_81/user_domains/ld_domain/ldrepository
/opt/prod/bea_81/user_domains/ld_domain/ldrepository
ldrepository
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
).In both cases you set the Liquid Data repository path using the Liquid Data node of the WebLogic Administration Console as follows:
BEAHOME/user_projects/domains/workshop/ldrepository
On each Managed Server, you need to 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 ldrepository
root directory field on the General tab in the Liquid Data node.
R:\ldrepos
).WebLogic Platform Servers are started by command scripts. These scripts have either cmd
(Windows) or sh
(UNIX) extensions. You need to make some minor editing changes to these scripts when deploying Liquid Data into an existing domain.
startWebLogic
scriptsstartManagedWebLogic
scriptsChanges required to server command scripts are described in the following sections:
Note: Command files are located in the root directory of the your extended domain and contain the following "readme" file:
LiquidData.ld-extension-changes.readme
Note: Generated command files may vary somewhat from examples shown.
This section describes changes needed in Windows or UNIX command script files to support domains extended to support Liquid Data but not WebLogic Application Integration.
Edit startWebLogic.cmd
, using these steps:
@rem Call WebLogic Server
set CLASSPATH=%WEBLOGIC_CLASSPATH%;%POINTBASE_CLASSPATH%;%JAVA_HOME%\jre\lib\rt.jar;%WL_HOME%\server\lib\webservices.jar;%CLASSPATH%;%LDCOMMONCP%
Changes to UNIX Start WebLogic Scripts
Edit the startWebLogic.sh
file.
LD_HOME=$WL_HOME/<LD_HOME>
.$LD_HOME%/setEnv.sh
where <LD_HOME> is the root Liquid Data directory.
WL_HOME=/bea/weblogic81
LD_HOME=$WL_HOME/liquiddata
. "$LD_HOME/setEnv.sh"
CLASSPATH=$CLASSPATH:$LDCOMMONCP
# Start WebLogic server
CLASSPATH="${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${POINTBASE_CLASSPATH}${CLASSPATHSEP}${JAVA_HOME}/jre/lib/rt.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${CLASSPATH}"
export CLASSPATH
CLASSPATH=$CLASSPATH;$LDCOMMONCP
# supports Liquid Data extension
"$JAVA_HOME/bin/java" ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS}
After the Liquid Data extension is imported into a domain, it will add a file called workshop.properties
into the domain. If a workshop.properties
file existed before the Liquid Data extension was imported, the old file will be automatically backed up by the WebLogic Configuration Wizard to the filename workshop.properties.bak
If you find such a file in the root directory of the server you are extending, you need to merge that file with the new workshop.properties
file. The order of the files being merged does not matter.
If you use the Domain Configuration Wizard to create a Liquid Data production domain, or if you have a domain that does not contain the boot.properties
file at the root level, you must modify the startup script to specify the name of an administrative user (a user who is a member of the WebLogic Administrators
group). If the domain does not have the administrative username set, an error will occur on server startup.
The startup script for Liquid Data domains created with the Domain Configuration Wizard contains the following code fragment:
if "%WLS_PRODUCTION_MODE%"=="true" (
set JAVA_OPTIONS=%JAVA_OPTIONS% -Dcom.bea.ld.adminusername=
)
Note: In order for the startup script to correctly run, an administrator's user name must be supplied.
Perform the following steps to update the startup scripts for production domains or domains that do not have a boot.properties
file:
JAVA_OPTIONS="%JAVA_OPTIONS% -Dcom.bea.ld.adminusername=system_admin"
JAVA_OPTIONS="%JAVA_OPTIONS% -Dcom.bea.ld.adminusername=system_admin"
There are two ways to copy a Liquid Data server configuration information from one server to another, such as from a development environment to a production environment.
For more information see Creating Configuration Templates Using the Weblogic Configuration Template Builder.
The following illustration shows the Liquid Data components that you need to transfer to the production server:
Figure 3-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:
Contains the WebLogic Server configuration, including the domain configuration and, if applicable, the JDBC database configuration. Open the |
|
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 |
|
Copy these files from |
|
Replicate the security realm configuration on the production server. The Liquid Data security configuration includes groups, users, and roles. 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. (Not necessary if the target server already has Liquid Data enabled.) |
|
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 WebLogic Administration Console and configure the repository root directory to be the directory where the source repository was unzipped to. |
|
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. |
|
If there are any "live" applications in the development server such as an . |
If you create a clustered Liquid Data domain or extend an existing clustered domain to support Liquid Data and you want to be able to remotely start your managed server(s) from the WebLogic Administration Console, you will need to insert instructions copied from the Administration Server's executed startWebLogic script to each Managed Server's configuration instructions.
You can use the following steps to accomplish this for each Managed Server in your cluster:
<user_domain>/<domain>/startWebLogic.cmd
where user_domain>/<domain> is the root directory of your WebLogic domain (for example,
d:\user_domains\mydomain
).
As you are copying sections of the executed script you may find it easiest to create a text file containing the output of the startWebLogic process. On Windows you can create such a file using:
startWebLogic >> scriptoutput.txt
See Overview of Node Manager at http://download.oracle.com/docs/cd/E13222_01/wls/docs81/adminguide/nodemgr.html for additional information.
If you create a Liquid Data domain and want to run it as a Windows Service, you must modify the startup script for the Window Service to include needed Liquid Data resources in the classpath.
If you have created your domain in the WebLogic Configuration Wizard and selected the Run as a Service option, then a file named installService.cmd
will be in your domain directory. You will need to edit that file.
Alternatively you can create a script which invokes the Windows service command file located in <WL_HOME>/server/bin
directory. If that is how your will start your Windows service then you will need to edit the installSvc.cmd
file located in that directory.
The editing instructions for installSvc.cmd
or installService.cmd
are the same.
<user_domain>/<domain>/installSvc.cmd
where user_domain>/<domain> is the root directory of your WebLogic domain (for example, d:\user_domains\mydomain
).
<WL_HOME>/server/bin/installService.cmd
set CLASSPATH=%WEBLOGIC_CLASSPATH%;%CLASSPATH%
call "%WL_HOME%\liquiddata\setenv.cmd
set CLASSPATH=%WEBLOGIC_CLASSPATH%;%CLASSPATH%;%LDCOMMONCP%
if "%PRODUCTION_MODE%"=="true" (
set JAVA_OPTIONS=%JAVA_OPTIONS% -Dcom.bea.ld.adminusername=
)
JAVA_OPTIONS="%JAVA_OPTIONS% -Dcom.bea.ld.adminusername=system_admin"
JAVA_OPTIONS="%JAVA_OPTIONS% -Dcom.bea.ld.adminusername=system_admin"