1 Reply Latest reply on Sep 17, 2014 12:01 PM by stevepiette

    Question about UME Store source transport

    New Member

      Hi there,


      There are some UME store and client config that we have been using for a long time. We are currently reviewing our UM config and found some discrepency between the sender / receiver & UME stores.


      From what we found from our config, UME store is now using the source transport LBT-RM while all the clients are using source transport TCP in their config.


      For the above case, would all the connection be established and data are sent through TCP ?  Is there any way we could tell which kind of transport the client app / UME store is currently using ?


      It looks to me that the transport we are using is TCP as there is no multicast address configured in the UME.cfg & UME.xml. We would also like to know if a variable is configured in UME.cfg & UME.xml, which value will be used ?


      Please find attached the UME.cfg & UME.xml.


      Thanks and Regards ,


        • 1. Re: Question about UME Store source transport
          New Member



          In your store XML config you source /appvol/29west/hsbc/config/efx-prd-ln-ume-8cs-twf_tcp-3.cfg in the <daemon> section. It sets "source transport LBT-RM on its first line, making RM the default transport overriding TCP.


          You don't specify a different transport option as an <ume-attributes> for any store so the transport remains set to RM.

          Since you also don't specify any additional multicast addresses or port ranges the LBM defaults remain in effect.


          Precedence ordering is LBM defaults, config file, UME XML.

          see https://mysupport.informatica.com/infakb/faq/7/Pages/1/148360.aspx


          The transport in question here is only used if Proxy Sources are enabled, which I didn't notice in either file. The proxy source would create a RM transport but never send any messages (since proxys don't send messages, just late join old messages)


          The various connections used by UMP is described in the UM Guide for Persistence, it discusses the registration, data transport, acknowledgement, and recovery channels. Only the source data transport is configurable, the rest are TCP.