<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="../../resources/stylesheets/wasmsgxml.css"?>
<TMSSource name="TivoliMessages" tmsVersion="1.0" xml:lang="en">
<!-- CMVC MSG File Name = UDDI/ws/code/uddi.core/src/com/ibm/uddi/ras/UDDIMessages.nlsprops, -->
<!-- DO NOT EDIT THIS FILE - This file was generated by the XML/Html & Property emitter -->
<!-- BEGIN MESSAGES -->
<Message ID="CWUDT0003E" severity="E" prefix="yes">
  <MsgText pgmKey="TransactionManagerProcessInTransaction_3_Error" varFormat="Java">
    TransactionManagerProcessInTransaction_3_Error=CWUDT0003E: UDDIFatalErrorException processing request.
  </MsgText>
  <Explanation>
    An error occurred while processing a UDDI Version 3 SOAP request.
  </Explanation>
  <UserResponse>
    Check the validity of the UDDI request.
  </UserResponse>
</Message>
<Message ID="CWUDM0104E" severity="E" prefix="yes">
  <MsgText pgmKey="error.property.update.failed" varFormat="Java">
    error.property.update.failed=CWUDM0104E: Unable to update configuration property with ID: {0}.
  </MsgText>
  <Explanation>
    This might occur if the updated property object shown in the message cannot be validated. See the accompanying error messages for more information. Alternatively, a database error might have occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0194I" severity="I" prefix="yes">
  <MsgText pgmKey="info.vs.unload" varFormat="Java">
    info.vs.unload=CWUDM0194I: Unloaded value set for tModel key {0}.
  </MsgText>
  <Explanation>
    The administrative operation described in the message completed successfully.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0060E" severity="E" prefix="yes">
  <MsgText pgmKey="error.user.getMultiple.failed" varFormat="Java">
    error.user.getMultiple.failed=CWUDM0060E: Unable to retrieve collection of UDDI publishers.
  </MsgText>
  <Explanation>
    A database error occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0122E" severity="E" prefix="yes">
  <MsgText pgmKey="error.policy.getPolicyGroup.failed" varFormat="Java">
    error.policy.getPolicyGroup.failed=CWUDM0122E: Unable to get policy group with group ID: {0}
  </MsgText>
  <Explanation>
    A database error occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDS0008E" severity="E" prefix="yes">
  <MsgText pgmKey="UDSP0008E_PersistenceRelError" varFormat="Java">
    UDSP0008E_PersistenceRelError=CWUDS0008E: Error during servlet release of persistence layer.
  </MsgText>
  <Explanation>
    The persistence layer reported a problem when the SOAP servlet attempted to release it.
  </Explanation>
  <UserResponse>
    Restart the UDDI registry.  If the error continues, examine the Application Server logs for information about its cause.
  </UserResponse>
</Message>
<Message ID="CWUDN0012E" severity="E" prefix="yes">
  <MsgText pgmKey="NodeManagerTxnlDestroy_2_Error" varFormat="Java">
    NodeManagerTxnlDestroy_2_Error=CWUDN0012E: Error, NodeManager destroy UDDIException during destroy.
  </MsgText>
  <Explanation>
    An exception occurred when the UDDI application was stopping.  This problem will not affect any subsequent UDDI restarts.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0142E" severity="E" prefix="yes">
  <MsgText pgmKey="error.vs.getProperty.failed" varFormat="Java">
    error.vs.getProperty.failed=CWUDM0142E: Unable to get value set property: {1} for value set with tModel key: {0}.
  </MsgText>
  <Explanation>
    The value set property ID or tModel key supplied was not recognized.
  </Explanation>
  <UserResponse>
    Supply a valid value set property ID and tModel key.
  </UserResponse>
</Message>
<Message ID="CWUDM0149E" severity="E" prefix="yes">
  <MsgText pgmKey="error.vs.updateMultiple.failed" varFormat="Java">
    error.vs.updateMultiple.failed=CWUDM0149E: Could not update value set status with tModel key: {0}.
  </MsgText>
  <Explanation>
    One of the supplied value set status objects contained a tModel key that was not recognized.
  </Explanation>
  <UserResponse>
    Supply tModel keys for value set tModels that exist. Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0123E" severity="E" prefix="yes">
  <MsgText pgmKey="error.policy.getPolicyGroups.failed" varFormat="Java">
    error.policy.getPolicyGroups.failed=CWUDM0123E: Unable to retrieve collection of policy groups.
  </MsgText>
  <Explanation>
    A database error occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0192I" severity="I" prefix="yes">
  <MsgText pgmKey="info.vs.loadFile" varFormat="Java">
    info.vs.loadFile=CWUDM0192I: Loaded value set for tModel key {0} from file {1}.
  </MsgText>
  <Explanation>
    The administrative operation described in the message completed successfully.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0070E" severity="E" prefix="yes">
  <MsgText pgmKey="error.tier.create.failed" varFormat="Java">
    error.tier.create.failed=CWUDM0070E: Unable to create tier with ID: {0}.
  </MsgText>
  <Explanation>
    A database error occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDG0012E" severity="E" prefix="yes">
  <MsgText pgmKey="UDUC0012E_DBConnectionFailed" varFormat="Java">
    UDUC0012E_DBConnectionFailed=CWUDG0012E: User console initialisation failed to connect to UDDI database. Exception: {0}
  </MsgText>
  <Explanation>
    During user console initialization, connection to the database failed, and threw the exception specified.
  </Explanation>
  <UserResponse>
    Check the connection to the UDDI database. Examine the exception message to help to resolve the problem.
  </UserResponse>
</Message>
<Message ID="CWUDQ1002E" severity="E" prefix="yes">
  <MsgText pgmKey="MigrationDisplayKeyValues" varFormat="Java">
    MigrationDisplayKeyValues=CWUDQ1002E: Table {0} values are: {1}
  </MsgText>
  <Explanation>
    This message shows the significant key values of the row being migrated into the specified database table.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDG0009E" severity="E" prefix="yes">
  <MsgText pgmKey="UDUC0009E_UddiGuiInvalidValueException" varFormat="Java">
    UDUC0009E_UddiGuiInvalidValueException=CWUDG0009E: An invalid value was supplied. error message: &lt;{0}&gt; error: {1} More information: {2}
  </MsgText>
  <Explanation>
    A value that was passed to an API call was not valid. Examine the error message, error type, and additional information to help to resolve the problem.
  </Explanation>
  <UserResponse>
    If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="CWUDM0025I" severity="I" prefix="yes">
  <MsgText pgmKey="error.node.activate.invalidState" varFormat="Java">
    error.node.activate.invalidState=CWUDM0025I: Unable to activate a UDDI node that is not initialized.
  </MsgText>
  <Explanation>
    The UDDI node must be initialized, and in deactivated state, before it can be activated.
  </Explanation>
  <UserResponse>
    If the UDDI node is ready to be initialized, start the initialization operation.
  </UserResponse>
