Lexmark X925 Lexmark Document Distributor - Page 17

Managing solution projects

Page 17 highlights

Developing workflow solutions 17 src\-This contains the source files of the project. conf\-This contains the configuration files for the project. devicePolicy.ldd-This is the configuration file that manages the profiles and associated policy settings associated with a solution. forms.ldd-This is the configuration file that manages the formsets included with or linked to the solution. reports.ldd-This is the configuration file that manages the custom reports included with the solution. solutionSettings.ldd-This is the configuration file that manages the global and local solution settings available for a solution. Settings created here are accessible by scripts and can be changed using Lexmark Management Console. statusPage.properties-This is the configuration file that manages the look and feel of the custom status page that may be used instead of Lexmark Management Console for non‑technical users. esf\-This contains any .fls files for eSF applications used with a hybrid solution. esf-app-source-code\-This contains the source files from any eSF applications used with a hybrid solution. forms\-This contains any formsets included with the solution. (Use the forms.ldd configuration file to add forms.) images\-This contains images associated with the solution, such as home screen images added using the device policy editor. Files in this folder are copied to the images\ folder of the solution on the LDD system when the solution is installed. reports\-This contains compiled Jasper custom report files associated with the solution. (Use the reports.ldd configuration file to add reports.) scripts\-This contains the JavaScript scripts included in the solution. This folder may be empty for solutions that deploy only an eSF application or LDD component. Each main script located here should be assigned to a profile in devicePolicy.ldd. scheduled\-This contains scripts that can be scheduled using Lexmark Management Console after a solution is deployed. solution\-This contains files and components accessed only by the current solution. This folder is accessible by scripts through the taskInfo.solutionDir property. WEB‑INF\-This contains property files for custom components specific to a solution that should not be shared with other solutions. lib\-This contains custom components specific to a solution that should not be shared with other solutions. target\-This contains the compiled solution after a project build, in addition to associated class files and XML descriptor files. This folder appears only in a new project after the first build. Note: This folder may be deleted to ensure a clean build. install\-This contains the compiled solution, with the extension .solution. The file contained here can be distributed independently as a complete solution. solution\-This contains copies of all files contained in the solution file from the time of the build. Note: File and folder names within a workflow solution project cannot contain double‑byte characters. However, files themselves may contain double‑byte characters. Managing solution projects The following operations are performed the same way for LDD solution projects and for any project in Eclipse: • Importing existing projects • Importing archive files

  • 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

src\
—This contains the source files of the project.
conf\
—This contains the configuration files for the project.
devicePolicy.ldd
—This is the configuration file that manages the profiles and associated policy settings
associated with a solution.
forms.ldd
—This is the configuration file that manages the formsets included with or linked to the
solution.
reports.ldd
—This is the configuration file that manages the custom reports included with the solution.
solutionSettings.ldd
—This is the configuration file that manages the global and local solution settings
available for a solution. Settings created here are accessible by scripts and can be changed using Lexmark
Management Console.
statusPage.properties
—This is the configuration file that manages the look and feel of the custom status
page that may be used instead of Lexmark Management Console for non
technical users.
esf\
—This contains any .fls files for eSF applications used with a hybrid solution.
esf-app-source-code\
—This contains the source files from any eSF applications used with a hybrid solution.
forms\
—This contains any formsets included with the solution. (Use the
forms.ldd
configuration file to add
forms.)
images\
—This contains images associated with the solution, such as home screen images added using the
device policy editor. Files in this folder are copied to the images\ folder of the solution on the LDD system
when the solution is installed.
reports\
—This contains compiled Jasper custom report files associated with the solution. (Use the
reports.ldd
configuration file to add reports.)
scripts\
—This contains the JavaScript scripts included in the solution. This folder may be empty for solutions
that deploy only an eSF application or LDD component. Each main script located here should be assigned
to a profile in devicePolicy.ldd.
scheduled\
—This contains scripts that can be scheduled using Lexmark Management Console after a
solution is deployed.
solution\
—This contains files and components accessed only by the current solution. This folder is accessible
by scripts through the
taskInfo.solutionDir
property.
WEB
INF\
—This contains property files for custom components specific to a solution that should not be
shared with other solutions.
lib\
—This contains custom components specific to a solution that should not be shared with other
solutions.
target\
—This contains the compiled solution after a project build, in addition to associated class files and XML
descriptor files. This folder appears only in a new project after the first build.
Note:
This folder may be deleted to ensure a clean build.
install\
—This contains the compiled solution, with the extension .solution. The file contained here can be
distributed independently as a complete solution.
solution\
—This contains copies of all files contained in the solution file from the time of the build.
Note:
File and folder names within a workflow solution project cannot contain double
byte characters. However,
files themselves may contain double
byte characters.
Managing solution projects
The following operations are performed the same way for LDD solution projects and for any project in Eclipse:
Importing existing projects
Importing archive files
Developing workflow solutions
17