http://<host>:<porta>/webdesk/services 

Watch out for each type of attribute that is expected, for example, the expirationDate attribute of the DocumentDto[] object is a date, however, each language interprets it differently, see some examples below:

• C#: dateTime
• Java™: XMLGregorianCalendar
• Progress®: DATETIME-TZ

For the example below, we used the IDE Adobe® Flex™ Builder™ 3.0 with Flex® SDK 3.2. For other versions of IDE and/or SDK, the process for creating stubs can undergo some variations. 

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" creationComplete="{this.start()}">
	<mx:Script>
		<![CDATA[
			import generated.webservices.ValuesDto;
			import generated.webservices.DatasetDto;
			import generated.webservices.GetDatasetResultEvent;
			import generated.webservices.SearchConstraintDtoArray;
			import generated.webservices.StringArray;
			import generated.webservices.ECMDatasetServiceService;
			import mx.rpc.events.FaultEvent;
			import mx.collections.ArrayCollection;
		
			//Creates an instance of the service access Stub
			private var ds:ECMDatasetServiceService = new ECMDatasetServiceService();
			public function start() : void {
				//Creates assistant types that will be used on the service called
				var fields:StringArray = new StringArray();
				var constraints:SearchConstraintDtoArray = new SearchConstraintDtoArray();
				var order:StringArray = new StringArray();
				//Defines the functions for treating return
				ds.addEventListener(GetDatasetResultEvent.GetDataset_RESULT, resultGetDataset);
				ds.addEventListener(FaultEvent.FAULT,faultGetDataset);
				
				//invokes the service getDataset method
				ds.getDataset("adm", 1, "adm", constraints, order, fields, "colleague");
			}
			
			//Treatment of data returned from the invoked service.
			public function resultGetDataset(ev:GetDatasetResultEvent) : void {
				//Recovers service return in the form of a DatasetDto
				var dataset:DatasetDto = ev.result as DatasetDto;
				//Mounts a string with all the dataset data
				var line:String = "";
				
				//Header with the name of the fields
				var columnsArray:ArrayCollection = new ArrayCollection(dataset.columns);
				for (var j:int = 0; j < columnsArray.length; j++) {
					line += columnsArray.getItemAt(j) + "\t";
				}
				//Data line
				var valuesArray:ArrayCollection = new ArrayCollection(dataset.values);
				for (var j:int = 0; j < valuesArray.length; j++) {
					var row:ValuesDto = valuesArray.getItemAt(j) as ValuesDto;
					line += "\n" + j + ":";
					
					for (var i:int = 0; i < row.length; i++) {
						line += row.getItemAt(i) + "\t";
					}
				}
				
				//Shows the string created in a textarea in the screen
				this.sysout.text = line;
			}
			
			public function faultGetDataset(ev:FaultEvent) : void {
				this.sysout.text = ev.fault.faultString;
			}
		]]>
	</mx:Script>
	<mx:TextArea id="sysout" name="sysout" width="100%" height="100%" 
		paddingBottom="5" paddingLeft="5" paddingRight="5" paddingTop="5"/>
</mx:Application>

Flex® has a bug that prevents proper functioning of services that work with multidimensional arrays of data, as in the above example, where an array (of Dataset lines) of array (of the columns of each record) is returned.

To work around this problem, you must change the class generated by Flex™ Builder™, which will encapsulate the multidimensional array. In the above example, this class is the DatasetDto, which should be changed (line 11) as shown in the example below:

public class DatasetDto
{
	/**
	 * Constructor, initializes the type class
	 */
	public function DatasetDto() {}
            
	[ArrayElementType("String")]
	public var columns:Array;
	[ArrayElementType("ValuesDto")]
	public var values:Array = new Array(); //iniciando o array
}

Other services that do not work with multidimensional arrays do not require changes in the generated code.

wsimport -d <output_directory> <wsdl_url>

package com.fluig.examples;
import javax.xml.ws.BindingProvider;
import net.java.dev.jaxb.array.StringArray;
import com.totvs.technology.ecm.dataservice.ws.DatasetDto;
import com.totvs.technology.ecm.dataservice.ws.DatasetService;
import com.totvs.technology.ecm.dataservice.ws.ECMDatasetServiceService;
import com.totvs.technology.ecm.dataservice.ws.SearchConstraintDtoArray;
import com.totvs.technology.ecm.dataservice.ws.ValuesDto;
/*
 * Class to invoke the DatasetService service
 */
public class ECMDatasetServiceClient {
	//Instantiates DatasetServiceService.
	private ECMDatasetServiceService ecmDatasetServiceService = new ECMDatasetServiceService();
	private DatasetService service = ecmDatasetServiceService.getDatasetServicePort();
	
	//Starts class execution
	public static void main(String[] args) {
		ECMDatasetServiceClient client = new ECMDatasetServiceClient();
		
		//Configures access to WebServices.
		BindingProvider bp = (BindingProvider) client.service;
		bp.getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, 
				"http://localhost:8080/webdesk/ECMDatasetService");
		try {
			client.getDataset();
		} catch (Exception e) {
			e.printStackTrace();
		}
	}
	public void getDataset() throws Exception {
		
		//Creates the parameters used in the call
		int companyId = 1;
		String username = "adm";
		String password = "adm";
		String name = "colleague";
		StringArray fields = new StringArray();
		SearchConstraintDtoArray constraints = new SearchConstraintDtoArray();
		StringArray order = new StringArray();
		
		//Invokes the dataset service
		DatasetDto result = service.getDataset(
				companyId, username, password, name, fields, constraints, order);
		
		//Displays the header
		for (String columnName : result.getColumns()) {
			System.out.print(columnName + "\t");
		}
		System.out.println();
		
		//Displays the dataset lines
		for (ValuesDto row : result.getValues()) {
			for (Object value : row.getValue()) {
				System.out.print(value + "\t");
			}
			System.out.println();
		}
	}
}

When using WebServices via Java™, you must pay attention to the type of each attribute and to the type of return of the WebService. For example, for values of the date type, you should use the XMLGregorianCalendar class:

DocumentDto document = new DocumentDto();

XMLGregorianCalendar date = DatatypeFactory.newInstance().newXMLGregorianCalendar();
date.setYear(2013);
date.setMonth(10);
date.setDay(16);
date.setHour(0);
date.setMinute(0);
date.setSecond(0);

document.setExpirationDate(date);

bprowsdldoc <URL_TO_WSDL>

/* Part I - Call WebService */
DEFINE VARIABLE hWebService     AS HANDLE NO-UNDO.
DEFINE VARIABLE hDatasetService AS HANDLE NO-UNDO.
DEFINE VARIABLE cFields  AS CHARACTER EXTENT 0 NO-UNDO.
DEFINE VARIABLE cOrder   AS CHARACTER EXTENT 0 NO-UNDO.
DEFINE VARIABLE cDataset AS LONGCHAR NO-UNDO.
DEFINE TEMP-TABLE item NO-UNDO
    NAMESPACE-URI ""
    FIELD contraintType AS CHARACTER
	FIELD fieldName     AS CHARACTER
	FIELD finalValue    AS CHARACTER
	FIELD initialValue  AS CHARACTER.
 
DEFINE DATASET dConstraints NAMESPACE-URI "http://ws.dataservice.ecm.technology.totvs.com/"
	FOR item.
CREATE SERVER hWebService.
hWebService:CONNECT("-WSDL 'http://localhost:8080/webdesk/ECMDatasetService?wsdl'").
RUN DatasetService SET hDatasetService ON hWebService.
RUN getDataset IN hDatasetService(INPUT 1,
                                  INPUT "adm",
                                  INPUT "adm",
                                  INPUT "colleague",
                                  INPUT cFields,
                                  INPUT DATASET dConstraints,
                                  INPUT cOrder,
                                  OUTPUT cDataset).
DELETE OBJECT hDatasetService.
hWebService:DISCONNECT().
DELETE OBJECT hWebService.
/* Part II - Parse XML and create a text file separated by tabs */
DEFINE VARIABLE iCount  AS INTEGER   NO-UNDO.
DEFINE VARIABLE iCount2 AS INTEGER   NO-UNDO.
DEFINE VARIABLE hDoc    AS HANDLE    NO-UNDO.
DEFINE VARIABLE hRoot   AS HANDLE    NO-UNDO.
DEFINE VARIABLE hValues AS HANDLE    NO-UNDO.
DEFINE VARIABLE hEntry  AS HANDLE    NO-UNDO.
DEFINE VARIABLE hText   AS HANDLE    NO-UNDO.
DEFINE VARIABLE cValue  AS CHARACTER NO-UNDO.
OUTPUT TO c:\dataset.txt.
CREATE X-DOCUMENT hDoc.
CREATE X-NODEREF hRoot.
CREATE X-NODEREF hEntry.
CREATE X-NODEREF hText.
CREATE X-NODEREF hValues.
hDoc:LOAD("longchar", cDataset, FALSE).
hDoc:GET-DOCUMENT-ELEMENT(hRoot).
/* Goes through the columns <columns> */ 
DO iCount = 1 TO hRoot:NUM-CHILDREN WITH 20 DOWN:
    hRoot:GET-CHILD(hEntry, iCount).
    IF hEntry:NAME <> "columns" THEN
        NEXT.
    hEntry:GET-CHILD(hText, 1).
    PUT UNFORMATTED hText:NODE-VALUE "~t".
    DOWN.
END.
PUT UNFORMATTED SKIP.
/* Goes through the records <values> */
DO iCount = 1 TO hRoot:NUM-CHILDREN WITH 20 DOWN:
    hRoot:GET-CHILD(hValues, iCount).
    IF hValues:NAME <> "values" THEN
        NEXT.
    /* Goes through the fields <value> */
    DO iCount2 = 1 TO hValues:NUM-CHILDREN:
        hValues:GET-CHILD(hEntry, iCount2).
        IF hEntry:NUM-CHILDREN = 0 THEN
            cValue = "".
        ELSE DO:
            hEntry:GET-CHILD(hText, 1).
            cValue = hText:NODE-VALUE.
        END.
        PUT UNFORMATTED cValue "~t".
    END.
    PUT UNFORMATTED SKIP.
END.
OUTPUT CLOSE.
DELETE OBJECT hValues.
DELETE OBJECT hText.
DELETE OBJECT hEntry.
DELETE OBJECT hRoot.
DELETE OBJECT hDoc.

function createDataset(fields, constraints, sortFields) {
	//Creates the dataset
	var dataset = DatasetBuilder.newDataset();
	dataset.addColumn("elementName");
	// Connects the service and searches for the books
	var periodicService = ServiceManager.getService('PeriodicTable');
	var serviceHelper = periodicService.getBean();
	var serviceLocator = serviceHelper.instantiate('net.webservicex.Periodictable');
	var service = serviceLocator.getPeriodictableSoap();
	//Invokes the service
	try {
		var result = service.getAtoms();
		var NewDataSet = new XML(result);
		for each(element in NewDataSet.Table) {
			dataset.addRow(new Array(element.ElementName.toString()));
		}
	} catch(erro) {
		dataset.addRow(new Array(erro));
	}
	return dataset;
}

var serviceLocator = serviceHelper.instantiate('net.webservicex.Periodictable');
var service = serviceLocator.getPeriodictableSoap();
var result = service.getAtoms();

<NewDataSet>
	<Table>
		<ElementName>Actinium</ElementName>
	</Table>
	<Table>
		<ElementName>Aluminium</ElementName>
	</Table>
	...
</NewDataSet>

var NewDataSet = new XML(result);
for each(element in NewDataSet.Table) {
	dataset.addRow(new Array(element.ElementName.toString()));
}

var serviceLocator = serviceHelper.instantiate('net.webservicex.Periodictable');
var service = serviceLocator.getPeriodictableSoap();
var authenticatedService = serviceHelper.getBasicAuthenticatedClient(service, "net.webservicex.PeriodictableSoap", 'usuario', 'senha');
var result = authenticatedService.getAtoms();

