{{indexmenu_n>1}}
====== Integration Connector with  Web Service ======
\\
\\
XOne has a connector to perform an integration between a database and a Web Service. \\
\\
We have to indicate that is complicated having a single connector for all the Web Services there are, since each one of them is different and they do not have anything generic, so therefore for almost all the Web Services integrations, the connector will have to be modified for its proper functioning.\\
\\
\\
Its configuration is done in the same way to the database connector, so they will have a config file to tell where is the XML file that has the integration itself.\\
\\
<box 90% blue left| ** [[wiki:3.-servidor:307.-bus-integracion:307.04.-conector-web-service:ITFWebService]].exe.config **> 
This field is the first one that reads the executable, and it is used to tell which one is the configuration file of the main data, as well as the name.\\
\\
<code xml>
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <appSettings>
    <!--
     **** VALORES GENERALES
    -->
    <!-- Nombre de la aplicación usado para mostrar mensajes en el visor de sucesos -->
    <add key="Application Name" value="Xone Integration Service" />
    <!-- Código devuelto por el webservice para determinar que los datos han sido recibidos correctamente -->
    <add key="Result Code Ok" value="00" />
    <!-- Código devuelto por el webservice para determinar que los datos han sido recibidos correctamente, pero que hay una advertencia -->
    <add key="Result Code Warning" value="50" />
    <!-- Nombre del campo ROWID de la base de datos, en ORACLE es palabra reservada y suele usarse CGSROWID -->
    <add key="ROWID Field Name" value="ROWID" />
    <!-- Nombre del campo SQL de la base de datos, en MYSQL es palabra reservada y suele usarse CGSSQL -->
    <add key="SQL Field Name" value="CGSSQL" />
    <!-- Numero de MID que se quiere usar para insertar las operaciones en el master_replica_queue -->
    <add key="MID Number" value="9999" />
    <!-- Ruta del intercliente de donde vamos a coger todas las transformaciones -->
    <add key="XML Path" value="C:\loquesea\interclient.xml" />
    <!-- Intervalo entre ejecucion y ejecucion de la interface, expresado en segundos -->
    <add key="Timer" value="60" />
    <!--
     **** VALORES PARA AUTOREGISTRO (GENERATE ADM DEVICE)
    -->
    <!-- IP en la que esta instalado el servidor de replica -->
    <add key="Replicator Server Address" value="IP del server de replica" />
    <!-- Puerto de escucha del servidor de replica -->
    <add key="Replicator Server Port" value="Puerto del server de replica" />
    <!-- DBLIC de la base de datos en la que queremos generar la licencia -->
    <add key="Replicator DataBase Number" value="10000026" />
    <!-- Formato de fecha de replica del dispositivo que vamos a firmar -->
    <add key="Replicator Client DLDATE" value="ymd" />
    <!-- Formato de fecha de replica del dispositivo que vamos a firmar -->
    <add key="Replicator Client RPDATE" value="ymd" />
    <!--
     **** OTROS VALORES
    -->
    <!-- Indica si queremos generar una DLL a partir de un fichero dado -->
    <add key="Generate wrapper" value="false" />
    <!-- Nombre de la tabla donde se guardan los errores generados por la interface -->
    <add key="Interclient Error Log Table" value="interclient_error_log" />
    <!-- Consulta de creacion de la tabla de sincronizacion, necesarias para la ejecucion de la interface -->
    <add key="Create Sync Table Stmt" value="CREATE TABLE interclient_sync_tables(&#xD;&#xA;    [ID] [int] IDENTITY(1,1) NOT NULL,&#xD;&#xA;    [OBJECTNAME] [nvarchar](50),&#xD;&#xA;    [LASTMODIFIED] [datetime] NULL,&#xD;&#xA;    [LASTCHARID] [nvarchar](50) COLLATE Modern_Spanish_CI_AS NULL,&#xD;&#xA;    [LASTNUMBERID] [int] NULL,&#xD;&#xA;    CONSTRAINT [PK__interclient_sync_tables__01234A04] PRIMARY KEY CLUSTERED&#xD;&#xA;    (&#xD;&#xA;    [ID] ASC&#xD;&#xA;    )WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY]&#xD;&#xA;    ) ON [PRIMARY]" />
    <!-- Consulta de creacion de la tabla de errores, necesarias para la ejecucion de la interface -->
    <add key="Create Sync Error Stmt" value="CREATE TABLE interclient_error_log(&#xD;&#xA;    [ID] [int] IDENTITY(1,1) NOT NULL,&#xD;&#xA;    [SOURCE] [nvarchar](150),&#xD;&#xA;    [ERRORCODE] [nvarchar](50),&#xD;&#xA;    [MESSAGE] [nvarchar](255),&#xD;&#xA;    [TEXT] [ntext],&#xD;&#xA;    CONSTRAINT [PK__interclient_error_log__01234B04] PRIMARY KEY CLUSTERED&#xD;&#xA;    (&#xD;&#xA;    [ID] ASC&#xD;&#xA;    )WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY]&#xD;&#xA;    ) ON [PRIMARY]" />

    <!-- .NET VALUES -->
    <add key="ClientSettingsProvider.ServiceUri" value="" />
  </appSettings>
