5
Defining Web-to-Go Applications

5.2.2.1 Window Sequence Example

The following example assigns the Window sequence to two clients.

Client	Sequence Range
Client 1	1-10
Client 2	11-20

When Client 1 runs out of values, Web-to-Go recreates the sequence with a new window containing unique values such as: 21, 22,..., 30.

5.2.2.2 Creating the Window Sequence

Web-to-Go creates and maintains the Window sequence on the client based on the sequence definition in the Mobile Server Repository. For example, assume that the Mobile Server Repository contains the following Window sequence definition:

Sequence Parameter	Definition
NAME	AUDIODB_SEQ
TYPE	WINDOW
START_VALUE	1
INCREMENT	1
WINDOW_SIZE	200
THRESHOLD	25

When the first client disconnects and is in offline mode, Web-to-Go creates the sequence locally by executing the following SQL statement:

CREATE SEQUENCE audiodb_seq START WITH 1 MAXVALUE 200 INCREMENT BY 1;

When the second client disconnects and is in offline mode, Web-to-Go creates the sequence locally by executing the following SQL statement:

CREATE SEQUENCE audiodb_seq START WITH 201 MAXVALUE 400 INCREMENT BY 1;

Web-to-Go keeps track of the number of assigned windows to ensure that each client has a unique range. When the first client's sequence exceeds 175, its available range drops below the specified threshold of 25. Web-to-Go detects this situation and recreates the sequence the next time the client synchronizes with the Mobile Server. Web-to-Go accomplishes this by executing the following SQL statements:

DROP SEQUENCE audiodb_seq;

CREATE SEQUENCE audiodb_seq START WITH 401 MAXVALUE 600 INCREMENT BY 1;

5.2.2.3 Defining Window Sequences for Online Mode

In online mode, all users can share the same sequence. This sequence must have a range of values that supports a large number of users and does not overlap with the range of values assigned to users in offline mode. You can meet these requirements by using one of the following methods:

• Reserve a large window for the Oracle sequence and allow disconnected clients to create sequences above this value.

• Reserve the odd sequence numbers for online mode, and the even sequence numbers for offline mode. This method requires a sequence increment of two to ensure uniqueness of the sequence numbers.

Large Window Sequence

To reserve a large window from 1 to 100000000 for the Oracle database sequence, execute the following SQL statement:

CREATE SEQUENCE audiodb_seq START WITH 1 MAXVALUE 100000000 INCREMENT BY 1;

Web-to-Go must assign disconnected clients sequence numbers that begin at least one increment higher than the window reserved for online users. If the window reserved for online users has a range from 1 to 100000000 then the first window assigned to a disconnected user must have a start value of 100000001 or higher. The following example defines window sequences to two clients whose start values account for the large window sequence already reserved for the Oracle database:

Sequence Parameter	Definition
NAME	AUDIODB_SEQ
TYPE	WINDOW
START_VALUE	100000001
INCREMENT	1
WINDOW_SIZE	200
THRESHOLD	25

Client	Sequence Range
Client 1	100000001 - 100000200
Client 2	100000201 - 100000400

Recommended: Even and Odd Window Sequences

You can provide unique sequence values for online and offline mode by assigning each mode with either odd or even sequence numbers and an identical increment value. The following procedure reserves a window with odd sequence numbers for online mode and a window with even sequence numbers for offline mode.

Execute the following SQL statement on the Oracle database server:

CREATE SEQUENCE audiodb_seq START WITH 1 INCREMENT BY 2;

Enter the following sequence definitions in the Packaging Wizard:

Sequence Parameter	Definition
NAME	AUDIODB_SEQ
TYPE	WINDOW
START_VALUE	2
INCREMENT	2
WINDOW_SIZE	200
THRESHOLD	25

When you use this method, the range of the online sequence is only limited by the maximum size of an Oracle sequence number, which is approximately 10²⁶. For offline clients, the WINDOW_SIZE and THRESHOLD parameters do not take the increment steps into account. In step 2, the disconnected clients only have 100 (200/2) possible sequence values before they need to recreate a sequence.

5.3.4.1 Locating Platform Files in the Local Application Directory

You can have multiple versions by platform of the same application published and managed in the Mobile Server Repository. Multiple implementations by platform (for example, Web-to-Go, Palm, WinCE, and Windows 32) of the same application (for example, Sales Force Automation) can exist, each of them accessing the same application tables in the Oracle database server.

For example, a C++ application developed for Compaq iPAQ can be recompiled to run on a Palm device without changing the application code. In this case, two application versions of the same application exist, each of them using the same database tables.

The Local Application Directory is the directory on the Windows development system where the different application versions are stored. Application files for each platform must be stored in a subdirectory that is dedicated to that platform, which must have a distinct name according to the platform, under the Local Application Directory. The Packaging Wizard recursively reads the application files under this application (root) directory.

