Note: This documentation assumes you have already installed the UIEvolution Software Development Kit (UIE SDK) using the installation program. If you need help installing the UIE SDK, please read the SDK Quickstart.

Use the SDK Quickstart to test drive UIEvolution's development environment with a simple application-to-phone example. The sample application in the QuickStart Guide illustrates the ease of modification and simple one-button publishing of UJML applications to various target devices and deployment environments.

1. Verify that you have completed all installation steps in the SDK Quickstart.
2. Run the samples as described in the SDK User Guide.
3. Work through the tutorial in the Inside UJML tutorial.
4. Review the UJML Language Reference to learn more about UJML.

Your UIE SDK installation includes the following documentation:

You can always find the latest documentation on the UIE SDK developer's Web site at http://developer.uievolution.com/docs/en.

The UIEvolution SDK consists of the following components:

• The UIE debugger allows you to run your UJML programs interactively; watching variables change values, stepping through the code, and setting breakpoints.
• The UIE Player runs compiled UJML programs on any device for which a player exists.
• The UJML compiler turns UJML source code into byte code files which the UIE Player interprets.

In standalone mode the SDK components run on your computer using Sun Microsystem's Java 2 Standard Edition virtual machine (J2SE). Standalone mode enables you to develop and run applications using UJML, an XML-based programming language.

In client-server mode, UJML applications incorporate server-side dynamic information, such as databases, Web services, or many other information sources. The UJML compiler resides on the server along with code used to generate UJML source code. You may deploy both client and server components on the same computer, or on different computers. A key assumption is that the client and server can communicate with each other using the HTTP protocol. The installation guide describes how to set up both the client and the server on the same machine.

The UIE Player and debugger (client components) use Sun Microsystem's Java 2 Standard Edition version machine (J2SE). The samples and byte code compiler (UIE server components) require the J2SE Software Development Kit and Java Servlet/Java Server Page container. Apache's Tomcat Java Servlet/Java Server Page container is installed as part of the UIE SDK installation process.

The UIEvolution SDK installs to the following directory structure, including both UIEvolution components and Tomcat components (Tomcat-only directories are in red): 

UIEvolution SDK - Installation root.

• bin - Contains batch files and build scripts.
• cache - Used by the UIE components to cache temporary files.
• doc - Contains the UIE SDK Documentation.
• dpref - Contains preference files and property bag files for UIE SDK components.
• dtd - Contains UJML DTDs (Document Type Declarations).
• extensions - Contains extensions for the UIE SDK components.
• lib - Contains Java .jar files for the UIE SDK components.
• plugins - Contains plugins for the UIE SDK components.
• tomcat-4.1.29 - Contains the Tomcat installation and UIE SDK sample files
  • bin - Binary executables and scripts for Tomcat.
  • common - Shared Tomcat server classes.
  • conf - Configuration files for Tomcat.
  • logs - Destination directory for Tomcat log files.
  • server - Internal Tomcat server classes and their dependencies.
  • shared - Classes shared by all Tomcat Web applications.
  • temp - Directory used by Tomcat/JVM for temporary files.
  • webapps - Base directory containing Tomcat Web applications.
    • examples - JSP (Java Server Pages) and Servlet examples for Tomcat.
    • ROOT - Tomcat server Web root.
    • starter - Contains a simple 'starter' UJML client-server application.
    • tomcat-docs - Documentation for Tomcat.
    • ujmlsamples - Sample UJML code for the UIE SDK.
      • appserver - Sample UJML code that runs in client/server mode.
      • standalone - Sample UJML code that runs in standalone mode.
      • uiexml - Sample JSP UJML Tag Library code.
    • webdav - Tomcat WEBDAV documentation.
  • work - Scratch directory used by Tomcat.