Shell-call - Revision history

Anonymous: /* {{VULCON}} / {{GVCONSOLE}} Configuration */

2012-02-24T16:51:55Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

Anonymous: /* {{VULCON}} / {{GVCONSOLE}} Configuration */

2012-02-24T16:51:23Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

Anonymous: /* {{VULCON}} / {{GVCONSOLE}} Configuration */

2012-02-24T16:49:14Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

Anonymous: /* Definition */

2012-02-24T16:38:58Z

‎Definition

Anonymous: /* {{VULCON}} / {{GVCONSOLE}} Configuration */

2012-02-24T16:38:22Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

G.iannello: /* Definition */

2012-02-17T14:27:39Z

‎Definition

Admin: /* {{VULCON}} / {{GVCONSOLE}} Configuration */

2012-02-17T14:03:14Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

Anonymous: /* {{VULCON}} / {{GVCONSOLE}} Configuration */

2012-02-09T09:39:09Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

Anonymous: moved Gvvcl-shell to Shell-call: Il nome del plugin

2012-02-01T21:35:59Z

moved Gvvcl-shell to Shell-call: Il nome del plugin

Anonymous at 11:57, 20 January 2012

2012-01-20T11:57:32Z

@@ Line 24: / Line 24: @@
 Might contain the following sub-elements:
-* [[ShellCommands#cmdcmd]] or [[ShellCommands#cmd-array-elem|md-array-elem]]
+* [[ShellCommands#cmd|cmd]] or [[ShellCommands#cmd-array-elem|cmd-array-elem]]
 * [[ShellCommands#env-property|env-property]]

@@ Line 22: / Line 22: @@
 | encoding || optional || The encoding with which encodes the command output in the [[GVBuffer]] body. If not specified, is used the ''file.encoding'' system property value.
 |}
 The following example shows the configuration generated from {{L_VULCON}} or {{L_GVCONSOLE}} when you configure a ''shell-call'' operation:

← Older revision		Revision as of 16:49, 24 February 2012
Line 36:		Line 36:


−	To use an ''excelreader-call'' in a {{GVESB}} service, you need to define a node of type [[GVOperationNode]] in [[Service ~~section~~]] and define in the field ''operation-name'' the name defined in ''excelreader-call'' operation.	+	To use an ''excelreader-call'' in a {{GVESB}} service, you need to define a node of type [[GVOperationNode]] into the [[Service]] and define in the field ''operation-name'' the name defined in ''excelreader-call'' operation.

	The following example shows the configuration generated from {{L_VULCON}} or {{L_GVCONSOLE}} when you configure an ''shell-call'' operation in {{GVESB}} service:		The following example shows the configuration generated from {{L_VULCON}} or {{L_GVCONSOLE}} when you configure an ''shell-call'' operation in {{GVESB}} service:

@@ Line 1: / Line 1: @@
 ==Definition==
-Many IT applications, within their business process, need to invoke shell commands. ''Gvvcl-shell'' plug-in can be used to invoke a command shell.
+Many IT applications, within their business process, need to invoke shell commands. ''shell-call'' plug-in can be used to invoke a command shell.
 It is very simple to configure.

@@ Line 6: / Line 6: @@
 =={{VULCON}} / {{GVCONSOLE}} Configuration==
-''shell-call'' is the operation that must be configured into {{L_VULCON}} or  {{L_GVCONSOLE}} [[System section]] to invoke command shell.
+''shell-call'' is the operation that must be configured into {{L_VULCON}} or  {{L_GVCONSOLE}} System section to invoke command shell.
 In order to add an operation ''shell-call'' you must define the following fields:

← Older revision		Revision as of 14:03, 17 February 2012
Line 74:		Line 74:

	At this point you have configured a service with a ''shell-call'' operation.		At this point you have configured a service with a ''shell-call'' operation.
−
−	~~--[[User:A.sicignano\|A.sicignano]] 16:30, 19 January 2012 (CET)~~

@@ Line 6: / Line 6: @@
 =={{VULCON}} / {{GVCONSOLE}} Configuration==
-''shell-call'' is the operation that must be configured into {{L_VULCON}} or  {{L_GVCONSOLE}} [[System section]], to invoke command shell
+''shell-call'' is the operation that must be configured into {{L_VULCON}} or  {{L_GVCONSOLE}} [[System section]] to invoke command shell.
 In order to add an operation ''shell-call'' you must define the following fields:
+{|class="gvtable"
-*''class'',it.greenvulcano.gvesb.virtual.shell.ShellCallOperation (java class that manage ''shell-call'' invocation).
+! Attribute !! Type !! Description
-*''name'',this field identify the operation name that you will use in service definition.
+|-
-*''directory'',Pathname of the directory in which the command is executed.This pathname can be static or may contain placeholders that are replaced at runtime.Can contains the following placeholders:
+| type || fixed || This attribute must assume the value '''call'''.
-**fixed : a text string;
+|-
-**<nowiki>${{propname}}</nowiki> =a System property name
+| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.shell.ShellCallOperation''' (java class that manages the ''shell-call'' invocation).
-**<nowiki>timestamp{{pattern}} : return the current timestamp formatted as 'pattern'</nowiki>
+|-
-**<nowiki>dateformat{{date::source-pattern::dest-pattern}} : reformat 'date' from 'source-pattern' to 'dest-pattern'</nowiki>
+| name || required || This field identify the operation name that you will use in service definition.
-**<nowiki>decode{{field[::cond1::val1][::cond2::val2][cond...n::val...n]::default}} : evaluate as if-then-else; if 'field' is equal to cond1...n, return the value of val1...n, otherwise 'default'</nowiki>
+|-
-**<nowiki>decodeL{{sep::field[::cond1::val1][::cond2::val2][cond...n::val...n]::default}} : is equivalent to 'decode', with the difference that 'condX' can be a list of values separated by 'sep'</nowiki>
+| directory || optional ||Pathname of the directory in which the command is executed. This pathname can be static or may contain [[placeholders]] that are replaced at runtime. If this attribute is not present, the command is executed within the current working directory.
-**<nowiki>js{{scope::script}} : evaluate a JavaScript script, using the scope 'scope', the GVBuffer is added to the scope as 'object'</nowiki>
+|-
-**<nowiki>sql{{conn::statement}}  : execute a select sql statement sql and return the value of the first field of the first selected record.  The 'conn' parameter is the JNDI name of a DataSource</nowiki>
+| encoding || optional || The encoding with which encodes the command output in the [[GVBuffer]] body. If not specified, is used the ''file.encoding'' system property value.
-**<nowiki>sqllist{{conn::statement}}: execute a select sql statement sql and return the value of the first field of all selected records as a comma separated list. The 'conn' parameter is the JNDI name of a DataSource</nowiki>
+|}
 The following example shows the configuration generated from {{L_VULCON}} or {{L_GVCONSOLE}} when you configure a ''shell-call'' operation:

← Older revision	Revision as of 21:35, 1 February 2012
(No difference)

@@ Line 31: / Line 31: @@
 <Channel id-channel="CHANNEL-NAME">
      <shell-call class="it.greenvulcano.gvesb.virtual.shell.ShellCallOperation"
-       directory="/home/greenvulcano/script" name="less_file"
+       directory="/home/greenvulcano/script" name="cat_file"
        type="call">
-      <cmd>less greenvulcano.log</cmd>
+      <cmd>cat greenvulcano.log</cmd>
      </shell-call>
 </Channel>
@@ Line 55: / Line 55: @@
                             out-check-type="none" type="operation">
                      <Participant id-channel="CHANNEL-NAME" id-system="SYSTEM-NAME"/>
-                     <Flow first-node="less_log_file" point-x="20" point-y="112">
+                     <Flow first-node="cat_log_file" point-x="20" point-y="112">
                          <GVOperationNode class="it.greenvulcano.gvesb.core.flow.GVOperationNode"
                                           id="shell-call" id-system="YOUR_SYSTEM"
                                           input="input" next-node-id="end"
                                           op-type="call"
-                                          operation-name="less_file"
+                                          operation-name="cat_file"
                                           output="output" point-x="158"
                                           point-y="112" type="flow-node"/>