WebSphere Process Server messages     Operating Systems: All supported

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
Problem This is the usage message displayed at the command line when the user has entered an invalid combination of arguments or options.
User response Enter the command according to the usage message.
CWUDU0002I: ********** Starting UDDI Utility Tools **********
Problem This message is used as a marker in the message log file to indicate tool start points.
User response None.
CWUDU0003I: Promoting entityType<{0}> key<{1}>...
Problem Indicates which entity type (business, tModel etc.) is being promoted, and it's key value.
User response None.
CWUDU0004W: Bad entityType: received<{0}>, expected <tModel|business|service|binding>
Problem The user entered an incorrect entity type.
User response Use an entity type of tModel, business, service or binding.
CWUDU0005I: Promotion successful.
Problem Indicates the promote function completed successfully.
User response None.
CWUDU0006I: Import successful.
Problem Indicates the import function completed successfully.
User response None.
CWUDU0007I: Export successful.
Problem Indicates the export function completed successfully.
User response None.
CWUDU0008I: Delete successful.
Problem Indicates the delete function completed successfully.
User response None.
CWUDU0009I: Exporting entities...
Problem Indicates the export function has started.
User response None.
CWUDU0010I: Exporting business, businessKey[{0}].
Problem Indicates that the businessEntity with the specified key is being exported.
User response None.
CWUDU0011I: Exporting service, serviceKey[{0}].
Problem Indicates that the businessService with the specified key is being exported.
User response None.
CWUDU0012I: Exporting binding, bindingKey[{0}].
Problem Indicates that the bindingTemplate with the specified key is being exported.
User response None.
CWUDU0013I: Exporting tModel, tModelKey[{0}].
Problem Indicates that the tModel with the specified key is being exported.
User response None.
CWUDU0014I: Exporting referenced tModel, tModelKey[{0}].
Problem Indicates that the referenced tModel with the specified key is being exported.
User response None.
CWUDU0015I: Exported {0} entities.
Problem Indicates that the export function completed, and shows the number of entities exported.
User response None.
CWUDU0016I: Importing entities...
Problem Indicates the import function has started.
User response None.
CWUDU0017I: Importing business, businessKey[{0}].
Problem Indicates that the businessEntity with the specified key is being imported.
User response None.
CWUDU0018I: Importing service, serviceKey[{0}].
Problem Indicates that the businessService with the specified key is being imported.
User response None.
CWUDU0019I: Importing binding, bindingKey[{0}].
Problem Indicates that the bindingTemplate with the specified key is being imported.
User response None.
CWUDU0020I: Importing tModel, tModelKey[{0}].
Problem Indicates that the tModel with the specified key is being imported.
User response None.
CWUDU0021I: Importing referenced tModel, tModelKey[{0}].
Problem Indicates that the referenced tModel with the specified key is being imported.
User response None.
CWUDU0022I: Imported {0} entities.
Problem Indicates that the import function completed, and shows the number of entities imported.
User response None.
CWUDU0023I: Deleting entities...
Problem Indicates the delete function has started.
User response None.
CWUDU0024I: Deleting business, businessKey[{0}].
Problem Indicates that the businessEntity with the specified key is being deleted.
User response None.
CWUDU0025I: Deleting service, serviceKey[{0}].
Problem Indicates that the businessService with the specified key is being deleted.
User response None.
CWUDU0026I: Deleting binding, bindingKey[{0}].
Problem Indicates that the bindingTemplate with the specified key is being deleted.
User response None.
CWUDU0027I: Deleting tModel, tModelKey[{0}].
Problem Indicates that the tModel with the specified key is being deleted.
User response None.
CWUDU0028I: Deleted {0} entities.
Problem Indicates that the delete function completed, and shows the number of entities deleted.
User response None.
CWUDU0029I: Serializing...
Problem Indicates that generation of the Entity Definition File has started.
User response None.
CWUDU0030I: Serialized entities.
Problem Indicates that generation of the Entity Definition File completed successfully.
User response None.
CWUDU0031I: Deserializing...
Problem Indicates that reading of the Entity Definition File and creation of UDDI entities has started.
User response None.
CWUDU0032I: Deserialized entities.
Problem Indicates that reading of the Entity Definition File and creation of UDDI entities completed successfully.
User response None.
CWUDU0033I: Function ''{0}'' completed successfully.
Problem Indicates the requested function completed successfully.
User response None.
CWUDU0034W: Function ''{0}'' did not complete successfully. See messages log for further information.
Problem Indicates the requested function did not complete successfully.
User response 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}
Problem The XML parser reports a warning about the content of the Entity Definition File.
User response Based on the context of the warning message, check the validity of the Entity Definition File.
CWUDU0036E: Parser error: {0}
Problem The XML parser reports an error about the content of the Entity Definition File.
User response Based on the context of the error message, check the validity of the Entity Definition File.
CWUDU0037E: Unrecognized parser feature: {0}
Problem A parser feature set by the UDDI Utility Tools is not recognized by the parser.
User response Check you are using the correct type and level of XML parser. If correct, contact your IBM support center.
CWUDU0038E: Unsupported parser feature: {0}
Problem A parser feature set by the UDDI Utility Tools is not supported by the parser.
User response 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}
Problem A parser property set by the UDDI Utility Tools is not recognized by the parser.
User response 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}
Problem A parser property set by the UDDI Utility Tools is not supported by the parser.
User response Check you are using the correct type and level of XML parser. If correct, contact your IBM support center.
CWUDU0042E: Unable to find the configuration file: {0}
Problem UDDI Utility Tools cannot locate the specified configuration file.
User response 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.
Problem The configuration file could not be read.
User response 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.
Problem A required property is missing from the configuration file.
User response 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''.
Problem A value was given to a property other than 'true' or 'false'.
User response Set the property value to 'true' or 'false'.
CWUDU0046W: Property: ''{0}'' has value ''{1}''. It must be an integer value.
Problem A value was given to a property other than an integer value.
User response Set the property value to an integer value.
CWUDU0047E: Unable to find the keyFile file: {0}
Problem The keys file could not be located at the specified path.
User response Check the file name and path are correct and that the file exists.
CWUDU0048E: Unable to read the keyFile file: {0}
Problem The keys file could not be read due to an IO error.
User response Check that the current user has permission to read the file.
CWUDU0049E: Unable to write to entity definition file: {0}
Problem During serialization, the Entity Definition File could not be written to.
User response Check the file's read only attribute is not set.
CWUDU0050E: Unable to find UDDI Entity definition file. {0}
Problem The Entity Definition File could not be found at the specified file path.
User response Check the file path is correct and that the file exists.
CWUDU0051E: Unable to read UDDI Entity definition file. {0}
Problem The Entity Definition File could not be read due to an IO error.
User response Check that the current user has permission to read the file.
CWUDU0052E: Unable to close the messages file: {0}
Problem The attempt to close the message log file failed.
User response 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}
Problem The attempt to close the trace log file failed.
User response 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}
Problem The UDDI Utility Tools logger could not find the specified file.
User response None.
CWUDU0056E: Exception:
Problem General purpose message prefix used for reporting exceptions.
User response None.
CWUDU0057W: Only one function may be specified on the command line.
Problem Multiple function commands were entered on the command line.
User response Specify one function in accordance with the usage message.
CWUDU0058W: No function was specified.
Problem UDDI Utility Tools was invoked with no function specified.
User response Specify one function in accordance with the usage message.
CWUDU0059W: The function: {0} was not recognised.
Problem The function value did not match any of the allowed functions.
User response Specify one function in accordance with the usage message.
CWUDU0060W: The argument ''{0}'' was not recognised.
Problem The argument value does not match any of the allowed arguments.
User response Specify arguments in accordance with the usage message.
CWUDU0061W: There was a missing value for {0} argument.
Problem An expected value for the specified argument was not supplied.
User response Specify a value for the argument in accordance with the usage message.
CWUDU0062W: Unexpected argument: {0} (entity key file is already specified).
Problem The entity type argument cannot be specified if the keysFile argument has already been supplied.
User response Specify arguments in accordance with the usage message.
CWUDU0063W: Unexpected argument: {0} (entity key is already specified).
Problem The keysFile argument cannot be specified if an entity type argument and key value has already been supplied.
User response Specify arguments in accordance with the usage message.
CWUDU0064W: Argument: {0} cannot be specified more than once.
Problem An argument was specified twice in the same command.
User response Specify arguments in accordance with the usage message.
CWUDU0065E: No entity keys were specified.
Problem A keys file or an entity type and key value must be specified for functions using keys.
User response Specify arguments in accordance with the usage message.
CWUDU0066E: Could not load Database driver: dbDriver< {0} >.
Problem The specified database driver could not be loaded.
User response Check the database driver value in the configuration file is valid, and the driver's class is present in the classpath property.
CWUDU0067E: Could not create Database connection: dbUrl<{0}>, dbUser<{1}>, (dbPasswd not shown).
Problem A connection could not be established with the database at the specified URL with the specified userid.
User response 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.
Problem An attempt to close the database connection failed.
User response If the problem persists, contact your IBM support center.
CWUDU0069E: Could not create minimal entity for tModel with tModelKey[{0}].
Problem The minimal data necessary for a valid tModel could not be inserted in the target UDDI registry database.
User response 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}].
Problem The minimal data necessary for a valid businessService could not be inserted in the target UDDI registry database.
User response 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}].
Problem The minimal data necessary for a valid businessEntity could not be inserted in the target UDDI registry database.
User response 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}].
Problem The minimal data necessary for a valid bindingTemplate could not be inserted in the target UDDI registry database.
User response 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.
Problem An attempt to create the Entity Definition File failed.
User response 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.
Problem An unspecified error occurred when parsing the Entity Definition File.
User response 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.
Problem Errors occurred when parsing the Entity Definition File.
User response 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.
Problem Warnings occurred when parsing the Entity Definition File.
User response 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.
Problem An unexpected Exception occurred when trying to discover the publisher.
User response Turn on trace logging and look for the Exception that is recorded.
CWUDU0078E: Unable to obtain authinfo.
Problem AuthInfo could not be obtained from the UDDI registry with the given userid and password.
User response Check the userid and password property values are correct in the configuration file.
CWUDU0079E: The inquiryURL is malformed: {0}
Problem The inquiry URL specified in the configuration file is not valid.
User response Correct the value for the inquiry URLs (fromInquiryURL and toInquiryURL) in the configuration file.
CWUDU0080E: The publishURL is malformed: {0}
Problem The publish URL specified in the configuration file is not valid.
User response Correct the value for the publish URL (toPublishURL)in the configuration file.
CWUDU0081E: Could not get tModel detail for tModelKey[{0}].
Problem The get tModel operation failed on the source registry.
User response Check the key exists in the source registry.
CWUDU0082E: Could not get service detail for serviceKey[{0}].
Problem The get service operation failed on the source registry.
User response Check the key exists in the source registry.
CWUDU0083E: Could not get business detail for businessKey[{0}].
Problem The get business operation failed on the source registry.
User response Check the key exists in the source registry.
CWUDU0084E: Could not get binding detail for bindingKey[{0}].
Problem The get binding operation failed on the source registry.
User response Check the key exists in the source registry.
CWUDU0085E: Could not save tModel for tModelKey[{0}].
Problem The publish operation failed at the target registry.
User response 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}].
Problem The publish operation failed at the target registry.
User response 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}].
Problem The publish operation failed at the target registry.
User response Check the businessEntity specified as the parent of the businessService exists in the target registry.
CWUDU0088E: Could not save binding for parent serviceKey[{0}].
Problem The publish operation failed at the target registry.
User response 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.
Problem The parent business for the specified businessService does not exist
User response 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.
Problem The parent service for the specified bindingTemplate does not exist
User response 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}].
Problem The UDDI4J operation to delete the businessEntity with the specified key failed.
User response 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}].
Problem The UDDI4J operation to delete the businessService with the specified key failed.
User response 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}].
Problem The UDDI4J operation to delete the bindingTemplate with the specified key failed.
User response 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}].
Problem The UDDI4J operation to delete the tModel with the specified key failed.
User response 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}.
Problem The UDDI Registry could not be contacted.
User response Check the correct URLs are specified in the UDDIUtilityTools.properties file.
CWUDU0096W: {0} is not a valid UUID.
Problem The key value entered does not comply with the format specified for a UUID in the UDDI specification.
User response 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.
Problem The tModel was not saved because the overwrite property is false.
User response 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.
Problem The businessEntity was not saved because the overwrite property is false.
User response 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.
Problem The businessService was not saved because the overwrite property is false.
User response 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.
Problem The bindingTemplate was not saved because the overwrite property is false.
User response 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>
Problem The entered entity type was not recognized.
User response Specify arguments in accordance with the usage message.
CWUDU0102E: Promotion failed.
Problem The promote function failed to complete.
User response Check the configuration properties file has correct settings.
CWUDU0103E: Error occurred while creating results file.
Problem A problem occurred when writing the results file.
User response Turn on trace logging and look for the Exception that is recorded.
CWUDU0104E: Minimal entity creation failed.
Problem An unexpected error occured when creating the entity.
User response Turn on trace logging and look for the Exception that is recorded.
CWUDU0105E: Rollback failed.
Problem The rollback operation failed with an Exception.
User response Turn on trace logging and look for the Exception that is recorded.
CWUDU0106E: Unable to commit transaction.
Problem The insertion of minimal entity data during the import function failed to commit to the database.
User response 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.
Problem UDDI Utility Tools needs to control commits of data changes, however the attempt to turn off auto-commit failed.
User response 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.
Problem An imported UDDI entity is not correctly constructed.
User response Examine the import file for UDDI entity errors.
CWUDU0109W: The import function requires a UDDI entity definition file to be specified.
Problem A required argument value was not supplied.
User response 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.
Problem 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.
User response 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.
Problem An unexpected SQLException occurred preparing a SQL statement for execution.
User response Turn on trace logging and look for the SQLException that is recorded.
CWUDU0112E: An unexpected exception has occurred: {0}
Problem An unexpected error occurred.
User response 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}
Problem A TransPortException occurred while performing an UDDI4J operation on the UDDI registry at the specified URL.
User response Check configuration properties for the UDDI registry in question and ensure the UDDI registry is active.
CWUDU0114E: An IOException occurred trying to invoke 'java'.
Problem When UDDI Utility Tools was invoked using the java -jar syntax, the invocation of the second JVM failed.
User response 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.
Problem Indicate that the import step of the import or promote function has completed, showing the number of entities imported.
User response None.
CWUDU0116W: Not all minimal entities could be removed. The following remain in the database:
Problem 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.
User response 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.
CWUDU0117W: Business minimal entity with businessKey [{0}] has not been removed from the database.
Problem A business minimal entity was orphaned in the target registry database and attempts to remove it failed.
User response 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.
Problem A service minimal entity was orphaned in the target registry database and attempts to remove it failed.
User response 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.
Problem A binding minimal entity was orphaned in the target registry database and attempts to remove it failed.
User response 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.
Problem A tModel minimal entity was orphaned in the target registry database and attempts to remove it failed.
User response 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}].
Problem Indicates the minimal data required for a businessEntity has successfully been inserted in the target UDDI registry database.
User response None.
CWUDU0122I: Created service minimal entity with serviceKey [{0}].
Problem Indicates the minimal data required for a businessService has successfully been inserted in the target UDDI registry database.
User response None.
CWUDU0123I: Created binding template minimal entity with bindingKey [{0}].
Problem Indicates the minimal data required for a bindingTemplate has successfully been inserted in the target UDDI registry database.
User response None.
CWUDU0124I: Created tModel minimal entity with tModelKey [{0}].
Problem Indicates the minimal data required for a tModel has successfully been inserted in the target UDDI registry database.
User response None.
CWUDU0125I: Deleted business minimal entity with businessKey [{0}].
Problem 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.
User response None.
CWUDU0126I: Deleted service minimal entity with serviceKey [{0}].
Problem 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.
User response None.
CWUDU0127I: Deleted binding template minimal entity with bindingKey [{0}].
Problem 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.
User response None.
CWUDU0128I: Deleted tModel minimal entity with tModelKey [{0}].
Problem 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.
User response None.
CWUDU0129E: Find related businesses failed.
Problem The UDDI4J find related businesses operation did not complete.
User response Check the configuration properties for the source registry, such as fromInquiryURL.
CWUDU0130E: Find businesses failed.
Problem The UDDI4J find businesses operation did not complete.
User response Check the configuration properties for the source registry, such as fromInquiryURL.
CWUDU0131E: Find services failed.
Problem The UDDI4J find services operation did not complete.
User response Check the configuration properties for the source registry, such as fromInquiryURL.
CWUDU0132E: Find tModels failed.
Problem The UDDI4J find tModels operation did not complete.
User response Check the configuration properties for the source registry, such as fromInquiryURL.
CWUDU0133E: Find bindings failed.
Problem The UDDI4J find bindings operation did not complete.
User response Check the configuration properties for the source registry, such as fromInquiryURL.
CWUDU0134I: Performing inquiry request...
Problem Indicates the find operation for selecting keys has started.
User response None.
CWUDU0135I: Extracted keys from inquiry results.
Problem Indicates the find operation to select keys has completed successfully.
User response None.
CWUDU0136E: node ID value could not be found in UDDI database.
Problem The UDDI Registries Node ID could not be found in the UDDI database.
User response Check that the UDDI application and database have initialized correctly.
CWUDU0137E: Unexpected database SQL exception: {0}.
Problem An unexpected SQL Exception has been encountered.
User response Examine the SQL Exception Message to determine the cause of the problem.
CWUDU0138E: Could not delete minimal entity for tModel with tModelKey[{0}].
Problem The entity with the supplied tModel key could not be located and therefore deleted.
User response Ensure tModel key is correct.
CWUDU0139E: Could not delete minimal entity for Service with serviceKey[{0}].
Problem The entity with the supplied Service key could not be located and therefore deleted.
User response Ensure Service key is correct.
CWUDU0140E: Could not delete minimal entity for Business with businessKey[{0}].
Problem The entity with the supplied Business key could not be located and therefore deleted.
User response Ensure Business key is correct.
CWUDU0141E: Could not delete minimal entity for Binding with bindingKey[{0}].
Problem The entity with the supplied Binding key could not be located and therefore deleted.
User response Ensure Binding key is correct.
CWUDU0142E: Invalid sequence number for service: {0}.
Problem The ServiceStub has an invalid sequence number.
User response Ensure the sequence number is greater than zero.
CWUDU0143E: Invalid sequence number for binding: {0}.
Problem The BindingStub has an invalid sequence number.
User response Ensure the sequence number is greater than zero.
CWUDU0144E: The configured JSSE Provider ({0}) could not be found.
Problem The JSSE Provider class name given in the jsse.provider property can not be loaded.
User response 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.
CWUDU0145E: The configured JSSE Provider ({0}) could not be instantiated.
Problem The JSSE Provider class name given in the jsse.provider property can not be instantiated.
User response Check that the class name is not an interface or abstract class.
CWUDU0146E: The configured JSSE Provider ({0}) could not be accessed during instantiation.
Problem The JSSE Provider class constructor for the class given in the jsse.provider property can not be accessed.
User response Check that the class name is correct e.g. com.ibm.jsse.IBMJSSEProvider and that the class has a public zero parameter constructor.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.uddi.promoter.Messages.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)