GVExample TOUPPER A - Revision history

D.franco: /* Defining Workflow Operations */

2014-05-29T13:35:33Z

‎Defining Workflow Operations

D.franco: /* Testing with {{GVCONSOLE}} */

2014-05-29T11:02:59Z

‎Testing with {{GVCONSOLE}}

D.franco: /* Testing with {{GVCONSOLE}} */

2014-05-29T10:58:30Z

‎Testing with {{GVCONSOLE}}

D.franco at 10:18, 29 May 2014

2014-05-29T10:18:51Z

D.franco: /* Defining Workflow Operations */

2014-05-28T16:38:07Z

‎Defining Workflow Operations

A.capaldo: /* Defining Workflow Operations */

2012-10-09T14:48:28Z

‎Defining Workflow Operations

G.iannello: /* Description */

2012-02-20T11:45:02Z

‎Description

G.dimaio at 14:27, 19 February 2012

2012-02-19T14:27:32Z

G.dimaio at 14:13, 19 February 2012

2012-02-19T14:13:27Z

G.dimaio at 11:48, 19 February 2012

2012-02-19T11:48:38Z

@@ Line 114: / Line 114: @@
 ! Node !! Request !! GetReply
 |-
-| GVOperationNode || output="output_JMSEnqueueTo::TOUPPER_A_Req"<br/>id="request"<br/>id-system="GVESB_TEST"<br/>input="input_JMSEnqueueTo::TOUPPER_A_Req"<br/>next-node-id="check_status" op-type="enqueue"<br/>operation-name="JMSEnqueueTo::TOUPPER_A_Req" || output="output_JMSDequeueTo::TOUPPER_A_Resp"<br/>id="request"<br/>id-system="GVESB_TEST"<br/>input="input_JMSDequeueTo::TOUPPER_A_Resp"<br/>next-node-id="check_status" op-type="dequeue"<br/>operation-name="JMSDequeueTo::TOUPPER_A_Resp"<br/>DequeueFilter:
+| [[GVOperationNode]] || output="output_JMSEnqueueTo::TOUPPER_A_Req"<br/>id="request"<br/>id-system="GVESB_TEST"<br/>input="input_JMSEnqueueTo::TOUPPER_A_Req"<br/>next-node-id="check_status" op-type="enqueue"<br/>operation-name="JMSEnqueueTo::TOUPPER_A_Req" || output="output_JMSDequeueTo::TOUPPER_A_Resp"<br/>id="request"<br/>id-system="GVESB_TEST"<br/>input="input_JMSDequeueTo::TOUPPER_A_Resp"<br/>next-node-id="check_status" op-type="dequeue"<br/>operation-name="JMSDequeueTo::TOUPPER_A_Resp"<br/>[[Op-type#DequeueFilter|DequeueFilter]]:
-: IDFilter
+: [[Op-type#IDFilter|IDFilter]]
 :: enabled="yes" use-input="yes"
 |-
-| GVNodeCheck || default-id="return_status"<br/>id="check_status"<br/>input="output_JMSEnqueueTo::TOUPPER_A_Req"<br/>on-exception-id="return_error"<br/>op-type="check" || default-id="return_status"<br/>id="check_status"<br/>input="output_JMSDequeueTo::TOUPPER_A_Resp"<br/>on-exception-id="return_error"<br/>op-type="check"
+| [[GVNodeCheck]] || default-id="return_status"<br/>id="check_status"<br/>input="output_JMSEnqueueTo::TOUPPER_A_Req"<br/>on-exception-id="return_error"<br/>op-type="check" || default-id="return_status"<br/>id="check_status"<br/>input="output_JMSDequeueTo::TOUPPER_A_Resp"<br/>on-exception-id="return_error"<br/>op-type="check"
 |-
-| GVEndNode || id="return_status"<br/>op-type="end"<br/>output="output_JMSEnqueueTo::TOUPPER_A_Req" || id="return_status"<br/>op-type="end"<br/>output="output_JMSDequeueTo::TOUPPER_A_Resp"
+| [[GVEndNode]] || id="return_status"<br/>op-type="end"<br/>output="output_JMSEnqueueTo::TOUPPER_A_Req" || id="return_status"<br/>op-type="end"<br/>output="output_JMSDequeueTo::TOUPPER_A_Resp"
 |-
-| GVEndNode || id="return_error"<br/>output="output_JMSEnqueueTo::TOUPPER_A_Req" || id="return_error"<br/>output="output_JMSDequeueTo::TOUPPER_A_Resp"
+| [[GVEndNode]] || id="return_error"<br/>output="output_JMSEnqueueTo::TOUPPER_A_Req" || id="return_error"<br/>output="output_JMSDequeueTo::TOUPPER_A_Resp"
 |}
@@ Line 130: / Line 130: @@
 ! Nodes/Subelements !! Attributes
 |-
-| GVOperationNode || id-system="GVESB_TEST"<br/>  input="input"<br/> next-node-id="enqueue_response" op-type="call"<br/>  operation-name="toupper_call" output="output"
+| [[GVOperationNode]] || id-system="GVESB_TEST"<br/>  input="input"<br/> next-node-id="enqueue_response" op-type="call"<br/>  operation-name="toupper_call" output="output"
 |-
-| GVOperationNode || id="enqueue_response" id-system="GVESB_TEST"<br/>  input="output" next-node-id="end"<br/> op-type="enqueue"<br/> operation-name="JMSEnqueueTo::TOUPPER_A_Resp"<br/>  output="output"
+| [[GVOperationNode]] || id="enqueue_response" id-system="GVESB_TEST"<br/>  input="output" next-node-id="end"<br/> op-type="enqueue"<br/> operation-name="JMSEnqueueTo::TOUPPER_A_Resp"<br/>  output="output"
 |-
-| GVEndNode || end-business-process="no" id="end" op-type="end"<br/>  output="output" <br/> ChangeGVBuffer: clear-data="true"
+| [[GVEndNode]] || end-business-process="no" id="end" op-type="end"<br/>  output="output" <br/> ChangeGVBuffer: clear-data="true"
 |}
@@ Line 141: / Line 141: @@
 <syntaxhighlight lang="XML">
 <ForwardConfiguration dump-message="true" enabled="true"
-                       forwardName="FWD_TOUPPER_A"
+                       forwardName="FWD_TOUPPER_A" name="ToupperA"
                        ref-dp="ReadString_JMSBytesMessageDataProvider">
      <ForwardDeployment connection-factory="java:/XAConnectionFactory"

@@ Line 315: / Line 315: @@
 [[File:GVConsoleTesting.jpg|thumb|{{GVCONSOLE}} Testing section]]Go to the {{GVCONSOLE}} section [[Testing]]. In this section you can finally test your new service. Remember that Service TOUPPER_A is composed by three independent Operations:
-'''Request'''
+*'''Request'''
 # Into the Service field select TOUPPER_A
 # Into the System field select GVESB_TEST
@@ Line 321: / Line 321: @@
 # Click Request
-The '''FWD_TOUPPER_A''' is executed by {{GVESB}} [[GVForwards|JMS Forward]].
+*'''FWD_TOUPPER_A''', executed by {{GVESB}} [[GVForwards|JMS Forward]].
-'''getReply'''
+*'''getReply'''
 # Clear the Payload area
 # Click getReply

@@ Line 303: / Line 303: @@
 The section [[Deploy_Service|Deploy Services]] will be open. In this section you can select the services you want to deploy.
-# Clicking on service TOUPPER_A a new view will be showed containing the files GVCore.xml present in local and on server side.
+# Selecting the TOUPPER_A service a new view will be shown. In this view is the contents of the file GVCore.xml in the local version and the one on the server.
 # Click Deploy. Now you can save the document and write some notes about it.
 # Save the Document. By saving you will return to the [[Deploy Service]] section.
@@ Line 309: / Line 309: @@
 [[File:GVConsoleUtilityReload1.jpg|thumb|{{GVCONSOLE}} Utility section]]Now pass to the {{GVCONSOLE}} section [[Utility]].
 # Click on [[Reload_Configuration|Reload configuration]]
-# Select GVCore.xml and GVAdapter.xml, then Reload. A new windows will be open to confirm the operation
+# Select GVCore.xml and GVAdapter.xml, then Reload.
-# Click OK.
+# Finally confirm the operation.
@@ Line 327: / Line 327: @@
 # Click getReply
-When each test completes, the Testing view will be expanded for containing the GVBUFFER OUTPUT. In this case no properties have been defined so there are only be presents the main informations about the process (System, Service, Id, etc.). To view the service payload output click on ''Show as Text'' button. Standard fields and the detailed GVBuffer are described in the [[Testing#Data_input|Output File Name]] (the default location is <nowiki>$GV_HOME</nowiki>/log/TestOutput.txt).
+When each test completes, the Testing view will be expanded for containing the GVBUFFER OUTPUT. In this case no properties have been defined, thus only main informations about the process (System, Service, Id, etc.) are shown. To view the service payload output click on ''Show as Text'' button. Standard fields and the detailed GVBuffer are described in the [[Testing#Data_input|Output File Name]] (the default location is <nowiki>$GV_HOME</nowiki>/log/TestOutput.txt).
-In case of error or exceptions you can review the logs file present in the folder <nowiki>$GV_HOME</nowiki>/log/.
+In case of error or exceptions you can review the logs file in the <nowiki>$GV_HOME</nowiki>/log/ folder.

@@ Line 114: / Line 114: @@
 ! Node !! Request !! GetReply
 |-
-| GVOperationNode || output: output_JMSEnqueueTo::TOUPPER_A_Req<br/>id="request"<br/>id-system="GVESB_TEST"<br/>input="input_JMSEnqueueTo::TOUPPER_A_Req"<br/>next-node-id="check_status" op-type="enqueue"<br/>operation-name="JMSEnqueueTo::TOUPPER_A_Req" || output: "output_JMSDequeueTo::TOUPPER_A_Resp"<br/>id="request"<br/>id-system="GVESB_TEST"<br/>input="input_JMSDequeueTo::TOUPPER_A_Resp"<br/>next-node-id="check_status" op-type="dequeue"<br/>operation-name="JMSDequeueTo::TOUPPER_A_Resp"<br/>DequeueFilter:
+| GVOperationNode || output="output_JMSEnqueueTo::TOUPPER_A_Req"<br/>id="request"<br/>id-system="GVESB_TEST"<br/>input="input_JMSEnqueueTo::TOUPPER_A_Req"<br/>next-node-id="check_status" op-type="enqueue"<br/>operation-name="JMSEnqueueTo::TOUPPER_A_Req" || output="output_JMSDequeueTo::TOUPPER_A_Resp"<br/>id="request"<br/>id-system="GVESB_TEST"<br/>input="input_JMSDequeueTo::TOUPPER_A_Resp"<br/>next-node-id="check_status" op-type="dequeue"<br/>operation-name="JMSDequeueTo::TOUPPER_A_Resp"<br/>DequeueFilter:
 : IDFilter
 :: enabled="yes" use-input="yes"
@@ Line 130: / Line 130: @@
 ! Nodes/Subelements !! Attributes
 |-
-| GVOperationNode || id-system="GVESB"<br/>  input="input"<br/> next-node-id="enqueue_response" op-type="call"<br/>  operation-name="toupper_call" output="output"
+| GVOperationNode || id-system="GVESB_TEST"<br/>  input="input"<br/> next-node-id="enqueue_response" op-type="call"<br/>  operation-name="toupper_call" output="output"
 |-
-| GVOperationNode || id="enqueue_response" id-system="GVESB"<br/>  input="output" next-node-id="end"<br/> op-type="enqueue"<br/> operation-name="JMSEnqueueTo::TOUPPER_A_Resp"<br/>  output="output"
+| GVOperationNode || id="enqueue_response" id-system="GVESB_TEST"<br/>  input="output" next-node-id="end"<br/> op-type="enqueue"<br/> operation-name="JMSEnqueueTo::TOUPPER_A_Resp"<br/>  output="output"
 |-
 | GVEndNode || end-business-process="no" id="end" op-type="end"<br/>  output="output" <br/> ChangeGVBuffer: clear-data="true"
@@ Line 156: / Line 156: @@
           service-activation="on" statistics="off">
      <Operation name="Request" operation-activation="on"
-                out-check-type="sys-svc-tid" type="operation">
+                out-check-type="sys-svc-id" type="operation">
           <Description>VulCon generated Operation</Description>
           <Participant id-channel="TEST_CHANNEL_A" id-system="GVESB_TEST"/>
@@ Line 183: / Line 183: @@
       </Operation>
       <Operation name="GetReply" operation-activation="on"
-                 out-check-type="sys-svc-tid" type="operation">
+                 out-check-type="sys-svc-id" type="operation">
           <Description>VulCon generated Operation</Description>
           <Participant id-channel="TEST_CHANNEL_A" id-system="GVESB_TEST"/>
@@ Line 205: / Line 205: @@
                            point-x="350" point-y="150" type="flow-node"/>
               <GVEndNode class="it.greenvulcano.gvesb.core.flow.GVEndNode"
-                         id="return_status" op-type="end" output="output_null"
+                         id="return_status" op-type="end"
                          point-x="700" point-y="150" type="flow-node"/>
               <GVEndNode class="it.greenvulcano.gvesb.core.flow.GVEndNode"
@@ Line 216: / Line 217: @@
                 operation-activation="on" out-check-type="none"
                 type="operation">
-          <Participant id-channel="TEST_CHANNEL_A" id-system="GVESB"/>
+          <Participant id-channel="TEST_CHANNEL_A" id-system="GVESB_TEST"/>
           <Flow first-node="call_server" point-x="20" point-y="150">
                <GVOperationNode class="it.greenvulcano.gvesb.core.flow.GVOperationNode"
-                                id="call_server" id-system="GVESB" input="input"
+                                id="call_server" id-system="GVESB_TEST" input="input"
                                 next-node-id="enqueue_response" op-type="call"
                                 operation-name="toupper_call" output="output"
                                 point-x="147" point-y="148" type="flow-node"/>
                <GVOperationNode class="it.greenvulcano.gvesb.core.flow.GVOperationNode"
-                                id="enqueue_response" id-system="GVESB"
+                                id="enqueue_response" id-system="GVESB_TEST"
                                 input="output" next-node-id="end"
                                 op-type="enqueue"
@@ Line 261: / Line 262: @@
                         destination-type="queue"
                         name="JMSEnqueueTo::TOUPPER_A_Resp" priority="4"
                         transacted="false" type="enqueue">
                    <XAHelper auto-enlist="false" transaction-status="TMSUCCESS"/>
@@ Line 271: / Line 273: @@
                         name="JMSDequeueTo::TOUPPER_A_Resp"
                         receive-timeout-overridable="false"
-                        receive-type="timeout" transacted="false" type="dequeue">
+                        receive-type="timeout"
                    <XAHelper auto-enlist="false" transaction-status="TMSUCCESS"/>
             </jms-dequeue>

@@ Line 68: / Line 68: @@
 ! Plugin !! Value
 |-
-| [[jms-enqueue]] || connection-factory="java:/XAConnectionFactory"<br/>destination-name="gvesb/jms/queue/TOUPPER_A_Request_Queue"<br/>name="JMSEnqueueTo::TOUPPER_A_Req"<br/>                            ref-dp="WriteString_JMSBytesMessageDataProvider"<br/>XAHelper
+| [[jms-enqueue]] || connection-factory="java:/XAConnectionFactory"<br/>delivery-mode="persistent"<br/>destination-name="gvesb/jms/queue/TOUPPER_A_Request_Queue"<br/>name="JMSEnqueueTo::TOUPPER_A_Req"<br/>                            ref-dp="WriteString_JMSBytesMessageDataProvider"
 |-
-| [[jms-enqueue]] || connection-factory="java:/XAConnectionFactory"<br/>delivery-mode="persistent"<br/>destination-name="gvesb/jms/queue/TOUPPER_A_Response_Queue"<br/>name="JMSEnqueueTo::TOUPPER_A_Resp"<br/>                            ref-dp="WriteString_JMSBytesMessageDataProvider"<br/>XAHelper
+| [[jms-enqueue]]/[[XAHelper]] || auto-enlist="false"<br/>transaction-status="TMSUCCESS"<br/>(You can find XAHelper section by adding it on the queue)
 |-
-| [[jms-dequeue]] || connection-factory="java:/XAConnectionFactory"<br/>delivery-mode="persistent"<br/>destination-name="gvesb/jms/queue/TOUPPER_A_Response_Queue"<br/>name="JMSDequeueTo::TOUPPER_A_Resp"<br/>                            ref-dp="ReadString_JMSBytesMessageDataProvider"<br/> receive-type="timeout"<br/>XAHelper
+| [[jms-enqueue]] || connection-factory="java:/XAConnectionFactory"<br/>delivery-mode="persistent"<br/>destination-name="gvesb/jms/queue/TOUPPER_A_Response_Queue"<br/>name="JMSEnqueueTo::TOUPPER_A_Resp"<br/>                            ref-dp="WriteString_JMSBytesMessageDataProvider"
-: auto-enlist="false"
+|-
-: transaction-status="TMSUCCESS"
+| [[jms-enqueue]]/[[XAHelper]] || auto-enlist="false"<br/>transaction-status="TMSUCCESS"
 |-
 | [[test-service-call]] || name="toupper_call" service="toupper"
 |}
-The ''WriteString_JMSBytesMessageDataProvider'' creates a JMS BytesMessage and write in its body the expected input java.lang.String converted to byte[].<br/>The ''ReadString_JMSBytesMessageDataProvider'' extract the input JMS BytesMessage body as byte[] then convert it into a java.lang.String.<br/>Check that [[Data provider|Data Providers]] ''WriteString_JMSBytesMessageDataProvider'' and ''ReadString_JMSBytesMessageDataProvider'' will be present in the element DataProviders (JMSBytesMessageDataProvider and StringDataProvider respectively), visualized from the {{VULCON}} Adapter view. If don't, you can add it setting their attributes as seen in the following table:
+The ''WriteString_JMSBytesMessageDataProvider'' creates a JMS BytesMessage and write in its body the expected input java.lang.String converted to byte[].<br/>
 {|class="gvtable"
 ! Data Provider !! Value
 |-
-| [[Data provider|JMSBytesMessageDataProvider]] || name="WriteString_JMSBytesMessageDataProvider"<br/>Field:
+| [[Data provider|JMSBytesMessageDataProvider]] || name="WriteString_JMSBytesMessageDataProvider"
-: direction="OUT" key="output" type="field">
+|-
-: Expression: type="ognl"
+| [[Data provider|JMSBytesMessageDataProvider]]/[[Field]] || direction="OUT"<br/>key="output"<br/>type="field"
-:: writeBytes(#input.object.getBytes('UTF-8'))
+|-
 |-
-| [[Data provider|StringDataProvider]] || name="ReadString_JMSBytesMessageDataProvider"<br/>Field:
+| [[Data provider|StringDataProvider]]/Expression || type="ognl"<br/>#bArr = new byte[object.getBodyLength()], object.reset(), object.readBytes(#bArr), new java.lang.String(#bArr, 'UTF-8')
 |}

@@ Line 2: / Line 2: @@
 This simple example shows how to configure an asynchronous service with a [[GVForwards|JMS Forward]] .
-The Service TOUPPER_A is composed of three workflow that defines the Client/ESB/Server interaction:
+The Service TOUPPER_A is composed of three workflows that define the Client/ESB/Server interaction:
-# the Client invoke the ''Request'' workflow to enqueue the input data into a request queue
+# the Client invokes the ''Request'' workflow to enqueue the input data into a request queue
-# the [[GVForwards|JMS Forward]] (a {{GVESB}} component), listening on the request queue, extract the JMS message and invoke the ''FWD_TOUPPER_A'' workflow that convert the payload to uppercase (simulate a Server invocation) then enqueue the new payload into a response queue
+# the [[GVForwards|JMS Forward]] (a {{GVESB}} component), listening on the request queue, extracts the JMS message and invokes the ''FWD_TOUPPER_A'' workflow that converts the payload to uppercase (simulate a Server invocation) then enqueues the new payload into a response queue
-# the Client invoke the ''getReply'' workflow to dequeue the output data from a response queue
+# the Client invokes the ''getReply'' workflow to dequeue the output data from a response queue
 ==How To==

@@ Line 11: / Line 11: @@
 The preferred mode for creating a Service (at least its skeleton) is through the Service Wizard. Before using it you must first configure the JMS Queue and the VCL plugins to interact with the JMS queuea and execute the uppercase conversion. So let's define a new Group, System and Channel, if you do not want to use those already present, and then start the Wizard.
-===Configuring a queue in JBoss===
+===Configuring JMS queues in JBoss===
-The queues are configured in JBoss by an XML file, ''gvesb-mq-destinations-service.xml'' present in <nowiki>$GV_HOME</nowiki>/application/deploy.
+The JMS queues are configured in JBoss by an XML file, ''gvesb-mq-destinations-service.xml'' present in <nowiki>$GV_HOME</nowiki>/application/deploy.
 A queue has:

@@ Line 10: / Line 10: @@
 The preferred mode for creating a Service (at least its skeleton) is through the Service Wizard. Before using it you must first configure the JMS Queue and the VCL plugins to interact with the JMS queuea and execute the uppercase conversion. So let's define a new Group, System and Channel, if you do not want to use those already present, and then start the Wizard.
 ===Configuring a queue in JBoss===
@@ Line 59: / Line 48: @@
 </mbean>
 </syntaxhighlight>
 ===Defining Workflow Operations===
@@ Line 286: / Line 287: @@
 ===Testing with {{GVCONSOLE}}===
-It is finally arrived the time to test your project. To do that execute the following steps:
+It is finally the time to test your project. To do that execute the following steps:
 [[File:GVCONSOLEDeploy.jpg|thumb|Deploy new Service]]Suppose you have saved the {{VULCON}} project as <nowiki>"${{gv.app.home}}/TEST/REPG1.zip"</nowiki>. To deploy the new Service follow this steps:
@@ Line 305: / Line 306: @@
-[[File:GVConsoleTesting.jpg|thumb|{{GVCONSOLE}} Testing section]]Go to the {{GVCONSOLE}} section [[Testing]]. In this section you can finally test your new service. Remember that Service TOUPPER_A is divided by three independent Operations:
+[[File:GVConsoleTesting.jpg|thumb|{{GVCONSOLE}} Testing section]]Go to the {{GVCONSOLE}} section [[Testing]]. In this section you can finally test your new service. Remember that Service TOUPPER_A is composed by three independent Operations:
 '''Request'''
-# Into the Service voice select TOUPPER_A
+# Into the Service field select TOUPPER_A
-# Into the System voice select GVESB_TEST
+# Into the System field select GVESB_TEST
-# Into Payload enter a sentence (we wrote "La vitta è bella")
+# Into the Payload area insert the text to convert in uppercase
 # Click Request
 '''getReply'''
-# Click getReply.
+# Clear the Payload area
-'''FWD_TOUPPER_A'''
+# Click getReply
-When each test finishes, the Testing view will be expanded for containing the GVBUFFER OUTPUT. In this case no properties have been defined so there are only be presents the main informations about the process (System, Service, Id, etc.). Standard fields and the detailed GVBuffer are described in the [[Testing#Data_input|Output File Name]] (we setted it as <nowiki>${{gv.app.home}}</nowiki>/log/TestOutput.txt).
+When each test completes, the Testing view will be expanded for containing the GVBUFFER OUTPUT. In this case no properties have been defined so there are only be presents the main informations about the process (System, Service, Id, etc.). To view the service payload output click on ''Show as Text'' button. Standard fields and the detailed GVBuffer are described in the [[Testing#Data_input|Output File Name]] (the default location is <nowiki>$GV_HOME</nowiki>/log/TestOutput.txt).
-In case of error or exceptions you can review the logs file presents in the folder <nowiki>${{gv.app.home}}</nowiki>/log/.
+In case of error or exceptions you can review the logs file present in the folder <nowiki>$GV_HOME</nowiki>/log/.