Architecture

SeaLiner is a Java EE web application server. It offers rich container shipping functionalities with multi-tiers, (layering architecture) components-based application implementation. SeaLiner modules are designed to be integrated, but have the principle in mind to support web service implementation and are able to leverage on an SOA environment.

SeaLiner adopts and enforces usage of open standards in IT software application development. It increases the application’s portability to various platforms and software components. For instance, JPA (Java Persistence API) is an open standard for Object Relation (OR) mapping frameworks and is implemented in SeaLiner. It is easy to switch from one OR mapping tool to the other without, or with very minimal, code changes. In addition, taking advantage of the layering architecture, changes to one layer do not affect other layers.

SeaLiner is designed to be scalable either vertically or horizontally. This is important as the system that can readily accommodate the additional users and provide good and optimal performance due to the customer business growth without much more investment.

Deployment Architecture

SeaLiner application servers could run on any Java EE compliance application server, in particular on Oracle WebLogic and IBM WebSphere. The deployment architecture above is able to support the high transaction volume that we expect to see in a top 20 shipping company. The number of servers can easily be reduced or scaled to smaller hardware capacities, for lower volume customers, as SeaLiner is designed on layering and component based architecture. E.g. SeaCruise, SeaMon and SAS can run on the same JVM without any code change by just having the components setting configured to support more functionalities according to the requirement and hardware specification. SeaLiner Application Server (SAS) SAS is the core component of the SeaLiner Enterprise application providing a complete interactive solution for all the data processing required by a Shipping Line. Information Broker Server (IBS) Modern distributed architectures require a secure, reliable way to exchange messages in asynchronous, loosely-coupled systems. The Apache ActiveMQ message broker is a complete open source implementation of the JMS specification. The ActiveMQ Message- Oriented Middleware, coupled with its Enterprise Integration Provider are the building blocks of an Enterprise Service Bus - the backbone of a contemporary Service Oriented Architecture. Customers could utilize their own message queue or middleware software, such as ESB product from Tibco, IBM, Oracle, JBoss, Sun or any others as long as it supports JMS specification.

SeaMon is the server that provides a “health” check for SeaLiner application servers. It could be used as middleman for mapping SeaLiner messages to the customers’ enterprise centralized message controlling and monitoring tool, for instance to SNMP agent.

SeaCruise is used for asynchronous / synchronous real-time transactions and scheduled jobs. It also serves as a notification server and offloads heavy processing for SAS. This is developed based on the TSI Cruiser framework and TSI Angkasa Transport component.

Database Server (DBS) The SeaLiner database architecture model is designed based on Oracle11g architecture and can support clustering environment, RAC.