Explanation | The UDDI deployment process is starting. |
Action | None. |
Explanation | This warning message indicates that changes in the wsadmin session previous to running the uddiDeploy.jacl script can not be discarded. The <Exception Message> describes the error that occurred. |
Action | None. |
Explanation | An active Application Manager can be used to stop and start UDDI on the deployment server. |
Action | None. |
Explanation | No active Application Manager can be found so there is no need to stop and start UDDI on the deployment server. |
Action | None. |
Explanation | Application Manager has been found, but is not running so there is no need to stop and start UDDI on the deployment server. |
Action | None. |
Explanation | The deployment script is checking for deployed UDDI applications. |
Action | None. |
Explanation | Attempting to stop a deployed UDDI application. |
Action | None. |
Explanation | The UDDI application stop request failed. |
Action | Attempt to stop the UDDI application via the Administration Console and rerun the uddiDeploy.jacl script. |
Explanation | The UDDI application has stopped executing. |
Action | None. |
Explanation | The deployment script is attempting to remove an existing UDDI application. |
Action | None. |
Explanation | The UDDI application has been removed from the configuration. |
Action | None. |
Explanation | A default UDDI deployment has been requested and therefore a Derby datasource will be created. |
Action | None. |
Explanation | The deployment script has detected a number of suitable Derby JDBC providers and will use the first. |
Action | None. |
Explanation | A Derby datasource has been created for the default UDDI deployment. |
Action | None. |
Explanation | The UDDI application requires PARENT_LAST class loading. |
Action | None. |
Explanation | The UDDI application class loader mode has been successfully changed. |
Action | None. |
Explanation | The UDDI application web modules require PARENT_LAST class loading. |
Action | None. |
Explanation | The UDDI Web modules class loader mode has been successfully changed. |
Action | None. |
Explanation | UDDI has been successfully deployed. |
Action | None. |
Explanation | Attempting to save the configuration after removing any existing UDDI application. |
Action | None. |
Explanation | Attempting to save the configuration after removing any existing UDDI application. |
Action | None. |
Explanation | Attempting to save the configuration after installing the UDDI application ear. |
Action | None. |
Explanation | The configuration changes have been successfully saved. |
Action | None. |
Explanation | Attempting to save the configuration after changing the class loader modes. |
Action | None. |
Explanation | The configuration changes have been successfully saved. |
Action | None. |
Explanation | This warning message indicates that changes in the wsadmin session previous to running the uddiDeploy.jacl script can not be discarded. The <Exception Message> describes the error that occurred. |
Action | None. |
Explanation | An active Application Manager can be used to stop and start UDDI on the deployment server. |
Action | None. |
Explanation | No active Application Manager can be found so there is no need to stop and start UDDI on the deployment server. |
Action | None. |
Explanation | Application Manager has been found, but is not running so there is no need to stop and start UDDI on the deployment server. |
Action | None. |
Explanation | Attempting to stop a deployed UDDI application. |
Action | None. |
Explanation | The UDDI application stop request failed. |
Action | Attempt to stop the UDDI application via the Administration Console and rerun the uddiDeploy.jacl script. |
Explanation | The UDDI application has stopped executing. |
Action | None. |
Explanation | The removal script is attempting to remove the UDDI application. |
Action | None. |
Explanation | The UDDI removal process is starting. |
Action | None. |
Explanation | The UDDI application has been removed from the configuration. |
Action | None. |
Explanation | A default UDDI removal has been requested and therefore the Derby datasource used for UDDI will be removed. |
Action | None. |
Explanation | The UDDI Derby datasource has been removed from the configuration. |
Action | None. |
Explanation | The default UDDI Derby datasource does not exist in this configuration and therefore does not need to be removed. |
Action | None. |
Explanation | UDDI has been successfully removed from the configuration. |
Action | None. |
Explanation | Attempting to save the configuration after removing the UDDI application. |
Action | None. |
Explanation | The configuration changes have been successfully saved. |
Action | None. |
Explanation | UDDI has been successfully removed from the configuration. |
Action | None. |
Explanation | The UDDI application has not been deployed and therefore the application can not be removed. |
Action | None. |
Explanation | The wrong number of arguments were passed to the script. Arguments are Node Name, Server Name, and optionally the <b>default keyword. |
Action | Retry with the correct arguments. |
Explanation | The deployment script has not been called with the correct arguments. |
Action | Retry with the correct arguments |
Explanation | An Exception occurred whilst trying to determine the Server ID. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | The Server ID could not be located for the given node name and server name. |
Action | Check the node name and server name are correct and are in the correct case. |
Explanation | The deployment script was unable to determine the list of JDBC providers. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to determine the list of JDBC providers for the server. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | A Derby JDBC provider is required for the default deployment of UDDI and an Exception occurred whilst trying to create this JDBC provider. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to create the UDDI Derby datasource. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to create J2EEResourcePropertySet. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to create the J2EE Resource Property 'databaseName' |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to create the J2EE Resource Property 'shutdownDatabase' |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to create the J2EE Resource Property 'dataSourceName' |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to create the J2EE Resource Property 'description' |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to create the J2EE Resource Property 'connectionAttributes' |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to create the J2EE Resource Property 'createDatabase' |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | The installation directory of WebSphere Application Server could not be determined. |
Action | Verify that WebSphere Application Server has been correctly installed and that the <b>WAS_INSTALL_ROOT WebSphere environment variable exists in the configuration. |
Explanation | An Exception occurred whilst trying to uninstall an existing UDDI application. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to install the UDDI application. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to locate the classloader for the UDDI application. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to determine the classloader mode of the UDDI application. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to change the classloader mode of the UDDI application. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to verify the new classloader mode of he UDDI application. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to determine the list of modules held in the UDDI application. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to determine the URI attribute of the application module. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to determine the classloader mode of a UDDI module. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to change the classloader mode of a UDDI module. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to verify the new classloader mode of a UDDI module. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to create the default Derby database. |
Action | Refer to messages displayed during creation to determine cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to locate the configurations Variable Map for the given node. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to to save the configuration after creating default datasource and removing an existing UDDI application. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to to save the configuration after installing the UDDI application. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to to save the final configuration. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | The wrong argument was passed to the script. Arguments are Node Name, Server Name, and optionally the <b>default keyword. |
Action | Retry with the correct arguments. |
Explanation | A default Derby UDDI Registry is not permitted in a WebSphere Application Server Network Deployment configuration. Please follow the UDDI Installation instructions on how to create a non default UDDI Registry database. |
Action | Retry with the correct arguments. |
Explanation | UDDI can only be deployed to a Cluster in a Network Deployment configuration. |
Action | Deploy UDDI using the arguments Node and Server. |
Explanation | An Exception occurred whilst trying to determine the Cluster ID. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | The Cluster ID could not be located for the given cluster name. |
Action | Check the cluster name are correct and are in the correct case. |
Explanation | The wrong number of arguments were passed to the script. Arguments are Node Name, Server Name, and optionally the <b>default keyword. |
Action | Retry with the correct arguments. |
Explanation | The removal script has not been called with the correct arguments. |
Action | Retry with the correct arguments |
Explanation | An Exception occurred whilst trying to determine the Server ID. |
Action | Retry the removal of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, then contact the IBM Customer Service Center. |
Explanation | The Server ID could not be located for the given node name or server name. |
Action | Check the node name or server name are correct and are in the correct case. |
Explanation | An Exception occurred whilst trying to uninstall the UDDI application. |
Action | Retry the removal of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to remove the UDDI Derby datasource. |
Action | Retry the removal of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | An Exception occurred whilst trying to to save the final configuration. |
Action | Retry the removal of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | The wrong argument was passed to the script. Arguments are Node Name, Server Name, and optionally the <b>default keyword. |
Action | Retry with the correct arguments. |
Explanation | A default Derby UDDI Registry is not permitted in a WebSphere Application Server Network Deployment configuration. Therefore there is no default Derby UDDI datasource to remove. |
Action | Retry with the correct arguments. |
Explanation | UDDI can only be removed from a Cluster in a Network Deployment configuration. |
Action | Remove UDDI using the arguments Node and Server. |
Explanation | An Exception occurred whilst trying to determine the Cluster ID. |
Action | Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center. |
Explanation | The Cluster ID could not be located for the given cluster name. |
Action | Check the cluster name are correct and are in the correct case. |