This technique is valid for Fluig 1.3.7 or higher.

In integrations that use services created with CXF with systems that do not support the HTTP/1.1 protocol (Protheus, for example), you need to use this method by setting the "disable.chunking" parameter to "true".

		var properties = {};
		properties["basic.authorization"] = "true";
		properties["basic.authorization.username"] = "username";
		properties["basic.authorization.password"] = "password";
		properties["disable.chunking"] = "true";
		properties["log.soap.messages"] = "true";
		
		var serviceLocator = serviceHelper.instantiate('net.webservicex.Periodictable');
		var service = serviceLocator.getPeriodictableSoap();
		var customClient = serviceHelper.getCustomClient(service, "net.webservicex.PeriodictableSoap", properties);
		var result = customClient.getAtoms();

/**************************************************************************
** Utility that provides procedures for extracting information
** on cost centers.
**************************************************************************/
DEFINE TEMP-TABLE ttCC NO-UNDO
    FIELD conta    LIKE conta.ct-codigo /* CHARACTER */
    FIELD natureza LIKE conta.natureza  /* INTEGER   */
    FIELD tipo     LIKE conta.tipo      /* INTEGER   */
    FIELD titulo   LIKE conta.titulo.   /* CHARACTER */
 
/*-------------------------------------------------------------------
  Procedure: readCostCenters
   Objective: Returns a temp-table with the list of cost centers.
----------------------------------------------------------------------*/
PROCEDURE readCostCenters:
    DEFINE OUTPUT PARAMETER TABLE FOR ttCC.
    FOR EACH conta:
        CREATE ttCC.
        ASSIGN
            ttCC.conta    = conta.ct-codigo
            ttCC.natureza = conta.natureza
            ttCC.tipo     = conta.tipo
            ttCC.titulo   = conta.titulo.
    END.
END.
/*-------------------------------------------------------------------
  Procedure: readCostNatureTypes
   Objective: Returns a string with the natures of cost centers,
             separated by comma.
----------------------------------------------------------------------*/
PROCEDURE readCostNatureTypes:
    DEFINE OUTPUT PARAMETER cNatureList AS CHARACTER NO-UNDO.
    cNatureList = {adinc/i01ad047.i 03}.
END.
/*-------------------------------------------------------------------
  Procedure: readCostTypes
   Objective: Returns a string with the types of cost centers,
             separated by comma.
----------------------------------------------------------------------*/
PROCEDURE readCostTypes: 
    DEFINE OUTPUT PARAMETER cTypeList   AS CHARACTER NO-UNDO.
    cTypeList = {adinc/i02ad047.i 3}.
END.

/**************************************************************************
** Utility that receives a temp-table with a list of users and returns
** another with only the users from the list that are in the database.
**************************************************************************/
DEFINE TEMP-TABLE ttUsers
    FIELD cod_usuar   AS CHARACTER
    FIELD nom_usuario AS CHARACTER
    INDEX principal	  IS PRIMARY UNIQUE cod_usuar.
	
DEFINE TEMP-TABLE ttOutUsers LIKE ttUsers.
DEFINE INPUT  PARAMETER TABLE FOR ttUsers.
DEFINE OUTPUT PARAMETER TABLE FOR ttOutUsers.
FOR EACH ttUsers:
   IF CAN-FIND(usuar_mestre WHERE usuar_mestre.cod_usuar = ttUsers.cod_usuar) THEN DO:
        CREATE ttOutUsers.
        BUFFER-COPY ttUsers TO ttOutUsers.
    END.
END.

Depending on the version of Progress®, the screens can suffer some variation in the amount and placement of fields. See the documentation in case of doubt

serviceHelper.getProxy().verifyUsers(inputTT, holder).

function

                    <div id="main-content" class="wiki-content group">
                    <h1 id="IntegraçãoComAplicativosExternos-Índice">Index:</h1><p>&#160;</p><p><style type='text/css'>/*<![CDATA[*/
div.rbtoc1412695546456 {padding: 0px;}
div.rbtoc1412695546456 ul {list-style: none;margin-left: 0px;}
div.rbtoc1412695546456 li {margin-left: 0px;padding-left: 0px;}
/*]]>*/</style><div class='toc-macro rbtoc1412695546456'>
<ul class='toc-indentation'>
<li><span class='TOCOutline'>1</span> <a href='#IntegraçãoComAplicativosExternos-ConsideraçõesGerais'>General Considerations</a></li>
<li><span class='TOCOutline'>2</span> <a href='#IntegraçãoComAplicativosExternos-VisãoGeral'>Overview</a></li>
<li><span class='TOCOutline'>3</span> <a href='#IntegraçãoComAplicativosExternos-WebServices'>WebServices</a>
<ul class='toc-indentation'>
<li><span class='TOCOutline'>3.1</span> <a href='#IntegraçãoComAplicativosExternos-AcessandoosWebServicesdoFluig'>Accessing Fluig WebServices</a>
<ul class='toc-indentation'>
<li><span class='TOCOutline'>3.1.1</span> <a href='#IntegraçãoComAplicativosExternos-ViaApacheFlex®'>Via Apache Flex®</a></li>
<li><span class='TOCOutline'>3.1.2</span> <a href='#IntegraçãoComAplicativosExternos-ViaJava™'>Via Java™</a></li>
<li><span class='TOCOutline'>3.1.3</span> <a href='#IntegraçãoComAplicativosExternos-ViaProgress®4GL'>Via Progress® 4GL</a></li>
</ul>
</li>
<li><span class='TOCOutline'>3.2</span> <a href='#IntegraçãoComAplicativosExternos-AcessandoWebServicesapartirdoFluig'>Accessing WebServices from Fluig</a>
<ul class='toc-indentation'>
<li><span class='TOCOutline'>3.2.1</span> <a href='#IntegraçãoComAplicativosExternos-WebServicescomAutenticaçãoBásica'>WebServices with Basic Authentication</a></li>
<li><span class='TOCOutline'>3.2.2</span> <a href='#IntegraçãoComAplicativosExternos-WebServicecomclientcustomizado'>WebService with customized client</a></li>
</ul>
</li>
<li><span class='TOCOutline'>3.3</span> <a href='#IntegraçãoComAplicativosExternos-CasodeUso'>Use Case</a></li>
<li><span class='TOCOutline'>3.4</span> <a href='#IntegraçãoComAplicativosExternos-ConfiguraçãodoAppServer'>AppServer Configuration</a></li>
<li><span class='TOCOutline'>3.5</span> <a href='#IntegraçãoComAplicativosExternos-Expondocódigos4GLcomProxyGen'>Exposing 4GL codes with ProxyGen</a></li>
<li><span class='TOCOutline'>3.6</span> <a href='#IntegraçãoComAplicativosExternos-ConfiguraçãodoServiçonoFluig'>Service Configuration in Fluig</a></li>
<li><span class='TOCOutline'>3.7</span> <a href='#IntegraçãoComAplicativosExternos-VisãoGeraldosObjetosEnvolvidos'>Overview of Objects Involved</a>
<ul class='toc-indentation'>
<li><span class='TOCOutline'>3.7.1</span> <a href='#IntegraçãoComAplicativosExternos-ProceduresPersistenteseNão-Persistentes'>Persistent and Non-Persistent Procedures</a></li>
<li><span class='TOCOutline'>3.7.2</span> <a href='#IntegraçãoComAplicativosExternos-ParâmetrosdeEntradaeSaída'>Input and Output Parameters</a></li>
</ul>
</li>
<li><span class='TOCOutline'>3.8</span> <a href='#IntegraçãoComAplicativosExternos-CriaçãodosDatasets'>Dataset Creation</a>
<ul class='toc-indentation'>
<li><span class='TOCOutline'>3.8.1</span> <a href='#IntegraçãoComAplicativosExternos-TiposdeCentrodeCusto'>Cost Center Types</a></li>
<li><span class='TOCOutline'>3.8.2</span> <a href='#IntegraçãoComAplicativosExternos-NaturezadosCentrosdeCusto'>Nature of Cost Centers</a></li>
<li><span class='TOCOutline'>3.8.3</span> <a href='#IntegraçãoComAplicativosExternos-CentrosdeCusto'>Cost Centers</a>
<ul class='toc-indentation'>
<li><span class='TOCOutline'>3.8.3.1</span> <a href='#IntegraçãoComAplicativosExternos-CodificaçãoProgress®9'>Progress® 9 Encoding</a></li>
<li><span class='TOCOutline'>3.8.3.2</span> <a href='#IntegraçãoComAplicativosExternos-CodificaçãoOpenEdge®10'>OpenEdge® 10 Encoding</a></li>
</ul>
</li>
<li><span class='TOCOutline'>3.8.4</span> <a href='#IntegraçãoComAplicativosExternos-UsuáriosemComum'>Users in Common</a>
<ul class='toc-indentation'>
<li><span class='TOCOutline'>3.8.4.1</span> <a href='#IntegraçãoComAplicativosExternos-CodificaçãoProgress®9.1'>Progress® 9 Encoding</a></li>
<li><span class='TOCOutline'>3.8.4.2</span> <a href='#IntegraçãoComAplicativosExternos-CodificaçãoOpenEdge®10.1'>OpenEdge® 10 Encoding</a></li>
</ul>
</li>
</ul>
</li>
<li><span class='TOCOutline'>3.9</span> <a href='#IntegraçãoComAplicativosExternos-ServiceHelper'>Service Helper</a></li>
</ul>
</li>
<li><span class='TOCOutline'>4</span> <a href='#IntegraçãoComAplicativosExternos-ThirdPartyTrademarks'>Third Party Trademarks</a></li>
</ul>
</div></p><h1 id="IntegraçãoComAplicativosExternos-ConsideraçõesGerais">General Considerations</h1><p>The information contained in this document is intended to demonstrate how to perform the integration between Fluig and external applications. In order to have a full understanding of this information, some knowledge is considered a prerequisite, including:</p><ul><li class="O1">Overview of Fluig product</li><li class="O1">Overview of system integration</li><li class="O1">JavaScript</li><li class="O1">WebServices</li><li class="O1">SOAP</li><li class="O1"><p><span style="font-size: 10.0pt;line-height: 13.0pt;">Progress® 4GL</span></p></li><li class="O1">Progress® Open App Server</li><li class="O1">Progress® Open Client for&#160;<span style="font-size: 10.0pt;line-height: 13.0pt;">Java</span></li><li class="O1">Datasets (Fluig)</li><li class="O1">Java™</li><li class="O1">Apache Flex®</li></ul><p>In several parts of this document, code snippets will be presented in different programming languages in order to show the use of Fluig integration resources. However, this document does not intend to empower the reader to use these technologies beyond the above-described purpose, the reader being responsible for searching for more detailed information on these languages.</p><p>With the intent of making it easier to understand the information presented and simulation of the concepts presented, the examples mentioned in this document use the Dataset feature as an example of the use of the product integration resources. However, it is important to note that other points of the product have the same integration characteristics available as those existing in Datasets, especially customizations of forms and processes.</p><h1 id="IntegraçãoComAplicativosExternos-VisãoGeral">Overview</h1><p>Although empirical, every company has business processes that enable the company to fulfill its objective, whether it is the provision of a service, the production of products or trading goods. A company has a multitude of processes, with each person in the organization being part of at least one of these processes, and all of them exchange information with each other at some point. The processes can be formal (such as hiring a professional) or informal (such as an incentive to innovation), critical (billing) or satellite (birthday card send control).</p><p>With the advent of Information System technologies, several systems began to provide support for these business processes, especially those considered most critical to company operation. The best example of this is the use of ERP systems that support the processes in various company areas.</p><p>Fluig has the objective of being an agnostic platform that manages processes, documents and identities through one collaborative communication interface. This can be realized to a greater or lesser degree in every one of its features, from the most simple (such as collaboration) to the more complex (such as DM and BPM).</p><p>However, part of these processes have a high reliance on existing information systems in the company and, therefore, Fluig's architecture is designed to enable integration with these systems, allowing the modeled processes to have higher added value.</p><p>Fluig allows both access through the product to external systems (to query or feed information) and enables other systems to connect to query information or to run transactional operations.</p><p>&#160;</p><p><img class="confluence-embedded-image image-center" src="attachments/73082260/73406805.png" data-image-src="attachments/73082260/73406805.png"></p><p>&#160;</p><p>The main product integration channel is through WebServices, which are becoming the most common standard for integration with any application. Through it, you can have access to Fluig features and provide access through the product to external applications. This document has a specific section on integration through WebServices.</p><p>The other form of integration is through calls to Progress® Open AppServer and is recommended for users who need to integrate Fluig with applications developed in that platform.</p><h1 id="IntegraçãoComAplicativosExternos-WebServices">WebServices</h1><p>Integration through WebServices uses the SOAP protocol and, since it is an open standard, allows systems developed in entirely different platforms, such as Java™, Microsoft® .Net, C, C++, PHP, Ruby, Pearl, Python, among others, to exchange information with each other in a seamless way.</p><h3 id="IntegraçãoComAplicativosExternos-AcessandoosWebServicesdoFluig">Accessing Fluig WebServices</h3><p>Fluig provides a set of WebServices that allow access to product information or running tasks, such as starting process requests.&#160;<span style="font-size: 10.0pt;line-height: 13.0pt;">For the list of WebServices available, go to:&#160;</span></p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
<pre>http://&lt;host>:&lt;porta>/webdesk/services&#160;</pre>
</div></div><p>Each link provided directs the browser to the service WSDL URL. The WSDL (Web Service Description Language) has the service description in XML format and is used by development tools to create components that will represent this service.</p>    <div class="aui-message warning shadowed information-macro">
                            <span class="aui-icon icon-warning">Icon</span>
                <div class="message-content">
                            <p>Watch out for each type of attribute that is expected, for example, the expirationDate attribute of the DocumentDto[] object is a date, however, each language interprets it differently, see some examples below:</p><ul><li>C#: <strong>dateTime</strong></li><li>Java™: <strong>XMLGregorianCalendar</strong></li><li>Progress®: <strong>DATETIME-TZ</strong></li></ul>
                    </div>
    </div>
