2 Installing and Running Applications on the Raspberry Pi Board

You can run IMlets directly on the Raspberry Pi board by using the commands shown in Table 2-1.

Table 2-1 Raspberry PiShell Commands

The Developer Agent program is the proxy.jar file inside the util directory of the Oracle Java ME Embedded distribution.

To install the Developer Agent program, follow these steps:

When using the Developer Agent in a server mode, it is important that you first started the Java runtime on the Raspberry Pi board to allow access to the AMS.

To start the Developer Agent program, follow these steps:

After the Developer Agent starts, use the AMS CLI.

When using the Developer Agent in a client mode, ensure that you configured the client mode as described in the Configuring Client Mode Connection.

To start the Developer Agent program, use these steps:

After the Developer Agent starts, use the AMS CLI.

Generate the Developer Agent connection CA certificate by performing the Java SE keytool command:

keytool.exe -genkeypair -keystore <JKS keystore file> -alias <keypair alias> -keyalg RSA -keysize 4096 -validity 7305 -storepass <keystore password> -keypass <keypair password>

Install the Developer Agent CA Certificate on your device by performing the CLI command while the device and Developer Agent are being connected:

ks-import -proxy -keystore <JKS keystore file> -storepass <keystore password> -keypass <keypair password> -alias <keypair alias>

This command installs the CA certificate to the /appdb/cert_proxy directory.

To configure the Java runtime properties involved in establishing a secured connection to the Developer Agent, set the following properties:

proxy.certificate=<CA certificate name>

proxy.secured=true

1. Start a PuTTY executable file on your desktop computer.
2. Create raw socket connections to the IP address of the host running the Developer Agent, and port 65002.

Here is a typical example of using the AMS to install, list, run, and remove an Oracle Java ME Embedded application on the board:

oracle>> ams-install file:///C:/some/directory/hello.jar hostdownload
<<ams-install,start install,file:///C:/some/directory/hello.jar
<<ams-install,install status: stage DONE, 0%
<<ams-install,install status: stage DONE, 100%
<<ams-install,OK,Install success
oracle>> ams-install http://www.example.com/netdemo.jar
<<ams-install,start install,http://www.example.com/netdemo.jar
<<ams-install,install status: stage DONE, 0%
<<ams-install,install status: stage DONE, 100%
<<ams-install,OK,Install success
oracle>> ams-install http://www.example.com/notthere.jar
<<ams-install,start install,http://www.example.com/notthere.jar
<<ams-install,FAIL,errorCode=103 (OTHER_ERROR)

Note that the final installation example failed with an error code and matching description.

Similarly, install an additional IMlet: rs232dem. After an IMlet is installed, verify it using the ams-list command. Each IMlet has been assigned a number by the AMS for convenience.

oracle>> ams-list
<<ams-list,0.hello|Oracle,STOPPED
<<ams-list,1.netdemo|Oracle,STOPPED
<<ams-list,2.rs232dem|Oracle,RUNNING
<<ams-list,OK,3 suites are installed

You can use the ams-remove command to remove any installed IMlet.

oracle>> ams-remove 0
<<ams-remove,OK,hello removed

The results can again be verified with the ams-list command.

oracle>> ams-list
<<ams-list,1.netdemo|Oracle,STOPPED
<<ams-list,2.rs232dem|Oracle,RUNNING
<<ams-list,OK,2 suites are installed

Finally, start the IMlet using the ams-run command. The application can be terminated with the ams-stop command.

oracle>> ams-run 1
<<ams-run,OK,started

oracle>> ams-list
<<ams-list,1.netdemo|Oracle,RUNNING
<<ams-list,2.rs232dem|Oracle,RUNNING
<<ams-list,OK,2 suites are installed

1. Ensure that the usertest.sh script in the /bin directory is running on the Raspberry Pi board.
2. Ensure that the Developer Agent program does not run on the desktop computer.
3. Start the Oracle Java ME SDK 8.3 Device Connections Manager (located in the <SDK Installation Folder>/bin) directory and click its icon in the system tray. A Device Connections Manager window is shown in Figure 2-3.

   Figure 2-3 Device Connections Manager Window

   [画像:Description of Figure 2-3 follows]
   Description of "Figure 2-3 Device Connections Manager Window"
4. Click the Add new device connection button, ensure that the IP Address or Host Name list contains the correct IP address of the Raspberry Pi board, and click OK.
5. After the Raspberry Pi board is registered, its IP address is listed on the Device Connections Manager list and its status is Connected as shown in Figure 2-4.

   Figure 2-4 Device Connections Manager Window with Raspberry Pi Connected

   [画像:Description of Figure 2-4 follows]
   Description of "Figure 2-4 Device Connections Manager Window with Raspberry Pi Connected"

