IBM BPM, V8.0.1, All platforms > Reference > Business Process Management messages > Business Monitor messages

CWMTC

CWMTC messages are topology configuration and administration messages.

• CWMTC0101E
  0: The specified cluster named '' 1'' does not exist.
• CWMTC0102E
  0: The specified node named '' 1'' does not exist.
• CWMTC0103E
  0: The specified server named '' 1'' does not exist on node '' 2''.
• CWMTC0104E
  To specify where to deploy the messaging engine for the event service bus, you must specify either a cluster, or both a server and a node.
• CWMTC0105E
  

  You cannot specify both the - 0 and - 1 parameters.

• CWMTC0106E
  

  You cannot specify the - 0 parameter when deploying a messaging engine to a cluster.

• CWMTC0107E
  The - 0 parameter must be specified.
• CWMTC0108E
  Cannot find a JDBC data source with JNDI name of '' 0'' from the specified target.
• CWMTC0109I
  A JDBC data source with a JNDI name of '' 0'' was found.
• CWMTC0110E
  An authentication alias named '' 0'' does not exist.
• CWMTC0111I
  An authentication alias named '' 0'' was found.
• CWMTC0112I
  The 0 bus does not exist; it will be created.
• CWMTC0113I
  The bus member on cluster 0 for bus 1 does not exist; it will be created.
• CWMTC0114I
  The bus member on server 0 on node 1 for bus 1 does not exist; it will be created.
• CWMTC0115E
  The - 0 parameter cannot be specified when the database type is Derby.
• CWMTC0116E
  

  You can only specify Derby for the database type if the event service will be deployed to a server.

• CWMTC0117E
  The - 0 parameter must be specified when the database type is 1.
• CWMTC0118E
  An unrecognized database type was specified. Valid values are db2, oracle, or derby.
• CWMTC0119W
  The action services distribution queue definition references a JMS queue connection factory that is not found.
• CWMTC0120W
  The event group named " 0" has a distribution queue definition that references a JMS queue that is not found.
• CWMTC0121E
  0: Specify either a cluster, or both a server and a node.
• CWMTC0122E
  The 0 bus was not found.
• CWMTC0123E
  The 0 bus does not have any messaging engines defined.
• CWMTC0124I
  The " 0" queue destination already exists.
• CWMTC0125I
  The action services queue destination does not exist; it will be created.
• CWMTC0126I
  A JMS queue destination with a JNDI name of 0 already exists.
• CWMTC0127I
  The action services JMS queue does not exist; it will be created.
• CWMTC0128I
  A JMS queue connection factory with a JNDI name of 0 already exists.
• CWMTC0129I
  The action services JMS queue connection factory does not exist; it will be created.
• CWMTC0130I
  A JMS activation specification with a JNDI name of 0 already exists.
• CWMTC0131I
  The action services JMS activation specification does not exist; it will be created.
• CWMTC0132I
  Changing the component-managed authentication alias of the 0 connection factory from '' 1'' to '' 2''.
• CWMTC0133E
  An event emitter factory with JNDI name of 0 was not found.
• CWMTC0134I
  An action services event group does not exist; it will be created.
• CWMTC0135I
  The action services event group is already configured to distribute events to the action services JMS queue.
• CWMTC0136I
  Configure the action services event group to distribute events to the action services JMS queue.
• CWMTC0137I
  The action services application ( 0) is already installed.
• CWMTC0138I
  Installing the action services application ( 0).
• CWMTC0139E
  The required authentication alias named 0 was not found.
• CWMTC0140W
  The inter-engine authentication alias on the 0 bus was changed from 1 to 2
• CWMTC0141E
  The required authentication alias named 0 does not have a user ID set.
• CWMTC0142I
  User 0 (with unique name of 1) was added to the 2 bus'' connector role.
• CWMTC0143W
  More than one bus member found on the 0 bus.
• CWMTC0144E
  A conflicting bus member already exists in the 0 bus.
• CWMTC0145W
  More than one messaging engine found on the 0 bus at 1.
• CWMTC0146W
  At least one module in the 0 application is mapped to 1.
• CWMTC0147E
  

  Specify the - 0 parameter when deploying the event service to a cluster.

• CWMTC0148E
  There is no CEI event service deployed on the cluster 0.
• CWMTC0149E
  There is no CEI event service deployed on the server 0 on node 1.
• CWMTC0150E
  Business Monitor event emitter factory is not pointing to a valid CEI event service.
• CWMTC0500E
  The specified authentication alias named '' 0'' does not exist.
• CWMTC0501E
  The specified event group profile list named '' 0'' does not exist.
• CWMTC0502E
  The specified event service alias named '' 0'' is registered already.
• CWMTC0503E
  Registration failed for the source CEI server alias named '' 0''.
• CWMTC0504E
  The specified authentication alias named '' 0'' already exists.
• CWMTC0505E
  The value of the -location parameter is not valid. Valid values are 'local' or 'remote'.
• CWMTC0506E
  The -location parameter is 'remote', but the -hostname and -rmiPort parameters are missing.