<p>&#160;</p><h5 id="IntegraçãoComAplicativosExternos-ViaApacheFlex®">Via Apache Flex®</h5><p>As the vast majority of development tools, Apache Flex® allows you to create stubs to access to web services. These stubs include all the packing and unpacking operations of XML standard information for the platform native types.</p><p>Use the step-by-step to view the process of creating stubs for a service provided by Fluig:</p>    
 
<a name="composition-deck-stubFlex"></a>
<div id="stubFlex" 
     class="deck"
     history="false" 
     loopcards="false" 
     effecttype="" 
     effectduration="1.0"
     nextafter="0.0">
    		<ul class="tab-navigation"></ul> <!-- // .tab-navigation -->    
            <div class="deck-cards panel" style="">	<div id="1" 
     class="deck-card  active-pane" 
     style="" 
     cssclass=""
	 accesskey=""
	 label="1&amp;ordm; Passo"
	 title=""
	 nextafter="0"
	 effecttype="fade"
	 effectduration="0.5"><p>The creation of stubs in Flex® is done through the Data menu, Import WebService(WSDL) option, as shown in the image below.</p><p><img class="confluence-embedded-image" src="attachments/73082260/73406802.png" data-image-src="attachments/73082260/73406802.png"></p></div>
	<div id="2" 
     class="deck-card " 
     style="" 
     cssclass=""
	 accesskey=""
	 label="2&amp;ordm; Passo"
	 title=""
	 nextafter="0"
	 effecttype="fade"
	 effectduration="0.5"><p>In the first window, the folder within the current project where the stubs should be generated is requested.</p><p><img class="confluence-embedded-image" src="attachments/73082260/73406800.png" data-image-src="attachments/73082260/73406800.png"></p></div>
	<div id="3" 
     class="deck-card " 
     style="" 
     cssclass=""
	 accesskey=""
	 label="3&amp;ordm; Passo"
	 title=""
	 nextafter="0"
	 effecttype="fade"
	 effectduration="0.5"><p>In the following screen, you should provide the WSDL address where the service is found. It is also possible to define if it will be accessed from the LifeCycle Data Services client or server station.</p><p><img class="confluence-embedded-image" src="attachments/73082260/73406797.png" data-image-src="attachments/73082260/73406797.png"></p></div>
	<div id="4" 
     class="deck-card " 
     style="" 
     cssclass=""
	 accesskey=""
	 label="4&amp;ordm; Passo"
	 title=""
	 nextafter="0"
	 effecttype="fade"
	 effectduration="0.5"><p>In the last screen, you should provide the package that will be used and the name of the main class (already suggested by the Flex™ Builder™).</p><p><img class="confluence-embedded-image" src="attachments/73082260/73406796.png" data-image-src="attachments/73082260/73406796.png"></p></div>
	<div id="5" 
     class="deck-card " 
     style="" 
     cssclass=""
	 accesskey=""
	 label="Resultado"
	 title=""
	 nextafter="0"
	 effecttype="fade"
	 effectduration="0.5"><p>When the process is finished, Flex™ Builder™ will add to the project a set of classes that will be used by the programmer to invoke the services, as shown in the figure below:</p><p><img class="confluence-embedded-image" src="attachments/73082260/73406795.png" data-image-src="attachments/73082260/73406795.png"></p></div>
</div>
    </div> <!-- // .deck -->
    <div class="aui-message hint shadowed information-macro">
                            <span class="aui-icon icon-hint">Icon</span>
                <div class="message-content">
                            <p>For the example below, we used the IDE Adobe® Flex™ Builder™ 3.0 with Flex® SDK 3.2. For other versions of IDE and/or SDK, the process for creating stubs can undergo some variations.<span style="font-size: 10.0pt;line-height: 13.0pt;">&#160;</span></p>
                    </div>
    </div>
<p>The code snippet below shows an example of the Fluig Dataset access WebService being called:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>ECMDatasetServiceClient.mxml</b></div><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: actionscript3; gutter: true" style="font-size:12px;">&lt;?xml version="1.0" encoding="utf-8"?>
&lt;mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" creationComplete="{this.start()}">
	&lt;mx:Script>
		&lt;![CDATA[
			import generated.webservices.ValuesDto;
			import generated.webservices.DatasetDto;
			import generated.webservices.GetDatasetResultEvent;
			import generated.webservices.SearchConstraintDtoArray;
			import generated.webservices.StringArray;
			import generated.webservices.ECMDatasetServiceService;
			import mx.rpc.events.FaultEvent;
			import mx.collections.ArrayCollection;
		
			//Creates an instance of the service access Stub
			private var ds:ECMDatasetServiceService = new ECMDatasetServiceService();
			public function start() : void {
				//Creates assistant types that will be used on the service called
				var fields:StringArray = new StringArray();
				var constraints:SearchConstraintDtoArray = new SearchConstraintDtoArray();
				var order:StringArray = new StringArray();
				//Defines the functions for treating return
				ds.addEventListener(GetDatasetResultEvent.GetDataset_RESULT, resultGetDataset);
				ds.addEventListener(FaultEvent.FAULT,faultGetDataset);
				
				//invokes the service getDataset method
				ds.getDataset("adm", 1, "adm", constraints, order, fields, "colleague");
			}
			
			//Treatment of data returned from the invoked service.
			public function resultGetDataset(ev:GetDatasetResultEvent) : void {
				//Recovers service return in the form of a DatasetDto
				var dataset:DatasetDto = ev.result as DatasetDto;
				//Mounts a string with all the dataset data
				var line:String = "";
				
				//Header with the name of the fields
				var columnsArray:ArrayCollection = new ArrayCollection(dataset.columns);
				for (var j:int = 0; j &lt; columnsArray.length; j++) {
					line += columnsArray.getItemAt(j) + "\t";
				}
				//Data line
				var valuesArray:ArrayCollection = new ArrayCollection(dataset.values);
				for (var j:int = 0; j &lt; valuesArray.length; j++) {
					var row:ValuesDto = valuesArray.getItemAt(j) as ValuesDto;
					line += "\n" + j + ":";
					
					for (var i:int = 0; i &lt; row.length; i++) {
						line += row.getItemAt(i) + "\t";
					}
				}
				
				//Shows the string created in a textarea in the screen
				this.sysout.text = line;
			}
			
			public function faultGetDataset(ev:FaultEvent) : void {
				this.sysout.text = ev.fault.faultString;
			}
		]]>
	&lt;/mx:Script>
	&lt;mx:TextArea id="sysout" name="sysout" width="100%" height="100%" 
		paddingBottom="5" paddingLeft="5" paddingRight="5" paddingTop="5"/>
&lt;/mx:Application></pre>
</div></div>    <div class="aui-message warning shadowed information-macro">
                            <span class="aui-icon icon-warning">Icon</span>
                <div class="message-content">
                            <p>Flex® has a bug that prevents proper functioning of services that work with multidimensional arrays of data, as in the above example, where an array (of Dataset lines) of array (of the columns of each record) is returned.</p><p>To work around this problem, you must change the class generated by Flex™ Builder™, which will encapsulate the multidimensional array. In the above example, this class is the DatasetDto, which should be changed (line 11) as shown in the example below:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: actionscript3; gutter: true" style="font-size:12px;">public class DatasetDto
{
	/**
	 * Constructor, initializes the type class
	 */
	public function DatasetDto() {}
            
	[ArrayElementType("String")]
	public var columns:Array;
	[ArrayElementType("ValuesDto")]
	public var values:Array = new Array(); //iniciando o array
}</pre>
</div></div><p>Other services that do not work with multidimensional arrays do not require changes in the generated code.</p>
                    </div>
    </div>
<p>&#160;</p><h5 id="IntegraçãoComAplicativosExternos-ViaJava™">Via Java™</h5><p>There are many implementations of WebServices use in Java™ and, in this example, we will use the libraries available in Java™ 7.</p><p>As in the previous example, in Apache Flex®, the first step is to use the WSDL address for generating Java™ stubs. The command below provides an example of how to generate these stubs:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
<pre>wsimport -d &lt;output_directory> &lt;wsdl_url></pre>
</div></div><p>Through this command, the stubs are generated in the target directory (output_directory), as described in the wsdl file (wsdl_url).</p><p><img class="confluence-embedded-image" src="attachments/73082260/73406803.png" data-image-src="attachments/73082260/73406803.png"></p><p>From the generated stubs, it is possible to consume the WebService as in the example below:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>ECMDatasetServiceClient.java</b></div><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: java; gutter: true" style="font-size:12px;">package com.fluig.examples;
import javax.xml.ws.BindingProvider;
import net.java.dev.jaxb.array.StringArray;
import com.totvs.technology.ecm.dataservice.ws.DatasetDto;
import com.totvs.technology.ecm.dataservice.ws.DatasetService;
import com.totvs.technology.ecm.dataservice.ws.ECMDatasetServiceService;
import com.totvs.technology.ecm.dataservice.ws.SearchConstraintDtoArray;
import com.totvs.technology.ecm.dataservice.ws.ValuesDto;
/*
 * Class to invoke the DatasetService service
 */
public class ECMDatasetServiceClient {
	//Instantiates DatasetServiceService.
	private ECMDatasetServiceService ecmDatasetServiceService = new ECMDatasetServiceService();
	private DatasetService service = ecmDatasetServiceService.getDatasetServicePort();
	