</Message>
<Message ID="CWUDM0029I" severity="I" prefix="yes">
  <MsgText pgmKey="error.node.init.missingRequired" varFormat="Java">
    error.node.init.missingRequired=CWUDM0029I: Unable to initialize UDDI node because a required property is missing or invalid: {0}.
  </MsgText>
  <Explanation>
    A configuration property that is required for UDDI node initialization has not been supplied.
  </Explanation>
  <UserResponse>
    Supply a value for the required property.
  </UserResponse>
</Message>
<Message ID="CWUDG0004I" severity="I" prefix="yes">
  <MsgText pgmKey="UDUC0004I_UddiGuiInitReadFinish" varFormat="Java">
    UDUC0004I_UddiGuiInitReadFinish=CWUDG0004I: Finished reading init parameters.
  </MsgText>
  <Explanation>
    The user console control servlet has finished reading external parameters during initialization. The user console is ready to accept client requests.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDQ0001I" severity="I" prefix="yes">
  <MsgText pgmKey="MigrationDatabasePresent" varFormat="Java">
    MigrationDatabasePresent=CWUDQ0001I: UDDI registry migration datasource is present
  </MsgText>
  <Explanation>
    The UDDI migration data source is defined when UDDI is started.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0187I" severity="I" prefix="yes">
  <MsgText pgmKey="info.tier.update" varFormat="Java">
    info.tier.update=CWUDM0187I: Tier {0} was updated.
  </MsgText>
  <Explanation>
    A UDDI tier has been updated.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDS0011E" severity="E" prefix="yes">
  <MsgText pgmKey="E_doGet_1_Error" varFormat="Java">
    E_doGet_1_Error=CWUDS0011E: incomplete URL receieved processing doGet Request.
  </MsgText>
  <Explanation>
    An incomplete or incorrect UDDI Version 3 GET request was received.
  </Explanation>
  <UserResponse>
    Check that the UDDI Version 3 GET request URL is valid.
  </UserResponse>
</Message>
<Message ID="CWUDM0124E" severity="E" prefix="yes">
  <MsgText pgmKey="error.policy.updateMultiple.failed" varFormat="Java">
    error.policy.updateMultiple.failed=CWUDM0124E: Unable to update policies.
  </MsgText>
  <Explanation>
    This might occur if an updated policy object cannot be validated. See the accompanying error messages for more information. Alternatively, a database error might have occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Ensure all policy IDs and values are valid. Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDS0005E" severity="E" prefix="yes">
  <MsgText pgmKey="UDSP0005E_ParserCreationError" varFormat="Java">
    UDSP0005E_ParserCreationError=CWUDS0005E: Error occurred during parser creation.
  </MsgText>
  <Explanation>
    An unspecified error occurred during the creation of a SOAP parser.
  </Explanation>
  <UserResponse>
    Restart the UDDI registry.  If the error continues, examine the Application Server logs for information about its cause.
  </UserResponse>
</Message>
<Message ID="CWUDN0001I" severity="I" prefix="yes">
  <MsgText pgmKey="NodeManagerStateChangeOK" varFormat="Java">
    NodeManagerStateChangeOK=CWUDN0001I: UDDI Node State change, new state: {0}
  </MsgText>
  <Explanation>
    The UDDI registry node has changed to the new state shown in the message.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDG0007E" severity="E" prefix="yes">
  <MsgText pgmKey="UDUC0007E_UddiGuiUserMismatchException" varFormat="Java">
    UDUC0007E_UddiGuiUserMismatchException=CWUDG0007E: A User mismatch error has occurred. error message: &lt;{0}&gt; error: {1} More information: {2}
  </MsgText>
  <Explanation>
    The user id provided does not match the user id required or expected while performing an operation that requires authentication. Examine the error message, error type, and additional information to help to resolve the problem.
  </Explanation>
  <UserResponse>
    Check that the user has authority for the operation that was requested.
  </UserResponse>
</Message>
<Message ID="CWUDQ1004E" severity="E" prefix="yes">
  <MsgText pgmKey="MigrationRowsNotMigrated" varFormat="Java">
    MigrationRowsNotMigrated=CWUDQ1004E: {0} rows not inserted into table {1} due to errors
  </MsgText>
  <Explanation>
    This message shows the number of database rows that were not converted for the specified UDDI table.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0184I" severity="I" prefix="yes">
  <MsgText pgmKey="info.user.update" varFormat="Java">
    info.user.update=CWUDM0184I: UDDI publisher {0} was updated.
  </MsgText>
  <Explanation>
    A UDDI publisher has been updated.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0061E" severity="E" prefix="yes">
  <MsgText pgmKey="error.user.getTier.failed" varFormat="Java">
    error.user.getTier.failed=CWUDM0061E: Unable to get tier assigned to UDDI publisher with user name {0}.
  </MsgText>
  <Explanation>
    The UDDI publisher with the specified user name might not exist, or a database error might have occurred when performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check that the UDDI publisher exists. If it does, check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDS0003W" severity="W" prefix="yes">
  <MsgText pgmKey="UDSP0003W_InitParmNotFound" varFormat="Java">
    UDSP0003W_InitParmNotFound=CWUDS0003W: Servlet unable to locate init parameter &apos;defaultPoolSize&apos;. Using internal defaults.
  </MsgText>
  <Explanation>
    The SOAP servlet could not locate the init parameter, which sets the default size of the ParserPool. It will use an internal default setting.
  </Explanation>
  <UserResponse>
    If this message occurred after attempting to change the defaultPoolSize init parameter, ensure that the changes were correct. If this message occurred after installation, ensure that installation was performed correctly.
  </UserResponse>
</Message>
<Message ID="CWUDN0008E" severity="E" prefix="yes">
  <MsgText pgmKey="NodeManagerTxnlInit_5_Error" varFormat="Java">
    NodeManagerTxnlInit_5_Error=CWUDN0008E: Error, NodeManager initialization Throwable.
  </MsgText>
  <Explanation>
    An exception occurred during initialization of the UDDI node manager.
  </Explanation>
  <UserResponse>
    Restart the UDDI registry.  If the error continues, examine the Application Server logs for information about its cause.
  </UserResponse>
</Message>
<Message ID="CWUDN0004E" severity="E" prefix="yes">
  <MsgText pgmKey="NodeManagerTxnlInit_1_Error" varFormat="Java">
    NodeManagerTxnlInit_1_Error=CWUDN0004E: Error, NodeManager initialization failed getting PersisterControl.
  </MsgText>
  <Explanation>
    The UDDI node manager could not access the UDDI database.
  </Explanation>
  <UserResponse>
    Restart the UDDI registry.  If the error continues, examine the Application Server logs for information about its cause.
  </UserResponse>
</Message>
<Message ID="CWUDS0007E" severity="E" prefix="yes">
  <MsgText pgmKey="UDSP0007E_PersistenceError" varFormat="Java">
    UDSP0007E_PersistenceError=CWUDS0007E: Error during servlet acquisition of persistence layer.
  </MsgText>
  <Explanation>
    The SOAP servlet could not acquire the persistence layer required for it to communicate with the UDDI data source.
  </Explanation>
  <UserResponse>
    Restart the UDDI registry.  If the error continues, examine the Application Server logs for information about its cause.
  </UserResponse>