• CWMTC0507E
  The value of the -rmiPort parameter is not valid.
• CWMTC0508E
  The -securityEnabled parameter is 'true', but either the -authAlias parameter or the -user and -password parameters are missing.
• CWMTC0509E
  The -securityEnabled parameter is 'true', and you specified both the -authAlias parameter and the -user and -password parameters.
• CWMTC0510I
  An authentication alias named '' 0'' was created.
• CWMTC0511I
  The source CEI event service named '' 0'' was registered.
• CWMTC0512E
  The specified event group profile list named '' 0'' does not exist at the 1 scope.
• CWMTC0513E
  No event group profile list was found.
• CWMTC0514E
  No event group profile list was found at the 1 scope.
• CWMTC0530I
  The data source named '' 0'' was created.
• CWMTC0531E
  The value of the -databaseType parameter is not valid. Valid values are 'db2' or 'oracle'.
• CWMTC0532E
  The value of the -databaseServerPort parameter is not valid.
• CWMTC0533E
  The value of the -driverType parameter is not valid. Valid values are '2' or '4'.
• CWMTC0534E
  The specified JDBC provider named '' 0'' does not exist.
• CWMTC0535I
  The data source named '' 0'' already exists.
• CWMTC0536E
  The specified JDBC provider named '' 0'' is not valid for the database type named '' 1''.
• CWMTC0537E
  Either the -authAlias parameter or the -user and -password parameters are missing.
• CWMTC0538E
  Both the -authAlias parameter and the -user and -password parameters are specified.
• CWMTC0550E
  The IBM Business Monitor bus named '' 0'' does not exist.
• CWMTC0551E
  No bus members were found on the '' 0'' bus.
• CWMTC0552E
  No messaging engines were found on the '' 0'' bus.
• CWMTC0553E
  Either the -remoteCluster parameter or the -remoteServer and -remoteNode parameters are missing.
• CWMTC0554E
  The -remoteCluster parameter conflicts with the -remoteServer and -remoteNode parameters.
• CWMTC0560I
  Queue-based configuration was completed for the bus named '' 0''.
• CWMTC0561I
  The '' 0'' bus will be created.
• CWMTC0562W
  The inter-engine authentication alias on the '' 0'' bus was changed from '' 1'' to '' 2''
• CWMTC0563I
  User '' 0'' (with unique name of '' 1'') was added to the connector role on the '' 2'' bus.
• CWMTC0564W
  More than one bus member was found on the '' 0'' bus.
• CWMTC0565I
  The '' 0'' bus member will be added on the '' 1'' bus.
• CWMTC0566W
  More than one messaging engine found on the '' 0'' bus at '' 1''.
• CWMTC0567I
  The '' 0'' messaging engine will be created on the '' 1'' bus.
• CWMTC0568I
  The '' 0'' foreign bus will be created on the '' 1'' bus.
• CWMTC0569E
  The value of the -messageStore parameter is not valid. Valid values are 'file' or 'data'.
• CWMTC0570E
  The -messageStore parameter is 'data', but the -datasourceAuthAlias parameter is missing.
• CWMTC0571E
  Cannot find a JDBC data source with a JNDI name of '' 0'' from the specified target.
• CWMTC0572E
  The value of the -SibEndpoint parameter is not valid.
• CWMTC0573E
  Either the -monitorCluster parameter or the -monitorServer and -monitorNode parameters are missing.
• CWMTC0574E
  Either the -cluster parameter or the -server and -node parameters are missing.
• CWMTC0575E
  The specified cluster named '' 0'' does not exist.
• CWMTC0576E
  The specified node named '' 0'' does not exist.
• CWMTC0577E
  The specified application server named '' 0'' does not exist on node '' 1''.
• CWMTC0578E
  The -securityEnabled parameter is ''true'', but either the - 0 parameter or the - 1 and - 2 parameters are missing.
• CWMTC0579E
  The -securityEnabled parameter is ''true'', and you specified both the - 0 parameter and the - 1 and - 2 parameters.
• CWMTC0580I
  The '' 0'' bus link will be created on the '' 1'' messaging engine.
• CWMTC0581E
  The -monitorCluster parameter conflicts with the -monitorServer and -monitorNode parameters.
• CWMTC0582E
  The -cluster parameter conflicts with the -server and -node parameters.
• CWMTC0583E
  The -messageStore parameter is 'data', but the -datasourceJndiName parameter is missing.
• CWMTC2000I
  The deployment has completed successfully.
• CWMTC2001E
  The 0 command is not available when Business Monitor has been installed.
• CWMTC2002E
  The removal has failed because the following error occurred: 0.
• CWMTC2003E
  The -cluster parameter or the -server and -node parameters are missing or conflicting.
• CWMTC2004E
  The cluster named '' 0'' does not exist.
• CWMTC2005E
  The node named '' 0'' does not exist.
• CWMTC2006E
  The server named '' 0'' does not exist on node '' 1''.
• CWMTC2007E
  

  Specify both the -adminName and -adminPassword parameters.

• CWMTC2008E
  

  Specify the -wasName and -wasPassword when security is enabled.