</configuration>
</code>

</box>
\\
===== Interclient =====

\\
Configuration file where the integration is going to be performed between the source system, the client system and the XOne system.\\

\\
\\
^   Nodes   ^^
|<**?xml version** >=**"1.0" encoding="ISO-8859-1"**?>| Node put in the upper part of the file. It is useful to use the  ISO-8859-1 codification, and admits the accents, among other things.  **OPTIONAL**.|
|<**xml**>| Main node, it is the father of all the nodes, and every file must has this node, in which everything else will go.  **MANDATORY**.|
|<**interface**>| Node child of the xml node, within this will go the rest of the options.   **MANDATORY**.|
\\
====  APP Node ====

<box 100% blue left| ** APP **> 

**Node in which is defined who are the source and destination databases in order to make the  Interface. MANDATORY. This node has several attributes that are: **


^       Attributes      ^ Description ^
| NAME | "INTERFACE": Name of the application.  |
| LOGOPER | "true": to enable the LOG, by showing everything the <nowiki>CGInterclientXone</nowiki> does in the Windows Events Visor. |
\\


<box 90% green left| ******  Connection  ******  > 
\\
**Node in which are placed the calls to the databases which the interface interacts with. It is made up for child nodes, with the calls to the databases.**
\\
^  Nodes         ^ Description ^
|  client       | Node that has the call to the source database, the database to mobility, that always will be the client database.|
|  source       | Node that has the call to the destination database, the XOne database.  |
|  optional     | It is a connection with an optional database (auxiliary) can be the same as the one that exists in the  client or source nodes, or it may be a different connection. It can be put all the optional nodes as needed, it is not limited to 1. They are called by making reference to its name (it is explained later in  DATA-SOURCE, DATA-DEST). |
\\
\\

^  Type   ^   Connstring   ^   User   ^    Pwd      ^
|  MYSQL      | connectionString="Persist Security Info=False;database=salesdemo;server=IPSERVIDORBD;user id=user;Password=pass" | usuario | contraseña |
|  SQLSERVER  | connectionString="Data Source=IPSERVIDORBD;Initial Catalog=beltranprod;Persist Security Info=True;User ID=user;Password=pass" | usuario | contraseña |
|  ORACLE     | connectionString="Data Source=CGS;Persist Security Info=True;User ID=user;Password=pass;Unicode=True" | usuario | contraseña |
|  ODBC       | DSN=nombredsnsistema;uid=usuario;pwd=clave | usuario | contraseña |
|  <nowiki>OLeDB</nowiki>      | provider=ej.[SQLOLEDB.1,MSDAORA...];data source=DATASOURCE;user id=USER;password=PWD.. | usuario | contraseña |
|  WEB        | url="Direccion del webservice" endpoint="Nombre del endpoint" wsdl="" wrapper="DLL que usaremos para conectarnos" class="Nombre de la clase principal de la DLL" | usuario | contraseña |
\\
\\


