GreenVulcano Wiki - User contributions [en]

https://gvwiki.greenvulcano.com/gvwiki/api.php?action=feedcontributions&feedformat=atom&user=M.deluca GreenVulcano Wiki - User contributions [en] 2026-04-13T08:37:45Z User contributions MediaWiki 1.31.7 https://gvwiki.greenvulcano.com/gvwiki/index.php?title=DBOInsert&diff=4493 DBOInsert 2016-01-26T17:23:04Z

<p>M.deluca: /* {{GVESB}} configuration */</p> <hr /> <div>==Description==<br /> <br /> The DBOInsert element represents the DBO optimized for insert operations.<br /> <br /> =={{GVESB}} configuration==<br /> [[File:DBOInsert.jpg|thumb|DBOInsert with VulCon]]<br /> DBOInsert allows you to make insert data into the database.<br /> <br /> Each statement is identified by the id.<br /> <br /> Actions can be defined in two ways:<br /> * Single execution of a statement<br /> * Complex execution guided by XML<br /> <br /> In the first modality any input is ignored and the code executes the first statement configured.<br /> <br /> In the second mode, the input XML (or its transformation) must contain the command (row) valid with all parameters (COL) required by the statement.<br /> <br /> It is used by [[DBOBuilder]]. <br /> <br /> The following table shows the DBOInsert attributes:<br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''dbo'''<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.datahandling.dbo.DBOInsert'''<br /> |-<br /> | name || required || DBOInsert name<br /> |-<br /> | transformation || optional || Transformation to be applied on the input data to obtain the internal XML commands.<br /> |-<br /> | force-mode || optional || (caller or xml2db): Force mode of the DBO, can be used in [[DBOBuilder]] whit more heterogeneous DBO. <br/> Mode:<br/> caller - inherit the mode of the caller<br/> xml2db - data entry mode<br /> |-<br /> | jdbc-connection-name || optional || DataSource JNDI name. <br/> Override connection defined in [[DBOBuilder]].<br /> |-<br /> | ignore-input || optional || (true or false): Tells the engine do not use the input data.<br /> |-<br /> | input-data || optional || The default is the value of @name-Input.<br/> Can be set as the @output-data of a preceding DBO to use its output as input.<br /> |-<br /> | output-data || optional || The default is the value of @name-Output.<br /> |}<br /> <div class="version_ge3.4.0.6"><br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | autogenerate-keys || optional || Tell the engine to handle auto generated keys at runtime (ex. autoincrement primary key fields). Default to false.<br /> |}<br /> </div><br /> <br /> <div class="version_ge3.5"><br /> It's possible to use positional parameters ''?'' notation or named parameters '':name'' notation into statement definition, but not mixed in the same statement.<br /> </div><br /> <br /> For example, given the following table:<br /> <syntaxhighlight lang="SQL"><br /> CREATE TABLE "TEST_GV"."TEST_TABLE_A" (<br /> "C1" VARCHAR2(50 CHAR),<br /> "C2" VARCHAR2(20 CHAR),<br /> "C3" NUMBER,<br /> "C4" NUMBER(10,3),<br /> "C5" NUMBER(5,4),<br /> "C6" DATE,<br /> "C7" TIMESTAMP (6)<br /> )<br /> </syntaxhighlight><br /> using the following input XML:<br /> <syntaxhighlight lang="XML"><br /> <ser:load xmlns:ser="http://www.gvtest.com/services"><br /> <ser:c1>text field</ser:c1><br /> <ser:c2>another text field</ser:c2><br /> <ser:c3>123456</ser:c3><br /> <ser:c4>123456.789</ser:c4><br /> <ser:c5>1.2345</ser:c5><br /> <ser:c6>2014-10-17T10:12:23</ser:c6><br /> <ser:c7>2014-10-17T10:13:00.123</ser:c7><br /> </ser:load><br /> </syntaxhighlight><br /> the following DBOInsert can load records into the table:<br /> <syntaxhighlight lang="XML"><br /> <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder"<br /> jdbc-connection-name="ds.test" name="Insert" type="dbobuilder"><br /> <DBOInsert class="it.greenvulcano.gvesb.datahandling.dbo.DBOInsert"<br /> name="Insert" transformation="Insert" type="dbo"><br /> <statement id="0" type="insert">insert into TEST_TABLE_A (C1, C2, C3, C4, C5, C6, C7)<br /> values (?, ?, ?, ?, ?, ?, ?)</statement><br /> </DBOInsert><br /> </DBOBuilder><br /> </syntaxhighlight><br /> using the following XSL transformation:<br /> <syntaxhighlight lang="XML"><br /> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="xsl fs java gvt" version="2.0"<br /> xmlns:fs="http://www.w3.org/2005/xpath-functions"<br /> xmlns:java="http://xml.apache.org/xalan/java"<br /> xmlns:gvt="http://www.gvtest.com/services"<br /> xmlns:xs="http://www.w3.org/2001/XMLSchema"><br /> <br /> <xsl:output encoding="utf-8" indent="yes" method="xml"/><br /> <br /> <xsl:template match="/gvt:load"><br /> <xsl:element name="RowSet"><br /> <xsl:element name="data"><br /> <xsl:element name="row"><br /> <xsl:element name="col"><br /> <xsl:value-of select="gvt:c1"/><br /> </xsl:element><br /> <xsl:element name="col"><br /> <xsl:value-of select="gvt:c2"/><br /> </xsl:element><br /> <xsl:element name="col"><br /> <xsl:attribute name="type">number</xsl:attribute><br /> <xsl:value-of select="gvt:c3"/><br /> </xsl:element><br /> <xsl:element name="col"><br /> <xsl:attribute name="type">float</xsl:attribute><br /> <xsl:attribute name="decimal-separator">.</xsl:attribute><br /> <xsl:attribute name="grouping-separator">,</xsl:attribute><br /> <xsl:value-of select="gvt:c4"/><br /> </xsl:element><br /> <xsl:element name="col"><br /> <xsl:attribute name="type">float</xsl:attribute><br /> <xsl:attribute name="decimal-separator">.</xsl:attribute><br /> <xsl:attribute name="grouping-separator">,</xsl:attribute><br /> <xsl:value-of select="gvt:c5"/><br /> </xsl:element><br /> <xsl:element name="col"><br /> <xsl:attribute name="type">timestamp</xsl:attribute><br /> <xsl:attribute name="format">yyyy-MM-dd'T'HH:mm:ss</xsl:attribute><br /> <xsl:value-of select="gvt:c6"/><br /> </xsl:element><br /> <xsl:element name="col"><br /> <xsl:attribute name="type">timestamp</xsl:attribute><br /> <xsl:attribute name="format">yyyy-MM-dd'T'HH:mm:ss.SSS</xsl:attribute><br /> <xsl:value-of select="gvt:c7"/><br /> </xsl:element><br /> </xsl:element><br /> </xsl:element><br /> </xsl:element><br /> </xsl:template><br /> </xsl:stylesheet><br /> </syntaxhighlight><br /> <br /> <div class="version_ge3.5"><br /> DBOInsert can also be used to make insert on a local or remote neo4j graph database. <br /> The statement must be written using the cypher (Cypher Query Language) language [http://neo4j.com/docs/stable/cypher-query-lang.html] as detailed in the following example:<br /> <syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?><br /> <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder"<br /> jdbc-connection-name="openejb:Resource/testDHDataSourceN4J" <br /> name="GVESB::TestInsertWithInputDataN4J" type="dbobuilder"><br /> <DBOInsert class="it.greenvulcano.gvesb.datahandling.dbo.DBOInsert" <br /> name="TestInsertWithInputDataN4J-InputData" type="dbo" ><br /> <statement id="0" type="insert">CREATE (Movie: Movie { title: {1}, released: {2}, tagline: {3} } )</statement><br /> </DBOInsert><br /> </DBOBuilder><br /> </syntaxhighlight><br /> As you can see in the above section you can make any queries insert achievable with cypher language using the parameters in input. <br /> </div><br /> <br /> Might contain the following sub-elements:<br /> * [[Description]]<br /> * [[DHVariables]]<br /> * [[statement]]</div>

M.deluca https://gvwiki.greenvulcano.com/gvwiki/index.php?title=DBOUpdate&diff=4492 DBOUpdate 2016-01-26T16:57:54Z