</Message>
<Message ID="CWUDS0001E" severity="E" prefix="yes">
  <MsgText pgmKey="UDSP0001E_ParserPoolEmpty" varFormat="Java">
    UDSP0001E_ParserPoolEmpty=CWUDS0001E: ParserPool found empty while attempting to process request. Request unsatisfied.
  </MsgText>
  <Explanation>
    A SOAP request was received, but could not be dealt with, because there were no free Parsers in the ParserPool.
  </Explanation>
  <UserResponse>
    Consider increasing the number of Parsers in the ParserPool by modifying the init parameter on the SOAP servlets.
  </UserResponse>
</Message>
<Message ID="CWUDM0023E" severity="E" prefix="yes">
  <MsgText pgmKey="error.node.description.failed" varFormat="Java">
    error.node.description.failed=CWUDM0023E: Unable to retrieve UDDI node description.
  </MsgText>
  <Explanation>
    A database error occurred.
  </Explanation>
  <UserResponse>
    Check the connection to the UDDI database and the installation configuration of the UDDI application.
  </UserResponse>
</Message>
<Message ID="CWUDM0195I" severity="I" prefix="yes">
  <MsgText pgmKey="info.vs.updatedStatus" varFormat="Java">
    info.vs.updatedStatus=CWUDM0195I: Updated value set supported status for tModel key {0} to {1}.
  </MsgText>
  <Explanation>
    The administrative operation described in the message completed successfully.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0100E" severity="E" prefix="yes">
  <MsgText pgmKey="error.property.get.failed" varFormat="Java">
    error.property.get.failed=CWUDM0100E: Unable to get configuration property information for property with ID: {0}.
  </MsgText>
  <Explanation>
    A database error occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0053E" severity="E" prefix="yes">
  <MsgText pgmKey="error.user.delete.failed" varFormat="Java">
    error.user.delete.failed=CWUDM0053E: Unable to delete UDDI publisher with user name {0}.
  </MsgText>
  <Explanation>
    An error occurred trying to register the UDDI publisher.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDS0004W" severity="W" prefix="yes">
  <MsgText pgmKey="UDSP0004W_InitParmUnusable" varFormat="Java">
    UDSP0004W_InitParmUnusable=CWUDS0004W: Servlet unable to understand init parameter &apos;defaultPoolSize&apos;. Using internal defaults.
  </MsgText>
  <Explanation>
    The SOAP servlet could not parse the init parameter which sets the default size of the ParserPool. It will use an internal default setting.
  </Explanation>
  <UserResponse>
    If this message occurred after attempting to change the defaultPoolSize init parameter, ensure that the changes were correct. If this message occurred after installation, ensure that installation was performed correctly.
  </UserResponse>
</Message>
<Message ID="CWUDS0006E" severity="E" prefix="yes">
  <MsgText pgmKey="UDSP0006E_InternalConfigError" varFormat="Java">
    UDSP0006E_InternalConfigError=CWUDS0006E: Internal configuration error.
  </MsgText>
  <Explanation>
    This error might occur if there was a failure creating a parser, with accompanying message CWUDS0005. It might also occur if there was a problem acquiring the persistence layer.
  </Explanation>
  <UserResponse>
    Restart the UDDI registry.  If the error continues, examine the Application Server logs for information about its cause.
  </UserResponse>
</Message>
<Message ID="CWUDM0005E" severity="E" prefix="yes">
  <MsgText pgmKey="error.setupConnection.noControl" varFormat="Java">
    error.setupConnection.noControl=CWUDM0005E: MBean could not establish control with persistence manager.
  </MsgText>
  <Explanation>
    The UDDI administrative function cannot connect to the UDDI registry database.
  </Explanation>
  <UserResponse>
    Check the connection to the UDDI database and the installation configuration of the UDDI application.
  </UserResponse>
</Message>
<Message ID="CWUDM0181I" severity="I" prefix="yes">
  <MsgText pgmKey="info.node.deactivated" varFormat="Java">
    info.node.deactivated=CWUDM0181I: UDDI node was deactivated.
  </MsgText>
  <Explanation>
    The UDDI node is not ready to accept UDDI Application Programming Interface requests. This might occur when administrative tasks are updating configuration settings.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDN0007E" severity="E" prefix="yes">
  <MsgText pgmKey="NodeManagerTxnlInit_4_Error" varFormat="Java">
    NodeManagerTxnlInit_4_Error=CWUDN0007E: Error, NodeManager initialization Exception.
  </MsgText>
  <Explanation>
    An exception occurred during initialization of the UDDI node manager.
  </Explanation>
  <UserResponse>
    Restart the UDDI registry.  If the error continues, examine the Application Server logs for information about its cause.
  </UserResponse>
</Message>
<Message ID="CWUDM0180I" severity="I" prefix="yes">
  <MsgText pgmKey="info.node.activated" varFormat="Java">
    info.node.activated=CWUDM0180I: UDDI node was activated.
  </MsgText>
  <Explanation>
    The UDDI node is ready to accept UDDI Application Programming Interface requests.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0075E" severity="E" prefix="yes">
  <MsgText pgmKey="error.tier.update.failed" varFormat="Java">
    error.tier.update.failed=CWUDM0075E: Unable to update tier with ID: {0}.
  </MsgText>
  <Explanation>
    The tier with the specified ID might not exist, or a database error might have occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the tier ID. If it does exist, check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0107E" severity="E" prefix="yes">
  <MsgText pgmKey="error.node.getRequired.failed" varFormat="Java">
    error.node.getRequired.failed=CWUDM0107E: Failed to retrieve required properties from database.
  </MsgText>
  <Explanation>
    A database error occurred when trying to initialize a UDDI node.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0193I" severity="I" prefix="yes">
  <MsgText pgmKey="info.vs.load" varFormat="Java">
    info.vs.load=CWUDM0193I: Loaded value set for tModel key {0}.
  </MsgText>
  <Explanation>
    The administrative operation described in the message completed successfully.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDG0013E" severity="E" prefix="yes">
  <MsgText pgmKey="UDUC0013E_SetupTModelsFailed" varFormat="Java">
    UDUC0013E_SetupTModelsFailed=CWUDG0013E: User console initialisation failed to initialize tModels. Exception: {0}
  </MsgText>
  <Explanation>
    An error has occurred during initialization of ActionServlet, specifically when reading tModels (invoking the init method in class TModelNames).
  </Explanation>
  <UserResponse>
    Check the state of the UDDI database. Check that the TMODEL table is populated with valid data. Examine the exception message to help resolve the problem.
  </UserResponse>