Sample code of the APP node. Each of the connections that can be identified is specified.\\
\\
<code xml>
<app name="ITF_PRUEBA" logoper="false">
   <!--
     logoper - deja log de todas las operaciones que realiza la interface, por defecto es false
   -->
   <dsn>
	<!--
	provider: especificamos el provider de la conexión, interpretando SqlClient, OracleClient, MySQLClient, SQLServerCE, 
	OleDB y ODBC. Por defecto es ODBC.
	connstring: cadena de conexión de la base de datos
        -->
	<client type="WEB" name="webservice-demo" persistent="true" url="https://localhost/services/WebservicesInHandler" endpoint="WebservicesInHandler" wsdl="" wsdl2="" wrapper="XOneWrapper" class="WebservicesInHandlerService"/>		
	<source type="ODBC" name="connstr1" connstring="DSN=Localhost_DES;Database=database;UID=root;PWD=password" user="root" pwd="password" />
	<lastmodified type="ODBC" name="connstr2" connstring="DSN=Localhost_DES;Database=database;UID=root;PWD=password" user="root" pwd="password" />
	<optional name="NOMBRE3" type="MYSQL" connstring="......."/>
	<!--
	Se pueden definir todas las conexiones optional que se deseen (conexion auxiliar), se llaman seleccionando 
	su "name" en data-source o data-dest dependiento de si se usan como source o dest en la transformación, 
	dentro del nodo coll
	-->
	<!-- Conexiones de ejemplo 
	**ODBC**:  dsn=nombredsnsistema;uid=usuario;pwd=clave
	**OleDB**: type=ej.[SQLOLEDB.1,MSDAORA...];data source=DATASOURCE;user id=USER;password=PWD..
	**System.Data.SqlClient**: User ID=USER;Password=PWD;Initial Catalog=BD;Data Source=DATASOURCE...
	**MySql.Data.MySqlClient**:Database=[NOMBRE BD];Data Source=[SERVIDOR{localhost...}];User Id=[USER];Password=[PASSWORD]
	**System.Data.OracleClient**: Data Source=[datasource{tns service name}];Persist Security Info=False;User ID=[user];Password=[password];Unicode=True 
	-->
    </dsn>
</app>
</code>
</box> 




</box> 
\\
\\
\\
====  TRANSFORMS Node====

<box 100% blue left| ** TRANSFORMS **> 

**Node that defines the data delivery address, by deciding which connection is the source and which one is the destination, being able to vary between client-to-source or source-to-client**.\\
\\
^   ADDRESS TYPE   ^   DESCRIPTION   ^
|  **client-to-source**  | Definition of the source table the connection of the  **client** node and as destination the **source** connection. This connection is what is used to replicate the information to the devices, since it inserts the SQL senteces in the **master_replica_queue.** table.|
|  **source-to-client**  | Definition of the source table the connection of the  **source** node and as destination the **client** connection. With this option nothing is written in any additional table, only in that one that is defined to which table the destination data go to.  |
\\
</box> 
\\
\\
\\
Once 
Once it has been decided in which order the data are transferred, each of the  // transform // nodes are defined, which are the ones that carry out the transfer of data from one table to another.\\


====  TRANSFORM Node====

Node  which the data of that transformation are defined in.\\
  
\\
The attributes of the node are: 
\\
^  ATTRIBUTE  ^   DESCRIPTION   ^
|  name  | Name of the transformation.  |
| iteration | Attribute that indicates if the calls to the  web service must be done by iterating over a database query, by default false |
| iteration-source | It indicates the query on which we should iterate if the iteration attribute is established to true. The data recovered by this query can be used with the ##EXTRADATA## macro followed by the  (##EXTRADATA##) field. |
<box 100% blue left| ** TRANSFORM **> 

Node that defines the transfer of data to be made. Each transform is for one or several tables that are dependent on each other, and only has one attribute, ** name **, which must be unique for the entire xml configuration file of the interface. If there is an error, the log will show the name of the transforms where it is and where the possible error occurred.\\