• CWMTC2009E
  The share library objects cannot be found because the following error occurred: 0
• CWMTC2010E
  The data source named '' 0'' cannot be used because the following error occurred: 1
• CWMTC2011E
  A connection to the data source '' 0'' failed because the following error occurred: 1
• CWMTC2012E
  The WebSphere Application Server install root environment variable does not exist.
• CWMTC2013E
  The Alphablox install root environment variable cannot be created.
• CWMTC2014E
  The WebSphere Application Server environment variable named '' 0'' cannot be found because the following error occurred: 1.
• CWMTC2015E
  The WebSphere Application Server environment variable name '' 0'' cannot be created because the following error occurred: 1.
• CWMTC2016E
  The Java virtual machine (JVM) arguments cannot be read or configured because the following error occurred: 0
• CWMTC2017E
  The WebSphere Application Server class loaders cannot be read or configured because the following error occurred: 0
• CWMTC2018E
  WebSphere Application Server settings cannot be accessed because the following error occurred: 0
• CWMTC2019E
  The Alphablox application .ear cannot be deployed because the following error occurred: 0
• CWMTC2020I
  Alphablox service was found to be already deployed, WAS user name and password were updated.
• CWMTC2021E
  The Alphablox application .ear cannot be mapped to a virtual host because the following error occurred: 0
• CWMTC2022E
  The Alphablox application .ear cannot be mapped to the default virtual host because the default virtual host was not found.
• CWMTC2023E
  The Alphablox application .ear cannot map users to roles because the following error occurred: 0
• CWMTC2024E
  The Alphablox deployment could not locate version information because the following error occurred: 0
• CWMTC2025E
  The Alphablox deployment could not find the schema qualifier for the database repository.
• CWMTC2026E
  The Alphablox service removal has failed because the following error occurred : 0
• CWMTC2027I
  The Alphablox service has been removed
• CWMTC2028E
  The Alphablox application .ear was not uninstalled successfully because the following error occurred: 0
• CWMTC2029E
  The Alphablox service request has not completed successfully
• CWMTC2030E
  

  Specify a valid user name and password when security is enabled.

• CWMTC2031E
  The WebSphere Application Server authorization alias cannot be created because the following error occurred: 0.
• CWMTC2032E
  The Alphablox repository database schema name cannot be determined because the following error occurred: 0.
• CWMTC2033E
  The WebSphere authorization alias for access to WebSphere administration was not found.
• CWMTC2034I
  The Alphablox service deployment has completed without making any system changes.
• CWMTC2035I
  The Alphablox service removal has completed without making any system changes.
• CWMTC2036I
  The Alphablox service is available.
• CWMTC2037E
  The Alphablox software is not installed on the node '' 0''
• CWMTC2038E
  Unable to connect to node '' 0'' to check for Alphablox installed software because the following error occurred: 1
• CWMTC2039E
  The -cluster parameter and the -server parameters may not be used together.
• CWMTC2040E
  The -cluster parameter and the -node parameters may not be used together.
• CWMTC2041E
  The -node parameter is missing.
• CWMTC2042E
  The -server parameter is missing.
• CWMTC2043E
  

  Specify both the -wasName and -wasPassword parameters.

• CWMTC2044E
  The system host name cannot be determined because the following error occurred: 0.
• CWMTC2045E
  The -clusterPort parameter must be a valid integer between 0 and 65535.
• CWMTC2046E
  The -isCluster parameter must be set to ''true'' or ''false''.
• CWMTC2047E
  The -isCluster parameter must be set to ''true'' when deploying Alphablox service to cluster.
• CWMTC2048E
  The cluster could not be determined to be an Alphblox service cluster because the following error occurred: 0
• CWMTC2049E
  The cluster member could not be added because the following error occurred: 0
• CWMTC2050E
  The cluster member has been deployed with the Alphablox service.
• CWMTC2051E
  The cluster member has not been deployed with the Alphablox service.
• CWMTC2052I
  The Alphablox service is not available.
• CWMTC2053I
  The Alphablox service will not be available from WebSphere administration.
• CWMTC2054I
  The Alphablox service has been enabled and will be available from WebSphere administration.
• CWMTC2100I
  The deployment has completed successfully.
• CWMTC2101E
  The deployment has failed because the following error occurred: 0.
• CWMTC2102E
  The removal has failed because the following error occurred: 0.
• CWMTC2103E
  The -cluster parameter or the -server and -node parameters are missing or conflicting.
• CWMTC2104E
  The cluster named '' 0'' does not exist.
• CWMTC2105E
  The node named '' 0'' does not exist.
• CWMTC2106E
  The server named '' 0'' does not exist on node '' 1''.
• CWMTC2109E
  The share library objects cannot be found because the following error occurred: 0
• CWMTC2110E
  The data source named '' 0'' cannot be used because the following error occurred: 1
• CWMTC2111E
  A connection to the data source '' 0'' failed because the following error occurred: 1
• CWMTC2112E
  The WebSphere Application Server install root environment variable does not exist.
