NetIQ AppManager 7.0.x
NetIQ AppManager Operator Console
What are the Operator Console command line options to customize the layout?
What are theÂ command line options to customize the layout of the AppManager Operator Console?
One reason the Operator Console may be slow to load is the volume of objects that are beingloaded may require a large amount of the console to be loaded into memory. You can improve the load time of the Operator Console by reducing the items being loaded when the console starts up. To do so, lauch the Operator Console from a command line, using some of teh available arguements to reduce the number and types of items being displayed.
To view all command line options for the AppManager Operator Console, use the /? option at a command prompt.
C:\> NetIQ.exe /?
Use command parameters to start and customize the layout of the Operator Console.
C:\> NetIQ.exe [arguments...]
C:\> Netiq.exe /N myuser /P password /S server /R qdb /SHOWMASTERVIEW /HIDEJOBS
Type this parameter to validate the user based on the Windows NT user information.
- /S <server>
Type the Windows NT name of the server where the AppManager repository you want to work with is installed.
- /N <name>
Type the user name of the SQL Server login account used to access the AppManager repository. This parameter is ignored when the /TRUST parameter is specified.
- /P <password>
Type the password for the SQL Server login account. This parameter is ignored when the /TRUST parameter is specified.
Shows the Master view and splits the TreeView pane.
Shows event information in the List pane (and hides all other tabs and panes, including the TreeView pane).
Shows all tabs in the List pane. Previously dimmed panes can be shown.
Dims the Events tab in the List pane and event-related menu commands.
Dims the Jobs tab in the List pane and job-related menu commands.
Dims the Details tab in the List pane.
Dims the Graph Data tab in the List pane and graph data-related commands.
Please note that other common reason for the AppManager Operator Console to be extremely slow to load can include:
- Out-of-date NetIQ.exe. The Operator Console has had several performance enhancements and bug fixes since teh release of AM 6.0. It is always adviseable to make sure that your Operator Console executable (NetIQ.exe) is as up-to-date as possible. The most recent version of the Operator Console can be found on the AppManager Hotfixes page for both AppManager 6.0.x and AppManager 7.0.x, located here .
- Too many visible Events. In some environments, customers may allow Events to pile up without either acknowledging or Closing them. Depending on your Event retention settings, these Events may remain in the Operator Console for weeks, months, or even years. The more Events there are to display, the more contiguous memory the Operator Console needs in order to load these Events into the Event View of the Operator Console. If you have in excess of 50,000 open Events, this may be the primary reason your Operator Console is very slow to load. Contact NetIQ Technical Support for assistance.
- Too many discovered objects. In some environment, customers may have hundreds if not thousands or tens of thousands of objects discovered which they may not want nor need to monitor with AppManager. One example of these types of objects would be Printers. If these objects are not being monitored, they can be deleted from the Object Tree View pane in the Operator Console, to reduce the amount of contiguous memory needed to load the Operator Console. Note that re-discovering the Servers that hosted those objects will cause those objects to be re-added to the Object Tree View pane.
- Running the Operator Console from a shared system, to which multiple users are tied to and also running a copy of the Operator Console. The Operator Consoel is a light weight application, designed to run on a user's desktop. However, if the need exists to run the Operator Consoel from a remote system that multiple users are sharing, it may help for individual users to close the Operator Console when it is not in use (for example, at the end of a shift), to free up resources for other users sharing that system.
If you find that your Operator Console is still being very slow to load after reviewing and applying the applicable changes listed within this article, please contact NetIQ Technical Support.