\\
<note important>
It is important to remark that if there were a fail when executing the active **transform**, it will skip to the following  **transform** node, so that the tables dependent on each other have to go in the same **transform** node consecutively. Therefore, the tables not dependent, or in which an error was occurred in the previous ones can continue with it, they must go in different  **transform** node.
</note>
\\
\\
Transformation with a unique coll node, in such way that the table does not depend on other tables.  
<code xml>
<transform name="modificados">
     <coll dest-table="gen_tmp" source-table="##WEBMETHOD##" not-replicate="true">
	<function name="getRegCambios" class="XOneWrapper.expService">
	    <param name="fecha" value="##NOW##" type="D" />
	    <param name="fechaSpecified" value="true" type="NC" />
	</function>
	<coll dest-table="gen_tmp" source-table="##PARENT##.id" not-replicate="true">
	     <prop source-name="" dest-name="ID" type="N" />
             <prop source-name="##PARENT##.##PARENT##.fechaCambio" dest-name="FECHA" type="D">
		<oper type="copy"/>
		<format name="dest-name" value="yyyy/MM/dd"/>
             </prop>
	     <prop source-name="explo" dest-name="EXPLOTACION" type="T" key="true">
		<oper type="copy"/>
	     </prop>
	     <prop source-name="coEspecie" dest-name="CO_ESPECIE" type="T" key="true">
		<oper type="copy"/>
	     </prop>
	     <prop source-name="BAJADO" dest-name="BAJADO" type="N">
		<oper type="setval" value="0"/>
	     </prop>
	</coll>
     </coll>
</transform>
</code>
\\
Transform with two coll nodes, that have been inserted in the same transform, because they are tables dependent on each other, and  if it does not transfer the data from the first one, the second one must not be inserted. \\
<code xml>
<transform name="datos" >
	<coll dest-table="gen_explotacion" source-table="##WEBMETHOD##">
		<function name="getDatos" class="XOneWrapper.Service">
			<param name="rega" value="COD2266" type="T"/>
			<param name="co_especie" value="COD344JK" type="T"/>
		</function>
		
		<prop source-name="" dest-name="ID" type="N" />
		<prop source-name="ads" dest-name="ADSG_TEX" type="T">
			<oper type="copy"/>
		</prop>
		<prop source-name="Menores6Meses" dest-name="ANM_6MES" type="N2">
			<oper type="copy"/>
		</prop>
		<prop source-name="censoActual" dest-name="CENSO" type="N2">
			<oper type="copy"/>
		</prop>
		<prop source-name="cp" dest-name="CP" type="T">
			<oper type="copy"/>
		</prop>
		<prop source-name="dir" dest-name="ENDEREZO" type="T">
			<oper type="copy"/>
		</prop>

		<coll dest-table="gen_anim" source-table="##PARENT##.maxAnimales">
			<prop source-name="" dest-name="ID" type="N" />
			<prop source-name="ESPECIE" dest-name="IDEXPLOTACION" type="N" key="true">
				<oper type="mapval" source="gen_explotacion" targetfld="ID">
					<prop mapfld="ESPECIE" mapvalue="##SELF##"/>
					<prop mapfld="REGA" mapvalue="REGA"/>
				</oper>
			</prop>
			<prop source-name="categoria" dest-name="CATEGORIA" type="T">
				<oper type="copy"/>
			</prop>
			<prop source-name="especie" dest-name="ESPECIE" type="T">
				<oper type="copy"/>
			</prop>
			<prop source-name="fcenso" dest-name="FCENSO" type="D">
				<oper type="copy"/>
				<format name="dest-name" value="yyyy/MM/dd"/>
			</prop>
		</coll>
		
		<after-action>
			<action name="execute-query">
				<param name="source" with-replica="false" value="UPDATE GEN_TMPREGA SET BAJADO=1 WHERE EXPLOTACION='COD2266' AND CO_ESPECIE='COD344JK'"/>
			</action>
		</after-action>
	</coll>
</transform>
</code>

</box> 
\\
\\
\\

====  COLL Node ====
\\

Node in which the origin and destination tables of the data to be integrated are taken.\\
 
