Explanation | The UDDI deployment process is starting. |
Action | No action is required. |
Explanation | This message warns that changes made in the wsadmin session before the uddiDeploy.jacl script was run cannot be discarded, and shows the error that occurred. |
Action | No action is required. |
Explanation | An active Application Manager can be used to stop and start UDDI on the deployment server. |
Action | No action is required. |
Explanation | No active Application Manager can be found, so there is no need to stop and start UDDI on the deployment server. |
Action | No action is required. |
Explanation | An Application Manager has been found, but it is not running, so there is no need to stop and start UDDI on the deployment server. |
Action | No action is required. |
Explanation | The deployment script is checking for deployed UDDI applications. |
Action | No action is required. |
Explanation | There is an attempt to stop a deployed UDDI application. |
Action | No action is required. |
Explanation | The UDDI application stop request failed. |
Action | Attempt to stop the UDDI application using the Administrative Console and rerun the uddiDeploy.jacl script. |
Explanation | The UDDI application has stopped running. |
Action | No action is required. |
Explanation | The deployment script is attempting to remove an existing UDDI application. |
Action | No action is required. |
Explanation | The UDDI application has been removed from the configuration. |
Action | No action is required. |
Explanation | A default UDDI deployment has been requested and therefore a Derby data source will be created. |
Action | No action is required. |
Explanation | The deployment script has detected a number of suitable Derby JDBC providers and will use the first one. |
Action | No action is required. |
Explanation | A Derby data source has been created for the default UDDI deployment. |
Action | No action is required. |
Explanation | The UDDI application requires the class loading mode to be PARENT_LAST. |
Action | No action is required. |
Explanation | The UDDI application class loader mode has been successfully changed. |
Action | No action is required. |
Explanation | The UDDI application web modules require PARENT_LAST class loading. |
Action | No action is required. |
Explanation | The UDDI Web modules class loader mode has been successfully changed. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | There is an attempt to save the configuration after removing any existing UDDI application. |
Action | No action is required. |
Explanation | There is an attempt to save the configuration after removing any existing UDDI application. |
Action | No action is required. |
Explanation | There is an attempt to save the configuration after installing the UDDI application ear. |
Action | No action is required. |
Explanation | The configuration changes have been successfully saved. |
Action | No action is required. |
Explanation | There is an attempt to save the configuration after changing the class loader modes. |
Action | No action is required. |
Explanation | The configuration changes have been successfully saved. |
Action | No action is required. |
Explanation | This message warns that changes made in the wsadmin session before the uddiDeploy.jacl script was run cannot be discarded, and shows the error that occurred. |
Action | No action is required. |
Explanation | An active Application Manager can be used to stop and start UDDI on the deployment server. |
Action | No action is required. |
Explanation | No active Application Manager can be found so there is no need to stop and start UDDI on the deployment server. |
Action | No action is required. |
Explanation | An Application Manager has been found, but it is not running, so there is no need to stop and start UDDI on the deployment server. |
Action | No action is required. |
Explanation | There is an attempt to stop a deployed UDDI application. |
Action | No action is required. |
Explanation | The request to stop the UDDI application failed. |
Action | Attempt to stop the UDDI application using the Administrative Console and rerun the uddiDeploy.jacl script. |
Explanation | The UDDI application has stopped running. |
Action | No action is required. |
Explanation | The removal script is attempting to remove the UDDI application. |
Action | No action is required. |
Explanation | The UDDI removal process is starting. |
Action | No action is required. |
Explanation | The UDDI application has been removed from the configuration. |
Action | No action is required. |
Explanation | A default UDDI removal has been requested and therefore the Derby data source that is used for UDDI will be removed. |
Action | No action is required. |
Explanation | The UDDI Derby data source has been removed from the configuration. |
Action | No action is required. |
Explanation | The default UDDI Derby data source does not exist in this configuration and therefore does not need to be removed. |
Action | No action is required. |
Explanation | UDDI has been successfully removed from the configuration. |
Action | No action is required. |
Explanation | There is an attempt to save the configuration after removing the UDDI application. |
Action | No action is required. |
Explanation | The configuration changes have been successfully saved. |
Action | No action is required. |
Explanation | UDDI has been successfully removed from the configuration. |
Action | No action is required. |
Explanation | The UDDI application has not been deployed and therefore the application cannot be removed. |
Action | No action is required. |
Explanation | The wrong number of arguments were passed to the script. Arguments are Node Name, Server Name, and optionally the default keyword. |
Action | Retry the script with the correct arguments. |
Explanation | The deployment script has not been called with the correct arguments. |
Action | Retry the script with the correct arguments |
Explanation | An exception occurred while trying to determine the Server ID. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | The server ID could not be located for the given node name and server name. |
Action | Check that 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 continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to determine the list of JDBC providers for the server. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | A Derby JDBC provider is required for the default deployment of UDDI and an exception occurred while trying to create this JDBC provider. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to create the UDDI Derby data source. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to create the Java Platform, Enterprise Edition resource property set. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to create the Java Platform, Enterprise Edition resource property 'databaseName'. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to create the Java Platform, Enterprise Edition resource property 'shutdownDatabase'. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to create the Java Platform, Enterprise Edition resource property 'dataSourceName'. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to create the Java Platform, Enterprise Edition resource property 'description'. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to create the Java Platform, Enterprise Edition resource property 'connectionAttributes' |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to create the Java Platform, Enterprise Edition resource property 'createDatabase' |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | The installation directory of Application Server could not be determined. |
Action | Verify that the Application Server has been correctly installed and that the WAS_INSTALL_ROOT environment variable exists in the configuration. |
Explanation | An exception occurred while trying to uninstall an existing UDDI application. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to install the UDDI application, probably during the installation of the UDDI application into the application server, but possibly at another stage during the deployment of UDDI. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to locate the classloader for the UDDI application. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to determine the classloader mode of the UDDI application. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to change the classloader mode of the UDDI application. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to verify the new classloader mode of the UDDI application. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to determine the list of modules held in the UDDI application. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to determine the URI attribute of the application module. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to determine the classloader mode of a UDDI module. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to change the classloader mode of a UDDI module. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to verify the new classloader mode of a UDDI module. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to create the default Derby database. |
Action | Refer to the accompanying messages to determine the cause. |
Explanation | An exception occurred while trying to locate the configurations Variable Map for the given node. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to save the configuration after creating a default data source and removing an existing UDDI application. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to save the configuration after installing the UDDI application. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to save the final configuration. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | The wrong argument was passed to the script. Arguments are Node Name, Server Name, and optionally the default keyword. |
Action | Retry the script with the correct arguments. |
Explanation | A default Derby UDDI registry is not permitted in a WebSphere Application Server Network Deployment configuration. Follow the UDDI installation instructions about how to create a non-default UDDI registry database. |
Action | Retry the script with the correct arguments. |
Explanation | UDDI can be deployed to a cluster only in a Network Deployment configuration. |
Action | Deploy UDDI using the arguments node name and server name. |
Explanation | An exception occurred while trying to determine the cluster ID. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | The cluster ID could not be located for the given cluster name. |
Action | Check the cluster name is correct and is in the correct case. |
Explanation | The wrong number of arguments were passed to the script. Arguments are Node Name, Server Name, and optionally the default keyword. |
Action | Retry the script with the correct arguments. |
Explanation | The removal script has not been called with the correct arguments. |
Action | Retry the script with the correct arguments |
Explanation | An exception occurred while trying to determine the Server ID. |
Action | Retry the removal of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | The Server ID could not be located for the given node name or server name. |
Action | Check that the node name or server name are correct and are in the correct case. |
Explanation | An exception occurred while trying to uninstall the UDDI application. |
Action | Retry the removal of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to remove the UDDI Derby data source. |
Action | Retry the removal of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | An exception occurred while trying to save the final configuration. |
Action | Retry the removal of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | The wrong argument was passed to the script. Arguments are Node Name, Server Name, and optionally the default keyword. |
Action | Retry the script 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 data source to remove. |
Action | Retry the script 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 name and server name. |
Explanation | An exception occurred while trying to determine the cluster ID. |
Action | Retry the deployment of UDDI. If the error continues, examine the exception information to determine its cause. |
Explanation | The cluster ID could not be located for the given cluster name. |
Action | Check the cluster name is correct and is in the correct case. |