<p>M.deluca: /* {{GVESB}} configuration */</p> <hr /> <div>==Description==<br /> <br /> The DBOUpdate element represents the DBO optimized for update operations.<br /> <br /> =={{GVESB}} configuration==<br /> [[File:DBOUpdate.jpg|thumb|DBOUpdate with VulCon]]<br /> DBOUpdate allows you to update data into the database.<br /> <br /> Each statement is identified by the id.<br /> <br /> Actions can be defined in two ways:<br /> * Single execution of a statement<br /> * Complex execution guided by XML<br /> <br /> In the first modality any input is ignored and the code executes the first statement configured.<br /> <br /> In the second mode, the input XML (or its transformation) must contain the command (row) valid with all parameters (COL) required by the statement.<br /> <br /> It is used by [[DBOBuilder]]. <br /> <br /> The following table shows the DBOUpdate attributes:<br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''dbo'''<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.datahandling.dbo.DBOUpdate'''<br /> |-<br /> | name || required || DBOUpdate name<br /> |-<br /> | transformation || required || Transformation to be applied on the input data to obtain the internal XML commands.<br /> |-<br /> | force-mode || optional || (caller or xml2db) Force mode of the [[DBOBuilder#DBOs|DBO]], can be used in [[DBOBuilder]] whit more heterogeneous [[DBOBuilder#DBOs|DBOs]]. <br/> Mode:<br/> caller - inherit the mode of the caller<br/> xml2db - data entry mode<br /> |-<br /> | jdbc-connection-name || optional || DataSource JNDI name. <br/> Override connection defined in [[DBOBuilder]].<br /> |-<br /> | ignore-input || optional || (true or false) Tells the engine do not use the input data.<br /> |-<br /> | input-data || optional || The default is the value of @name-Input.<br/> Can be set as the @output-data of a preceding [[DBOBuilder#DBOs|DBO]] to use its output as input.<br /> |-<br /> | output-data || optional || The default is the value of @name-Output.<br /> |}<br /> <div class="version_ge3.4.0.6"><br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | autogenerate-keys || optional || Tell the engine to handle auto generated keys at runtime (ex. autoincrement primary key fields). Default to false.<br /> |}<br /> </div><br /> <div class="version_ge3.5"><br /> It's possible to use positional parameters ''?'' notation or named parameters '':name'' notation into statement definition, but not mixed in the same statement.<br /> </div><br /> <br /> For example, given the following table:<br /> <syntaxhighlight lang="SQL"><br /> CREATE TABLE "TEST_GV"."CREDIT_CARD" (<br /> "ID" NUMBER NOT NULL,<br /> "ID_OWNER" NUMBER NOT NULL,<br /> "CNUMBER" VARCHAR2(20 CHAR) NOT NULL,<br /> "CREDIT" NUMBER(15,5) NOT NULL,<br /> "ENABLED" VARCHAR2(1 CHAR) NOT NULL,<br /> CONSTRAINT "CCRED_PK" PRIMARY KEY ("ID")<br /> )<br /> </syntaxhighlight><br /> the following input XML:<br /> <syntaxhighlight lang="XML"><br /> <ser:Pay xmlns:ser="http://www.credit.com/services"><br /> <ser:cnumber>1111222233334444</ser:cnumber><br /> <ser:amount>10</ser:amount><br /> </ser:Pay><br /> </syntaxhighlight><br /> the following DBOUpdate can update the table:<br /> <syntaxhighlight lang="XML"><br /> <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder"<br /> jdbc-connection-name="gv_test" name="CCardPay" type="dbobuilder"><br /> <DHVariables><br /> <DHVariable name="decimal-separator" value="."/><br /> <DHVariable name="grouping-separator" value=","/><br /> <DHVariable name="format" value="#0.00"/><br /> </DHVariables><br /> <DBOUpdate class="it.greenvulcano.gvesb.datahandling.dbo.DBOUpdate"<br /> name="CCardPay" transformation="CCardPay" type="dbo"><br /> <statement id="1" type="update"><![CDATA[update CREDIT_CARD set CREDIT= CREDIT - ?<br /> where CNUMBER=?<br /> and ENABLED='Y'<br /> and CREDIT >= ?]]></statement><br /> </DBOUpdate><br /> </DBOBuilder><br /> </syntaxhighlight><br /> through the following XSL transformation:<br /> <syntaxhighlight lang="XML"><br /> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="xsl int fs" version="2.0"<br /> xmlns:fs="http://www.w3.org/2005/xpath-functions"<br /> xmlns:int="http://www.credit.com/services"<br /> xmlns:xs="http://www.w3.org/2001/XMLSchema"><br /> <xsl:output encoding="utf-8" indent="yes" method="xml"/><br /> <xsl:template match="/"><br /> <xsl:element name="RowSet"><br /> <xsl:apply-templates select="/int:Pay"/><br /> </xsl:element><br /> </xsl:template><br /> <xsl:template match="/int:Pay"><br /> <xsl:element name="data"><br /> <xsl:element name="row"><br /> <xsl:attribute name="id">1</xsl:attribute><br /> <xsl:element name="col"><br /> <xsl:attribute name="type">float</xsl:attribute><br /> <xsl:value-of select="int:amount"/><br /> </xsl:element><br /> <xsl:element name="col"><br /> <xsl:value-of select="int:cnumber"/><br /> </xsl:element><br /> <xsl:element name="col"><br /> <xsl:attribute name="type">float</xsl:attribute><br /> <xsl:value-of select="int:amount"/><br /> </xsl:element><br /> </xsl:element><br /> </xsl:element><br /> </xsl:template><br /> </xsl:stylesheet><br /> </syntaxhighlight><br /> <br /> <div class="version_ge3.5"><br /> Using named parameters, the following DBOUpdate can update the table:<br /> <syntaxhighlight lang="XML"><br /> <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder"<br /> jdbc-connection-name="gv_test" name="CCardPay" type="dbobuilder"><br /> <DHVariables><br /> <DHVariable name="decimal-separator" value="."/><br /> <DHVariable name="grouping-separator" value=","/><br /> <DHVariable name="format" value="#0.00"/><br /> </DHVariables><br /> <DBOUpdate class="it.greenvulcano.gvesb.datahandling.dbo.DBOUpdate"<br /> name="CCardPay" transformation="CCardPay" type="dbo"><br /> <statement id="1" type="update"><![CDATA[update CREDIT_CARD set CREDIT= CREDIT - :amount<br /> where CNUMBER=:cnumber<br /> and ENABLED='Y'<br /> and CREDIT >= :amount]]></statement><br /> </DBOUpdate><br /> </DBOBuilder><br /> </syntaxhighlight><br /> through the following XSL transformation:<br /> <syntaxhighlight lang="XML"><br /> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="xsl fs" version="2.0"<br /> xmlns:fs="http://www.w3.org/2005/xpath-functions"<br /> xmlns:int="http://www.credit.com/services"<br /> xmlns:ns0="http://www.greenvulcano.com/database"<br /> xmlns:xs="http://www.w3.org/2001/XMLSchema"<br /> xmlns:xsd="http://www.w3.org/2001/XMLSchema"><br /> <xsl:output encoding="utf-8" indent="yes" method="xml"/><br /> <xsl:template match="/"><br /> <xsl:element name="RowSet" namespace="http://www.greenvulcano.com/database"><br /> <xsl:element name="data" namespace="http://www.greenvulcano.com/database"><br /> <xsl:apply-templates select="/int:Pay"/><br /> </xsl:element><br /> </xsl:element><br /> </xsl:template><br /> <xsl:template match="/int:Pay"><br /> <xsl:element name="row" namespace="http://www.greenvulcano.com/database"><br /> <xsl:attribute name="id">1</xsl:attribute><br /> <xsl:element name="cnumber" namespace="http://www.greenvulcano.com/database"><br /> <xsl:attribute name="type">float</xsl:attribute><br /> <xsl:value-of select="int:cnumber"/><br /> </xsl:element><br /> <xsl:element name="amount" namespace="http://www.greenvulcano.com/database"><br /> <xsl:attribute name="type">float</xsl:attribute><br /> <xsl:value-of select="int:amount"/><br /> </xsl:element><br /> </xsl:element><br /> </xsl:template><br /> </xsl:stylesheet><br /> </syntaxhighlight><br /> </div><br /> <br /> <div class="version_ge3.5"><br /> DBOUpdate can be used to make update on a local or remote neo4j graph database. <br /> The statement must be write using the cypher (Cypher Query Language) language [http://neo4j.com/docs/stable/cypher-query-lang.html] as detailed in the following example:<br /> <syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?><br /> <?xml version="1.0" encoding="UTF-8"?><br /> <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder" <br /> jdbc-connection-name="openejb:Resource/testDHDataSourceN4J" <br /> name="GVESB::TestUpdateWithInputDataN4J" type="dbobuilder"><br /> <DBOUpdate class="it.greenvulcano.gvesb.datahandling.dbo.DBOUpdate" <br /> name="TestUpdateWithInputDataN4J-InputData"<br /> type="dbo"><br /> <statement id="0" type="update">MATCH (n { title: {1} }) SET n.tagline = {2}</statement><br /> </DBOUpdate><br /> </DBOBuilder><br /> </syntaxhighlight><br /> As you can see in the above section you can make any queries update achievable with cypher language using the parameters in input. <br /> <br /> This DBO can be used also to delete elements present in the neo4j graph database usign the keyword and the related cypher language syntax.<br /> In the following example is shown a cypher query used to delete all nodes and the related relationships that meet the MATCH condition:<br /> <syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?><br /> <?xml version="1.0" encoding="UTF-8"?><br /> <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder"<br /> jdbc-connection-name="openejb:Resource/testDHDataSourceN4J" <br /> name="GVESB::TestDeleteWithPropsN4J" type="dbobuilder"><br /> <DBOUpdate class="it.greenvulcano.gvesb.datahandling.dbo.DBOUpdate" <br /> name="TestDeleteWithPropsN4J-Props" type="dbo" ><br /> <statement id="0" type="update">MATCH (n { title: '@{{TITLE_INPUT}}' }) OPTIONAL MATCH (n)-[r]-() DELETE n</statement><br /> </DBOUpdate><br /> </DBOBuilder><br /> </syntaxhighlight><br /> <br /> </div><br /> <br /> DBOUpdate might contain the following sub-elements:<br /> * [[Description]]<br /> * [[DHVariables]]<br /> * [[statement]]</div>

M.deluca https://gvwiki.greenvulcano.com/gvwiki/index.php?title=DBOUpdate&diff=4491 DBOUpdate 2016-01-25T22:53:55Z

<p>M.deluca: /* {{GVESB}} configuration */</p> <hr /> <div>==Description==<br /> <br /> The DBOUpdate element represents the DBO optimized for update operations.<br /> <br /> =={{GVESB}} configuration==<br /> [[File:DBOUpdate.jpg|thumb|DBOUpdate with VulCon]]<br /> DBOUpdate allows you to update data into the database.<br /> <br /> Each statement is identified by the id.<br /> <br /> Actions can be defined in two ways:<br /> * Single execution of a statement<br /> * Complex execution guided by XML<br /> <br /> In the first modality any input is ignored and the code executes the first statement configured.<br /> <br /> In the second mode, the input XML (or its transformation) must contain the command (row) valid with all parameters (COL) required by the statement.<br /> <br /> It is used by [[DBOBuilder]]. <br /> <br /> The following table shows the DBOUpdate attributes:<br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''dbo'''<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.datahandling.dbo.DBOUpdate'''<br /> |-<br /> | name || required || DBOUpdate name<br /> |-<br /> | transformation || required || Transformation to be applied on the input data to obtain the internal XML commands.<br /> |-<br /> | force-mode || optional || (caller or xml2db) Force mode of the [[DBOBuilder#DBOs|DBO]], can be used in [[DBOBuilder]] whit more heterogeneous [[DBOBuilder#DBOs|DBOs]]. <br/> Mode:<br/> caller - inherit the mode of the caller<br/> xml2db - data entry mode<br /> |-<br /> | jdbc-connection-name || optional || DataSource JNDI name. <br/> Override connection defined in [[DBOBuilder]].<br /> |-<br /> | ignore-input || optional || (true or false) Tells the engine do not use the input data.<br /> |-<br /> | input-data || optional || The default is the value of @name-Input.<br/> Can be set as the @output-data of a preceding [[DBOBuilder#DBOs|DBO]] to use its output as input.<br /> |-<br /> | output-data || optional || The default is the value of @name-Output.<br /> |}<br /> <div class="version_ge3.4.0.6"><br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | autogenerate-keys || optional || Tell the engine to handle auto generated keys at runtime (ex. autoincrement primary key fields). Default to false.<br /> |}<br /> </div><br /> <div class="version_ge3.5"><br /> It's possible to use positional parameters ''?'' notation or named parameters '':name'' notation into statement definition, but not mixed in the same statement.<br /> </div><br /> <br /> For example, given the following table:<br /> <syntaxhighlight lang="SQL"><br /> CREATE TABLE "TEST_GV"."CREDIT_CARD" (<br /> "ID" NUMBER NOT NULL,<br /> "ID_OWNER" NUMBER NOT NULL,<br /> "CNUMBER" VARCHAR2(20 CHAR) NOT NULL,<br /> "CREDIT" NUMBER(15,5) NOT NULL,<br /> "ENABLED" VARCHAR2(1 CHAR) NOT NULL,<br /> CONSTRAINT "CCRED_PK" PRIMARY KEY ("ID")<br /> )<br /> </syntaxhighlight><br /> the following input XML:<br /> <syntaxhighlight lang="XML"><br /> <ser:Pay xmlns:ser="http://www.credit.com/services"><br /> <ser:cnumber>1111222233334444</ser:cnumber><br /> <ser:amount>10</ser:amount><br /> </ser:Pay><br /> </syntaxhighlight><br /> the following DBOUpdate can update the table:<br /> <syntaxhighlight lang="XML"><br /> <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder"<br /> jdbc-connection-name="gv_test" name="CCardPay" type="dbobuilder"><br /> <DHVariables><br /> <DHVariable name="decimal-separator" value="."/><br /> <DHVariable name="grouping-separator" value=","/><br /> <DHVariable name="format" value="#0.00"/><br /> </DHVariables><br /> <DBOUpdate class="it.greenvulcano.gvesb.datahandling.dbo.DBOUpdate"<br /> name="CCardPay" transformation="CCardPay" type="dbo"><br /> <statement id="1" type="update"><![CDATA[update CREDIT_CARD set CREDIT= CREDIT - ?<br /> where CNUMBER=?<br /> and ENABLED='Y'<br /> and CREDIT >= ?]]></statement><br /> </DBOUpdate><br /> </DBOBuilder><br /> </syntaxhighlight><br /> through the following XSL transformation:<br /> <syntaxhighlight lang="XML"><br /> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="xsl int fs" version="2.0"<br /> xmlns:fs="http://www.w3.org/2005/xpath-functions"<br /> xmlns:int="http://www.credit.com/services"<br /> xmlns:xs="http://www.w3.org/2001/XMLSchema"><br /> <xsl:output encoding="utf-8" indent="yes" method="xml"/><br /> <xsl:template match="/"><br /> <xsl:element name="RowSet"><br /> <xsl:apply-templates select="/int:Pay"/><br /> </xsl:element><br /> </xsl:template><br /> <xsl:template match="/int:Pay"><br /> <xsl:element name="data"><br /> <xsl:element name="row"><br /> <xsl:attribute name="id">1</xsl:attribute><br /> <xsl:element name="col"><br /> <xsl:attribute name="type">float</xsl:attribute><br /> <xsl:value-of select="int:amount"/><br /> </xsl:element><br /> <xsl:element name="col"><br /> <xsl:value-of select="int:cnumber"/><br /> </xsl:element><br /> <xsl:element name="col"><br /> <xsl:attribute name="type">float</xsl:attribute><br /> <xsl:value-of select="int:amount"/><br /> </xsl:element><br /> </xsl:element><br /> </xsl:element><br /> </xsl:template><br /> </xsl:stylesheet><br /> </syntaxhighlight><br /> <br /> <div class="version_ge3.5"><br /> Using named parameters, the following DBOUpdate can update the table:<br /> <syntaxhighlight lang="XML"><br /> <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder"<br /> jdbc-connection-name="gv_test" name="CCardPay" type="dbobuilder"><br /> <DHVariables><br /> <DHVariable name="decimal-separator" value="."/><br /> <DHVariable name="grouping-separator" value=","/><br /> <DHVariable name="format" value="#0.00"/><br /> </DHVariables><br /> <DBOUpdate class="it.greenvulcano.gvesb.datahandling.dbo.DBOUpdate"<br /> name="CCardPay" transformation="CCardPay" type="dbo"><br /> <statement id="1" type="update"><![CDATA[update CREDIT_CARD set CREDIT= CREDIT - :amount<br /> where CNUMBER=:cnumber<br /> and ENABLED='Y'<br /> and CREDIT >= :amount]]></statement><br /> </DBOUpdate><br /> </DBOBuilder><br /> </syntaxhighlight><br /> through the following XSL transformation:<br /> <syntaxhighlight lang="XML"><br /> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="xsl fs" version="2.0"<br /> xmlns:fs="http://www.w3.org/2005/xpath-functions"<br /> xmlns:int="http://www.credit.com/services"<br /> xmlns:ns0="http://www.greenvulcano.com/database"<br /> xmlns:xs="http://www.w3.org/2001/XMLSchema"<br /> xmlns:xsd="http://www.w3.org/2001/XMLSchema"><br /> <xsl:output encoding="utf-8" indent="yes" method="xml"/><br /> <xsl:template match="/"><br /> <xsl:element name="RowSet" namespace="http://www.greenvulcano.com/database"><br /> <xsl:element name="data" namespace="http://www.greenvulcano.com/database"><br /> <xsl:apply-templates select="/int:Pay"/><br /> </xsl:element><br /> </xsl:element><br /> </xsl:template><br /> <xsl:template match="/int:Pay"><br /> <xsl:element name="row" namespace="http://www.greenvulcano.com/database"><br /> <xsl:attribute name="id">1</xsl:attribute><br /> <xsl:element name="cnumber" namespace="http://www.greenvulcano.com/database"><br /> <xsl:attribute name="type">float</xsl:attribute><br /> <xsl:value-of select="int:cnumber"/><br /> </xsl:element><br /> <xsl:element name="amount" namespace="http://www.greenvulcano.com/database"><br /> <xsl:attribute name="type">float</xsl:attribute><br /> <xsl:value-of select="int:amount"/><br /> </xsl:element><br /> </xsl:element><br /> </xsl:template><br /> </xsl:stylesheet><br /> </syntaxhighlight><br /> </div><br /> <br /> <div class="version_ge3.5"><br /> DBOUpdate can be used to make update on a local or remote neo4j graph database. <br /> The statement must be write using the cypher (Cypher Query Language) language [http://neo4j.com/docs/stable/cypher-query-lang.html] as detailed in the following example:<br /> <syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?><br /> <?xml version="1.0" encoding="UTF-8"?><br /> <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder" <br /> jdbc-connection-name="openejb:Resource/testDHDataSourceN4J" <br /> name="GVESB::TestUpdateWithInputDataN4J" type="dbobuilder"><br /> <DBOUpdate class="it.greenvulcano.gvesb.datahandling.dbo.DBOUpdate" <br /> name="TestUpdateWithInputDataN4J-InputData"<br /> type="dbo"><br /> <statement id="0" type="update">MATCH (n { title: {1} }) SET n.tagline = {2}</statement><br /> </DBOUpdate><br /> </DBOBuilder><br /> </syntaxhighlight><br /> As you can see in the above section you can make any queries update achievable with cypher language using the parameters in input. <br /> <br /> This DBO can be used also to delete elements present in the neo4j graph database usign the keyword and the related syntax of the cypher language.<br /> In the following example is shown a cypher query used to delete all nodes that meet the MATCH conditions and the related relationship:<br /> <syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?><br /> <?xml version="1.0" encoding="UTF-8"?><br /> <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder"<br /> jdbc-connection-name="openejb:Resource/testDHDataSourceN4J" <br /> name="GVESB::TestDeleteWithPropsN4J" type="dbobuilder"><br /> <DBOUpdate class="it.greenvulcano.gvesb.datahandling.dbo.DBOUpdate" <br /> name="TestDeleteWithPropsN4J-Props" type="dbo" ><br /> <statement id="0" type="update">MATCH (n { title: '@{{TITLE_INPUT}}' }) OPTIONAL MATCH (n)-[r]-() DELETE n</statement><br /> </DBOUpdate><br /> </DBOBuilder><br /> </syntaxhighlight><br /> <br /> </div><br /> <br /> DBOUpdate might contain the following sub-elements:<br /> * [[Description]]<br /> * [[DHVariables]]<br /> * [[statement]]</div>

M.deluca https://gvwiki.greenvulcano.com/gvwiki/index.php?title=DBOUpdate&diff=4490 DBOUpdate 2016-01-25T22:45:15Z

<p>M.deluca: /* {{GVESB}} configuration */</p> <hr /> <div>==Description==<br /> <br /> The DBOUpdate element represents the DBO optimized for update operations.<br /> <br /> =={{GVESB}} configuration==<br /> [[File:DBOUpdate.jpg|thumb|DBOUpdate with VulCon]]<br /> DBOUpdate allows you to update data into the database.<br /> <br /> Each statement is identified by the id.<br /> <br /> Actions can be defined in two ways:<br /> * Single execution of a statement<br /> * Complex execution guided by XML<br /> <br /> In the first modality any input is ignored and the code executes the first statement configured.<br /> <br /> In the second mode, the input XML (or its transformation) must contain the command (row) valid with all parameters (COL) required by the statement.<br /> <br /> It is used by [[DBOBuilder]]. <br /> <br /> The following table shows the DBOUpdate attributes:<br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''dbo'''<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.datahandling.dbo.DBOUpdate'''<br /> |-<br /> | name || required || DBOUpdate name<br /> |-<br /> | transformation || required || Transformation to be applied on the input data to obtain the internal XML commands.<br /> |-<br /> | force-mode || optional || (caller or xml2db) Force mode of the [[DBOBuilder#DBOs|DBO]], can be used in [[DBOBuilder]] whit more heterogeneous [[DBOBuilder#DBOs|DBOs]]. <br/> Mode:<br/> caller - inherit the mode of the caller<br/> xml2db - data entry mode<br /> |-<br /> | jdbc-connection-name || optional || DataSource JNDI name. <br/> Override connection defined in [[DBOBuilder]].<br /> |-<br /> | ignore-input || optional || (true or false) Tells the engine do not use the input data.<br /> |-<br /> | input-data || optional || The default is the value of @name-Input.<br/> Can be set as the @output-data of a preceding [[DBOBuilder#DBOs|DBO]] to use its output as input.<br /> |-<br /> | output-data || optional || The default is the value of @name-Output.<br /> |}<br /> <div class="version_ge3.4.0.6"><br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | autogenerate-keys || optional || Tell the engine to handle auto generated keys at runtime (ex. autoincrement primary key fields). Default to false.<br /> |}<br /> </div><br /> <div class="version_ge3.5"><br /> It's possible to use positional parameters ''?'' notation or named parameters '':name'' notation into statement definition, but not mixed in the same statement.<br /> </div><br /> <br /> For example, given the following table:<br /> <syntaxhighlight lang="SQL"><br /> CREATE TABLE "TEST_GV"."CREDIT_CARD" (<br /> "ID" NUMBER NOT NULL,<br /> "ID_OWNER" NUMBER NOT NULL,<br /> "CNUMBER" VARCHAR2(20 CHAR) NOT NULL,<br /> "CREDIT" NUMBER(15,5) NOT NULL,<br /> "ENABLED" VARCHAR2(1 CHAR) NOT NULL,<br /> CONSTRAINT "CCRED_PK" PRIMARY KEY ("ID")<br /> )<br /> </syntaxhighlight><br /> the following input XML:<br /> <syntaxhighlight lang="XML"><br /> <ser:Pay xmlns:ser="http://www.credit.com/services"><br /> <ser:cnumber>1111222233334444</ser:cnumber><br /> <ser:amount>10</ser:amount><br /> </ser:Pay><br /> </syntaxhighlight><br /> the following DBOUpdate can update the table:<br /> <syntaxhighlight lang="XML"><br /> <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder"<br /> jdbc-connection-name="gv_test" name="CCardPay" type="dbobuilder"><br /> <DHVariables><br /> <DHVariable name="decimal-separator" value="."/><br /> <DHVariable name="grouping-separator" value=","/><br /> <DHVariable name="format" value="#0.00"/><br /> </DHVariables><br /> <DBOUpdate class="it.greenvulcano.gvesb.datahandling.dbo.DBOUpdate"<br /> name="CCardPay" transformation="CCardPay" type="dbo"><br /> <statement id="1" type="update"><![CDATA[update CREDIT_CARD set CREDIT= CREDIT - ?<br /> where CNUMBER=?<br /> and ENABLED='Y'<br /> and CREDIT >= ?]]></statement><br /> </DBOUpdate><br /> </DBOBuilder><br /> </syntaxhighlight><br /> through the following XSL transformation:<br /> <syntaxhighlight lang="XML"><br /> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="xsl int fs" version="2.0"<br /> xmlns:fs="http://www.w3.org/2005/xpath-functions"<br /> xmlns:int="http://www.credit.com/services"<br /> xmlns:xs="http://www.w3.org/2001/XMLSchema"><br /> <xsl:output encoding="utf-8" indent="yes" method="xml"/><br /> <xsl:template match="/"><br /> <xsl:element name="RowSet"><br /> <xsl:apply-templates select="/int:Pay"/><br /> </xsl:element><br /> </xsl:template><br /> <xsl:template match="/int:Pay"><br /> <xsl:element name="data"><br /> <xsl:element name="row"><br /> <xsl:attribute name="id">1</xsl:attribute><br /> <xsl:element name="col"><br /> <xsl:attribute name="type">float</xsl:attribute><br /> <xsl:value-of select="int:amount"/><br /> </xsl:element><br /> <xsl:element name="col"><br /> <xsl:value-of select="int:cnumber"/><br /> </xsl:element><br /> <xsl:element name="col"><br /> <xsl:attribute name="type">float</xsl:attribute><br /> <xsl:value-of select="int:amount"/><br /> </xsl:element><br /> </xsl:element><br /> </xsl:element><br /> </xsl:template><br /> </xsl:stylesheet><br /> </syntaxhighlight><br /> <br /> <div class="version_ge3.5"><br /> Using named parameters, the following DBOUpdate can update the table:<br /> <syntaxhighlight lang="XML"><br /> <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder"<br /> jdbc-connection-name="gv_test" name="CCardPay" type="dbobuilder"><br /> <DHVariables><br /> <DHVariable name="decimal-separator" value="."/><br /> <DHVariable name="grouping-separator" value=","/><br /> <DHVariable name="format" value="#0.00"/><br /> </DHVariables><br /> <DBOUpdate class="it.greenvulcano.gvesb.datahandling.dbo.DBOUpdate"<br /> name="CCardPay" transformation="CCardPay" type="dbo"><br /> <statement id="1" type="update"><![CDATA[update CREDIT_CARD set CREDIT= CREDIT - :amount<br /> where CNUMBER=:cnumber<br /> and ENABLED='Y'<br /> and CREDIT >= :amount]]></statement><br /> </DBOUpdate><br /> </DBOBuilder><br /> </syntaxhighlight><br /> through the following XSL transformation:<br /> <syntaxhighlight lang="XML"><br /> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="xsl fs" version="2.0"<br /> xmlns:fs="http://www.w3.org/2005/xpath-functions"<br /> xmlns:int="http://www.credit.com/services"<br /> xmlns:ns0="http://www.greenvulcano.com/database"<br /> xmlns:xs="http://www.w3.org/2001/XMLSchema"<br /> xmlns:xsd="http://www.w3.org/2001/XMLSchema"><br /> <xsl:output encoding="utf-8" indent="yes" method="xml"/><br /> <xsl:template match="/"><br /> <xsl:element name="RowSet" namespace="http://www.greenvulcano.com/database"><br /> <xsl:element name="data" namespace="http://www.greenvulcano.com/database"><br /> <xsl:apply-templates select="/int:Pay"/><br /> </xsl:element><br /> </xsl:element><br /> </xsl:template><br /> <xsl:template match="/int:Pay"><br /> <xsl:element name="row" namespace="http://www.greenvulcano.com/database"><br /> <xsl:attribute name="id">1</xsl:attribute><br /> <xsl:element name="cnumber" namespace="http://www.greenvulcano.com/database"><br /> <xsl:attribute name="type">float</xsl:attribute><br /> <xsl:value-of select="int:cnumber"/><br /> </xsl:element><br /> <xsl:element name="amount" namespace="http://www.greenvulcano.com/database"><br /> <xsl:attribute name="type">float</xsl:attribute><br /> <xsl:value-of select="int:amount"/><br /> </xsl:element><br /> </xsl:element><br /> </xsl:template><br /> </xsl:stylesheet><br /> </syntaxhighlight><br /> </div><br /> <br /> <div class="version_ge3.5"><br /> DBOUpdate can be used to make update on a local or remote neo4j graph database. <br /> The statement must be write using the cypher (Cypher Query Language) language [http://neo4j.com/docs/stable/cypher-query-lang.html] as detailed in the following example:<br /> <syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?><br /> <?xml version="1.0" encoding="UTF-8"?><br /> <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder" <br /> jdbc-connection-name="openejb:Resource/testDHDataSourceN4J" <br /> name="GVESB::TestUpdateWithInputDataN4J" type="dbobuilder"><br /> <DBOUpdate class="it.greenvulcano.gvesb.datahandling.dbo.DBOUpdate" <br /> name="TestUpdateWithInputDataN4J-InputData"<br /> type="dbo"><br /> <statement id="0" type="update">MATCH (n { title: {1} }) SET n.tagline = {2}</statement><br /> </DBOUpdate><br /> </DBOBuilder><br /> </syntaxhighlight><br /> As you can see in the above section you can make any queries update achievable with cypher language using the parameters in input. <br /> <br /> </div><br /> <br /> DBOUpdate might contain the following sub-elements:<br /> * [[Description]]<br /> * [[DHVariables]]<br /> * [[statement]]</div>

M.deluca https://gvwiki.greenvulcano.com/gvwiki/index.php?title=DBOSelect&diff=4489 DBOSelect 2016-01-25T20:33:53Z

<p>M.deluca: /* {{GVESB}} configuration */</p> <hr /> <div>==Description==<br /> <br /> The DBOSelect element represents the DBO optimized for select operations.<br /> <br /> =={{GVESB}} configuration==<br /> [[File:DBOSelect.jpg|thumb|DBOSelect with VulCon]]<br /> <br /> DBOSelect allows you to perform a select on database.<br /> <br /> The result of the select(s) is an XML document in internal format that can then be transformed into a useful document for the client.<br /> <br /> Can be executed more select statements, each one associated to an id, with the possibility of aggregating, using keys, the extracted data.<br /> <br /> Can be defined, for every statement and field, the FieldFormatter that allows you to force the formatting of the values extracted from the database.<br /> <br /> It is used by [[DBOBuilder]].<br /> <br /> The following table shows the DBOSelect attributes:<br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''dbo'''<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.datahandling.dbo.DBOSelect'''<br /> |-<br /> | name || required || DOSelect name<br /> |-<br /> | transformation || optional || Transformation to be used for converting internal rowset representation in user desired XML document.<br /> |-<br /> | force-mode || required || (caller or db2xml): Force mode of the DBO, can be used in [[DBOBuilder]] whit more heterogeneous [[DBOBuilder#DBO|DBO]]. <br/> Mode:<br/> caller - inherit the mode of the caller<br/> db2xml - data extraction mode<br /> |-<br /> | jdbc-connection-name || required || DataSource JNDI name. <br/> Override connection defined in [[DBOBuilder]].<br /> |-<br /> | ignore-input || optional || (true or false): Tells the engine do not use the input data.<br /> |-<br /> | output-data || optional || The default is the value of @name-Output.<br /> |}<br /> <div class="version_ge3.4"><br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | rowset-builder || optional || Defines how-to build the output RowSet XML document:<br /> * standard (default)<br /> * extended<br /> |}<br /> </div><br /> <br /> For example:<br /> <syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?><br /> <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder" <br /> jdbc-connection-name="ds.gv_test" <br /> name="SearchPerson" type="dbobuilder"><br /> <DHVariables><br /> <DHVariable name="decimal-separator" value="."/><br /> <DHVariable name="grouping-separator" value=","/><br /> <DHVariable name="format" value="#0.00"/><br /> <DHVariable name="NAME" value="NULL"/><br /> <DHVariable name="CITY" value="NULL"/><br /> </DHVariables><br /> <DBOSelect class="it.greenvulcano.gvesb.datahandling.dbo.DBOSelect" <br /> name="SearchPerson" <br /> transformation="SearchPerson" type="dbo"><br /> <statement id="1" keys="1,2,3" type="select"><br /> select p.NAME, p.BIRTHDATE, c.NAME, cc.CNUMBER, cc.CREDIT, cc.ENABLED<br /> from PERSON p, CITY c, CREDIT_CARD cc<br /> where p.ID_CITY = c.ID<br /> and p.ID = cc.ID_OWNER<br /> decode{{@{{NAME}}::NULL::::and p.NAME like ‘%@{{NAME}}%’}}<br /> decode{{@{{CITY}}::NULL::::and c.NAME like ‘%@{{CITY}}%’}}<br /> order by c.NAME, p.NAME<br /> </statement><br /> </DBOSelect><br /> </DBOBuilder><br /> </syntaxhighlight><br /> <br /> According to the data present into the DB we obtain as output the following XML (also known as 'standard' RowSet mode):<br /> <syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?><br /> <RowSet><br /> <data id="1" key_1="ANTONIO ROSSI" key_2="19800205 00:00:00" key_3="MILANO"><br /> <row id="1"><br /> <col type="string">1111222233338888</col><br /> <col type="string">48.32000</col><br /> <col type="string">Y</col><br /> </row><br /> <row id="1"><br /> <col type="string">1234123414444789</col><br /> <col type="string">600.00000</col><br /> <col type="string">Y</col><br /> </row><br /> </data><br /> <data id="1" key_1="MARIO BIANCHI" key_2="19700815 00:00:00" key_3="MILANO"><br /> <row id="1"><br /> <col type="string">1234123412341234</col><br /> <col type="string">100.00000</col><br /> <col type="string">Y</col><br /> </row><br /> <row id="1"><br /> <col type="string">1234123415555666</col><br /> <col type="string">300.00000</col><br /> <col type="string">Y</col><br /> </row><br /> </data><br /> </RowSet><br /> </syntaxhighlight><br /> <br /> <div class="version_ge3.4"><br /> To enable 'extended' RowSet mode:<br /> <syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?><br /> <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder" <br /> jdbc-connection-name="ds.gv_test" <br /> name="SearchPerson" type="dbobuilder"><br /> <DHVariables><br /> <DHVariable name="decimal-separator" value="."/><br /> <DHVariable name="grouping-separator" value=","/><br /> <DHVariable name="format" value="#0.00"/><br /> <DHVariable name="NAME" value="NULL"/><br /> <DHVariable name="CITY" value="NULL"/><br /> </DHVariables><br /> <DBOSelect class="it.greenvulcano.gvesb.datahandling.dbo.DBOSelect" <br /> name="SearchPerson" rowset-builder="extended"<br /> transformation="SearchPerson" type="dbo"><br /> <statement id="1" keys="1,2,3" type="select"><br /> select p.NAME, p.BIRTHDATE, c.NAME, cc.CNUMBER, cc.CREDIT, cc.ENABLED<br /> from PERSON p, CITY c, CREDIT_CARD cc<br /> where p.ID_CITY = c.ID<br /> and p.ID = cc.ID_OWNER<br /> decode{{@{{NAME}}::NULL::::and p.NAME like ‘%@{{NAME}}%’}}<br /> decode{{@{{CITY}}::NULL::::and c.NAME like ‘%@{{CITY}}%’}}<br /> order by c.NAME, p.NAME<br /> </statement><br /> </DBOSelect><br /> </DBOBuilder><br /> </syntaxhighlight><br /> According to the data present into the DB we obtain as output the following XML (also known as 'extended' RowSet mode):<br /> <syntaxhighlight lang="xml"><br /> <RowSet xmlns="http://www.greenvulcano.com/database"><br /> <data id="1"><br /> <key><br /> <NAME id="1" isNull="false" type="string">ANTONIO ROSSI</NAME><br /> <BIRTHDATE format="yyyyMMdd HH:mm:ss" id="2" isNull="false" type="timestamp">19800205 00:00:00</BIRTHDATE><br /> <CITY id="3" isNull="false" type="string">MILANO</CITY><br /> </key><br /> <row id="1"><br /> <CNUMBER isNull="false" type="string">1111222233338888</CNUMBER><br /> <CREDIT isNull="false" type="string">500.57000</CREDIT><br /> <ENABLED isNull="false" type="string">Y</ENABLED><br /> </row><br /> <row id="1"><br /> <CNUMBER isNull="false" type="string">1234123414444789</CNUMBER><br /> <CREDIT isNull="false" type="string">600.00000</CREDIT><br /> <ENABLED isNull="false" type="string">Y</ENABLED><br /> </row><br /> </data><br /> <data id="1"><br /> <key><br /> <NAME id="1" isNull="false" type="string">MARIO BIANCHI</NAME><br /> <BIRTHDATE format="yyyyMMdd HH:mm:ss" id="2" isNull="false" type="timestamp">19700815 00:00:00</BIRTHDATE><br /> <CITY id="3" isNull="false" type="string">MILANO</CITY><br /> </key><br /> <row id="1"><br /> <CNUMBER isNull="false" type="string">1234123412341234</CNUMBER><br /> <CREDIT isNull="false" type="string">100.00000</CREDIT><br /> <ENABLED isNull="false" type="string">Y</ENABLED><br /> </row><br /> <row id="1"><br /> <CNUMBER isNull="false" type="string">1234123415555666</CNUMBER><br /> <CREDIT isNull="false" type="string">300.00000</CREDIT><br /> <ENABLED isNull="false" type="string">Y</ENABLED><br /> </row><br /> </data><br /> </RowSet><br /> </syntaxhighlight><br /> </div><br /> <br /> <div class="version_ge3.5"><br /> It's possible to make a query also on a local or remote neo4j graph database using the related cypher (Cypher Query Language) language [http://neo4j.com/docs/stable/cypher-query-lang.html].<br /> To enable this type of query it needs to set the jdbc-connection-name using the neo4j driver jdbc and write a query using the cypher syntax:<br /> <syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?><br /> <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder" <br /> jdbc-connection-name="openejb:Resource/testDHDataSourceN4J" <br /> name="GVESB::TestSelectWithPropsN4J" type="dbobuilder"><br /> <DBOSelect class="it.greenvulcano.gvesb.datahandling.dbo.DBOSelect" <br /> name="TestSelectWithPropsN4J-select"<br /> transformation="identityXML" type="dbo"><br /> <statement id="0" type="select">MATCH (n {title: '@{{PARAM_TITLE}}'}) RETURN n</statement><br /> </DBOSelect><br /> </DBOBuilder><br /> </syntaxhighlight><br /> As you can see in the above section you can make any queries achievable with cypher language.<br /> According to the data present into neo4j DB we obtain as output the same XML structure as returned with the use of the standard jdbc driver SQL.<br /> </div><br /> <br /> DBOSelect might contain the following sub-elements:<br /> * [[Description]]<br /> * [[DHVariables]]<br /> * [[FieldFormatters]]<br /> * [[statement]]</div>

M.deluca https://gvwiki.greenvulcano.com/gvwiki/index.php?title=HDFSRemoteManager&diff=4375 HDFSRemoteManager 2015-03-01T22:00:29Z

<p>M.deluca: /* Description */</p> <hr /> <div>==Description==<br /> <br /> Use this element for encapsulating the parameters required to connect to an Hadoop Distributed File System (HDFS) [http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/HdfsDesign.html] .<br /> Hadoop Distributed File System is a Java-based distributed file system that provides scalable and reliable data storage that is designed to span large clusters of commodity servers. It allows to store and process big data in a distributed environment across clusters of computers. It is designed to scale up from single servers to thousands of machines, each offering local computation and storage.<br /> HDFS follows the master-slave architecture and it has the following elements:<br /> <br /> * Namenode: acts as the "master" server. It manages the file system namespace and regulates client’s access to files stored in the datanodes.<br /> * Datanode: where HDFS stores the data that are replicated in the nodes of the cluster. Datanodes perform read-write operations on the file systems and perform operations such as block creation, deletion, and replication according to the instructions of the namenode.<br /> * Secondary Namenode: is a separate service that keeps a copy of both the edit logs, and filesystem image, merging them periodically to keep the size reasonable.<br /> <br /> HDFSRemoteManager allows to execute the [[remotemanager-call]] on the HDFS filesystem.<br /> <br /> =={{VULCON}} / {{GVCONSOLE}} Configuration==<br /> <br /> If the target directory is on a HDFS file system, you can define the parameters for connection.<br /> <br /> The HDFSRemoteManager Element is used by [[Fsmonitor-call#RemoteFileSystemMonitor|RemoteFileSystemMonitor]] and [[remotemanager-call]]. It has the following attributes:<br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-manager'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.util.remotefs.hdfs.HDFSRemoteManager.<br /> |-<br /> | connectionURL || required || Server host name and port to contact HDFS. The entire URI is passed to the FileSystem instance's initialize method. Example: hdfs://[IP_NAME_NOME]:[PORT_NAME_NODE]. [http://wiki.apache.org/hadoop/NameNode] <br /> |-<br /> | username || required || User name used to access to the HDFS file system.<br /> |-<br /> | password || required || User password. #Encrypted<br /> |-<br /> | autoConnect || optional || If true the instance use autoconnect/disconnect at each method invocation. Default: false.<br /> |}</div>

M.deluca https://gvwiki.greenvulcano.com/gvwiki/index.php?title=HDFSRemoteManager&diff=4374 HDFSRemoteManager 2015-03-01T21:55:08Z

<p>M.deluca: /* Description */</p> <hr /> <div>==Description==<br /> <br /> Use this element for encapsulating the parameters required to connect to an Hadoop Distributed File System (HDFS) [http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/HdfsDesign.html] .<br /> Hadoop Distributed File System is a Java-based distributed file system that provides scalable and reliable data storage that is designed to span large clusters of commodity servers. It allows to store and process big data in a distributed environment across clusters of computers. It is designed to scale up from single servers to thousands of machines, each offering local computation and storage.<br /> HDFS follows the master-slave architecture and it has the following elements:<br /> <br /> * Namenode: acts as the "master" server. It manages the file system namespace and regulates client’s access to files stored in the datanodes.<br /> * Datanode: where HDFS stores the data that are replicated in the nodes of the cluster. Datanodes perform read-write operations on the file systems and perform operations such as block creation, deletion, and replication according to the instructions of the namenode.<br /> * Secondary Namenode: is a separate service that keeps a copy of both the edit logs, and filesystem image, merging them periodically to keep the size reasonable.<br /> <br /> =={{VULCON}} / {{GVCONSOLE}} Configuration==<br /> <br /> If the target directory is on a HDFS file system, you can define the parameters for connection.<br /> <br /> The HDFSRemoteManager Element is used by [[Fsmonitor-call#RemoteFileSystemMonitor|RemoteFileSystemMonitor]] and [[remotemanager-call]]. It has the following attributes:<br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-manager'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.util.remotefs.hdfs.HDFSRemoteManager.<br /> |-<br /> | connectionURL || required || Server host name and port to contact HDFS. The entire URI is passed to the FileSystem instance's initialize method. Example: hdfs://[IP_NAME_NOME]:[PORT_NAME_NODE]. [http://wiki.apache.org/hadoop/NameNode] <br /> |-<br /> | username || required || User name used to access to the HDFS file system.<br /> |-<br /> | password || required || User password. #Encrypted<br /> |-<br /> | autoConnect || optional || If true the instance use autoconnect/disconnect at each method invocation. Default: false.<br /> |}</div>

M.deluca https://gvwiki.greenvulcano.com/gvwiki/index.php?title=HDFSRemoteManager&diff=4373 HDFSRemoteManager 2015-03-01T21:46:09Z

<p>M.deluca: /* Description */</p> <hr /> <div>==Description==<br /> <br /> Use this element for encapsulating the parameters required to connect to an Hadoop Distributed File System (HDFS).<br /> Hadoop Distributed File System is a Java-based distributed file system that provides scalable and reliable data storage that is designed to span large clusters of commodity servers. It allows to store and process big data in a distributed environment across clusters of computers. It is designed to scale up from single servers to thousands of machines, each offering local computation and storage.<br /> HDFS follows the master-slave architecture and it has the following elements:<br /> <br /> * Namenode: acts as the "master" server. It manages the file system namespace and regulates client’s access to files stored in the datanodes.<br /> * Datanode: where HDFS stores the data that are replicated in the nodes of the cluster. Datanodes perform read-write operations on the file systems and perform operations such as block creation, deletion, and replication according to the instructions of the namenode.<br /> * Secondary Namenode: is a separate service that keeps a copy of both the edit logs, and filesystem image, merging them periodically to keep the size reasonable.<br /> <br /> =={{VULCON}} / {{GVCONSOLE}} Configuration==<br /> <br /> If the target directory is on a HDFS file system, you can define the parameters for connection.<br /> <br /> The HDFSRemoteManager Element is used by [[Fsmonitor-call#RemoteFileSystemMonitor|RemoteFileSystemMonitor]] and [[remotemanager-call]]. It has the following attributes:<br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-manager'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.util.remotefs.hdfs.HDFSRemoteManager.<br /> |-<br /> | connectionURL || required || Server host name and port to contact HDFS. The entire URI is passed to the FileSystem instance's initialize method. Example: hdfs://[IP_NAME_NOME]:[PORT_NAME_NODE]. [http://wiki.apache.org/hadoop/NameNode] <br /> |-<br /> | username || required || User name used to access to the HDFS file system.<br /> |-<br /> | password || required || User password. #Encrypted<br /> |-<br /> | autoConnect || optional || If true the instance use autoconnect/disconnect at each method invocation. Default: false.<br /> |}</div>

M.deluca https://gvwiki.greenvulcano.com/gvwiki/index.php?title=HDFSRemoteManager&diff=4372 HDFSRemoteManager 2015-03-01T21:45:13Z

<p>M.deluca: /* Description */</p> <hr /> <div>==Description==<br /> <br /> Use this element for encapsulating the parameters required to connect to an Hadoop Distributed File System (HDFS).<br /> Hadoop Distributed File System is a Java-based distributed file system that provides scalable and reliable data storage that is designed to span large clusters of commodity servers. It allows to store and process big data in a distributed environment across clusters of computers. It is designed to scale up from single servers to thousands of machines, each offering local computation and storage.<br /> HDFS follows the master-slave architecture and it has the following elements:<br /> <br /> - Namenode: acts as the "master" server. It manages the file system namespace and regulates client’s access to files stored in the datanodes.<br /> - Datanode: where HDFS stores the data that are replicated in the nodes of the cluster. Datanodes perform read-write operations on the file systems and perform operations such as block creation, deletion, and replication according to the instructions of the namenode.<br /> - Secondary Namenode: is a separate service that keeps a copy of both the edit logs, and filesystem image, merging them periodically to keep the size reasonable.<br /> <br /> =={{VULCON}} / {{GVCONSOLE}} Configuration==<br /> <br /> If the target directory is on a HDFS file system, you can define the parameters for connection.<br /> <br /> The HDFSRemoteManager Element is used by [[Fsmonitor-call#RemoteFileSystemMonitor|RemoteFileSystemMonitor]] and [[remotemanager-call]]. It has the following attributes:<br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-manager'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.util.remotefs.hdfs.HDFSRemoteManager.<br /> |-<br /> | connectionURL || required || Server host name and port to contact HDFS. The entire URI is passed to the FileSystem instance's initialize method. Example: hdfs://[IP_NAME_NOME]:[PORT_NAME_NODE]. [http://wiki.apache.org/hadoop/NameNode] <br /> |-<br /> | username || required || User name used to access to the HDFS file system.<br /> |-<br /> | password || required || User password. #Encrypted<br /> |-<br /> | autoConnect || optional || If true the instance use autoconnect/disconnect at each method invocation. Default: false.<br /> |}</div>

M.deluca https://gvwiki.greenvulcano.com/gvwiki/index.php?title=Remotemanager-call&diff=4361 Remotemanager-call 2015-01-14T13:24:51Z

<p>M.deluca: /* RemoteMoveCommand */</p> <hr /> <div>==Description==<br /> <br /> This {{GVESB}} plug-in allows you to perform a sequence of file operations in a remote file system accessible via various protocols.<br /> <br /> =={{VULCON}} / {{GVCONSOLE}} Configuration==<br /> <br /> The operations allowed are: <br /> * Download a file/directory from a remote directory to a local directory <br /> * Upload a file/directory from a local directory to a remote directory <br /> * Control of one or more files (whose name corresponds to a date regular expressions) in a remote directory<br /> * Deleting a file/directory from a remote directory <br /> * Rename/move a file/directory in a remote directory<br /> <br /> <br /> The remotemanager-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:<br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''call'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.RemoteManagerCall'''.<br /> |-<br /> | name || required || Operation name. Used in the [[Flow]] section to associate workflow nodes to VCL operations.<br /> |}<br /> <br /> and the subelements:<br /> <br /> * Description<br /> * [[FTPManager]] | [[FTPSManager]] | [[SFTPManager]]<br /> <div class="version_ge3.5"><br /> | [[HDFSRemoteManager]]<br /> </div><br /> * RemoteCommands<br /> <br /> ===RemoteCommands===<br /> <br /> The RemoteCommands element contains the sequence of FTP operations to be carried out. These operations will be performed in the order they were configured. An error in one of the operation marked as critical will terminate the execution of the entire<br /> sequence.<br /> <br /> The RemoteCommands Element is used by [[remotemanager-call]] and, internally, it is possible to configure the following operations:<br /> {|class="gvtable"<br /> ! Remote Command !! Use this for...<br /> |-<br /> | [[Remotemanager-call#RemoteSearchCommand | RemoteSearchCommand]] || Controlling one or more files (whose name corresponds to a regular expressions) in a remote directory <br /> |-<br /> | [[Remotemanager-call#RemoteMoveCommand |RemoteMoveCommand]] || Renaming/moving a file/directory in a remote directory<br /> |-<br /> | [[Remotemanager-call#RemoteDeleteCommand |RemoteDeleteCommand]] || Deleting a file/directory from a remote directory <br /> |-<br /> | [[Remotemanager-call#RemoteDownloadCommand |RemoteDownloadCommand]] || Downloading a file/directory from a remote directory to a local directory <br /> |-<br /> | [[Remotemanager-call#RemoteUploadCommand|RemoteUploadCommand]] || Uploading a file/directory from a local directory to a remote directory <br /> |}<br /> <br /> The remote commands can have the following subelements:<br /> * Description<br /> <div class="version_ge3.5"><br /> * [[PropertyDef]]<br /> </div><br /> <br /> ====RemoteSearchCommand====<br /> <br /> The {{GVESB}} operation '''RemoteSearchCommand''' checks if one or more files, whose name conforms to a given regular expression, exists within the specified directory.<br /> <br /> On completion and in the absence of errors the following properties of output GVBuffer are setted:<br /> # GVRM_FIND_FILES_NUM Number of files found (>= 0)<br /> # GVRM_FIND_FILES_LIST List of names of found files, separated by ','. Set only if the value of field 'GVRM_FIND_FILES_NUM' is greater than 0. <br/> Both the pattern of the file and that the directory can be static or contain [[placeholders]] that are replaced at runtime.<br /> <br /> The following table shows its attributes:<br /> <br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-command'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVSearch'''.<br /> |-<br /> | sourcePath || required || Absolute path of the directory to search in.<br /> |-<br /> | filePattern || required || File name to search for. Can be a regular expression.<br /> |-<br /> | isCritical || optional || If true an internal error interrupt the command sequence. Default true.<br /> |}<br /> <br /> ====RemoteMoveCommand====<br /> <br /> The {{GVESB}} operation '''RemoteMoveCommand''' moves/renames a file/directory. <br /> <br /> The file name, the source and destination directory names can be static or contain [[placeholders]] that are replaced at runtime. After the replacement of the [[placeholders|placeholder]], the value of the ''filename'' may contain a regular expression, in which case, all files of the source directory, whose name is in accordance with the corresponding pattern, will be moved to the destination directory. If the destination directory already contains files with the same name, they will be overwritten.<br /> <br /> The following table shows its attributes:<br /> <br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-command'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVMove'''.<br /> |-<br /> | targetPath || required || Absolute path of the file/directory where is the file to move. <br /> |-<br /> | oldName || required || Name of the file to be moved. <br /> |-<br /> | newName || required || Name of the file moved. <br /> |-<br /> | isCritical || optional || If true an internal error interrupt the command sequence. Default true.<br /> |}<br /> <br /> <div class="version_ge3.5"><br /> The following table shows the PropertyDef possible elements that can be set when the command is executed on the [[HDFSRemoteManager|HDFS]] file system:<br /> {|class="gvtable"<br /> ! Property !! Possible Values<br /> |-<br /> | dfs.file.overwrite || true/false; default=false<br /> |}<br /> This parameter can be used to owerwrite the target destination with the source one when a move operation is used on the HDFS file system.<br /> <br /> ====RemoteDeleteCommand====<br /> <br /> The {{GVESB}} operation '''RemoteDeleteCommand''' deletes a file or directory. <br /> <br /> Both the file name and the directory can be static or contain [[placeholders]] that are replaced at runtime. After the replacement of the [[placeholders|placeholder]], the value of the ''filename'' may contain a regular expression, in which case, will erase all files in the specified directory whose name is consistent with the corresponding pattern.<br /> <br /> The following table shows its attributes:<br /> <br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-command'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVDelete'''<br /> |-<br /> | targetPath || required || Absolute path of the file/directory to remove.<br /> |-<br /> | filePattern || optional || File name to remove. Might contain a regular expression. It is used only if ''targetPath'' is a directory, and if empty the filter is ignored.<br /> |-<br /> | isCritical || optional || If true an internal error interrupt the command sequence. Default true.<br /> |}<br /> <br /> ====RemoteDownloadCommand==== <br /> <br /> The {{GVESB}} operation '''RemoteDownloadCommand''' downloads a file or directory from a remote directory and saved in the local directory you specified (or in GVBuffer). <br /> <br /> File names and directories can be static or contain [[placeholders]] that are replaced at runtime.<br /> <br /> The following table shows its attributes:<br /> <br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-command'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVDownload'''.<br /> |-<br /> | remotePath || required || Pathname of remote directory containing the file to download. It can be an absolute pathname or relative, in the second case it is relative to home directory of ftp user.<br /> |-<br /> | remoteFilePattern || required || The name of the file to download.<br /> |-<br /> | toGVBufferExpression || optional || GVBuffer OGNL expression used to specify how to handle the current downloaded file. In the expression, the downloaded file will be referenced by the variable #input, and will be a byte [].<br /> |-<br /> | targetPath || optional || Pathname of the local directory to save the downloaded file. Must be an absolute pathname.<br /> |-<br /> | isCritical || optional || If true an internal error interrupt the command sequence. Default true.<br /> |}<br /> <br /> <div class="version_ge3.5"><br /> The following table shows the PropertyDef possible elements that can be set when the command is executed on the [[HDFSRemoteManager|HDFS]] file system:<br /> {|class="gvtable"<br /> ! Property !! Possible Values<br /> |-<br /> | dfs.file.delete-source || fixed=false<br /> |-<br /> | dfs.file.raw-local-filesystem || fixed=true<br /> |-<br /> | dfs.stream-buffer-size || default: 4096<br /> |}<br /> These parameters can be used to specify the related action when a download operation is used on the HDFS file system.<br /> <br /> ====RemoteUploadCommand====<br /> <br /> The {{GVESB}} operation '''RemoteUploadCommand''' uploads a file from a local directory (or [[GVBuffer]]) to the remote directory specified. <br /> <br /> File and/or directory names can be static or contain [[placeholders]] that are replaced at runtime.<br /> <br /> The following table shows its attributes:<br /> <br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-command'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVUpload'''.<br /> |-<br /> | sourcePath || optional || Pathname of the local directory where the file is transferred. Must be an absolute pathname.<br /> |-<br /> | sourceFilePattern || optional || The name of the file to transfer. <br /> |-<br /> | fromGVBufferExpression || optional || OGNL Expression applied to the current [[GVBuffer]] that specifies how to build the file content. In the expression, the [[GVBuffer]] is associated with #object, and must return a byte[]. <br /> |-<br /> | remotePath || required || Pathname of remote directory where upload the file. It can be an absolute pathname or relative, in the second case it is relative to home directory of ftp user.<br /> |-<br /> | isCritical || optional || If true an internal error interrupt the command sequence. Default true.<br /> |}<br /> <br /> <div class="version_ge3.5"><br /> The following table shows the PropertyDef possible elements that can be set when the command is executed on the [[HDFSRemoteManager|HDFS]] file system:<br /> {|class="gvtable"<br /> ! Property !! Possible Values<br /> |-<br /> | dfs.file.delete-source || true/false; default=false<br /> |-<br /> | dfs.file.overwrite || true/false; default=false<br /> |-<br /> | dfs.permissions.path || Unix-like permission Example: 777; default 700<br /> |-<br /> | dfs.stream-buffer-size || default: 8192<br /> |-<br /> | dfs.replication || default: 1<br /> |-<br /> | dfs.blocksize || default: 4194304<br /> |-<br /> | dfs.permissions.user || hdfs user owner<br /> |-<br /> | dfs.permissions.group || hdfs user group<br /> |}<br /> These parameters can be used to owerwrite the target destination with the source one, set the replication, permissions and the other properties on destination target when an upload operation is used on the HDFS file system.</div>

M.deluca https://gvwiki.greenvulcano.com/gvwiki/index.php?title=Remotemanager-call&diff=4360 Remotemanager-call 2015-01-14T13:20:19Z

<p>M.deluca: /* RemoteDownloadCommand */</p> <hr /> <div>==Description==<br /> <br /> This {{GVESB}} plug-in allows you to perform a sequence of file operations in a remote file system accessible via various protocols.<br /> <br /> =={{VULCON}} / {{GVCONSOLE}} Configuration==<br /> <br /> The operations allowed are: <br /> * Download a file/directory from a remote directory to a local directory <br /> * Upload a file/directory from a local directory to a remote directory <br /> * Control of one or more files (whose name corresponds to a date regular expressions) in a remote directory<br /> * Deleting a file/directory from a remote directory <br /> * Rename/move a file/directory in a remote directory<br /> <br /> <br /> The remotemanager-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:<br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''call'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.RemoteManagerCall'''.<br /> |-<br /> | name || required || Operation name. Used in the [[Flow]] section to associate workflow nodes to VCL operations.<br /> |}<br /> <br /> and the subelements:<br /> <br /> * Description<br /> * [[FTPManager]] | [[FTPSManager]] | [[SFTPManager]]<br /> <div class="version_ge3.5"><br /> | [[HDFSRemoteManager]]<br /> </div><br /> * RemoteCommands<br /> <br /> ===RemoteCommands===<br /> <br /> The RemoteCommands element contains the sequence of FTP operations to be carried out. These operations will be performed in the order they were configured. An error in one of the operation marked as critical will terminate the execution of the entire<br /> sequence.<br /> <br /> The RemoteCommands Element is used by [[remotemanager-call]] and, internally, it is possible to configure the following operations:<br /> {|class="gvtable"<br /> ! Remote Command !! Use this for...<br /> |-<br /> | [[Remotemanager-call#RemoteSearchCommand | RemoteSearchCommand]] || Controlling one or more files (whose name corresponds to a regular expressions) in a remote directory <br /> |-<br /> | [[Remotemanager-call#RemoteMoveCommand |RemoteMoveCommand]] || Renaming/moving a file/directory in a remote directory<br /> |-<br /> | [[Remotemanager-call#RemoteDeleteCommand |RemoteDeleteCommand]] || Deleting a file/directory from a remote directory <br /> |-<br /> | [[Remotemanager-call#RemoteDownloadCommand |RemoteDownloadCommand]] || Downloading a file/directory from a remote directory to a local directory <br /> |-<br /> | [[Remotemanager-call#RemoteUploadCommand|RemoteUploadCommand]] || Uploading a file/directory from a local directory to a remote directory <br /> |}<br /> <br /> The remote commands can have the following subelements:<br /> * Description<br /> <div class="version_ge3.5"><br /> * [[PropertyDef]]<br /> </div><br /> <br /> ====RemoteSearchCommand====<br /> <br /> The {{GVESB}} operation '''RemoteSearchCommand''' checks if one or more files, whose name conforms to a given regular expression, exists within the specified directory.<br /> <br /> On completion and in the absence of errors the following properties of output GVBuffer are setted:<br /> # GVRM_FIND_FILES_NUM Number of files found (>= 0)<br /> # GVRM_FIND_FILES_LIST List of names of found files, separated by ','. Set only if the value of field 'GVRM_FIND_FILES_NUM' is greater than 0. <br/> Both the pattern of the file and that the directory can be static or contain [[placeholders]] that are replaced at runtime.<br /> <br /> The following table shows its attributes:<br /> <br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-command'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVSearch'''.<br /> |-<br /> | sourcePath || required || Absolute path of the directory to search in.<br /> |-<br /> | filePattern || required || File name to search for. Can be a regular expression.<br /> |-<br /> | isCritical || optional || If true an internal error interrupt the command sequence. Default true.<br /> |}<br /> <br /> ====RemoteMoveCommand====<br /> <br /> The {{GVESB}} operation '''RemoteMoveCommand''' moves/renames a file/directory. <br /> <br /> The file name, the source and destination directory names can be static or contain [[placeholders]] that are replaced at runtime. After the replacement of the [[placeholders|placeholder]], the value of the ''filename'' may contain a regular expression, in which case, all files of the source directory, whose name is in accordance with the corresponding pattern, will be moved to the destination directory. If the destination directory already contains files with the same name, they will be overwritten.<br /> <br /> The following table shows its attributes:<br /> <br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-command'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVMove'''.<br /> |-<br /> | targetPath || required || Absolute path of the file/directory where is the file to move. <br /> |-<br /> | oldName || required || Name of the file to be moved. <br /> |-<br /> | newName || required || Name of the file moved. <br /> |-<br /> | isCritical || optional || If true an internal error interrupt the command sequence. Default true.<br /> |}<br /> <br /> ====RemoteDeleteCommand====<br /> <br /> The {{GVESB}} operation '''RemoteDeleteCommand''' deletes a file or directory. <br /> <br /> Both the file name and the directory can be static or contain [[placeholders]] that are replaced at runtime. After the replacement of the [[placeholders|placeholder]], the value of the ''filename'' may contain a regular expression, in which case, will erase all files in the specified directory whose name is consistent with the corresponding pattern.<br /> <br /> The following table shows its attributes:<br /> <br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-command'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVDelete'''<br /> |-<br /> | targetPath || required || Absolute path of the file/directory to remove.<br /> |-<br /> | filePattern || optional || File name to remove. Might contain a regular expression. It is used only if ''targetPath'' is a directory, and if empty the filter is ignored.<br /> |-<br /> | isCritical || optional || If true an internal error interrupt the command sequence. Default true.<br /> |}<br /> <br /> ====RemoteDownloadCommand==== <br /> <br /> The {{GVESB}} operation '''RemoteDownloadCommand''' downloads a file or directory from a remote directory and saved in the local directory you specified (or in GVBuffer). <br /> <br /> File names and directories can be static or contain [[placeholders]] that are replaced at runtime.<br /> <br /> The following table shows its attributes:<br /> <br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-command'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVDownload'''.<br /> |-<br /> | remotePath || required || Pathname of remote directory containing the file to download. It can be an absolute pathname or relative, in the second case it is relative to home directory of ftp user.<br /> |-<br /> | remoteFilePattern || required || The name of the file to download.<br /> |-<br /> | toGVBufferExpression || optional || GVBuffer OGNL expression used to specify how to handle the current downloaded file. In the expression, the downloaded file will be referenced by the variable #input, and will be a byte [].<br /> |-<br /> | targetPath || optional || Pathname of the local directory to save the downloaded file. Must be an absolute pathname.<br /> |-<br /> | isCritical || optional || If true an internal error interrupt the command sequence. Default true.<br /> |}<br /> <br /> <div class="version_ge3.5"><br /> The following table shows the PropertyDef possible elements that can be set when the command is executed on the [[HDFSRemoteManager|HDFS]] file system:<br /> {|class="gvtable"<br /> ! Property !! Possible Values<br /> |-<br /> | dfs.file.delete-source || fixed=false<br /> |-<br /> | dfs.file.raw-local-filesystem || fixed=true<br /> |-<br /> | dfs.stream-buffer-size || default: 4096<br /> |}<br /> These parameters can be used to specify the related action when a download operation is used on the HDFS file system.<br /> <br /> ====RemoteUploadCommand====<br /> <br /> The {{GVESB}} operation '''RemoteUploadCommand''' uploads a file from a local directory (or [[GVBuffer]]) to the remote directory specified. <br /> <br /> File and/or directory names can be static or contain [[placeholders]] that are replaced at runtime.<br /> <br /> The following table shows its attributes:<br /> <br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-command'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVUpload'''.<br /> |-<br /> | sourcePath || optional || Pathname of the local directory where the file is transferred. Must be an absolute pathname.<br /> |-<br /> | sourceFilePattern || optional || The name of the file to transfer. <br /> |-<br /> | fromGVBufferExpression || optional || OGNL Expression applied to the current [[GVBuffer]] that specifies how to build the file content. In the expression, the [[GVBuffer]] is associated with #object, and must return a byte[]. <br /> |-<br /> | remotePath || required || Pathname of remote directory where upload the file. It can be an absolute pathname or relative, in the second case it is relative to home directory of ftp user.<br /> |-<br /> | isCritical || optional || If true an internal error interrupt the command sequence. Default true.<br /> |}<br /> <br /> <div class="version_ge3.5"><br /> The following table shows the PropertyDef possible elements that can be set when the command is executed on the [[HDFSRemoteManager|HDFS]] file system:<br /> {|class="gvtable"<br /> ! Property !! Possible Values<br /> |-<br /> | dfs.file.delete-source || true/false; default=false<br /> |-<br /> | dfs.file.overwrite || true/false; default=false<br /> |-<br /> | dfs.permissions.path || Unix-like permission Example: 777; default 700<br /> |-<br /> | dfs.stream-buffer-size || default: 8192<br /> |-<br /> | dfs.replication || default: 1<br /> |-<br /> | dfs.blocksize || default: 4194304<br /> |-<br /> | dfs.permissions.user || hdfs user owner<br /> |-<br /> | dfs.permissions.group || hdfs user group<br /> |}<br /> These parameters can be used to owerwrite the target destination with the source one, set the replication, permissions and the other properties on destination target when an upload operation is used on the HDFS file system.</div>

M.deluca https://gvwiki.greenvulcano.com/gvwiki/index.php?title=Remotemanager-call&diff=4359 Remotemanager-call 2015-01-14T13:17:09Z

<p>M.deluca: /* RemoteUploadCommand */</p> <hr /> <div>==Description==<br /> <br /> This {{GVESB}} plug-in allows you to perform a sequence of file operations in a remote file system accessible via various protocols.<br /> <br /> =={{VULCON}} / {{GVCONSOLE}} Configuration==<br /> <br /> The operations allowed are: <br /> * Download a file/directory from a remote directory to a local directory <br /> * Upload a file/directory from a local directory to a remote directory <br /> * Control of one or more files (whose name corresponds to a date regular expressions) in a remote directory<br /> * Deleting a file/directory from a remote directory <br /> * Rename/move a file/directory in a remote directory<br /> <br /> <br /> The remotemanager-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:<br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''call'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.RemoteManagerCall'''.<br /> |-<br /> | name || required || Operation name. Used in the [[Flow]] section to associate workflow nodes to VCL operations.<br /> |}<br /> <br /> and the subelements:<br /> <br /> * Description<br /> * [[FTPManager]] | [[FTPSManager]] | [[SFTPManager]]<br /> <div class="version_ge3.5"><br /> | [[HDFSRemoteManager]]<br /> </div><br /> * RemoteCommands<br /> <br /> ===RemoteCommands===<br /> <br /> The RemoteCommands element contains the sequence of FTP operations to be carried out. These operations will be performed in the order they were configured. An error in one of the operation marked as critical will terminate the execution of the entire<br /> sequence.<br /> <br /> The RemoteCommands Element is used by [[remotemanager-call]] and, internally, it is possible to configure the following operations:<br /> {|class="gvtable"<br /> ! Remote Command !! Use this for...<br /> |-<br /> | [[Remotemanager-call#RemoteSearchCommand | RemoteSearchCommand]] || Controlling one or more files (whose name corresponds to a regular expressions) in a remote directory <br /> |-<br /> | [[Remotemanager-call#RemoteMoveCommand |RemoteMoveCommand]] || Renaming/moving a file/directory in a remote directory<br /> |-<br /> | [[Remotemanager-call#RemoteDeleteCommand |RemoteDeleteCommand]] || Deleting a file/directory from a remote directory <br /> |-<br /> | [[Remotemanager-call#RemoteDownloadCommand |RemoteDownloadCommand]] || Downloading a file/directory from a remote directory to a local directory <br /> |-<br /> | [[Remotemanager-call#RemoteUploadCommand|RemoteUploadCommand]] || Uploading a file/directory from a local directory to a remote directory <br /> |}<br /> <br /> The remote commands can have the following subelements:<br /> * Description<br /> <div class="version_ge3.5"><br /> * [[PropertyDef]]<br /> </div><br /> <br /> ====RemoteSearchCommand====<br /> <br /> The {{GVESB}} operation '''RemoteSearchCommand''' checks if one or more files, whose name conforms to a given regular expression, exists within the specified directory.<br /> <br /> On completion and in the absence of errors the following properties of output GVBuffer are setted:<br /> # GVRM_FIND_FILES_NUM Number of files found (>= 0)<br /> # GVRM_FIND_FILES_LIST List of names of found files, separated by ','. Set only if the value of field 'GVRM_FIND_FILES_NUM' is greater than 0. <br/> Both the pattern of the file and that the directory can be static or contain [[placeholders]] that are replaced at runtime.<br /> <br /> The following table shows its attributes:<br /> <br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-command'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVSearch'''.<br /> |-<br /> | sourcePath || required || Absolute path of the directory to search in.<br /> |-<br /> | filePattern || required || File name to search for. Can be a regular expression.<br /> |-<br /> | isCritical || optional || If true an internal error interrupt the command sequence. Default true.<br /> |}<br /> <br /> ====RemoteMoveCommand====<br /> <br /> The {{GVESB}} operation '''RemoteMoveCommand''' moves/renames a file/directory. <br /> <br /> The file name, the source and destination directory names can be static or contain [[placeholders]] that are replaced at runtime. After the replacement of the [[placeholders|placeholder]], the value of the ''filename'' may contain a regular expression, in which case, all files of the source directory, whose name is in accordance with the corresponding pattern, will be moved to the destination directory. If the destination directory already contains files with the same name, they will be overwritten.<br /> <br /> The following table shows its attributes:<br /> <br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-command'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVMove'''.<br /> |-<br /> | targetPath || required || Absolute path of the file/directory where is the file to move. <br /> |-<br /> | oldName || required || Name of the file to be moved. <br /> |-<br /> | newName || required || Name of the file moved. <br /> |-<br /> | isCritical || optional || If true an internal error interrupt the command sequence. Default true.<br /> |}<br /> <br /> ====RemoteDeleteCommand====<br /> <br /> The {{GVESB}} operation '''RemoteDeleteCommand''' deletes a file or directory. <br /> <br /> Both the file name and the directory can be static or contain [[placeholders]] that are replaced at runtime. After the replacement of the [[placeholders|placeholder]], the value of the ''filename'' may contain a regular expression, in which case, will erase all files in the specified directory whose name is consistent with the corresponding pattern.<br /> <br /> The following table shows its attributes:<br /> <br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-command'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVDelete'''<br /> |-<br /> | targetPath || required || Absolute path of the file/directory to remove.<br /> |-<br /> | filePattern || optional || File name to remove. Might contain a regular expression. It is used only if ''targetPath'' is a directory, and if empty the filter is ignored.<br /> |-<br /> | isCritical || optional || If true an internal error interrupt the command sequence. Default true.<br /> |}<br /> <br /> ====RemoteDownloadCommand==== <br /> <br /> The {{GVESB}} operation '''RemoteDownloadCommand''' downloads a file or directory from a remote directory and saved in the local directory you specified (or in GVBuffer). <br /> <br /> File names and directories can be static or contain [[placeholders]] that are replaced at runtime.<br /> <br /> The following table shows its attributes:<br /> <br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-command'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVDownload'''.<br /> |-<br /> | remotePath || required || Pathname of remote directory containing the file to download. It can be an absolute pathname or relative, in the second case it is relative to home directory of ftp user.<br /> |-<br /> | remoteFilePattern || required || The name of the file to download.<br /> |-<br /> | toGVBufferExpression || optional || GVBuffer OGNL expression used to specify how to handle the current downloaded file. In the expression, the downloaded file will be referenced by the variable #input, and will be a byte [].<br /> |-<br /> | targetPath || optional || Pathname of the local directory to save the downloaded file. Must be an absolute pathname.<br /> |-<br /> | isCritical || optional || If true an internal error interrupt the command sequence. Default true.<br /> |}<br /> <br /> <div class="version_ge3.5"><br /> The following table shows the PropertyDef possible elements that can be set when the command is executed on the [[HDFSRemoteManager|HDFS]] file system:<br /> {|class="gvtable"<br /> ! Property !! Possible Values<br /> |-<br /> | dfs.file.delete-source || true/false<br /> |-<br /> | dfs.file.raw-local-filesystem || true/false<br /> |-<br /> | dfs.stream-buffer-size || default: 8192<br /> |}<br /> These parameters can be used to specify the related action when a download operation is used on the HDFS file system.<br /> <br /> ====RemoteUploadCommand====<br /> <br /> The {{GVESB}} operation '''RemoteUploadCommand''' uploads a file from a local directory (or [[GVBuffer]]) to the remote directory specified. <br /> <br /> File and/or directory names can be static or contain [[placeholders]] that are replaced at runtime.<br /> <br /> The following table shows its attributes:<br /> <br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-command'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVUpload'''.<br /> |-<br /> | sourcePath || optional || Pathname of the local directory where the file is transferred. Must be an absolute pathname.<br /> |-<br /> | sourceFilePattern || optional || The name of the file to transfer. <br /> |-<br /> | fromGVBufferExpression || optional || OGNL Expression applied to the current [[GVBuffer]] that specifies how to build the file content. In the expression, the [[GVBuffer]] is associated with #object, and must return a byte[]. <br /> |-<br /> | remotePath || required || Pathname of remote directory where upload the file. It can be an absolute pathname or relative, in the second case it is relative to home directory of ftp user.<br /> |-<br /> | isCritical || optional || If true an internal error interrupt the command sequence. Default true.<br /> |}<br /> <br /> <div class="version_ge3.5"><br /> The following table shows the PropertyDef possible elements that can be set when the command is executed on the [[HDFSRemoteManager|HDFS]] file system:<br /> {|class="gvtable"<br /> ! Property !! Possible Values<br /> |-<br /> | dfs.file.delete-source || true/false; default=false<br /> |-<br /> | dfs.file.overwrite || true/false; default=false<br /> |-<br /> | dfs.permissions.path || Unix-like permission Example: 777; default 700<br /> |-<br /> | dfs.stream-buffer-size || default: 8192<br /> |-<br /> | dfs.replication || default: 1<br /> |-<br /> | dfs.blocksize || default: 4194304<br /> |-<br /> | dfs.permissions.user || hdfs user owner<br /> |-<br /> | dfs.permissions.group || hdfs user group<br /> |}<br /> These parameters can be used to owerwrite the target destination with the source one, set the replication, permissions and the other properties on destination target when an upload operation is used on the HDFS file system.</div>

M.deluca https://gvwiki.greenvulcano.com/gvwiki/index.php?title=PropertyDef&diff=4356 PropertyDef 2015-01-13T20:45:18Z

<p>M.deluca: /* PropertyDef */</p> <hr /> <div>==PropertyDef==<br /> <br /> Defines a property to set in [[GVBuffer]]. <br /> <br /> The PropertyDef Element is used by: [[ChangeGVBuffer]], [[GVSavePointNode#SpProperties|SpProperties]], [[JbProperties]], [[Remotemanager-call#RemoteCommandsRemoteCommands|RemoteCommands]].<br /> <br /> The following table shows the PropertyDef element's attributes:<br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | name || required || Property name. <br /> |-<br /> | value || required || Property value. Can contains [[Placeholders|metadata]]<br /> |-<br /> | overwrite-body || optional || If "yes" the [[GVBuffer]] body is overwitten with the GVBuffer's property value or with the current property value, or is set to null.<br /> The body overwrite is execute prior of 'compress', 'crypto' or 'base64' operations.<br /> WARNING!!!!!!! The 'clear-data' operation is still performed invalidating the body overwriting.<br /> The attribute's admitted values are:<br /> * yes<br /> * no<br /> |}<br /> <br /> Might contain the sub-element [[Description]].<br /> <br /> <br /> <br /> The following table shows the PropertyDef possible elements that can be set when a RemoteCommand is executed on the HDFS file system:<br /> {|class="gvtable"<br /> ! RemoteCommand !! Possible Values<br /> |-<br /> | GVDownload || * dfs.file.delete-source [true|false]<br /> * dfs.file.raw-local-filesystem [true|false]<br /> * dfs.stream-buffer-size [default: 8192]<br /> <br /> These parameters can be used to specify the related action when a download operation is used on the HDFS file system. <br /> |-<br /> | GVUpload || * dfs.file.delete-source [true|false]<br /> * dfs.file.overwrite [true|false]<br /> * dfs.permissions.path [Unix-like permission Example: 777]<br /> * dfs.stream-buffer-size<br /> * dfs.replication [default 1:]<br /> * dfs.blocksize [default: 1048576]<br /> * dfs.permissions.user [hdfs user owner]<br /> * dfs.permissions.group [hdfs user group]<br /> These parameters can be used to owerwrite the target destination with the source one, set the replication, permissions and the other properties on destination target when a download operation is used on the HDFS file system.<br /> |}</div>

M.deluca https://gvwiki.greenvulcano.com/gvwiki/index.php?title=PropertyDef&diff=4355 PropertyDef 2015-01-13T20:39:14Z

<p>M.deluca: /* PropertyDef */</p> <hr /> <div>==PropertyDef==<br /> <br /> Defines a property to set in [[GVBuffer]]. <br /> <br /> The PropertyDef Element is used by: [[ChangeGVBuffer]], [[GVSavePointNode#SpProperties|SpProperties]], [[JbProperties]], [[Remotemanager-call#RemoteCommandsRemoteCommands|RemoteCommands]].<br /> <br /> The following table shows the PropertyDef element's attributes:<br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | name || required || Property name. <br /> |-<br /> | value || required || Property value. Can contains [[Placeholders|metadata]]<br /> |-<br /> | overwrite-body || optional || If "yes" the [[GVBuffer]] body is overwitten with the GVBuffer's property value or with the current property value, or is set to null.<br /> The body overwrite is execute prior of 'compress', 'crypto' or 'base64' operations.<br /> WARNING!!!!!!! The 'clear-data' operation is still performed invalidating the body overwriting.<br /> The attribute's admitted values are:<br /> * yes<br /> * no<br /> |}<br /> <br /> Might contain the sub-element [[Description]].<br /> <br /> -<br /> <br /> When is used a connection to an HDFS file system these are the PropertyDef based on the type of RemoteCommands:<br /> The following table shows the PropertyDef element's attributes:<br /> {|class="gvtable"<br /> ! RemoteCommand !! Possible Values<br /> |-<br /> | GVDownload || * dfs.file.delete-source [true|false]<br /> * dfs.file.raw-local-filesystem [true|false]<br /> * dfs.stream-buffer-size [default: 8192]<br /> <br /> These parameters can be used to specify the related action when a download operation is used on the HDFS file system. <br /> |-<br /> | GVUpload || * dfs.file.delete-source [true|false]<br /> * dfs.file.overwrite [true|false]<br /> * dfs.permissions.path [Unix-like permission Example: 777]<br /> * dfs.stream-buffer-size<br /> * dfs.replication [default 1:]<br /> * dfs.blocksize [default: 1048576]<br /> * dfs.permissions.user [hdfs user owner]<br /> * dfs.permissions.group [hdfs user group]<br /> These parameters can be used owerwrite the target destination with the source one, set the replication, permissions and the other properties on destination target when a download operation is used on the HDFS file system.<br /> |}</div>

M.deluca https://gvwiki.greenvulcano.com/gvwiki/index.php?title=HDFSRemoteManager&diff=4354 HDFSRemoteManager 2015-01-13T19:58:37Z

<p>M.deluca: /* Description */</p> <hr /> <div>==Description==<br /> <br /> Use this element for encapsulating the parameters required to connect to an Hadoop Distributed File System (HDFS).<br /> <br /> =={{VULCON}} / {{GVCONSOLE}} Configuration==<br /> <br /> If the target directory is on a HDFS file system, you can define the parameters for connection.<br /> <br /> The HDFSRemoteManager Element is used by [[Fsmonitor-call#RemoteFileSystemMonitor|RemoteFileSystemMonitor]] and [[remotemanager-call]]. It has the following attributes:<br /> {|class="gvtable"<br /> ! Attribute !! Type !! Description<br /> |-<br /> | type || fixed || This attribute must assume the value '''remote-manager'''.<br /> |-<br /> | class || fixed || This attribute must assume the value '''it.greenvulcano.util.remotefs.hdfs.HDFSRemoteManager.<br /> |-<br /> | connectionURL || required || Server host name and port to contact HDFS. The entire URI is passed to the FileSystem instance's initialize method. Example: hdfs://[IP_NAME_NOME]:[PORT_NAME_NODE]. [http://wiki.apache.org/hadoop/NameNode] <br /> |-<br /> | username || required || User name used to access to the HDFS file system.<br /> |-<br /> | password || required || User password. #Encrypted<br /> |-<br /> | autoConnect || optional || If true the instance use autoconnect/disconnect at each method invocation. Default: false.<br /> |}</div>

M.deluca https://gvwiki.greenvulcano.com/gvwiki/index.php?title=HDFSRemoteManager&diff=4353 HDFSRemoteManager 2015-01-13T19:28:17Z

<p>M.deluca: /* Description */</p> <hr /> <div>==Description==<br /> <br /> Use this element for encapsulating the parameters required to connect to an Hadoop Distributed File System (HDFS).</div>

M.deluca