	//Starts class execution
	public static void main(String[] args) {
		ECMDatasetServiceClient client = new ECMDatasetServiceClient();
		
		//Configures access to WebServices.
		BindingProvider bp = (BindingProvider) client.service;
		bp.getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, 
				"http://localhost:8080/webdesk/ECMDatasetService");
		try {
			client.getDataset();
		} catch (Exception e) {
			e.printStackTrace();
		}
	}
	public void getDataset() throws Exception {
		
		//Creates the parameters used in the call
		int companyId = 1;
		String username = "adm";
		String password = "adm";
		String name = "colleague";
		StringArray fields = new StringArray();
		SearchConstraintDtoArray constraints = new SearchConstraintDtoArray();
		StringArray order = new StringArray();
		
		//Invokes the dataset service
		DatasetDto result = service.getDataset(
				companyId, username, password, name, fields, constraints, order);
		
		//Displays the header
		for (String columnName : result.getColumns()) {
			System.out.print(columnName + "\t");
		}
		System.out.println();
		
		//Displays the dataset lines
		for (ValuesDto row : result.getValues()) {
			for (Object value : row.getValue()) {
				System.out.print(value + "\t");
			}
			System.out.println();
		}
	}
}</pre>
</div></div>    <div class="aui-message warning shadowed information-macro">
                            <span class="aui-icon icon-warning">Icon</span>
                <div class="message-content">
                            <p>When using WebServices via Java™, you must pay attention to the type of each attribute and to the type of return of the WebService. For example, for values of the <strong>date </strong>type, you should use the <strong>XMLGregorianCalendar</strong> class:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: java; gutter: true" style="font-size:12px;">DocumentDto document = new DocumentDto();
XMLGregorianCalendar date = DatatypeFactory.newInstance().newXMLGregorianCalendar();
date.setYear(2013);
date.setMonth(10);
date.setDay(16);
date.setHour(0);
date.setMinute(0);
date.setSecond(0);
document.setExpirationDate(date);</pre>
</div></div>
                    </div>
    </div>
<p>&#160;</p><h5 id="IntegraçãoComAplicativosExternos-ViaProgress®4GL">Via Progress® 4GL</h5><p>So, as in the previous examples, the first step to use a Webservice in Progress® is to use a utility that will read the ESDL address and generate the required information for accessing it. Different from Java™ and Flex®, Progress® does not generate stub objects, but only a documentation on how to consume the services described in the WSDL file. Although in some situations you can use the Progress® native types as parameters, depending on the data type used, you need to handle the SOAP XML to extract or send information.</p><p>To generate the documentation for a service, you must use the <strong>bprowsdldoc</strong> utility as in the example below:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
<pre>bprowsdldoc &lt;URL_TO_WSDL></pre>
</div></div><p>With the execution of this utility, some HTML files will be generated with information on how to use the service. This documentation provides information and examples on how to perform the connection with the services and use the service methods and datatypes.&#160;</p><p><span style="font-size: 10.0pt;line-height: 13.0pt;">The code below shows an example of how to use the service:</span></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>wsECMDatasetService.p</b></div><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: javafx; gutter: true" style="font-size:12px;">/* Part I - Call WebService */
DEFINE VARIABLE hWebService     AS HANDLE NO-UNDO.
DEFINE VARIABLE hDatasetService AS HANDLE NO-UNDO.
DEFINE VARIABLE cFields  AS CHARACTER EXTENT 0 NO-UNDO.
DEFINE VARIABLE cOrder   AS CHARACTER EXTENT 0 NO-UNDO.
DEFINE VARIABLE cDataset AS LONGCHAR NO-UNDO.
DEFINE TEMP-TABLE item NO-UNDO
    NAMESPACE-URI ""
    FIELD contraintType AS CHARACTER
	FIELD fieldName     AS CHARACTER
	FIELD finalValue    AS CHARACTER
	FIELD initialValue  AS CHARACTER.
&#160;
DEFINE DATASET dConstraints NAMESPACE-URI "http://ws.dataservice.ecm.technology.totvs.com/"
	FOR item.
CREATE SERVER hWebService.
hWebService:CONNECT("-WSDL 'http://localhost:8080/webdesk/ECMDatasetService?wsdl'").
RUN DatasetService SET hDatasetService ON hWebService.
RUN getDataset IN hDatasetService(INPUT 1,
                                  INPUT "adm",
                                  INPUT "adm",
                                  INPUT "colleague",
                                  INPUT cFields,
                                  INPUT DATASET dConstraints,
                                  INPUT cOrder,
                                  OUTPUT cDataset).
DELETE OBJECT hDatasetService.
hWebService:DISCONNECT().
DELETE OBJECT hWebService.
/* Part II - Parse XML and create a text file separated by tabs */
DEFINE VARIABLE iCount  AS INTEGER   NO-UNDO.
DEFINE VARIABLE iCount2 AS INTEGER   NO-UNDO.
DEFINE VARIABLE hDoc    AS HANDLE    NO-UNDO.
DEFINE VARIABLE hRoot   AS HANDLE    NO-UNDO.
DEFINE VARIABLE hValues AS HANDLE    NO-UNDO.
DEFINE VARIABLE hEntry  AS HANDLE    NO-UNDO.
DEFINE VARIABLE hText   AS HANDLE    NO-UNDO.
DEFINE VARIABLE cValue  AS CHARACTER NO-UNDO.
OUTPUT TO c:\dataset.txt.
CREATE X-DOCUMENT hDoc.
CREATE X-NODEREF hRoot.
CREATE X-NODEREF hEntry.
CREATE X-NODEREF hText.
CREATE X-NODEREF hValues.
hDoc:LOAD("longchar", cDataset, FALSE).
hDoc:GET-DOCUMENT-ELEMENT(hRoot).
/* Goes through the columns &lt;columns> */ 
DO iCount = 1 TO hRoot:NUM-CHILDREN WITH 20 DOWN:
    hRoot:GET-CHILD(hEntry, iCount).
    IF hEntry:NAME &lt;> "columns" THEN
        NEXT.
    hEntry:GET-CHILD(hText, 1).
    PUT UNFORMATTED hText:NODE-VALUE "~t".
    DOWN.
END.
PUT UNFORMATTED SKIP.
/* Goes through the records &lt;values> */
DO iCount = 1 TO hRoot:NUM-CHILDREN WITH 20 DOWN:
    hRoot:GET-CHILD(hValues, iCount).
    IF hValues:NAME &lt;> "values" THEN
        NEXT.
    /* Goes through the fields &lt;value> */
    DO iCount2 = 1 TO hValues:NUM-CHILDREN:
        hValues:GET-CHILD(hEntry, iCount2).
        IF hEntry:NUM-CHILDREN = 0 THEN
            cValue = "".
        ELSE DO:
            hEntry:GET-CHILD(hText, 1).
            cValue = hText:NODE-VALUE.
        END.
        PUT UNFORMATTED cValue "~t".
    END.
    PUT UNFORMATTED SKIP.
END.
OUTPUT CLOSE.
DELETE OBJECT hValues.
DELETE OBJECT hText.
DELETE OBJECT hEntry.
DELETE OBJECT hRoot.
DELETE OBJECT hDoc.</pre>
</div></div><h3 id="IntegraçãoComAplicativosExternos-AcessandoWebServicesapartirdoFluig">Accessing WebServices from Fluig</h3><p>Fluig allows call to third-party WebServices through the Fluig Studio Service View Service registration.</p><p>In order to add a new WebService, you need to click the <strong>Add Service</strong> option by opening the New Service wizard and providing the Fluig server where the service will be added,&#160;<span style="font-size: 10.0pt;line-height: 13.0pt;">an identifier code for it, its description, the WSDL URL ans its type (in this case, WebService).&#160;</span><span style="font-size: 10.0pt;line-height: 13.0pt;">In the example below, you will use a public WebService to query to the periodic table, whose WSDL address is&#160;</span><span class="nolink" style="font-size: 10.0pt;line-height: 13.0pt;"><a href="http://www.webservicex.com/periodictable.asmx?wsdl" class="external-link" rel="nofollow">http://www.webservicex.com/periodictable.asmx?wsdl</a></span><span style="font-size: 10.0pt;line-height: 13.0pt;">.</span></p><p><span style="font-size: 10.0pt;line-height: 13.0pt;"><img class="confluence-embedded-image image-center" src="attachments/73082260/73406793.png" data-image-src="attachments/73082260/73406793.png"></span></p><p>Based on this information, Fluig will extract the provided WebService information and will finish the registration of this service.&#160;</p><p><span style="font-size: 10.0pt;line-height: 13.0pt;">Once the service is registered, you can view the classes and methods available in this service and which will be used in the JavaScript code that will use it. The screen below shows an example of a WebService view.</span></p><p><span style="font-size: 10.0pt;line-height: 13.0pt;"><img class="confluence-embedded-image image-center" src="attachments/73082260/73406792.png" data-image-src="attachments/73082260/73406792.png"></span></p><p>Services added to Fluig can be instantiated and used where the product allows for customization using JavaScript, as in the scripts for global events, process events, form definition events or Datasets.&#160;<span style="font-size: 10.0pt;line-height: 13.0pt;">In the following example, you will create a Dataset that will use this service to get the periodic table data.</span></p><p>The code below shows a sample implementation of the use of a service in the construction of a Dataset:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>periodicTable.js</b></div><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: javascript; gutter: true" style="font-size:12px;">function createDataset(fields, constraints, sortFields) {
	//Creates the dataset
	var dataset = DatasetBuilder.newDataset();
	dataset.addColumn("elementName");
	// Connects the service and searches for the books
	var periodicService = ServiceManager.getService('PeriodicTable');
	var serviceHelper = periodicService.getBean();
	var serviceLocator = serviceHelper.instantiate('net.webservicex.Periodictable');
	var service = serviceLocator.getPeriodictableSoap();
	//Invokes the service
	try {
		var result = service.getAtoms();
		var NewDataSet = new XML(result);
		for each(element in NewDataSet.Table) {
			dataset.addRow(new Array(element.ElementName.toString()));
		}
	} catch(erro) {
		dataset.addRow(new Array(erro));
	}
	return dataset;
}</pre>
</div></div><p>The first step to call the service is to request Fluig to load the service, from the <strong>ServiceManager.getService ('PeriodicTable ')</strong> method. The value passed as a parameter must be the code used when the services was registered.</p><p>Once the service has been loaded, the <strong>getBean()</strong> method is used to return a utility for access to the service classes through the <strong>instantiate</strong> method. Through this utility, it is possible to instantiate the classes available and that are listed in the Service registration (as in image above).</p><p>Once you have instantiated the service utility object, the classes that must be instantiated and the methods that should be invoked depend on each WebService used, and you must check its documentation for more information.</p><p>For the periodic table service, you need to perform the following steps:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: javascript; gutter: true" style="font-size:12px;">var serviceLocator = serviceHelper.instantiate('net.webservicex.Periodictable');
var service = serviceLocator.getPeriodictableSoap();
var result = service.getAtoms();</pre>
</div></div><p>Where:</p><ul><li><p><strong>Step 1:&#160;</strong>Instantiate the&#160;<strong><span style="font-size: 10.0pt;line-height: 13.0pt;">net.webservicex.Periodictable</span></strong><span style="font-size: 10.0pt;line-height: 13.0pt;">&#160; class to have access to the locator service;&#160;</span></p></li><li><span style="font-size: 10.0pt;line-height: 13.0pt;"><strong>Step 2:</strong> Call the <strong>getPeriodictableSoap</strong> method to instantiate the service;</span></li><li><span style="font-size: 10.0pt;line-height: 13.0pt;"><strong>Step 3:</strong> Call the <strong>getAtoms</strong> method to get the element list.</span><br /><span style="font-size: 10.0pt;line-height: 13.0pt;"><br /></span></li></ul><p>In the case of this service, the <strong>getAtoms</strong> method returns a string containing an XML with the list of all elements, according to the example below:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: html/xml; gutter: true" style="font-size:12px;">&lt;NewDataSet>
	&lt;Table>
		&lt;ElementName>Actinium&lt;/ElementName>
	&lt;/Table>
	&lt;Table>
		&lt;ElementName>Aluminium&lt;/ElementName>
	&lt;/Table>
	...
