NFuse Classic
NFuse Classic

Application lists can potentially be returned in a different order if the applist request is made to different XML servers. This is because the order is kept in RAM and is generated upon a server event (boot up/down or an application being published). Each server in a farm reports to all servers what applications it has published on it (by looking in its registry) every time one of these server events transpires. However, timing is a factor here because other servers could start notifying a booting server of its application list before it reads the initial list from its registry. The following example demonstrates this concept:
< p>There are three servers, all with App1, App2, and App3 published across them.

Server 1 boots first. The order is:
App1 - Server1
App2 - Server1
App3 - Server1

Server 2 begins to boot, followed by Server 3 after a five second delay.

Server 1 begins to broadcast what applications it has. These broadcasts could potentially be received by the booting servers before they look into their registry to see what applications it has published.

Server 2 gets notified of App1 followed by App2 before beginning to look in its registry. Server 3 (because of the delay) gets notification of App2 and App3 during this round of broadcasts before beginning to look in its registry.

Therefore, the list for Server 2 looks like:
App1 - Server1, Server2
App2 - Server1, Server2
App3 - Server2, Server1

And the list for Server3 looks like:
App2 - Server1, Server3
App3 - Server1, Server3
App1 - Server3

Following sequential broadcasts by all three servers, the list finally includes all applications and the servers to which it is published.

Server 1:
App1 - Server1, Server2, Server3
App2 - Server1, Server2, Server3
App3 - Server1, Server2, Server3

Server 2:
App1 - Server1, Server2, Server3
App2 - Server1, Server2, Server3
App3 - Server2, Server1, Server3

Server 3
App2 - Server1, Server3, Server2
App3 - Server1, Server3, Server2
App1 - Server3, Server1, Server2

Possible Solution

This sorting solution requires the use of some server-side scripting, but does not require recoding (if a new application gets added) or a reordering of the applications.

NOTE: This solution assumes that the application set presented to NFuse users does not contain any folders.

Using Published Application Manager, modify the properties of each application so the application is contained in a folder. The folder name becomes the sorting mechanism. For example, if you want the applist to look like: Word, Excel, PowerPoint, Word would be contained in a folder called "1," Excel in "2," and Powerpoint in "3." In Applist.asp, the application list is sorted based on folder numbers, but the folders themselves are not displayed. That makes it easy to add another application or reorder the list without having to ever modify the ASP script.

This algorithm can also be accomplished by using another application property that is not being displayed; for example, application description.