Difference between revisions of "Context XML Nodes"

From PresenceWiki
Jump to: navigation, search
(See Also)
(Context XML Nodes)
Line 1: Line 1:
 
== Context XML Nodes ==
 
== Context XML Nodes ==
  
These Nodes allow you to save and restore the [[Presence Context]]. This is exceptionally useful if you wish  to send the state of your Task to the Presence support staff for investigation, or if you want to preserve your data for later use.
+
These Nodes allow you to save and restore the [[Presence Context]]. This is exceptionally useful if you wish  to send the state of your Task to the Presence support staff for investigation, or if you want to preserve your data for later use. Another more useful feature of being able to export the context is parallel processing with multiple Presence Servers. Say you had a very large dataset to number crunch, you would simply chunk the data into separate parts and invoke the processing task(s) on separate servers.   
  
 
=== Write Context To XML ===
 
=== Write Context To XML ===
Line 18: Line 18:
  
 
Again you can specify a file name for the XML or a variable name (if the context was saved to a variable). Local and task variables can either be ignored, appended to the existing variables in the context (or ignored if present) or can replace all existing variables in the Context. Global variables can be ignored (do not read) or appended as Task variables.
 
Again you can specify a file name for the XML or a variable name (if the context was saved to a variable). Local and task variables can either be ignored, appended to the existing variables in the context (or ignored if present) or can replace all existing variables in the Context. Global variables can be ignored (do not read) or appended as Task variables.
 
  
 
== See Also ==
 
== See Also ==
  
 
{{DataAccess}}
 
{{DataAccess}}

Revision as of 05:43, 13 August 2015

Context XML Nodes

These Nodes allow you to save and restore the Presence Context. This is exceptionally useful if you wish to send the state of your Task to the Presence support staff for investigation, or if you want to preserve your data for later use. Another more useful feature of being able to export the context is parallel processing with multiple Presence Servers. Say you had a very large dataset to number crunch, you would simply chunk the data into separate parts and invoke the processing task(s) on separate servers.

Write Context To XML

This Node saves the current Presence Context to an XML file of your choosing.

http://www.international-presence.com/wikidocs/images/write_xml_dialog.png

Enter the file location in the field provided, or alternatively specify a variable to save the context to. You can opt to store global variables, task variables, local variables and the data table.

Read Context from XML

This Node loads the Presence Context from an XML file or from a variable.

http://www.international-presence.com/wikidocs/images/read_xml_dialog.png

Again you can specify a file name for the XML or a variable name (if the context was saved to a variable). Local and task variables can either be ignored, appended to the existing variables in the context (or ignored if present) or can replace all existing variables in the Context. Global variables can be ignored (do not read) or appended as Task variables.

See Also

Task Elements : Data Accesss Task Elements : Context XML Nodes

SQL Statement Nodes | Object Monitor Nodes | XML Query Nodes | Mail Scanner Nodes
Web Services Nodes | LDAP Query Nodes | JSON Node | Flat File Parser | Data Table Nodes | Variable Nodes
Transaction Control Nodes | Context XML Nodes


Task Elements | Resources