Resolution:
Description:
============

Domain Utility fails to add secondary server or machine to an Administrator domain using EMS transport.

Environment:
===========
TIBCO Runtime Agent (TRA) 5.x.x
TIBCO Administrator 5.x.x
Domain using EMS transport

Symptoms:
========

1). In Domain Utility the "discover" button doesn't return the required domain.

2). Domain Utility fails to add secondary server or machine  to a Administrator domain using EMS transport.

3). The domainutility.log has the following error:

Validation Failed: Failed to connect to TIBCO Administration Domain (DomainName). Please make sure the domain is up and running.

4). The Administrator.log contains the following error:

2012 Jun 26 18:14:11:272 GMT +2 Error [JMSRepoProcess] AESDKJ-0000 [Thread-1]  javax.jms.InvalidDestinationException: Not allowed to create destination
    at com.tibco.tibjms.Tibjmsx.buildException(Tibjmsx.java:551)
    at com.tibco.tibjms.TibjmsxSessionImp._createConsumer(TibjmsxSessionImp.java:425)
    at com.tibco.tibjms.TibjmsxSessionImp._createConsumer(TibjmsxSessionImp.java:347)
    at com.tibco.tibjms.TibjmsQueueSession.createReceiver(TibjmsQueueSession.java:68)
    at com.tibco.repo.JMSRepoProcess.&ltinit>(JMSRepoProcess.java:102)
    at com.tibco.repo.RemoteRepoServlet$JMSRepoProcessThread.run(RemoteRepoServlet.java:189)


Cause:
=====

Domain Utility uses topics/queues to communicate with the Administrator server. If dynamic destinations are not enabled or the EMS user has does not have proper permissions, then the required queues/topics cannot be created. This leads to failure in the domain discovery procedure.


Resolution:
==========

The following configuration needs to done to resolve this issue:

Specify the user account name authorized to administer the TIBCO Enterprise Message Service server. Specify a user that is a member of the $admin group (for example, the predefined admin user), or a user who has the following permissions:
•     publish, subscribe, and create permissions to the following topics:
com.tibco.repo.>
com.tibco.pof.>
or
com.tibco.pof.HawkConfig.>
com.tibco.pof.MonitoringManagement.>
com.tibco.repo.server_discovery.>
com.tibco.pof.domain-name.> (for each domain)>
com.tibco.pof.AUTH_domain-name.> (for each domain)
com.tibco.repo.instance_mgmt.*.trustworthy_HAWK.domain-name (for each domain)
  public, subscribe, and create permissions to the com.tibco.repo.> queues

Note: You must add the following topics to the TIBCO_HOME/ems/bin/topics.conf file:
com.tibco.pof.domain-name.>
com.tibco.repo.server_discovery.>
com.tibco.pof.AUTH_domain-name.>
com.tibco.repo.instance_mgmt.*.trustworthy
_HAWK.domain-name (one line for each domain)

You must also add the following queue to the TIBCO_HOME/ems/bin/queues.conf file:
com.tibco.repo.>

Note that if domain-name contains the characters '.', '>' and '*', the characters must be replaced by the following strings:
"." replaced by "2E"
">" replaced by "3E"
"*" replaced by "%2A".

References:
==========
TIBCO Runtime Agent™ Domain Utility User’s Guide

Domain Utility fails to add secondary server or machineto an Administrator domain using EMS transport.