IBM Tivoli Netcool/OMNIbus, Version 7.4

Importing configurations

To import a configuration, run the nco_confpack utility on the installation of Tivoli Netcool/OMNIbus that contains the ObjectServer into which you want to import the configuration. You can import a configuration package into any V7.4 ObjectServer. You can import information from a configuration package into only one ObjectServer at a time.

The source and target ObjectServers can be on different installations of Tivoli Netcool/OMNIbus. You can export the configuration from one installation, send it to an installation on another server, and import the configuration to an ObjectServer on that installation.

Note: If an object in the configuration package has the same name as an object of the same type in the target ObjectServer, the existing object is replaced with the object from the configuration package. For example, a tool named sample in the configuration package will overwrite an existing tool named sample in the target ObjectServer. To avoid data loss, make sure that you back up your ObjectServer before importing a configuration package.

To import a configuration package, run the following command:

$NCHOME/omnibus/bin/nco_confpack -import -subcommand parameter, ...

In this command, -subcommand parameter can be any of the subcommands in the following table.

Table 1. Subcommands and corresponding properties nco_confpack -import
Subcommand	Property	Description
-force TRUE \| FALSE	confpack.import.force TRUE \| FALSE	By default, when importing a tool or stored procedure that references an external file (such as a script) the file is included during the import. If an identical file already exists, the existing file is not overwritten. You can use the -force option to force an overwrite even if the referenced file already exists. Attention: Use the -force subcommand with caution. Make sure your file system is backed up before importing the configuration package. The default is FALSE.
-from `string`	confpack.import.from `string`	The source ObjectServer name, as indicated in the configuration package from which you are importing configuration objects. Note: If the configuration package contains information for only one ObjectServer, you do not need to use this subcommand. If the configuration package contains information for multiple ObjectServers, this subcommand is required. The default is `''`.
-memstoredatadirectory `OSname:string, OSname2:string, ...`	objectserver.`OSname`.memstoredatadirectory `string`	Specifies an alternative database directory for each ObjectServer, where: `OSname` is the name of the ObjectServer. `string` is the path that contains the ObjectServer database files. The default is $NCHOME/omnibus/db. `OSName` can be substituted with an asterisk () to indicate a general path for all ObjectServers for which an explicit path is not supplied. If the path is the same for all ObjectServers, `OSName` can be omitted. For example: -memstoredatadirectory `string` You can have multiple entries in the same properties file for different ObjectServers. For example: `objectserver.NCOMSA. memstoredatadirectory : path1 objectserver.NCOMSB. memstoredatadirectory : path2` Note: On Windows, if you want to specify a path that includes a drive letter, do not* omit the `OSName` value because the drive letter will be interpreted as an ObjectServer name. For example, specifying `-memstoredatadirectory C:\MyDir` causes C to be interpreted as the ObjectServer name.
-nowarn TRUE \| FALSE	confpack.import.nowarn TRUE \| FALSE	Suppresses warning messages. Note: If you use stdin to import the configuration package, you must enable this option. The default is FALSE.
-package `string`	confpack.package.name `string`	Name of the configuration package. The default is stdin.
-password `string`	objectserver.`OSname`.password `string`	Login password for the ObjectServer. The default password is `''`.
-propsfile `string`	N/A	Specifies the nco_confpack properties file. You can use the properties file instead of entering individual subcommands on the command line. The default properties file is $NCHOME/omnibus/etc/nco_confpack.props.
-select `string`	confpack.import.select `string`	Specifies a file containing a subset of objects to be extracted from the package and imported into the ObjectServer. Create the file by using the -list command-line option. Edit the file to remove all entries except for the ones that you want to import into the ObjectServer. The default is `''`.
-server `OSname`	confpack.omnibus.servers `OSname`	The ObjectServer into which you are importing configuration objects. You can only import data into an ObjectServer that is running on the local machine. The default ObjectServer is NCOMS.
-timeout`OSname:string, OSname2:string,...`	objectserver.`OSname`.timeout `string`	Specifies the time, in milliseconds, that the utility waits for a response from the ObjectServer, where `OSname` is the name of the ObjectServer, and `string` is the amount of time. The default time is 6000 milliseconds (one minute).
-user `string`	objectserver.`OSname`.user `string`	Login user name for the ObjectServer. The default user name is the current operating system user.