JavaFX and JEE 7

Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 131
Java FX for Java Batch
(JSR-352) and Spring Batch
Vijay Nair
Architect (OFSSL)

The following is intended to outline our general product direction. It is intended
for information purposes only, and may not be incorporated into any contract.
It is not a commitment to deliver any material, code, or functionality, and should
not be relied upon in making purchasing decisions. The development, release,
and timing of any features or functionality described for Oracle’s products
remains at the sole discretion of Oracle.

Program Agenda
 Background/Capabilities
 Architecture
 Server Agent Component – Design and Tools
 Client Component – Design and Tools
 Short Demo

Background
 Batch Operations are among the most critical operations performed by
IT staff in a bank
 Batch Operators need an easy to use system to help them maintain
batch jobs across systems and monitor them in real time
 Pilot project utilizing Java FX and JEE 7 to help address this space

Capabilities
Visualize
 Job Meta Data (Names/Descriptions/
Thresholds/Definitions/Schedule
Expressions)
 Job Step Meta Data (Names/
Descriptions/Thresholds/Failure
Actionable)
 Job Process Flows (Hierarchies/
Dependencies/Decisions)
Configure MonitorConfigure
 New Jobs (Job Definitions/Step
Definitions/Flows and Schedules)
 Authorization of maintenance
 Job Testing
 Purging Policies (Job/Step Execution Data)

Capabilities
Monitor
 Real Time Job Status Monitoring (Running
Jobs/Failed Jobs/Threshold Time Exceeded
Jobs)
 Step Monitoring (Running Steps/Failed Steps/
Threshold Time Exceeded Steps)
 Diagnosis (Job Failure Reasons/Step
Failure Reasons/What to do ?)
 Actions (Stop/Abandon/Restart)
Configure MonitorReport
 Job/Step Execution Reports
(Historical/Current)
 Time Series Analysis (Job/Step Executions)
 Job Hierarchies

Will result in a….

Architecture – JEE 7
USER INTERFACE
VIEWS CONTROLLERS
TRANSFORMATIONSERVICE CLIENTSCONNECTORS
DATA SERVICES EXECUTION SERVICES TIMER SERVICES
ORM BATCH RUNTIME INFRASTRUCTURE
MySQL
 JavaFX 2.2.7
FXML Layouts
Controllers
 JAX-RS 2.0 (JSR-339) - RESTful Clients
 Eclipselink MOXy – JSON Provider
 EJB 3.2 (JSR-345) - RESTful/Timer
Services
 CDI 1.1 (JSR-346) - DI
 JPA 2.1 (JSR-338) - ORM/PL-SQL Support
 Java Batch 1.0 (JSR-352) - Batch
Runtime Infrastructure
 Eclipselink MOXy - JSON Provider
 MySQL – Batch Runtime Database
SERVER AGENT
DATABASE/BATCH SYSTEMSEXTERNAL SYSTEMS
RESTful JSON

Architecture - Packaging
FCBSMODEL
MySQL
SERVER AGENT
FCBSWEBAPP
FCBSCLIENTAPP
DEPENDS ON
SHIPS WITH
DEPENDSON
SHIPSWITH
ACCESSES
ACCESSES

Architecture – Spring Batch
USER INTERFACE
VIEWS CONTROLLERS
TRANSFORMATIONSERVICE CLIENTSCONNECTORS
DATA SERVICES EXECUTION SERVICES TIMER SERVICES
ORM BATCH RUNTIME INFRASTRUCTURE
MySQL
 JavaFX 2.2.7
FXML Layouts
Controllers
 Jersey Client - RESTful Clients
 Jackson – JSON Provider
 Spring MVC + WS – RESTful Services
 Spring Core - DI
 JPA 2.0 - ORM/PL-SQL Support
 Spring Batch - Batch
Runtime Infrastructure
 Jackson - JSON Provider
 MySQL – Batch Runtime Database
SERVER AGENT
DATABASE/BATCH SYSTEMSEXTERNAL SYSTEMS

Server Agent – Java Batch 1.0 (JSR-352)
 JEE 7 standard for Batch Jobs
 Runtime for Batch Operations including start/stop/abandoning and
monitoring of the same
Why Java Batch ?
How have we used Java Batch ?
 Configure Jobs across systems
 Spawn Jobs
 Monitor Jobs

CHECKPOINTDATA
EXECUTIONINSTANCEDATA
JOBINSTANCEDATA
JOBSTATUS
STEPEXECUTIONINSTANCEDATA
STEPSTATUS
PROVIDED TABLES
JOBMETADATA
 Name
 Description
 Definition
 Threshold
 ScheduleExpression
STEPMETADATA
 Name
 Description
 Threshold
 StepFailureAction
EXTENSIONS
JOBPARAMETERSMETADATA
 Parametername
 Parametervalue
EXECINSTANCEFAILREASON
 ExecId
 ExecDate
 FailureReason
 Status

Application Job Process Flow
Job Flow
Decision
Flow
Decision
Steps
Steps
Steps
Batchlets
Batchlets
Job Listeners
Step Listeners
Step Listeners
Exit
System A
System B

Server Agent – EJB 3.2 / JAX-RS 2.0
RESTful Services
 RESTful Services exposed as Stateless EJBs
 Eclipselink MOXy as the JSON Provider
Timer Services
 Timer Services exposed as Stateless EJBs

Server Agent – CDI 1.1
Dependency Injection
 JEE Resource Injection
 Batchlets configured as “Named” resources
 Batchlets loaded via “Named” references

Server Agent – JPA 2.1
ORM
 JPA 2.1 Models
 PL/SQL support

User Interface – Why JavaFX ?
 Productivity
– Rapid Application Development using Tooling (Netbeans and
SceneBuilder)
– Testing and…
– We are coding only in Java
Why JavaFX ?

 Capability
– Layouts built using WYSIWYG
– Control Set (Basic and Advanced)
– Eventing (e.g. Value Change Listeners, Thread State Listeners)
– CSS styling
Why JavaFX ?

 Monitoring using VisualVM
 Stability and Acceptance
– Extremely Performant
– Class of users are familiar with Desktop Applications
Why JavaFX ?

User Interface – Views
FXML
VIEWS
 Screen Building using Scene Builder
which generates FXML
– Layout Containers
– Place Controls
– Associate Events
– Style
 Map to a Controller Class
FXML
Generates
Controller
Associate

User Interface – Controllers
 Java Class which has
– Controls injected using “@FXML”
– “Service” threads to load data
– Event listeners to populate data
or respond to other events
Controller Implementation

User Interface – Client Services
 Controllers use JAX-RS 2.0 clients to load data with Eclipselink
MOXy as the JSON Provider
JAX-RS 2.0 (JSR-339) Client API

Graphic Section Divider

JavaFX and JEE 7

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie JavaFX and JEE 7

Ähnlich wie JavaFX and JEE 7 (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

JavaFX and JEE 7