• CWMTC2113E
  The Cognos install root environment variable cannot be created.
• CWMTC2114E
  The WebSphere Application Server environment variable '' 0'' cannot be found because the following error occurred: 1.
• CWMTC2115E
  The WebSphere Application Server environment variable '' 0'' cannot be created because the following error occurred: 1.
• CWMTC2116E
  The Java virtual machine (JVM) settings cannot be read or configured because the following error occurred: 0
• CWMTC2117E
  The WebSphere Application Server class loaders cannot be read or configured because the following error occurred: 0
• CWMTC2118E
  WebSphere Application Server settings cannot be accessed because the following error occurred: 0
• CWMTC2119E
  The Cognos application .ear cannot be deployed because the following error occurred: 0
• CWMTC2120I
  The Cognos Content Store DB user name and password were updated.
• CWMTC2121E
  The Cognos application .ear cannot be mapped to a virtual host because the following error occurred: 0
• CWMTC2122E
  The Cognos application .ear cannot be mapped to the default virtual host because the default virtual host was not found.
• CWMTC2123E
  The Cognos application EAR file cannot map users to roles because the following error occurred: 0
• CWMTC2124E
  The Cognos deployment could not locate the version information because the following error occurred: 0
• CWMTC2126E
  The Cognos service removal has failed because the following error occurred : 0
• CWMTC2127I
  The Cognos service has been removed.
• CWMTC2128E
  The Cognos application EAR file was not uninstalled successfully because the following error occurred: 0
• CWMTC2129E
  The Cognos service request has not completed successfully.
• CWMTC2130E
  The WebSphere Application Server authorization alias cannot be removed because the following error occurred: 0.
• CWMTC2131E
  The WebSphere Application Server authorization alias cannot be created because the following error occurred: 0.
• CWMTC2133E
  The WebSphere authorization alias for access to the Cognos content store database was not found.
• CWMTC2134I
  The Cognos service deployment has completed without making any system changes.
• CWMTC2135I
  The Cognos service removal has completed without making any system changes.
• CWMTC2136I
  The Cognos software is installed on the system.
• CWMTC2137E
  The Cognos software is not installed on the node '' 0''.
• CWMTC2138E
  Unable to connect to node '' 0'' to check for Cognos installed software because the following error occurred: 1
• CWMTC2139E
  The -cluster parameter and the -server parameters cannot be used together.
• CWMTC2140E
  The -cluster parameter and the -node parameters cannot be used together.
• CWMTC2141E
  The -node parameter is missing.
• CWMTC2142E
  The -server parameter is missing.
• CWMTC2143E
  

  Specify both the -adminUserName and -adminPassword parameters.

• CWMTC2144E
  The system host name or port number cannot be determined because the following error occurred: 0.
• CWMTC2148E
  The cluster could not be determined to be a Cognos service cluster because the following error occurred: 0
• CWMTC2149E
  The cluster member could not be added because the following error occurred: 0
• CWMTC2150I
  The cluster member has been deployed with the Cognos service.
• CWMTC2151I
  The cluster member has not been deployed with the Cognos service.
• CWMTC2152E
  The location specified by the -installRoot parameter does not exist.
• CWMTC2153E
  The Cognos startup xml file could not be updated or created because of the following error: 0
• CWMTC2154E
  The Cognos URI required for Monitor Lifecycle could not be updated or created because of the following error: 0
• CWMTC2155E
  The Cognos content store database user name and password are required.
• CWMTC2156E
  IBM Cognos version 0 is not supported. Version 1 or higher is required.
• CWMTC2157E
  The user registry type cannot be determined because the following error occurred: 0
• CWMTC2158E
  The following user registry type is not supported: 0
• CWMTC2159I
  The setting of the Cognos service address has completed successfully.
• CWMTC2160E
  The setting of the Cognos service address has not completed because the following error occurred: 0
• CWMTC2161E
  The end point Resource Provider was not created because the following error occurred: 0
• CWMTC2162E
  The end point resource provider was not updated because the following error occurred: 0
• CWMTC2200I
  Creating Cognos cubes has completed successfully.
• CWMTC2201I
  Removing Cognos cubes has completed successfully.
• CWMTC2202E
  Cubes could not be created on the Cognos server because the following error occurred: 0
• CWMTC2203E
  Unable to remove the cubes. See the server log file SystemOut.log for detail.
• CWMTC2204E
  Unable to retrieve the cubes. See the server log file SystemOut.log for detail.
• CWMTC2205E
  It was not possible to retrieve cube status from the Cognos server because the following error occurred: 0
• CWMTC2206E
  Parameter 0 is not valid.
• CWMTC2207E
  The Cognos end point resource provider was not found because the following error occurred: 0
• CWMTC2208E
  Unable to connect to the Cognos server. See the server log file SystemOut.log for detail.
• CWMTC2209E
  Unable to generate the Cognos cube. See the server log file SystemOut.log for detail.
• CWMTC2210E
  Unable to create the Cognos cube. See the server log file SystemOut.log for detail.
• CWMTC2211E
  It was not possible to locate the Monitor data source because the following error occurred: 0
