Difference between revisions of "Create Web Application"

From PresenceWiki
Jump to: navigation, search
 
(Web Application Limitations)
Line 12: Line 12:
 
The WAR file container is similar to a standard JAR File in that it is simply a zip file format containing a compressed version of multiple Java class files, however, additionally it also includes a /WEB-INF folder that includes a web.xml file to define the structure of the web application.  In the case of a Presence Web Application, the web.xml file defines how the servlet engine calls the Presence tasks contained in the Web Application.
 
The WAR file container is similar to a standard JAR File in that it is simply a zip file format containing a compressed version of multiple Java class files, however, additionally it also includes a /WEB-INF folder that includes a web.xml file to define the structure of the web application.  In the case of a Presence Web Application, the web.xml file defines how the servlet engine calls the Presence tasks contained in the Web Application.
  
=== Web Application Limitations ===
+
== Web Application Limitations ==
  
 
When you export one or more Presence tasks into a Web Application, the Presence Database engine is not exported.  Only the execution engine (Primary/Slave server) is exported.
 
When you export one or more Presence tasks into a Web Application, the Presence Database engine is not exported.  Only the execution engine (Primary/Slave server) is exported.
Line 20: Line 20:
 
Because the database engine is not exported, any data that you wish to access must be maintained in a separate external database such as MySQL or SQL Server. This will usually mean exporting the JAR files for those JDBC drivers (see Libraries Tab below).
 
Because the database engine is not exported, any data that you wish to access must be maintained in a separate external database such as MySQL or SQL Server. This will usually mean exporting the JAR files for those JDBC drivers (see Libraries Tab below).
  
Also, any tasks that rely on comparison data - such as those that use Data Filters, or Object Monitors with the Deviation tab enabled - will not function.  This should not pose a major problem as tasks that use comparison data are not good candidates for web applications.  See [[[Data Filter]]
+
Also, any tasks that rely on comparison data - such as those that use Data Filters, or Object Monitors with the Deviation tab enabled - will not function.  This should not pose a major problem as tasks that use comparison data are not good candidates for web applications.  See [[Data Filter]].
 +
 
 +
== Creating A Web Application ==
 +
 
 +
From the Tools menu select Create Web Application.  The Export Web Application dialog appears.
 +
 
 +
=== Introduction Tab ===
 +
 
  
  
 
{{AdminClientNavigation}}
 
{{AdminClientNavigation}}

Revision as of 11:51, 12 July 2010

Administration Client > Create Web Application

Create Web Application

In many cases, Presence web applications are run on an internal web server, which means the Presence system can run tasks called On Demand by the web server.

However, there may also be cases where, for reasons of security or convenience, the web server is physically isolated on the network from the Presence system, and therefore Presence tasks cannot be run. For example you may wish to create an application using Presence and then deploy it onto a PDA.

In this instance, you can still run Presence based applications on your web server by exporting them from the Presence System.

A Presence Web Application is a standalone copy of one or more Presence Tasks, which also includes the Presence execution engines (Primary/Slave server engines). The Web Application is exported as a .WAR file (Web ARchive) which can be installed and hosted on any web server that supports a Java Servlet container.

The WAR file container is similar to a standard JAR File in that it is simply a zip file format containing a compressed version of multiple Java class files, however, additionally it also includes a /WEB-INF folder that includes a web.xml file to define the structure of the web application. In the case of a Presence Web Application, the web.xml file defines how the servlet engine calls the Presence tasks contained in the Web Application.

Web Application Limitations

When you export one or more Presence tasks into a Web Application, the Presence Database engine is not exported. Only the execution engine (Primary/Slave server) is exported.

In order for the execution engine to run the tasks, the configuration of each task is exported in an XML format which can then be read and processed at run-time.

Because the database engine is not exported, any data that you wish to access must be maintained in a separate external database such as MySQL or SQL Server. This will usually mean exporting the JAR files for those JDBC drivers (see Libraries Tab below).

Also, any tasks that rely on comparison data - such as those that use Data Filters, or Object Monitors with the Deviation tab enabled - will not function. This should not pose a major problem as tasks that use comparison data are not good candidates for web applications. See Data Filter.

Creating A Web Application

From the Tools menu select Create Web Application. The Export Web Application dialog appears.

Introduction Tab

Architecture > Administration Client > Create Web Application

Task Explorer | Resources Explorer | Task Designer
Menu Options | Toolbar Items