Outline

• FINALUNA
• FINALUNA API
• Framework (Reference Implementation of API)
• Related Solution of NTTDATA
• Support Platform
• Announcement

FINALUNA

FINALUNA is NTTDATA's solution which we extended our own Open System Development Solution (TERASOLUNA) for the financial system and created based on the financial system needs.

FINALUNA API

What's FINALUNA API?

Purpose of API

FINALUNA API is java interface for use in business logic for the purpose of separating framework which realizes a processing mode and non-functioning requirements from business logic which realizes functional requirements as an independent component.
Each component can be developed separately by ridding the dependency between components. Specifically, business logic can be maintained for a long time period independently from upgrading of HW/MW products, crossovering to other rival brands or changing framework or processing mode etc.

Outline of API

• FINALUNA API defines only the function required for business logic so that homogeneous and independent business logic can be described from non-functional requirements.
• Although function addition will be performed in FINALUNA API, function modification will be not performed in the future.
• FINALUNA API is created from only java interface class as much as possible so that restrictions may not be given to framework implementation. Moreover FINALUNA-API is created by JavaSE that has very few specification changes.

Main Function (Interface) of FINALUNA API

• Type (FINALUNA type)：Original data type which FINALUNA defines *By implementing business logic with the FINALUNA type which defined very minimum type for implementing business logic, the long-term maintenance and standardization for business logic are possible.
• Logic (Business Logic)：Interface which implement business logic
  • Business logic that is created using FINALUNA API only is recyclable as a component which is independent from execution environment (H/W, M/W and Processing mode).
• DTO (Data Transfer Object)：Interface which define system traffic message
  • Physical message format is concealed from business logic.
• DAO (Data Access Object)：Interface for business logic to access resource
  • The definitions (DB connection, transaction control, file access, etc.) depending on the physical resource which influences non-functioning requirements or the definitions (SQL statements etc.) depending on products is concealed from business logic.
• Context：Interface which conceals execution environment
  • Context is factory which acquires FINALUNA API conformable object by which implementation was concealed within business logic.

Implement classes defined for each execution environment are generated.

• FinalunaApplException,FinalunaSysException：Exception which business logic controls
  • Processing of exception or error depending on execution environment such as framework is left to framework, and it conceals from business logic.

Detail of API

○Needs

• Long-term AP Maintenance
  • By changing of Java technology, application lifetime be thought as limiting for around five years.
    • ⇒Five years or more of continuation of application assets is needed.
    • ⇒Minimization of AP revision workload after system upgraded is needed.

• Standardization of AP Development
  • Necessity of supporting to develop large-scale system associated with open sourcing from mainframe from now.(Number of Msteps, Over 100 human resources)
    • ⇒Standardization of AP development is needed.
• Business Logic deevelopment Independent of Processing mode
  • Necessity of supporting to develop large-scale system with more than one processing patterns.
    • ⇒Productivity and maintainability are improved with commonalization and componentization by sharing the business logic of a different processing mode

• Test case Maintenance
  • Necessity for long-term test case maintenance
    • ⇒Test case modification is carried out only when business logic is modified by specification change etc.

○Implementation Method

• Portion depending on changing Java technology is concealed by framework, and taken off from business logic. Possible to use continuously without modifying business logic by renewing framework when Java technology is upgraded.

• By applying framework, developer creates business logic only. Moreover, business logic is described with API (FINALUNA API) which framework offers, so business logic standardization can be realized.

• By absorbing processing difference that come from difference of processing mode by framework, influence on a business layer (business logic) is minimized. Possible to realize sharing of the business logic in more than one processing modes and improve productivity and maintainability by this.

• Source code that depend on change of Java technology is cut off from describing test case code by using FINALUNA API, test API (FINALUNA API Ex) and driver for UT. Thereby, test case modification is occured only when business logic is updated.

○Configration Outline Chart of FINALUNA API

Explanation about each API is shown below.

○FINALUNA Type
Possbile to describe business logic that is standardized more by using FINALUNA type within business logic. FINALUNA type can be added by extending base of FINALUNA type or existing FINALUNA type for each project.

○Message I/O
Input data and output data of business logic and framework are performed via DTO. Framework have a role to execute data extraction from resource (file or database) as input source or data insertion to output target. For this reason, developer can concentrate on business logic development without thinking of input-and-output resource.
DTO holds information including conversion rule between java standard type of API, and FINALUNA type etc.
(※) While business developer needs to set up this rule, in FINALUNA java is adopted for formula although java and XML can be considered for setting it.
Reason is that readability of Java is higher than XML and that it is thought that development efficiency of java improves by supporting compile-checking by IDE (Integrated Development Environment).

○DB, File I/O, Shared Valiable
At business logic when accessing to external resources like a file, database and shared variable, DAO which FINALUNA provides is used. By using DAO, even if developers do not know access method for external data, they can access data for reference, updating, etc. Moreover, mentioned previously , DTO is used for the interface between business logic and DAO. Accessing to shared variable is only allowed for referrence action.

○Business Logic
Only pure business logic which took out generalized processing is described using FINALUNA API. Thereby, business logic with high maintainability can be created more efficiently. Moreover, by the reason that interface of business logic is common to online, messaging and batch, business logic can be shared between these processings.