• CWMTC2212E
  It was not possible to create the Cognos data source for cube data because the following error occurred: 0
• CWMTC2213E
  It was not possible to locate the authorization alias 0 because the following error occurred: 1
• CWMTC2214I
  Purging of cubes on the Cognos server for a monitor model has completed successfully.
• CWMTC2215E
  Model database schema not available.
• CWMTC2216E
  Unable to create data source: 0
• CWMTC2217E
  Cube 0 already existed on the Cognos server.
• CWMTC2218W
  Cube 0 does not exist on the Cognos server.
• CWMTC2219I
  Getting of Cognos cubes has completed successfully.
• CWMTC2220I
  Cognos 0 is installed.
• CWMTC2221I
  Cognos is not installed.
• CWMTC2222I
  Cognos is deployed.
• CWMTC2223I
  The Cognos service has not been deployed.
• CWMTC2224I
  The Cognos service is active.
• CWMTC2225I
  The Cognos service is not active.
• CWMTC2226I
  The Cognos service endpoint was not found.
• CWMTC2227E
  The status command '' 0'' option was not found.
• CWMTC2228I
  The Cognos service endpoint admin alias was updated.
• CWMTC2229E
  Unable to authenticate with Cognos Server.
• CWMTC2230E
  Package 0 does not exist on the Cognos server.
• CWMTC2231I
  The purging of cubes on the Cognos server for a monitor model has completed successfully.
• CWMTC2232E
  A lifecycle step was not found: 0
• CWMTC2233E
  The package does not exist on Cognos server: 0
• CWMTC2234E
  A lifecycle step is not allowed: 0
• CWMTC2235E
  A lifecycle version was not found: 0
• CWMTC2236E
  Failed to load data security filters: 0
• CWMTC2237E
  Failed to load object security settings: 0
• CWMTC2238I
  Cognos cubes are being created for monitoring model 0 version 1.
• CWMTC2239I
  The Cognos data source is being created: 0
• CWMTC2240I
  Removing Cognos cubes for monitoring model 0 version 1
• CWMTC2241I
  Purging Cognos cubes for monitoring model 0
• CWMTC2242I
  Reading Cognos cubes for monitoring model 0 version 1
• CWMTC2243E
  There was a failure to read the Cognos cube from Cognos server: 0
• CWMTC2244E
  There is an unsupported filter value expression: 0
• CWMTC2245E
  The metric ID not exist: 0
• CWMTC2246I
  Publishing Cognos cubes for each version has completed successfully.
• CWMTC2247E
  Unable to publish cubes for each version because the following error occurred: 0
• CWMTC2248E
  Failed to load model security settings: 0
• CWMTC2249E
  Monitor server security is not enabled.
• CWMTC2250I
  Updating package security for monitoring model has completed successfully.
• CWMTC2251E
  It was not possible to update the Cognos package security settings because the following error occurred: 0
• CWMTC2252I
  Updating Cognos package security for monitoring model 0
• CWMTC2253I
  Cognos cube cache was successfully cleared for model 0 and version 1
• CWMTC2254E
  Could not clear Cognos cube cache for model 0 and version 1 due to the following error: 2
• CWMTC2255E
  IBM Cognos application EAR version does not match the IBM Cognos install base version
• CWMTC2256I
  Cognos application EAR version: 0 was found in 1
• CWMTC2257I
  Cognos install base version: 0 was found in 1
• CWMTC2258E
  IBM Cognos application EAR version file was not found at 0.
• CWMTC2259E
  IBM Cognos install base version file was not found at 0.
• CWMTC2260E
  It was not possible to create the Cognos report because the following error occurred: 0
• CWMTC2261E
  The database logon failed. Ensure that a local database client is installed on the Cognos server and that the MONITOR database is cataloged. The cataloged name must match the database name configured in the Cognos data source for the Monitor database.
• CWMTC2262E
  The database logon failed. Ensure that all Cognos fixpacks are installed.
• CWMTC2263E
  Unable to publish cubes for 0.
• CWMTC0570E
  The -messageStore parameter is 'data', but the -datasourceAuthAlias parameter is missing.
• CWMTC0571E
  Cannot find a JDBC data source with a JNDI name of '' 0'' from the specified target.
• CWMTC0572E
  The value of the -SibEndpoint parameter is not valid.
• CWMTC0573E
  Either the -monitorCluster parameter or the -monitorServer and -monitorNode parameters are missing.
• CWMTC0574E
  Either the -cluster parameter or the -server and -node parameters are missing.
• CWMTC0575E
  The specified cluster named '' 0'' does not exist.
• CWMTC0576E
  The specified node named '' 0'' does not exist.
• CWMTC0577E
  The specified application server named '' 0'' does not exist on node '' 1''.
• CWMTC0578E
  The -securityEnabled parameter is ''true'', but either the - 0 parameter or the - 1 and - 2 parameters are missing.
• CWMTC0579E
  The -securityEnabled parameter is ''true'', and you specified both the - 0 parameter and the - 1 and - 2 parameters.
