IBM Tivoli Netcool/OMNIbus V7.2.1 IEA IBM Tivoli Netcool/OMNIbus V7.2.1 IEA Using the nco_confpack utility Hello, and welcome to the OMNIBUS IBM Education Assistant module, Using the nco_confpack utility. Introduction to the nco_confpack utility Introduction to the nco_confpack utility You can use the nco_confpack utility to: Import and export entire ObjectServer configurations installations Extract a subset of configuration objects (for example, event list menus and tools) from ObjectServers and import them into other ObjectServers Save ObjectServer configuration objects for backup purposes Create Backup ObjectServers Implement changes to an existing ObjectServer You can use the nco_confpack utility to: Import and export entire ObjectServer configurations installations, Extract a subset of configuration objects (for example, event list menus and tools) from ObjectServers and import them into other ObjectServers, Save ObjectServer configuration objects for backup purposes, Create Backup ObjectServers, Implement changes to an existing ObjectServer. Specifications Specifications The administrator GUI and the nco_confpack utility require the Java™ Runtime Environment (JRE) to be installed on your operating system. OMNIbus supports the following JREs: JavaSoft JRE 1.5 on Linux®, Solaris, and Windows® platforms IBM JRE 1.4.2 on AIX® platforms HP JRE 1.5 on HP-UX platforms You can use nco_confpack to import and export the following ObjectServer objects: Triggers Trigger groups Procedures User-defined signals Menus Tools Prompts Classes Conversions Column visuals Colors Users Groups Roles Tables Views Restriction filters Object server file definitions The nco_confpack utility requires a Java Runtime Environment to be installed on your operating system. The appropriate, operating system specific, JRE is installed during product installation. The nco_confpack utility can import and export several ObjectServer objects. General steps General steps The general guidelines to use the nco_confpack utility are to: Ensure that your ObjectServer is running Create, edit, and save a configuration list file Export configuration list file to a Java archive Select and import the archive to the destination ObjectServer The general guidelines to use the nco_confpack utility are to: Ensure that your ObjectServer is running. Create, edit, and save a configuration list file. Export configuration list files to a Java archive. Select and import the archive to the destination ObjectServer. Configuration List File Configuration List File To create the configuration list file: Select the ObjectServer to copy the configuration from As an OMNIbus administrator, go to the $OMNIHOME/bin directory. As a single entry, specify a location and name of the editable file. Use the ObjectServer’s super-user credentials to complete the following command: ./nco_confpack –list –server PRIMARY –file $OMNIHOME/etc/PRI_LIST.txt –user objservadmin –password objservadmin’spassword To create the configuration list file: Select the ObjectServer to copy the configuration from. As an OMNIbus administrator, go to the $OMNIHOME/bin directory. As a single entry, specify a location and name of the editable file. Use the ObjectServer’s super-user credentials to complete the following command: ./nco_confpack –list –server then the objectServer’s name –file the path and name of the file –user the ObjectServer’s super-user –password the superusers password. Create a configuration list file: options Create a configuration list file: options Additional command-line parameters exist for multiple or all running ObjectServers as well as additional user and password combinations. You might also create and reference a properties file for the nco_confpack command as in the following example: nc.home                          :  '/opt/netcool' omni.home                        :  '/opt/netcool/omnibus' license.file                     :  '27000@licenseA_NY&27000@licenseB_NY' objectserver.NCOMS_NY.user:  'joe_ny' objectserver.NCOMS_NY.password:  'jOE_4_NY' confpack.list.name               :  'NCOMS_NY_export_list.txt' confpack.package.name            :  '' confpack.omnibus.servers         :  'NCOMS_NY' Additional command-line parameters exist for multiple, or all, running ObjectServers as well as additional user and password combinations. You might also create and reference a properties file for the nco_confpack command. Refer to the administrator’s manual for additional options. When to edit a configuration list file When to edit a configuration list file After you have your configuration list file created, you can either export the file or open the file for editing. If you are creating backup or disaster recovery instances of any or all of your ObjectServers, you must export and store your configuration list file. If you are migrating data, creating a fail-over or duplicate ObjectServer, or running configuration changes, you must edit the configuration list file. After you have your configuration list file created, you can either export the file or open the file for editing. If you are creating backup or disaster recovery instances of any or all of your ObjectServers, you must export and store your configuration list file. If you are migrating data, creating a fail over or duplicate ObjectServer, or running configuration changes, you must edit the configuration list file. Editing and saving a configuration list file Editing and saving a configuration list file To edit the configuration list file, you must navigate to the location where you saved the file and edit the file with your editor. If you are performing a data migration or changing an existing configuration, you must select the ObjectServer elements to retain or remove from the configuration list before exporting. If you are creating a duplicate ObjectServer or failover ObjectServer, you must remove two line items from the configuration file before exporting: ObjectServer PRIMARY SQLfile profiler_report ObjectServer PRIMARY SQLfile trigger_stats_report Save the configuration file when you are finished editing. To edit the configuration list file you must navigate to the location where you saved the file and edit the file with your editor. If you are performing a data migration or changing an existing configuration, you must select the ObjectServer elements to retain or remove from the configuration file before exporting. If you are performing a creation of a duplicate or fail-over ObjectServer two line items must be removed from the configuration file prior to exporting. This step is due to the reference to the source’s ObjectServer within the path to the report directories. Save the configuration file when you are finished editing. Exporting the configuration file Exporting the configuration file After all tasks are completed with the ObjectServer’s configuration file you must export the file into a Java archive (JAR) archived format. To export a configuration list file, from the saved location, to the same or another location. Use the following two commands: cd $OMNIHOME/bin ./nco_confpack –export –file $OMNIHOME/etc/PRI_LIST.txt –package $OMNIHOME/etc/PRIMARY_CONFIGURATION.jar After all tasks are completed with the ObjectServer’s configuration file you must export the file into a Java archive (JAR) archived format. To export a configuration list file, from the saved location, to the same or another location. Use the following two commands: cd $OMNIHOME/bin ./nco_confpack –export –file the path and file name of your saved configuration list file –package the desired path and name for your archive file. Exporting the configuration file Exporting the configuration file You can use other command-line options to export the ObjectServers configuration list file or use a properties file reference for the process. The following example shows a properties file contents: nc.home                          :  '/opt/netcool' omni.home                       :  '/opt/netcool/omnibus' license.file                     :  '27000@licenseA_NY&27000@licenseB_NY' objectserver.NCOMS_NY.user       :  'joe_ny' objectserver.NCOMS_NY.password  :  'jOE_4_NY' confpack.list.name               :  'NCOMS_NY_export_list.txt' confpack.package.name            :  'NCOMS_NY_export.pak.jar' confpack.omnibus.servers         :  'NCOMS_NY' confpack.export.rename           :  '' You can use other command-line options to export the ObjectServer’s configuration list file or use a properties file reference for the process. Importing an archived configuration Importing an archived configuration Before importing a configuration, you might want to observe the contents of the archived file. To accomplish this task, you must run the following command on the stored file: ./nco_confpack –contents –package $OMNIHOME/etc/PRIMARY_CONFIGURATION.jar When required, you might import an archived configuration into any destination ObjectServer. The following command reflects creation of a backup ObjectServer. Use the following single-line command: ./nco_confpack –import –package $OMNIHOME/etc/PRIMARY_CONFIGURATION.jar –server BACKUP –user backupobjservadmin –password backupobjservadmin’spassword Before importing a configuration, you might want to observe the contents of an archived file. To accomplish this task, you must run the following command on the stored file: ./nco_confpack –contents –package the path and file name of your stored archive file . When required, you might import an archived configuration into any destination ObjectServer. The following command reflects creation of a backup ObjectServer. Use the following single-line command: ./nco_confpack –import –package the path and name of your stored archive file –server then your destination ObjectServer –user the destination Objectserver’s administrative user –password and the administrative user’s password. Importing an archived configuration: options Importing an archived configuration: options The nco_confpack –import command also has a variety of additional options. Some of the additional commands correlate to their counterpart nco_confpack –export command. Additionally, a properties file might be used with an import activity. Consult the administrator’s guide for more advanced command-line options. The nco_confpack – import command also has a variety of additional options. Some of the additional commands correlate to their counterpart nco_confpack –export command. Additionally, a properties file might be used with an import activity. Consult the administrator’s guide for more advanced command-line options. Training roadmap for Netcool® Tivoli OMNIbus Training roadmap for Netcool® Tivoli OMNIbus http://www.ibm.com/software/tivoli/education/edu_prd.html For further training, refer to the link http://www.ibm.com/software/tivoli/education/edu_prd.html Trademarks This concludes this module.