Difference between revisions of "GVExample CCardQuery"

From GreenVulcano Wiki
Jump to: navigation, search
(→‎Defining Systems, Channels and Operations)
Line 138: Line 138:
 
| GVEndNode || end-business-process="yes"  <br/>id="end"  <br/>op-type="end"  <br/>output="output"
 
| GVEndNode || end-business-process="yes"  <br/>id="end"  <br/>op-type="end"  <br/>output="output"
 
|}
 
|}
 +
 +
=={{GVCONSOLE}} Configuration==
 +
 +
It is time to deploy and test your new Service. To do that follows these steps:
 +
 +
[[File:GVCONSOLEDeploy.jpg|thumb|Deploy new Service]]Suppose you have saved the {{VULCON}} Configuration file as <nowiki>"${{gv.app.home}}/TEST/REPG1.zip"</nowiki>. To deploy the new Service follow this steps:
 +
# [[Starting|Start {{GVESB}}]]
 +
# [[GV_Console#Access|Access to the {{GVCONSOLE}}]].
 +
# In the Deploy New Service section click Sfoglia... (Browse) and select the file where you have saved the {{VULCON}} configuration.
 +
#`Click Submit.
 +
 +
The section [[Deploy_Service|Deploy Services]] will be open. In this section you can select the services you want to deploy.
 +
# Clicking on service CCardQuery a new view will be open containing the files GVCore.xml present in local and in server.
 +
# Click Deploy. Now you can save the document and write some notes about it.
 +
# Save the Document. Saving you return to the [[Deploy Service]] section.
 +
 +
[[File:GVConsoleUtilityReload1.jpg|thumb|{{GVCONSOLE}} Utility section]]Now pass to the {{GVCONSOLE}} section [[Utility]].
 +
# Click on [[Reload_Configuration|Reload configuration]]
 +
# Select GVCore.xml and GVAdapters.xml and then Reload. A new windows will be open to confirm the operation
 +
# Click OK.
 +
 +
[[File:GVConsoleTesting.jpg|thumb|{{GVCONSOLE}} Testing section]]Go to the {{GVCONSOLE}} section [[Testing]]. In this section you can finally test your new services:
 +
# Into the Service voice select CCardQuery
 +
# Into the System voice select CREDIT_EXTERNAL
 +
# Select the Payload on input containing the credit card number you want to test
 +
# Click RequestReply
 +
 +
The Testing View will be expanded and it is also possible to view the GVBuffer Output panel where there are present some properties, among these the REC_READ property setted to 1, representing the number of record read from DB.
 +
 +
The file TestOutput.txt will be generated in the directory <nowiki>${{gv.app.home}}</nowiki>/log as previously setted (see [[Testing]], [[data input]] area) containing information about owner, credit and state of the credit card number "1234123415555666" as passed in input.
 +
<syntaxhighlight lang="XML">
 +
<pre>
 +
----------- TEST N. 0 2012.02.15 at 11:46:26 -----------
 +
Standard Field:
 +
system  = CREDIT_EXTERNAL
 +
service  = CCardQuery
 +
id      = 7F0001014F3B87B900021429
 +
retCode  = 0
 +
GVBuffer: class org.apache.xerces.dom.DocumentImpl
 +
<?xml version="1.0" encoding="UTF-8"?>
 +
  <QueryResponse xmlns="http://www.credit.com/services">
 +
    <name>MARIO BIANCHI</name>
 +
    <cnumber>1234123415555666</cnumber>
 +
    <credit>300.00000</credit>
 +
    <active>true</active>
 +
  </QueryResponse>
 +
Properties:
 +
REC_DISCARD = 0
 +
IS_INTERNAL = true
 +
REC_TOTAL = 0
 +
REC_UPDATE = 0
 +
REC_INSERT = 0
 +
REC_READ = 1
 +
CNUMBER = 1234123415555666
 +
REC_DISCARD_CAUSE =
 +
</pre>
 +
</syntaxhighlight>

Revision as of 12:18, 15 February 2012

Description

This service has the scope of showing how GreenVulcano® ESB uses DataHandler for quering a DB and implements a Web Services.