For all platforms other than Web-to-Go for which you have applications, or application versions of the same application, the subdirectory for each platform must be named exactly as shown in Table 5-1, which lists the required subdirectory names and the corresponding platforms.

Table 5-1 List of Required Subdirectory Names According to the Platform

Platform	Required Subdirectory Name for Application Files
Windows 32	WIN32
WinCE SH3	wce\<platform>\<language>\SH3
WinCE SH4	wce\<platform>\<language>\SH4
WinCE MIPS	wce\<platform>\<language>\MIPS
WinCE StrongArm	wce\<platform>\<language>\ARM
EPOC	EPOC
Palm	PALM

Example:

On your local machine, a Local Application Directory called which can be any name you choose, for example, 'Applications'. This subdirectory stores the different application versions by platform, or in a directory name of your choice for Web-to-Go applications, which is illustrated as follows:

C:\Applications

The Java application files for the Web-to-Go platform may be stored in a subdirectory, which you may name as you choose, for example, MyAPP. This is stored under the Applications directory, which is illustrated as follows:

C:\Applications\MyAPP

If no platform type directory is specified, for example, PALM, the application will be treated as a Web-to-Go application. Web-to-Go applications can be packaged into any directory, for example:

C:\

or

C:\Applications

or

C:\Applications\MyAPP

The C++ application files for the Palm platform must be stored in the \PALM subdirectory under the Applications directory, which is illustrated as follows:

C:\Applications\PALM

The C++ application files for iPAQ must be stored in the \WCE\<platform>\<language>\ARM subdirectory, where <platform> determines the operating system, and <language> determines the language set you wish to use. See the Oracle9i Lite Developers Guide for Windows CE for more information. These are placed under the Applications directory, which is illustrated as follows:

C:\Applications\WCE\<platform>\<language>\SH4

The Local Application Directory is C:\Applications but it has three subdirectories, each of which contains the version of the application files for a particular platform:

C:\Applications            // Local Application Directory

C:\Applications\MyAPP      // Application subdirectory for the Web-to-Go version

C:\Applications\PALM       // Application subdirectory for the Palm version

C:\Applications\WCE\Pocket_PC\us\SH4  // Application subdirectory for the Pocket

                                          PC, US English, StrongArm version

5.3.5.1 Compile JSP

If you click the Compile JSP button, the Packaging Wizard will compile all the JSP files that are listed in the Files panel.

The Compile JSP button allows you to compile your JSP files for deployment. If you click the Compile JSP button, the following Compile JSP dialog box appears with detailed compilation information. If there are any errors, you should correct the JSP files before proceeding.

5.3.5.2 Sorting

You can sort the files by their extensions or by the directory in which they are located. To sort files, click the By Extension or By Directory radio buttons.

5.3.5.3 Filters

When you click the Load button, the Input dialog box appears. You can use the Input dialog box to create a comma-separated list of filters that either include or exclude application files from the upload process. To exclude a file, type a preceding minus sign (-) before the file name. For example, to load all files but exclude files with the .bak and .java suffixes, type the following:

*,-*.bak,-*.java

5.3.9.1 Creating New Snapshots

To create new snapshots, click the New button. The New Snapshots dialog box appears. As Figure 5-10 illustrates, if you click the Server tab, the Server panel appears, which contains fields for snapshot name, weight, owner, and SQL, as well as a check box for generating SQL.

Create a new snapshot by entering the appropriate information. The name that you enter in the Name field reflects the underlining database table name.

For a description of Weight, see Section 5.3.9, "Defining Snapshots For Replication".

If you enable Generate SQL, you should provide a CreateTable SQL statement to construct the database table. Enter the SQL statement in the SQL field. At the end of the defining phase, you will have the option to generate a SQL file.

Use the Win32 tab for the Mobile Client for Web-to-Go.

If you click the Win32 tab, the following panel appears:

Create a new snapshot on the Mobile Client for Web-to-Go by modifying the following features in the New Snapshots dialog box:

Feature	Description
Updateable	When selected, this check box creates an updateable snapshot of the named table.
Template	Displays the snapshot template for the named table. You can modify the snapshot template. Administrators can instantiate variables for different users to this template using the Mobile Server Control Center. See "Defining Snapshots For Replication" for more information about template variables.

5.3.9.2 Creating Indexes for Snapshots

To create an index for a snapshot using the Packaging Wizard, use the following procedure:

1. From the Snapshots Panel (see Figure 5-9, "Snapshots Panel") select the Edit button to create an index from an existing snapshot, or the New button for creating a new snapshot and new index.

   Figure 5-12 Index Creation

   
   

2. Select the platform tab on the panel which appears, for example Win 32. The SQL statement which defines your snapshot appears in the Template field. Below that is an Indices table; to create a new index, select the New button beneath this table.

