Rich Client (J2ME CDC) Apps

In this section, we will show you how to generate a sample rich client crm application from scratch. This assumes that the web service for the application is already available and ITAnyplace plugin is installed in Eclipse. This sample ships with ITAnyplace.

Follow the following steps:

• File -> New -> Other. Select Rich Client(J2ME CDC Based) under the field ITAnyplace Project

• Enter project name 'crmcdc' and click Next

• Edit any Java settings and click Finish

• This creates a new project with the following hierarchy

• Select the project and then click New --> Other --> ITAnyplace Model Creation Wizard. Select ITAnylace Workflow and click Next

• Enter model file name and click Next

• Pick a web service WSDL file from local file system (eg. SyncablePort.wsdl) and click Finish

• Tool will parse the wsdl and generate the following model

• Click on the 'Semi Connected Workflow', the model appears with all the methods of the wsdl. Enter name (crmcdc), App Server (http://localhost), App Server port (8080) and select Notification (If user wants notification support click on yes) .

• Add 'index' node to Semi Connected Workflow. Semi Connected Workflow --> Select new child -->Semi Connected Node

• Add 'Add' Link to Semi Connected Node. Semi Connected Node --> Select new child --> Link

• Add 'View' Link to Semi Connected Node. Semi Connected Node --> Select new child --> Link

• Add 'Update' Link to Semi Connected Node. Semi Connected Node --> Select new child --> Link

• Add 'Delete' Link to Semi Connected Node. Semi Connected Node --> Select new child --> Link

• Add  'Purge' Link to Semi Connected Node. Semi Connected Node --> Select new child --> Link

• Add 'Sync' Link to Semi Connected Node. Semi Connected Node --> Select new child --> Link

Index node looks as shown below:

• Add 'Add' node to Semi Connected Workflow. Semi Connected Workflow --> Select new child -->Semi Connected Node

After save, Insert node looks as shown below:

• Add Attachment support in the Add node by Semi Connected Workflow --> Select new child -->Attachment

      Since this is Add operation, only Upload is enabled.

Attachment node looks as shown below:

• Add 'View' node to Semi Connected Workflow. Semi Connected Workflow --> Select new child -->Semi Connected Node

• Add 'accountName' Semi Connected Outport Port to Semi Connected Node. Semi Connected Node --> Select new child -->Semi Connected Outport Port

View node looks as shown below:

• Add 'Attachment' element Semi Connected Node View . Semi Connected Node view --> Select new child -->Attachment

     Set Download to Yes and Upload to No.

• Add  'Update' node to Semi Connected Workflow. Semi Connected Workflow --> Select new child -->Semi Connected Node

• Add 'accounName' Semi Connected Outport Port to Semi Connected Node. Semi Connected Node --> Select new child -->Semi Connected Outport Port

Update node looks as shown below:

• Add attachment support to Update node by Semi Connected Workflow --> Select new child -->Attachment

• Add 'Delete' node to Semi Connected Workflow. Semi Connected Workflow --> Select new child -->Semi Connected Node

• Add 'accoutName' Semi Connected Outport Port to Semi Connected Node. Semi Connected Node --> Select new child -->Semi Connected Outport Port

Delete node looks as shown below:

• Add 'Purge' node to Semi Connected Workflow. Semi Connected Workflow --> Select new child -->Semi Connected Node

• Add 'accountName' Semi Connected Outport Port to Semi Connected Node. Semi Connected Node --> Select new child -->Semi Connected Outport Port

Purge node looks as shown below:

• Add 'Sync' node to Semi Connected Workflow. Semi Connected Workflow --> Select new child -->Semi Connected Node

• Add 'accountName' Semi Connected Outport Port to Semi Connected Node. Semi Connected Node --> Select new child -->Semi Connected Outport Port

• Add 'accountNo' primary key to Semi Connected Node. Semi Connected Node --> Select new child -->Primary Key

Sync node looks as shown below:

After Generating the model, its time to generate the code for the model.

• Right Click on My.Model and go to itanyplace Generate Code. This will generate the classes under crmcdc folder (same as the Semi Connected workflow name) for each node

Directory Structure is shown below:

• cards.properties – Holds configuration information for the generated application
• run. bat – Launcher for Win32
• wmrun.lnk – Launcher for Windows Mobile
• clientdb.yap - Database for the application

Deployment of semi-connected applications

A couple of additional steps are required to deploy a J2ME CDC application:

• Server side

• Put all classes except (Syncable.java and SyncRecord.java) generated by “Generate Code” command in the class path of the sync servlet on the server. These classes are required by Axis to serialize and de-serialize objects. Use the Web service import utility in the Admin Console to import jar of these classes.

• Client side
• ‘Generate Code’ command creates a file called cards.properties.

ITAnyplace app container uses cards.properties to create screens (cards) for each node. It uses AWT cardlayout. If it finds any node with operation type ‘None’, that node is used as the index (first) card. If you have more than one ‘None’ nodes, then please edit cards.properties and mark the desired card as the index card

• Before launching the app on the client, please ensure that wmrun.lnk and win32run.bat have proper commands. Our client assumes that a jvm is installed on the device. Please make sure that these files point to the correct jvm.

• To test the generated code for (J2ME CDC) inside the project (say crmcdc) which contain the java file name AppLauncher.java under the package crmcdc as shown in fig above.

• Create provisioning archive for the application. Deploy the par by using ITAnyplace Admin Console. Use the Download Manager to install it on the device.

Setting up the test environment

While ITAnyplace client only requires a JVM, here is a list of utilities that you would find useful in developing and testing applications on PocketPC.

• Emulator

Microsoft provides a standalone PocketPC emulator. You can download and install it from the link given below. The emulator requires Virtual Machine Network Driver. Please install it from the link given below.

• Emulator

http://www.microsoft.com/downloads/details.aspx?familyid=C62D54A5-183A-4A1E-A7E2-CC500ED1F19A&displaylang=en#QuickInfoContainer

• Virtual Machine Network Driver for Microsoft Device Emulator

http://www.microsoft.com/downloads/details.aspx?familyid=DC8332D6-565F-4A57-BE8C-1D4718D3AF65&displaylang=en

• Microsoft Active Sync

http://www.microsoft.com/windowsmobile/downloads/activesync38.mspx

• Windows Mobile Developer Power Toys

http://www.microsoft.com/downloads/details.aspx?FamilyID=74473fd6-1dcc-47aa-ab28-6a2b006edfe9&DisplayLang=en

Running your applications in JVM

There are two ways to use the virtual machine, by invoking j9.exe or j9w.exe. The first one is equivalent to java.exe in traditional J2SE; the second is equivalent to javaw.exe in that environment. j9w.exe starts the application without generating command line output. In other words, it starts silently. For development purposes, j9.exe is better, since the exceptions will be displayed on the screen; while for final software releases j9w.exe is better.

In order to run applications in the pocket PC, you must always use full path file names in your applications. This includes the options and parameters of your java application. The pocket PC and the j9 virtual machine seem not to understand relative paths.

The path names, jvm option keys and the java application name must be writtenIn double quotes - " ". For, example, to run a Hello World application you can create a windows link file by creating a file with extension .lnk. Change its content to look like:

• for java Class file

255#"\J9\PPRO10\bin\j9.exe" "-jcl:ppro10" "-cp" "\opt\SWT\" "HelloWorld"

or

• for java jar file containing classes

255#"\J9\PPRO10\bin\j9.exe" "-jcl:ppro10" "-cp" "\My documents\example\hello.jar"

"com.Hello"

In this example, the HelloWorld.class file is located at \opt\SWT\ directory. The parameter "-jcl:ppro10" indicates to J9 which profile to use for its execution, in this case the personal profile. The current directory is provided as the classpath. This is necessary, since the HelloWorld.class file is located in the \opt\SWT directory. The additional packages, installed in the ext folder of J9 runtime are automatically part of the classpath and do not need to be passed to the -cp parameter. The "255#" part in the begining of the link file indicates the size of the command line in bytes. This seems not to work well in the Windows CE 2003, though: more than 255 characters are ignored.

Alternatively, you can create a .bat file, similar to the ones you use in regular windows desktop, and add the line above with the exception of the "255#" part. In order to execute .bat files, however, you need to run the cmd.exe application you previously installed in Microsoft Power Toys.

Here it is an example of a .bat file that runs a YANCEES publish client."\Program Files\J9\PPRO10\bin\j9.exe" "-jcl:ppro10" "-cp" "\opt\RMI\Yancees-

SNAPSHOT.jar;\opt\RMI\" -D"java.security.policy=file://opt/RMI/java.policy.all" -

D"java.rmi.server.codebase=file://opt/RMI/Yancees-SNAPSHOT.jar" "RMIPublisher"

"bahia.ics.uci.edu" "/opt/RMI/event.xml"

Test the client installation

On Windows Mobile, use the launcher (say wm.lnk) to launch the application. You should see the following application after running wm.lnk.