amigadave: add links

amigadave — Wed, 02 Feb 2011 10:20:51 GMT

add links

← Older revision		Revision as of 10:20, 2 February 2011
Line 2:		Line 2:

	Supported devices:		Supported devices:
-	* N900 (Fremantle)	+	* [[Nokia N900\|N900]] ([[Open development/Maemo roadmap/Fremantle\|Fremantle]])

	It supports the installation and modification of:		It supports the installation and modification of:
Line 212:		Line 212:
	A complete XML document...		A complete XML document...
	</pre>		</pre>
-	* <code>type</code>: Tells that it's an ~~xml~~ in-file.	+	* <code>type</code>: Tells that it's an XML in-file.
	* <code>target</code>: The file system path of the final output. If the file exists, it is also used as input.		* <code>target</code>: The file system path of the final output. If the file exists, it is also used as input.
	* <code>node_path</code>: It is an XML-path that defines the nodes in the in-file <code>DATA</code> section that will be added to the target file.		* <code>node_path</code>: It is an XML-path that defines the nodes in the in-file <code>DATA</code> section that will be added to the target file.

amigadave: wikify slightly

amigadave — Tue, 25 Jan 2011 11:01:27 GMT

wikify slightly

Show changes

amigadave: Category:Enterprise

amigadave — Tue, 01 Jun 2010 13:19:58 GMT

Category:Enterprise

← Older revision		Revision as of 13:19, 1 June 2010
Line 276:		Line 276:
	scripts, perl and python scripts, etc..		scripts, perl and python scripts, etc..
	Command lines cannot start with <code>"install:"</code> or <code>"uninstall:"</code>!		Command lines cannot start with <code>"install:"</code> or <code>"uninstall:"</code>!
		+
		+	[[Category:Enterprise]]

jpalko: EDG - Configurator

jpalko — Thu, 27 May 2010 12:01:11 GMT

EDG - Configurator

New page

Epconf helps to configure software components that are commonly used in
an enterprise environment (e.g. at companies).

Supported devices:
* N900 (Fremantle)

It supports the installation and modification of:
* Browser bookmark thumbnail images: thumbnail_* files.
* Wifi root certificates: <code>*.crt</code> files are used when authenticating via WLAN.
* GConf schemas: <code>*.schemas</code> files are registered with GConf.
* VCard files: <code>*.vcard</code> files are added to the contact list.
* Custom actions: Custom configuration can be done with epconftool in-files (<code>*.epin</code>).

The above mentioned input files are taken from the
<code>/usr/share/epconf-sets/SET</code> directory.

With epconf in-files you can configure:
* Arbitrary XML files
* GConf values
* Anything with script files