CCardQuery Service executes the following operations:

  1. Receives a request Web Service from client, with a credit card number to be controlled.
  2. If this card is locally managed, reads the data using DataHandler.
  3. If this card is managed by an external system, forwards a Web Service request to that system.
  4. Returns the response to the client

VulCon Configuration

To configure CCardQuery service follow these steps:

  1. Define Systems, Channels and Operations
  2. Define the Services
  3. Implement the flows.

Defining Systems, Channels and Operations

To define a System, go to VulCon core view and insert the System CREDIT with the Channel CHANNEL_CREDIT_WS, with the following operations:

Attribute Value
name DataHandler
DBOBuilder name="CREDIT::CCardQuery"
jdbc-connection-name="ds.test_gv"

DHVariables:

name="decimal-separator" value="."
name="grouping-separator" value=","
name="format" value="#0.00"
DBOBuilder/ DBOSelect name="CCardQuery"
transformation="CCardQuery"
type="dbo"
statement id="1"

type="select" 

select p.NAME, cc.CNUMBER, cc.CREDIT, cc.ENABLED
from PERSON p, CREDIT_CARD cc
where p.ID = cc.ID_OWNER
and cc.CNUMBER = @{{CNUMBER}}

The operation defined in the DataHandler makes use of the data-transformation module for the data transformations that allow to have data in XML format. So, you need to define the following parameters into the GVDataTransformation section:

Attribute Value
DataSourceSet/LocalFSDataSource formatHandled="xsl" name="XSLDataSource"
repositoryHome="${{gv.app.home}}/gvdte/datasource/xsl"
type="datasource"
XSLTransformation name="CCardQuery" DataSourceSet="Default"
XSLMapName="DataHandler/CREDIT/CCardQuery.xsl"
type="transformation"
XSLTransformation name="QueryExternalInput" DataSourceSet="Default"
XSLMapName=" CREDIT_EXTERNAL/QueryExternalInput.xsl"
type="transformation"
XSLTransformation name="QueryExternalOutput" DataSourceSet="Default"
XSLMapName=" CREDIT_EXTERNAL/QueryExternalOutput.xsl"
type="transformation"

Now insert the Service CREDIT_EXTERNAL with the Channel CHANNEL_CREDIT_EXT with the following operations:

Attribute Value
Name QueryExternal
AxisWebServiceInvoker operation="Query"
ref-dp="EXTERNAL::QueryWSDataProvider"
returnType="body-element"
type="invoker"
WSDLInfo:
type="wsdlinfo"
wsdl="file://${{gv.app.home}}/xmlconfig/wsdl/ExternalCreditService.wsdl"

Note that the easiest way to configure a Web service with VulCon® is using the Wizard. We start from a Web Service WSDL, that describes a withdrawal operation on a credit card.

From the Core view of VulCon®, right clicking the Services element, launch the Wizard Call Web Service and, after selecting the WSDL file -in this example we use ExternalCreditService.wsdl present in folder ${{gv.app.home}}/xmlconfig/wsdl-, choose the parameters to create the GreenVulcano® ESB service.

After that you can modify your workflow through VulCon® Palette and set the elements as will be described in the section Flow implementation.

Definition of Services

To define the CCardQuery Service, use the voice "Wizard new Service" (Right clicking the element Services) and set the following parameters:

Attribute Value
Service name CCardQuery
Group CREDIT_GRP
Scenario Synchronous- Synchronous
Server (Participant) system="CREDIT"
channel="CHANNEL_CREDIT_WS"
request operation= "DataHandler"

A new Flow has been created and must be modified in its main steps. But first it is also needed to add a Participant with the attributes:

  • system="CREDIT_EXTERNAL"
  • channel="CHANNEL_CREDIT_EXT"

Flow implementation

CCardQuery flow

To define the CCardQuery service Flow design it as shown in the picture:


The service receives a Web Service request from a client with a credit card number. If this card is managed locally, reads its data using Data Handler, otherwise forwards the request to an external system using Web Service.


The following table shows the parameters to be defined for each operations of the Flow:

