GVExample TestProperty

Description

TestProperty service shows the use of the various metadata. This example is limited to create some properties and set its value with the scope of illustrating how metadata can be used. But shows also how to construct the possible properties that you will need in more complex flows.

For more information about metadata (or placeholders) click here.

VulCon Configuration

The Service TestProperty can be configured using the VulCon Editor View. The following list enumerates the configuration steps.

1. By commodity, we will use an existing Group, in this case DEFAULT_GRP group. But is also possible create a new one if your project needed.
2. Create a new Service: From the VulCon Core View, right clicking on Services, insert-after -> Service. A new element Service will be created.
3. Set the Service parameters in the Properties panel. We setted:
   • group-name as DEFAULT-GRP
   • id-service as TestProperty
4. Insert a new Operation: Right click the new Service element -> Insert after -> Operation. A new element Operation will be created.
5. Set the Operation attributes: We setted the attribute name as Request.
6. Add a Participant: Right clicking the operation element -> Insert after -> Participant. A new Participant element will be created.
7. Set the parameters value for Participant: Click on the new Participant element. From the Properties view set:
   • id-System as GVESB
   • id-channel as TEST_CHANNEL
8. Finally, open the editor: Right click the element Operation -> Open Editor. A new window will be open into the VulCon Editor View with the Start Node.

Now we are able to configure our flow from the Editor View. Expand the Palette if it is not already visible from the Editor View. This can be done by clicking into a little arrow head present into the Editor right top corner. The steps are:

1. Add a ChangeGVBuffer Node:
   1. From the Palette drag and drop into the editor a ChangeGVBuffer Node.
      

      Adding a ChangeGVBuffer Node
      A new windows will be open where you can set the element id and its input GVBuffer name. In this example we set
   • id: test_property
   • input: data
     Then -> Next
   1. Choose the Virtual Layer Operation you need: in this case we add a ChangeGVBuffer. Then -> Next
   2. You can also set an Operation Level 2: As we want to define some Properties, we select a PropertyDef.
   3. Set the property name as SQL and the value as sql{{ds.gv_test::select 'OK' from dual}}. Then -> Finish.
2. Add an End Node:
   1. From the Palette drag and drop into the editor a EndNode Node. A new windows will be open where you can set the element id. In this example we set
   • id: end.
     Then -> Finish
3. Create the connections:
   1. From the Palette click into the Default Connection (black arrow)
   2. Create a connection between the Star Node and test_property ChangeGVBuffer Node. This is done by clicking first the Start Node and then the test_property node.
   3. Create another Default Connection between test_property ChangeGVBuffer Node and end node.
4. Save the Editor in the Eclipse Main Menu.

The flow is already created. We added more properties in order to illustrate some GreenVulcano^® ESB Placeholders. You can add more PropertyDef elements by right clicking the ChangeGVBuffer element present in the ChangeGVBufferNode -> Insert After -> PropertyDef. The defined properties are:

PropertyDef name	value
SQL	sql{{ds.gv_test::select 'OK' from dual}}
SQLLIST	[sqllist{{ds.gv_test::select name from city order by 1}}]
TIMESTAMP	timestamp{{yyyyMMdd HH:mm:ss}}
OGNL	Service: ognl{{#object.getService()}}
JAVASCRIPT	System: js{{gvesb::object.getSystem()}}
SYSTEM	Server Name: ${{jboss.server.name}}
CLASS	%{{fqclass}}
DECODE	decode{{ognl{{#object.getProperty('SQL')}}::OK::Sql OK::Sql KO}}
MINUTE	Minute decode{{js{{gvesb::timestamp{{mm}} % 2 == 0}}::true::EVEN::ODD}}

TestProperty configuration

Before finishing you must control that the VulCon Configuration has not errors. Errors are indicated by a red cross into the element icon.

1. As we can see, it is present an error in the end node. Clicking this element we realize that is missing the output field.
2. Set the parameter output as the output of the preceding node, that of test_property node.
3. On clicking test_property element we see that the output has been setted automatically to output_1. You can change this value or set it if is not present. We changed it to output.
4. Set the end element attribute output as output too.
5. Save your changes using the Save icon present in the Core View.

Now your Service TestProperty will be configured as seen in the following picture.