If an epconf in-file file matches <code>*.do-as-user.epin</code> then the
operations described by it will be executed as the user <code>'user'</code>.
For more information about in-files, please refer to epconftool.
See [[Enterprise_Configurator#epconftool|here]] for more details about epconftool in-files.

== Command line syntax ==

usage: epconf [debug] macro file_name ACTION SET[:GROUP[:ELEMENT]]...
debug Enables debug output.
macro Uses the specified macro file instead of the default one.
ACTION May be either install or uninstall.
SET Name of the configuration set to process.
It may be "all" which means "Process all the available set".
"all" cannot be mixed with other sets!
GROUP Can be one of
thumbnail: Process thumbnail_* thumbnails
crt: Process *.crt certificates
vcard: Process *.vcard vCards.
schemas: Process *.schemas GConf schemas
epin: Process *.epin epconftool in-files
If it is not given then all the groups are processed.
ELEMENT This can be used only with epin group.
Only the infile with the given name willbe processed.

The following example pulls the input files from <code>/usr/share/enterprise_pilot/my_set</code>:

epconf macro /home/user/macro.xml install my_set

The following example processes
* <code>best_in*.epin</code> from <code>/usr/share/enterprise_pilot/my_set</code> then
* <code>*.vcard</code> from <code>/usr/share/enterprise_pilot/your_set</code> and finally
* all supported files from <code>/usr/share/enterprise_pilot/their_set</code>:

epconf install my_set:epin:best_in your_set:vcard their_set

= epconftool =

Epconftool processes in-files that can be used for the creation of sophisticated configuration
scripts.

== Command line syntax ==

usage: epconftool [-f] [-s] [-d] { -x | -l } macro-file { -i | -u } in-files...

-i Install using the given input files.
-u Uninstall using the given input files.
-x Macro file in XML format
-l Macro file in plain key-value format
-f Force. If the process fails at one input file it goes on to the next one.
Without this option (default), a bad input file stops the entire process
and the subsequent input files are not processed.
-s Do simple macro substitution (a macro in a macro is not processed).
-d Print debug output to stderr.
Either -i or -u can be used. They cannot be mixed.

Built-in macros:
* <code>TIME_EPOCH</code>: The seconds elapsed since 1970.01.01 (see 'man 2 time').
* <code>INFILE_DIR</code>: Absolute path of the directory containing the in-file being processed.
* <code>MARKER</code>: This may be used e.g. in XML in-files. If a node_path node contains this as a text field anywhere in its subtree, then that node is removed during un-installation. Otherwise it is not removed!

== Macro file ==

The MACRO file contains usernames, passwords, etc.
Each value in this file has a key associated with it.
E.g., the WLAN_username key may have the value Jack.
The keys of the MACRO file can be used in in-files
as <code>%key_name%</code>. E.g., <code>%WLAN_username%</code>.

Two kinds of macro files are supported:
* XML
* Key-value list

=== XML ===

Let's take the following as an example:

<?xml version="1.0" encoding="UTF-8" ?>
<CONF>
<NAME>Joe Buck</NAME>
<REMOTE_ACCESS>
<LOGIN>joebuck</LOGIN>
</REMOTE_ACCESS>
<SIP>
<NAME>ext-joe.4.buck</NAME>
<PASS>98765876</PASS>
</SIP>
<WLAN>
<RESTAURANT>
<LOGIN>joejoe</LOGIN>
<PASS>buckybuck</PASS>
</RESTAURANT>
</WLAN>
<EMAIL>
<ADDRESS>ext-joe.4.buck@company.org</ADDRESS>
</EMAIL>
</CONF>

When using the above example macro file, the macro values are the text nodes
and the macro names are formed formed the tag names. For example, the
<code>%CONF_REMOTE_ACCESS_LOGIN%</code> macro refers to the value <code>"joebuck"</code>.

=== Key-value list ===

Let's take the following as an example:
"CONF_NAME" "Joe Buck"
"CONF_REMOTE_ACCESS_LOGIN" "joebuck"
"CONF_SIP_NAME" "ext-joe.4.buck"
"CONF_SIP_PASS" "98765876"
"CONF_WLAN_RESTAURANT_LOGIN" "joejoe"
"CONF_WLAN_RESTAURANT_PASS" "buckybuck"
"CONF_EMAIL_ADDRESS" "ext-joe.4.buck@company.org"

When using the above example macro file, the
<code>%CONF_REMOTE_ACCESS_LOGIN%</code> macro refers to the value "joebuck".

If the " (double quote) character appears in a key or a value, then it must be escaped. For example, "Norton said \"Howdy!\" and then he left.". Same for the \ (backslash) character. For example, "\\" represents a single backslash character.

== Input Template file (in-file) ==

In-files have the following general format:

[CONTROL]
# Comment
type:gconf|xml|shell
...

[DATA]
...
...%MACRO%...
...

The following lines are ignored:
* empty lines: lines with only whitespace or newline
* comments: lines whose first non-whitespace character is hash-mark ("#")

The tag (e.g., "type") and its value (e.g., "xml") in the <code>CONTROL</code> section are
separated by a single colon character.
The "type" tag is mandatory, and it must be the first non-ignored line in the
<code>CONTROL</code> section.

Every <code>%MACRO%</code> macro is replaced with the matching value from the <code>MACRO</code>
file during the installation/un-installation process. Macro substitution
is applied to the entire in-file (e.g. if the value of <code>MARKER</code> is "Hello Hippo" then <code>[CON%MARKER%TROL]</code> is replaced with
<code>[CONHello HippoTROL]</code>).

No recursive macro substitution is done. For example, if macro <code>%APPLE%</code> has
the value <code>"Hello %WORLD%"</code> then the <code>%WORLD"</code> is not considered as a macro
for substitution.

=== gconf ===

This in-file is used to add/remove gconf values.
See [2] for an example!

Syntax:
[CONTROL]
type:gconf

[DATA]
dir:/path/to/gconf/directory
behavior:type:key_name:value
behavior:type-list:key_name:[value,value,...]
...

The <code>"type"</code> tag tells that it's a gconf in-file.
The first line in the DATA section is the gconf directory that we want to configure.
Subsequent lines describe key/value pairs for gconf keys, whitespaces are
not allowed.
Value lists are also supported. In this case, the type name is suffixed
with the <code>"-list"</code> word and the value is a comma separated list enclosed in brackets.
The behavior can be one of the following:
* <code>replace</code>: If the key already exists, it is replaced.
* <code>merge</code>: Only for value lists. If the key already exists, it is merged with the specified one.
* <code>keepold</code>: If the key already exists, it is not changed.

Installation:
* In the <code>DATA</code> section, all the <code>%MACRO%</code> tags are replaced with the proper values.
* If the gconf directory <code>/path/to/gconf/directory</code> does not exist, it is created and populated with the provided key/value pairs.
* If the gconf directory <code>/path/to/gconf/directory</code> exists:
** If a provided key does not exist, it is created and its value is set.
** If a provided key exists, the action taken depends on the specified behavior.

Uninstallation:
* Simple values: The key is deleted.
* List values: If behavior is <code>"merge"</code> only the values given in the in-file are removed from the list. For other behaviors, the entire key is deleted.
* If after removing the keys, the entire <code>/path/to/gconf/directory</code> directory is deleted from gconf if it has become empty.

=== xml ===

This in-file is used to add/remove xml nodes in xml files, such as bookmarks
and Pidgin accounts.

Syntax:

[CONTROL]
type:xml
target:/path/to/the/xml/file/that/we/want/to/modify/or/create.xml
node_path:/xml/path/to/a/node
node_id_path:/xml/path/to/the/id/node /xml/path/to/another/id/node
remove_by:id|marker
if_exists:replace|keepold

[DATA]
A complete XML document...

* <code>type</code>: Tells that it's an xml in-file.
* <code>target</code>: The file system path of the final output. If the file exists, it is also used as input.
* <code>node_path</code>: It is an XML-path that defines the nodes in the in-file <code>DATA</code> section that will be added to the target file.
* <code>node_id_path</code>: It is a spaces and/or tabs separated list of XML-paths. These paths are combined and used as the primary-key to identify duplicate/existing entries.
* <code>if_exists</code>: Optional. Default is <code>"keepold"</code>. Defines the behavior for installation. When set to <code>"replace"</code>, existing nodes are replaced with the ones in the <code>DATA</code> section. When set to <code>"keepold"</code>, existing nodes are left intact.
* <code>remove_by</code>: Optional. Default is <code>"marker"</code>. Defines the behavior for uninstallation. When set to <code>"id"</code>, nodes that match the <code>node_path/node_id_path</code> are removed. When set to <code>"marker"</code>, nodes that contain the <code>%MARKER%</code> value in any of their (or children) attributes or children nodes, are removed.

All XML-paths use the X-Path syntax, see http://www.w3schools.com/XPath/default.asp, http://www.w3.org/TR/xpath20/, http://xmlsoft.org/html/libxml-xpath.html.

The <code>DATA</code> section contains a complete XML document.

Installation:
* In the <code>DATA</code> section, all the <code>%MACRO%</code> tags are replaced with the proper values.
* If the target file does not exist, it is created with the output of the previous steps, which is the processed <code>DATA</code> section (the un-macroed <code>DATA</code> section).
* If the target file exists:
** Based on the <code>node_id_path</code> and <code>node_path</code>, nodes from the processed <code>DATA</code> section are added to the target file. If a node already exists (based on <code>node_id_path</code>), the node is not added.

Uninstallation:
* If <code>remove_by</code> is <code>"marker"</code>: Delete every node (based on <code>node_path</code>), from the target file that has a text element anywhere in it with the <code>%MARKER%</code> macro. Therefore, you MUST add the <code>%MARKER%</code> macro somewhere in the nodes that you want to be removed later.
* If <code>remove_by</code> is <code>"id"</code>: Delete every node (based on <code>node_path</code>), from the target file that has the same id value (based on <code>node_id_path</code>) as the XML in the <code>DATA</code> section.

=== shell ===

Shell in-files are a flexible way to create custom configurator scripts.

Syntax:

[CONTROL]
type:shell

[DATA]
install:
commands
commands
commands
...

uninstall:
commands
commands
commands
...

The <code>DATA</code> section consists of and <code>"install"</code> and an <code>"uninstall"</code> subsection. The command
lines below the subsections constitute the content of the script. A script file
is created with that content and is executed. So basically, you can write, e.g., shell
scripts, perl and python scripts, etc..
Command lines cannot start with <code>"install:"</code> or <code>"uninstall:"</code>!

Enterprise Configurator - Revision history

amigadave: add links

amigadave: wikify slightly

amigadave: Category:Enterprise

jpalko: EDG - Configurator