Development Environment
Our components are built using the following technology set
- JDK 1.8
- The Spring Framework
- Hibernate (an Object Relational Mapping tool which uses JDBC to connect to the database)
- The Apache Struts framework as our Model View Controller (MVC) GUI framework.
- Our reference implementation front-end is a browser based application which can run on Internet Explorer, Mozilla Firefox and Google Chrome. The solution is therefore not restricted to a specific front end platform but it relies on the presence of a compliant browser.
- J2EE with EJB3 support
The following components are used for LUNOS based development:
- Java IDE like Rational Software Architecture (RSA), Eclipse or IntelliJ (if development is undertaken)
- Maven 3.1.1 or later (if development is undertaken)
- J2EE compliant application server. We currently have the following in production:
- Red Hat JBoss 6.4
- IBM Websphere version 8.5
- LUNOS optionally supports Oracle WebLogic Server 12.1.3.0
- Hibernate
- Spring
- Relational Database Systems
- IBM DB2
- Microsoft SQL Server
- Oracle
- LUNOS optionally supports PostgreSQL and EnterpriseDB
- Operating Systems
- Linux (Ubuntu 14.04, CentOS v7.1)
- Unix
- AIX
- Windows
- Environments
- Locally deployed
- Cloud Based (Amazon EC2) managed by Silvermoon or by the client
Database Connectivity Framework
- Java Database Connectivity (JDBC)
Integration Mechanisms Supported
- Web Services (WSDL/SOAP)
- Java Messaging Service (JMS) (SOAP)
- MQ Based Messaging (XML)
- JMS Based Messaging (XML)
- Java Connector Architecture
- Remote Method Invocation/CORBA
Service enablement frameworks used in the application
The preferred way to expose functionality on top of LUNOS is through RESTful services. Alternatively, we can also support :
- J2EE Web Services (JAX-RPC, JAX-WS, JAXB, Apache)
- J2EE Based (Java Connector Architecture, Java Messaging Service)
- J2EE Based (Remote Method Invocation)
Middleware Platforms
Our architecture can be integrated into platforms in a variety of ways, including using SOA-based mechanisms. Silvermoon has deployed solutions connecting to the following Middleware Platforms:
- WebSphere Message Broker
- MQ Series
- JMS Based Messaging
- Java Connector Architecture
- Remote Method Invocation/CORBA
BPMS Platforms
We do not specify which BPMS platform should be used for workflow. Our solution will support any BPMS platform which uses web services to access information.
We know it will work with the following:
- WebSphere Process Server
- TIBCO iProcess (Staffware)
- BPEL Based and/or Capable Tools (SUN, BEA, BizTalk, JBoss)
- XPDL Based and/or Capable Tools
Although we haven't included "Microsoft .NET (Workflow Foundation)" in the above selection, there is no reason why our components could not participate/service SOA based interaction using this platform.
