Parameterized component (application) is component or application than can be customized using parameter(s). Behavior of component or application will be different for different parameter(s) in used.
Here is an example of parameterized component,CIISONLINE_FileEditor, and its usage on web application as an example:
parameterized component (FileEditor.php):
application #1:
manifest (AliasConfig.pageprop):
configuration (AliasConfig.pageconf):
application #2:
manifest (AutoIncludeConfig.pageprop):
configuration (AutoIncludeConfig.pageconf):
You can also use different style for that applications as needed.
What kind of contents the help file is ?
There are five files to render help: contents, index, keywords, name and overview.
You will access the contents using context id like this: context_id=<root help>.ManifestProcessMaint.Queen.email_autoresponse. Here are as that examples:
contents:
index:
keywords:
name:
overview:
You will access the contents using context id like this: context_id=<root help>.ManifestProcessMaint.Queen.email_autoresponse. Here are as that examples:
contents:
index:
keywords:
name:
overview:
Where I can found information of manifest parameters for a type?
LightArmy provides help context-sensitive for all applications inside. You just open an appropriate page and then click provided help context (question mark image). Appropriate help context will be displayed on new window.
Here is an example help for email_autoresponse:
Here is an example help for email_autoresponse:
How to sync data/files between site?
You must prepare your IPC first as explains before.
Then your only work as an example is defined manifest like this:
Execute this manifest then.
Then your only work as an example is defined manifest like this:
<?xml version="1.0" encoding="UTF-8"?>
<configuration id="file_synchronize">
<section name="core">
<!-- Process Configuration-->
<config name="process">
<config name="type">file_synchronize</config>
<config name="name"><![CDATA[FileSynchronizer]]></config>
<config name="description"><![CDATA[File Synchronizer]]></config>
<config name="start"></config>
<config name="end"></config>
</config>
<!--Wrapper Configuration-->
<config name="wrappers">
<config name="doc">
<config name="wrapper">fep</config>
<config name="server">http://localhost/document/Public/IPC.php</config>
<config name="user">admin</config>
<config name="password"></config>
<config name="md5">1</config>
</config>
<config name="admin">
<config name="wrapper">fep</config>
<config name="server">http://localhost/admin/Public/IPC.php</config>
<config name="user">admin</config>
<config name="password"></config>
<config name="md5">1</config>
</config>
</config>
<!--Proxy Configuration-->
<config name="proxy">
</config>
<!--Update Configuration-->
<config name="sync">
<config name="all">0</config>
<config name="directories">Extensions</config>
<config name="exceptions"></config>
<config name="files">index.php</config>
<config name="source">doc://</config>
<config name="destination">admin://Public/tmp/test/</config>
</config>
</section>
</configuration>
Execute this manifest then.
How to setup IPC?
Preparation for IPC is only in this configuration:
<?xml version="1.0" encoding="UTF-8"?>
<configuration id="ipc">
<section name="directories">
<config name="tmp">
<config name="name">tmp</config>
<config name="description">tmp</config>
<config name="dir">/tmp/</config>
<config name="protectdir"></config>
</config>
<config name="queue">
<config name="name">RemoteQueue</config>
<config name="description">RemoteQueue</config>
<config name="dir">/data/ext-01/Miscs/admin/RemoteQueue</config>
<config name="protectdir"></config>
</config>
</section>
</configuration>
How to setup Remote Queue server?
You can expose more than one queue to remote user. Your only work is configure your queue server setting and your queue.
Here is an example of server configuration:
Here is an example of server configuration:
<?xml version="1.0" encoding="UTF-8"?>
<configuration id="queuesvr">
<section name="core">
<config name="root">queue</config>
<config name="selector"></config>
</section>
<section name="queues">
<config name="SYSTEM">
<config name="description">?</config>
<config name="queue">
<config name="ref">QUEUEROUTER:SYSTEM:default</config>
</config>
<config name="selector">inbox</config>
<config name="parameters"></config>
</config>
<config name="SYSNOTIFY">
<config name="description">?</config>
<config name="queue">
<config name="ref">QUEUEROUTER:NOTIFYSUBSCRIBER::{subscriber}:default</config>
</config>
<config name="parameters">
<config name="subscriber">subscriber</config>
</config>
<config name="selector">subscriber</config>
</config>
<config name="SUBSCRIBER">
<config name="description">?</config>
<config name="queue">
<config name="router">
<config name="selectors">
<config name="subscriber">
<config name="selector" >
<config name="type" >Message</config>
<config name="unique-id" >subscriber</config>
</config>
<config name="box">
<config name="ref">QUEUEBOX:NOTIFYSUBSCRIBER:Sync:{subscriber}:subscriber:buffer</config>
</config>
</config>
</config>
</config>
</config>
<config name="parameters">
<config name="subscriber">subscriber</config>
</config>
<config name="selector">subscriber</config>
</config>
</section>
</configuration>
Full features CRUD database no more than 1 minute
You can create full features CRUD (create, read, update, and delete) database application in no more than 1 minute. Here are your steps to create such of application:
You can finishing step 2 and 3 in no more than 1 minute.
If you fast enough doing step 1 and 4, all steps can be finishing in ~ 1 minute.
Here is an example CRUD database application that need only 20 seconds for step 2 and 3:
Manifest in usage:







- Create your table database.
- Create manifest with process_type: gencode_dblist1,or gencode_dbmaint1, or gencode_dbmix1. Fill only the name of application and table you just created. (another process_type will be added countinually.)
- Execute the manifest.
- Install your application in container.
You can finishing step 2 and 3 in no more than 1 minute.
If you fast enough doing step 1 and 4, all steps can be finishing in ~ 1 minute.
Here is an example CRUD database application that need only 20 seconds for step 2 and 3:
Manifest in usage:
<?xml version="1.0" encoding="UTF-8"?>
<configuration id="mix">
<section name="core">
<!-- Process Configuration-->
<config name="process">
<config name="type">gencode_dbmix1</config>
<config name="name">GenCodeDbmix1TEST</config>
<config name="start"></config>
<config name="end"></config>
</config>
<!--Database Connection-->
<!--configuration-->
<config name="config">
<config name="public">0</config>
<config name="securitycodes">
<config name="default">
<config name="code">2</config>
<config name="name">dbmix1 TEST</config>
<config name="description">dbmix1 TEST</config>
</config>
</config>
</config>
<!--Query-->
<config name="query">
<config name="table">Test</config>
</config>
<!--Form-->
<config name="form">
<config name="search">
<config name="name">Test</config>
<config name="parameters">
<config name="ds_keywords">
<config name="type">like</config>
<config name="caption">KeywordsColumn</config>
<config name="column">1,0</config>
</config>
</config>
</config>
<config name="data">
<config name="frame">
<config name="maint">
</config>
</config>
</config>
</config>
<!--Output-->
<config name="output">
<config name="sign"><![CDATA[stevanus.dh@gmail.com]]></config>
</config>
<!--Item-->
<config name="item">
<config name="name">Test</config>
<config name="names">Tests</config>
</config>
<!--Class-->
<config name="class">
<config name="name">TestMix</config>
<config name="author">Stevanus DH</config>
<config name="package">TEST</config>
<config name="version">1.0.0</config>
<config name="copyright">Stevanus DH</config>
<config name="description">DESCR</config>
</config>
</section>
</configuration>








Subscribe to:
Posts (Atom)