What is heap memory allocation

Tivoli Netcool / OMNIbus Version 8 Release 1. Web GUI Administration and User's Guide IBM SC

Transcript

1 Tivoli Netcool / OMNIbus Version 8 Release 1 Web GUI Administration and User Guide IBM SC

2

3 Tivoli Netcool / OMNIbus Version 8 Release 1 Web GUI Administration and User's Guide IBM SC

4 Note Before using this information and the product it supports, read the information under Notices on page 381. This publication is a translation of the manual IBM Tivoli Netcool / OMNIbus, Version 8 Release 1, Web GUI Administration and User Guide, IBM Form SC, published by International Business Machines Corporation, USA Copyright International Business Machines Corporation 2001, 2017 Information intended for use only certain countries are valid and do not apply to Germany, Austria and Switzerland, have been taken over in this publication in the original text. It is possible that not all products listed in this translation are announced and available in Germany; Before making any decisions, it is advisable to contact the responsible IBM office. Change to the text are reserved. Issued by: TSC Germany Kst July 2017 Copyright IBM Corporation 2001, 2017.

5 Table of Contents About This Publication vii Audience vii Publications vii Disabled Access ix Tivoli Training ix Support Information ix Conventions Used in This Guide .. x Chapter 1. Administering the Web GUI Server .. x Chapter 1. Administering the Web GUI Server .. 1 Restart the Server View the Application Server Profile Change the Port Assignment Timeout Setting Disable the Session Timeout Define ObjectServer as user repository ... 6 Change password for ObjectServer connection ... 7 Manage time-controlled tasks Control the use of time-controlled tasks ... 8 Define update properties Overview of time-controlled tasks Query event database Copy data between Web GUI servers Overview of data from a Web GUI -Export servers .. 13 Import data to a Web GUI server .. 17 Clone data between servers Set the log level for the utility 25 Back up and restore data Back up and restore the Web GUI Dashboard Application Services Backing up and restoring the hub Chapter 2. Managing the GUI framework .. 27 Managing pages Creating dashboards Configuring communication between widgets using connections Editing dashboards or pages Creating folders Editing the content and layout of dashboards 33 Deleting customized pages and folders Deleting system pages, folders and external URLs Restore Create Start Pages Manage Views Create Views Edit Views Delete Custom Views Working with Widgets Configure Custom Help for Web GUI Widgets Manage Console Settings Profiles Create Settings Profiles Edit Console Settings Profiles Delete Console Settings Develop Transformations Develop Java Transformations Develop JavaScript Transformations Servlets for Developing URL Transformations Defining Transformations in the Transformation Descriptor Implementing Transformations Resource Types Managing Global Update Chapter 3. Dars Dashboards Develop locations of events Connect event displays Connect event lists to display related events from a measurement display Connect measurement displays with an event display for mobile devices Display event data in Dashboard Application Services Hub Show event data from the Web GUI data provider Supply dashboard widgets Source and target databases for connecting widgets Chapter 4. Managing Users, Roles, and Groups Provided Users and Groups Provided Roles Change Passwords Create Web GUI Administrative Users Create Users in the WebSphere Administrative Console Change User Preferences Manage Roles Manage Roles for Users Manage Roles for Groups Create Roles Edit Roles Delete Custom Roles Assigning Roles for Users and Groups Chapter 5. Managing Load Balancing Clusters The Web GUI in a Load Balanced Environment 81 Structure of a Cluster Configuration Information Configuration Information update prerequisites for changing configuration information managing load balancing clusters using load balancing clusters managing the list of files to be monitored. 91 Copyright IBM Corp. 2001, 2017 iii

6 Cluster Management Tools Monitoring Load Balancing Clusters Best Practices for Load Balancing Chapter 6. Tips for Optimizing Performance for the Web GUI Increase JVM Memory on the Web GUI Server 117 Increase Memory for Java Virtual Machines of the Web GUI Client Optimizing Performance Chapter 8. Event Viewer in the Web GUI Customize Create Event Management Tools Overview of Tools Define Tool Prompts Define and Register Tools Runtime Parameters Define Tools Modify Menus Set Widget Preferences Set LAE Widgets Preferences 150 Set Graph Widgets Preferences Set Event Dashboard Widget Preferences and Defaults Setting Preferences for Event Viewer Widgets Setting Preferences for Gauge Viewer Widgets Setting Preferences for Inline Frame Widgets Setting Preferences for VEL Widgets 173 Setting Preferences for Map Portlet Setting Preferences for Relationship Definition Widgets Setting Preferences for Table View Widgets Setting Preferences for Web Widgets 169 Filtering Event Data Filters

7 Configuring views Configuring the filter for event data 200 Customizing event lists Changing the update rate Changing the display for the event severity Changing the font and window settings 213 Changing the font color of confirmed events 214 Customizing the event display Defining the display and behavior of the list of active events (LAE) Chapter 9. Invalid Characters in Filters, Views, and Tools Appendix D. SmartPage Commands and Templates SmartPage Commands Overview SmartPage Code Sample SmartPage Commands Reference Enable: smartpage Command Validate Command Insert: ael Command Insert: aelmapview Insert command: maplet insert: filterpage command insert: usermaplist command insert: tableview command insert: username command insert: usershomeurl command Template overview Example template Guidelines for using SmartPage templates Create SmartPage templates Appendix E. Web GUI Database Tables Table OMNIBUS_WEB_GUI.CONFIG_ITEMS Table OMNIBUS_WEB_GUI.NODES Table OMNIBUS_WEB_GUI.NODES_CONFIG_ITEMS Appendix F. URLs for opening Web GUI widgets Comments Brands Index Appendix A. Functions for handicapped accessible operation for the Web GUI- source. Elements of the Web GUI DTD Table of Contents v

8 vi IBM Tivoli Netcool / OMNIbus: Web GUI Administration and User's Guide