&lt;/NewDataSet></pre>
</div></div><p>In order to go through the XML and extract the available data, the features for handling JavaScript XML are used, which makes it easier to handle this type of data. For more information on this feature, go to:&#160;<a href="http://www.ecma-international.org/publications/standards/Ecma-357.htm" style="font-size: 10.0pt;line-height: 13.0pt;" class="external-link" rel="nofollow">http://www.ecma-international.org/publications/standards/Ecma-357.htm</a><span style="font-size: 10.0pt;line-height: 13.0pt;"> or </span><a href="http://www.xml.com/pub/a/2007/11/28/introducing-e4x.html" style="font-size: 10.0pt;line-height: 13.0pt;" class="external-link" rel="nofollow">http://www.xml.com/pub/a/2007/11/28/introducing-e4x.html</a><span style="font-size: 10.0pt;line-height: 13.0pt;">.</span></p><p>The example below presents the code used to go through the XML returned:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: javascript; gutter: true" style="font-size:12px;">var NewDataSet = new XML(result);
for each(element in NewDataSet.Table) {
	dataset.addRow(new Array(element.ElementName.toString()));
}</pre>
</div></div><p>Once the Dataset code is implemented, you can view it, as shown in the figure below:</p><p><img class="confluence-embedded-image image-center" src="attachments/73082260/73406791.png" data-image-src="attachments/73082260/73406791.png"></p><p>&#160;</p><h5 id="IntegraçãoComAplicativosExternos-WebServicescomAutenticaçãoBásica">WebServices with Basic Authentication</h5><p>In order to use WebServices that use basic authentication (<em>WSS</em> or <em>WS-Security</em>), you need to use the&#160;<strong>getBasicAuthenticatedClient&#160;</strong>method located in the service provider (the same obtained through the <strong>ServiceManager).&#160;</strong>This method provides an authenticated client.</p><p>&#160;</p><p>The parameters that should be provided in the method follow this order:</p><ol><li>Service instance</li><li>Service class name</li><li>User for authentication</li><li>Password for authentication</li></ol><p>Using the example of the&#160;<strong>PeriodicTable&#160;</strong>service presented previously, the code of the call would have the changes below:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: javascript; gutter: true" style="font-size:12px;">var serviceLocator = serviceHelper.instantiate('net.webservicex.Periodictable');
var service = serviceLocator.getPeriodictableSoap();
var authenticatedService = serviceHelper.getBasicAuthenticatedClient(service, "net.webservicex.PeriodictableSoap", 'usuario', 'senha');
var result = authenticatedService.getAtoms();</pre>
</div></div><h5 id="IntegraçãoComAplicativosExternos-WebServicecomclientcustomizado"><span style="color: rgb(0,0,0);font-size: 1.8em;font-weight: bold;line-height: normal;"><br /></span>WebService with customized client</h5>    <div class="aui-message warning shadowed information-macro">
                    <p class="title">Attention</p>
                            <span class="aui-icon icon-warning">Icon</span>
                <div class="message-content">
                            <p>This technique is valid for Fluig 1.3.7 or higher.</p><p>In integrations that use services created with CXF with systems that do not support the HTTP/1.1 protocol (Protheus, for example), you need to use this method by setting the "disable.chunking" parameter to "true".</p>
                    </div>
    </div>
<p>To customize the client that accesses the services, you need to use the <strong>getCustomClient</strong>&#160;method, located in the service provider (the same that is obtained via&#160;<strong>ServiceManager</strong>). This setting requires the creation of a map of parameters with their respective values to pass to the method, as show by the <em style="line-height: 1.4285715;">snippet</em> below:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="theme: Eclipse; brush: js; gutter: false" style="font-size:12px;">		var properties = {};
		properties["basic.authorization"] = "true";
		properties["basic.authorization.username"] = "username";
		properties["basic.authorization.password"] = "password";
		properties["disable.chunking"] = "true";
		properties["log.soap.messages"] = "true";
		
		var serviceLocator = serviceHelper.instantiate('net.webservicex.Periodictable');
		var service = serviceLocator.getPeriodictableSoap();
		var customClient = serviceHelper.getCustomClient(service, "net.webservicex.PeriodictableSoap", properties);
		var result = customClient.getAtoms();</pre>
</div></div><p>&#160;</p><p>The following parameters can be set:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th class="confluenceTh">Property</th><th class="confluenceTh">Function</th></tr><tr><td class="confluenceTd"><pre>basic.authorization</pre></td><td class="confluenceTd"><p>When set to "true", it does the same as the&#160;<strong>getBasicAuthenticatedClient</strong> method, but allows you to apply authentication settings along with the other customizations below. In order to configure authentication<span style="line-height: 1.4285715;">, properties with "username" and "password" below must also be defined.</span></p></td></tr><tr><td class="confluenceTd"><pre>basic.authorization.username</pre></td><td class="confluenceTd">User to be used for basic authentication.</td></tr><tr><td class="confluenceTd"><pre>basic.authorization.password</pre></td><td class="confluenceTd">User password to be used for basic authentication.</td></tr><tr><td class="confluenceTd"><pre>disable.chunking</pre></td><td class="confluenceTd"><p>When set to "true", disables the sending of large requests in smaller "pieces". It can be useful when the service called does not support this type of request.</p></td></tr><tr><td colspan="1" class="confluenceTd"><pre>log.soap.messages</pre></td><td colspan="1" class="confluenceTd">When set to "true", allows the SOAP messages used in requests made to services to be presented in the server log, making it easier to debug in case of failures.</td></tr></tbody></table></div><p>&#160;</p><p><span style="color: rgb(0,0,0);font-size: 1.8em;font-weight: bold;line-height: normal;">Progress® Open AppServer</span></p><p>Thus since you can call operations in WebServices, Fluig also allows to make calls to programs in Progress® 4GL (or ABL) exposed through Progress® Open AppServer.</p><p>In the following examples, we create Datasets that, through service layer, will access 4GL logic, which will extract data. Although the 4GL codes in this example are very simple, they comprise the most common cases required on a day-to-day basis, since integration complexity is in the interfaces (input and output parameters) of each exposed procedure, not in its internal logic.</p><p>Note that the examples presented here intend to demonstrate the integration dynamics between Progress® and Fluig without going into specific details of the technologies involved. The Fluig Progress® service layer creates a JavaScript interface for the Progress® Open AppServer Client Java library and, therefore, for more information on how to integrate Java™ and Progress® applications, refer to the documentation provided by Progress®.</p><h3 id="IntegraçãoComAplicativosExternos-CasodeUso">Use Case</h3><p>The examples shown below, intend to create four Datasets&#160;<sup>1</sup> in Fluig:</p><ol><li><strong>Cost Center Types,&#160;</strong>which should return the cost center types existing in the application in Progress® (in this case, EMS2).</li><li><strong>Nature of Cost Centers,&#160;</strong>which should return the possible types of nature, according to the application in Progress® (in this case, EMS2).</li><li><strong>Cost Centers,&#160;</strong>you should return the records in the table conta&#160;<sup>2</sup>.</li><li><p><strong>Common Users,&#160;</strong>which should generate a list of common users for Fluig and the application in Progress® (using the table usuar_mestre).</p>    <div class="aui-message warning shadowed information-macro">
                            <span class="aui-icon icon-warning">Icon</span>
                <div class="message-content">
                            <p><span>1 - The examples use an EMS2 database for querying cost centers and users. However, overall, only two tables and 6 fields are used, which should not affect the understanding of the logic by the reader, nor prevent the creation of an equivalent scheme for testing, if required.</span></p><p><span>2 - The code presented for extracting cost centers has educational purposes only and cannot be considered for production use. For more information on how to extract cost centers from EMS2, see its technical documentation.</span></p>
                    </div>
    </div>
</li></ol><p>For the first three cases, the extraction logic of the desired information will be exposed in a program with several procedures, one for each need presented here:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>CostCenterUtils.p</b></div><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: javafx; gutter: true" style="font-size:12px;">/**************************************************************************
** Utility that provides procedures for extracting information
** on cost centers.
**************************************************************************/
DEFINE TEMP-TABLE ttCC NO-UNDO
    FIELD conta    LIKE conta.ct-codigo /* CHARACTER */
    FIELD natureza LIKE conta.natureza  /* INTEGER   */
    FIELD tipo     LIKE conta.tipo      /* INTEGER   */
    FIELD titulo   LIKE conta.titulo.   /* CHARACTER */
&#160;
/*-------------------------------------------------------------------
  Procedure: readCostCenters
   Objective: Returns a temp-table with the list of cost centers.
----------------------------------------------------------------------*/
PROCEDURE readCostCenters:
    DEFINE OUTPUT PARAMETER TABLE FOR ttCC.
    FOR EACH conta:
        CREATE ttCC.
        ASSIGN
            ttCC.conta    = conta.ct-codigo
            ttCC.natureza = conta.natureza
            ttCC.tipo     = conta.tipo
            ttCC.titulo   = conta.titulo.
    END.
END.
/*-------------------------------------------------------------------
  Procedure: readCostNatureTypes
   Objective: Returns a string with the natures of cost centers,
             separated by comma.
----------------------------------------------------------------------*/
PROCEDURE readCostNatureTypes:
    DEFINE OUTPUT PARAMETER cNatureList AS CHARACTER NO-UNDO.
    cNatureList = {adinc/i01ad047.i 03}.
END.
/*-------------------------------------------------------------------
  Procedure: readCostTypes
   Objective: Returns a string with the types of cost centers,
             separated by comma.
----------------------------------------------------------------------*/
PROCEDURE readCostTypes: 
    DEFINE OUTPUT PARAMETER cTypeList   AS CHARACTER NO-UNDO.
    cTypeList = {adinc/i02ad047.i 3}.
END.</pre>
</div></div><p>In the case of extracting users that are common to both products, a single program will be used, as shown in the code below:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>verifyUsers.p</b></div><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: javafx; gutter: true" style="font-size:12px;">/**************************************************************************
** Utility that receives a temp-table with a list of users and returns
** another with only the users from the list that are in the database.
**************************************************************************/
DEFINE TEMP-TABLE ttUsers
    FIELD cod_usuar   AS CHARACTER
    FIELD nom_usuario AS CHARACTER
    INDEX principal	  IS PRIMARY UNIQUE cod_usuar.
	
DEFINE TEMP-TABLE ttOutUsers LIKE ttUsers.
DEFINE INPUT  PARAMETER TABLE FOR ttUsers.
DEFINE OUTPUT PARAMETER TABLE FOR ttOutUsers.
FOR EACH ttUsers:
   IF CAN-FIND(usuar_mestre WHERE usuar_mestre.cod_usuar = ttUsers.cod_usuar) THEN DO:
        CREATE ttOutUsers.
        BUFFER-COPY ttUsers TO ttOutUsers.
    END.
END.</pre>
</div></div><p>Both codes presented have significant differences in the way they are used and the way they will be exposed by Progress®. In the first one, the program is loaded persistently and its procedures can be run independently. In the second case, the program is run in a non-persistent way and the main logic is in the main-block. The internal procedures, if any, are intended to improve code organization and cannot be used in isolation.</p><h3 id="IntegraçãoComAplicativosExternos-ConfiguraçãodoAppServer"><a name="_Toc324776230" rel="nofollow"></a>AppServer Configuration</h3><p>Some important information in the AppServer configuration:</p><ol><li>The AppServer should be loaded in Stateless mode;</li><li><p>In the agent configuration, in the Propath field, you should add the directory where compiled files are located (.r).</p>    <div class="aui-message warning shadowed information-macro">
                            <span class="aui-icon icon-warning">Icon</span>
                <div class="message-content">
                            <p><strong>Important:</strong> When a relative path (\\server\folder) is used, the Progress® Windows®service (AdminService) should be started with a network user that has access permission to the directory provided.</p>
                    </div>
    </div>
