This paper identifies the additional procedures for installing Unicenter NSM r11.1 in an environment where the MDB resides on a separate machine from the Unicenter NSM manager server. It should be used in conjunction with the standard procedures documented in the Unicenter NSM Implementation Guide.
There are 3 parts to this process:
Configure the existing MDB on the Microsoft SQL Server machine
Install required Unicenter NSM Management components on a separate machine.
Identify the target MDB that will be used by the WorldView and Management Command Center (MCC) components
The MDB can be installed by any r11.1 product. For example, if you have already installed Unicenter Desktop and Server Management r11.1, you will already have an existing MDB that can be used by Unicenter NSM.
Even though the MDB exists, however, you will still need to configure it in order for Unicenter NSM to use it. Further, if you intend to use WorldView or MCC, both the WorldView Manager and optional WorldView Provider (required for MCC) components must be installed on the MDB machine.
Since you cannot install or configure the MDB remotely, you will need to first run the Unicenter NSM setup on the MS-SQL Server on which the MDB resides.
Figure 1: NSM Component Selection Dialog
You will have the option of selecting either “MDB for Microsoft SQL Server” or “Configure MDB for Microsoft SQL Server.”
If you select “MDB for Microsoft SQL Server,” the MDB setup will update the MDB if necessary but it will also protect any existing data. It will also handle the configuration necessary for Unicenter NSM.
If you select “Configure MDB for Microsoft SQL Server” it will only configure the MDB for Unicenter NSM.
If you select both options a warning message will be issued and the configuration option will be deselected.
Figure 2: Warning message when both MDB install and configuration options are selected.
The install will prompt for the user credentials for the Unicenter NSM MDB administrator. By default this is “nsmadmin” however, it can be any six character or longer string should your security policy require something different. It cannot, however, be a user id that has already been defined to the SQL Server. The install will create and configure the user id as required.
The installer will present the appropriate Database Selection and Configuration screen with database selections based on which components were previously selected.
Once the MDB has been configured, the next step is to install the Unicenter NSM management components on the NSM management machine. This server must, minimally, already have the MS-SQL Client installed and must have connectivity to the MDB.
Note: For additional details regarding this step, consult the “Microsoft SQL Server Considerations” in the Unicenter NSM Implementation Guide.
When you execute the installation, the list of selectable components will depend on which Microsoft SQL Server components have already been installed.
Figure 3: Default component selection for remote install.
As you can see in Figure 3 above, the MDB options are disabled because MS-SQL Server is not available on the machine. Also, components such as the WorldView Manager are disabled since you cannot install the WorldView Manager on any machine other than that on which the MDB resides.
On the Database Selection and Configuration dialog shown in Figure 4 enter or use the Browse button to identify the SQL server on which the MDB is installed. Since the installation supports the definition of separate MDBs for WorldView and Enterprise Manager, there are two selections on this dialog and you should be aware that the credentials are not copied across.
Figure 4: Database selection
Once you have entered the appropriate database credentials, click Validate Logon. The status of the target MDB and the connection status (successful or not) will be displayed in the top pane.
Select an MDB
In order for WorldView to access the MDB it must first be defined and selected.
When you first open the classic 2D map, wvrepsel identifies the local host. Click Find to display the MDB server (and instance). Click OK to use this MDB. The map should then proceed to open.
When you first open the Management Command Center (MCC), you will need to point it to a global catalog with the MDB definition.
Figure 5: Prompt to select a global catalog.
Click Yes and provide the name of the Global Catalog server. Click OK and the MCC should then open.
Figure 6: Global catalog selection
File: installing nsm r11.1 w remote mdb.doc - –