9 About this publication Audience publications The IBM Tivoli Netcool / OMNIbus Web GUI is a web-based application that processes network events from one or more data sources and presents the event data to users in various graphical formats. The IBM Tivoli Netcool / OMNIbus Web GUI Administration and User's Guide explains how to manage, customize, and use the Tivoli Netcool / OMNIbus Web GUI. For information on using the Web GUI Administration API (WAAPI) to remotely administer the Web GUI, see the IBM Tivoli Netcool / OMNIbus Web GUI Administration API (WAAPI) User's Guide. This manual is intended for administrators and operators who use the Tivoli Netcool / OMNIbus Web GUI. The guide provides information on administering the Web GUI, creating custom event displays, and monitoring and managing event data. This section lists the publications in the Tivoli Netcool / OMNIbus library and related documents. It also describes how to access the available Tivoli publications online and how to order Tivoli publications. Tivoli Netcool / OMNIbus Library The following documents are available from the Tivoli Netcool / OMNIbus library: v IBM Tivoli Netcool / OMNIbus Installation and Deployment Guide, This guide provides installation and upgrade procedures for Tivoli Netcool / OMNIbus. It also describes how to configure security and component communication. The publication also includes examples of Tivoli Netcool / OMNIbus architectures and descriptions of their implementation. v IBM Tivoli Netcool / OMNIbus Administration Guide, This guide describes how to perform administrative tasks using the Tivoli Netcool / OMNIbus administrator GUI, command line tools, and process control. The publication also includes descriptions and examples of ObjectServer's SQL syntax and automations. v IBM Tivoli Netcool / OMNIbus Web GUI Administration and User's Guide, Describes how to perform administrative and event visualization tasks using the Tivoli Netcool / OMNIbus Web GUI. v IBM Tivoli Netcool / OMNIbus User's Guide, This guide provides an overview of the desktop tools. It also describes the operator tasks involved in managing events using these tools. Copyright IBM Corp. 2001, 2017 vii

10 v IBM Tivoli Netcool / OMNIbus Probe and Gateway Guide, This guide contains - in addition to an introduction - reference information about tests and gateways (including information on the syntax of test rule files and gateway commands). v IBM Tivoli Monitoring for Tivoli Netcool / OMNIbus Agent User's Guide, Describes how to install the status monitoring agent for Tivoli Netcool / OMNIbus and contains agent reference information. v IBM Tivoli Netcool / OMNIbus Event Integration Facility Reference, Describes how to develop event adapters that are specific to your network environment and the needs of your business. This publication also describes how to filter events at the source. v IBM Tivoli Netcool / OMNIbus Error Messages Guide, This guide lists the system messages in Tivoli Netcool / OMNIbus and how to receive them. v IBM Tivoli Netcool / OMNIbus Web GUI Administration API (WAAPI) User's Guide, Describes how to administer the Tivoli Netcool / OMNIbus Web GUI using the XML application programming interface called WAAPI. v IBM Tivoli Netcool / OMNIbus ObjectServer HTTP Interface Reference Guide, Describes the URIs and general behavior of the ObjectServer HTTP Interface API. It also describes how the API can be activated and provides examples of JSON payloads and HTTP requests and responses. v IBM Tivoli Netcool / OMNIbus ObjectServer OSLC Interface Reference Guide, Describes the services, resources, and general behavior of the ObjectServer OSLC Interface (OSLC) API. It also describes how the API can be activated and provides examples of service provider definitions, RDF / XML payloads, and HTTP requests and responses. If you are using other IBM products to extend the functionality of Tivoli Netcool / OMNIbus, such as DB2, IBM Tivoli Monitoring, or Tivoli Common Reporting, refer to the relevant product information center for information on the relevant publications. Accessing terminology online The IBM Terminology Web site provides an easy and convenient way to access terminology in the IBM product libraries. You can access the terminology web site at the following web address: Accessing publications online IBM provides publications for this and all other Tivoli products on the following Tivoli Downloads web site as they become available or when they are updated: ftp: / /public.dhe.ibm.com/software/tivoli/netcool/netcoolomnibus/library/ viii IBM Tivoli Netcool / OMNIbus: Web GUI Administration and User Guide

11 Note: If you do not want to print letter-size PDF documents, use the option in the File> Print window to instruct Adobe Reader to print letter-size pages on the paper you are using. Accessibility Features Tivoli Training The Accessibility Features help users with physical disabilities, such as limited mobility or limited vision, to successfully use software products. This product supports technologies for handicapped accessible operation, with the help of which the elements of the user interface can be announced and the navigation in the interface is simplified. In addition, you can use the keyboard instead of the mouse to perform most of the graphical user interface functions. For more information, see the Accessibility Appendix in Appendix A, Accessibility Features for the Web GUI, on page 313. For information about Tivoli training, see the following IBM Tivoli training website: For assistance with using your IBM Software problems occur, then it is important to fix them as soon as possible. IBM provides the following options for you to get support: On-line Go to the IBM Software Support website at, and follow the instructions there. IBM Support Assistant IBM Support Assistant (ISA) is a free, local, serviceability enhancement environment that you can use to answer questions and troubleshoot problems you may have while using IBM software products. IBM Support Assistant gives you quick access to support-related information and serviceability tools to help you diagnose problems. Go to support / isa to install the IBM Support Assistant software. Documentation If you have any suggestions on how to improve the content or structure of this guide, please send your suggestions to the Tivoli Netcool / OMNIbus Information Development team at: About this publication ix

12 Conventions Used in This Manual In this manual, various conventions are used to represent certain terms and actions as well as to specify commands and paths that are dependent on the operating system. Web GUI home directory WEBGUI_HOME Points to the directory where the web GUI is installed. This directory is known as the Web GUI home directory. The default values ​​are as follows: UNIX Linux / opt / ibm / tivoli / netcool / omnibus_webgui Windows C: \ IBM \ tivoli \ netcool \ omnibus_webgui The Web GUI home directory is different from the Jazz for Service Management home directories. Jazz for Service Management home directories WAS_HOME Points to the location where WebSphere Application Server is installed. This position can be specified during the installation. The default values ​​are as follows: UNIX Linux / opt / ibm / websphere / appserver Windows C: \ Program Files \ IBM \ WebSphere \ AppServer JazzSM_HOME Points to the location where Jazz for Service Management is installed. This position can be specified during the installation. The default values ​​are as follows: UNIX Linux / opt / ibm / jazzsm Windows C: \ Program Files \ IBM \ JazzSM jazzsm-was-profile Points to the location of the application server profile used for Jazz for Service Management. This location is in the / profile / subdirectory of the Jazz for Service Management home directory: UNIX Linux / opt / ibm / jazzsm / profile Windows C: \ Program Files \ IBM \ JazzSM \ profile DASH_HOME Points to the location of the Dashboard Application Services Hub is installed. This position can be specified during the installation. The default values ​​are as follows: UNIX Linux / opt / ibm / jazzsm / ui Windows C: \ Program Files \ IBM \ JazzSM \ ui For other Jazz for Service Management installation locations, see the Jazz for Service Management information center at x IBM Tivoli Netcool / OMNIbus: Web GUI Administration and User's Guide

