Stable Business Operation
- Automatic expansion of system resources/predictive monitoring (Enterprise Edition only)
System resources, such as memory, that are running are tuned according to the load and expanded automatically.Additionally, the consumption of system resources is monitored/warnings are output. The system resources can be tuned according to the warning to ensure that application errors because of insufficient resources are avoided.
- HotStandby (Enterprise Edition only)
A function that enables HotStandby in the Web server and application server is provided. Even if trouble occurs in the server (current) running the application, the application can be started on a standby server automatically so that the business can be taken on (failover).
- Distribution of requests from HTTP server to backend, and fault monitoring. (Supported by Standard-J Edition, Enterprise Edition and the functions of Web Package included in Enterprise Edition)
The function which distributes requests from HTTP server to backend is provided. Operation can be continued by separating the breakdown server when a distribution server breaks down.
- Smart Tuning
Smart Tuning monitors applications for warning signs of Full GC, while autonomously controlling input flow to completely eliminate poor responsiveness due to the impact of Full GC. Because the product stabilizes the responsiveness of applications on its own, there is no need, as in the past, for coding complex response stabilization processes into applications and for meticulous memory tuning.
- Warning-sign monitoring: By monitoring the memory utilization history and GC status of Java VMs, this feature autonomously determines and detects signs of Full GC and signs associated with slow responsiveness and other problems.
- Input flow control: While monitoring for warning signs and suppressing requests to the affected processes, this feature guarantees that applications are responsive by running them in separate Java VMs. After a Full GC process is complete, the Java VM can accept requests again. This prevents other Java applications and non-Java applications from being affected.
- Session Recovery (Enterprise Edition only)
Servlet session information is saved on another server called the session registry server. The Servlet session information is then carried over to another web container so business operations can continue if the web container process or machine crashes.
- Concurrent GC (Enterprise Edition only)
Fujitsu's GC(*) stabilizes response depending on the nature of applications. Fujitsu's concurrent GC eliminates poor responsiveness due to the impact of Full GC.
(*)GC (Garbage Collection) is a technology which releases unused memory from an area of memory that programs can actively reserve.
- Operation management control in business units (WorkUnit)
A mechanism that makes it possible to operate multiple applications as 1 business (WorkUnit) is provided. Effective utilization of resources and error recovery is performed in each WorkUnit automatically.
- Automatic recovery of business
Application errors (abnormal end, loop, deadlock) are detected promptly, so business is recovered automatically by the restart of the application, for example. Business requests can also be received during recovery, so stops and delays in business are avoided. The application recovery processing settings can be changed as the WorkUnit service level.
- Resource pooling
Obtain server resources, such as processes and threads, in advance so that they can be re-used in the WorkUnit.Server resources can be utilized to the maximum effect, so CPU and memory can be used optimally.
- Application HotDeploy (activation change)
Applications can be added/switched without affecting business operation. even when an application is corrected or an interface modified, business can be switched dynamically without stopping it, so flexible support for cost reduction associated with system modification and environment change is possible.
Note: Addition/switch of Web, EJB, and CORBA applications is possible. For details about the operating target Edition, refer to the list of functions.
- Diagnostic log function and automatic data collection in batch
If an application error (abnormal end, loop, deadlock) occurs, it is possible to refer to an error message or diagnostic log from the Interstage Management Console. Additionally, data required for trouble investigations can be collected in batch automatically.
- Application multi loop control (multi container)
Multiple execution of an application is controlled, so stable response is guaranteed, even for vast numbers of requests. Together with the prevention of performance deterioration because of access concentration, for example, CPU performance can be used effectively, and scalable structures can also be supported.Additionally, if business runs on multiple containers, even if trouble occurs in an identified container business operation can continue, so the effect of the trouble can be controlled so that is kept to the minimum.
- Distributed transaction function (Standard-J Edition/Enterprise Edition)
- If an application accesses multiple databases, synchronous update is guaranteed so that conflicts do not occur in the update data.
- Even if an application accesses multiple databases located on different systems, synchronous update is guaranteed so that conflicts do not occur in the update data.
- Interstage Application Server performs recovery processing when there is an error.