Installation

Nexus requires a USB dongle on the computer where it is installed or it will need to use one of the licenses from a network USB dongle. If you already have either of these options available, no additional purchase is necessary.

NexusInstallation

The machine that Nexus is installed on should meet the same requirements for MusicMaster itself. It is strongly recommended that Nexus be run on a workstation or server that is not also used by a MusicMaster user, or for normal daily computing tasks, as this may require frequent and unexpected restarts, which may lead to performances issues. The Nexus application must be running at all times. Otherwise functions occurring while it is down are not processed as Nexus does not cache commands that come in when it is not running. Any commands like this would be lost forever.

 

In an ideal situation, Nexus would be installed and run on the computer where the MusicMaster databases are located or at least have a fast network connection to the database server.

 

The Nexus Server executable is called MMSERVER.EXE and is inside the application directory of MusicMaster on the server with the databases. Any setup that is different from this, for instance a different server than the databases, will result in decreased performance.

The Nexus Sever executable cannot be moved outside this directory, as it requires a number of .dll files in order to work.

If you need a connection outside of your internal network, you would need to consider VPN or some alternative method to do so. It should be noted that there is no authentication of any kind in Nexus. The third-party requesting information does so with full access to all the data available via Nexus. Nexus will update or retrieve information to or from the MusicMaster database as specified.

Nexus runs as an application and must be running on a logged on desktop at all times. If installed on a computer using Remote Desktop Protocol (RDP), there can only be one instance of the application running at a time on any RDP desktop. Failure to adhere to this will create problems with Nexus.

Number of databases per Nexus copy

If the application is only making occasional, simple requests, a single copy may be able to service eight to 10 MusicMaster databases. If the application is calling for information continuously or is asking for the return of large amounts of data, then only one to four databases may be all that can be connected to maintain good performance.

 

Keep in mind that the specifications of the computer (CPU speed, memory, etc) will also come into play. The more powerful the computer, the more databases Nexus should be able to service.

 

There are many possibilities and factors to consider here, so it is difficult to provide a generic answer to this.

Need More Information?

The complete documentation for Nexus is located on our website under Nexus Documentation. Here you'll find full Station Setup and Configuration information.