![]() ![]() ![]() ![]() ![]() ![]() |
Previous tutorials explained how to compile, build, and deploy parts of individual MedRec applications. In this tutorial, you compile and build the entire MedRec application suite using the project-level build.xml
file. Compiling the entire application suite is necessary to deploy all components on your system and verify that MedRec is running and usable.
Create the project directory using the instructions in Tutorial 5: Creating the MedRec Project Directory.
The project directory contains a master build.xml
script that compiles and stages all of the MedRec applications in the correct order. To run this script:
prompt> c:\bea\user_projects\domains\MedRecDomain\bin\setDomainEnv.cmd
src
subdirectory of the MedRec project directory:prompt> cd c:\medrec_tutorial\src
build.xml
script with the deploy.dev
target:prompt> ant deploy.dev
The build process displays messages indicating the progress for each application. The entire build process take approximately 2 to 5 minutes to complete, depending on the speed of your computer. The script should complete with the following message:
build:
[echo] #### E N D M E D R E C ####
BUILD SUCCESSFUL
Total time: 2 minutes 22 seconds
build.xml
file using the WebLogic Ant tasks will suffice.build.xml
file at the source level to iterate through each application's build.xml
files.
The MedRec application suite has many dependencies that require coordination during the build process. When you run the master build file, the following events occur:
startBrowserEar
and initEar
are compiled using the wlcompile
task.security
directory are compiled using the javac
task.common
are compiled. The common
directory contains the Java source code for several kinds of objects used by different MedRec applications:ServiceLocator
class. Servlets in the Web Tier of the MedRec application suite use ServiceLocator
to lookup generic services such as Enterprise JavaBeans.medrecEar
Enterprise Application is compiled. Although medrecEar
uses the split development directory structure and the WebLogic Ant tasks in the build script, the application has several internal dependencies that are hard-coded in its build.xml
script, using the include
and exclude
options to wlcompile
.physicianEar
application is compiled. The Web Service clients in this application that invoke the Web Services of both the physicianEar
and medrecEar
applications are generated from the .wsdl
files that were previously generated into the build
directory by the jwsc
Web Services Ant task.clients
directory, are compiled.
The deploy.dev
target of the master build.xml
file takes an additional step of packaging up the contents of the build
directory for each application (initEar
, medrecEar
, and so on) and creating an exploded directory for each application in the dist
directory. These exploded directories can be deployed to WebLogic Server in the standard way, outside of the split development directory framework. The next tutorials in this suite (Tutorial 14: Packaging MedRec for Distribution and Tutorial 15: Using WLST and the Administration Console to Deploy the MedRec Package for Production) go into more detail.
![]() ![]() ![]() |