Topic
  • 8 replies
  • Latest Post - ‏2013-09-03T10:37:15Z by nukite8d
thomas.quadflieg
thomas.quadflieg
27 Posts

Pinned topic 2 ServerLocations in TECPublisher.conf?

‏2012-11-23T07:31:38Z |
Hello,

we use TEC Publisher to send events to our event console. Our event console admin asked:
Is it possible to define 2 ServerLocations? 1 Active, one as Backup which is used if the active one fails.

Is this supported? If yes, what is the correct syntax?

Thanks,
Thomas
Updated on 2012-11-26T15:50:48Z at 2012-11-26T15:50:48Z by thomas.quadflieg
  • xf00657
    xf00657
    113 Posts

    Re: 2 ServerLocations in TECPublisher.conf?

    ‏2012-11-23T07:57:47Z  
    Hi Thomas,

    nice question. This is the desription in the IHSAMTEC-File from the EAS feature in zOS (the TECPublisher.conf from zOS):

    1. The ServerLocation is required. It specifies the hostname
    2. or IP address of the IP host on which the event server is
    3. installed. The ServerLocation keyword may contain up to
    4. 16 values, separated by commas. If more than one value is
    # specified, the first location for which a connection can be
    # established will be the location used. There is no default.

    Here the first value that can be reached will be used. Perhaps the same behavior in TECPublisher-conf?

    Regards
    Rüdiger
  • SystemAdmin
    SystemAdmin
    120 Posts

    Re: 2 ServerLocations in TECPublisher.conf?

    ‏2012-11-23T08:16:12Z  
    Hi,

    the TECPublisher.conf configuration file ServerLocation keyword can contain up to eight values, separated by commas. The first location is the primary event server, while others are secondary servers to be used in the order specified when the primary server is down.

    Best Regards
    Andreas Schauberer
  • thomas.quadflieg
    thomas.quadflieg
    27 Posts

    Re: 2 ServerLocations in TECPublisher.conf?

    ‏2012-11-23T08:24:19Z  
    Hi,

    the TECPublisher.conf configuration file ServerLocation keyword can contain up to eight values, separated by commas. The first location is the primary event server, while others are secondary servers to be used in the order specified when the primary server is down.

    Best Regards
    Andreas Schauberer
    Thank you! That sounds good!
  • thomas.quadflieg
    thomas.quadflieg
    27 Posts

    Re: 2 ServerLocations in TECPublisher.conf?

    ‏2012-11-23T09:35:32Z  
    Thank you! That sounds good!
    Hello,

    I test it with the following entries:

    ServerLocation=de000011sae62.de.top.com,de000011sae64.de.top.com
    ServerPort=1811
    ConnectionMode=connection_less
    BufferEvents=YES
    BufEvtPath=/etc/Tivoli/tec/TECPublisher.cache
    NO_UTF8_CONVERSION=YES
    The connection to the primary server (de000011sae62.de.top.com) works.
    Then, we tested stopped the reciever task on the primary, so the backup system (de000011sae64.de.top.com) became primary. Now, we can see, that the events aren't sent, but cached:

    -rw------- 1 root root 1285 Nov 23 10:37 TECPublisher.cache

    Is the failover not done automatically? Where can I find troubleshooting docs for this topic?

    Thanks,
    Thomas
  • SystemAdmin
    SystemAdmin
    120 Posts

    Re: 2 ServerLocations in TECPublisher.conf?

    ‏2012-11-23T13:20:53Z  
    Hello,

    I test it with the following entries:

    ServerLocation=de000011sae62.de.top.com,de000011sae64.de.top.com
    ServerPort=1811
    ConnectionMode=connection_less
    BufferEvents=YES
    BufEvtPath=/etc/Tivoli/tec/TECPublisher.cache
    NO_UTF8_CONVERSION=YES
    The connection to the primary server (de000011sae62.de.top.com) works.
    Then, we tested stopped the reciever task on the primary, so the backup system (de000011sae64.de.top.com) became primary. Now, we can see, that the events aren't sent, but cached:

    -rw------- 1 root root 1285 Nov 23 10:37 TECPublisher.cache

    Is the failover not done automatically? Where can I find troubleshooting docs for this topic?

    Thanks,
    Thomas
    Hi,

    sorry, for what ever reason, the documented syntax with ServerLocation does not work.
    But I found and tested the following alternate syntax:

    ServerLocation=127.0.0.1
    TransportList=t1
    t1Type=SOCKET
    t1Channels=c1,c2
    c1ServerLocation=<hostname1>
    c1Port=5529
    c2ServerLocation=<hostname2>
    c2Port=5529

    Best Regards
    Andreas Schauberer
  • SystemAdmin
    SystemAdmin
    120 Posts

    Re: 2 ServerLocations in TECPublisher.conf?

    ‏2012-11-23T13:32:10Z  
    Hi,

    sorry, for what ever reason, the documented syntax with ServerLocation does not work.
    But I found and tested the following alternate syntax:

    ServerLocation=127.0.0.1
    TransportList=t1
    t1Type=SOCKET
    t1Channels=c1,c2
    c1ServerLocation=<hostname1>
    c1Port=5529
    c2ServerLocation=<hostname2>
    c2Port=5529

    Best Regards
    Andreas Schauberer
    Hi,

    and here the TEC documentation link:

    Configuring backup servers to deliver events
    http://publib.boulder.ibm.com/tividd/td/tec/SC32-1241-00/en_US/HTML/ecoemst42.htm

    Best Regards
    Andreas Schauberer
  • thomas.quadflieg
    thomas.quadflieg
    27 Posts

    Re: 2 ServerLocations in TECPublisher.conf?

    ‏2012-11-26T15:50:48Z  
    Hi,

    and here the TEC documentation link:

    Configuring backup servers to deliver events
    http://publib.boulder.ibm.com/tividd/td/tec/SC32-1241-00/en_US/HTML/ecoemst42.htm

    Best Regards
    Andreas Schauberer
    Thank you!
    We tested it today an it works. After a fail over of our Event Console all TSA events were routed to the backup system.
  • nukite8d
    nukite8d
    98 Posts

    Re: 2 ServerLocations in TECPublisher.conf?

    ‏2013-09-03T10:37:15Z  

    BTW:
    It is possible to send EIF events to two or more TEC servers in parallel.

    To do this you have to define one publisher per server in /etc/Tivoli/tec/samPublisher.conf
    with a different name and a different ConfigPath (eg TEC, TEC2)
    (Here I noticed the EEZ Publisher is also a TEC publisher. ^-^)

    Then copy the TECPublisher.conf for each additional TEC publisher (e.g TEC2Publisher.conf)
    and change ServerLocation and BufEvtPath

    After a (re-)start of the publishers (samctrl -d P ; samctrl -e P) all events are now sent to all defined receivers.