</Message>
<Message ID="CWUDM0076E" severity="E" prefix="yes">
  <MsgText pgmKey="error.tier.usercount.failed" varFormat="Java">
    error.tier.usercount.failed=CWUDM0076E: Unable to get count of UDDI publishers for tier ID: {0}.
  </MsgText>
  <Explanation>
    The tier with the specified ID might not exist, or a database error might have occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the tier ID. If it does exist, check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0072E" severity="E" prefix="yes">
  <MsgText pgmKey="error.tier.getDetail.failed" varFormat="Java">
    error.tier.getDetail.failed=CWUDM0072E: Unable to retrieve information for tier with ID: {0}.
  </MsgText>
  <Explanation>
    The supplied tier ID might not be an integer, the tier with the ID might not exist, or of a database error might have occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the tier ID is an integer and the tier exists. If it does exist, check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0196I" severity="I" prefix="yes">
  <MsgText pgmKey="info.vs.changedKeys" varFormat="Java">
    info.vs.changedKeys=CWUDM0196I: Changed tModel key for value set from {0} to {1}.
  </MsgText>
  <Explanation>
    The administrative operation described in the message completed successfully.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0004E" severity="E" prefix="yes">
  <MsgText pgmKey="error.postInvoke.release" varFormat="Java">
    error.postInvoke.release=CWUDM0004E: MBean transaction connection failed to release.
  </MsgText>
  <Explanation>
    A connection was not released after a transaction was committed or rolled back.
  </Explanation>
  <UserResponse>
    Check the connection to the UDDI database and the installation configuration of the UDDI application.
  </UserResponse>
</Message>
<Message ID="CWUDM0009W" severity="W" prefix="yes">
  <MsgText pgmKey="error.register.exists" varFormat="Java">
    error.register.exists=CWUDM0009W: A UddiNode MBean is already registered.
  </MsgText>
  <Explanation>
    There is a UddiNode MBean registered in the same cell, node, and server.
  </Explanation>
  <UserResponse>
    Ensure that there is only one UDDI application deployed in the server.
  </UserResponse>
</Message>
<Message ID="CWUDM0147E" severity="E" prefix="yes">
  <MsgText pgmKey="error.vs.update.failed" varFormat="Java">
    error.vs.update.failed=CWUDM0147E: Could not update value set status with tModel key: {0}.
  </MsgText>
  <Explanation>
    The value set status object supplied is null or the tModel key is not known.
  </Explanation>
  <UserResponse>
    Supply a valid value set status object with  tModel key for a value set tModel that exists. Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDQ0002I" severity="I" prefix="yes">
  <MsgText pgmKey="MigrationStarted" varFormat="Java">
    MigrationStarted=CWUDQ0002I: UDDI registry migration has started {0} {1}
  </MsgText>
  <Explanation>
    The UDDI database migration process has started. This can take some time to complete, depending on the size of the database.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0001E" severity="E" prefix="yes">
  <MsgText pgmKey="admin.unexpected.error" varFormat="Java">
    admin.unexpected.error=CWUDM0001E: An unexpected error occurred performing the administrative operation: {0}. Exception: {1}.
  </MsgText>
  <Explanation>
    An internal error occurred during the specified administrative operation.
  </Explanation>
  <UserResponse>
    Check the connection to the UDDI database and the installation configuration of the UDDI application.
  </UserResponse>
</Message>
<Message ID="CWUDM0051E" severity="E" prefix="yes">
  <MsgText pgmKey="error.user.create.failed" varFormat="Java">
    error.user.create.failed=CWUDM0051E: Unable to create UDDI publisher with user name {0}.
  </MsgText>
  <Explanation>
    An error occurred trying to register the UDDI publisher.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0143E" severity="E" prefix="yes">
  <MsgText pgmKey="error.vs.getMultiple.failed" varFormat="Java">
    error.vs.getMultiple.failed=CWUDM0143E: Unable to retrieve value sets collection.
  </MsgText>
  <Explanation>
    A database error might have occurred.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDQ1005E" severity="E" prefix="yes">
  <MsgText pgmKey="MigrationSQLExceptionKeyExtraction" varFormat="Java">
    MigrationSQLExceptionKeyExtraction=CWUDQ1005E: SQL Exception during key value extraction: {0}
  </MsgText>
  <Explanation>
    An SQL exception occurred during the production of the CWUDQ1002E message.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0144E" severity="E" prefix="yes">
  <MsgText pgmKey="error.vs.isExisting.failed" varFormat="Java">
    error.vs.isExisting.failed=CWUDM0144E: Unable to determine if value set with tModel key: {0} exists.
  </MsgText>
  <Explanation>
    The tModel key supplied is not valid or a database error might have occurred.
  </Explanation>
  <UserResponse>
    Ensure that the tModel exists. Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDN0010E" severity="E" prefix="yes">
  <MsgText pgmKey="NodeManagerTxnlInit_7_Error" varFormat="Java">
    NodeManagerTxnlInit_7_Error=CWUDN0010E: Error, NodeManager initialization Throwable releasing connection.
  </MsgText>
  <Explanation>
    An exception occurred during initialization of the UDDI node manager when releasing the database connection.
  </Explanation>
  <UserResponse>
    Restart the UDDI registry.  If the error continues, examine the Application Server logs for information about its cause.
  </UserResponse>
</Message>
<Message ID="CWUDS0010E" severity="E" prefix="yes">
  <MsgText pgmKey="E_doPost_1_Error" varFormat="Java">
    E_doPost_1_Error=CWUDS0010E: Serious error while servlet attempting to process doPost Request.
  </MsgText>
  <Explanation>
    An error occurred processing a UDDI Version 1 or Version 2 SOAP request.
  </Explanation>
  <UserResponse>
    Check that the UDDI Version 1 or Version 2 SOAP request is valid.
  </UserResponse>
</Message>
<Message ID="CWUDM0190I" severity="I" prefix="yes">
  <MsgText pgmKey="info.policy.update" varFormat="Java">
    info.policy.update=CWUDM0190I: Policy {0} was updated to value {1}.
  </MsgText>
  <Explanation>
    The administrative operation described in the message completed successfully.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDT0002E" severity="E" prefix="yes">
  <MsgText pgmKey="TransactionManagerProcessInTransaction_2_Error" varFormat="Java">
    TransactionManagerProcessInTransaction_2_Error=CWUDT0002E: UDDIFatalErrorException processing request.
  </MsgText>
  <Explanation>
    A UDDI error occurred while processing a UDDI Version 3 SOAP request.
  </Explanation>
  <UserResponse>
    Check the validity of the UDDI request.
  </UserResponse>
