Installing a monitor model using wsadmin in interactive mode

Use the interactive scripting method for installation of the EAR file using the installation wizard.

1. Open a command prompt, and change directories to the following directory: Monitor_Profile_Home/bin
2. Type wsadmin to launch the wsadmin scripting client. If security is enabled, use the following command: wsadmin -user user_ID -password password
   where:

   • user_ID is the user ID for a WebSphere Application Server administrator
   • password is the password for user_ID
3. Install the EAR file by typing the following command: $AdminApp installInteractive path_to_Monitor_ear_file
   The installation wizard consists of many steps. However, there are four tasks, near the end of the installation procedure, that are specific to a monitor EAR file. Change the options specified in these steps as appropriate:

   Specify Monitor Model database options

   Specify information about database scripts, model runtime options, KPI merge, and business situations merge.

   • Run scripts to create the schema (yes/no; the default is yes)
   • Run scripts to enable Data Movement Services (yes/no; the default is no)
   • Run scripts to delete the schema during uninstallation (yes/no; the default is no)
   • Processing strategy (the default is based on monitor model capabilities as documented in the monitor EAR file)
   • Enable event reordering (yes/no; the default is based on monitor model capabilities as documented in the monitor EAR file)
   • Enable KPI merge from previous version (yes/no; the default is yes)
   • Enable business situations merge from previous version (yes/no; the default is yes)
   • Is profile migration in progress? (yes/no; the default is no and should not be changed)
   • First field reserved for use by automatically generated models (the default is no and should not be changed)
   • Second field reserved for use by automatically generated models (the default is no and should not be changed)
   • Field reserved for use by custom models (the default is no and should not be changed)
   • Generate Dashboard during monitor model installation (yes/no; the default is yes if the server is in development mode, no if the server is not in development mode)
   • User to add for Business Space dashboard (the user name; defaults to the current user)
   • Name of Business Space dashboard (name for the dashboard; defaults to the model name and version)

   Specify Monitor model Cognos options

   Specify whether to create Cognos cubes.

   • Publish Cognos cube package (yes/no; default is yes)

   Specify Monitor Model Security options

   If application security is enabled, installed monitor models are not available unless monitor data security is configured correctly. Specify information about the resource group for the monitor model.

   • Create Resource Group (existing/creating; the default is existing)
   • Data Security resource group name (the name of the resource group; the default is root)
   • Resource Group Description (use when creating a new resource group)
   • User name (the user name to be assigned to a role; no default)
   • User role (the role for the user name; no default)

   Specify Monitor Model CEI options

   Specify information about CEI configuration.

   • Server location (local/remote; the default is local)
   • Host name (this prompt is ignored if location is local; no default)
   • RMI port (this prompt is ignored if location is local; no default)
   • Security (enabled/disabled; the default is disabled; this prompt is ignored if location is local)
   • User ID (this prompt is ignored if security is disabled; no default)
   • Password (this prompt is ignored if security is disabled; no default)
   • Event group profile list name (no default)
   • Cell (no default)
   • Node (no default)
   • Server (no default)
   • Cluster (no default)
   • Distribution mode (active/activeBest/activeBypass/activeScalable/inactive; the default is activeBest)

   If the first part of the deployment process was successful, you then see a list of messages. Verify that the following messages are in the list:

   • CWMLC0253I: Model [model_name] version [version_number] registration complete.
   • Several messages that begin with CWMRT600*
   • ADMA5011I: The cleanup of the temp directory for application model_application_name is complete.
   • ADMA5013I: Application model_application_name installed successfully.
4. After you have received all of the messages indicating that the deployment succeeded, type this command at the wsadmin prompt: $AdminConfig save. At this point, the last part of the deployment process occurs.
5. To close the wsadmin prompt, type exit.
6. Optional: If you are working in a secured environment, see the related task for an additional task you must perform to complete the installation of this model.