About Zephyr Portal:

The Zephyr Portal is a J2EE application that can be hosted on any standard J2EE Application Server of client’s choice as our portal is an Application Server agnostic. Portal supports almost all databases – all major (Oracle, MS SQL Server, MySQL, etc.) including InterSystem’s Cache`, Firebird, etc. Currently, we have tested portal on Tomcat and JBoss with MySQL as the database on Windows 2003 Server.

Zephyr portal can be deployed with any standard web farm to scale any large volume of concurrent requests. No additional code changes will be required.

Requirements to Host Zephyr Portal

Zephyr recommends the following hardware to setup each instance/node in a web farm depending upon the scaling requirements. Alternatively, Cloud or blades, etc. are options for hosting on a big scale.

Hardware:

A server machine (whether Windows or Linux or Unix) with

1. At least 2 CPU
2. At least 4 GB RAM
3. At least 2 GHz processor
4. Network enabled/ready
5. At least 120 GB disk space to accommodate database back-ups and eventually, depending up on the scaling requirements, we may need more displace to keep backups

Software:

1. JDK 1.6.x
2. Tomcat or JBoss or any Servlet container at minimum, but can be hosted on any J2EE application server – Zephyr portal is J2EE container agnostic.
3. MySQL 5.x or higher version
4. Axis 2.x or any web service container
5. Purchase a SSL certificate from any CA (Certificate Authority) depending up on local/Country federal/government regulations, enable SSL.
6. Optionally, Apache 2.x Web Server to facilitate SSL and simple load balancer to scale. Depending upon the scalability, we recommend the hardware based load balancer and avoid Apache later.
7. A few open source software/shareware that will be provided by Zephyr as an installable package

Note: Optionally, Zephyr can provide Apollo (or any client) a single package that will setup everything from J2EE container to database.

Client Workstations:

A standard Web Browser is required to access Zephyr portal. Zephyr has currently tested on Microsoft’s IE, Google’s Chrome and Firefox. Zephyr web pages require Adobe Flash player. Each end user needs to install Flash player on his/her workstation to view portal pages/content properly. Alternatively users can view limited information like a plain vanilla grid view rather than a nice Gauge based views.

Zephyr API and Interfaces:

Zephyr provides web services and HL7 interfacing to support any Enterprise Application Integration requirements. For example, exchanging vital sign data between an EHR (Electronic Health Record) and hosted portal that facilitates remote monitoring based on Bio Harness and other sensor device generated data. Another example is to exchange vital signs between portal and Google Health or MS HealthVault.

Zephyr Portal facilitates a direct HTTP requests to save/update or retrieve vital signs from/to portal database.

Zephyr supports Android application to remote data viewing. Customizations are possible for clients’ needs.