You create your page as any other pages. To cache your page, you just only add an attribute 'Cache' with value of 'true' for page xml element of your page configuration (*.pageconf file). For more custom cache, utilize two other attributes: CacheLifetime, and CacheKeys.
CacheLifetime attribute defines for how long time (in minutes), page cache is valid. CacheKeys attribute defines in what parameters (key), separate cache will be made for the same page. As for example, you have page to deliver user information that not change for a user but different from user to user, you can use user id for CacheKeys.
Here is for your example:
How to use dynamic value inside page configuration?
You can assign dynamic value to any parameters inside page configuration (*.pageconf file). You define your dynamic value using prefix 'fn::' for parameter value. As for example: fn::GetParam('context_id'). Any statement after prefix must can be evaluated and resulting a simple value.
Here is for your example:
Here is for your example:
How to create static page?
You create your page as any other pages. To change your page as static page, you just only add an attribute 'Static' with value of 'true' for page xml element of your page configuration (*.pageconf file).
If you want to use parameter for your static page, you can utilize cache inside page configuration. There are some attributes related to cached page: Cache, CacheLifetime, and CacheKeys.
Here is for your example:
If you want to use parameter for your static page, you can utilize cache inside page configuration. There are some attributes related to cached page: Cache, CacheLifetime, and CacheKeys.
Here is for your example:
How to link help context-sensitive with application?
You do link help context-sensitive with application inside of its configuration (*.pageconf file). Inside 'page' xml root will present a 'processor' xml element. For static security code, you define a HelpContext attribute to do. Other, you create HelpContext element inside PageSecurityCode element under 'processor' xml element.
See below for your example:
See below for your example:
How to use Remote Queue?
First you need to define a queue box with the type of Remote. Fill the queue server uri, username and password.
Now you can access queue as any other type of queue and completely transparent. You can put message, get message, delete message, and list messages using common way.
Here is an example of queue configuration using remote queue:
Now you can access queue as any other type of queue and completely transparent. You can put message, get message, delete message, and list messages using common way.
Here is an example of queue configuration using remote queue:
Steps for delivering SMS application
You need kannel SMS/WAP gateway to deliver SMS application using LightArmy. Here are your steps:
After all of that, you just start all of that manifests.
Now SMS service is available for serving.
If you want to change your service you may only change the last step and make/change code as appropriate or even no programming needed.
Note:
You can integrate SMS application with any other applications easily. You can shutting down computer using SMS as for example. Another example is sending you an SMS if a process is terminated. You can also sending SMS by email and so on.
- Install and configure Kannel SMS/WAP gateway. See Kannel documentation. You can use this for many services. Kannel website: http://www.kannel.org/
- Create Kannel interface for LightArmy and configure the settings. You can use this for many services.
Here is for an example: - Create manifest of kannel handler you what (direct reply, stomp, or queue)
If you choose stomp you need ActiveMQ queue server. ActiveMQ website: http://activemq.apache.org/
If you choose queue you need queue.
Here is for an example: - Create manifest of Kannel Service as appropriate. Use kannel_stompservice for stomp handler. Use kannel_queueservice for queue.
Here is for an example: - Create database for logging messages as you need.
- Create manifest of Kannel Sender as appropriate. Use kannel_stompsender for stomp handler. Use kannel_queuesender for queue.
Here is for an example: - If you want to know the status of delivery, create manifest of Kannel delivery status as appropriate. Use kannel_stompdeliverystatus for stomp handler. Use kannel_queuedeliverystatus for queue.
Here is for an example: - Create your responder for your service. Responder is the only program (code) you need to create for your specific purpose. You can use any available responder if appropriate.
Here is for an example:
After all of that, you just start all of that manifests.
Now SMS service is available for serving.
If you want to change your service you may only change the last step and make/change code as appropriate or even no programming needed.
Note:
You can integrate SMS application with any other applications easily. You can shutting down computer using SMS as for example. Another example is sending you an SMS if a process is terminated. You can also sending SMS by email and so on.
Using Parameterized component (Application)
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.
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:
Execute this manifest then.
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:
Subscribe to:
Posts (Atom)
Posts
