Lightstreamer 7.3.3 for IG Markets

iceman89

olevo sapere una info su Lightstreamer 7.3.3 da usare con il mio broker(IG ,che tra l'altro lo usano anche loro) per fare trading. io ho scaricato la versione che loro mi hanno detto la 7.3.3 poi l ho scompattata nella cartella principale C: ; classico , poi ho cancellato quello che c'era nella cartella WELCOME standard , perchè volevo creare il collegamento streaming con IG Markets, ho creato una Cartella (IG_Streaming_Data) e dento c'è solo il file adapters.xml ok ?
se io devo mettere i parametri che sono presenti in questo sito di IG " https://labs.ig.com/streaming-api-reference.html" se potete darci un attimo un occhiata mi farebbe piacere , io ho fatto una cosa del genere in adapters.xml :

PRICE:{XJCM1}:{CS.D.CFEGOLD.CBE.IP}
Pricing
MERGE

sempre se non ho sbagliato dove il 1° indica l'item cioè lo strumento da mettere , guisto , il 2 ° il nome del Data Adapter x IG è Pricing se vedete e il 3° il Mode : per loro di IG MERGE ; non so dove andare a mettere la lista dei " Field" dopo di che dovrebbe ripartire a livello locale il lightstreamer giusto , perchè poi io lo lancio dal windows Terminal e dopo faccio un collegamento per lo Streaming dal Windows Terminal in formato generico cioè HTTP perchè mi serve che funzioni prima il lightstreamer una volta lanciato poi posso fare il collegamento con IG Markets per fare trading ,capito non riesco a capire dov'è il problema e dove aggiungere nell adapters.xml i valori del Field di IG come presa visione dal loro sito web per le REST Api : https://labs.ig.com/streaming-api-reference.html ; mi potete gentilmente dare le indicazioni su come completare il tutto e poi poterlo rilanciare il lightstreamer a livello locale e poi con il collegamento http con cURL non un problema dopo li ce la faccio da solo, Grazie in anticipo.
Luca Pilotti.

in allegato l'adapters.xml :

<?xml version="1.0" encoding="UTF-8"?>

<!--
This is a generic template for the configuration file of an Adapter Set
pluggable into Lightstreamer Server.
It can be considered a reference example of in-process Java Adapter deploy.
Note that element and attribute names are handled in a case sensitive way.

A very simple variable-expansion feature is available; see
<enable_expansion_for_adapters_config> in the Server's main configuration file.

-->

<adapters_conf id="Pricing">

<!-- Optional. Requests the creation of a specific "SET" thread pool, devoted
     to the management of all the client requests pertaining to sessions
     based on this Adapter Set. Only requests related with the special
     Data Adapter used to supply the state of the MPN Module (if enabled)
     are not included and fall into the global SERVER pool.

     If not defined, these requests are managed by the global SERVER
     thread pool.
     If defined, the <max_size> and <max_free> elements are mandatory,
     with meaning similar to that of the global <server_pool_max_size>
     and <server_pool_max_free> settings.
     Using a specific thread pool is advisable if the implementation
     of any of the Adapter methods introduces delays and more specific
     thread pools are not being used. -->
<!--
<adapter_set_pool>
    <max_size>100</max_size>
    <max_free>10</max_free>
</adapter_set_pool>
-->

<!-- Optional. If "Y", ensures that the call of the method 'init' of the
     Metadata Adapter ends before any 'init' of the Data Adapters is called.
     Otherwise the Metadata Adapter is initialised in parallel with all the
     other Data Adapters.

     If not defined, the default value is "Y" (i.e. Metadata Adapter
     initialised first). -->
<!--
<metadata_adapter_initialised_first>Y</metadata_adapter_initialised_first>
-->

<!-- Mandatory. Define the Metadata Adapter. -->
<metadata_provider>

    <!-- Optional. Specify a directory other than "."
         for this Adapter's own class and configuration files. -->
    <!--
    <install_dir>my_metadata</install_dir>
    -->

    <!-- Mandatory. Java class name of the adapter. -->
    <adapter_class>com.lightstreamer.adapters.metadata.LiteralBasedProvider</adapter_class>

    <!-- Optional. Determines the ClassLoader to be used to load the Adapter
         related classes. Possible values are:
         - "common": The common ClassLoader assigned to the whole Adapter Set
           is used; this ClassLoader already includes all the classes found
           in the common "lib" and "classes" folders; it also inherits from
           a global ClassLoader that includes all the classes found under the
           "shared/lib" and "shared/classes" folders. If a specific <install_dir>
           is assigned to the Adapter, classes found in its "lib" and "classes"
           subfolders are added to the Adapter Set ClassLoader.
         - "dedicated": A dedicated ClassLoader, which still inherits from the
           Adapter Set ClassLoader, is used. In this case, it is mandatory
           that a specific <install_dir> is assigned to the Adapter; hence,
           classes found in its "lib" and "classes" subfolders are added to
           the dedicated ClassLoader.
         - "log-enabled": A dedicated ClassLoader which also includes the
           slf4j library used by the Server is used; hence the Adapter shares
           the log configuration with the Server. However, in this case, the
           Adapter ClassLoader does not inherit from the Adapter Set
           ClassLoader, hence no sharing of classes with other Adapters is
           possible. If no specific <install_dir> is assigned to the Adapter,
           then the dedicated ClassLoader will be added all classes found in
           the common "lib" and "classes" folders.

         The determined ClassLoader is also set as the "context ClassLoader"
         in all Adapter method invocations.
         If not defined, the default value is "common" (i.e. the common
         Adapter Set ClassLoader is used). -->
    
    <classloader>common</classloader>
    

    <!-- Optional. Requests the creation of a specific "AUTHENTICATION"
         thread pool, expressly devoted to the calls of "notifyUser" against
         this Metadata Adapter.

         If not defined, these calls are managed by the thread pool related
         with the Adapter Set, if, in turn, defined.
         If defined, the <max_size> and <max_free> elements are mandatory,
         with meaning similar to that of the global <server_pool_max_size>
         and <server_pool_max_free> settings.
         Using a specific thread pool is advisable if the "notifyUser"
         implementation may introduce delays. -->
    <!--
    <authentication_pool>
        <max_size>100</max_size>
        <max_free>10</max_free>
    </authentication_pool>
    -->

    <!-- Optional. Requests the creation of a specific "MSG" thread pool,
         expressly devoted to the calls of "notifyUserMessage", which
         handle messages sent by the client, against this Metadata Adapter.

         If not defined, these calls are managed by the thread pool related
         with the Adapter Set, if, in turn, defined.
         If defined, the <max_size> and <max_free> elements are mandatory,
         with meaning similar to that of the global <server_pool_max_size>
         and <server_pool_max_free> settings.
         Using a specific thread pool is advisable if the
         "notifyUserMessage" implementation may introduce delays. -->
    <!--
    <messages_pool>
        <max_size>100</max_size>
        <max_free>10</max_free>
    </messages_pool>
    -->

    <!-- Optional. Requests the creation of a specific "MPN REQUESTS" thread
         pool, devoted to the management of all the mobile push notification
         requests pertaining to sessions based on this Adapter Set.

         If not defined, these calls are managed by the thread pool related
         with the Adapter Set, if, in turn, defined.
         If defined, the <max_size> and <max_free> elements are mandatory,
         with meaning similar to that of the global <server_pool_max_size>
         and <server_pool_max_free> settings.
         Using a specific thread pool is advisable if implementation
         of MPN operations (like "notifyMpnSubscriptionActivation" etc.)
         may introduce delays. -->
    <!--
    <mpn_pool>
        <max_size>100</max_size>
        <max_free>10</max_free>
    </mpn_pool>
    -->

    <!-- Optional. If "Y", ensures that all Table (i.e. Subscription)
         notifications (that is, all the invocations to "notifyNewTables" and
         "notifyTablesClose") pertaining to the same session will be sequential,
         with no overlapping; if "N", then concurrent invocations will be
         possible.
         Note that the final invocation to "notifySessionClose" is always
         guaranteed to occur after all the above notifications have terminated.

         If not defined, the default value is "N" (i.e. do not sequentialize). -->
    <!--
    <sequentialize_table_notifications>Y</sequentialize_table_notifications>
    -->

    <!-- Optional. List of initialization parameters specific to the adapter.
         The various <param> elements are not interpreted by Lightstreamer,
         but they are forwarded to the specific adapter configured.
         The following are sample parameters, some of which are the ones
         handled by the sample Metadata Adapters provided. -->

    <!-- Optional. Sample log configuration; the path is relative to <install_dir>. -->
    <!--
    <param name="log_config">../adapters_log_conf.xml</param>
    -->

    <!-- Optional (specific for adapters that inherit from
         com.lightstreamer.adapters.metadata.LiteralBasedProvider).

         Define values to be returned in getAllowedMaxBandwidth(),
         getAllowedMaxItemFrequency(), getAllowedBufferSize(),
         getDistinctSnapshotLength() and getMinSourceFrequency()
         methods, for any User and Item supplied
         and optional comma-separated list of User names to be
         allowed by the notifyUser() method.
         See LiteralBasedProvider javadoc. -->
    
    <param name="max_bandwidth">50</param>
    
    
    <param name="max_frequency">2</param>
    
    
    <param name="buffer_size">30</param>ost

    
    
    <param name="prefilter_frequency">5</param>
    
    
    <param name="allowed_users">Iceman89</param>
    
    
    <param name="distinct_snapshot_length">300</param>
    
    <!-- Optional (specific for adapters that inherit from
         com.lightstreamer.adapters.metadata.LiteralBasedProvider).

         Define how the modeMayBeAllowed method should behave, by
         associating to each item the modes in which it can be managed
         by the Server.
         Each triple of parameters of the form "item_family_<n>",
         "data_adapter_for_item_family_<n> (optional), and
         "modes_for_item_family_<n>" define respectively the item name
         pattern (in java.util.regex.Pattern format),
         the related Data Adapter, and the allowed
         modes (in comma separated format) for a family of items.
         Each item is assigned to the first family that matches its name
         and (if supplied) the related Data Adapter.
         If no families are specified at all, then modeMayBeAllowed
         always returns true, though this is not recommended, because
         the Server does not support more than one mode out of MERGE,
         DISTINCT, and COMMAND for the same item. In such a case, the
         Server would just manage each item in the mode specified by the
         first Client request it receives for the item and would be up to
         the Clients to ensure that the same item cannot be requested in
         two conflicting Modes.
         See LiteralBasedProvider javadoc. -->

    <!-- items supplied by the Server-supplied Monitoring Data Adapter -->
    <!-- DEMO Streaming Item for DEMO REST Api-->
    <!-- Spot Gold (E1 Contract) -->
    <param name="item_family_1">PRICE:{XJCM1}:{CS.D.CFEGOLD.CBE.IP}</param>
    <param name="data_adapter_for_item_family_1">Pricing</param>
    <param name="modes_for_item_family_1">MERGE</param>
    
    <!-- Spot Gold ($1) -->
    <param name="item_family_2">PRICE:{XJCM1}:{CS.D.CFEGOLD.CEB.IP}</param>
    <param name="data_adapter_for_item_family_2">Pricing</param>
    <param name="modes_for_item_family_2">MERGE</param>

    <!-- Gold (33.20$) -->
    <param name="item_family_3">PRICE:{XJCM1}:{MT.D.GC.FWM2.IP}</param>
    <param name="data_adapter_for_item_family_3">Pricing</param>
    <param name="modes_for_item_family_3">MERGE</param>

    <!-- EUR/USD Mini -->
    <param name="item_family_4">PRICE:{XJCM1}:{CS.D.EURUSD.CEBM.IP}</param>
    <param name="data_adapter_for_item_family_4">Pricing</param>
    <param name="modes_for_item_family_4">MERGE</param>

    <!-- GBP/USD Mini -->
    <param name="item_family_5">PRICE:{XJCM1}:{CS.D.GBPUSD.MINI.IP}</param>
    <param name="data_adapter_for_item_family_5">Pricing</param>
    <param name="modes_for_item_family_5">MERGE</param>

    <!-- USD/JPY Mini -->
    <param name="item_family_6">PRICE:{XJCM1}:{CS.D.USDJPY.MINI.IP}</param>
    <param name="data_adapter_for_item_family_6">Pricing</param>
    <param name="modes_for_item_family_6">MERGE</param>

    <!-- GBP/USD Mini -->
    <param name="item_family_7">PRICE:{XJCM1}:{CS.D.GBPUSD.MINI.IP}</param>
    <param name="data_adapter_for_item_family_7">Pricing</param>
    <param name="modes_for_item_family_7">MERGE</param>

    <!-- Germany Tech 30 Cash (EUR2 Mini Contract) -->
    <param name="item_family_8">PRICE:{XJCM1}:{TM.D.TECDAX.IFM.IP}</param>
    <param name="data_adapter_for_item_family_8">Pricing</param>
    <param name="modes_for_item_family_8">MERGE</param>

    <!-- Germany 40 Cash (5€)  -->
    <param name="item_family_9">PRICE:{XJCM1}:{IX.D.DAX.IFM1.IP}</param>
    <param name="data_adapter_for_item_family_9">Pricing</param>
    <param name="modes_for_item_family_9">MERGE</param>

    <!-- Germany 40 Cash (1€)  -->
    <param name="item_family_10">PRICE:{XJCM1}:{IX.D.DAX.IFMM.IP}</param>
    <param name="data_adapter_for_item_family_10">Pricing</param>
    <param name="modes_for_item_family_10">MERGE</param>

    <!-- Germany 40 Cash (1€)  -->
    <param name="item_family_11">PRICE:{XJCM1}:{IX.D.DAX.IBE.IP}</param>
    <param name="data_adapter_for_item_family_11">Pricing</param>
    <param name="modes_for_item_family_11">MERGE</param>

    <!-- Germany 40 Cash (5€)  -->
    <param name="item_family_12">PRICE:{XJCM1}:{IX.D.DAX.FWM1.IP}</param>
    <param name="data_adapter_for_item_family_12">Pricing</param>
    <param name="modes_for_item_family_12">MERGE</param>

    <!-- US Russell 2000 ($10)  -->
    <param name="item_family_13">PRICE:{XJCM1}:{IX.D.RUSSELL.FWM2.IP}</param>
    <param name="data_adapter_for_item_family_13">Pricing</param>
    <param name="modes_for_item_family_13">MERGE</param>

    <!-- US Russell 2000 ($10)  -->
    <param name="item_family_14">PRICE:{XJCM1}:{IX.D.RUSSELL.IFM.IP}</param>
    <param name="data_adapter_for_item_family_14">Pricing</param>
    <param name="modes_for_item_family_14">MERGE</param>

    <!-- US Russell 2000 Cash (E1)  -->
    <param name="item_family_15">PRICE:{XJCM1}:{IX.D.RUSSELL.IBE.IP}</param>
    <param name="data_adapter_for_item_family_15">Pricing</param>
    <param name="modes_for_item_family_15">MERGE</param>

    <!-- US Tech 100 (20$)  -->
    <param name="item_family_16">PRICE:{XJCM1}:{IX.D.NASDAQ.FWM1.IP}</param>
    <param name="data_adapter_for_item_family_16">Pricing</param>
    <param name="modes_for_item_family_16">MERGE</param>

    <!-- US Tech 100 Cash (1€)  -->
    <param name="item_family_17">PRICE:{XJCM1}:{IX.D.NASDAQ.IBE.IP}</param>
    <param name="data_adapter_for_item_family_17">Pricing</param>
    <param name="modes_for_item_family_17">MERGE</param>

    <!-- US Tech 100 Cash (20$)  -->
    <param name="item_family_18">PRICE:{XJCM1}:{IX.D.NASDAQ.IFM.IP}</param>
    <param name="data_adapter_for_item_family_18">Pricing</param>
    <param name="modes_for_item_family_18">MERGE</param>

    <!-- Wall Street Cash (1$)  -->
    <param name="item_family_19">PRICE:{XJCM1}:{IX.D.DOW.IEB.IP}</param>
    <param name="data_adapter_for_item_family_19">Pricing</param>
    <param name="modes_for_item_family_19">MERGE</param>

    <!-- Wall Street Cash (1€)  -->
    <param name="item_family_20">PRICE:{XJCM1}:{IX.D.DOW.IBE.IP}</param>
    <param name="data_adapter_for_item_family_20">Pricing</param>
    <param name="modes_for_item_family_20">MERGE</param>

    <!-- Wall Street Cash (2$)  -->
    <param name="item_family_21">PRICE:{XJCM1}:{IX.D.DOW.IFM.IP}</param>
    <param name="data_adapter_for_item_family_21">Pricing</param>
    <param name="modes_for_item_family_21">MERGE</param>

    <!-- Oil - US Crude (1€)  -->
    <param name="item_family_22">PRICE:{XJCM1}:{CC.D.CL.UBE.IP}</param>
    <param name="data_adapter_for_item_family_22">Pricing</param>
    <param name="modes_for_item_family_22">MERGE</param>

    


    <!-- REALE Streaming Item for REALE REST Api-->
    <!-- Spot Gold (E1 Contract) -->
    <param name="item_family_23">PRICE:{PZN71}:{CS.D.CFEGOLD.CBE.IP}</param>
    <param name="data_adapter_for_item_family_23">Pricing</param>
    <param name="modes_for_item_family_23">MERGE</param>
    
    <!-- Spot Gold ($1) -->
    <param name="item_family_24">PRICE:{PZN71}:{CS.D.CFEGOLD.CEB.IP}</param>
    <param name="data_adapter_for_item_family_24">Pricing</param>
    <param name="modes_for_item_family_24">MERGE</param>

    <!-- Gold (33.20$) -->
    <param name="item_family_25">PRICE:{PZN71}:{MT.D.GC.FWM2.IP}</param>
    <param name="data_adapter_for_item_family_25">Pricing</param>
    <param name="modes_for_item_family_25">MERGE</param>

    <!-- EUR/USD Mini -->
    <param name="item_family_26">PRICE:{PZN71}:{CS.D.EURUSD.CEBM.IP}</param>
    <param name="data_adapter_for_item_family_26">Pricing</param>
    <param name="modes_for_item_family_26">MERGE</param>

    <!-- GBP/USD Mini -->
    <param name="item_family_27">PRICE:{PZN71}:{CS.D.GBPUSD.MINI.IP}</param>
    <param name="data_adapter_for_item_family_27">Pricing</param>
    <param name="modes_for_item_family_27">MERGE</param>

    <!-- USD/JPY Mini -->
    <param name="item_family_28">PRICE:{PZN71}:{CS.D.USDJPY.MINI.IP}</param>
    <param name="data_adapter_for_item_family_28">Pricing</param>
    <param name="modes_for_item_family_28">MERGE</param>

    <!-- GBP/USD Mini -->
    <param name="item_family_29">PRICE:{PZN71}:{CS.D.GBPUSD.MINI.IP}</param>
    <param name="data_adapter_for_item_family_29">Pricing</param>
    <param name="modes_for_item_family_29">MERGE</param>

    <!-- Germany Tech 30 Cash (EUR2 Mini Contract) -->
    <param name="item_family_30">PRICE:{PZN71}:{TM.D.TECDAX.IFM.IP}</param>
    <param name="data_adapter_for_item_family_30">Pricing</param>
    <param name="modes_for_item_family_30">MERGE</param>

    <!-- Germany 40 Cash (5€)  -->
    <param name="item_family_31">PRICE:{PZN71}:{IX.D.DAX.IFM1.IP}</param>
    <param name="data_adapter_for_item_family_31">Pricing</param>
    <param name="modes_for_item_family_31">MERGE</param>

    <!-- Germany 40 Cash (1€)  -->
    <param name="item_family_32">PRICE:{PZN71}:{IX.D.DAX.IFMM.IP}</param>
    <param name="data_adapter_for_item_family_32">Pricing</param>
    <param name="modes_for_item_family_32">MERGE</param>

    <!-- Germany 40 Cash (1€)  -->
    <param name="item_family_33">PRICE:{PZN71}:{IX.D.DAX.IBE.IP}</param>
    <param name="data_adapter_for_item_family_33">Pricing</param>
    <param name="modes_for_item_family_33">MERGE</param>

    <!-- Germany 40 Cash (5€)  -->
    <param name="item_family_34">PRICE:{PZN71}:{IX.D.DAX.FWM1.IP}</param>
    <param name="data_adapter_for_item_family_34">Pricing</param>
    <param name="modes_for_item_family_34">MERGE</param>

    <!-- US Russell 2000 ($10)  -->
    <param name="item_family_35">PRICE:{PZN71}:{IX.D.RUSSELL.FWM2.IP}</param>
    <param name="data_adapter_for_item_family_35">Pricing</param>
    <param name="modes_for_item_family_35">MERGE</param>

    <!-- US Russell 2000 ($10)  -->
    <param name="item_family_36">PRICE:{PZN71}:{IX.D.RUSSELL.IFM.IP}</param>
    <param name="data_adapter_for_item_family_36">Pricing</param>
    <param name="modes_for_item_family_36">MERGE</param>

    <!-- US Russell 2000 Cash (E1)  -->
    <param name="item_family_37">PRICE:{PZN71}:{IX.D.RUSSELL.IBE.IP}</param>
    <param name="data_adapter_for_item_family_37">Pricing</param>
    <param name="modes_for_item_family_37">MERGE</param>

    <!-- US Tech 100 (20$)  -->
    <param name="item_family_38">PRICE:{PZN71}:{IX.D.NASDAQ.FWM1.IP}</param>
    <param name="data_adapter_for_item_family_38">Pricing</param>
    <param name="modes_for_item_family_38">MERGE</param>

    <!-- US Tech 100 Cash (1€)  -->
    <param name="item_family_39">PRICE:{PZN71}:{IX.D.NASDAQ.IBE.IP}</param>
    <param name="data_adapter_for_item_family_39">Pricing</param>
    <param name="modes_for_item_family_39">MERGE</param>

    <!-- US Tech 100 Cash (20$)  -->
    <param name="item_family_40">PRICE:{PZN71}:{IX.D.NASDAQ.IFM.IP}</param>
    <param name="data_adapter_for_item_family_40">Pricing</param>
    <param name="modes_for_item_family_40">MERGE</param>

    <!-- Wall Street Cash (1$)  -->
    <param name="item_family_41">PRICE:{PZN71}:{IX.D.DOW.IEB.IP}</param>
    <param name="data_adapter_for_item_family_41">Pricing</param>
    <param name="modes_for_item_family_41">MERGE</param>

    <!-- Wall Street Cash (1€)  -->
    <param name="item_family_42">PRICE:{PZN71}:{IX.D.DOW.IBE.IP}</param>
    <param name="data_adapter_for_item_family_42">Pricing</param>
    <param name="modes_for_item_family_42">MERGE</param>

    <!-- Wall Street Cash (2$)  -->
    <param name="item_family_43">PRICE:{PZN71}:{IX.D.DOW.IFM.IP}</param>
    <param name="data_adapter_for_item_family_43">Pricing</param>
    <param name="modes_for_item_family_43">MERGE</param>

    <!-- Oil - US Crude (1€)  -->
    <param name="item_family_44">PRICE:{PZN71}:{CC.D.CL.UBE.IP}</param>
    <param name="data_adapter_for_item_family_44">Pricing</param>
    <param name="modes_for_item_family_44">MERGE</param>

</metadata_provider>


<!-- Mandatory and cumulative. Define a Data Adapter.
     The "name" attribute is optional and the default name is "DEFAULT";
     if multiple Data Adapters are defined in the same Adapter Set,
     then using the "name" attribute is needed to distinguish them. -->
<data_provider name="MY_DATA_ADAPTER_ONE">

    <!-- Optional. Specify a directory other than "."
         for this Adapter's own class and configuration files. -->
    <!-- 
    <install_dir>myadapter_one</install_dir>
    -->

    <!-- Mandatory. Java class name of the adapter. -->
    <adapter_class>com.lightstreamer.adapters.metadata.LiteralBasedProvider</adapter_class>

    <!-- Optional. The same as for the Metadata Adapter; see above. -->
    
    <classloader>common</classloader>
    

    <!-- Optional. Requests the creation of a specific "DATA" thread pool,
         expressly devoted to the management of table subscription and
         unsubscription requests for all the tables based on this Data
         Adapter. This involves the various calls to the Data Adapter
         and some calls to the Metadata Adapter. Among the latter, the most
         critical are "getItems", "getSchema", and "notifyNewTables";
         the pool associated to each Metadata Adapter call can be found
         in the related API documentation.

         If not defined, these requests are managed by the thread pool
         related with the Adapter Set, if, in turn, defined.
         If defined, the <max_size> and <max_free> elements are mandatory,
         with meaning similar to that of the global <server_pool_max_size>
         and <server_pool_max_free> settings.
         Using a specific thread pool is advisable if the implementation
         of any of the involved Adapter methods introduces delays. -->
    <!--
    <data_adapter_pool>
        <max_size>100</max_size>
        <max_free>10</max_free>
    </data_adapter_pool>
    -->

    <!-- Optional. List of initialization parameters specific to the adapter.
         The various <param> elements are not interpreted by Lightstreamer,
         but they are forwarded to the specific adapter configured. -->

    <!-- Optional. Sample log configuration; the path is relative to <install_dir>. -->
    <!--
    <param name="log_config">../adapters_log_conf.xml</param>
    -->

</data_provider>


<!-- Mandatory. Define a Data Adapter. -->
<data_provider name="MONITOR">

    <!-- Mandatory. Java class name of the adapter.
         In this case, "MONITOR" is a special keyword that identifies the
         Monitoring Data Adapter, which is embedded in Lightstreamer Server
         and available out of the box. -->
    <adapter_class>MONITOR</adapter_class>

    <!-- Optional. See above.
         But ignored for the special "MONITOR" adapter. -->
    
    <classloader>common</classloader>
    

    <!-- Optional. See above. -->
    <!--
    <data_adapter_pool>
        <max_size>100</max_size>
        <max_free>10</max_free>
    </data_adapter_pool>
    -->

</data_provider>


<!-- Mandatory. Define a Data Adapter. -->
<data_provider name="MY_DATA_ADAPTER_TWO">

    <!-- Optional. Specify a directory other than "."
         for this Adapter's own class and configuration files. -->
    <!--
    <install_dir>myadapter_two</install_dir>
    -->

    <!-- Mandatory. Java class name of the adapter. -->
    <adapter_class>com.lightstreamer.adapters.metadata.LiteralBasedProvider</adapter_class>

    <!-- Optional. See above. -->
    
    <classloader>common</classloader>
    

    <!-- Optional. See above. -->
    <!--
    <data_adapter_pool>
        <max_size>100</max_size>
        <max_free>10</max_free>
    </data_adapter_pool>
    -->

    <!-- Optional. List of initialization parameters specific to the adapter.
         See above. -->

    <!-- Optional. Sample log configuration; the path is relative to <install_dir>. -->
    <!--
    <param name="log_config">../adapters_log_conf.xml</param>
    -->

</data_provider>

</adapters_conf>

Tenendo in considerazione che io il Lightstraemer v7.3.3 lo devo usare con il Generic Platform (client protocol specification) come lo devo impostare a livello locale sul mio Notebook?

Giuseppe Corti

iceman89 Temo ci sia stato un malinteso fondamentale riguardo al ruolo del Lightstreamer Server in questo scenario.
Per consumare i dati di streaming pubblici di IG Markets, non è necessario scaricare, installare o configurare il Lightstreamer Server (versione 7.3.3 o qualsiasi altra).
IG Markets ti espone un servizio di streaming che è già un Lightstreamer Server, pronto per essere interrogato. Usare il tuo Server locale nel mezzo è un passaggio superfluo e introduce la complicazione di cui stai discutendo (la necessità di un Data Adapter).

Cosa devi fare:

Ignora il tuo Lightstreamer Server locale.
Scegli una delle Librerie Client Lightstreamer supportate da IG (trovi l'elenco qui).
Crea direttamente la tua applicazione client (in Java, JavaScript, Python, ecc.) che:
Apre una connessione verso i server di IG Markets.
Sottoscrive gli Item desiderati (es. PRICE:{XJCM1}:...).
Inizia a ricevere i dati.

Il processo è interamente lato client e non richiede la modifica di nessun file adapters.xml sul tuo PC.

Se il tuo unico obiettivo è ricevere i dati di IG, ti suggerisco di seguire la Guida all'API di Streaming di IG per implementare l'applicazione client, in quanto è la strada più diretta.
Spero che questo ti aiuti a sbloccare la situazione semplificandola!

iceman89

se io voglio usare solo il Generic Platform TLCP (client protocol specification) insieme alal funzionalità cURL + ./jq + le REST api di IG come devo fare ?

perchè ho necessità di usare il lightstreamer v 7.3.3 in questà modalità più semplice con IG Markets : https://github.com/Lightstreamer/Lightstreamer-example-Quickstart-client-socket : Lightstreamer - Quickstart Example - HTTP clients come dovrei fare ? e poi il collegamento lo faccio io come ho detto nella maniera più nuda e cruda con cURL ./jq + REST Api e via andando con i limiti che loro mi danno

Giuseppe Corti

iceman89 Si esatto puoi prendere come riferimento gli esempi di quel tutorial, adattando i vari parametri (url, adapters set name, data adapter name, item list, field list ...) che in quel caso fanno riferimeno alla nostra demo con quelli per la connessione a IG.

iceman89

qundi potrei fare che installo nella cartella C. generale lightstreamer v7.3.3 modifico solo nella configurazione alcuni parametri e le porte in entrata per non creare conflitto in altre applicazioni poi senza cancellare la parte WELCOME che la Vostra demo giusto? lancio il lightsteramer dal windows terminal per farlo andare e poi con la funzionalità cURL + ./jq o jo + REST Api faccio funzionare il mio codice dici che può funzionare così dato che la licenza enterprice sostiene fino a 20 user poi sono solo io .

Giuseppe Corti

iceman89 No, come dicevo in un post precedente non devi installare nessun Lightstreamer server. La tua applicazione client si deve connettere direttamente agli endpoint di IG.

iceman89

volevo sapere questo parametro nell adapter.xml a cosa si riferisce : <param name="data_adapter_for_item_family_1">MyDataAdapter</param> è qui che bosognerebbe mettere i Field?

Dario Crivelli

Questo non è un parametro di Lightstreamer Server, ma un parametro esemplificativo riconosciuto solo da un Metadata Adapter esemplificativo (LiteralBasedProvider) messo a disposizione a fini di demo.
Il parametro consente a questo Metadata Adapter di implementare il metodo di interfaccia modeMayBeAllowed.
La documentazione rilevante è qui.

Ma per tornare al tema principale del thread, tutto ciò che riguarda adapters.xml è irrilevante e solo le risposte precedenti sono significative.

iceman89

Dario Crivelli quindi se io volessi usare solo il Generic Platform (client protocol specification) TLCP 2.4.0 per lightstreamer 7.3.3 sdk devo perfoza lanciare il Lightstreamer no?, e poi in windows Terminal uso la funzione cURL + .jq o jo + la REST Api che è attiva con il mio broker IG Markets ,giusto?

Giuseppe Corti

iceman89 No, non devi lanciare nessun Lightstreamer, devi connetterti direttamente a Lightstreamer di IG.
In pratica seguendo l'esmpio del tutorial devi sostituire il parametro LS_adapter_set e l'host and path' con quelle forniti dal tuo broker.

iceman89

ok ora provo e cosi solo a sostituire questo e poi ci collego anche le REST Api sempre con cURL + ./jq + jo + REST Api etc...