</li></ol><h3 id="IntegraçãoComAplicativosExternos-Expondocódigos4GLcomProxyGen">Exposing 4GL codes with ProxyGen</h3><p><span style="font-size: 10.0pt;font-family: Arial , sans-serif;">The first step to be able to run routines in Progress® 4GL is to create the client library, which is done by using the ProxyGen application, which is shipped with the Progress® installation, as shown in the example below.</span></p><p>Use the step-by-step to view the process of creating the proxy:</p>    
 
<a name="composition-deck-proxyGen"></a>
<div id="proxyGen" 
     class="deck"
     history="false" 
     loopcards="false" 
     effecttype="fade" 
     effectduration="0.5"
     nextafter="0.0">
    		<ul class="tab-navigation"></ul> <!-- // .tab-navigation -->    
            <div class="deck-cards panel" style="">	<div id="1" 
     class="deck-card  active-pane" 
     style="" 
     cssclass=""
	 accesskey=""
	 label="1&amp;ordm; Passo"
	 title=""
	 nextafter="0"
	 effecttype="default"
	 effectduration="-1.0"><p><span style="font-size: 10.0pt;line-height: 13.0pt;text-align: justify;">In the first screen of ProxyGen, the main point that should be noted is the name of the Project (in this example, EMSProxies). The information in this field will be used by ProxyGen to name the service access class, which will be used to configure the service in Fluig. In this screen, you also need to correctly configure the PROPATH, so that you can search for the compiled files (.r).</span></p><p><span style="font-size: 10.0pt;line-height: 13.0pt;text-align: justify;"><img class="confluence-embedded-image" src="attachments/73082260/73406790.png" data-image-src="attachments/73082260/73406790.png"><br /></span></p></div>
	<div id="2" 
     class="deck-card " 
     style="" 
     cssclass=""
	 accesskey=""
	 label="2&amp;ordm; Passo"
	 title=""
	 nextafter="0"
	 effecttype="default"
	 effectduration="-1.0"><p><span style="font-size: 10.0pt;line-height: 13.0pt;text-align: justify;">The second step consists in inserting which procedures will be exposed in a persistent or non-persistent way. The choice of each option to use depends on the way each exposed object was built. After the procedures are inserted, click the <strong>Generate</strong> option.</span></p><p><span style="font-size: 10.0pt;line-height: 13.0pt;text-align: justify;"><img class="confluence-embedded-image" src="attachments/73082260/73406789.png" data-image-src="attachments/73082260/73406789.png"><br /></span></p></div>
	<div id="3" 
     class="deck-card " 
     style="" 
     cssclass=""
	 accesskey=""
	 label="3&amp;ordm; Passo"
	 title=""
	 nextafter="0"
	 effecttype="default"
	 effectduration="-1.0"><p>D<span style="font-size: 10.0pt;line-height: 13.0pt;text-align: justify;">uring the </span><span style="font-size: 10.0pt;line-height: 13.0pt;text-align: justify;">process of generating the proxy, in the General tab, check the Java option in Client Proxy and enter the directory where the proxy is generated in the Output Dir. </span><span style="font-size: 10.0pt;line-height: 13.0pt;text-align: justify;">Also note the AppService field, it must be the </span><span style="font-size: 10.0pt;line-height: 13.0pt;text-align: justify;">name of the service posted in AppServer, otherwise it will be </span><span style="font-size: 10.0pt;line-height: 13.0pt;text-align: justify;">impossible to connect to the server.</span></p><p><span style="font-size: 10.0pt;line-height: 13.0pt;text-align: justify;"><img class="confluence-embedded-image" src="attachments/73082260/73406788.png" data-image-src="attachments/73082260/73406788.png"><br /></span></p></div>
	<div id="4" 
     class="deck-card " 
     style="" 
     cssclass=""
	 accesskey=""
	 label="4&amp;ordm; Passo"
	 title=""
	 nextafter="0"
	 effecttype="default"
	 effectduration="-1.0"><p><span style="font-size: 10.0pt;font-family: Arial , sans-serif;">The last relevant information for the proxy generation is the name of the package where the classes will be created. This information is used during the configuration of the Progress® service in Fluig. Finally click on the <strong>OK</strong> button.</span></p><p><span style="font-size: 10.0pt;font-family: Arial , sans-serif;">&#160;</span><img class="confluence-embedded-image" src="attachments/73082260/73406787.png" data-image-src="attachments/73082260/73406787.png"></p></div>
	<div id="5" 
     class="deck-card " 
     style="" 
     cssclass=""
	 accesskey=""
	 label="&amp;Uacute;ltimo Passo"
	 title=""
	 nextafter="0"
	 effecttype="default"
	 effectduration="-1.0"><p style="text-align: left;"><span style="font-size: 10.0pt;line-height: 13.0pt;text-align: justify;">After </span><span style="font-size: 10.0pt;line-height: 13.0pt;text-align: justify;">the classes are created, you need to package them in a .JAR file. This can be </span><span style="font-size: 10.0pt;line-height: 13.0pt;text-align: justify;">done in the command line using the command below:</span></p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
<pre>jar -cvf &lt;jar_file_name> &lt;directory></pre>
</div></div><p class="MsoNormal" style="margin-bottom: 6.0pt;text-align: justify;">However note that, in the file generated, the classes need to be in the correct directories. In the example shown, the<strong> com</strong> directory must be included and be at the root of the JAR file. <span style="font-size: 10.0pt;line-height: 13.0pt;">To be compatible with the ZIP format, another option is to generate a </span><span style="font-size: 10.0pt;line-height: 13.0pt;">file with the generated classes (respecting the directories) and rename it to </span><span style="font-size: 10.0pt;line-height: 13.0pt;">the .JAR extension.</span></p></div>
</div>
    </div> <!-- // .deck -->
    <div class="aui-message hint shadowed information-macro">
                            <span class="aui-icon icon-hint">Icon</span>
                <div class="message-content">
                            <p><span style="font-size: 10.0pt;font-family: Arial , sans-serif;">Depending on the version of Progress®, the screens can suffer some variation in the amount and placement of fields. See the documentation in case of doubt</span></p>
                    </div>
    </div>
<h3 id="IntegraçãoComAplicativosExternos-ConfiguraçãodoServiçonoFluig">Service Configuration in Fluig</h3><p>The registration of a service is performed through Fluig Studio, in the Services View<strong> through the Add Service option.&#160;</strong>The screen below shows the new service wizard and the fields used to register the Progress® service:</p><p><img class="confluence-embedded-image image-center" src="attachments/73082260/73406786.png" data-image-src="attachments/73082260/73406786.png"></p><p>Where:</p><ul><li><strong><strong>Server</strong>:&#160;</strong>Fluig server where the service will be added;</li><li><strong>Code:&#160;</strong>Unique code that will identify the service in the system.&#160;This code will be used in the JavaScript codes to have access to this service;</li><li><strong>Description:&#160;</strong>Text that describes the data service;</li><li><strong style="font-size: 10.0pt;line-height: 13.0pt;">URL:&#160;</strong><span style="font-size: 10.0pt;line-height: 13.0pt;">Identifies the AppServer service access URL, such as AppServer://&lt;server>/&lt;service_name>;</span><br /><span style="font-size: 10.0pt;line-height: 13.0pt;">In case you're not using the default NameServer, the NameServer access port must be provided. E.g.: AppServer://&lt;server>:&lt;NameServer_port>/&lt;service_name>.&#160;</span><br /><span style="font-size: 10.0pt;line-height: 13.0pt;">Note that depending on the service configuration and/or form of connection, the URL may change. Check the documentation of the Open AppServer for more information.</span></li><li><strong style="font-size: 10.0pt;line-height: 13.0pt;">Type:&#160;</strong><span style="font-size: 10.0pt;line-height: 13.0pt;">Identifies the service type (Progress or WebService). Progress should be selected;</span></li><li><strong style="font-size: 10.0pt;line-height: 13.0pt;">Remote Object:&#160;</strong><span style="font-size: 10.0pt;line-height: 13.0pt;">Identifies the proxy access class. This class is usually formed by the package name used for generating Proxy classes, plus the ProxyGen project name.&#160;</span><br /><span style="font-size: 10.0pt;line-height: 13.0pt;">Example: In the screens that present the ProxyGen, we used the package </span><strong style="font-size: 10.0pt;line-height: 13.0pt;">com.fluig.samples.ems</strong><span style="font-size: 10.0pt;line-height: 13.0pt;">, and the name given to the project in ProxyGen was </span><strong style="font-size: 10.0pt;line-height: 13.0pt;">EMSProxies</strong><span style="font-size: 10.0pt;line-height: 13.0pt;">. In this case, the class of the remote Object will be </span><strong style="font-size: 10.0pt;line-height: 13.0pt;">com.fluig.samples.ems.EMSProxies</strong><span style="font-size: 10.0pt;line-height: 13.0pt;">;</span></li><li><strong style="font-size: 10.0pt;line-height: 13.0pt;">User:&#160;</strong><span style="font-size: 10.0pt;line-height: 13.0pt;">User used when connecting to the service, as defined in the settings of the AppServer;</span></li><li><strong style="font-size: 10.0pt;line-height: 13.0pt;">Password:&#160;</strong><span style="font-size: 10.0pt;line-height: 13.0pt;">Password used when connecting to the service, as defined in the settings of the AppServer;</span></li><li><strong style="font-size: 10.0pt;line-height: 13.0pt;">Extra Parameters:&#160;</strong><span style="font-size: 10.0pt;line-height: 13.0pt;">Extra (and optional) parameters used for connecting to the AppServer. Check the documentation of the Open AppServer to check the options available in each version of the Progress®;</span></li><li><strong style="font-size: 10.0pt;line-height: 13.0pt;">Proxy file directory:&#160;</strong><span style="font-size: 10.0pt;line-height: 13.0pt;">.JAR file containing the classes generated by ProxyGen; the Select File button should be used to find it.</span><br /><span style="font-size: 10.0pt;line-height: 13.0pt;"><br /></span></li></ul><p>Once the service has been added, you can view the available classes and the methods that exist in each one of them. This information is important to guide the development of customization codes that will use this service. To view the service classes and methods, use the Service Query option in Services View, as in the screen below:</p><p><strong><img class="confluence-embedded-image image-center" src="attachments/73082260/73406785.png" data-image-src="attachments/73082260/73406785.png"><br /></strong></p><h3 id="IntegraçãoComAplicativosExternos-VisãoGeraldosObjetosEnvolvidos">Overview of Objects Involved</h3><p>Access to procedures presented in the AppServer involves four elements that interact with each other, as shown in the diagram below:</p><p>&#160;</p><p><img class="confluence-embedded-image image-center" src="attachments/73082260/73406794.png" data-image-src="attachments/73082260/73406794.png"></p><p>&#160;</p><p>Where:</p><ul><li><strong>Script Code</strong>: is the JavaScript code that will make use of the procedures presented in the AppServer. As previously mentioned, this JavaScript can be of any nature, such as the implementation of a Dataset or the customization of a process event.</li><li><strong>Service Provider:</strong> Object retrieved through ServiceManager.getService method that provides access to service features. This object is responsible for managing the connection and resources allocated by the service during script execution.</li><li><strong>Service Helper:</strong> Object retrieved through the getBean method in the ServiceProvider and that provides a set of utility methods that allow, among other things, to create Progress® specific objects (StringHolder, ResultSetHolder, etc.), to have access to the ProxyGen remote object and to instantiate classes. For more information about the Service Helper, query <a href="73082260.html">here</a>.</li><li><strong>ProxyGen Classes:</strong> Classes generated by ProxyGen and that will be used by the developer for the Progress® routine execution. The list of available classes, as well as their methods, can be viewed in the Fluig Studio Service View.</li></ul><div>&#160;</div><h5 id="IntegraçãoComAplicativosExternos-ProceduresPersistenteseNão-Persistentes">Persistent and Non-Persistent Procedures</h5><p>When a procedure is added to the ProxyGen project, it must be configured in two lists: Persistent or Non-Persistent Procedures This decision affects directly how these objects are accessed by the generated library and, consequently, how the developer will access them in JavaScript codes.</p><p>The procedures presented in a non-persistent way give rise to the methods in the class configured as Remote (or Proxy) object in the Service, and its execution is made by calling the corresponding method, for example:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
<pre>serviceHelper.getProxy().verifyUsers(inputTT, holder).</pre>
</div></div><p>The procedures presented in a persistent way give rise to new classes that can be instantiated through calls to methods in the Remote Object (through the Service View in Fluig Studio, you can check the available methods in the class) or through the <strong>createManagedObject</strong> method. The call through the <strong>createManagedObject</strong> method allows Fluig to have control over this object life cycle, freeing it automatically at the end of the method. If the object is instantiated, the developer must manually encode the object release (<strong>_ release ()</strong> method), otherwise there is the risk of blocking a new AppServer agent at each call to the method.</p><p>&#160;</p><h5 id="IntegraçãoComAplicativosExternos-ParâmetrosdeEntradaeSaída">Input and Output Parameters</h5><p>Another important point in 4GL routine calls is to observe the input and output parameter types for each procedure or program. Depending on the data type (CHARACTER, INTEGER, TEMP-TABLE, etc.), the parameter type (INPUT, INPUT-OUTPUT, BUFFER, etc.) and the Progress® version used, the way to handle these parameters may vary.</p><p>For the simplest types, like strings, dates or integer values, the ProxyGen uses a direct mapping to the Java™ language default types or classes. For complex types, such as temp-tables and buffers, ProxyGen uses classes that are part of the runtime library of these services.</p><p>When parameters are input and output (INPUT-OUTPUT) or output (OUTPUT), the primitive types need to be substituted by <em>Holder</em> classes, which will contain the value returned after the execution of the method. The most common examples are StringHolder or ResultSetHolder.</p><p>The data types used in each method can be consulted through the Fluig Studio Service View. Note that, depending on the Progress® version, there may be a variation in the types of parameters used and the way they are used. If in doubt, check the documentation provided by Progress®.</p><h3 id="IntegraçãoComAplicativosExternos-CriaçãodosDatasets">Dataset Creation</h3><p>Once the Progress® service is added to Fluig, you can use it at the points where the product allows customization using JavaScript, such as in the scripts for global events, process events, form definition events or Datasets.</p><p>The way to call the routines presented by service is always the same, regardless of which point is being called. However, to make it easier to understand the use of the Progress® services in Fluig and to make it easier to reproduce the examples presented in the reader's environment, all of the examples below will use Datasets as target.</p><p>As previously seen, the Datasets that will be presented here are <strong>Cost Center Types</strong>, <strong>Nature of the Cost Centers</strong>, <strong>Cost Centers</strong> and <strong>Users in Common</strong>.</p><p>&#160;</p><h5 id="IntegraçãoComAplicativosExternos-TiposdeCentrodeCusto">Cost Center Types</h5><p>The code below shows the implementation of the Cost Center Types Dataset. The explanation of each step of the implementation will be presented after the code:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>dsTipoCentroCusto.js</b></div><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: javascript; gutter: true" style="font-size:12px;">function createDataset(fields, constraints, sortFields) {
	
	//Step 1 - Creates the dataset
	var dataset = DatasetBuilder.newDataset();
    dataset.addColumn("id");
    dataset.addColumn("descricao");
   &#160;
	//Step 2 - Calls the service registered in Fluig
	var servico = ServiceManager.getService("EMS2");
