Explanation | This is the usage message displayed at the command line when the user has entered an invalid combination of arguments or options. |
Action | Enter the command according to the usage message. |
Explanation | This message is used as a marker in the message log file to indicate tool start points. |
Action | None. |
Explanation | Indicates which entity type (business, tModel etc.) is being promoted, and it's key value. |
Action | None. |
Explanation | The user entered an incorrect entity type. |
Action | Use an entity type of tModel, business, service or binding. |
Explanation | Indicates the promote function completed successfully. |
Action | None. |
Explanation | Indicates the import function completed successfully. |
Action | None. |
Explanation | Indicates the export function completed successfully. |
Action | None. |
Explanation | Indicates the delete function completed successfully. |
Action | None. |
Explanation | Indicates the export function has started. |
Action | None. |
Explanation | Indicates that the businessEntity with the specified key is being exported. |
Action | None. |
Explanation | Indicates that the businessService with the specified key is being exported. |
Action | None. |
Explanation | Indicates that the bindingTemplate with the specified key is being exported. |
Action | None. |
Explanation | Indicates that the tModel with the specified key is being exported. |
Action | None. |
Explanation | Indicates that the referenced tModel with the specified key is being exported. |
Action | None. |
Explanation | Indicates that the export function completed, and shows the number of entities exported. |
Action | None. |
Explanation | Indicates the import function has started. |
Action | None. |
Explanation | Indicates that the businessEntity with the specified key is being imported. |
Action | None. |
Explanation | Indicates that the businessService with the specified key is being imported. |
Action | None. |
Explanation | Indicates that the bindingTemplate with the specified key is being imported. |
Action | None. |
Explanation | Indicates that the tModel with the specified key is being imported. |
Action | None. |
Explanation | Indicates that the referenced tModel with the specified key is being imported. |
Action | None. |
Explanation | Indicates that the import function completed, and shows the number of entities imported. |
Action | None. |
Explanation | Indicates the delete function has started. |
Action | None. |
Explanation | Indicates that the businessEntity with the specified key is being deleted. |
Action | None. |
Explanation | Indicates that the businessService with the specified key is being deleted. |
Action | None. |
Explanation | Indicates that the bindingTemplate with the specified key is being deleted. |
Action | None. |
Explanation | Indicates that the tModel with the specified key is being deleted. |
Action | None. |
Explanation | Indicates that the delete function completed, and shows the number of entities deleted. |
Action | None. |
Explanation | Indicates that generation of the Entity Definition File has started. |
Action | None. |
Explanation | Indicates that generation of the Entity Definition File completed successfully. |
Action | None. |
Explanation | Indicates that reading of the Entity Definition File and creation of UDDI entities has started. |
Action | None. |
Explanation | Indicates that reading of the Entity Definition File and creation of UDDI entities completed successfully. |
Action | None. |
Explanation | Indicates the requested function completed successfully. |
Action | None. |
Explanation | Indicates the requested function did not complete successfully. |
Action | The messages log may yield further information if the verbose option is on. Check the configuration properties file settings are correct. If that does not identify the problem, try running with trace logging enabled. If that does not yield a solution, contact your IBM support center. |
Explanation | The XML parser reports a warning about the content of the Entity Definition File. |
Action | Based on the context of the warning message, check the validity of the Entity Definition File. |
Explanation | The XML parser reports an error about the content of the Entity Definition File. |
Action | Based on the context of the error message, check the validity of the Entity Definition File. |
Explanation | A parser feature set by the UDDI Utility Tools is not recognized by the parser. |
Action | Check you are using the correct type and level of XML parser. If correct, contact your IBM support center. |
Explanation | A parser feature set by the UDDI Utility Tools is not supported by the parser. |
Action | Check you are using the correct type and level of XML parser. If correct, contact your IBM support center. |
Explanation | A parser property set by the UDDI Utility Tools is not recognized by the parser. |
Action | Check you are using the correct type and level of XML parser. If correct, contact your IBM support center. |
Explanation | A parser property set by the UDDI Utility Tools is not supported by the parser. |
Action | Check you are using the correct type and level of XML parser. If correct, contact your IBM support center. |
Explanation | UDDI Utility Tools cannot locate the specified configuration file. |
Action | UDDI Utility Tools looks for a default configuration properties with the file name 'UDDIUtilityTools.properties' in the current directory. Check that the configuration file has this name, or that the argument value supplied with the '-properties' option is pointing at a file that exists. |
Explanation | The configuration file could not be read. |
Action | Check the file path points to a valid file and that the current user has permission to read the file. |
Explanation | A required property is missing from the configuration file. |
Action | Add the missing property name and value to the configuration file. Check that the property name is not misspelled. |
Explanation | A value was given to a property other than 'true' or 'false'. |
Action | Set the property value to 'true' or 'false'. |
Explanation | A value was given to a property other than an integer value. |
Action | Set the property value to an integer value. |
Explanation | The keys file could not be located at the specified path. |
Action | Check the file name and path are correct and that the file exists. |
Explanation | The keys file could not be read due to an IO error. |
Action | Check that the current user has permission to read the file. |
Explanation | During serialization, the Entity Definition File could not be written to. |
Action | Check the file's read only attribute is not set. |
Explanation | The Entity Definition File could not be found at the specified file path. |
Action | Check the file path is correct and that the file exists. |
Explanation | The Entity Definition File could not be read due to an IO error. |
Action | Check that the current user has permission to read the file. |
Explanation | The attempt to close the message log file failed. |
Action | The disk might be full. If so, clear some space or direct log output to a different disk. |
Explanation | The attempt to close the trace log file failed. |
Action | The disk might be full. If so, clear some space or direct log output to a different disk. |
Explanation | The UDDI Utility Tools logger could not find the specified file. |
Action | None. |
Explanation | General purpose message prefix used for reporting exceptions. |
Action | None. |
Explanation | Multiple function commands were entered on the command line. |
Action | Specify one function in accordance with the usage message. |
Explanation | UDDI Utility Tools was invoked with no function specified. |
Action | Specify one function in accordance with the usage message. |
Explanation | The function value did not match any of the allowed functions. |
Action | Specify one function in accordance with the usage message. |
Explanation | The argument value does not match any of the allowed arguments. |
Action | Specify arguments in accordance with the usage message. |
Explanation | An expected value for the specified argument was not supplied. |
Action | Specify a value for the argument in accordance with the usage message. |
Explanation | The entity type argument cannot be specified if the keysFile argument has already been supplied. |
Action | Specify arguments in accordance with the usage message. |
Explanation | The keysFile argument cannot be specified if an entity type argument and key value has already been supplied. |
Action | Specify arguments in accordance with the usage message. |
Explanation | An argument was specified twice in the same command. |
Action | Specify arguments in accordance with the usage message. |
Explanation | A keys file or an entity type and key value must be specified for functions using keys. |
Action | Specify arguments in accordance with the usage message. |
Explanation | The specified database driver could not be loaded. |
Action | Check the database driver value in the configuration file is valid, and the driver's class is present in the classpath property. |
Explanation | A connection could not be established with the database at the specified URL with the specified userid. |
Action | Check the database URL, userid and password values are correct in the configuration file, and that the database manager is running. |
Explanation | An attempt to close the database connection failed. |
Action | If the problem persists, contact your IBM support center. |
Explanation | The minimal data necessary for a valid tModel could not be inserted in the target UDDI registry database. |
Action | Check the database URL, userid and password values are correct in the configuration file, and that the database manager is running. |
Explanation | The minimal data necessary for a valid businessService could not be inserted in the target UDDI registry database. |
Action | Check the database URL, userid and password values are correct in the configuration file, and that the database manager is running. |
Explanation | The minimal data necessary for a valid businessEntity could not be inserted in the target UDDI registry database. |
Action | Check the database URL, userid and password values are correct in the configuration file, and that the database manager is running. |
Explanation | The minimal data necessary for a valid bindingTemplate could not be inserted in the target UDDI registry database. |
Action | Check the database URL, userid and password values are correct in the configuration file, and that the database manager is running. |
Explanation | An attempt to create the Entity Definition File failed. |
Action | Check the file path specified in the configuration file for the Entity Definition File is valid and is not set to be read only. |
Explanation | An unspecified error occurred when parsing the Entity Definition File. |
Action | Check the entity definiton file content is valid according to the UDDI Utility Tools schema file, promoter.xsd. |
Explanation | Errors occurred when parsing the Entity Definition File. |
Action | Check the entity definiton file content is valid according to the UDDI Utility Tools schema file, promoter.xsd. |
Explanation | Warnings occurred when parsing the Entity Definition File. |
Action | Check the entity definiton file content is valid according to the UDDI Utility Tools schema file, promoter.xsd. |
Explanation | An unexpected Exception occurred when trying to discover the publisher. |
Action | Turn on trace logging and look for the Exception that is recorded. |
Explanation | AuthInfo could not be obtained from the UDDI registry with the given userid and password. |
Action | Check the userid and password property values are correct in the configuration file. |
Explanation | The inquiry URL specified in the configuration file is not valid. |
Action | Correct the value for the inquiry URLs (fromInquiryURL and toInquiryURL) in the configuration file. |
Explanation | The publish URL specified in the configuration file is not valid. |
Action | Correct the value for the publish URL (toPublishURL)in the configuration file. |
Explanation | The get tModel operation failed on the source registry. |
Action | Check the key exists in the source registry. |
Explanation | The get service operation failed on the source registry. |
Action | Check the key exists in the source registry. |
Explanation | The get business operation failed on the source registry. |
Action | Check the key exists in the source registry. |
Explanation | The get binding operation failed on the source registry. |
Action | Check the key exists in the source registry. |
Explanation | The publish operation failed at the target registry. |
Action | Check the tModel is not referencing another entity (such as a tModel) that is not present in the target registry. This may occur if the 'importReferenced' property is set to 'false'. Specify referenced tModels in the referencedTModels section of the Entity Definition File and set 'importReferenced' property in the configuration file to 'true'. |
Explanation | The publish operation failed at the target registry. |
Action | Check the businessEntity is not referencing another entity (such as a tModel) that is not present in the target registry. This may occur if the 'importReferenced' property is set to 'false'. Specify referenced tModels in the referencedTModels section of the Entity Definition File and set 'importReferenced' property in the configuration file to 'true'. |
Explanation | The publish operation failed at the target registry. |
Action | Check the businessEntity specified as the parent of the businessService exists in the target registry. |
Explanation | The publish operation failed at the target registry. |
Action | Check the businessService specified as the parent of the bindingTemplate exists in the target registry. |
Explanation | The parent business for the specified businessService does not exist |
Action | Check the key value for the parent entity is correct in the Entity Definition File, and that the entity exists in the target registry. |
Explanation | The parent service for the specified bindingTemplate does not exist |
Action | Check the key value for the parent entity is correct in the Entity Definition File, and that the entity exists in the target registry. |
Explanation | The UDDI4J operation to delete the businessEntity with the specified key failed. |
Action | Check userid and password property values in the configuration file and that the entity exists on the target UDDI registry. |
Explanation | The UDDI4J operation to delete the businessService with the specified key failed. |
Action | Check userid and password property values in the configuration file and that the entity exists on the target UDDI registry. |
Explanation | The UDDI4J operation to delete the bindingTemplate with the specified key failed. |
Action | Check userid and password property values in the configuration file and that the entity exists on the target UDDI registry. |
Explanation | The UDDI4J operation to delete the tModel with the specified key failed. |
Action | Check userid and password property values in the configuration file and that the entity exists on the target UDDI registry. |
Explanation | The UDDI Registry could not be contacted. |
Action | Check the correct URLs are specified in the UDDIUtilityTools.properties file. |
Explanation | The key value entered does not comply with the format specified for a UUID in the UDDI specification. |
Action | Enter a valid UUID key. |
Explanation | The tModel was not saved because the overwrite property is false. |
Action | If the desired action is to overwrite existing entities, specify -overwrite on the command line or set the overwrite property in the configuration file to true. |
Explanation | The businessEntity was not saved because the overwrite property is false. |
Action | If the desired action is to overwrite existing entities, specify -overwrite on the command line or set the overwrite property in the configuration file to true. |
Explanation | The businessService was not saved because the overwrite property is false. |
Action | If the desired action is to overwrite existing entities, specify -overwrite on the command line or set the overwrite property in the configuration file to true. |
Explanation | The bindingTemplate was not saved because the overwrite property is false. |
Action | If the desired action is to overwrite existing entities, specify -overwrite on the command line or set the overwrite property in the configuration file to true. |
Explanation | The entered entity type was not recognized. |
Action | Specify arguments in accordance with the usage message. |
Explanation | The promote function failed to complete. |
Action | Check the configuration properties file has correct settings. |
Explanation | A problem occurred when writing the results file. |
Action | Turn on trace logging and look for the Exception that is recorded. |
Explanation | An unexpected error occured when creating the entity. |
Action | Turn on trace logging and look for the Exception that is recorded. |
Explanation | The rollback operation failed with an Exception. |
Action | Turn on trace logging and look for the Exception that is recorded. |
Explanation | The insertion of minimal entity data during the import function failed to commit to the database. |
Action | Check the database configuration. If necessary, turn on trace logging and look for the SQLException that is recorded. |
Explanation | UDDI Utility Tools needs to control commits of data changes, however the attempt to turn off auto-commit failed. |
Action | Check the database configuration. If necessary, turn on trace logging and look for the SQLException that is recorded. |
Explanation | An imported UDDI entity is not correctly constructed. |
Action | Examine the import file for UDDI entity errors. |
Explanation | A required argument value was not supplied. |
Action | Specify -definition <path to Entity Definition File> on the command line, or set the value of the UddiEntityDefinitionFile property in the configuration file to the path to the Entity Definition File. |
Explanation | A cycle has been detected such that a tModel is being referenced by a tModel that it directly or indirectly references. This would cause the UDDI Utility Tools to enter an infinite loop trying to import referenced tModels, so the process is halted. |
Action | Edit the Entity Definition File and temporarily remove the reference to the tModel in the cycle, taking a note of the reference details. After the import has successfully completed, update the tModel in the target registry to reintroduce the reference you previously removed. This can be done using the UDDI User Console, UDDI4J, or by creating a new Entity Defnition File with just the tModel to be updated, and running the UDDI Utility Tools with the import function. |
Explanation | An unexpected SQLException occurred preparing a SQL statement for execution. |
Action | Turn on trace logging and look for the SQLException that is recorded. |
Explanation | An unexpected error occurred. |
Action | Check configuration file settings and all registries and databases are active. If necessary, contact your IBM support center. |
Explanation | A TransPortException occurred while performing an UDDI4J operation on the UDDI registry at the specified URL. |
Action | Check configuration properties for the UDDI registry in question and ensure the UDDI registry is active. |
Explanation | When UDDI Utility Tools was invoked using the java -jar syntax, the invocation of the second JVM failed. |
Action | Check the configuration property 'classpath' value is correct, and that Java is configured to run from the command line. |
Explanation | Indicate that the import step of the import or promote function has completed, showing the number of entities imported. |
Action | None. |
Explanation | A publish step was not successful which may have left one or more minimal entities in the target registry database. UDDI Utility Tools attempts to remove these minimal entities but in this case, the removal has failed. Following messages will indicate which minimal entities are left in the target registry. |
Action | You can attempt to remove the minimal entities using normal methods, such as the user console, UDDI4J, or using the delete function of the UDDI Utility Tools. |
Explanation | A business minimal entity was orphaned in the target registry database and attempts to remove it failed. |
Action | Identify the orphaned minimal entity in the target registry and attempt to remove using normal UDDI delete methods, or by using the delete function of the UDDI Utility Tools. |
Explanation | A service minimal entity was orphaned in the target registry database and attempts to remove it failed. |
Action | Identify the orphaned minimal entity in the target registry and attempt to remove using normal UDDI delete methods, or by using the delete function of the UDDI Utility Tools. |
Explanation | A binding minimal entity was orphaned in the target registry database and attempts to remove it failed. |
Action | Identify the orphaned minimal entity in the target registry and attempt to remove using normal UDDI delete methods, or by using the delete function of the UDDI Utility Tools. |
Explanation | A tModel minimal entity was orphaned in the target registry database and attempts to remove it failed. |
Action | Identify the orphaned minimal entity in the target registry and attempt to remove using normal UDDI delete methods, or by using the delete function of the UDDI Utility Tools. |
Explanation | Indicates the minimal data required for a businessEntity has successfully been inserted in the target UDDI registry database. |
Action | None. |
Explanation | Indicates the minimal data required for a businessService has successfully been inserted in the target UDDI registry database. |
Action | None. |
Explanation | Indicates the minimal data required for a bindingTemplate has successfully been inserted in the target UDDI registry database. |
Action | None. |
Explanation | Indicates the minimal data required for a tModel has successfully been inserted in the target UDDI registry database. |
Action | None. |
Explanation | Indicates the minimal data inserted for a businessEntity was successfully removed from the target UDDI registry database. This would normally happen after a publish operation has failed. |
Action | None. |
Explanation | Indicates the minimal data inserted for a businessService was successfully removed from the target UDDI registry database. This would normally happen after a publish operation has failed. |
Action | None. |
Explanation | Indicates the minimal data inserted for a bindingTemplate was successfully removed from the target UDDI registry database. This would normally happen after a publish operation has failed. |
Action | None. |
Explanation | Indicates the minimal data inserted for a tModel was successfully removed from the target UDDI registry database. This would normally happen after a publish operation has failed. |
Action | None. |
Explanation | The UDDI4J find related businesses operation did not complete. |
Action | Check the configuration properties for the source registry, such as fromInquiryURL. |
Explanation | The UDDI4J find businesses operation did not complete. |
Action | Check the configuration properties for the source registry, such as fromInquiryURL. |
Explanation | The UDDI4J find services operation did not complete. |
Action | Check the configuration properties for the source registry, such as fromInquiryURL. |
Explanation | The UDDI4J find tModels operation did not complete. |
Action | Check the configuration properties for the source registry, such as fromInquiryURL. |
Explanation | The UDDI4J find bindings operation did not complete. |
Action | Check the configuration properties for the source registry, such as fromInquiryURL. |
Explanation | Indicates the find operation for selecting keys has started. |
Action | None. |
Explanation | Indicates the find operation to select keys has completed successfully. |
Action | None. |
Explanation | The UDDI Registries Node ID could not be found in the UDDI database. |
Action | Check that the UDDI application and database have initialized correctly. |
Explanation | An unexpected SQL Exception has been encountered. |
Action | Examine the SQL Exception Message to determine the cause of the problem. |
Explanation | The entity with the supplied tModel key could not be located and therefore deleted. |
Action | Ensure tModel key is correct. |
Explanation | The entity with the supplied Service key could not be located and therefore deleted. |
Action | Ensure Service key is correct. |
Explanation | The entity with the supplied Business key could not be located and therefore deleted. |
Action | Ensure Business key is correct. |
Explanation | The entity with the supplied Binding key could not be located and therefore deleted. |
Action | Ensure Binding key is correct. |
Explanation | The ServiceStub has an invalid sequence number. |
Action | Ensure the sequence number is greater than zero. |
Explanation | The BindingStub has an invalid sequence number. |
Action | Ensure the sequence number is greater than zero. |
Explanation | The JSSE Provider class name given in the jsse.provider property can not be loaded. |
Action | Check that the class name is correct e.g. com.ibm.jsse.IBMJSSEProvider and the jar that contains the class has been defined in the classpath property. |
Explanation | The JSSE Provider class name given in the jsse.provider property can not be instantiated. |
Action | Check that the class name is not an interface or abstract class. |
Explanation | The JSSE Provider class constructor for the class given in the jsse.provider property can not be accessed. |
Action | Check that the class name is correct e.g. com.ibm.jsse.IBMJSSEProvider and that the class has a public zero parameter constructor. |