XML Server Getting Started    
Cross platform development 
XMLSP supports cross platform development and deployment. For example, you can develop an application using XMLSP 
on Windows and deploy the very same application on UNIX   or vice versa. You can even have a cross platform team of 
developers, some using Windows and some using UNIX, developing the same application at the same time. They can freely 
share XMLSP objects used in the application, because the objects are the same across the different computing platforms that 
XMLSP supports. 
Database connectivity  
XMLSP provides easy access to corporate information stored in a wide variety of databases. Data can be accessed by an 
application server objects via JDBC interface  either with or without connection pool. 
XMLSP WebApplications 
This document describes how to develop XML Server Pages (XMLSP) 
Web Application
 for J2EE compliant application 
servers. It outlines the difference between developing a regular J2EE Web Application and the one powered with XMLSP 
technology solutions.   
As a reminder, 
Web Application
 is a term defined by the 
Java Servlet Specification v2.2
 to describe the set of server side 
resources that make up the interactive interface of an online application, such as servlets, Java Server Pages, HTML pages, 
server side classes etc. The specification defines how these resources can be packaged into a portable "Web Application 
aRchive" (WAR) file so they may be deployed on an application server that supports the WAR standard. A Web Application 
operates within a Servlet Context that defines an environment that is separated from other Web Applications running on the 
same server. Each Web Application is accompanied by a deployment descriptor that ties its resources together, and describes 
how they are deployed on the Servlet2.2 compliant application server. 
XMLSP software itself is installed on the customer's Application Server as two WebApplications: 
xmlsp
 and 
Examples
.  
WebApplication 
xmlsp 
is a repository of run time files to be used by the browser   JavaScript and HTML files, images etc.   
WebApplication 
Examples 
illustrates usage of different XMLSP controls and coding techniques.  Assuming XMLSP 
software is installed on the 
localhost
 at port 80 you can start page, which integrates all examples at 
http://localhost/Examples
.  
It is recommended that you also partition your own development into J2EE WebApplication(s). For the purpose of this 
tutorial we will use pre installed  Examples  one. 
Installation options for MSXML parser on client Workstations 
The basic requirement XMLSP imposes on the client PCs is that Internet Explorer 5.5 SP2 or higher is used as a browser. 
Recommended version of the IE is 6.0 as it includes proper version of MSXML parser. For IE5.5, the XML engine is a 
separately distributed module   primarily because XML specifications were approved much after the official release of IE5.5.  
In particular, the latest release of MSXML that XMLSP has been tested with is MSXML 3.0 SP2 (You can find all available 
XML downloads at MSDNLibrary
 on line.)   
To support automatic on demand download of MSXML 3.0 SP2, XMLSP software is installed with 
msxml3.cab
 located in 
the root of Web Application named 
xmlsp 
on your Application Server (you can also 
download 
msxml3.cab
 from MSDN 
Library
)
. 
Below is the snippet of the HTML that forces the download and install of MSXML 3.0 SP2 engine during the 
parsing of the :