</Message>
<Message ID="CWUDG0001I" severity="I" prefix="yes">
  <MsgText pgmKey="UDUC0001I_UddiGuiInitStart" varFormat="Java">
    UDUC0001I_UddiGuiInitStart=CWUDG0001I: {0} starting initialization.
  </MsgText>
  <Explanation>
    The user console control servlet is starting.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDG0005E" severity="E" prefix="yes">
  <MsgText pgmKey="UDUC0005E_UddiGuiUnknownError" varFormat="Java">
    UDUC0005E_UddiGuiUnknownError=CWUDG0005E: A serious error has occurred. error message: &lt;{0}&gt; error: {1} More information: {2}
  </MsgText>
  <Explanation>
    An unexpected error has occurred. Examine the error message, error type, and additional information to help to resolve the problem.
  </Explanation>
  <UserResponse>
    If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="CWUDG0010E" severity="E" prefix="yes">
  <MsgText pgmKey="UDUC0010E_UddiGuiIntrospectionFailed" varFormat="Java">
    UDUC0010E_UddiGuiIntrospectionFailed=CWUDG0010E: Failed to introspect ActionForm fields. Exception: {0}
  </MsgText>
  <Explanation>
    The contents of a form object cannot be checked for characters that are not valid.
  </Explanation>
  <UserResponse>
    If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="CWUDN0011E" severity="E" prefix="yes">
  <MsgText pgmKey="NodeManagerTxnlDestroy_1_Error" varFormat="Java">
    NodeManagerTxnlDestroy_1_Error=CWUDN0011E: Error, NodeManager destroy failed getting PersisterControl.
  </MsgText>
  <Explanation>
    An exception occurred when the UDDI application was stopping.  This problem will not affect any subsequent UDDI restarts.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDQ0004W" severity="W" prefix="yes">
  <MsgText pgmKey="MigrationError" varFormat="Java">
    MigrationError=CWUDQ0004W: UDDI registry not started due to migration errors
  </MsgText>
  <Explanation>
    The UDDI registry has not been activated because there were migration errors.
  </Explanation>
  <UserResponse>
    Examine the messages produced during the migration process and determine whether the problem is one that you can resolve, for example, the Version 2 database is shut down.If you can, resolve the problem, then re-create the Version 3 UDDI database and restart the UDDI application.
  </UserResponse>
</Message>
<Message ID="CWUDM0074E" severity="E" prefix="yes">
  <MsgText pgmKey="error.tier.setDefault.failed" varFormat="Java">
    error.tier.setDefault.failed=CWUDM0074E: Unable to set default tier to tier ID: {0}.
  </MsgText>
  <Explanation>
    The tier with the specified ID might not exist, or a database error might have occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the tier ID. If it does exist, check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0003E" severity="E" prefix="yes">
  <MsgText pgmKey="error.preInvoke.begin" varFormat="Java">
    error.preInvoke.begin=CWUDM0003E: MBean transaction did not begin.
  </MsgText>
  <Explanation>
    An error occurred trying to start a transaction.
  </Explanation>
  <UserResponse>
    Check the connection to the UDDI database and the installation configuration of the UDDI application.
  </UserResponse>
</Message>
<Message ID="CWUDQ1003E" severity="E" prefix="yes">
  <MsgText pgmKey="MigrationSQLException" varFormat="Java">
    MigrationSQLException=CWUDQ1003E: SQL Exception during migration: {0}
  </MsgText>
  <Explanation>
    The SQL exception shown in the message has occurred during the migration process.
  </Explanation>
  <UserResponse>
    Examine the SQL exception message and the accompanying error messages to help to resolve the problem.  Message CWUDQ1002E contains table details and significant key values.
  </UserResponse>
</Message>
<Message ID="CWUDM0026E" severity="E" prefix="yes">
  <MsgText pgmKey="error.node.deactivate.failed" varFormat="Java">
    error.node.deactivate.failed=CWUDM0026E: Unable to deactivate UDDI node.
  </MsgText>
  <Explanation>
    An error occurred trying to deactivate the UDDI node.
  </Explanation>
  <UserResponse>
    Check the running state of the UDDI application. Restart the application if necessary.
  </UserResponse>
</Message>
<Message ID="CWUDS0009E" severity="E" prefix="yes">
  <MsgText pgmKey="UDSP0009E_ResponseError" varFormat="Java">
    UDSP0009E_ResponseError=CWUDS0009E: Error during sending of response to client.
  </MsgText>
  <Explanation>
    An error occurred when sending a SOAP response message back to a client. The client might not have received the response.
  </Explanation>
  <UserResponse>
    This error is recorded so that failed responses to clients are logged. The client might have disconnected before the reply could be sent, or there might be a network problem. Examine the Application Server logs for more information about its cause.
  </UserResponse>
</Message>
<Message ID="CWUDT0001E" severity="E" prefix="yes">
  <MsgText pgmKey="TransactionManagerProcessInTransaction_1_Error" varFormat="Java">
    TransactionManagerProcessInTransaction_1_Error=CWUDT0001E: UDDIFatalErrorException processing request.
  </MsgText>
  <Explanation>
    An internal error occurred while processing a UDDI Version 3 SOAP request.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI enterprise application.
  </UserResponse>
</Message>
<Message ID="CWUDG0011E" severity="E" prefix="yes">
  <MsgText pgmKey="UDUC0011E_UddiGuiReflectionFailed" varFormat="Java">
    UDUC0011E_UddiGuiReflectionFailed=CWUDG0011E: Failed to invoke reflected methods in ActionForm. Exception: {0}
  </MsgText>
  <Explanation>
    The contents of a form object cannot be checked for characters that are not valid.
  </Explanation>
  <UserResponse>
    If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="CWUDM0171W" severity="W" prefix="yes">
  <MsgText pgmKey="error.digester.parse" varFormat="Java">
    error.digester.parse=CWUDM0171W: Parsing of configuration file {0} failed.
  </MsgText>
  <Explanation>
    The Digester configuration file is not in the correct format.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application.
  </UserResponse>
</Message>
<Message ID="CWUDG0002I" severity="I" prefix="yes">
  <MsgText pgmKey="UDUC0002I_UddiGuiInitFinish" varFormat="Java">
    UDUC0002I_UddiGuiInitFinish=CWUDG0002I: {0} finished initialization.
  </MsgText>
  <Explanation>
    The user console control servlet has completed startup successfully.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDN0014E" severity="E" prefix="yes">
  <MsgText pgmKey="NodeManagerTxnlDestroy_4_Error" varFormat="Java">
    NodeManagerTxnlDestroy_4_Error=CWUDN0014E: Error, NodeManager destroy Exception releasing connection.
  </MsgText>
  <Explanation>
    An exception occurred when the UDDI application was stopping.  This problem will not affect any subsequent UDDI restarts.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDG0008E" severity="E" prefix="yes">
  <MsgText pgmKey="UDUC0008E_UddiGuiInvalidKeyPassedException" varFormat="Java">
    UDUC0008E_UddiGuiInvalidKeyPassedException=CWUDG0008E: An invalid key was passed. error message: &lt;{0}&gt; error: {1} More information: {2}
  </MsgText>
  <Explanation>
    The requested operation is trying to retrieve information about an entity with a key that is not valid. This might occur if the entity has been deleted by another session. Examine the error message, error type, and additional information to help to resolve the problem.
  </Explanation>
  <UserResponse>
    Ask the client to close existing sessions and attempt the operation in a new browser session.
  </UserResponse>
</Message>
<Message ID="CWUDG0006E" severity="E" prefix="yes">
  <MsgText pgmKey="UDUC0006E_UddiGuiPersistenceException" varFormat="Java">
    UDUC0006E_UddiGuiPersistenceException=CWUDG0006E: A persistence error has occurred. error message: &lt;{0}&gt; error: {1} More information: {2}
  </MsgText>
  <Explanation>
    An error occurred while performing a database operation. Examine the error message, error type, and additional information to help to resolve the problem.
  </Explanation>
  <UserResponse>
    Check the database connections.
  </UserResponse>
