EMS server Heartbeat failure when Authorization is enabled .

EMS server Heartbeat failure when Authorization is enabled .

book

Article ID: KB0088370

calendar_today

Updated On:

Products Versions
TIBCO Enterprise Message Service -
Not Applicable -

Description

Resolution:

Description:
= = = = = = =
EMS server heartbeat failure when Authorization is enabled, “Missing heartbeats from primary server” message is displayed.

Environment:
= = = = = = =
ALL

Resolution:
= = = = = =
This could be due to the EMS Servers being configured incorrectly, resulting in the Fault Tolerant (FT) servers not connecting to each other.

When authorization is enabled and the EMS Servers are configured in FT mode, both EMS Servers must have the same server name and password.  Additionally, there must also be a user (in users.conf) with the same name as the EMS Server name ("server" parameter in the tibemsd.conf file).  The user's password should be the same as the
server's password.

If these EMS Servers are not sharing the users.conf file, make sure that you create a user with the same name as the EMS Server and set the user's password with the value of the "server" password.

Assume there are two EMS FT Servers (Server 1 and Server 2), the server name is "EMS-SERVER", here are the steps:

(a). from the active (Server 1), use the tibemsadmin tool to enter the following:

set server password=&ltserver_password>
create user EMS-SERVER password=&ltserver_password> (if the user "EMS-SERVER" is not already created)

(b). for the backup EMS Server (Server 2), use the tibemsadmin tool to enter the following::

set server password=&ltserver_password>
create user EMS-SERVER password=&ltserver_password> (if the user "EMS-SERVER" is not already created)

(c). from the active EMS server (Server 1):

set server authorization=enabled

(d). from the backup EMS Server (Server 2):

set server authorization=enabled

Reference:
= = = = = =
EMS user manual.

Issue/Introduction

EMS server Heartbeat failure when Authorization is enabled .