3.3. intra-mart System ArchitectureΒΆ

System architecture of intra-mart Accel Platform is shown below.

../../_images/iap_architecture.png
LoadBalancer
It is an equipment to transfer connection request from client to Web server, and performs load balancing etc.
Use of Load Balancer with the following functions is recommended on intra-mart.
* Session maintenance function by Cookie
* Health check function based on HTTP response contents
* Capability to add redundancy to the Load Balancer itself
Web Server
Accel Platform supports Apache WebServer and IIS.
In case Resin is used, it utilizes the module called Web Server Connector that is integrated into Web server.
It functions as an interface between Web server and Accel Platform by sending the client request from
Web server to Accel Platform on Resin, or receiving the execution result from Accel Platform and passing it
to Web server. In case multiple Accel Platforms are set as the connection destination of
Web Server Connector, automatic process allocation will be possible by the round-robin function.
WebApplicationServer
It is a server to run intra-mart Accel Platform, and it supports Resin included in intra-mart Accel Platform
as standard, Oracle Weblogic Server, and IBM Websphere Application Server.
intra-mart Accel Platform is placed (deployed) as WAR (Web archive) file
on this Web application server.
intra-mart Accel Platform
This is the product we offer, which is placed (deployed) as WAR (Web Archive) file generated by
IM-Juggling, and works on Web application server.

Note

What is WAR file?

It is a Web Application Archive file which is defined in JavaEE and
various types of files necessary for the operations of intra-mart Accel Platform are included.
WAR files for intra-mart Accel Platform are created by IM-Juggling.
Various types of files necessary for the operations of intra-mart Accel Platform are stored and
by placing (deploying) WAR files created by IM-Juggling in Web Application Server
such as Resin, and running Web Application Server,
intra-mart Accel Platform itself and various applications for intra-mart Accel Platform
that are stored in the WAR file are started and can be used.

Since WAR file would be the minimum unit of intra-mart Accel Platform product itself,
number of intra-mart Accel Platform licenses are counted by the number of WAR files.
RDB
It is used as a save location for various master data or transaction data of
intra-mart Accel Platform. intra-mart Accel Platform supports Oracle, SQLServer, DB2, and
PostgresSQL as RDB products at connection destination.
Storage
It is used as a save location of attachment files or electronic files for various document
used on intra-mart Accel Platform. By the setting of intra-mart Accel Platform, you can specify
any storage location. However, if you are operating multiple Web/AP servers, it is
necessary to provide a Storage Server such as NFS or CIFS, which allows the operations of
the same disk area on every Web/AP server.
Apache Cassandra
It is an open source NoSQL server provided by ApacheFoundation. It is needed separately if
IMBox is in use. (If IMBox is not used, there is no need to install Apache Cassandra server.)
While Cassandra itself provides the redundancy mechanism, operations with 3 or more Cassandra units are
recommended from Cassandra/IMBox specifications viewpoint, if you need redundancy and data consistency.
Apache Solr
It is an open source search engine provided by ApacheFoundation and used by IM-ContentsSearch.
Since Apacphe Solr is also a Web application server like intra-mart, Web application server such as
Resin or Jetty must be provided for the operations environment of Apache Solr.
(In case IM-ContentsSearch is not used, there is no need to install Solr server.)

Note

Cloud functions are greatly enhanced in [Resin4]

[Resin Ver.4] which has major enhancement of Cloud functions is integrated into intra-mart Accel Platform.
Web sites that are built upon Resin can not only cope with the periodic request increases such as the seasonal changes, but can also handle explosive occurrences of large-volume requests at a certain time in a flexible manner.
Resin Ver.4 adopts the cluster with the [Triad] architecure, and hence 3 Resin servers (2 Resin servers are allowed too) work as a set, and achieve high availability with the mutual fail-over among them. It is also possible to handle drastic changes of requests by dynamically increasing/decreasing the number of Resin servers at the cluster with this mechanism. Triad can be also applied to Resin servers on the Cloud.
Operation status of Resin servers is being monitored by the agent (Watchdog) that performs periodic monitoring. In case of any failure the report is automatically generated, which can be used for the cause investigation, recovery, and prevention of future occurrences.