Unified Agent discovery services support these protocols:
Jini – an open architecture that enables developers to create network-centric services that are highly adaptive to change. Jini offers a standard lookup service for discovery.
User Datagram Protocol (UDP) – a network protocol that provides a procedure for application programs to send messages to other programs with a minimal protocol mechanism.
Jini requires a dedicated Jini server to provide lookup services. UDP does not require a dedicated server. Configuration these services using Server Discovery page on the Logon dialog.
The discovered servers are sorted by name. Each Adaptive Server entry includes the following information:
Name – the server name set by the UA Adaptive Server agent. If the client side interfaces file contains an entry for the same server, the client-side server name is shown.
Version – the version of the Adaptive Server.
Host:Port – the host name and the port number (of the interfaces file for UNIX users and SQL.ini file for Windows users), of the Adaptive Server.
Platform and operating system – platform and operating system of the host.
Status – the current server state.
To edit the plug-in search configuration for Adaptive Server in the discovery process:
Right-click Adaptive Server Enterprise.
Select Properties.
Select the Server Discovery tab, which includes the protocol, host, and port information for the current search. You can change the entries with the following buttons:
Use “Add...” to add a discovery service setting. Select the Discovery method (Jini or UDP). If you select Jini, specify either the default host or the host name and the default port or the port number. Duplicate discovery services are not permitted.
Select OK to add this discovery setting.
Use “Edit ...” to edit an existing discovery service setting.
Use “Remove” to remove the discovery setting. If you remove all discovery settings, the Adaptive Server plug-in uses UDP as the default discovery service.
Use “Up” to move an existing discovery service setting higher in the list.
Use “Down” to move an existing discovery service setting lower in the list.
Server discovery is performed in the order the discovery
settings are specified.
If all the discovery settings are removed, the plug-in uses UDP to search for servers.
The settings you configure for server discovery for
the plug-in are shared with the DBISQL. That is, if you modify the
settings for the Plug-in and then start a session with DBISQL, it
will have the same settings, not those you configured in the last
DBISQL session.
You can use filters to limit the scope of your server discovery search so that only certain Adaptive Servers that match a set of rules are displayed. For example, you can create a filter to show only Adaptive Servers built in the last 12 months.
The plug-in shows what filters are enabled on the Server Discovery tab. To add or edit a filter, click the Filter button. The plug-in displays the Server Discovery Filters dialog box, which lists the current filters. You can enable or disable filters, but Server Discovery only uses the enabled filters for its search. The Server Discovery Filter dialog box includes these buttons:
Add – Add a new filter
Remove – Remove a listed filter
Edit – Edit a listed filter
Enable All – Enable all listed filters
Disable All – Disable all listed filters
Filters are comprised of a Target (a server attribute) and a Condition (a search condition). To add a new filter:
Click Add. The plug-in displays the Add Filter dialog box.
If you want this filter enabled, select Enable this filter.
Select the target you want filtered from this list (the Name target shows by default. The available targets are: Host, Name, OS, Platform, Port, Release type, Status, Version.
Select the condition you want filtered from the list (the “does not contain” condition shows by default). This available conditions are: contains, does not contain, is, is not, starts with, ends with.
Enter the condition string you want filtered.
Select OK to configure this filter.
The settings you configure for filters for the plug-in
are shared with DBISQL. That is, if you add or edit the filters
for the plug-in and then start a session with DBISQL, it will have
the same filter configuration, not those you configured in the last
DBISQL session.