BriteSoft™ - Platforms and Technology

RELATED LINKS / DOCUMENTS

BriteMobility Overview

BriteMobility Sample Screens

Summary Fact Sheet

Codeless development comparison

Productivity comparison

Brite Applications - out of the box

BriteWorks and the Software Crisis

BriteWorks Studio	Built-in Features	Platforms & Technology
Extensibility	Business Benefits	Huge Productivity Gains
Business Objects Exchange

Platforms & Technology

Environments & Platforms
- Since BriteWorks™ is java based, it can run under any platform that supports JVM (Java Virtual Machine).
- JDBC is used to access databases, however, since it does not support all functions, BriteSoft™ has created its own database handlers that complement JDBC.
- The following databases and environments have been tested:
  1. Desktop: Windows, Unix, Linux, MAC
  2. Client / Server Application Server - BriteWorks™' own Application Server
  3. Web/App Server: Tomcat, JBOSS, Websphere, OC4
  4. Web: IE, Firefox, Netscape, Opera, Safari
  5. Mobile: J2ME, Windows, Symbian
  6. Database: MySQL, SQL Server, Oracle, DB2, Informix, HSQL, Derby
Methodology / Architecture
- With BriteWorks™, any methodology can be used for development.
- Rapid, Iterative, Production Prototyping is ideally suited to BriteWorks™ development as creating applications is so fast that it may not make sense to go through all the traditions development life cycle steps.
- BriteWorks™ methodology can be considered as a hybrid between Information Engineering and Spiral Development.
- The following are architectural aspects which form the basis of BriteWorks™:
  1. MDA - Model Driven Architecture.
  2. SOA - Service Oriented Architecture
  3. Repository Based Development
Technology
- Studio and Desktop (Client Server) Implementations.
  1. Studio is normally run under Windows (XP, 2000, Vista, etc.) as well as Mac and any other environment that supports JRE.
  2. Desktop Runner version has the same properties as the Designer and will run on any machine that supports JRE.
  3. Server runs on Windows, Linux, Unix, Solaris, AIS etc. - any environment that supports JVM.
  4. These modules are written or run under Java, JDBC, JRE, J2SE, J2EE.
  5. Relatively thin client, in that updates to the server / application do not require client updates.
  6. Remote installation can run in the same way as a local intranet environment. All that is needed is an IP address and a port.
  7. Local caching ensures that speed is maintained and there are options to compress data transfer to/from the server.
- Web Implementations
  1. The same designed application that runs on the client/server immediately run on the web
  2. JSF and AJAX allows for Web 2.0. Rich Internet Applications (RIA)
  3. Web applications look and behave in the same manner as client/server
  4. Zero install deployment - no installation is required on client machines.
  5. Reduces bandwidth requirement, reduces pressure on the server, utilizes the distributed power of the desktop.
- Mobile Implementations
  1. The same client/server and web application can immediately run on mobile devices
  2. Applications can run online connect to a server through local network
  3. Applications can run through IP/port
  4. Applications can run in offline mode, without any connection to a server.
  5. Supported environments are any that support Java Midlets
  6. Works under Windows, Symbian, J2ME
- No code is ever written or generated. A single design in the studio works under all the above environments.