</Message>
<Message ID="CWUDM0079I" severity="I" prefix="yes">
  <MsgText pgmKey="error.tier.default.notDeleteable" varFormat="Java">
    error.tier.default.notDeleteable=CWUDM0079I: The default tier cannot be deleted.
  </MsgText>
  <Explanation>
    When auto-registration of UDDI publishers is enabled, a tier that is designated as the tier assigned to UDDI publishers must always exist.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDN0003I" severity="I" prefix="yes">
  <MsgText pgmKey="NodeManagerConfigurationPersistedOK" varFormat="Java">
    NodeManagerConfigurationPersistedOK=CWUDN0003I: {0}
  </MsgText>
  <Explanation>
    The UDDI registry node configuration is successfully made persistent.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDQ1001E" severity="E" prefix="yes">
  <MsgText pgmKey="MigrationRowNotInserted" varFormat="Java">
    MigrationRowNotInserted=CWUDQ1001E: Row not inserted into {0}
  </MsgText>
  <Explanation>
    A row could not be inserted into the database table shown in the message.
  </Explanation>
  <UserResponse>
    See the accompanying error messages for more information. CWUDQ1003E shows details of the SQL exception.
  </UserResponse>
</Message>
<Message ID="CWUDQ1006E" severity="E" prefix="yes">
  <MsgText pgmKey="MigrationException" varFormat="Java">
    MigrationException=CWUDQ1006E: Exception during migration: {0}
  </MsgText>
  <Explanation>
    The exception shown in the message has occurred during the migration process.
  </Explanation>
  <UserResponse>
    Examine the exception message and the accompanying error messages to help to resolve the problem.  Message CWUDQ1002E contains table details and significant key values.
  </UserResponse>
</Message>
<Message ID="CWUDN0002E" severity="E" prefix="yes">
  <MsgText pgmKey="NodeManagerStateChangeError" varFormat="Java">
    NodeManagerStateChangeError=CWUDN0002E: Error, invalid Node State requested: {0}
  </MsgText>
  <Explanation>
    The UDDI registry node was requested to change to a state that is not valid.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0102E" severity="E" prefix="yes">
  <MsgText pgmKey="error.property.getMultiple.failed" varFormat="Java">
    error.property.getMultiple.failed=CWUDM0102E: Unable to retrieve collection of configuration properties.
  </MsgText>
  <Explanation>
    A database error occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0188I" severity="I" prefix="yes">
  <MsgText pgmKey="info.tier.delete" varFormat="Java">
    info.tier.delete=CWUDM0188I: Tier {0} was deleted.
  </MsgText>
  <Explanation>
    A UDDI tier has been deleted.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0103E" severity="E" prefix="yes">
  <MsgText pgmKey="error.property.updateMultiple.failed" varFormat="Java">
    error.property.updateMultiple.failed=CWUDM0103E: Unable to update configuration properties.
  </MsgText>
  <Explanation>
    This might occur if an updated property object cannot be validated. See the accompanying error messages for more information. Alternatively, a database error might have occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0151E" severity="E" prefix="yes">
  <MsgText pgmKey="error.vs.unload.failed" varFormat="Java">
    error.vs.unload.failed=CWUDM0151E: Unable to unload value set data with tModel key: {0}.
  </MsgText>
  <Explanation>
    The tModel key is not recognized or a database error occurred.
  </Explanation>
  <UserResponse>
    Ensure that the tModel exists. Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0185I" severity="I" prefix="yes">
  <MsgText pgmKey="info.user.delete" varFormat="Java">
    info.user.delete=CWUDM0185I: UDDI publisher {0} was deleted.
  </MsgText>
  <Explanation>
    A UDDI publisher has been deleted.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0189I" severity="I" prefix="yes">
  <MsgText pgmKey="info.property.update" varFormat="Java">
    info.property.update=CWUDM0189I: Configuration property {0} was updated to value {1}.
  </MsgText>
  <Explanation>
    The administrative operation described in the message completed successfully.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0007E" severity="E" prefix="yes">
  <MsgText pgmKey="error.unregister" varFormat="Java">
    error.unregister=CWUDM0007E: UddiNode MBean with ObjectName {0} could not be unregistered.
  </MsgText>
  <Explanation>
    The UddiNode MBean for the UDDI application could not be unregistered from the MBeanServer.
  </Explanation>
  <UserResponse>
    Restart the UDDI application or the application server.
  </UserResponse>
</Message>
<Message ID="CWUDM0172W" severity="W" prefix="yes">
  <MsgText pgmKey="warning.unexpected.dateFormat" varFormat="Java">
    warning.unexpected.dateFormat=CWUDM0172W: An unexpected date format was found while parsing configuration file.
  </MsgText>
  <Explanation>
    A date format in the configuration file is not correct.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application.
  </UserResponse>
</Message>
<Message ID="CWUDM0120E" severity="E" prefix="yes">
  <MsgText pgmKey="error.policy.get.failed" varFormat="Java">
    error.policy.get.failed=CWUDM0120E: Unable to get policy information for policy with ID: {0}.
  </MsgText>
  <Explanation>
    A database error occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDG0014E" severity="E" prefix="yes">
  <MsgText pgmKey="UDUC0014E_SetupCategoryTreeFailed" varFormat="Java">
    UDUC0014E_SetupCategoryTreeFailed=CWUDG0014E: User console initialization failed to initialize taxonomies. Exception: {0}
  </MsgText>
  <Explanation>
    An error has occurred during initialization of ActionServlet, specifically when reading taxonomy data (invoking the init method of CategoryTaxonomyTree).
  </Explanation>
  <UserResponse>
    Check the state of the UDDI database. Examine the exception message to help to resolve the problem.
  </UserResponse>
</Message>
<Message ID="CWUDQ0005I" severity="I" prefix="yes">
  <MsgText pgmKey="MigrationRowsMigrated" varFormat="Java">
    MigrationRowsMigrated=CWUDQ0005I: {0} rows have been inserted into table {1}
  </MsgText>
  <Explanation>
    This message shows the number of database rows converted for each UDDI table.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0150E" severity="E" prefix="yes">
  <MsgText pgmKey="error.vs.updateMultiple.supported.failed" varFormat="Java">
    error.vs.updateMultiple.supported.failed=CWUDM0150E: Could not update value set status with tModel key: {0}, property: {1}.
  </MsgText>
  <Explanation>
    A database error occurred when updating the supported status of one of the value set status objects.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0148E" severity="E" prefix="yes">
  <MsgText pgmKey="error.vs.update.supported.failed" varFormat="Java">
    error.vs.update.supported.failed=CWUDM0148E: Could not update value set status with tModel key: {0}, property: {1}.
  </MsgText>
  <Explanation>
    A database error occurred when updating the supported status of the value set status.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0062E" severity="E" prefix="yes">
  <MsgText pgmKey="error.user.createMultiple.failed" varFormat="Java">
    error.user.createMultiple.failed=CWUDM0062E: Unable to create UDDI publishers with user names: {0}.
  </MsgText>
  <Explanation>
    A database error occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0145E" severity="E" prefix="yes">
  <MsgText pgmKey="error.vs.loadFile.failed" varFormat="Java">
    error.vs.loadFile.failed=CWUDM0145E: Unable to load value set data for value set with tModel key: {0} and file name: {1}.
  </MsgText>
  <Explanation>
    The tModel key is not recognized, the file doesn&apos;t contain valid value set data, or a database error occurred.
  </Explanation>
  <UserResponse>
    Ensure that the tModel exists and the value set data object is populated. Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDN0006E" severity="E" prefix="yes">
  <MsgText pgmKey="NodeManagerTxnlInit_3_Error" varFormat="Java">
    NodeManagerTxnlInit_3_Error=CWUDN0006E: Error, NodeManager initialization UDDIException.
  </MsgText>
  <Explanation>
    An exception occurred during initialization of the UDDI node manager.
  </Explanation>
  <UserResponse>
    Restart the UDDI registry.  If the error continues, examine the Application Server logs for information about its cause.
  </UserResponse>