Attribute Value
first-node Prepare
Conditions/GVBufferCondition condition="isInternalCCard"
Property:
name="IS_INTERNAL" operator="equal"
type="gvbuffer-field"
value="true"
value-type="text"
ChangeGVBufferNode dump-in-out="true"
id="prepare"
input="input"
next-node-id="check_internal"
clear-data="false"
PropertyDef:
name="CNUMBER"
value="js{{gvesb::var doc=XMLUtils.parseDOM_S(new java.lang.String(object.getObject()),false,true); XMLConfig.get(doc,'//cred:cnumber')}}"

PropertyDef:

name="IS_INTERNAL"
value="sql{{ds.test_gv::select decode(count(*), 1, 'true', 'false') from credit_card where number=ognl{{#object.getProperty('CNUMBER')}}}}"
GVRouting condition="isInternalCCard"
next-node-id="search_internal"
GVOperationNode dump-in-out="false"
id="search_internal"
id-system="CREDIT"
input="input"
next-node-id="end"
op-type="call"
operation-name="DataHandler"
output="output"
GVOperationNode dump-in-out="false"
id="search_external"
id-system="CREDIT_EXTERNAL"
input="input"
next-node-id="end"
op-type="call"
operation-name="QueryExternal"
InputServices:
gvdte-service
crtical="yes", internal="yes"
remove-fields="yes" type="service"
map-name-param:name="map-name" type="param"
value="QueryExternalInput”
name="QueryExternalInput

OutputServices:

gvdte-service:
critical="yes" internal="yes"
remove-fields="yes" type="service"
map-name-param:
name="map-name" type="param"
value="QueryExternalOutput"
name="QueryExternalOutput"
GVEndNode end-business-process="yes"
id="end"
op-type="end"
output="output"

GV Console Configuration

It is time to deploy and test your new Service. To do that follows these steps:

Deploy new Service

Suppose you have saved the VulCon Configuration file as "${{gv.app.home}}/TEST/REPG1.zip". To deploy the new Service follow this steps:

  1. Start GreenVulcano® ESB
  2. Access to the GV Console.
  3. In the Deploy New Service section click Sfoglia... (Browse) and select the file where you have saved the VulCon configuration.
  4. `Click Submit.

The section Deploy Services will be open. In this section you can select the services you want to deploy.

  1. Clicking on service CCardQuery a new view will be open containing the files GVCore.xml present in local and in server.
  2. Click Deploy. Now you can save the document and write some notes about it.
  3. Save the Document. Saving you return to the Deploy Service section.
GV Console Utility section

Now pass to the GV Console section Utility.

  1. Click on Reload configuration
  2. Select GVCore.xml and GVAdapters.xml and then Reload. A new windows will be open to confirm the operation
  3. Click OK.
GV Console Testing section

Go to the GV Console section Testing. In this section you can finally test your new services:

  1. Into the Service voice select CCardQuery
  2. Into the System voice select CREDIT_EXTERNAL
  3. Select the Payload on input containing the credit card number you want to test
  4. Click RequestReply

The Testing View will be expanded and it is also possible to view the GVBuffer Output panel where there are present some properties, among these the REC_READ property setted to 1, representing the number of record read from DB.

The file TestOutput.txt will be generated in the directory ${{gv.app.home}}/log as previously setted (see Testing, data input area) containing information about owner, credit and state of the credit card number "1234123415555666" as passed in input. 

<pre>
----------- TEST N. 0 2012.02.15 at 11:46:26 -----------
Standard Field:
	system   = CREDIT_EXTERNAL
	service  = CCardQuery
	id       = 7F0001014F3B87B900021429
	retCode  = 0
GVBuffer: class org.apache.xerces.dom.DocumentImpl
<?xml version="1.0" encoding="UTF-8"?>
  <QueryResponse xmlns="http://www.credit.com/services">
     <name>MARIO BIANCHI</name>
     <cnumber>1234123415555666</cnumber>
     <credit>300.00000</credit>
     <active>true</active>
  </QueryResponse>
Properties:
	REC_DISCARD = 0
	IS_INTERNAL = true
	REC_TOTAL = 0
	REC_UPDATE = 0
	REC_INSERT = 0
	REC_READ = 1
	CNUMBER = 1234123415555666
	REC_DISCARD_CAUSE = 
</pre>
Retrieved from "https://gvwiki.greenvulcano.com/gvwiki/index.php?title=GVExample_CCardQuery&oldid=2281"