\\
The attributes of the node are:
\\
^  ATTRIBUTE  ^   DESCRIPTION   ^
| dest-table  | Name of the destination table.   |
| source-table  | Selection from a query of the data to be integrated from the source in the destination.  |
| type-not-allowed  | It may take  1 and 3 values, so that if the value is  1, it will not execute inserts and with value 3 it will not execute updates. |
| extrainfo  | By default true. With false value it would not leave record in the master_replica_queue table. |
| data-source  | Attribute that admits the name of any connection  <optional> on we want to get the source of the coll data, if we want it to be different from the one that was configured by default in the client node or source node in interface/app/connection.  |
| data-dest  | Attribute that admits the name of any connection  <optional> on we want to get the destination of the coll data, if we want it to be different from the one that was configured by default in the client node or source node in interface/app/connection.  |
| name | Name of the function to which we are going to call. |
| not-replicate | The changes made do not insert records in the master_replica_queue table, by default false |
| continue-errors | It indicates whether records should continue to be transferred from the current query although one of them gives error, by default  false. |
\\
\\

Within the coll node, each and every one of the fields that have to be transferred from one table to another will be placed. For this purpose, different nodes ** prop ** are set, which will be those with the name of the source field and the name of the destination field. Subsequently several attributes will be defined defining the type or what type of action has to be performed.
\\

====  PROP Node ====

Node in which you define which field is transferred and what action is performed in the destination table.
\\
The attributes of this node are:\\
\\
^  ATTRIBUTE  ^   DESCRIPTION   ^
|  source-name  | Name of the source field  |
|  dest-name  | Name of the destination field.  |
|  type  | Attribute to tell the type of data of the field that are going to be transferred. The options are: **T**(text type field). **Nx**:(numeric field. The x character means that it can be put the number of decimals it has. It will vary between do not putting anything, N, or putting the number of decimals that are going to be transferred,  N2, N3, N4, etc.) **D:**(date type field.) **X:**(To pass data that are going to be keys.) |
|  key  | To tell it if the field is a primary key or it does not in the destination table. By this field will be made the query about if the record exits in the destination table. The key, of course, may be multiple, so it may exist more than one field being the primary key of the record.  **This field is mandatory that as minimum in one of the  “prop” that the “coll” has, this attribute has to be true**. |
|  saved-source  | Attribute that is going to save the value of the  **source-name** field into a macro, tor later performing operations on the fields that meet the condition that the macro saves. The macro is **##SOURCEKEYVALUES##**.  |
|  saved-dest  | Attribute that saves the values of the  **dest-name** field into a macro, for later operating with the records that meet the condition. The macro **##DESTKEYVALUES##**.  |
|  always-update  | If the attribute is to **true** we are forcing it to insert an update at the “master_replica_queue” replica queue, even if its value does not change.  |
\\
\\
Once we define which field is origin and the destination field, with its individual characteristics, we have to define the action to be performed, which will be defined within a  ** oper ** node within the  ** prop ** node.
\\
\\
====  OPER Node ====

Types of operations that can be performed with the fields that we want to transfer from one table to another, in the ** prop ** node.\\
\\
===  SETVAL Action ===
\\
Operation to put a given value in the destination field. That's why the  ** prop ** node, only has the type of the  ** type ** field, and the name of the field that is the destination, ** dest-name **.
\\
In the example we can see that in the IDPADRE field of the destination table, which is of numeric type, N, the value 1 will be saved.\\
\\

<code xml>
<prop dest-name="IDPADRE" type="N">
	<oper type="setval" value="1"/>
</prop>
</code>

In this other example we put the "xone" value in the NOMBRE destination field, that is text type.\\
\\

<code xml>
<prop dest-name="NOMBRE" type="T">
	<oper type="setval" value="xone"/>
</prop>
</code>

===  COPY Action ===
\\
Operation to copy the value of a source field into a destination field.\\