</Message>
<Message ID="CWUDM0191I" severity="I" prefix="yes">
  <MsgText pgmKey="info.tier.default" varFormat="Java">
    info.tier.default=CWUDM0191I: Default tier was set to {0}.
  </MsgText>
  <Explanation>
    The administrative operation described in the message completed successfully.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0186I" severity="I" prefix="yes">
  <MsgText pgmKey="info.tier.create" varFormat="Java">
    info.tier.create=CWUDM0186I: Tier {0} was created.
  </MsgText>
  <Explanation>
    A new UDDI tier has been created.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0028E" severity="E" prefix="yes">
  <MsgText pgmKey="error.node.init.failed" varFormat="Java">
    error.node.init.failed=CWUDM0028E: Unable to initialize UDDI node.
  </MsgText>
  <Explanation>
    An error occurred during initialization of the UDDI node.
  </Explanation>
  <UserResponse>
    Check the installation and data source settings of the UDDI application.
  </UserResponse>
</Message>
<Message ID="CWUDM0141E" severity="E" prefix="yes">
  <MsgText pgmKey="error.vs.getDetail.failed" varFormat="Java">
    error.vs.getDetail.failed=CWUDM0141E: Unable to retrieve value set details for tModel key: {0}.
  </MsgText>
  <Explanation>
    A database error occurred getting the value set details.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDS0012E" severity="E" prefix="yes">
  <MsgText pgmKey="E_doGet_2_Error" varFormat="Java">
    E_doGet_2_Error=CWUDS0012E: non-UDDI exception received processing doGet Request.
  </MsgText>
  <Explanation>
    An error occurred while processing a UDDI Version 3 GET request.
  </Explanation>
  <UserResponse>
    Check that the UDDI Version 3 GET request URL is valid.
  </UserResponse>
</Message>
<Message ID="CWUDM0077E" severity="E" prefix="yes">
  <MsgText pgmKey="error.entitlement.getMultiple.failed" varFormat="Java">
    error.entitlement.getMultiple.failed=CWUDM0077E: Unable to retrieve collection of entitlements.
  </MsgText>
  <Explanation>
    A database error occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0071E" severity="E" prefix="yes">
  <MsgText pgmKey="error.tier.delete.failed" varFormat="Java">
    error.tier.delete.failed=CWUDM0071E: Unable to delete tier with ID: {0}.
  </MsgText>
  <Explanation>
    The tier with the specified ID might not exist, or a database error might have occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the tier ID. If it does exist, check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0073E" severity="E" prefix="yes">
  <MsgText pgmKey="error.tier.getInfos.failed" varFormat="Java">
    error.tier.getInfos.failed=CWUDM0073E: Unable to retrieve collection of tiers.
  </MsgText>
  <Explanation>
    A database error occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0183I" severity="I" prefix="yes">
  <MsgText pgmKey="info.user.create" varFormat="Java">
    info.user.create=CWUDM0183I: UDDI publisher {0} was created.
  </MsgText>
  <Explanation>
    A new UDDI publisher has been created.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0006E" severity="E" prefix="yes">
  <MsgText pgmKey="error.setupConnection.acquireJndi" varFormat="Java">
    error.setupConnection.acquireJndi=CWUDM0006E: MBean could not acquire connection for UDDI datasource.
  </MsgText>
  <Explanation>
    The UDDI administrative function cannot connect to the UDDI registry database.
  </Explanation>
  <UserResponse>
    Check the configuration of the data source.
  </UserResponse>
</Message>
<Message ID="CWUDM0059E" severity="E" prefix="yes">
  <MsgText pgmKey="error.user.get.failed" varFormat="Java">
    error.user.get.failed=CWUDM0059E: Unable to retrieve information for UDDI publisher with user name {0}.
  </MsgText>
  <Explanation>
    A database error occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0024E" severity="E" prefix="yes">
  <MsgText pgmKey="error.node.activate.failed" varFormat="Java">
    error.node.activate.failed=CWUDM0024E: Unable to activate UDDI node.
  </MsgText>
  <Explanation>
    An error occurred trying to activate the UDDI node.
  </Explanation>
  <UserResponse>
    Check the running state of the UDDI application. Restart the application if necessary.
  </UserResponse>
</Message>
<Message ID="CWUDM0170W" severity="W" prefix="yes">
  <MsgText pgmKey="error.digester.load" varFormat="Java">
    error.digester.load=CWUDM0170W: Loading of configuration file {0} failed.
  </MsgText>
  <Explanation>
    The Digester configuration file could not be loaded.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application.
  </UserResponse>
</Message>
<Message ID="CWUDM0002E" severity="E" prefix="yes">
  <MsgText pgmKey="error.postInvoke.commit" varFormat="Java">
    error.postInvoke.commit=CWUDM0002E: MBean transaction failed. Commit flag was: {0}
  </MsgText>
  <Explanation>
    The current transaction did not commit or roll back.
  </Explanation>
  <UserResponse>
    Check the connection to the UDDI database and the installation configuration of the UDDI application.
  </UserResponse>
</Message>
<Message ID="CWUDM0008W" severity="W" prefix="yes">
  <MsgText pgmKey="error.notification.mbean" varFormat="Java">
    error.notification.mbean=CWUDM0008W: MBean notfication for event {0} failed.
  </MsgText>
  <Explanation>
    The UDDI administrative function did not complete successfully.
  </Explanation>
  <UserResponse>
    Check the connection to the UDDI database and the installation configuration of the UDDI application.
  </UserResponse>
</Message>
<Message ID="CWUDM0022E" severity="E" prefix="yes">
  <MsgText pgmKey="error.node.appname.failed" varFormat="Java">
    error.node.appname.failed=CWUDM0022E: Unable to retrieve UDDI node application name.
  </MsgText>
  <Explanation>
    A database error occurred.
  </Explanation>
  <UserResponse>
    Check the connection to the UDDI database and the installation configuration of the UDDI application.
  </UserResponse>
</Message>
<Message ID="CWUDS0002E" severity="E" prefix="yes">
  <MsgText pgmKey="UDSP0002E_SchemasNotFound" varFormat="Java">
    UDSP0002E_SchemasNotFound=CWUDS0002E: Error locating schemas required for UDDI processing. SOAP servlets unworkable.
  </MsgText>
  <Explanation>
    The SOAP servlet could not locate the schemas it requires to process SOAP requests. Without these, the servlet cannot process SOAP requests.
  </Explanation>
  <UserResponse>
    Check that the installation of UDDI was performed correctly. If the error continues, examine the Application Server logs for information about its cause.
  </UserResponse>