3. There are three columns in the Indices table:

   • Name - This is the name of the index.

   • Type - Indexes can be Regular, Primary, or Unique. There is a drop down menu to select this.

   • Columns - Enter the column name which the index uses.

5.3.9.3 Importing Snapshots

To import snapshots from an Oracle database or from an Oracle Lite database, click the Import button. The database connection window appears if you have not specified a connection.

Enter the user name, password, and database URL for the Oracle database, or Oracle Lite database from which you are importing your snapshot(s). The Tables window appears.

Select the schema from which you want to import your table(s), and then select the table(s). Click Add and then click Close. The table appears in the Snapshots panel of the Packaging Wizard.

5.3.9.4 Editing Snapshots

To edit a snapshot, select the snapshot from the Snapshots panel and click Edit. The Edit Snapshots dialog box appears.

Edit the snapshot by modifying the following features of the Edit Table window:

Feature	Description
Create on Client	When selected, the check box allows you to edit the snapshot on the Mobile Client for Web-to-Go.
Updateable	When selected, this check box creates an updateable snapshot of the named table.
Template	Displays the snapshot template for the named table. You can modify the snapshot template. Administrators can instantiate variables for different users to this template using the Mobile Server Control Center.

5.3.10.1 Importing Sequences

To import sequences from an Oracle database, click the Import button. The Sequences window appears.

Select the sequence you want to import, click Add, and then click Close.

To edit a sequence, select the sequence from the Sequences panel and click Edit. The Edit Sequences window appears.

Edit the sequence by modifying the following features of the Edit Sequences window:

Feature	Description
Name	The name of the sequence.
Create on Server	When selected, this check box enables the options for creating a sequence on the Oracle database. Information entered by the user is used to generate a SQL script to create the sequence on the Oracle server.
Start Value	The start value of the sequence on the Oracle database.
Increment	The increment of the sequence on the Oracle database, beginning with its start value.
Minimum	The minimum start value for an ascending sequence on the Oracle database. For example, an ascending sequence could start at 1 and continue in ascending order.
Maximum	The maximum start value for a descending sequence on the Oracle database. For example, a descending sequence could start at -1 and continue in descending order.
Create on Client	When selected, this check box enables the options for creating a sequence on the Mobile Client for Web-to-Go.
Type	Defines the type of sequence on the Mobile Client for Web-to-Go. Options include the window and leapfrog sequences.
Start Value	The sequence start value on the Mobile Client for Web-to-Go.
Increment	The increment of the sequence on the Mobile Client for Web-to-Go, beginning with its start value.
Window Size	The range of numbers that constitute a window sequence on the Mobile Client for Web-to-Go. This information is not used by the leapfrog sequence.
Threshold	The minimum range of required numbers in a window sequence. Web-to-Go creates a new sequence when the existing one reaches this range and when the client goes offline. This information is not used by the leapfrog sequence.

5.3.11.1 Importing Views and Indexes Definitions

To import views and indexes definitions from an Oracle database, click the Import button. The import DDLs window appears.

To import an index definition, click the Indexes tab and then click the schema from which you want to import an index. Select the index you want to import, click Add, and then click Close.

To import a view definition, click the Views tab and then click the schema from which you want to import a view. Select the view you want to import, click Add, and then click Close.

5.3.13.1 The XML File

The Packaging Wizard automatically outputs all of your application information to an XML file. The Packaging Wizard retains the XML file on the local machine and provides you with the option of publishing it to the Mobile Server, among others. You can only publish the XML file to the Mobile Server when the server is running. Packaging Wizard always retains the Web-to-Go application's XML file on the local machine.

5.3.13.2 Creating Files

The Create Files option allows you to either package your application components in a .jar file or generate SQL scripts that create database objects. To package your application components in a .jar file, click Create Files, and then click "Package applications in a JAR file". You can specify the location for the .jar file. To generate SQL scripts, click Create Files, and then click "Generate SQL scripts for database objects". The generated script will be placed in a SQL subdirectory under the application's local root directory. The SQL scripts, which make use of the information you supplied about the server-side table, sequences, and DDLs, can be executed on the database to create these database objects.

5.3.13.3 Publishing the Application

The Publish Current Application option enables you to publish the application that you created and defined in the Packaging Wizard. To publish the Web-to-Go application, click the Publish Current Application button and then click OK. The Publish Application window appears.

Enter the required information in the specified fields of the Publish the Application dialog box.

Field	Value
Mobile Server URL	http://server
Mobile Server Username	Administrator
Mobile Server Password	admin
Repository Directory	/tutorial
Public	Do not select the Public check box.

5.3.13.4 Restarting the Packaging Wizard

The Restart Wizard option enables you to restart the Packaging Wizard. Using this option returns you to the Welcome panel of the Packaging Wizard. To restart the Packaging Wizard, click Restart Wizard and then click OK.