Technology Stack

Chakra

CHAKRA is built on Java EE technology stack and uses industry standard architectural components for seamless interoperability. CHAKRA's asynchronous message based loosely coupled modular architecture enables high throughput and flexible deployment options. CHAKRA's Adobe Flex based UI provides a rich user experience.

Solution Architecture
[ View large diagram ]
  • The infrastructure component manages all resources (database access, message queues, etc.)
  • All business components is managed by a Central Monitor, which polls component specific message queues for incoming XML messages, process them and finally write output messages in the designated output message queues of that component
  • The Message Router service will route messages across various components based on a rule base that is configurable
  • Multi-tier architecture - the back-end database ensures data integrity; the message based middleware ensures guaranteed delivery of data across modules and the browser based client ensures easy availability & manageability of the application

Technology Components

Following are the technology components upon which CHAKRA is architected:

Technology Stack Java EE and Java 2 Platform SDK
Application Server Any Java EE compatible Application Server; has been tested on the following:
  • IBM Websphere
  • Weblogic
  • JBoss
  • Apache Tomcat
Presentation Media Web Browser
Presentation Layer Framework Struts at Server Side, Adobe Flex at Client Side
Presentation Technique
  • JSP/Servlet
  • Flash
Messaging Middleware Any JMS compliant messaging system; has been tested on the following:
  • IBM Websphere MQ
  • ActiveMQ
Relational Databases Oracle 10G, MySQL, H2 (in-memory database)
Grid Infrastructure Terracotta
Domain Model POJO Based
Persistence Framework Custom DAO interfacing with JDBC
Business Rules Custom Rule Engine
Transaction Management Global Transaction managed by Custom Developed Transaction Manager
Session Management Cookie Based
System Logging File logging with Log4J
System Monitoring JMX based Admin Interface
Resource Configuration and Lookup Application Managed
Authentication Container Managed as per Java EE spec
Authorization Managed by Application Roles configured in database
Reporting Embedded Reporting Engine, XML based manual report layout configuration
Message Format XML
Message Transformation Custom Gateway and Adapter component
Message Routing Custom Message Router
Message Consumer POJO based P2P Message Consumer running as a service outside Java EE container
Service Lookup RMI Registry
Service Architecture POJO based - services developed on top of Custom Services Framework
Batch Processes POJO based – developed on top of Custom Application Launcher Framework