|
About Orion
Below are the questions currently covered in the About Orion section of the FAQ.
Who makes the Orion Application Server?
The company is called Ironflare AB and is located in Sweden. The Orion Application Server is our only product so we are focusing more on marketing the product than the company. Contact information is available here.
What platforms can I run Orion on?
Orion runs on the Java2 platform which means any platform with a Java2 compatible Java Virtual Machine can run Orion.
Orion has been tested on the following platforms:
- Windows 95/98/NT/2000/XP
- Sparc Solaris
- Linux
- FreeBSD 4.x
- AS/400
- HP-UX (with classic vm)
Note that we can not guarantee that all configurations or jvm's will work on the above OSes, it's merely an indication on what platforms Orion has been succesfully used.
What sets Orion apart from other application servers?
Any plans to offer your source under a Linux-style license?
No, there are currently no such plans.
In fact, if we did, Sun might sue us since they see any implementation of
the J2EE specification as their intellectual property that we can not show to anyone.
What is the pricing structure if I want to use this product in a commercial environment?
The pricing structure is very simple. You pay nothing for all the development licenses you need and you pay only $1500 per host you deploy on (no matter how many CPU:s the server has).
A commercial deployment license
includes twelve months of free email bug support and free upgrades, a
license extension for $1000 gives you a second year of upgrades and support.
What's the WAP strategy for Orion?
Our WAP strategy is basically to make dynamic content being as easy to do for both web and wap clients as for just one of them. The strategy is to have JSP:s (talking to EJB:s) that produce XML documents. Then, a client-dependent XSL is used to transform the XML into either HTML or WML. All this is automated. What the developer has to do is this: Write an XML JSP (And any beans, ejbs, etc. in the system) or just an XML file (for static content) and write two XSL files (one for HTML, one for WML). Orion will automatically determine whether the user is using a normal web browser or a wap client and return the correct document. Our goal is simply to transparently bring the J2EE platform to wap clients as well as normal browsers. All this is basically available today, but it's not that easy to use. We expect it to be usable pretty soon however.
Does Cold Fusion work with Orion?
What tools for configuration, administration, development and deployment are available with Orion?
Do I need a license for a server in standby?
Only if Orion is up and running on the standby server at the same time as your regular server, i.e. hot standby.
Our sales department is ready to help with any further questions on this topic.
Copyright 2008 IronFlare AB
|