com.webos.service.configurator

Creates the database schema, filecache configuration, and activities for webOS applications.

Any webOS application typically needs standard resources, like:

• Register in DB8 database (maindb/tempdb/mediadb) kind, give permissions.
• Register/modify Activity Manager Activities.
• Provide the directories which should be cached by file cache.

Typically applications have two different approaches for achieving the above:

• The application can check by itself, that all required things are registered by itself by directly calling each required service
• Alternatively, the application can provide config file for configurator for automatic resources registration/update

The first approach offers more control to the application and allows the application to execute more complex logic to initialize/update resources. However such behavior is more complex.

The second approach has benefits as all logic for kind register and kind update, activities, filecache is executed by the configurator service. The application needs only to provide only text files with the required information for configurator, and configurator will do all logic by itself.

The configurator logic works as follows:

On startup or when scan/rescan API is called, configurator reads each file from the configurator directory and:

• If the resource file is kind, then it makes a direct call to DB8 and executes the putKind API call
• If the resource file is kind permission, then it makes a direct call to DB8 and executes the putPermission API call
• If the resource file is activity, then it makes a direct call to Activity Manager and registers the activities
• If the resource file is File Cache conf, then it makes a direct call to the File Cache and register the directories

After processing a resource file, configurator will remember, that the resource file has been processed and will not process that file on the next configurator directory scan.

Configurator Directory:

In the webOS platform there exists two different type of applications: webOS services and third party applications. Configurator use two locations for resource file processing: system and runtime.

System Configurator Directory:

This directory is used for searching for resource files when the configurator service starts. By default this directory is: /etc/palm/db

Runtime Configurator Directory:

After configurator has started, it provides a luna API for dynamic processing of resource files. For those API calls, configurator uses the Runtime Configurator Directory

The application type and hint location gives configurator the information where it should search for resource files. configurator determines the configurator directory using the logic below.

configurator directory = (location) + offset + (type) + (app_id) + (postfixdir)

The default values for the above parameters are listed in the table below.

Error handling:

If configurator cannot process API calls (internal error, bad params, no resources, etc) it always returns error in the following format:

• returnValue - if an error occurs, it  will contain false
• errorCode - code that indicates the cause of  the error
• errorText   -  text representation of the error code

Error codes and description are provided for each API call. For example, if the client calls the  scan API with bad parameter:

The above response indicates, that:

• returnValue: false - API call failed
• errorCode: -1000        - See API call scan for more details on error code -1000
• errorText: Application or service doesn't exist - A quick textual explanation of the error

rescan

run

scan

unconfigure