&#160;
	//Step 3 - Loads the utility object for integration with Progress
    var serviceHelper = servico.getBean();
&#160;
	//Step 4 - Loads the CostCenterUtils.p persistent procedure
    var remoteObj = serviceHelper.createManagedObject("CostCenterUtils");
	//Step 5 - Calls the procedure that returns a string with the CC types
    var types = serviceHelper.createStringHolder();
    remoteObj.readCostTypes(types);
	//Step 6 - Breaks the string into an array with each of the types
    var typeArray = types.getStringValue().split(",");
&#160;
	//Step 7 - Add each type returned
    for(var pos = 0; pos &lt; typeArray.length; pos++) {
        dataset.addRow(new Array(pos + 1, typeArray[pos]));
    }
    return dataset;
}</pre>
</div></div><p>Where:</p><ul><li><strong>Step 1:&#160;</strong>Creates the dataset and adds its fields;</li><li><strong>Step 2:</strong>&#160;The registered service invocation is made in Fluig through the <strong>ServiceManager.getService</strong> method, and the value passed as parameter should be the service code. Note that at this point there's no need to provide any connection parameter in the service, since this has already been done in your registration;</li><li><strong>Step 3:</strong> Use the <strong>getBean</strong>&#160;method to return a utility object for Progress® services. This utility provides a series of methods that facilitate interaction with the generated proxy and its methods will be presented in more details later in this document;</li><li><strong>Step 4:</strong> Loads the <strong>CostCenterUtils</strong> object in a managed way through the <strong>createManagedObject</strong> method of the previously created utility;</li><li><strong>Step 5:</strong> Invokes the method desired, in this case <strong>readCostTypes</strong>, passing a StringHolder which will receive the output value;</li><li><strong>Step 6:</strong> Transforms the String received by the parameter in an array with the options. The , (comma) character is used to determine the breaking points of the string;</li><li><strong>Step 7:</strong> Goes through the array created, adding a row in the Dataset for each item in the array.&#160;</li></ul><p>The screen below shows the Dataset data view created:</p><p><img class="confluence-embedded-image" src="attachments/73082260/73406784.png" data-image-src="attachments/73082260/73406784.png"></p><p>&#160;</p><h5 id="IntegraçãoComAplicativosExternos-NaturezadosCentrosdeCusto">Nature of Cost Centers</h5><p>The Nature of Cost Centers Dataset is very similar to the cost center type Dataset. In practice, the only change is the called procedure:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>dsNaturezaCentroCusto.js</b></div><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: javascript; gutter: true" style="font-size:12px;">function createDataset(fields, constraints, sortFields) {
	var dataset = DatasetBuilder.newDataset();
    dataset.addColumn("id");
    dataset.addColumn("descricao");
	var servico = ServiceManager.getService("EMS2");
	var serviceHelper = servico.getBean();
	var remoteObj = serviceHelper.createManagedObject("CostCenterUtils");
	var types = serviceHelper.createStringHolder();
	remoteObj.readCostNatureTypes(types);
    var typeArray = types.getStringValue().split(",");
    for(var pos = 0; pos &lt; typeArray.length; pos++) {
        dataset.addRow(new Array(pos + 1, typeArray[pos]));
    }
    return dataset;
}</pre>
</div></div><p>After Dataset registration, you can view its content:</p><p><img class="confluence-embedded-image" src="attachments/73082260/73406783.png" data-image-src="attachments/73082260/73406783.png"></p><p>&#160;</p><h5 id="IntegraçãoComAplicativosExternos-CentrosdeCusto">Cost Centers</h5><p>The Cost Centers Dataset has a structure that is very similar to the two Datasets previously seen. The main difference is that, in this case, the procedure returns a temp-table with cost centers, which changes the way data is handled.</p><p>Depending on the Progress® version, the objects used may vary. The following are examples of encoding for Progress® 9 and OpenEdge® 10, respectively. In both cases, the result presented by the Dataset will be the same.</p><h6 id="IntegraçãoComAplicativosExternos-CodificaçãoProgress®9">Progress® 9 Encoding</h6><p>The temp-table in Progress® 9 are treated through objects that implement the java.sql.ResultSet interface:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>dsCentroCustoP9.js</b></div><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: javascript; gutter: true" style="font-size:12px;">function createDataset(fields, constraints, sortFields) {
    	
	//CreatesStep the1 structure- ofCreates the Dataset
    dataset
	var dataset = DatasetBuilder.newDataset();
    dataset.addColumn("contaid");
    dataset.addColumn("titulodescricao");
    dataset.addColumn("natureza");
    dataset.addColumn("tipo
	//Step 2 - Calls the service registered in Fluig
	var servico = ServiceManager.getService("EMS2");
    
	//RetrievesStep 3 - Loads the serviceutility andobject loadsfor theintegration remotewith objectProgress
    var servicoserviceHelper = ServiceManagerservico.getServicegetBean("EMS2");
 
	//Step 4 - var serviceHelper = servico.getBean();Loads the CostCenterUtils.p persistent procedure
    var remoteObj = serviceHelper.createManagedObject("CostCenterUtils");
	//Step 5 - Calls 
the procedure that returns a string //Readswith the currentCC accountstypes
    var holdertypes = serviceHelper.createResultSetHoldercreateStringHolder();
    remoteObj.readCostCentersreadCostTypes(holdertypes);
	//Step 6 - Breaks the string into an array with each of the types
    //Goesvar throughtypeArray the records, loading the Dataset with data= types.getStringValue().split(",");
 
	//Step 7 - Add each type returned
    for(var rspos = holder.getResultSetValue()0;
 pos <  while (rs.next())typeArray.length; pos++) {
        var conta 	 = rs.getObject("conta"dataset.addRow(new Array(pos + 1, typeArray[pos]));
    }
    var natureza = rs.getObject("natureza");
        var tipo 	 = rs.getObject("tipo");
        var titulo   = rs.getObject("titulo");
	
        dataset.addRow(new Array(conta, titulo, natureza, tipo));
    }
    
    return dataset;
}</pre>
</div></div><h6 id="IntegraçãoComAplicativosExternos-CodificaçãoOpenEdge®10">OpenEdge® 10 Encoding</h6><p>In OpenEdge® 10, the temp-tables returned are encapsulated as objects of the ProDataGraph class. This class is also used when you use parameters of the DATASET type:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>dsCentroCustoOE10.js</b></div><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: javascript; gutter: true" style="font-size:12px;">function return dataset;
}