13 Operating system-dependent variables and path specifications In this manual, the UNIX conventions are used to define environment variables and directory specifications. If you use the Windows command line, replace $ variable with% variable% for environment variables and replace slashes ((/)) with backslashes ((\)) in directory paths. For example, on UNIX systems, the $ NCHOME environment variable specifies the path to the Netcool home directory. On Windows systems, the% NCHOME% environment variable specifies the path to the Netcool home directory. Environment variable names can vary on Windows and UNIX. So is z. For example, in Windows environments the% TEMP% environment variable has the same meaning as the $ TMPDIR environment variable in UNIX environments. If you are using the Bash shell on a Windows system, you can use the UNIX conventions. Netcool Home The Netcool Home is the home directory in which Tivoli Netcool / OMNIbus is installed. The Netcool home position is defined by the NCHOME environment variable. The value of NCHOME is as follows: v UNIX Linux $ NCHOME default: / opt / ibm / tivoli / netcool v Windows% NCHOME% default: C: \ IBM \ Tivoli \ Netcool If a directory or command path with the NCHOME variable starts, the information applies to all supported operating systems. Other products that use the NCHOME environment variable, such as: B.IBM Tivoli Network Manager IP Edition, can be installed in the Netcool home location. For each product, the respective components and files are installed in an assigned product subdirectory of the Netcool starting position. Files that are common to all products are installed in shared subdirectories of the Netcool home location. Note graphic conventions The documentation for Tivoli Netcool / OMNIbus contains note graphics that indicate that parts of a section or instruction apply only under certain conditions. The meaning of the individual graphics is described in the following table. Table 1. Note graphics for Tivoli Netcool / OMNIbus Graphic PureData Web GUI Description The text or instruction applies only to the Web GUI component. UNIX The text or instruction applies only to UNIX operating systems such as AIX and Solaris. The following note graphics are used for AIX and Solaris as needed: AIX Solaris Linux The text or instruction applies only to Linux operating systems. About this publication xi

14 Table 1. Note graphics for Tivoli Netcool / OMNIbus (cont.) Graphic Windows 32-bit 64-bit FIPS Default Fix Pack 1 Description The text or instruction applies only to Windows operating systems. The text or instruction is only valid for 32-bit operating systems. The text or instruction is only valid for 64-bit operating systems. The text or the instruction applies only to the use or configuration of FIPS encryption. The text or instruction is used to describe the standard behavior or is only valid for standard configurations. The text or instruction applies only to the fix pack number shown in the graphic. Features or functional enhancements described in the text are not available until the specified fix pack has been installed. Note: Fix packs for the server component and the Web GUI component are released independently. Web GUI fix packs are indicated as follows: Administrator PureData Web GUI Fix Pack 1 The text or instruction applies only to Web GUI administrators. These are users who are assigned the roles "ncw_user" and "ncw_admin". C The text or the instruction is only valid for the programming language C. Java The text or the instruction is only valid for the programming language Java. Typeface Conventions This manual uses the following typeface conventions: bold italic type v lower case or mixed case commands that are difficult to distinguish from surrounding text. v Interface controls (check boxes, buttons, radio buttons, spin boxes, fields, folders, icons, list windows and associated entries, multi-column lists, containers, menu options and names, tabs, and feature pages) and notes (such as Tip: and Notes on the operating system :). v Keywords and parameters in the text. v Citations (such as book titles, CD and other media labels). v Words defined in the text (e.g. "... a leased line is also referred to as a point-to-point line."). v Highlighting of words and letters (words as examples: "Use the word that to introduce a restrictive clause."; Letters as examples: "The LUN address must begin with the letter L."). xii IBM Tivoli Netcool / OMNIbus: Web GUI Administration and User's Guide

15 v New terms introduced in the text (except in definition lists): "A view is a frame within the work area that contains data.". v Variables and values ​​that must be specified by the user: "... where my_name stands for ...". Monospaced font v code elements and other examples. v File names, programming keywords, and other elements that are difficult to distinguish from surrounding text. v Texts of messages and system requests intended for the user. v Text to be entered by the user. v Values ​​for arguments or command options. About this publication xiii

16 xiv IBM Tivoli Netcool / OMNIbus: Web GUI Administration and User's Guide

17 Chapter 1. Administering the Web GUI server Restarting the server Perform these tasks to administer the Web GUI server. After customization and configuration activities, you may need to restart the Web GUI server. About this task A server restart is required during or after the following actions on the Web GUI server: v Changes to any of the following files: server.init ncwdatasourcedefinitions.xml virtualhosts.xml deployment.xml security.xml winconfig.xml userdefaults .props property files in the jazzsm-was-profil / properties directory. v Setting up a load balancing cluster v Adding a node to a load balancing cluster v Adding or modifying user registries v Backing up and restoring the Web GUI v Copying configurations from another Web GUI server v Configuring encryption v Configuring single sign-on v Configuring LDAP or Active Directory and its connections If you do not use the scheduled tasks feature in the server.init file, you must also restart the server if files in the following directories in WEBGUI_HOME / etc have changed: v configstore v cgi-bin v charts v charts / definitions v templates and all subdirectories Procedure To restart the server: 1. Change to the jazzsm-was-profil / bin directory. 2. Stop the server: v Linux UNIX stopserver.sh server1 Copyright IBM Corp. 2001,

18 Attention: On Linux and UNIX systems, you will be prompted for the administrator username and password. v Windows stopserver.bat server1 Note: Provide the correct username for the operating system. 3. Wait a moment for the server to shut down completely and confirm that all Java processes have ended. This is especially important when installing a fix pack. The following messages confirm that the server has been shut down: ADMU3201I: Server stop request issued. Waiting for stop status. ADMU4000I: Server server1 stop completed. 4. Start the server: v Linux UNIX startserver.sh server1 v Windows startserver.bat server1 Related tasks: Set a trace on page 100 Enable a trace of the Jazz for Service Management application server server if you want to capture the activity. View the application server profile Open the application server profile to review port number mappings and other information. The application server profile is available as a text file on the computer on which it is installed. Procedure Open the jazzsm-was-profil / logs / aboutthisprofile.txt file. Example The following is an example of the profile for an installation in a Windows environment: Application server environment to create: Application server Location: C: \ Program Files \ IBM \ JazzSM \ profile Disk space required: 200 MB Profile name: JazzSM Profile Make this profile the default: True Node name: TIPNode Host name: tivoliadmin.usca.ibm.com Enable administrative security (recommended): True Administrative consoleport: Administrative console secure port: HTTP transport port: HTTPS transport port: Bootstrap port: SOAP connector port: Run application server as a service: False Create a Web server definition: False Performance tuning setting: Standard JazzSM_HOME \ profile Disk space required: 200 MB Profile name: JazzSM Profile Make this profile the default: True Node name: TIPNode Host name: tivoliadmin.usca.ibm.com 2 IBM Tivoli Netcool / OMNIbus: Web GUI Administration and User Guide

