Express (Distributed operating systems), v8.0 > Reference > Messages
CWUDU
CWUDU0001I: Usage: java -jar UDDIUtilityTools.jar '{'function'}' [options]
function:
-promote <entity source> Promote entites between registries
-export <entity source> Extract entities from registry to XML
-delete <entity source> Delete entities from registry
-import Create entities from XML to registry
where <entity source> is one of:
-tmodel|-business|-service|-binding <key> Specify single entity type and key
-keysFile | -f <filename> Specify file containing entity types and keys
options:
-properties <filename> Specify path to configuration file
-overwrite | -o Overwrite an entity if it already exists
-log | -v Output verbose messages
-definitionFile <filename> Specify path to UDDI entity definition file
-importReferenced Import entities referenced by source entities
The following options override property settings in configuration file:
-overwrite
-log
-definitionFile
-importReferenced
Example: java -jar UDDIUtilityTools.jar -promote -keysFile C:/uddikeys.txt
Explanation This is the usage message displayed at the command line when the user has entered a combination of arguments or options that are not valid. Action Enter the command according to the usage message.
CWUDU0002I: ********** Starting UDDI Utility Tools **********
Explanation This message is used as a marker in the message log file to indicate tool start points. Action None.
CWUDU0003I: Promoting entityType <{0}> key <{1}>...
Explanation Indicates which entity type (business, tModel for example) is being promoted, and it's key value. Action None.
CWUDU0004W: Bad entityType: received <{0}>, expected <tModel|business|service|binding>
Explanation The user entered an incorrect entity type. Action Use an entity type of tModel, business, service or binding.
CWUDU0005I: Promotion successful.
Explanation Indicates the promote function completed successfully. Action None.
CWUDU0006I: Import successful.
Explanation Indicates the import function completed successfully. Action None.
CWUDU0007I: Export successful.
Explanation Indicates the export function completed successfully. Action None.
CWUDU0008I: Delete successful.
Explanation Indicates the delete function completed successfully. Action None.
CWUDU0009I: Exporting entities...
Explanation Indicates the export function has started. Action None.
CWUDU0010I: Exporting business, businessKey[{0}].
Explanation Indicates that the businessEntity with the specified key is being exported. Action None.
CWUDU0011I: Exporting service, serviceKey[{0}].
Explanation Indicates that the businessService with the specified key is being exported. Action None.
CWUDU0012I: Exporting binding, bindingKey[{0}].
Explanation Indicates that the bindingTemplate with the specified key is being exported. Action None.
CWUDU0013I: Exporting tModel, tModelKey[{0}].
Explanation Indicates that the tModel with the specified key is being exported. Action None.
CWUDU0014I: Exporting referenced tModel, tModelKey[{0}].
Explanation Indicates that the referenced tModel with the specified key is being exported. Action None.
CWUDU0015I: Exported {0} entities.
Explanation Indicates that the export function completed, and shows the number of entities exported. Action None.
CWUDU0016I: Importing entities...
Explanation Indicates the import function has started. Action None.
CWUDU0017I: Importing business, businessKey[{0}].
Explanation Indicates that the businessEntity with the specified key is being imported. Action None.
CWUDU0018I: Importing service, serviceKey[{0}].
Explanation Indicates that the businessService with the specified key is being imported. Action None.
CWUDU0019I: Importing binding, bindingKey[{0}].
Explanation Indicates that the bindingTemplate with the specified key is being imported. Action None.
CWUDU0020I: Importing tModel, tModelKey[{0}].
Explanation Indicates that the tModel with the specified key is being imported. Action None.
CWUDU0021I: Importing referenced tModel, tModelKey[{0}].
Explanation Indicates that the referenced tModel with the specified key is being imported. Action None.
CWUDU0022I: Imported {0} entities.
Explanation Indicates that the import function completed, and shows the number of entities imported. Action None.
CWUDU0023I: Deleting entities...
Explanation Indicates the delete function has started. Action None.
CWUDU0024I: Deleting business, businessKey[{0}].
Explanation Indicates that the businessEntity with the specified key is being deleted. Action None.
CWUDU0025I: Deleting service, serviceKey[{0}].
Explanation Indicates that the businessService with the specified key is being deleted. Action None.
CWUDU0026I: Deleting binding, bindingKey[{0}].
Explanation Indicates that the bindingTemplate with the specified key is being deleted. Action None.
CWUDU0027I: Deleting tModel, tModelKey[{0}].
Explanation Indicates that the tModel with the specified key is being deleted. Action None.
CWUDU0028I: Deleted {0} entities.
Explanation Indicates that the delete function completed, and shows the number of entities deleted. Action None.
CWUDU0029I: Serializing...
Explanation Indicates that generation of the Entity Definition File has started. Action None.
CWUDU0030I: Serialized entities.
Explanation Indicates that generation of the Entity Definition File completed successfully. Action None.
CWUDU0031I: Deserializing...
Explanation Indicates that reading of the Entity Definition File and creation of UDDI entities has started. Action None.
CWUDU0032I: Deserialized entities.
Explanation Indicates that reading of the Entity Definition File and creation of UDDI entities completed successfully. Action None.
CWUDU0033I: Function ''{0}'' completed successfully.
Explanation Indicates the requested function completed successfully. Action None.
CWUDU0034W: Function ''{0}'' did not complete successfully. See messages log for further information.
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.
CWUDU0035W: Parser warning: {0}
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.
CWUDU0036E: Parser error: {0}
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.
CWUDU0037E: Unrecognized parser feature: {0}
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.
CWUDU0038E: Unsupported parser feature: {0}
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.
CWUDU0039E: Unrecognized parser property: {0}, value: {1}
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.
CWUDU0040E: Unsupported parser property: {0}, value: {1}
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.
CWUDU0041I: {0}
Explanation None Action None
CWUDU0042E: Unable to find the configuration file: {0}
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.
CWUDU0043E: An Exception occurred trying to read the configuration file.
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.
CWUDU0044W: Configuration file is missing the ''{0}'' property.
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.
CWUDU0045W: Property: ''{0}'' has value ''{1}''. It must be either ''true'' or ''false''.
Explanation A value was given to a property other than 'true' or 'false'. Action Set the property value to 'true' or 'false'.
CWUDU0046W: Property: ''{0}'' has value ''{1}''. It must be an integer value.
Explanation A value was given to a property other than an integer value. Action Set the property value to an integer value.
CWUDU0047E: Unable to find the keyFile file: {0}
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.
CWUDU0048E: Unable to read the keyFile file: {0}
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.
CWUDU0049E: Unable to write to entity definition file: {0}
Explanation During serialization, the Entity Definition File could not be written to. Action Check the file's read only attribute is not set.
CWUDU0050E: Unable to find UDDI Entity definition file. {0}
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.
CWUDU0051E: Unable to read UDDI Entity definition file. {0}
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.
CWUDU0052E: Unable to close the messages file: {0}
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.
CWUDU0053E: Unable to cloes the trace file: {0}
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.
CWUDU0054E: The logger was unable to find the file: {0}
Explanation The UDDI Utility Tools logger could not find the specified file. Action None.
CWUDU0055E: ERROR OCCURRED...
Explanation None Action None
CWUDU0056E: Exception:
Explanation General purpose message prefix used for reporting exceptions. Action None.
CWUDU0057W: Only one function may be specified on the command line.
Explanation Multiple function commands were entered on the command line. Action Specify one function in accordance with the usage message.
CWUDU0058W: No function was specified.
Explanation UDDI Utility Tools was invoked with no function specified. Action Specify one function in accordance with the usage message.
CWUDU0059W: The function: {0} was not recognised.
Explanation The function value did not match any of the allowed functions. Action Specify one function in accordance with the usage message.
CWUDU0060W: The argument ''{0}'' was not recognised.
Explanation The argument value does not match any of the allowed arguments. Action Specify arguments in accordance with the usage message.
CWUDU0061W: There was a missing value for {0} argument.
Explanation An expected value for the specified argument was not supplied. Action Specify a value for the argument in accordance with the usage message.
CWUDU0062W: Unexpected argument: {0} (entity key file is already specified).
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.
CWUDU0063W: Unexpected argument: {0} (entity key is already specified).
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.
CWUDU0064W: Argument: {0} cannot be specified more than once.
Explanation An argument was specified twice in the same command. Action Specify arguments in accordance with the usage message.
CWUDU0065E: No entity keys were specified.
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.
CWUDU0066E: Could not load Database driver: dbDriver < {0} >.
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 class path property.
CWUDU0067E: Could not create Database connection: dbUrl <{0}>, dbUser <{1}>, (dbPasswd not shown).
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.
CWUDU0068E: Could not close the database connection.
Explanation An attempt to close the database connection failed. Action If the problem persists, contact your IBM support center.
CWUDU0069E: Could not create minimal entity for tModel with tModelKey[{0}].
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.
CWUDU0070E: Could not create minimal entity for Service with serviceKey[{0}].
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.
CWUDU0071E: Could not create minimal entity for Business with businessKey[{0}].
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.
CWUDU0072E: Could not create minimal entity for Binding with bindingKey[{0}].
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.
CWUDU0073E: There was an error while trying to create an XML Document.
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.
CWUDU0074E: There was an error parsing the entity definition file.
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.
CWUDU0075E: One or more errors occurred while parsing the entity definition file. See message log for details.
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.
CWUDU0076W: One or more warnings were raised while parsing the entity definition file. See message log for details.
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.
CWUDU0077E: An error occurred trying to discover the publisher.
Explanation An unexpected Exception occurred when trying to discover the publisher. Action Turn on trace logging and look for the Exception that is recorded.
CWUDU0078E: Unable to obtain authinfo.
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.
CWUDU0079E: The inquiryURL is malformed: {0}
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.
CWUDU0080E: The publishURL is malformed: {0}
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.
CWUDU0081E: Could not get tModel detail for tModelKey[{0}].
Explanation The get tModel operation failed on the source registry. Action Check the key exists in the source registry.
CWUDU0082E: Could not get service detail for serviceKey[{0}].
Explanation The get service operation failed on the source registry. Action Check the key exists in the source registry.
CWUDU0083E: Could not get business detail for businessKey[{0}].
Explanation The get business operation failed on the source registry. Action Check the key exists in the source registry.
CWUDU0084E: Could not get binding detail for bindingKey[{0}].
Explanation The get binding operation failed on the source registry. Action Check the key exists in the source registry.
CWUDU0085E: Could not save tModel for tModelKey[{0}].
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'.
CWUDU0086E: Could not save business for businessKey[{0}].
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'.
CWUDU0087E: Could not save service for parent businessKey[{0}].
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.
CWUDU0088E: Could not save binding for parent serviceKey[{0}].
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.
CWUDU0089W: Did not save service for serviceKey[{0}] because parent business did not exist.
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.
CWUDU0090W: Did not save binding for bindingKey[{0}] because parent service did not exist.
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.
CWUDU0091E: Could not delete business for businessKey[{0}].
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.
CWUDU0092E: Could not delete service for serviceKey[{0}].
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.
CWUDU0093E: Could not delete binding for bindingKey[{0}].
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.
CWUDU0094E: Could not delete tModel for tModelKey[{0}].
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.
CWUDU0095E: Could not reach {0}.
Explanation The UDDI Registry could not be contacted. Action Check the correct URLs are specified in the UDDIUtilityTools.properties file.
CWUDU0096W: {0} is not a valid UUID.
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.
CWUDU0097W: Did not save tModel for tModelKey[{0}] as it already exists. Use the -overwrite argument to overwrite the tModel.
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.
CWUDU0098W: Did not save business for businessKey[{0}] as it already exists. Use the -overwrite argument to overwrite the business.
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.
CWUDU0099W: Did not save service for serviceKey[{0}] as it already exists. Use the -overwrite argument to overwrite the service.
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.
CWUDU0100W: Did not save binding for bindingKey[{0}] as it already exists. Use the -overwrite argument to overwrite the binding.
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.
CWUDU0101W: Bad entityType: received <{0}>, expected <tModel|business|service|binding>
Explanation The entered entity type was not recognized. Action Specify arguments in accordance with the usage message.
CWUDU0102E: Promotion failed.
Explanation The promote function failed to complete. Action Check the configuration properties file has correct settings.
CWUDU0103E: Error occurred while creating results file.
Explanation A problem occurred when writing the results file. Action Turn on trace logging and look for the Exception that is recorded.
CWUDU0104E: Minimal entity creation failed.
Explanation An unexpected error occured when creating the entity. Action Turn on trace logging and look for the Exception that is recorded.
CWUDU0105E: Rollback failed.
Explanation The rollback operation failed with an Exception. Action Turn on trace logging and look for the Exception that is recorded.
CWUDU0106E: Unable to commit transaction.
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.
CWUDU0107E: Unable to set auto-commit off on the database connection.
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.
CWUDU0108E: An entity to be imported was found to be invalid.
Explanation An imported UDDI entity is not correctly constructed. Action Examine the import file for UDDI entity errors.
CWUDU0109W: The import function requires a UDDI entity definition file to be specified.
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.
CWUDU0110E: A cyclic dependency exists in the referenced tModels. The reference from tModel with key [{0}] to the tModel with key [{1}] completes the detected cycle.
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.
CWUDU0111E: Error occurred trying to create PreparedStatements. Check database configuration.
Explanation An unexpected SQLException occurred preparing a SQL statement for execution. Action Turn on trace logging and look for the SQLException that is recorded.
CWUDU0112E: An unexpected exception has occurred: {0}
Explanation An unexpected error occurred. Action Check configuration file settings and all registries and databases are active. If necessary, contact your IBM support center.
CWUDU0113E: Could not get a response from UDDI registry at URL: {0}
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.
CWUDU0114E: An IOException occurred trying to invoke 'java'.
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.
CWUDU0115I: Imported {0} entities and {1} referenced entities.
Explanation Indicate that the import step of the import or promote function has completed, showing the number of entities imported. Action None.
CWUDU0116W: Not all minimal entities could be removed. The following remain in the database:
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 We 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.
CWUDU0117W: Business minimal entity with businessKey [{0}] has not been removed from the database.
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.
CWUDU0118W: Service minimal entity with serviceKey [{0}] has not been removed from the database.
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.
CWUDU0119W: Binding Template minimal entity with bindingKey [{0}] has not been removed from the database.
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.
CWUDU0120W: TModel minimal entity with tModelKey [{0}] has not been removed from the database.
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.
CWUDU0121I: Created business minimal entity with businessKey [{0}].
Explanation Indicates the minimal data required for a businessEntity has successfully been inserted in the target UDDI registry database. Action None.
CWUDU0122I: Created service minimal entity with serviceKey [{0}].
Explanation Indicates the minimal data required for a businessService has successfully been inserted in the target UDDI registry database. Action None.
CWUDU0123I: Created binding template minimal entity with bindingKey [{0}].
Explanation Indicates the minimal data required for a bindingTemplate has successfully been inserted in the target UDDI registry database. Action None.
CWUDU0124I: Created tModel minimal entity with tModelKey [{0}].
Explanation Indicates the minimal data required for a tModel has successfully been inserted in the target UDDI registry database. Action None.
CWUDU0125I: Deleted business minimal entity with businessKey [{0}].
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.
CWUDU0126I: Deleted service minimal entity with serviceKey [{0}].
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.
CWUDU0127I: Deleted binding template minimal entity with bindingKey [{0}].
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.
CWUDU0128I: Deleted tModel minimal entity with tModelKey [{0}].
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.
CWUDU0129E: Find related businesses failed.
Explanation The UDDI4J find related businesses operation did not complete. Action Check the configuration properties for the source registry, such as fromInquiryURL.
CWUDU0130E: Find businesses failed.
Explanation The UDDI4J find businesses operation did not complete. Action Check the configuration properties for the source registry, such as fromInquiryURL.
CWUDU0131E: Find services failed.
Explanation The UDDI4J find services operation did not complete. Action Check the configuration properties for the source registry, such as fromInquiryURL.
CWUDU0132E: Find tModels failed.
Explanation The UDDI4J find tModels operation did not complete. Action Check the configuration properties for the source registry, such as fromInquiryURL.
CWUDU0133E: Find bindings failed.
Explanation The UDDI4J find bindings operation did not complete. Action Check the configuration properties for the source registry, such as fromInquiryURL.
CWUDU0134I: Performing inquiry request...
Explanation Indicates the find operation for selecting keys has started. Action None.
CWUDU0135I: Extracted keys from inquiry results.
Explanation Indicates the find operation to select keys has completed successfully. Action None.
CWUDU0136E: node ID value could not be found in UDDI database.
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.
CWUDU0137E: Unexpected database SQL exception: {0}.
Explanation An unexpected SQL Exception has been encountered. Action Examine the SQL Exception Message to determine the cause of the problem.
CWUDU0138E: Could not delete minimal entity for tModel with tModelKey[{0}].
Explanation The entity with the supplied tModel key could not be located and therefore deleted. Action Ensure tModel key is correct.
CWUDU0139E: Could not delete minimal entity for Service with serviceKey[{0}].
Explanation The entity with the supplied Service key could not be located and therefore deleted. Action Ensure Service key is correct.
CWUDU0140E: Could not delete minimal entity for Business with businessKey[{0}].
Explanation The entity with the supplied Business key could not be located and therefore deleted. Action Ensure Business key is correct.
CWUDU0141E: Could not delete minimal entity for Binding with bindingKey[{0}].
Explanation The entity with the supplied Binding key could not be located and therefore deleted. Action Ensure Binding key is correct.
CWUDU0142E: Invalid sequence number for service: {0}.
Explanation The ServiceStub has a sequence number that is not valid. Action Ensure the sequence number is greater than zero.
CWUDU0143E: Invalid sequence number for binding: {0}.
Explanation The BindingStub has a sequence number that is not valid. Action Ensure the sequence number is greater than zero.
CWUDU0144E: The configured JSSE Provider ({0}) could not be found.
Explanation The JSSE Provider class name given in the jsse.provider property cannot be loaded. Action Check that the class name is correct, for example com.ibm.jsse.IBMJSSEProvider and the jar that contains the class has been defined in the class path property.
CWUDU0145E: The configured JSSE Provider ({0}) could not be instantiated.
Explanation The JSSE Provider class name given in the jsse.provider property cannot be instantiated. Action Check that the class name is not an interface or abstract class.
CWUDU0146E: The configured JSSE Provider ({0}) could not be accessed during instantiation.
Explanation The JSSE Provider class constructor for the class given in the jsse.provider property cannot be accessed. Action Check that the class name is correct, for example com.ibm.jsse.IBMJSSEProvider and that the class has a public zero parameter constructor.