\\
Example where it is seen how the value of the "delegation" field will be copied to the "LABEL" field. This field is text type. We can also see how it is the primary key, so to find if there is such a record in the destination, it will made by searching for the value of this field. It is also being told to save the value of the source in the macro ** ## SOURCEKEYVALUES ## **, and to save the value of the destination in the macro ** ## DESTKEYVALUES ## **.
\\
<code xml>
<prop source-name="delegación" dest-name="ETIQUETA" key="true" type="T" saved-source="true" saved-dest="true">
		<oper type="copy"/>
</prop>
</code>


Node that transfers the value of the "PASSWORD_E" field into the PWD field. As we can see, it has type X, so it is being indicated that it is a password field, and its value keeps it encrypted. Encryption is supported by the XOne Platform, so that users can subsequently enter the application.\\
\\
<code xml>
<prop source-name="PASSWORD_E" dest-name="PWD" type="X">
           <oper type="copy"/>
</prop>	
</code>

\\	
Node that transfers the value of the "DESCPTE" field into the "INCIDENCE" field. It is  text type. We also see that it has the  "always-update" attribute, so we are forcing it into the replication queue, "master_replica_queue", to insert an update even if its value does not change.\\
\\
<code xml>
<prop source-name="DESCPTE" dest-name="INCIDENCIA" key="false" type="T" always-update="true">
	<oper type="copy"/>
</prop>	
</code>
\\

Node that transfers the value of the "FECCARGA" field into the "DATE" field. The field is  date type. You can also see a new node, ** format **, node that is used within the  ** prop ** nodes, and that is used to format the value in the destination with the characteristics that are indicated in the value attribute. In the example, when we put it, we are telling it that in the destination the date has to be inserted in day / month / year mode.\\
\\

<code xml>
<prop source-name="FECCARGA" dest-name="FECHA" type="D">				
  <oper type="copy"/>
  <format name="dest-name" value="dd/mm/yyyy"/>
</prop>	
</code>


\\
Node that transfers the data from the "CODAVISO" field into the "TIPOPARTE" field, and we see that it is  the text type. We can also see that there is the ** format ** node. Here we can see that it has a new attribute, ** trim **. This attribute does or does not eliminate the blank spaces that come from the origin in the destination. The attribute if it is not defined is "true", that is, it eliminates the blank spaces. For it to work, it is necessary to put the value "NULL" in the "value" attribute.\\
\\
<code xml>
<prop source-name="CODAVISO" dest-name="TIPOPARTE" type="T">
	<oper type="copy"/>
	<format value="NULL" trim="false"/>
</prop>	
</code>
\\

Node that transfers the data from the "PRETAR" field into the "PRICE" field. It is numeric, and  with 5 decimals specifically. In order for the copy to be done well, the ** format ** node has been set, placing exactly the number of decimals that will be put to it.\\
\\
<code xml>
<prop source-name="PRETAR" dest-name="PRECIO" type="N5">
	<oper type="copy"/>
	<format name="dest-name" value="0.00000"/>
</prop>
</code>


===  MAPVAL Action  ===  


Operation to transfer data from fields related to values ​​that are in other tables. What would be in the mappings fields of type IDEMPRESA or IDUSUARIO. For this, what is done is to take the value of the source field, and look for it in a table, when it finds the value, it puts the value of a field that we indicate it of that table in the destination field of the beginning.\\
\\
In the example that is seen, the value of the "delegation" field is taken, and compared with the "LABEL" field, which is put in the ** mapfld ** attribute, which exists in the "Gen_Business" table, defined in the ** source ** attribute. If there is a record that has that value, there only has to be one, since the field by which the search is made in the "Gen_Business" table, must be the primary key of the same, take the value of the field that is define in the attribute ** targetfld **, "ID" for this case, and put it in the field ** dest-name **, field "IDEMPRESA".
\\
<code xml>
<prop source-name="delegación" dest-name="IDEMPRESA" type=”N”>
	<oper type="mapval" source="Gen_Empresa" targetfld="ID">
		<prop mapfld="ETIQUETA" mapvalue="##SELF##"/>
	</oper>
</prop>	
</code>
\\
In this case, several props can be used within the same oper, which is for those cases in which the first key of the record we are looking for is defined by several fields, in this case "COMPANY_ID" and "CAMPO2".\\
\\
Example:

<code xml>
<oper type="mapval" source="gen_usuarios" targetfld="ID">
     <prop mapfld="COMPANY_ID" mapvalue="##SELF##"/>
     <prop mapfld="CAMPO2" mapvalue="##FLD_PROPIEDAD##"/>
</oper>  
</code>



====  AFTER-ACTION Node====

\\
Node that is executed when we finishing to perform the data transfer from one table to another.\\

\\

===  EXECUTE-QUERY Action ===
\\

It executes an SQL. This is quite useful for putting a field in the source table with a value, to indicate that this value has already been transferred to the destination table.\\

In the given example, we see that it has two nodes ** param **, in which it is told that SQL will be executed, in the attribute ** value **. Also in that database, the  ** name ** attribute, is given "dest", which is the destination database, and "source", which is the source database.\\
\\
We can also see that it uses the  ** ## SOURCEKEYVALUES ## ** and ** ## DESTKEYVALUES ## ** macros, which have been filled in while transferring the data from one database to another.\\
\\
<code xml>
<action name="execute-query">
<param name="source" value="Update Gen_DetDocumento SET ACTUALIZADO=1 WHERE ##SOURCEKEYVALUES##"/>				<param name="dest" value="UPDATE Gen_Documentos  SET ACTUALIZADO=1  WHERE ID IN (SELECT IDDOCUMENTO FROM GEN_DETDOCUMENTO WHERE ##DESTKEYVALUES##)"/>	
</action>
</code>
\\




=====  Example Code =====
\\
It is a sample code  about how it would be an interclient.xml file.