There are two ways to assign the Raspberry Pi board to your project:

• Using an Existing NetBeans Project

• Creating a New NetBeans Project

After you assign the board to your project, clicking Run Project in the NetBeans IDE runs your IMlet on the board instead of on the emulator.

Using an Existing NetBeans Project

Creating a New NetBeans Project

1. Double-click the ME8EmbeddedApplication1.java file in the Projects window.
2. Copy the following sample code and paste it in the Source window.

   package me8embeddedapplication1;
    
   import jdk.dio.DeviceManager;
   import jdk.dio.UnavailableDeviceException;
   import jdk.dio.gpio.GPIOPin;
   import java.io.IOException;
   import java.util.logging.Level;
   import java.util.logging.Logger;
   import javax.microedition.midlet.*;
    
    
   public class ME8EmbeddedApplication1 extends MIDlet {
    
    @Override
    public void startApp() {
    
    try {
    GPIOPin pin = (GPIOPin)DeviceManager.open(2);
    boolean b = pin.getValue();
    } catch (UnavailableDeviceException ex) {
    } catch (IOException ex) {
    Logger.getLogger(ME8EmbeddedApplication1.class.getName()).log(
   Level.SEVERE, null, ex);
    }
    
    }
    
    public void pauseApp() {
    }
    
    public void destroyApp(boolean unconditional) {
    }
   }
   

3. Clean and build the ME8EmbeddedApplication1 project by clicking on the hammer-and-broom icon in the NetBeans toolbar or by selecting Run then Clean and Build Project (ME8EmbeddedApplication1).
4. Run the newly cleaned and built ME8EmbeddedApplication1 project by selecting the green right-arrow icon in the NetBeans toolbar or by selecting Run then Run Project (ME8EmbeddedApplication1).

   When the run is successful, the EmbeddedExternalDevice1 emulator starts with the ME8EmbeddedApplication1 suite running.

1. Open the source code of your IMlet class on the NetBeans editor.
2. Click once directly on the line number where you want to set a breakpoint. The line number is replaced by a red square and the line is highlighted in red.
3. Select Debug then Debug Project or use the Debug button on the toolbar.

1. In NetBeans, right-click the project name (ME8EmbeddedApplication1 in this example) and select Properties.
2. Click Application Descriptor, then in the resulting pane, click API Permissions.
3. Click the Add button, and add the jdk.dio.DeviceMgmtPermission API, as shown in Figure 2-6.
4. Click OK to close the project properties dialog.

   Figure 2-6 Adding API Permissions with NetBeans

   [画像:Description of Figure 2-6 follows]
   Description of "Figure 2-6 Adding API Permissions with NetBeans"
5. If you are not using an IDE, then manually modify the application descriptor file to contain the following permissions:

   MIDlet-Permission-1: jdk.dio.DeviceMgmtPermission "*:*" "open"
   

Method #1: Signing Application Using the NetBeans IDE

Method #2: Signing Application Using a Command Line

Method #3: Using NullAuthenticationProvider

1. Run the SDK Device Connections Manager located at <SDK Installation Folder>/bin/device-manager.exe.
2. Wait until the device connection status displays Connected.
3. Run the SDK EmbeddedExternalDevice1 by using the following command:

   emulator.exe -Xjam -Xdevice:EmbeddedExternalDevice1
   

4. Install and run an IMlet using the GUI of the SDK EmbeddedExternalDevice1 window.
5. Click the Output button. The log is available in the SDK EmbeddedExternalDevice1 Output Console window shown in Figure 2-11.

   Figure 2-11 Java Logging Using the SDK Output Console

   [画像:Description of Figure 2-11 follows]
   Description of "Figure 2-11 Java Logging Using the SDK Output Console "

1. Start a console application and enter the following command specifying the IP address of the Raspberry Pi board:

   java -jar proxy.jar -socket <IP Address>
   

2. Install and run IMlets using the CLI.
3. The log will be available in the same console window shown in Figure 2-12.

   Figure 2-12 Java Logging Using a Console Application

   [画像:Description of Figure 2-12 follows]
   Description of "Figure 2-12 Java Logging Using a Console Application"

You can control the scope of information being logged by editing the following parameters in the jwc_properties.ini file:

Table 2-2 Logging Parameters

To select a level of logging details, set a parameter value as follows.

• 0 - all information messages

• 1 - warning level messages

• 2 - errors

• 3 - critical (system's functioning is not guaranteed)

• 4 - logging is turned off