Appliance Benefits

1. Inexpensive Powerful Hardware.
2. Open Source Software
3. Standard Protocol: http
4. Standard Way To Describe Data: xml
5. Improved Browser Technlologies

Open Source software has benefited the appliance model in he same manner. Many appliance-based solutions contain open source software, greatly reducing the cost of supporting software like the operating system and database. These two factors have made the appliance model very cost effective for both the developer and end-user.

The first two points make appliances economical the following make them highly functional. Together http and xml-based technologies represent a powerful open standards that allows an appliance to interface with desperate systems. Other protocols may be implemented but these two standards carry a heavy load.

Most Appliance Based Solutions, XAP included, rely on the Web Browser for delivering user interfaces. Specialized client development is no longer required and browser interface technologies have matured to a point where highly functional browser interfaces are now possible. Improved Browser technologies , XML, and http make this all possible

Less Conflicts
In order for any piece of software to effectively service the needs of its users there must NOT exist any conflicts between the software, hardware and other installed software. The appliance model of software delivery minimizes the possibility of any of these conflicts arising. XAP Server Appliances come pre-installed and configured resulting in less down time, less support calls, and an over all better user experience, increasing usability and productivity.

Traditional software only methods of distribution are ridden with conflict issues. Multiple installed applications consuming the same hardware resources each with its own set of prerequisites which also may be in conflict. The ASP model does manage these conflicts however this is accomplished by a one size fits all mentality. Customers consuming an ASP based application are using the same version of the software, the same features, and the same hardware configuration. XAP server Appliances offers the same conflict management without these rigid constraints. Customer needs vary(see below) and XAP Server Appliances are designed to allow for different flavors of the same application to be offered thus better servicing the needs of the Enterprise

Better Change Management
Software is similar to an organism. It must grow and adapt to its surroundings. As the surroundings change the organism must change or it will die. The same can be said of software if it does not change as its surroundings change it will become obsolete.

The most influencing aspect of software's surroundings is the user. In fact software exist for the sole purpose of serving the needs of the user. User needs are not static they are dynamic, constantly changing. In order to effectively meet these needs software must be changing with them.

In the traditional software distribution model these changes are introduced with upgrades, patches and new version releases. This is a very cumbersome and ineffective way to mange change. It is disruptive, error prone, and not timely. Users needs can change in an instant therefore the software must also be able to meet these needs in a timely manner.

With the XAP Server Appliance changes to the software are made without end user intervention. They are not disruptive and small incremental more timely improvements may be applied more in line with the demands of Enterprise.

What about the ASP model? Actually a XAP Server Appliance may be distributed as a ASP(hosted) application. Where the XAP Server Appliance is housed is a logistical matter. Enterprise may deploy a XAP Server Appliance within their corporate firewall or allow access to it from the Internet or both. In one case it's an internally distributed application in the other case it looks like an ASP. However The XAP architecture allows features to be introduced in more granular Enterprise by Enterprise bases unlike a traditionally ASP model(SEE BELOW)

Allows for Customization
XAP Applications may be customized per deployed appliance. In a pure ASP model the service is consumed and very little customization if any is offered to the end user. The reason is that customization will cause the application to be forked and multiple versions will need to be maintained. This is a costly endeavor and maintenance and support will become a major obstacle.

All XAP Applications are extensible in that each deployed XAP Server Appliance may contain "extensible code" that represent Enterprise specific logic.

For example lets say a Human Resource solution is developed in XAP. Several XAP Server Appliances are distributed to different Enterprises. Each XAP Server Appliance receives updates from the XAP Application Updates and Maintenance Service and the XAP Software Maintenance Service. Each XAP Server Appliance may also contain extensible code, which was customized to meet the specific needs of the Enterprise. The update services maintain the core XAP Application and the XAP Appliance Software while the extensible code remains unaltered.

Quality and Quantity
The ASP model is ideal for delivering web applications to a large user base with minimal customization. XAP can be used to effectively offer solutions in this manner. An excellent strategy for an ISV is to offer the base XAP solution as an ASP and when customization is requested the same XAP Application may be delivered as a XAP Server Appliance.

Both offerings are actually XAP Server Appliances. The ASP version offers the XAP application with minimal customization on a XAP hardware configuration designed to handle heavy usages. The Service Provider sill benefits from XAP managed services to update, maintain and enhance the XAP Application and XAP Appliance Software. The XAP "customized" Server Appliance is delivered in a less robust hardware configuration but tailored to meet the specific needs of the Enterprise. All XAP Server Appliances come with the Integrated Development and Hosting Environment allowing for the customizations to be maintained remotely on the deployed XAP Server Appliance.

XAP allows an ISV to offer a high volume, "Quantity" based strategy as well as a lower volume, "Quality" based strategy.

Easier Data Integration
Most business applications are data centric. They gather, manipulate and display data. Often integration with legacy data whether as input or output to a legacy system is required. Traditional software only solutions hardwire this integration which is costly, time intensive, and error prone. The ASP model may offer data integration interfaces but by their nature are remote applications thus security and responsiveness often is an issue. With the appliance model the XAP Server Appliance may be housed in the approximately of the legacy system behind the corporate firewall alleviating all security issues and greatly increasing responsiveness.

More Secure and Easier to Secure
In the software only model all security is the responsibility of the Enterprise. Enterprises maintaining there own hardware infrastructure or Network Service Providers must proceed very cautiously when a new software installation or integration is deployed. With each new piece of software comes a new set of security vulnerabilities. Often the Enterprise does not completely understand the intricacies of the new software thus do not completely understand the security breaches it may introduce. The same is true for the company, which is providing security services. They have an understanding of the network and possibly existing services running on the maintained hardware but every new piece of code installed and every update and change to existing installed software possibly may introduces new vulnerabilities. It is very difficult for the Enterprise or Service Provider to effectively maintain a secure environment when the environment (the installed software) is constantly changing.

The ASP method of software delivery does offer a better security model over traditional methods. In the ASP model a wide range of users, spanning enterprises and in many cases spanning the globe are consuming the same services. All users are accessing the same network, the same software, and the same hardware infrastructure. This makes intrusion detection or secretary breaches more difficult to detect since the make up of users is diverse and in the event of a security breach data across all Enterprises is compromised.

In the appliance model Enterprises need only be concerned with their network. The XAP Server Appliance represents a device on the network easily distinguished from other network devices and easily secured from a network perspective. Changes and enhancements to the XAP Server Appliance do not introduce new vulnerabilities to other networked services.

This leaves securing the XAP Server Appliance. Unlike the ASP model the populations of users on the XAP Server Appliance is limited. Often users will only access the appliance from inside the corporate firewall and often the user base is small enough were access can be restricted by IP address or other user base demographics. Unusual activity on the appliance is thus easier to detect and proactive measures are easier to implement. Secure environments can be maintained in the ASP model however the XAP architecture makes it easier to secure small pockets of users accessing XAP Server Appliances deployed across Enterprises.

All XAP Server Appliances come with an integrated, configurable firewall. Also as part of the XAP Managed Services security notices are patched immediately. Xornet subscribes to security "watch dog" services. With in minutes of a discovered vulnerability updates are made to the Xornet Application Server an applied to all deployed XAP Server Appliances.

Truly Plug and Play
The XAP Server Appliance does truly offer plug and play deployment. There is no software to install, just plug it into your network, a minimal browser based configuration set up, and your XAP Application is up and running.