Prev Chapter 7 Build, Webapp and Deployment Next

Chapter 7 Build, Webapp and Deployment

This chapter provides you with information about the

of XMA-Webapplications.

Due to the special requirements of an XMA-Client some additinal elements are necessary on top of a standard Wep Application Archive. That will be described in the chapter XMA Webapplication (XMA Webapplication) .

A detailed description about application descriptors required by the xma-client can be found inApplication and Plugin Descriptors (Application and Plugin Descriptors) . This section will introduce you into application and plugin descriptors.

There are also some available Standard-Plugins. A Documentation about these Plugins can be found here: Standard Plugins (XMA Plugins).

7.1 Build

This is the simplified designd of an XMA-Build. In principle the XMA Build is split into 3 parts.

Build Overview

Figure 7.1. Build Overview


  1. Compile is the evant where .java files changed into .class files. In an XMA Application the Compile Section works a little more.

  2. Pack is a Section in which different Components and Files where pack in a server-side application.war file

  3. Deploy can be optional. You can deploy and a war file in different ways on different servers.

More details about the Targets and how to start building an application, you will find here. (Build Process)

Compile

Figure 7.2. Compile


  1. These Targets are the pre-stage to become a correct and clean compile. All Variables and external properties fiels are prepared.

  2. INPUT: All .java files from the source directory

  3. OUTPUT: The compiled .class files are copied into the class directory

Pack

Figure 7.3. Pack


  1. There are two different Common_jar files: First the CommonClient.jar and second the CommonServer.jar

  2. For each Component you add to your application, this target will call the target "jar"

  3. The WebApp Target has to calling "make_hash_for_jar" even the you want to sign a file.

  4. Two files: ComponentServer.jar and ComponentClient.jar with a Hashcode. Now they can be pack into the application.war file.

  5. Now the file will have a Hashcode.

  6. At this time the externalPlug-Ins (XMA Plugins) where delivered.

The Common_Jar target is very importent for you. If you are using a database or any .gif and so on, you have to edit this target in the build.xml file.

common jars

Figure 7.4. common jars


This means that you have to pack the data directory within all files into the CommonServer.jar

This means that all .gif, .jpeg, and so on have to placed in a specified folder which is set in the CommonClient.jar The Component-jars Target is fully auto generated. Every time you create a new Component (Getting started with the GUIDesigner), one such block will be created.

component jars

Figure 7.5. component jars


The WebApp Target

create a new directory named "build_war" and copied your application template (=the folder who has the same name like your application).Then different files where copied into this build_war directory:

  1. all server component-jar files

  2. all required runtime libraries for the server

  3. all client components into the components directory, which is used to download from clients

  4. all runtime libaries required by the client

After this can be set a antcall to the "make_hash_for_jar"-Target for file who have currently no Hash.Finalize webapplication by building thexma-application descriptor (Application and Plugin Descriptors) . the descriptor will be checked and all hash values are included for each required component Last but not least we need to include a plugin vendor, which is delivered as a WAR-File. And then rebuild the new xma webapplication.

For detailed informations about the Web Application take a look here. (XMA Webapplication)

Deploy

Figure 7.6. Deploy


  1. The Input only can be a application.war file

  2. This only can be used while Tomcat Server is still running and the application was already deployed.We are using the Tomcat Manager to be able to provide this.

  3. If Tomcat isn´t running use this targets.

  4. This Target copied the war file in the specified Weblogic folder which deploy the file while running.

  5. The fastest procedure to become a running application. This will Compile, Pack and Deploy the application on a running Tomcat Server

The "Little Helpers" are realy self-explanatory.

Prev   Next
6.18 Appendix B: XMA BootRuntime Properties Home 7.2 XMA Webapplication