Description:
Although the adapter documentation for R/3 adapter version 5.4.0 states that adapter v5.4.0 supports discovery agent feature, the discovery agent provided during the adapter installation will not function properly.

This same behavior is seen with adapter versions 5.4.0 and below for both Unicode and Non-Unicode adapters.

Symptoms:
=========
While using Discovery agent feature, the “SERVERHOST” is not published/ published empty. The values published for “SERVICE” are incorrect.

While listening on the DiscoveryPublishSubject=R3.APPSERVERS.ACTIVE, the following output will be displayed:-
2007-08-16 18:08:11 (2007-08-16 12:38:11.156000000Z): subject=R3.APPSERVERS.ACTIVE, message={^type^=1 ^pfmt^=10 ^ver^=30 ^encoding^=1 ^prefixList^={1="/tibco/public/class/ae/SAPAdapter40/classes" default="/tibco/public/sequence/ae/class/ae/SAPAdapter40/classes"} ^tracking^={^id^="54M--C--FgF3Ak7k-2o9f/YLI-i5E"} ^data^={^class^="sequence[SERVERINFO]" ^1^={^class^="SERVERINFO" ^idx^=1 SERVERNAME="Blrkecsvr1490_ECU_00" SERVERHOST="" SERVICE="blrkecsvr1490"}}}

The value for SERVERHOST which is returned for SERVICE appears as empty (SERVERHOST="").

Cause:
=====

The adr3Discovery.dat file shipped with the adapter installation is invalid.

Impact:
=====
Loss of Functionality as the adapter is not able to connect to the application servers while discovery agent is turned on.

Workaround:
==========
Use the adr3Discovery.dat file shipped with the adr3 5.4.1 or higher versions.

Resolution:
=========
This issue has been fixed in adapter version 5.4.1. Please upgrade to adapter version 5.4.1 or above to overcome this.
Symptoms:

Cause:

The discovery agent feature of TIBCO Adapter (TM) for R/3 does not work as expected with adapter versions 5.4.0 and below.