<code xml>
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- Nodo xml obligatorio, puesto que es el formato del documento -->
<xml>
	<!-- Nodo interface, dentro del cual va todo lo necesario para nuestra integración -->
	<interface>
		<!-- Aqui van los datos a nivel de aplicación -->
		<app name="WEBSERVICE" timeaccess="false" logoper="true">
			<!-- Aquí vamos a tener las distintas conexiones -->
			<dsn>
				<!-- Esta es la conexión al webservice -->
				<client type="WEB" name="webservice-demo" persistent="true" url="https://localhost/services/WebservicesInHandler" endpoint="WebservicesInHandler" wsdl="" wsdl2="" wrapper="XOneWrapper" class="WebservicesInHandlerService"/>		
				<!-- Conexión normal a nuestra BD -->
				<source type="ODBC" name="connstr1" connstring="DSN=Localhost_DES;Database=database;UID=root;PWD=password" user="root" pwd="password" />
				<!-- Conexión a nuestra BD para actualizar registros lastmodified (Se usa para marcar por donde vamos en algunas iteraciones) -->
				<lastmodified type="ODBC" name="connstr2" connstring="DSN=Localhost_DES;Database=database;UID=root;PWD=password" user="root" pwd="password" />
				<!-- Conexión a nuestra BD para operaciones opcionales (Normalmente no se usa) -->
				<optional name="NOMBRE3" type="MYSQL" connstring="......."/>
			</dsn>
			<!-- Intervalo tras el cual se vuelve a ejecutar la interface, expresado en segundos -->
			<schedule type="continue" interval="5"/>
		</app>
		<!-- Estas son las transformaciones de BAJADA, es decir del CLIENTE a NOSOTROS -->
		<transforms type="client-to-source">
			<!-- TRANSFORMACIÓN DE USUARIOS -->
			<transform name="t_usuarios">
				<!-- En el nodo coll tenemos la tabla de destino y el origen, en este caso un ##WEBMETHOD## -->
				<coll dest-table="TABLA_DESTINO" source-table="##WEBMETHOD##">
					<!--
						Aqui tenemos el nodo function, el cual indica la función a la que tenemos que llamar y su Clase
						Si tuviéramos que enviar parámetros estos irían dentro del nodo, añadiendo nuevos nodos param
					-->
					<function name="GetUsuarios" class="XOneWrapper.ObtenerDatosClient" />
					
					<!--
						A continuación vamos pasando prop a prop, de sus campos a los nuestros.
						¡IMPORTANTE! Siempre debemos tener un prop al menos con key="true"
						sino nuestros datos se van a ver duplicados y vamos a generar miles de operaciones
						en el queue totalmente innecesarias.
					-->
					<prop source-name="IDNUMPERSO" dest-name="CAMPO_A_MAPEAR" type="N" key="true">
						<oper type="copy"/>
					</prop>
					<prop source-name="APEYNOM" dest-name="CAMPO_A_MAPEAR" type="T">
						<oper type="copy"/>
					</prop>
					<prop source-name="LOGIN" dest-name="CAMPO_A_MAPEAR" type="T">
						<oper type="copy"/>
					</prop>
					<prop source-name="FECHAMODIFICACION" dest-name="CAMPO_A_MAPEAR" type="D">
						<oper type="copy"/>
						<format name="dest-name" value="dd/MM/yyyy"/>
					</prop>					
				</coll>
			</transform><!-- FIN TRANSFORMACIÓN DE USUARIOS -->
		</transforms><!-- FIN TRANSFORMACIÓN DE USUARIOS -->
		
		<!-- Estas son las transformaciones de SUBIDA, es decir de NOSOTROS al CLIENTE -->
		<transforms type="source-to-client">
			<!-- TRANSFORMACIÓN DE ASOCIAR USUARIO PARTE -->
			<transform name="t_asociar_usuario_parte">
				<!-- 
					La coll principal, aqui seleccionamos los datos que queramos pasar, con los WHERE necesarios para filtrar
					
					source-table	es el SQL del que vamos a sacar las filas que queremos pasar (Aqui no hace falta sacar datos, tan solo el ID y ROWID)
					dest-table		en este caso ##WEBMETHOD## indica que es una llamada a un webservice
					desc			es el nombre del método que vamos a llamar
					name			es el nombre del método que vamos a llamar
					
					NOTA: empty-result="true" Usamos este atributo ya que la funcion del webservice no nos devuelve nada
				-->
				<coll source-table="SELECT t.ID,t.ROWID	FROM tabla1 t WHERE CAMPO6 IS NULL" 
				dest-table="##WEBMETHOD##" desc="AsociarUsuarioParte" name="AsociarUsuarioParte" empty-result="true" >
					<!-- Nodo function indicando la función que queremos invocar -->
					<function name="AsociarUsuarioParte" />
					<prop source-name="ID" dest-name="ID" type="N" key="true" saved-source="true" />
					<!--
						En esta coll indicamos la variable a la que van a ir los datos y su tipo
						
						source-table	es el SQL del que vamos a sacar nuestros datos filtrados por el ID que cogimos antes arriba.
						dest-table		Nombre de la variable a donde van los datos
						name			Nombre de la variable a donde van los datos
						desc			Tipo de la variable
					-->
					<coll dest-table="Parte" name="Parte" desc="XOneWrapper.Datos.PARTE_USUARIOS" 
					source-table="SELECT t.ID, t.CAMPO1, t.CAMPO2 FROM tabla1 t where t.ID=##ID##">
						<prop source-name="CAMPO1" dest-name="IDNUMPERSO" type="N">
							<oper type="copy"/>
						</prop>
						<prop source-name="CAMPO2" dest-name="IDPA" type="N2">
							<oper type="copy"/>
						</prop>
					</coll>
					<!--
						Indicamos en el nodo after-action que queremos que se ejecute para cada registro
					-->
					<after-action each-record="true">
						<!-- execute-query: Lo que queremos es ejecutar una consulta a una base de datos -->
						<action name="execute-query">
							<!-- aqui el SQL que queremos ejecutar filtrado por los ID's de nuestros registros -->
							<param name="source" value="update tabla1 set CAMPO6='4432' WHERE ##SOURCEKEYVALUES##"/>
						</action>
					</after-action>
				</coll> 
			</transform><!-- FIN TRANSFORMACIÓN DE ASOCIAR USUARIO PARTE -->
		</transforms><!--FIN de las transformaciones de SUBIDA -->
	</interface><!-- FIN Nodo interface -->
</xml>
</code>