| Page Menu |
|
|
| Monthly Newsletter |
|
|
|
Marketing |
|
|
|
|
|
|
|
| |
|
| NeuroKernel
is a cross platform, cross browser client/server computing
platform. It can run any kind of server/client
ecosystem. Here you will find the supported and required
client/server configurations |
|
|
|
|
|
|
NeuroKernel Client Side :
| Operating
System |
Any Operating System
with a Supported Browser |
| Browsers Supported |
Internet Explorer 5.0+, Firefox 1.5+, Seamonkey
1.0.1+, Safari 3.0+ and Netscape 9.0+. NeuroKernel automatically upgrades old
MSXML for Internet Explorer 5.0 and 5.5 if not already upgraded. |
Java
Plug-in
(Client Kernel Only) |
- Sun JRE 1.3+ (1.5+ recommended) and Microsoft Virtual Machine
for Internet Explorer. If you want to support Microsoft Virtual
Machine with your programs, you must compile your applications
with Java 1.1 compatibility.
- JRE 1.5+ with full live-connect support for Firefox, Seamonkey
and Netscape browsers.
- Latest available JRE is required for Safari/Webkit.
|
NeuroKernel Server Side :
| Operating
System |
Any Operating System with a Java
Runtime Environment. |
| Servlet Engine: |
Any J2EE compliant Servlet Engine
(Servlet Specification 2.2+). NeuroKernel may not work in Cross
context mode. In addition, servlet engine must have an the internal http server
up and running. If you have a scalable
edition, your servlet engine must be able to extract war files
directly into the webapps directory and should support hot context
addition. |
| JDK
Supported |
Default support is for JDK 1.5+, but
NeuroKernel can run with JDK 1.4+. |
| Database |
An RDBMS database engine with JDBC 3.0
and Unicode support. The NeuroKernel Installer will set up and install
an HSQL database server if requested automatically. Tested with
PostgreSQL, MySQL, Oracle, SQLServer, SAP MaxDB, FireBird and HSQLDB.
NeuroKernel can work from all databases because of its standards based
SQL schema. |
| File
System |
For all editions running from a single
server, local file system is sufficient. However, for scalable
editions running with multiple servers, a Network File System is
required for user accounts. |
| Load
Balancer |
For scalable editions running with
multiple servers, a load balancer is required. Some servlet engines
offer load balancing modules as well. However, for maximum performance
and large deployments, a Load Balancer hardware will be the best
option. If you have a single server, no load balancer is needed. |
|
|