19 The following is an example of an installation profile in a Linux environment: Application server environment to create: Application server Location: / opt / ibm / jazzsm / profile Disk space required: 200 MB Profile name: JazzSMProfile Make this profile the default: True Node name: JazzSMNode01 Host name: OMNIbus-8.1.ibm.com Enable administrative security (recommended): True Administrative console port: Administrative console secure port: HTTP transport port: HTTPS transport port: Bootstrap port: SOAP connector port: Run application server as a service: False Create a Web server definition: False Performance tuning setting: Standard Next steps The complete list of the defined ports on the server can be found in the file JazzSM_HOME / var / JazzSMProfile_portDef.properties (see following example): # Mon Oct 06 09:26:30 PDT 2008 CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS = 16323 WC_adminhost = 16315 DCS_UNICAST_ADDRESS = 16318 BOOTSTRAP_ADDRESS = 16312 SAS_SSL_SERVERAU TH_LISTENER_ADDRESS = 16321 SOAP_CONNECTOR_ADDRESS = 16313 ORB_LISTENER_ADDRESS = 16320 WC_defaulthost_secure = 16311 CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS = 16322 WC_defaulthost = 16310 WC_adminhost_secure = 16316 IPC_CONNECTOR_ADDRESS = 16314 REST_NOTIFICATION_PORT = 16324 Related tasks: JazzSM profile logs for Logon View on page 97 Check in the event of a logon failure, the issue and the System error log to determine the cause. Port Mapping The Jazz for Service Management application server requires a number of consecutively numbered ports. The sequence of ports is provided in the response file during installation. The installer checks that the required number of ports (starting with the starting port value) are available before allocating them. If one of the ports is subsequently in use, the installation program will terminate the installation process and you will need to specify a different port range in the response file. Chapter 1. Administering the server 3

20 Changing the time-out setting You can set the length of time after which users are automatically logged out of the Web GUI; the default time-out is 30 minutes. Perform this task in a load balancing cluster on all nodes. Procedure v HTTP session timeout 1. Open the following file: jazzsm-was-profil / config / cells / JazzSMNode01Cell / applications / isc.ear / deployments / isc / deployment.xml 2. In this file, locate the following section: 3. Enter the desired period in minutes as the value for the invalidationtimeout attribute. For example, to set the timeout to 15 minutes, set the value as follows: invalidationtimeout = "15" 4. Save and close the file. 5. Check the timeout setting for the ISC.KEEPALIVE.INTERVAL property in the JazzSM_Home / config / cells / JazzSMNode01Cell / applications / isc.ear / deployments / isc / isclite.war / WEBINF / consoleProperties.xml file. This timeout setting should be less than the HTTP session timeout interval. 6. Check the timeout setting for the webtop.keepalive.interval property in the server.init file. This timeout setting should be less than the HTTP session timeout interval. 7. Restart the server. v LTPA timeout 1. Open the following file: jazzsm-was-profil / config / cells / JazzSMNode01Cell / security.xml 2. In this file, find the following section: 3. Enter the desired timeout interval in minutes as the value for the timeout attribute. 4. Save and close the file. 5. Restart the server. Related concepts: Using the Web GUI in a Load Balanced Environment on page 81 This section explains how to operate the Web GUI in a load balanced environment and how operating in such an environment affects the management and use of the product. Related tasks: 4 IBM Tivoli Netcool / OMNIbus: Web GUI Administration and User's Guide

