This section provides a list of tasks and a general discussion of how those
tasks might be sequenced in the application development process. The sample
application demonstrates how completion of these tasks results in a working
application. Refer to the Solution architecture document for details of the
development methodology.
Note that the Branch Transformation provides a deployable EAR file containing
all the code and resources you need to run the Java(TM) Client Sample Application. Phases 1
through 4 describe how the Java Client Sample Application was created
but you do not have to do any of the actions described in the phases to make
the sample run.
The following is a typical workflow for developing an application:
Phase 1: Analysis and design
- Gather the requirements
- Identify the business processes
- Identify the needed backend system transactions and the types of journal
entries that need to be recorded
- Create a data dictionary
- Identify the required services
- Identify the needed presentation flows
- Identify the data elements
- Identify the formatters
- Define the user interface
- Define the context hierarchies
Phase 2: Customizing the toolkit
- Code the extensions to the base runtime toolkit
- Set up the CHA Editor, and use it to create the needed CHA contexts definitions
and data elements definitions (You can also use a text editor to edit these
definitions if you do not set up the CHA Editor)
- Set up the Format Editor, and use it to create the needed format definitions
(You can also use a text editor to edit these definitions if you do not set
up the Format Editor)
Phase 3: Coding the runtime application
- Code the startup and the session-end processes
- Code the client
- Code the main presentation flows
- Code the main business logics
Phase 4: Generating the runtime files
- Generate XML files and other files required by the application in the
proper location (client, application presentation server, and application
logic server)