function createDataset(fields, constraints, sortFields) {
    
	//Creates the structure of the Dataset
    var dataset = DatasetBuilder.newDataset();
    dataset.addColumn("contaid");
    dataset.addColumn("titulodescricao");
	var servico =  datasetServiceManager.addColumngetService("naturezaEMS2");
	var serviceHelper =  datasetservico.addColumngetBean("tipo");
    
	//Retrieves the service and loads the remote object
    var servicoremoteObj = ServiceManagerserviceHelper.getServicecreateManagedObject("EMS2CostCenterUtils");
    	var serviceHelpertypes = servico.getBean(serviceHelper.createStringHolder();
	remoteObj.readCostNatureTypes(types);
    var remoteObjtypeArray = serviceHelper.createManagedObjecttypes.getStringValue().split("CostCenterUtils,");
    
for(var pos =  //Reads the current accounts0; pos < typeArray.length; pos++) {
    var  holder = serviceHelper.createProDataGraphHolder()dataset.addRow(new Array(pos + 1, typeArray[pos]));
    remoteObj.readCostCenters(holder);}
    
	//Goes through the records, loading the Dataset with data
    var ttCC = holder.getProDataGraphValue().getProDataObjects("ttCC");
    for (var row_index = 0; row_index &lt; ttCC.size(); row_index++) {
        var row = ttCC.get(row_index);
        dataset.addRow(new Array(row.get("conta"),
                                 row.get("titulo"),
                                 row.get("natureza"),
                                 row.get("tipo")));
    }
    
    return dataset;
}</pre>
</div></div><p>Dataset View:</p><p><img class="confluence-embedded-image" src="attachments/73082260/73406782.png" data-image-src="attachments/73082260/73406782.png"></p><p>&#160;</p><h5 id="IntegraçãoComAplicativosExternos-UsuáriosemComum">Users in Common</h5><p>The first difference between the users in common Dataset and the previous examples is that, in this case, you must pass a temp-table as a parameter to the procedure called.</p><p>The second difference is that the 4GL code is implemented in a non-persistent program, which changes the way the logic is called from the JavaScript code.</p><p>The third difference that can be observed in this case is that it is possible to transform a Dataset into the data types required by Progress® (ResultSet or ProDataGraph).</p><h6 id="IntegraçãoComAplicativosExternos-CodificaçãoProgress®9.1">Progress® 9 Encoding</h6><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>dsUsuariosComunsP9.js</b></div><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: javascript; gutter: true" style="font-size:12px;">function createDataset(fields, constraints, sortFields) {
    
    //Creates the new Dataset
    var dataset = DatasetBuilder.newDataset();
    dataset.addColumn("usuario");
    dataset.addColumn("nome");
    
	//Retrieves Fluig users
    var campos = new Array("colleaguePK.colleagueId", "colleagueName");
    var colleaguesDataset = DatasetFactory.getDataset("colleague", campos, null, null);
    
    //Instantiates the service
    var servico = ServiceManager.getService("EMS2");
    var serviceHelper = servico.getBean();
    
    //Transforms the dataset in a ResultSet (v9) and creates holder for the output
    var inputTT = colleaguesDataset.toResultSet();
    var holder = serviceHelper.createResultSetHolder();
    
    //Calls the procedure in Progress
    serviceHelper.getProxy().verifyUsers(inputTT, holder);
    
    var rs = holder.getResultSetValue();
    while (rs.next()) {
        dataset.addRow(new Array(rs.getObject("cod_usuar"), rs.getObject("nom_usuario")));
    }
    
    return dataset;
}</pre>
</div></div><h6 id="IntegraçãoComAplicativosExternos-CodificaçãoOpenEdge®10.1">OpenEdge® 10 Encoding</h6><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>dsUsuariosComunsOE10.js</b></div><div class="codeContent panelContent pdl">
<pre class="first-line: 1; theme: Eclipse; brush: javascript; gutter: true" style="font-size:12px;">function createDataset(fields, constraints, sortFields) {
    
	//Creates the new Dataset
    var dataset = DatasetBuilder.newDataset();
    dataset.addColumn("usuario");
    dataset.addColumn("nome");
    
	//Retrieves Fluig users
    var campos = new Array("colleaguePK.colleagueId", "colleagueName");
    var colleaguesDataset = DatasetFactory.getDataset("colleague", campos, null, null);
    
    //Instantiates the service
    var servico = ServiceManager.getService("EMS2");
    var serviceHelper = servico.getBean();
	
    //Transforms the dataset in a ProDataGraph (v10) and creates holder for output
    var inputTT = serviceHelper.toProDataGraph(colleaguesDataset);
    var holder = serviceHelper.createProDataGraphHolder();
    
    //Calls the procedure in Progress
    serviceHelper.getProxy().verifyUsers(inputTT, holder);
    
    var ttCC = holder.getProDataGraphValue().getProDataObjects("ttOutUsers");
    for (var row_index = 0; row_index &lt; ttCC.size(); row_index++) {
        var row = ttCC.get(row_index);
        dataset.addRow(new Array(row.get("cod_usuar"), row.get("nom_usuario")));
    }
    
    return dataset;
}</pre>
</div></div><p>Dataset View:</p><p><img class="confluence-embedded-image" src="attachments/73082260/73406781.png" data-image-src="attachments/73082260/73406781.png"></p><p><span class="confluence-anchor-link" id="IntegraçãoComAplicativosExternos-servicehelper"></span></p><h3 id="IntegraçãoComAplicativosExternos-ServiceHelper">Service Helper</h3><p>The table below shows the list of existing methods in the utility class for Progress® services:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th class="confluenceTh">Return</th><th class="confluenceTh">Method and Description</th></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>createBigDecimalHolder</strong></span>()</code><div class="block">Creates a Holder object for the DECIMAL type</div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>createBooleanHolder</strong></span>()</code><div class="block">Creates a Holder object for the LOGICAL type</div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>createByteArrayHolder</strong></span>()</code><div class="block">Creates a Holder object for the RAW type</div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>createCOMHandleHolder</strong></span>()</code><div class="block">Creates a Holder object for the COM-HANDLE type</div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>createDateHolder</strong></span>()</code><div class="block">Creates a Holder object for the DATE type</div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>createHandleHolder</strong></span>()</code><div class="block">Creates a Holder object for the WIDGET-HANDLE type (Handle)</div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>createIntHolder</strong></span>()</code><div class="block">Creates a Holder object for the INTEGER type</div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>createLongHolder</strong></span>()</code><div class="block">Creates a Holder object for the RECID type</div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>createManagedObject</strong></span>(java.lang.String&#160;objName)</code><div class="block">Reads a .p or .r file which has been exposed through AppServer in a persistent way. <span style="color: rgb(53,56,51);">Through this method, the service provider can manage the life cycle of these objects, releasing them at the end of script execution.</span></div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>createMemptrHolder</strong></span>()</code><div class="block">Creates a Holder object for the MEMPTR type</div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>createProDataGraph</strong></span>(java.lang.Object&#160;metadata)</code><div class="block">Creates an object of the ProDataGraph class</div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>createProDataGraphHolder</strong></span>()</code><div class="block">Creates a Holder object for the ProDataGraphHolder type</div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>createProDataGraphMetaData</strong></span>(java.lang.String&#160;name)</code><div class="block">Creates an object of the ProDataGraphMetadata class</div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>createProDataObjectMetaData</strong></span>(java.lang.String&#160;tableName, int&#160;numFields, boolean&#160;bimageFlag, int&#160;numIndexes, java.lang.String&#160;multiIxCols, java.lang.String&#160;XMLNamespace, java.lang.String&#160;XMLPrefix)</code><div class="block">Creates an object of the ProDataObjectMetadata class.</div><div class="block">Creates an object for a dataset (Temp-table).</div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>createResultSetHolder</strong></span>()</code><div class="block">Creates a Holder object for the TABLE type</div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>createRowidHolder</strong></span>()</code><div class="block">Creates a Holder object for the ROWID type</div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>createStringHolder</strong></span>()</code><div class="block">Creates a Holder object for the CHARACTER type.</div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>getProxy</strong></span>()</code><div class="block">Returns the instance of the connection object to the AppServer, already connected and available for use. <span style="color: rgb(53,56,51);">The remote object is the main class generated by ProxyGen.</span></div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>instantiate</strong></span>(java.lang.String&#160;className)</code><div class="block">Instantiates an object of a class inside the proxy library.</div></td></tr><tr><td class="confluenceTd"><code>java.lang.Object</code></td><td class="confluenceTd"><code><span style="color: rgb(51,102,255);"><strong>toProDataGraph</strong></span>(com.datasul.technology.webdesk.dataset.DefaultDataset&#160;d)</code><div class="block">Transforms a dataset into a ProDataGraph.</div></td></tr></tbody></table></div><h1 id="IntegraçãoComAplicativosExternos-ThirdPartyTrademarks">Third Party Trademarks</h1><p>Adobe and&#160;Flex Builder&#160;are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.</p><p>Apache Flex is a&#160;registered&#160;trademark of The Apache Software Foundation.</p><p>JavaScript is a trademark of Oracle Corporation.</p><p>Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States and/or other countries.</p><p>Java is a trademark of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.</p><p>Progress and OpenEdge are trademarks or registered trademarks of Progress Software Corporation or one of its subsidiaries or affiliates in the U.S. and other countries.</p><p>This product includes software developed by the Visigoth Software Society.</p><p><span style="font-size: 10.0pt;line-height: 13.0pt;">Any other third party trademarks are the property of their respective owners.</span></p><p><span style="font-size: 10.0pt;line-height: 13.0pt;"><br /></span></p>
                    </div>
                                      

return dataset;
}

function createDataset(fields, constraints, sortFields) {
    
	//Creates the structure of the Dataset
    var dataset = DatasetBuilder.newDataset();
    dataset.addColumn("conta");
    dataset.addColumn("titulo");
    dataset.addColumn("natureza");
    dataset.addColumn("tipo");
    
	//Retrieves the service and loads the remote object
    var servico = ServiceManager.getService("EMS2");
    var serviceHelper = servico.getBean();
    var remoteObj = serviceHelper.createManagedObject("CostCenterUtils");
    
    //Reads the current accounts
    var holder = serviceHelper.createResultSetHolder();
    remoteObj.readCostCenters(holder);
    
    //Goes through the records, loading the Dataset with data
    var rs = holder.getResultSetValue();
    while (rs.next()) {
        var conta 	 = rs.getObject("conta");
        var natureza = rs.getObject("natureza");
        var tipo 	 = rs.getObject("tipo");
        var titulo   = rs.getObject("titulo");
	
        dataset.addRow(new Array(conta, titulo, natureza, tipo));
    }
    
    return dataset;
}

function createDataset(fields, constraints, sortFields) {
    
	//Creates the structure of the Dataset
    var dataset = DatasetBuilder.newDataset();
    dataset.addColumn("conta");
    dataset.addColumn("titulo");
    dataset.addColumn("natureza");
    dataset.addColumn("tipo");
    
	//Retrieves the service and loads the remote object
    var servico = ServiceManager.getService("EMS2");
    var serviceHelper = servico.getBean();
    var remoteObj = serviceHelper.createManagedObject("CostCenterUtils");
    
    //Reads the current accounts
    var holder = serviceHelper.createProDataGraphHolder();
    remoteObj.readCostCenters(holder);
    
	//Goes through the records, loading the Dataset with data
    var ttCC = holder.getProDataGraphValue().getProDataObjects("ttCC");
    for (var row_index = 0; row_index < ttCC.size(); row_index++) {
        var row = ttCC.get(row_index);
        dataset.addRow(new Array(row.get("conta"),
                                 row.get("titulo"),
                                 row.get("natureza"),
                                 row.get("tipo")));
    }
    
    return dataset;
}

function createDataset(fields, constraints, sortFields) {
    
    //Creates the new Dataset
    var dataset = DatasetBuilder.newDataset();
    dataset.addColumn("usuario");
    dataset.addColumn("nome");
    
	//Retrieves Fluig users
    var campos = new Array("colleaguePK.colleagueId", "colleagueName");
    var colleaguesDataset = DatasetFactory.getDataset("colleague", campos, null, null);
    
    //Instantiates the service
    var servico = ServiceManager.getService("EMS2");
    var serviceHelper = servico.getBean();
    
    //Transforms the dataset in a ResultSet (v9) and creates holder for the output
    var inputTT = colleaguesDataset.toResultSet();
    var holder = serviceHelper.createResultSetHolder();
    
    //Calls the procedure in Progress
    serviceHelper.getProxy().verifyUsers(inputTT, holder);
    
    var rs = holder.getResultSetValue();
    while (rs.next()) {
        dataset.addRow(new Array(rs.getObject("cod_usuar"), rs.getObject("nom_usuario")));
    }
    
    return dataset;
}

function createDataset(fields, constraints, sortFields) {
    
	//Creates the new Dataset
    var dataset = DatasetBuilder.newDataset();
    dataset.addColumn("usuario");
    dataset.addColumn("nome");
    
	//Retrieves Fluig users
    var campos = new Array("colleaguePK.colleagueId", "colleagueName");
    var colleaguesDataset = DatasetFactory.getDataset("colleague", campos, null, null);
    
    //Instantiates the service
    var servico = ServiceManager.getService("EMS2");
    var serviceHelper = servico.getBean();
	
    //Transforms the dataset in a ProDataGraph (v10) and creates holder for output
    var inputTT = serviceHelper.toProDataGraph(colleaguesDataset);
    var holder = serviceHelper.createProDataGraphHolder();
    
    //Calls the procedure in Progress
    serviceHelper.getProxy().verifyUsers(inputTT, holder);
    
    var ttCC = holder.getProDataGraphValue().getProDataObjects("ttOutUsers");
    for (var row_index = 0; row_index < ttCC.size(); row_index++) {
        var row = ttCC.get(row_index);
        dataset.addRow(new Array(row.get("cod_usuar"), row.get("nom_usuario")));
    }
    
    return dataset;
}