○Exception Handling
Many exception handling classes are prepared as usage in standard java API. Although it is very useful to specify exception which occured, when the differences are occured at exceptions handling expression by each developer, it involve the risk of becoming impossible to maintain unity as the project. Therefore, FINALUNA minimize these issues by specifying the exception throwed within business logic. Also, the exception which is occurred by system operator is specfied from the message activated at the time of exception throw.Thrown exception is extendable from exceptions for application, and can also be added for every project.

API Download

Java Docs, Java Source Files, Documents of FINALUNA API are downloadable from Download

• FINALUNA API Java Doc (Japanese)
• FINALUNA API Java Source
• FINALUNA API Detail Design Document (Japanese)

Framework (Reference Implementation of API)

What's FINALUNA Framework

FINALUNA Framework released at this site is reference implementation of java interface(FINALUNA API) for business logic. Currently our framework has many proven applied system development records in NTTDATA's financial systems.(ex.running with 5 or more MStep java source code at Apr., 2010)

Related Solution of NTTDATA

In NTTDATA, know-how based on actual performance of abundant financial system developments is adjusted/improved as "FINALUNA recommended architectonics" corresponded to technical reference model.
As shown in figure, for the purpose of the increase in efficiency of financial open-system development, FINALUNA utilizes NTTDATA's own solution and promotes componentize of know-how by following four category table.

FINALUNA Scheme Product Line Up

• FINALUNA API：disclosure
• FINALUNA framework：non-disclosure
  • TERASOLUNA®
  • http://TERASOLUNA.jp/
• Scale-out architectonics / System consolidation：non-disclosure
  • PRORIZE^™
  • PORTOMICS^®
  • Prossione^®
• Appliance Products
  • Websphere
  • ORACLE
  • JP1
  • InterstageListCreator
  • SVF
• Document Guidelines：non-disclosure
  • Development processes

Support Platform

Status of supported application server lineup and operation compatibility

• IBM PureSystems
  　
  　　https://www.ibm.com/software/brandcatalog/puresystems/centre/details?uid=GSD_48981
  
  • Supported Solution
    　　IBM PureApplication
    　　IBM PureFlex
    
  • Contact point of Implementation Service
    　　NTTDATA INTELLILINK Corp.
    
    

• • IBM WebSphere Application Server
    
  • Contact point of Implementation Service
    　　NTTDATA INTELLILINK Corp.
    　　※They also carries on WebSphere OEM licences and supports. (OEM products supplied from IBM)
    
    

• • Fujitsu Interstage Application Server
    
  • Contact point of Implementation Service
    　　Fujitus・Fujitusu middleware
    
    

• • Hitachi uCosminexus Application Server
    
  • Contact point of Implementation Service
    　　Hitachi
    
    

• • tomcat
    
  • Contact point of Implementation Service
    　　None

Announcement

Followings are historical press release information.

• News Release
  
  • Feb 2nd, 2011 / FINALUNA rock-solid framework released
    NTTDATA released java solution for enterprise financial systems
    - High reliability for social infrastructure level is realized by java -
    http://www.nttdata.com/jp/ja/news/release/2011/020200.html (Japanese)
    http://www.nttdata.com/global/en/news-center/global/2011/020200.html (English)
    
  • Apr. 16th, 2010 / FINALUNA open-source released
    NTTDATA opened NTTDATA's financial system development know-how
    - Establish to make FINALUNA open-source -
    http://www.nttdata.co.jp/release/2010/041600.html (Japanese)
    
  • July 13th, 2009 / FINALUNA rock-solid framework
    NTT DATA newly developed java solution for enterprise financial systems.
    - SOA base middleware using the IBM's Cloud technology was adopted for FINALUNA -
    http://www.nttdata.com/jp/ja/news/release/2009/071300.html (Japanese)
    http://www.nttdata.com/global/en/news-center/global/2009/071300.html (English)
    
  • Dec. 14th, 2005 / Hitachi's JP1® was adopted for FINALUNA <<NTTDATA-Hitachi joint press release>>
    NTT DATA enhance function for financial system development solution
    - NTTDATA signed the agreement to resale partner contract of Hitachi's integrated system operation management software "JP1" -
    http://www.nttdata.com/jp/ja/news/release/2005/121400.html (Japanese)
    http://www.hitachi.co.jp/New/cnews/month/2005/12/1214.html (Japanese)
    
  • Dec. 14th, 2004 / Fujitsu's Interstage® was adopted for FINALUNA <<NTTDATA-Fujitsu joint press release>>
    NTT DATA enhance function for financial system development solution
    - Fujitsu agreed to make OEM middleware supply to NTTDATA, and collaborate with NTTDATA in reporting solution -
    http://www.nttdata.com/jp/ja/news/release/2004/121401.html (Japanese)
    http://pr.fujitsu.com/jp/news/2004/12/14.html (Japanese)
    
  • Jun. 15th, 2004 / IBM WebSphere® was adopted for FINALUNA <<NTTDATA-IBM joint press release>>
    NTTDATA released financial system development solution
    - IBM agreed to make OEM software supply to NTTDATA -
    http://www.nttdata.com/jp/ja/news/release/2004/061500.html (Japanese)
    http://www.ibm.com/jp/press/2004/06152.html (Japanese)
    
    

• Record of Awards