Posted date
Updated date
Nablarch System Development Guide
Table of contents
- Preface
- Purpose of this document
- Who should read this document?
- Notes on reading
- Overall picture
- Project plan
- Requirements definition phase
- Requirement definition
- Architecture design
- Checking the project deliverables
- Test plan
- Creating a development guide for a project
- Design phase
- Standardization
- Programming and Unit testing phase
- Initial build of Nablarch project
- Setting up the team development environment
- Preparation of setup guide for development environment
- Establishment of development standards
- Integration test phase
- Preparation for integration test (communication confirmation)
- System test phase
- Maintenance operation
- Nablarch Pattern Collection
- Commonly used patterns in Nablarch
- Nablarch anti-pattern
- Nablarch Batch Processing Pattern
- Classification by startup method
- Classification by input/output
- Important points
- Asynchronous Operation in Nablarch
- To sending emails
- Nablarch Anti-pattern
- Web application
- Nablarch batch
- JSR352 batch
- Customization of UI Standards
- UI standard (screen)
- UI standard (screen) separate volume_UI parts catalog
- Examination of Test Items
- Collecting test viewpoints
- Extraction of test viewpoint
- Nablarch Environment Construction
- Generating projects from archetypes
- Component settings
- Introduction of static analysis tool
- Java Style Guide
- Setting Up the Team Development Environment
- Preparation of Setup Guide for Development Environment
- xxx Project development environment construction guide
- Prerequisites
- Development environment construction procedure
- Package Configuration Study
- Concept of package configuration
- Example of division by business function
- Example of division by class role
Asynchronous Operation in Nablarch
In web applications of Nablarch, asynchronous operation can be achieved by combining “Messaging Using Tables as Queues”.
For example, assume that a web application is taking too long to process a single request.
In this case, asynchronous operation can be realized by using the “Messaging Using Tables as Queues” as follows.
- Web application accepts the request, registers data necessary for subsequent processing in DB, and returns the response
- “Messaging Using Tables as Queues” detects data registration to DB and processes the data
To sending emails
The sending emails functionality provided by Nablarch is based on Resident batch.
Both “Resident batch” and “Messaging Using Tables as Queues” can monitor data registration to the DB and execute batch processing.
However, “Resident batch” has a problem that when running in multi-threaded mode, monitoring of the next data registration does not start until all threads running in parallel finish.
Therefore, it is recommended that new projects use “Messaging Using Tables as Queues” rather than “Resident batch”.
However, the sending emails is not supposed to be used for sending so many messages that multi-threading is required in the first place.
Therefore, when using the sending emails, there is no problem using “Resident batch” instead of “Messaging Using Tables as Queues”.