• CWMTC0580I
  The '' 0'' bus link will be created on the '' 1'' messaging engine.
• CWMTC0581E
  The -monitorCluster parameter conflicts with the -monitorServer and -monitorNode parameters.
• CWMTC0582E
  The -cluster parameter conflicts with the -server and -node parameters.
• CWMTC0583E
  The -messageStore parameter is 'data', but the -datasourceJndiName parameter is missing.
• CWMTC2000I
  The deployment has completed successfully.
• CWMTC2001E
  The 0 command is not available when Business Monitor has been installed.
• CWMTC2002E
  The removal has failed because the following error occurred: 0.
• CWMTC2003E
  The -cluster parameter or the -server and -node parameters are missing or conflicting.
• CWMTC2004E
  The cluster named '' 0'' does not exist.
• CWMTC2005E
  The node named '' 0'' does not exist.
• CWMTC2006E
  The server named '' 0'' does not exist on node '' 1''.
• CWMTC2007E
  

  Specify both the -adminName and -adminPassword parameters.

• CWMTC2008E
  

  Specify the -wasName and -wasPassword when security is enabled.

• CWMTC2009E
  The share library objects cannot be found because the following error occurred: 0
• CWMTC2010E
  The data source named '' 0'' cannot be used because the following error occurred: 1
• CWMTC2011E
  A connection to the data source '' 0'' failed because the following error occurred: 1
• CWMTC2012E
  The WebSphere Application Server install root environment variable does not exist.
• CWMTC2013E
  The Alphablox install root environment variable cannot be created.
• CWMTC2014E
  The WebSphere Application Server environment variable named '' 0'' cannot be found because the following error occurred: 1.
• CWMTC2015E
  The WebSphere Application Server environment variable name '' 0'' cannot be created because the following error occurred: 1.
• CWMTC2016E
  The Java virtual machine (JVM) arguments cannot be read or configured because the following error occurred: 0
• CWMTC2017E
  The WebSphere Application Server class loaders cannot be read or configured because the following error occurred: 0
• CWMTC2018E
  WebSphere Application Server settings cannot be accessed because the following error occurred: 0
• CWMTC2019E
  The Alphablox application .ear cannot be deployed because the following error occurred: 0
• CWMTC2020I
  Alphablox service was found to be already deployed, WAS user name and password were updated.
• CWMTC2021E
  The Alphablox application .ear cannot be mapped to a virtual host because the following error occurred: 0
• CWMTC2022E
  The Alphablox application .ear cannot be mapped to the default virtual host because the default virtual host was not found.
• CWMTC2023E
  The Alphablox application .ear cannot map users to roles because the following error occurred: 0
• CWMTC2024E
  The Alphablox deployment could not locate version information because the following error occurred: 0
• CWMTC2025E
  The Alphablox deployment could not find the schema qualifier for the database repository.
• CWMTC2026E
  The Alphablox service removal has failed because the following error occurred : 0
• CWMTC2027I
  The Alphablox service has been removed
• CWMTC2028E
  The Alphablox application .ear was not uninstalled successfully because the following error occurred: 0
• CWMTC2029E
  The Alphablox service request has not completed successfully
• CWMTC2030E
  

  Specify a valid user name and password when security is enabled.

• CWMTC2031E
  The WebSphere Application Server authorization alias cannot be created because the following error occurred: 0.
• CWMTC2032E
  The Alphablox repository database schema name cannot be determined because the following error occurred: 0.
• CWMTC2033E
  The WebSphere authorization alias for access to WebSphere administration was not found.
• CWMTC2034I
  The Alphablox service deployment has completed without making any system changes.
• CWMTC2035I
  The Alphablox service removal has completed without making any system changes.
• CWMTC2036I
  The Alphablox service is available.
• CWMTC2037E
  The Alphablox software is not installed on the node '' 0''
• CWMTC2038E
  Unable to connect to node '' 0'' to check for Alphablox installed software because the following error occurred: 1
• CWMTC2039E
  The -cluster parameter and the -server parameters may not be used together.
• CWMTC2040E
  The -cluster parameter and the -node parameters may not be used together.
• CWMTC2041E
  The -node parameter is missing.
• CWMTC2042E
  The -server parameter is missing.
• CWMTC2043E
  

  Specify both the -wasName and -wasPassword parameters.

• CWMTC2044E
  The system host name cannot be determined because the following error occurred: 0.
• CWMTC2045E
  The -clusterPort parameter must be a valid integer between 0 and 65535.
• CWMTC2046E
  The -isCluster parameter must be set to ''true'' or ''false''.
• CWMTC2047E
  The -isCluster parameter must be set to ''true'' when deploying Alphablox service to cluster.
• CWMTC2048E
  The cluster could not be determined to be an Alphblox service cluster because the following error occurred: 0
• CWMTC2049E
  The cluster member could not be added because the following error occurred: 0
• CWMTC2050E
  The cluster member has been deployed with the Alphablox service.
• CWMTC2051E
  The cluster member has not been deployed with the Alphablox service.
• CWMTC2052I
  The Alphablox service is not available.
