Chapter 3. Planning a Branch Transformation Toolkit migration 75
– The application presentation tier, providing a bridge between the client
and the application logic tier, and managing the views of the Java client
sample application
– The application logic tier, conducting business transactions.
– The back-end system tier, storing the business data.
HTML sample application
This sample demonstrates the important steps in developing an online home
banking application using the features of the Branch Transformation Toolkit
that support HTML clients. This sample can be used as a guideline for
solution providers who wish to gain a better understanding of the toolkit
facilities.
The target environment for the HTML sample is a four-tier architecture: client,
application presentation layer, application logic layer, and backend system
layer. In this case, the client is the Web browser used to access the home
banking application. This sample does not show the details of communication
between the server and the host because this is not its main purpose.
The application comprises the following:
– Client user interface components (JSP files)
– Business navigation processes (toolkit Struts extension externalized XML
files)
– Invoker definition (resource bundle file)
– Business logic components (Java code in Single Action EJB and business
process component)
3.2 Application packaging and topology
As part of building a Branch Transformation Toolkit solution, you should consider
application packaging and managing runtime topologies.
3.2.1 Application packaging
An important deployment issue is to determine a policy for packaging the
application code and resources. This policy determines how to distribute the
code and resources on different servers. A solution based on Branch
Transformation Toolkit may use Java Archive (JAR) files that provide physical
packaging for a set of files. The JAR files have the following advantages:
– Reduced interactions with the server during the download process.
– Improved transmission performance because of object compression.
– Optimized memory usage in the browser cache.