This option allows you to import a configuration from a running SAM 7.x/NOTIF 2.x server into the NOTIF Editor and save it as an .ncf file on a SAM 9.2/ NOTIF server.

Note:

This option functions in a similar fashion as the Import from file option previously described. For example, if no configuration is open, the import will create a new configuration; if a configuration is open, the NOTIF Editor will ask you if it should Cancel Import, Create New, or Add to Current, and so on.

To import a configuration from an older NOTIF server:

  1. In the NOTIF Editor, select Help > Migration > Import from an older NOTIF server…

  2. The Connect to a Server dialog box appears, as shown in the figure. Choose the running SAM 7.x/NOTIF 2.x server where you want to import the configuration from and click OK.

    The configuration from the running SAM 7.x/NOTIF 2.x server is loaded into into the NOTIF Editor.

  3. Select Remote > Push to Server...

  4. The Connect to a Server dialog box appears. Choose the SAM 9.2 server where you want to push the older configuration to and click OK.

  5. The Directory dialog box appears, as shown in the figure. Choose the directory location on the SAM 9.2 server where you want to store your configuration and click OK.

  6. The Select Remote File dialog box appears as shown in the figure. This is the name of the *.ncf file you are storing on the SAM 9.2 server. The *.ncf file is always stored to the BASEDIR/smarts/local/conf/<config> directory on the SAM 9.2 server. Name the *.ncf file that you want to push to the SAM 9.2 server and click OK.

  7. The Push Complete dialog box appears, as shown in the figure. This dialog confirms that the *.ncf file has been pushed to the SAM 9.2 server and prompts you to reload the NOTIF processor on that server so that the new configuration takes effect.

    Note:

    Reloading of the *.ncf file on a remote NOTIF server reloads all *.ncf files in the corresponding icoi/ics directories in that server. Care should be taken to ensure there are no conflicting configurations within multiple *.ncf files as the order in which these files are read is undetermined.

  8. Click Yes to reload the NOTIF processor to make the new configuration active on the SAM 9.2 server.

  9. The Reload Complete dialog box appears as shown in the figure. This dialog box confirms that the new configuration in the *.ncf file has been reloaded and is persistent in the SAM 9.2 server. Click OK.

    Note:

    In SAM 8.1 and above, the configurations are saved to the .ncf file and can be imported to SAM 9.2 using Open Configuration and Push to server operation . “Open Configuration...” on page 74 and “Push to server...” on page 81 provide more details.