• CWMTC2053I
  The Alphablox service will not be available from WebSphere administration.
• CWMTC2054I
  The Alphablox service has been enabled and will be available from WebSphere administration.
• CWMTC2100I
  The deployment has completed successfully.
• CWMTC2101E
  The deployment has failed because the following error occurred: 0.
• CWMTC2102E
  The removal has failed because the following error occurred: 0.
• CWMTC2103E
  The -cluster parameter or the -server and -node parameters are missing or conflicting.
• CWMTC2104E
  The cluster named '' 0'' does not exist.
• CWMTC2105E
  The node named '' 0'' does not exist.
• CWMTC2106E
  The server named '' 0'' does not exist on node '' 1''.
• CWMTC2109E
  The share library objects cannot be found because the following error occurred: 0
• CWMTC2110E
  The data source named '' 0'' cannot be used because the following error occurred: 1
• CWMTC2111E
  A connection to the data source '' 0'' failed because the following error occurred: 1
• CWMTC2112E
  The WebSphere Application Server install root environment variable does not exist.
• CWMTC2113E
  The Cognos install root environment variable cannot be created.
• CWMTC2114E
  The WebSphere Application Server environment variable '' 0'' cannot be found because the following error occurred: 1.
• CWMTC2115E
  The WebSphere Application Server environment variable '' 0'' cannot be created because the following error occurred: 1.
• CWMTC2116E
  The Java virtual machine (JVM) settings cannot be read or configured because the following error occurred: 0
• CWMTC2117E
  The WebSphere Application Server class loaders cannot be read or configured because the following error occurred: 0
• CWMTC2118E
  WebSphere Application Server settings cannot be accessed because the following error occurred: 0
• CWMTC2119E
  The Cognos application .ear cannot be deployed because the following error occurred: 0
• CWMTC2120I
  The Cognos Content Store DB user name and password were updated.
• CWMTC2121E
  The Cognos application .ear cannot be mapped to a virtual host because the following error occurred: 0
• CWMTC2122E
  The Cognos application .ear cannot be mapped to the default virtual host because the default virtual host was not found.
• CWMTC2123E
  The Cognos application EAR file cannot map users to roles because the following error occurred: 0
• CWMTC2124E
  The Cognos deployment could not locate the version information because the following error occurred: 0
• CWMTC2126E
  The Cognos service removal has failed because the following error occurred : 0
• CWMTC2127I
  The Cognos service has been removed.
• CWMTC2128E
  The Cognos application EAR file was not uninstalled successfully because the following error occurred: 0
• CWMTC2129E
  The Cognos service request has not completed successfully.
• CWMTC2130E
  The WebSphere Application Server authorization alias cannot be removed because the following error occurred: 0.
• CWMTC2131E
  The WebSphere Application Server authorization alias cannot be created because the following error occurred: 0.
• CWMTC2133E
  The WebSphere authorization alias for access to the Cognos content store database was not found.
• CWMTC2134I
  The Cognos service deployment has completed without making any system changes.
• CWMTC2135I
  The Cognos service removal has completed without making any system changes.
• CWMTC2136I
  The Cognos software is installed on the system.
• CWMTC2137E
  The Cognos software is not installed on the node '' 0''.
• CWMTC2138E
  Unable to connect to node '' 0'' to check for Cognos installed software because the following error occurred: 1
• CWMTC2139E
  The -cluster parameter and the -server parameters cannot be used together.
• CWMTC2140E
  The -cluster parameter and the -node parameters cannot be used together.
• CWMTC2141E
  The -node parameter is missing.
• CWMTC2142E
  The -server parameter is missing.
• CWMTC2143E
  

  Specify both the -adminUserName and -adminPassword parameters.

• CWMTC2144E
  The system host name or port number cannot be determined because the following error occurred: 0.
• CWMTC2148E
  The cluster could not be determined to be a Cognos service cluster because the following error occurred: 0
• CWMTC2149E
  The cluster member could not be added because the following error occurred: 0
• CWMTC2150I
  The cluster member has been deployed with the Cognos service.
• CWMTC2151I
  The cluster member has not been deployed with the Cognos service.
• CWMTC2152E
  The location specified by the -installRoot parameter does not exist.
• CWMTC2153E
  The Cognos startup xml file could not be updated or created because of the following error: 0
• CWMTC2154E
  The Cognos URI required for Monitor Lifecycle could not be updated or created because of the following error: 0
• CWMTC2155E
  The Cognos content store database user name and password are required.
• CWMTC2156E
  IBM Cognos version 0 is not supported. Version 1 or higher is required.
• CWMTC2157E
  The user registry type cannot be determined because the following error occurred: 0
• CWMTC2158E
  The following user registry type is not supported: 0
• CWMTC2159I
  The setting of the Cognos service address has completed successfully.
• CWMTC2160E
  The setting of the Cognos service address has not completed because the following error occurred: 0
• CWMTC2161E
  The end point Resource Provider was not created because the following error occurred: 0
• CWMTC2162E
  The end point resource provider was not updated because the following error occurred: 0
