Intermec IF2 IF2 Network Reader User Manual - Page 66

Create a Configuration File

Get Intermec IF2 PDF manuals and user guides View all Intermec IF2 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 66 highlights

Chapter 4 - Install Applications on the IF2 with Expanded Memory Option Create a Configuration File When you package your application for installation on the IF2, you need to include a configuration file in the root directory of the archive. The file must be named "userapp.conf " and must include this syntax: AUTOSTART=true|false RUNAFTERINSTALL=true|false CMDLINE= where: AUTOSTART specifies whether or not the application should automatically be executed when the IF2 boots. When AUTOSTART=true, the Auto-Start check box for this application on the Application Control screen will be checked. Note: After you install the application on the IF2, you can enable or disable the auto-start feature from the web browser interface. For help, see "Manage Applications" on page 56. RUNAFTERINSTALL specifies whether or not the application should be started immediately after installation. CMDLINE specifies the application name and optional parameters it accepts. Specify command line parameters as if the application is being executed from inside the directory containing the application. Note: Do not use the $JAVA_HOME environment variable in the command line. This example runs a C# application named "testapp.exe" using the Mono runtime: CMDLINE=./testapp.exe For Java applications, CMDLINE should specify the Java interpreter location, the classpath, and the class containing the application's entry point. This example runs the class "HelloWorld": CMDLINE=/usr/java/bin/java -cp . HelloWorld 52 IF2 Network Reader User Manual

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
Chapter 4 — Install Applications on the IF2 with Expanded Memory Option
52
IF2 Network Reader User Manual
Create a Configuration File
When you package your application for installation on the IF2, you
need to include a configuration file in the root directory of the
archive. The file must be named “userapp.conf” and must include this
syntax:
AUTOSTART=true|false
RUNAFTERINSTALL=true|false
CMDLINE=<command line to start the application>
where:
AUTOSTART
specifies whether or not the application should
automatically be executed when the IF2 boots. When
AUTOSTART=true
, the Auto-Start check box for this application on
the Application Control screen will be checked.
RUNAFTERINSTALL
specifies whether or not the application should
be started immediately after installation.
CMDLINE
specifies the application name and optional parameters it
accepts. Specify command line parameters as if the application is
being executed from inside the directory containing the application.
This example runs a C# application named “testapp.exe” using the
Mono runtime:
CMDLINE=./testapp.exe
For Java applications,
CMDLINE
should specify the Java interpreter
location, the classpath, and the class containing the application’s
entry point. This example runs the class “HelloWorld”:
CMDLINE=/usr/java/bin/java -cp . HelloWorld
Note:
After you install the application on the IF2, you can enable or
disable the auto-start feature from the web browser interface. For
help, see
“Manage Applications” on page 56.
Note:
Do not use the $JAVA_HOME environment variable in the
command line.