</Message>
<Message ID="CWUDN0009E" severity="E" prefix="yes">
  <MsgText pgmKey="NodeManagerTxnlInit_6_Error" varFormat="Java">
    NodeManagerTxnlInit_6_Error=CWUDN0009E: Error, NodeManager initialization rollback Exception.
  </MsgText>
  <Explanation>
    An exception occurred during initialization of the UDDI node manager.
  </Explanation>
  <UserResponse>
    Restart the UDDI registry.  If the error continues, examine the Application Server logs for information about its cause.
  </UserResponse>
</Message>
<Message ID="CWUDN0005E" severity="E" prefix="yes">
  <MsgText pgmKey="NodeManagerTxnlInit_2_Error" varFormat="Java">
    NodeManagerTxnlInit_2_Error=CWUDN0005E: Error, NodeManager initialization UDDIFatalErrorException.
  </MsgText>
  <Explanation>
    An exception occurred during initialization of the UDDI node manager.
  </Explanation>
  <UserResponse>
    Restart the UDDI registry.  If the error continues, examine the Application Server logs for information about its cause.
  </UserResponse>
</Message>
<Message ID="CWUDM0056E" severity="E" prefix="yes">
  <MsgText pgmKey="error.user.update.failed" varFormat="Java">
    error.user.update.failed=CWUDM0056E: Unable to update UDDI publisher with user name {0}.
  </MsgText>
  <Explanation>
    An error occurred trying to update the UDDI publisher.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0140E" severity="E" prefix="yes">
  <MsgText pgmKey="error.vs.changeKey.failed" varFormat="Java">
    error.vs.changeKey.failed=CWUDM0140E: Unable to change value set tModelKey from {0} to {1}.
  </MsgText>
  <Explanation>
    The policy with the specified ID does not exist.
  </Explanation>
  <UserResponse>
    Use a valid policy ID. You can find these in the PolicyConstants interface information.
  </UserResponse>
</Message>
<Message ID="CWUDM0078E" severity="E" prefix="yes">
  <MsgText pgmKey="error.limit.getMultiple.failed" varFormat="Java">
    error.limit.getMultiple.failed=CWUDM0078E: Unable to retrieve collection of limits.
  </MsgText>
  <Explanation>
    A database error occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDQ0003I" severity="I" prefix="yes">
  <MsgText pgmKey="MigrationCompleted" varFormat="Java">
    MigrationCompleted=CWUDQ0003I: UDDI registry migration has completed
  </MsgText>
  <Explanation>
    This message is for informational purposes only.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDG0003I" severity="I" prefix="yes">
  <MsgText pgmKey="UDUC0003I_UddiGuiInitReadStart" varFormat="Java">
    UDUC0003I_UddiGuiInitReadStart=CWUDG0003I: Reading init parameters.
  </MsgText>
  <Explanation>
    The user console control servlet has started reading external parameters during initialization.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0146E" severity="E" prefix="yes">
  <MsgText pgmKey="error.vs.loadValueSet.failed" varFormat="Java">
    error.vs.loadValueSet.failed=CWUDM0146E: Unable to load value set data for value set with tModel key: {0}.
  </MsgText>
  <Explanation>
    The tModel key is not recognized or a database error occurred.
  </Explanation>
  <UserResponse>
    Ensure that the tModel exists and the value set data object is populated. Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDM0021E" severity="E" prefix="yes">
  <MsgText pgmKey="error.node.state.failed" varFormat="Java">
    error.node.state.failed=CWUDM0021E: Unable to retrieve UDDI node state.
  </MsgText>
  <Explanation>
    A database error occurred.
  </Explanation>
  <UserResponse>
    Check the connection to the UDDI database and the installation configuration of the UDDI application.
  </UserResponse>
</Message>
<Message ID="CWUDM0031I" severity="I" prefix="yes">
  <MsgText pgmKey="error.node.init.alreadyInit.default" varFormat="Java">
    error.node.init.alreadyInit.default=CWUDM0031I: Initialize operation did not occur because the UDDI node is in default configuration and is already initialized.
  </MsgText>
  <Explanation>
    A UDDI node can be initialized only once.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0030I" severity="I" prefix="yes">
  <MsgText pgmKey="error.node.init.alreadyInit" varFormat="Java">
    error.node.init.alreadyInit=CWUDM0030I: Initialize operation did not occur because the UDDI node is already initialized.
  </MsgText>
  <Explanation>
    A UDDI node can be initialized only once.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0182I" severity="I" prefix="yes">
  <MsgText pgmKey="info.node.init.ok" varFormat="Java">
    info.node.init.ok=CWUDM0182I: UDDI node initialized successfully.
  </MsgText>
  <Explanation>
    The UDDI node is ready to accept UDDI Application Programming Interface requests.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0125E" severity="E" prefix="yes">
  <MsgText pgmKey="error.policy.update.failed" varFormat="Java">
    error.policy.update.failed=CWUDM0125E: Unable to update policy with ID: {0}.
  </MsgText>
  <Explanation>
    This might occur if the updated policy object shown in the message cannot be validated, or its ID is not recognized. See the accompanying error messages for more information. Alternatively, a database error might have occurred performing the operation described in the message.
  </Explanation>
  <UserResponse>
    Check the policy ID and value are valid. Check the configuration of the UDDI application and the connection to the UDDI database.
  </UserResponse>
</Message>
<Message ID="CWUDN0013E" severity="E" prefix="yes">
  <MsgText pgmKey="NodeManagerTxnlDestroy_3_Error" varFormat="Java">
    NodeManagerTxnlDestroy_3_Error=CWUDN0013E: Error, NodeManager destroy rollback Exception.
  </MsgText>
  <Explanation>
    An exception occurred when the UDDI application was stopping.  This problem will not affect any subsequent UDDI restarts.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="CWUDM0020E" severity="E" prefix="yes">
  <MsgText pgmKey="error.node.id.failed" varFormat="Java">
    error.node.id.failed=CWUDM0020E: Unable to retrieve UDDI node ID.
  </MsgText>
  <Explanation>
    A database error occurred.
  </Explanation>
  <UserResponse>
    Check the connection to the UDDI database and the installation configuration of the UDDI application.
  </UserResponse>
</Message>
<Message ID="CWUDM0027I" severity="I" prefix="yes">
  <MsgText pgmKey="error.node.deactivate.failed.invalidState" varFormat="Java">
    error.node.deactivate.failed.invalidState=CWUDM0027I: Unable to deactivate UDDI node that is not initialized.
  </MsgText>
  <Explanation>
    The UDDI node must be initialized, and activated, before it can be deactivated.
  </Explanation>
  <UserResponse>
    If the UDDI node is ready to be initialized, start the initialization operation.
  </UserResponse>
</Message>
<!-- END MESSAGES -->
</TMSSource>