• CWMTC2200I
  Creating Cognos cubes has completed successfully.
• CWMTC2201I
  Removing Cognos cubes has completed successfully.
• CWMTC2202E
  Cubes could not be created on the Cognos server because the following error occurred: 0
• CWMTC2203E
  Unable to remove the cubes. See the server log file SystemOut.log for detail.
• CWMTC2204E
  Unable to retrieve the cubes. See the server log file SystemOut.log for detail.
• CWMTC2205E
  It was not possible to retrieve cube status from the Cognos server because the following error occurred: 0
• CWMTC2206E
  Parameter 0 is not valid.
• CWMTC2207E
  The Cognos end point resource provider was not found because the following error occurred: 0
• CWMTC2208E
  Unable to connect to the Cognos server. See the server log file SystemOut.log for detail.
• CWMTC2209E
  Unable to generate the Cognos cube. See the server log file SystemOut.log for detail.
• CWMTC2210E
  Unable to create the Cognos cube. See the server log file SystemOut.log for detail.
• CWMTC2211E
  It was not possible to locate the Monitor data source because the following error occurred: 0
• CWMTC2212E
  It was not possible to create the Cognos data source for cube data because the following error occurred: 0
• CWMTC2213E
  It was not possible to locate the authorization alias 0 because the following error occurred: 1
• CWMTC2214I
  Purging of cubes on the Cognos server for a monitor model has completed successfully.
• CWMTC2215E
  Model database schema not available.
• CWMTC2216E
  Unable to create data source: 0
• CWMTC2217E
  Cube 0 already existed on the Cognos server.
• CWMTC2218W
  Cube 0 does not exist on the Cognos server.
• CWMTC2219I
  Getting of Cognos cubes has completed successfully.
• CWMTC2220I
  Cognos 0 is installed.
• CWMTC2221I
  Cognos is not installed.
• CWMTC2222I
  Cognos is deployed.
• CWMTC2223I
  The Cognos service has not been deployed.
• CWMTC2224I
  The Cognos service is active.
• CWMTC2225I
  The Cognos service is not active.
• CWMTC2226I
  The Cognos service endpoint was not found.
• CWMTC2227E
  The status command '' 0'' option was not found.
• CWMTC2228I
  The Cognos service endpoint admin alias was updated.
• CWMTC2229E
  Unable to authenticate with Cognos Server.
• CWMTC2230E
  Package 0 does not exist on the Cognos server.
• CWMTC2231I
  The purging of cubes on the Cognos server for a monitor model has completed successfully.
• CWMTC2232E
  A lifecycle step was not found: 0
• CWMTC2233E
  The package does not exist on Cognos server: 0
• CWMTC2234E
  A lifecycle step is not allowed: 0
• CWMTC2235E
  A lifecycle version was not found: 0
• CWMTC2236E
  Failed to load data security filters: 0
• CWMTC2237E
  Failed to load object security settings: 0
• CWMTC2238I
  Cognos cubes are being created for monitoring model 0 version 1.
• CWMTC2239I
  The Cognos data source is being created: 0
• CWMTC2240I
  Removing Cognos cubes for monitoring model 0 version 1
• CWMTC2241I
  Purging Cognos cubes for monitoring model 0
• CWMTC2242I
  Reading Cognos cubes for monitoring model 0 version 1
• CWMTC2243E
  There was a failure to read the Cognos cube from Cognos server: 0
• CWMTC2244E
  There is an unsupported filter value expression: 0
• CWMTC2245E
  The metric ID not exist: 0
• CWMTC2246I
  Publishing Cognos cubes for each version has completed successfully.
• CWMTC2247E
  Unable to publish cubes for each version because the following error occurred: 0
• CWMTC2248E
  Failed to load model security settings: 0
• CWMTC2249E
  Monitor server security is not enabled.
• CWMTC2250I
  Updating package security for monitoring model has completed successfully.
• CWMTC2251E
  It was not possible to update the Cognos package security settings because the following error occurred: 0
• CWMTC2252I
  Updating Cognos package security for monitoring model 0
• CWMTC2253I
  Cognos cube cache was successfully cleared for model 0 and version 1
• CWMTC2254E
  Could not clear Cognos cube cache for model 0 and version 1 due to the following error: 2
• CWMTC2255E
  IBM Cognos application EAR version does not match the IBM Cognos install base version
• CWMTC2256I
  Cognos application EAR version: 0 was found in 1
• CWMTC2257I
  Cognos install base version: 0 was found in 1
• CWMTC2258E
  IBM Cognos application EAR version file was not found at 0.
• CWMTC2259E
  IBM Cognos install base version file was not found at 0.
• CWMTC2260E
  It was not possible to create the Cognos report because the following error occurred: 0
• CWMTC2261E
  The database logon failed. Ensure that a local database client is installed on the Cognos server and that the MONITOR database is cataloged. The cataloged name must match the database name configured in the Cognos data source for the Monitor database.
• CWMTC2262E
  The database logon failed. Ensure that all Cognos fixpacks are installed.
• CWMTC2263E
  Unable to publish cubes for 0.

Messages