21 Restart the server on page 1 After customization and configuration activities, you may need to restart the Web GUI server. Disabling the session timeout You can set the session timeout to a high value to prevent the session from timing out. This is useful when there are facilities such as wall displays that need to be continuously available. Perform this task in a load balancing cluster on all nodes. About this task The timeout setting cannot be completely disabled. However, you can set the value for this function so high that the function is no longer triggered in practice. Before you implement this procedure, be aware of the following security and system resource implications: v Consider that security may be compromised if unsupervised sessions cannot time out. v Resource usage can increase if users close their browsers without logging out. Restart the server to free these resources. Procedure Follow the procedure in Change the time-out setting to set the time-out to the following values: Table 2. Attribute values ​​to turn off the session time-out File Attribute Value deployment.xml invalidationtimeout -1 security.xml timeout or with LTPAFIX disabled. (To set the LTPA setting timeout to, the LTPAFIX property in the JazzSM_HOME / profile / config / cells / JazzSMNode01Cell / applications / isc.ear / deployments / isc / isclite.war / WEB-INF / consoleproperties.xml file must be false Related Concepts: The Web GUI in a Load Balanced Environment on page 81 This section explains how to operate the Web GUI in a load balanced environment and how operating in such an environment affects the management and use of the product affects. Related tasks: Restarting the server on page 1 After customization and configuration activities, you might need to restart the Web GUI server. Chapter 1. Administering the server 5

22 Defining the ObjectServer as a user repository With the script confvmm4ncos for reconfiguring the VMM (Virtual Member Manager) component, you can add an ObjectServer to the realm as a user repository. Before you begin v Have the following information about the ObjectServer ready: Username Password IP address Port number If the previous user repository was the default file-based repository, remove any default users that were created when the file-based repository was added. These users must be removed to avoid duplicate users in the realm's repositories. v If you have a second ObjectServer, get the same information about that ObjectServer. About this task The script has the following directory requirements: v The WebSphere Application Server installation directory is the parent directory. v JazzSM_Home is the profile. v JazzSMNode01Cell is the cell. Procedure 1. Go to the WAS_HOME / bin directory and enter the following command: confvmm4ncos profiledir user password address port [address2 port2] where: v v v v v v profiledir is the profile directory of Jazz for Service Management. Example: / opt / ibm / jazzsm / profile. user is the ID of a user with administrator rights for this ObjectServer. password is the password for the user ID. address is the IP address of the ObjectServer. port is the port number used by the ObjectServer. If a failover ObjectServer is used, address2 and port2 are the IP address and port number of this ObjectServer. Tip: Run confvmm4ncos with no command line options for help for the command, including examples of how to use the command. 2. Restart the server. 3. Repeat the steps on each web GUI host. 6 IBM Tivoli Netcool / OMNIbus: Web GUI Administration and User's Guide

23 Results The VMM component is configured for the ObjectServer and the ObjectServer is added to the realm as a user repository. The file jazzsm-was-profil / config / cells / jazzsmnode01cell / wim / config / wimconfig.xml now contains the element for the ObjectServer. Tip: In the wimconfig.xml file, find the entry element, enter the new password as the value for the password attribute. c. Save and close the file. 2. Go to the WAS_HOME / bin directory and enter the following command: confvmm4ncos profiledir user password address port [address2 port2] where: v v v v v profiledir is the profile directory of Jazz for Service Management. Example: / opt / ibm / jazzsm / profile. user is the ID of a user with administrator rights for this ObjectServer. password is the password for the user ID. address is the IP address of the ObjectServer. port is the port number used by the ObjectServer. Chapter 1. Administering the server 7

24 v If a failover ObjectServer is used, address2 and port2 are the IP address and port number of this ObjectServer. Tip: Run confvmm4ncos with no command line options for help for the command, including examples of how to use the command. 3. Restart the server. Related tasks: Restarting the server on page 1 After customization and configuration activities, you might need to restart the Web GUI server. Managing time-controlled tasks Time-controlled tasks are an essential requirement so that the Web GUI server can automatically load changes to the configuration data without restarting the server. Scheduled tasks are managed using properties in the Web GUI initialization file (server.init). About this task To manage the scheduled task feature, do the following: Procedure 1. Open the WEBGUI_HOME / etc / server.init file in a text editor. 2. Perform a combination of the following tasks, as needed: v v Control the use of scheduled tasks Set update properties 3. Save the file. 4. If you enabled scheduled tasks in step 2, restart the Dashboard Application Services Hub server. Related tasks: Restarting the server on page 1 After customization and configuration activities, you might need to restart the Web GUI server. Related reference: Load balancing best practices on page 81 To manage the Web GUI in a load balancing environment, follow these best practices to avoid cluster problems. Controlling the use of scheduled tasks Procedure 1. Locate the timedtasks.enabled property. 2. Define the value of the property as required: Value false true Meaning Deactivates the function for time-controlled tasks. Activates the function for scheduled tasks. This setting is required for the automatic processing of configuration data changes. 8 IBM Tivoli Netcool / OMNIbus: Web GUI Administration and User's Guide

25 Specifying update characteristics About this task In most cases, the specified values ​​will be sufficient. You can use this procedure to change these values ​​if necessary. Procedure 1. Set values ​​(in seconds) for the following properties: v v Start delay execution time 2. Locate the timedtasks.default.startdelay property and provide the required value for the start delay. 3. Locate the timedtasks.default.runperiod property and provide the required value for the run time. Scheduled Tasks Overview Scheduled tasks make it easy to manage a Web GUI server or a cluster of Web GUI servers. Time-controlled tasks enable a Web GUI server to recognize and load changes to the configuration data. The tasks implement changes in the configuration without restarting the server. This is especially important in a load balancing cluster where the service must be provided to users in a non-disruptive manner. What are scheduled tasks? Scheduled tasks are a group of batch processes that periodically check the configuration files for changes. If one of these files has been changed since the last execution, the processes load the new configuration data into the Web GUI server. Characteristics of a scheduled task A scheduled task has the following characteristics: v Start delay The start delay specifies the number of seconds after the server starts to look for changes in the associated configuration data for the first time. v Execution Time The execution time is the number of seconds that elapse between successive executions of the task. The start delay and the execution time together form the schedule of the time-controlled task. In a load balancing cluster, it is recommended that all cluster members use the same schedule. Scheduled Task Definition The Web GUI configuration file contains the definition of scheduled tasks. The path for this file is WEBGUI_HOME / etc / server.init. The definition of the time-controlled tasks is as follows: Chapter 1. Administering the server 9

26 timedtasks.default.startdelay: 120 timedtasks.default.runperiod: 60 Query event database This specifies a start delay of 2 minutes and an execution time of two minutes. You can run all ObjectServer SQL commands and query ObjectServer data. Before you begin To perform this task, you must meet the following requirements: v The ncw_admin role must be associated with your Web GUI user profile. v You must be a user on the ObjectServer and your user ID must be a member of the ISQL and ISQLWrite groups. Note: If authentication is performed using LDAP and the users.credentials.sync feature of the server.init file is activated, LDAP users are automatically synchronized with the ObjectServer. Otherwise a user must be created in the ObjectServer and assigned to the groups. v The webtop_compatibility trigger automation must have been run on the ObjectServer. This is a time-controlled trigger. This trigger is enabled by default. Tip: You can reduce the trigger frequency from the default (60 minutes). For more information on configuring temporary triggers, see the IBM Tivoli Netcool / OMNIbus Administration Guide. v The Web GUI configuration cache must be synchronized with the ObjectServer. The cache can be synchronized using the WEBGUI_HOME / bin / webtop_osresync script. About this task The Web GUI event database query behaves like the Tivoli Netcool / OMNIbus SQL interactive interface and can be used to perform tasks such as creating a new database table or stopping the ObjectServer. You can establish ObjectServer connections and interact with and control the ObjectServer using SQL commands. Attention: Use caution when using the Event Database Query window. Any command entered will be executed for the ObjectServer. Improper use of SQL commands can cause irreparable damage to the database. To send SQL statements to the ObjectServer: Procedure 1. Click Administration> Event Management Tools> Event Database Query. 2. In the Select data source list, select the data source on which you want to run the command. 10 IBM Tivoli Netcool / OMNIbus: Web GUI Administration and User's Guide

27 3. Enter an SQL query in the text editor and click Submit. The result of the SQL query is displayed in the Results Displayed Below area. Example of an SQL query The following example result shows an excerpt of the data that were returned after the following query was submitted: select Node, Summary from alerts.status where Severity = 4; select Node, Summary from alerts.status where Severity => Executed select Node, Summary from alerts.status where Severity = 4; Tokyo Diskspace alert sl-server2.ibm.com A process running on sl-server2.ibm.com has connected as username bertha sl-server2.ibm.com A process running on sl-server2.ibm.com has connected as username bertha London Machine has gone offline sl-server2.ibm.com A process running on sl-server2.ibm.com has connected as username herbert sl-server2.ibm.com A process running on sl-server2.ibm.com has connected as username bertha sl-server2.ibm.com A process running on sl-server2.ibm.com has connected as username filter sl-server2.ibm.com A process running on sl-server2.ibm.com has connected as username root Shanghai Link Down on port sl-server2.ibm.com A process running on sl-server2.ibm.com has connected as username bertha For more information on ObjectServer SQL syntax, see the IBM Tivoli Netcool / OMNIbus Administration Guide in the ObjectServer SQL chapter . Copying Data Between Web GUI Servers The Web GUI has a utility for copying selected data from one server to another. Overview Occasionally it will be necessary to copy data from one Web GUI server to another. An example of this is copying data from a test server to a production server. The web GUI provides a utility for such cases. The server on which the data to be copied resides is the source server; and the server to which data is copied is the destination server. Each of these servers can be a stand-alone system or part of a load balancing cluster. Copying process Copying data between servers is carried out as follows: 1. Define which data should be exported from the source server. 2. Export the data from the source server. The utility writes the selected data to a .zip file. 3. Copy the file to the destination server. Chapter 1. Administering the Server 11

28 4. Set up the utility to import data from the .zip file. In this step you can define whether all data should be imported from the file or only selected data elements. 5. Import the data from the .zip file. 6. Reboot the target server, if necessary. Tip: In many cases, you do not need to restart the server if your system uses scheduled tasks. What items can be copied between servers? The following items can be copied between servers: v Filters v Maps v Menus v Prompts v Relationships v Tools v Views v Any customized files or directories in WEBGUI_HOME or in jazzsm-was-profil / installedapps / jazzsmnode01cell / isc.ear / OMNIbusWebGUI.war Note: Unadjusted files or directories should not be copied between servers. Always back up your files and directories before copying them between servers. You can also specify files and directories that should not be copied between servers. For example the Web GUI configuration file (server.init). Some elements (such as maps) have dependent elements that define their behavior. When exporting such an element, the utility includes all dependent elements. This makes it easier to move complex elements from one web GUI server to another. Cloning data between servers Occasionally, you may need to copy all of the Web GUI and Dashboard Application Services Hub data from one server to another. This process is known as cloning and is useful for moving a configuration from a test environment to a production environment. Cloning is basically the same as copying, but with the difference that the elements to be exported and imported do not have to be defined. Rather, the utility provides a file that defines all of the required elements. You specify this file when you export and import data. This simplifies the cloning process and reduces the risk that important data may not be copied. Note: The ncwdatasourcedefinitions.xml file is excluded from the cloning process. 12 IBM Tivoli Netcool / OMNIbus: Web GUI Administration and User's Guide

29 Exporting data from a Web GUI server First, export the required data from the source server. Define the elements to be exported Define the elements to be exported and the position for the .zip file. Procedure 1. Make sure you are logged in as an administrative user. 2. Navigate to the directory that contains the utility properties file: cd WEBGUI_HOME / integration / importexport_tool / etc 3. Define the items that you want to export from the source server by editing the OMNIbusWebGUI_settings.properties file: Many of the property definitions consist of a Element list. Separate the individual elements in these lists with a comma. On Windows systems, add two backslashes as separators for properties that specify file paths. Example: C: \ IBM \ tivoli \ netcool \ omnibus_webgui. Set the following characteristics as needed. First remove the comment character at the beginning of the line and change the value as required. So that a certain element is not exported, leave the comment characters at the beginning of the line. In some cases, the utility uses a default value for missing features. Table 3. Set properties to define data to be exported Property JazzSM.home JazzSM.cell.name product.home Value The full path to a JazzSM home directory. Cell name of the server to be imported or exported. The installation directory of the Web GUI. Define this characteristic if you did not install the product in the default location. The default installation location is one of the following directories: UNIX Linux ibm / tivoli / netcool / omnibus_webgui output.dir Windows C: \ IBM \ tivoli \ netcool \ omnibus_webgui The full path of the destination directory for the exported data. The default is JazzSM_HOME / ui / output. Chapter 1. Administering the server 13

30 Table 3. Specifying the characteristics to define the data to be exported (continued) Characteristic ExportWebGUIPlugin.input Value To export data from the OMNIbusWebGUI.war file, remove the comment symbol in front of the definition of the characteristic ExportWebGUIPlugin.input and add a comment symbol in front of the item for the Web GUI folder. ExportWebGUIPlugin.ignore ExportPromptPlugin.input ExportToolPlugin.input ExportMenuPlugin.input ExportMenuConfigPlugin.input ExportViewPlugin.global ExportViewPlugin.system ExportViewPlugin.user Add further files and directories to be exported in the property definition. Enter the directory and the file path in relation to the WEBGUI_HOME. Specify the files and directories to be excluded from the data export. Separate the individual file or directory paths with a comma. Enter the directory and the file path in relation to the WEBGUI_HOME. A list of export prompt names (without extensions). A list of the names of the tools to be exported (without extensions). A list of the names of the menus to be exported (without extensions). A list of the names of the menu configurations to be exported (without extensions). A list with the names of the global views to be exported (without extensions). If you want to export all global views, enter the forward slash (/) as the value for this property. A list with the names of the system views to be exported (without extensions). If you want to export all system views, enter the forward slash (/) as the value for this characteristic. A list of the names of the custom views to be exported (without extensions). For each view, enter the user ID and the view name, separated by a comma. For example, use a definition like the following to specify View1 and View2 for user ID User1 and View3 for user ID User2: ExportViewPlugin.user = User1, View1, User1, View2, User2, View3 ExportFilterPlugin.global if you all If you want to export user views, enter the forward slash (/) as the value for this characteristic. A list of the names of the global filters to be exported (without extensions). If you want to export all global filters, enter the forward slash (/) as the value for this property. 14 IBM Tivoli Netcool / OMNIbus: Web GUI Administration and User's Guide

31 Table 3. Specifying properties to define the data to be exported (cont.) Property ExportFilterPlugin.system ExportFilterPlugin.groups Value A list of the names of the system filters to be exported (without extensions). If you want to export all system filters, enter the forward slash (/) as the value for this property. A list with the names of the group filters to be exported (without extensions). For each filter, enter the group ID and the filter name separated by a comma. For example, use a definition like the following to specify GroupFilter1 for group ID Group1 and GroupFilter2 and GroupFilter3 for group ID: ExportFilterPlugin.groups = Group1, GroupFilter1, Group2, GroupFilter2, Group2, GroupFilter3 ExportFilterPlugin.user if you have any group filters export, enter the forward slash (/) as the value for this characteristic. A list of the names of the custom filters to be exported (without extensions). For each filter, enter the user ID and the filter name, separated by a comma. For example, use a definition like the following to specify Filter1 and Filter2 for user ID User1 and Filter3 for user ID User2: ExportFilterPlugin.user = User1, Filter1, User1, Filter2, User2, Filter3 ExportFilterCollectionPlugin. input ExportMapPlugin.input ExportRelationshipPlugin.input If you want to export all user filters, enter the forward slash (/) as the value for this property. A list of the names of the filter collections to be exported (without extensions). The utility includes all associated objects for the individual object groups. These include, for example, filters, dependency filters, and views.A list of the names of the maps to be exported (without extensions). The utility includes all associated objects for the individual maps. This includes, for example, map resources, filters, dependency filters and views. A list of the names of the relationships to be exported (without extensions). Chapter 1. Administering the server 15

32 Exporting data Exporting the defined data to a .zip file on the source server. Before you begin The source and target systems should have the same version and fix pack level. Procedure 1. Make sure that you are logged on to the source server as an administrative user and that Dashboard Application Services Hub is running. 2. The utility as provided writes information, warnings, and error messages to the log file. Change the log level if necessary. Note: Recommended values ​​are FINE, FINER, and FINEST. Each of these stages causes an increase in the number of messages. This can be useful in diagnosing a problem in the export utility. However, after using either of these values, make sure to return to the original value before resuming normal server operations. 3. Navigate to the directory that contains the utility: JazzSM_HOME / ui / bin. 4. Enter one of the following commands to export the data: UNIX Linux./consolecli.sh Export --username smadmin --password password --excludeplugins ExportPagePlugin, ChartExportPlugin --settingfile WEBGUI_HOME / integration / importexport_tool / etc / OMNIbusWebGUI_settings .properties Windows consolecli.bat Export --username smadmin --password password --excludeplugins ExportPagePlugin, ChartExportPlugin --settingfile WEBGUI_HOME \ integration \ importexport_tool \ etc \ OMNIbusWebGUI_settings.properties Replace the name of the dashboard with the name of the dashboard. smadmin -User with administrative tasks. password with the password for the Dashboard Application Services Hub administrative user. To exclude certain plug-ins from the export, add the names of these plug-ins to the qualifier --excludeplugins and separate the individual names with a comma. For example, enter the following to exclude the prompt plug-in: --excludeplugins ExportPagePlugin, ChartExportPlugin, ExportPromptPlugin Make sure to include the 'ExportPagePlugin' and 'ChartExportPlugin' plug-ins in the list. Note: Enter the following command to get a list of the names of the plug-ins that can be excluded from the export operation: ./ consolecli.sh ListExportPlugins. 16 IBM Tivoli Netcool / OMNIbus: Web GUI Administration and User's Guide

33 Results The utility creates the following files: v The data file in data.zip in the directory specified by the output.dir property in OMNIbusWebGUI_settings.properties. If this property is not specified, the file is located in the JazzSM_HOME / ui / output directory. v A log file in JazzSM_HOME / ui / logs / consolecli.log. Related tasks: Setting the log level for the utility on page 23 As it is provided, the utility writes informational messages to the log file in addition to warnings and errors. You can use this procedure to adjust the log level in export and import operations. Verify that the export is complete Before copying the .zip file to the destination server, make sure that it contains all the required directories, files, and Web GUI objects. Procedure 1. Open the log file in JazzSM_HOME / ui / logs / consolecli.log and ensure that all phases of the export process have completed successfully. Correct the errors, if any, and retry the export activity before continuing. For example, correct incorrect names and paths in the OMNIbusWebGUI_settings.properties file, retry the export operation, and then ensure that the errors have been resolved. 2. Navigate to the output directory and open the data.zip file with a suitable file compression tool. 3. Make sure the file contains all of the files, directories, and Web GUI objects that you want to export. If not all items are included, edit the OMNIbusWebGUI_settings.properties file to add the missing items. Then repeat the export operation and make sure that all elements are now present. 4. Close the data.zip file. Importing data into a Web GUI server In the second step, import the data into the target server. Define the items to be imported Copy the exported file to the destination server, install the utility (if necessary), and define the items to be imported from the file. Procedure 1. Copy the data.zip file from the source server to the JazzSM_HOME / ui / input directory on the destination server. 2. Make sure the target server is running and log in as an administrative user. 3. Change to the directory containing the utility properties file: WEBGUI_HOME / integration / importexport_tool / etc. Chapter 1. Administering the server 17

34 4. Define the elements that you want to import from the data.zip file by editing the OMNIbusWebGUI_settings.properties file: v v To define a property, uncomment the beginning of the relevant line and enter an appropriate value. Many of the feature definitions consist of a list of elements. Separate the list items with commas (,). v Windows Use two backslashes as separators for properties that indicate file paths. Example: C: \ IBM \ tivoli \ netcool \ omnibus_webgui. v The properties listed in the following table control the behavior of the utility. Set these characteristics as needed. Table 4. Specifying Properties to Define the Data to Import Property JazzSM.home JazzSM.cell.name product.home Value The full path to a JazzSM home directory. Cell name of the server to be imported or exported. The installation directory of the Web GUI. Define this characteristic if you did not install the product in the default location. The default installation location is one of the following directories: UNIX Linux / opt / ibm / tivoli / netcool / omnibus_webgui output.dir import.importfile import.backupdir Windows C: \ IBM \ tivoli \ netcool \ omnibus_webgui Directory in which the content of the data. zip is extracted. If you do not define this property, the contents of the data.zip file will be extracted to JazzSM_HOME / ui / output / data.zip. The full path of the data.zip file. If you do not define this property, the utility expects this file at JazzSM_HOME / ui / input / data.zip. The full path of the directory where the utility will save backup copies of the imported files. Specify a directory other than output.dir, although you can specify a subdirectory in output.dir. If you do not set this property, the utility uses the jazzsm-was-profil / ui / backups directory. Related tasks: Managing scheduled tasks on page 8 Scheduling tasks are essential for the Web GUI server to automatically load changes to configuration data without restarting the server. Scheduled tasks are managed using properties in the Web GUI initialization file (server.init). 18 IBM Tivoli Netcool / OMNIbus: Web GUI Administration and User's Guide

35 Importing data Importing the data from the .zip file into the target server. Preparatory steps 1. Back up the installation of the Web GUI and the installation of the Dashboard Application Services Hub to prevent loss of information in the event of an incident and to be able to take recovery measures. 2. Copy the data.zip file from the source server to the JazzSM_HOME / ui / input directory on the destination server. Procedure To import the data from the .zip file into the target server: 1. The utility as provided writes information, warnings and error messages to the log file. Change the log level if necessary. Note: Recommended values ​​are FINE, FINER, and FINEST. Each of these stages causes an increase in the number of messages. This can be useful in diagnosing a problem in the import utility. However, after using any of these values, make sure to return to the original value before resuming normal server operations. 2. Navigate to the directory that contains the utility: JazzSM_HOME / ui / bin. 3. Enter one of the following commands to import the data: UNIX Linux./consolecli.sh Import --username smadmin --password password --excludeplugins ImportPagePlugin, ChartImportPlugin --settingfile WEBGUI_HOME / integration / importexport_tool / etc / OMNIbusWebGUI_settings .properties Windows consolecli.bat Import --username smadmin --password password --excludeplugins ImportPagePlugin, ChartImportPlugin --settingfile WEBGUI_HOME \ integration \ importexport_tool \ etc \ OMNIbusWebGUI_settings.properties Replace the following information with the name of the dashboard -User with administrative tasks. password with the password for the Dashboard Application Services Hub administrative user. To exclude certain plug-ins from the import, add the names of these plug-ins to the qualifier --excludeplugins and separate the individual names with a comma. For example, specify the following to exclude the prompt plug-in: --excludeplugins ImportPagePlugin, ChartImportPlugin, ImportPromptPlugin Make sure to include the ImportPagePlugin and ChartImportPlugin plug-ins in the list. Note: Enter the following command to get a list of the names of the plug-ins that can be excluded from the import operation: ./ consolecli.sh ListImportPlugins. Chapter 1. Administering the Server 19

36 4. Reboot the Dashboard Application Services Hub server. The server must be restarted if your site does not use scheduled tasks or if you have imported an important system file such as server.init or ncwdatasourcedefinitions.xml. Related tasks: Setting the log level for the utility on page 23 As it is provided, the utility writes informational messages to the log file in addition to warnings and errors. You can use this procedure to adjust the log level in export and import operations. Restart the server on page 1 After customization and configuration activities, you may need to restart the Web GUI server. Check that the import is complete Check the log file to see whether the import was completed successfully, whether all the necessary files are present and whether the imported functions are available in the Web GUI. Procedure 1. Open the log file in JazzSM_HOME / ui / logs / consolecli.log and ensure that all phases of the import process have completed successfully. Correct the errors, if any, and retry the import activity before continuing. For example, correct incorrect names and paths in the OMNIbusWebGUI_settings.properties file, retry the import operation, and then ensure that the errors have been resolved. 2. Verify that all required files, directories, and Web GUI objects exist on the target servers. 3. Check whether all functions are available in the web GUI. For example, check that all imported filters are available. 4. In a load balancing cluster, verify that all files, directories, and Web GUI objects have been replicated to all nodes in the cluster. 5. If the system is not part of a cluster and is not using scheduled tasks, restart the server. Cloning data between servers You can clone data (including or only Dashboard Application Services Hub data) between servers running the Web GUI. All servers must be running the same version of the Web GUI and the same version of Dashboard Application Services Hub. You cannot clone data between servers running different versions of the Web GUI and Dashboard Application Services Hub. Limitation: The ncwdatasourcedefinitions.xml file cannot be cloned. Adjust this file manually after importing cloned data into a server. Before you begin Ensure that all available fix packs for the Web GUI and Dashboard Application Services Hub have been applied. 20 IBM Tivoli Netcool / OMNIbus: Web GUI Administration and User's Guide

37 Exporting data Export all Web GUI data with or without Dashboard Application Services Hub data to a .zip file on the source server. Related tasks: Setting the log level for the utility on page 23 As it is provided, the utility writes informational messages to the log file in addition to warnings and errors. You can use this procedure to adjust the log level in export and import operations. To export Web GUI and Dashboard Application Services Hub data: Procedure 1. Ensure that you are logged in as an administrative user and that the Dashboard Application Services Hub server is running. 2. The utility as provided writes information, warnings, and error messages to the log file. Change the log level if necessary. 3. If your Web GUI installation is not in the default location, do the following: a. Navigate to the WEBGUI_HOME / integration / plugins directory. b. Edit the OMNIbusWebGUI_clone_settings.properties file. c. Find the following line: JazzSM.cell.name = d. Add the following line after this line: product.home = webgui_home Replace WEBGUI_HOME with the actual installation directory of the web GUI. Note: The default installation directory for the Web GUI is one of the following: UNIX Linux ibm / tivoli / netcool / omnibus_webgui Windows C: \ IBM \ tivoli \ netcool \ omnibus_webgui 4. Navigate to the directory that contains the utility: JazzSM_HOME / ui / am. 5. Enter one of the following commands to export the data: UNIX Linux./consolecli.sh Export --username smadmin --password password --settingfile WEBGUI_HOME / integration / plugins / OMNIbusWebGUI_DASH_clone.properties Windows consolecli.bat Export - -username smadmin --password password --settingfile WEBGUI_HOME \ integration \ plugins \ OMNIbusWebGUI_DASH_clone.properties Replace smadmin and password with the username and password of the Dashboard Application Services Hub administrative user. Results The utility creates the following files: v The data file in data.zip in the JazzSM_HOME / ui / output directory. v A log file in JazzSM_HOME / ui / logs / consolecli.log. Chapter 1. Administering the Server 21

38 To export web GUI data only: Procedure 1. Make sure you are logged in as an administrative user and that the Dashboard Application Services Hub server is running. 2. The utility as provided writes information, warnings, and error messages to the log file. Change the log level if necessary. 3. If your Web GUI installation is not in the default location, do the following: a. Navigate to the WEBGUI_HOME / integration / plugins directory. b. Edit the OMNIbusWebGUI_clone_settings.properties file. c. Find the following line: JazzSM.cell.name = d. Add the following line after this line: product.home = webgui_home Replace WEBGUI_HOME with the actual installation directory of the web GUI. Note: The default installation directory for the Web GUI is one of the following: UNIX Linux ibm / tivoli / netcool / omnibus_webgui Windows C: \ IBM \ tivoli \ netcool \ omnibus_webgui 4. Navigate to the directory that contains the utility: JazzSM_HOME / ui / am. 5. Enter one of the following commands to export the data: UNIX Linux./consolecli.sh Export --username smadmin --password password --excludeplugins ExportPagePlugin, ChartExportPlugin --settingfile WEBGUI_HOME / integration / plugins / OMNIbusWebGUI_clone_settings Windows consolecli .bat Export --username smadmin --password password --excludeplugins ExportpagePlugin, ChartExportPlugin --settingfile WEBGUI_HOME \ integration \ plugins \ OMNIbusWebGUI_clone_settings Replace smadmin and password with the username and password of the administrative user from Dashboard Application Services Hub. Results The utility creates the following files: v The data file in data.zip in the JazzSM_HOME / ui / output directory. v A log file in JazzSM_HOME / ui / logs / consolecli.log. 22 IBM Tivoli Netcool / OMNIbus: Web GUI Administration and User's Guide

39 Importing data Importing the data from the .zip file into the target server. Related tasks: Setting the log level for the utility on page 23 As it is provided, the utility writes informational messages to the log file in addition to warnings and errors. You can use this procedure to adjust the log level in export and import operations. Restart the server on page 1 After customization and configuration activities, you may need to restart the Web GUI server. Importing Web GUI and Dashboard Application Services Hub Data: Before You Begin Back up the Web GUI installation and Dashboard Application Services Hub installation to prevent loss of information in the event of an incident and to be able to take recovery measures. Procedure 1. Copy the data.zip file from the source server to the JazzSM_HOME / ui / input directory on the destination server. 2.Make sure that you are logged in to the target server as an administrative user and that the Dashboard Application Services Hub server is running. 3. The utility as provided writes information, warnings, and error messages to the log file. Change the log level if necessary. 4. If your Web GUI installation is not in the default location, do the following: a. Navigate to the WEBGUI_HOME / integration / plugins directory. b. Edit the OMNIbusWebGUI_clone_settings.properties file. c. Find the following line: JazzSM.cell.name = d. Add the following line after this line: product.home = webgui_home Replace WEBGUI_HOME with the actual installation directory of the web GUI. Note: The default installation directory for the Web GUI is one of the following: UNIX Linux ibm / tivoli / netcool / omnibus_webgui Windows C: \ IBM \ tivoli \ netcool \ omnibus_webgui 5. Navigate to the directory that contains the utility: JazzSM_HOME / ui / am. 6. Enter one of the following commands to import the data: UNIX Linux./consolecli.sh Import --username smadmin --password password --settingfile WEBGUI_HOME / integration / plugins / OMNIbusWebGUI_DASH_clone.properties Chapter 1. Administering the server 23

40