WebSphere Process Server messages     Operating Systems: All supported
CWLAE0000E: The relationship definition {0} was not found.
Explanation: The definition of the referenced relationship cannot be found. A likely cause of this problem is that the relationship name is spelled incorrectly.
User Action: Verify that the relationship name is spelled correctly.

 

CWLAE0001E: The role definition {0} was not found.
Explanation: The definition of the referenced role cannot be found. A likely cause of this problem is that the role name is spelled incorrectly.
User Action: Verify that the role name is spelled correctly.

 

CWLAE0005I: An exception was encountered when the relationship service code was executing.
Explanation: The error is listed in the stack trace. It can help determine the problem.
User Action: Refer to the stack trace for help in determining the problem. For more information, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.

 

CWLAE0006E: The role object type in the role {0} was not found.
Explanation: The business object schema for the role object in the specified role was not loaded. The schema might be missing or a name might be misspelled.
User Action: Check the target business object schema. If the role object type is missing, supply it. Also check that the target namespace and the local name are spelled correctly. If a name is misspelled, correct it.

 

CWLAE0007E: The stored procedure {0} already exist, but its parameters are inconsistent with the current role definition.
Explanation: The stored procedure with same name as current one already exists in the database. However its parameters are different from the parameters of the stored procedure already in the database.
User Action: Check the stored procedures in database. Delete the existed stored procedure and then reinstall or restart the application if users want to replace the existed one with the current one.

 

CWLAE0100I: No participant was found for the relationship {0}, the role {1}, and the values {2}.
Explanation: The participant was not found when trying to retrieve it from the persistent store by the value. The participant should have been created in a previous run of the relationship service.
User Action: This is an informational message. No user action is required.

 

CWLAE0101I: No participant was found for the relationship {0}, the role {1}, and the instance ID {2}.
Explanation: The participant was not found when trying to retrieve it from the persistent store using the instance ID. The participant should have been created in a previous run of the relationship service.
User Action: This is an informational message. No user action is required.

 

CWLAE0102W: The value of the attribute {0} of the business object {1} is an empty string.
Explanation: The specified attribute cannot have an empty string as its value.
User Action: This is a warning message. Check the data that is passed into the relationship service.

 

CWLAE0103W: A participant was created for relationship {0}, the role {1}, and the values {2}. The instance ID is {3}, but the expected ID is {4}.
Explanation: A likely cause of this error is that the participants are not correlated correctly.
User Action: This is a warning message. Check the database table.

 

CWLAE0104W: The index on key attributes cannot be created.
Explanation: A likely cause of this error is that the total length of the key attributes columns is too long. Database management systems (DBMS) have a limitation on the total length of all of the indexed columns in one COMPOSITE index. For example, the limitation is 1024 bytes for DB2 Universal Database, v8 (Windows/Linux/UNIX), and 380 bytes for Informix Dynamic Server, v9.4.
User Action: If there are several key attributes whose type is string, set a maximum length in the business object attributes.

 

CWLAE0105W: No participant was found for the relationship {0}, the role {1}, and the values {2}. A new participant will be created by the relationship service.
Explanation: The participant was not found when trying to retrieve it from the persistent store by the value. The participant should have been created in a previous run of the relationship service.
User Action: This is a warning message. Check the operation of relationship service.

 

CWLAE0106I: No participant was found for the relationship {0}, the role {1}, and the values {2}. The output GBOID will be left as it is.
Explanation: The participant was not found when trying to retrieve it from the persistent store by the value. The participant should have been created in a previous run of the relationship service.
User Action: This is an informational message. Check the operation of relationship service.

 

CWLAE0107W: No participant with the instance ID {0} was found for the relationship {1} and the role {2}.
Explanation: The participant was not found when trying to retrieve it from the persistent store by the instance ID. The participant should have been created in a previous run of the relationship service.
User Action: This is a warning message. Check the operation of relationship service.

 

CWLAE0108W: No participant was found for the relationship {0}, the role {1}, and the values {2}.
Explanation: The participant was not found when trying to retrieve it from the persistent store by the value. The participant should have been created in a previous run of the relationship service.
User Action: This is a warning message. Check the operation of relationship service.

 

CWLAE0109E: The relationship {0} is not static.
Explanation: A relationship must be static for this operation. A like cause of this error is that an incorrect relationship is selected.
User Action: Verify that the correct static relationship is selected.

 

CWLAE0110E: The key attribute for the role {0} of the relationship {1} is not set.
Explanation: A key attribute must be set, or execution cannot continue.
User Action: Make sure to set all key attributes for this role in the Relationship Editor.

 

CWLAE0111E: The instance ID for the role {0} of the relationship {1} and the data {2} cannot be found.
Explanation: The instance ID must match the specified data, or execution cannot continue.
User Action: Use relationship manager to validate that the data that was used to populate the relationship includes current data. If it does not, update the data.

 

CWLAE0112E: No participant was found for the role {0} of the relationship {1} and the instance ID {2}.
Explanation: A participant that matches this instance ID was not found. Execution cannot continue.
User Action: Use the relationship manager to validate that this instance ID has matching participant data.

 

CWLAE0113E: More than one instance ID was found for the role {0} of the relationship {1} and the data {2}.
Explanation: The existence of more than one instance ID indicates that this is a one-to-many or a many-to-many relationship. The static lookup application programming interface (API) supports only one-to-one relationships.
User Action: Use another API for this relationship. For more information, refer to the WebSphere Process Server documentation (http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp).

 

CWLAE0114E: More than one participant was found for the role {0} of relationship {1} and the instance ID {2}.
Explanation: The existence of more than one participant with the specified characteristics indicates that this is a one-to-many or many-to-many relationship. The static lookup application programming interface (API) supports only one-to-one relationships.
User Action: Use another API for this relationship. For more information, refer to the WebSphere Process Server documentation (http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp).

 

CWLAE0115E: no parent object found for "{0}" when retrieving the role parent object for child "{1}" in role "{2}"
Explanation: No parent object was found when retrieving the role parent object for this child as defined by the role key attribute path definitions
User Action: Use a child that is contained in a hierarchy that conforms to the role object and key attribute path definitions

 

CWLAE0116E: Existing instance id found for the Role "{0}" of Relationship "{1}" and data "{2}".
Explanation: An existing instance was found.
User Action: Use Relationship Manager to validate that the existing instance is consistent with your data.

 

CWLAE0117E: Existing participant found for the Role "{0}" of Relationship "{1}" and value "{2}".
Explanation: An existing participant was found.
User Action: Use Relationship Manager to validate that the existing instance is consistent with your data.

 

CWLAE0118E: Pattern violation detected for Role "{0}", Relationship "{1}", instanceId "{2}" - event delivery creation of a target application object no supported.
Explanation: When creating a target application business object, request/response invocation must be used.
User Action: Use request/response invocation for target application object creation

 

CWLAE0119E: invalid correlation invocation - the key attribute of the managed role "{0}" is not defined as a simple property of a business object.
Explanation: When invoking the correlation APIs, the managed role must be defined as a simple business object with a key attribute to a simple property.
User Action: Use the deprecated maintainRelationship APIs for composite managed roles or change your managed role's key attribute to point to a simple property.

 

CWLAE0120E: invalid correlation invocation - The source role "{0}" and target role "{1}" do not specify one managed and one application specific role.
Explanation: When invoking the correlation APIs, one role must be the generic role, while the other must be an application specific role.
User Action: Invoke the APIs with the qualified name of the generic and one application specific role.

 

CWLAE0121E: invalid correlation invocation - The relationship "{0}" is not an identity relationship.
Explanation: The correlation APIs can only be used for identity relationships.
User Action: Change your relationship definition by setting the "is identity" flag to "true"

 

CWLAE0122E: invalid correlation invocation - "correlate" was invoked with the composite role "{0}", but may only be used for simple roles.
Explanation: This method is used to correlate between two simple business objects.
User Action: Use "correlateFromComposite" or "correlateToComposite" instead.

 

CWLAE0123E: invalid correlation invocation - "{0}" was invoked with the simlpe role "{1}", but may only be used for composite roles.
Explanation: This method is used to correlate between the parent of a composite role and the children of a simple role.
User Action: Use "correlate" to correlate two simple business object.

 

CWLAE0124E: invalid correlation invocation - correlateFromComposite cannot be used for correlation going from the generic role to an application specific role.
Explanation: This method is used to correlate between an application specific composite role and a list of generic children.
User Action: Use "correlateToComposite" instead.

 

CWLAE0125E: invalid correlation invocation - correlateToComposite cannot be used for correlation going from an application specific role to the generic role.
Explanation: This method is used to correlate between a list of generic children and an application specific composite role.
User Action: Use "correlateFromComposite" instead.

 

CWLAE0126E: invalid correlation invocation - The numbers of existing source children, target children, and original target children are not equal
Explanation: Correlation between existing children lists of different length is not supported
User Action: Ensure that the number of existing children for the composite parent is the same as the number of existing children passed to the correlate APIs.

 

CWLAE0127E: invalid correlation invocation - original input BO(s) may not be null or empty for service call responses or failures
Explanation: The original BO(s) was found to be null or empty
User Action: Invoke correlate with the original input BO that was used for the initial service call request or event delivery when invoking correlate for response or failure invocations

 

CWLAE0128E: invalid correlation invocation - no child was found when attempting to correlate a relationship spaning multiple BOs
Explanation: When invoking correlate for a role definition that spans multiple single cardinality BOs, each BO must be present in the refernce in order to correlate
User Action: Invoke correlate with the full hierarchy of business objects as they are defined in the according role definition

 

CWLAE0129E: invalid correlation invocation - inputBO is neither of role type {0} nor of managed role type {1}, but instead of type {2}
Explanation: When invoking correlate, the inputBO must be either of the type of an application specific role or of the managed role type
User Action: Invoke correlate with an inputBO that is either of the type of an application specific role or of the managed role type

 

CWLAE0130E: invalid correlation invocation - verb does not match changes logged in change summary: {0} logged for {1} verb
Explanation: Correlate was invoked with an inconsistent business graph, which prohibits determining the correct action
User Action: Invoke correlate with a valid business graph with respect to the verb and changes that have been applied to it

 

CWLAE0131E: invalid correlation invocation - the business object of type {0} is not part of a business graph that contains verb or change summary information.
Explanation: In order to infer the appropriate action for correlating business objects, the Relationship Service requires the input business object to be contained in business graph that has a verb set or change summary information logged.
User Action: Invoke correlate APIs with input business objects that are contained in a business graph, and ensure that a verb is set or change summary entries are present.

 

CWLAE0132E: property {0} not found in business object {1}
Explanation: When attempting to extract a property from a business object as defined by the role definition, this property was not found
User Action: Invoke the Relationship Service with busines objects that match the role definition or revise your role definition

 

CWLAE0133E: No participant is available for a managed role {0}. It is invalid to add/create/delete/deactivate/retrieve participant for a managed role.
Explanation: Managed role does not have corresponding participants. It is used to correlate different participants for application specific roles.
User Action: Please specify a correct application specific role as an argument.

 

CWLAE0134E: Invalid key attribute value {0} with respect to the key attribute type {1}.
Explanation: The key attribute value is not an instance of the key attribute type specified in the role definition.
User Action: Please specify correct value according to its type.

 

CWLAE0135E: The instance id in the {0} property of the {1} business object belonging to {2} role is not set.
Explanation: The instance id must be present in the generic business object when invoking the Relationship Service.
User Action: Please specify an instance id when invoking the relationship service.

 

CWLAE0136E: Relationship definition {0} not found. Either the database is down or the relationship is not installed correctly.
Explanation: The database is down or the relationship is not installed correctly.
User Action: Check the database connection. If the server is connected to the database, then please make sure the relationship is installed correctly.

 

CWLAE0400W: The orphan role {0} was found. It will not be loaded.
Explanation: Only roles that have corresponding relationships can be added to the parent relationship.
User Action: Check the role and verify that its relationship and target namespace are included in a separate file.

 

CWLAE0401I: The relationship {0} was aggregated to the cache.
Explanation: The specified relationship was placed in the internal cache of the relationship service.
User Action: This is an informational message. No user action is required.

 

CWLAE0402I: The role {0} was aggregated to the relationship {1}.
Explanation: The specified role was attached to the relationship.
User Action: This is an informational message. No user action is required.

 

CWLAE0403W: More than one instance of the role {0} was found in the relationship {1}.
Explanation: A role cannot be in an individual file if it exists in the corresponding relationship.
User Action: Delete the role from the file if it is not needed.

 

CWLAE0404I: All relationships and roles (.rel and .rol files) in this application are being loaded.
Explanation: This is an informational message. The relationship service is loading all of the relationships and roles that are in the scope of this application.
User Action: No user action is required.

 

CWLAE0405W: The relationship from the URL {0} cannot be loaded. The error is {1}.
Explanation: It is unclear if the file is a relationship definition file. Likely reasons for this error are that the file is not meant to define a relationship, or there is an error in the relationship format.
User Action: If the file is intended to define a relationship, check its format and correct errors. If it is not intended to define a relationship, you can ignore this message.

 

CWLAE0406I: The relationship service cannot load relationship {0} from the URL {1} because the relationship is already loaded. This one will be ignored.
Explanation: After loading a relationship from this file, the relationship service runtime found that the relationship had been loaded from another file.
User Action: Remove the duplicate relationship file from the scope of the application.

 

CWLAE0407W: The role from the URL {0} cannot be loaded. The error is {1}.
Explanation: It is unclear if the file is a role definition file. Likely reasons for this error are that the file is not meant to define a role, or there is an error in the role format.
User Action: If the file is intended to define a role, check its format and correct errors. If it is not intended to define a role, you can ignore this message.

 

CWLAE0408W: Relationship instances cannot be loaded from the URL {0}. The error is {1}.
Explanation: It is unclear if the file is a relationship instance file, but the relationship service fail to load its content.
User Action: If the file is intended to present relationship instances, check its format. If it is not intended to present relationship instances, you can ignore this message.

 

CWLAE0409W: The role {0} (URL {1}) refers to the nonexistent relationship {2}. This role will be ignored.
Explanation: The "relationship" element of the role refers to a relationship, but that relationship is not in the scope of this application.
User Action: Check whether the relationship file exists in the scope of this application.

 

CWLAE0410I: The role {0} (URL {1}) refers to the relationship {2}, but in this relationship, a role exists with the same name. This role will be ignored.
Explanation: Only one role file should define the role.
User Action: Remove the redundant role file.

 

CWLAE0411I: All of the relationships and roles in this application have been loaded.
Explanation: This is an informational message. The relationship service runtime loaded all of the relationship, role, and relationship instance files that are in the scope of this application.
User Action: No user action is required.

 

CWLAE0412W: The relationship instance object from the URL {0} refers to the nonexistent relationship {1}. It will be ignored.
Explanation: The relationship instance refers to a relationship, but that relationship is not in the scope of the application.
User Action: Check whether the relationship file exists in the scope of the application.

 

CWLAE0413W: The relationship instance object from the URL {0} refers to the relationship {1}, but an instance ID already exists.
Explanation: This is a warning message. An instance object for this relationship already exists, so the current one will be ignored.
User Action: No user action is required.

 

CWLAE0414I: Runtime schemas for all of the loaded relationships and roles in this application are being created.
Explanation: This is an informational message.
User Action: No user action is required.

 

CWLAE0415I: Schemas have been created for all of the loaded relationships and roles in this application.
Explanation: This is an informational message.
User Action: No user action is required.

 

CWLAE0416W: Instance data for the relationship {0} was not populated. The error is {1}.
Explanation: The following error has occurred while relationship service runtime is populating relationship instance into persistent store: {1}. The error message explains the cause of the problem.
User Action: Please check the error message.

 

CWLAE0417W: The relationship {0} cannot be found for the application {1}.
Explanation: The relationship definition is not included in the application.
User Action: Correct the relationship name.

 

CWLAE0418W: The role {0} cannot be found for the application {1}.
Explanation: The role definition is not included in the application.
User Action: Correct the role name.

 

CWLAE0420I: The relationship table schema {0} does not exist in the database.
Explanation: This is an informational message.
User Action: No user action is required.

 

CWLAE0421I: Deleting the relationship table schema {0} from the database.
Explanation: This is an informational message.
User Action: No user action is required.

 

CWLAE0422I: {0} is a loose application.
Explanation: This is an informational message. The application is running in a unit-test environment (UTE).
User Action: No user action is required.

 

CWLAE0423I: {0} is not a loose application.
Explanation: This is an informational message. The application is running in a runtime environment.
User Action: No user action is required.

 

CWLAE0424I: The .jar file {0} has been removed from the database.
Explanation: This is an informational message.
User Action: No user action is required.

 

CWLAE0425I: Relationships in application "{0}" have been uninstalled.
Explanation: This is an informational message.
User Action: No user action is required.

 

CWLAE0426I: Relationships in application "{0}" have been installed.
Explanation: This is an informational message.
User Action: No user action is required.

 

CWLAE0430E: Access to the relationship service WebSphere Common Configuration Model (WCCM) failed.
Explanation: The current server is neither WebSphere Process Server nor WebSphere Enterprise Service Bus.
User Action: Install WebSphere Process Server or WebSphere Enterprise Service Bus to enable the relationship service.

 

CWLAE0431E: The {0} attribute name does not match the {1} key attribute that is defined in the {2} role.
Explanation: The key attribute must be part of the attribute name.
User Action: Make the key attribute part of the attribute name, or select a role with a key attribute that matches the attribute name.

 

CWLAE0432E: The transform from the {0} raw string to a raw object failed with the following exception: {1}
Explanation: The data value and its corresponding data type might not be compatible, or this data type might not be supported.
User Action: Use a supported data type and pass in a valid data value.

 

CWLAE0433E: The {0} value that is used in the {1} static lookup relationship and the {2} role is the {3} type, which is not supported.
Explanation: Supported data types for static lookup relationship are Boolean, int, long, float, double, and string.
User Action: Pass in the supported data for a static relationship.

 

CWLAE0434E: The business object is not the expected type {0}:{1}. It is the {2}:{3} type.
Explanation: The type of business object is not expected.
User Action: Pass in a business object that is of the expected type.

 

CWLAE0451W: The list represented by the relationship instance is null.
Explanation: There is no data in the .ri files.
User Action: Add relationship instance information to the .ri files.

 

CWLAE0452W: The URL of the relationship instance file is null.
Explanation: The .ri file URL cannot be null, otherwise the relationship instance cannot be located.
User Action: Change the URL to a valid value.

 

CWLAE0453W: The relationship instance file contains invalid objects.
Explanation: The objects in the .ri file must be of the type RelationshipInstance, RelationshipInstanceRoot, or RelationshipInstanceBG.
User Action: Ensure the objects in the .ri file are valid.

 

CWLAE0454W: The relationship instance was not found in the URL {0}.
Explanation: There is no relInstance contained in the file URL.
User Action: Ensure that there are non-empty relInstance data contained in the file URL.

 

CWLAE0455W: Inconsistent instance ID in one relationship instance.
Explanation: A likely cause of the problem is a duplicate instance of a role.
User Action: Ensure that there are no duplicate roleInstances for the same role.

 

CWLAE0456E: The relationship instance business graph contains instances for more than one relationship.
Explanation: The business graph cannot contain instances for more than one relationship.
User Action: Make sure the graph contains instances for only one relationship.

 

CWLAE0457E: Application directory for the relationship {0} is null.
Explanation: Application directory for the relationship must be specified.
User Action: Check the directory path to the relationship and make sure it is installed properly.

 

CWLAE0500I: The relationship runtime table view {0} does not exist in the database.
Explanation: This is an informational message.
User Action: No user action is required.

 

CWLAE0501I: No view will be created this time because the view already exists in the database {0}.
Explanation: This is an informational message.
User Action: No user action is required.

 

CWLAE0502I: Dropping the relationship runtime table view {0} from the database.
Explanation: This is an informational message.
User Action: No user action is required.

 

CWLAE0503I: Creating relationship runtime table view from the database {0}.
Explanation: This is an informational message.
User Action: No user action is required.

 

CWLAE0504I: Deleting view meta data from RELN_VIEW_META_T table {0}.
Explanation: This is an informational message.
User Action: No user action is required.

 

CWLAE0505I: Adding view meta data into RELN_VIEW_META_T table {0}.
Explanation: This is an informational message.
User Action: No user action is required.

 

CWLAE0520E: The input value for the role {0} may not be null.
Explanation: The input value is found to be null.
User Action: Check data input to make sure the value is not null.

 

CWLAE0521E: The input instance id {1} is not valid for role {0}.
Explanation: The instance id is not found in the database.
User Action: Check data input to make sure the instance id is a valid id.

 

CWLAE0522E: The input value {0} is of invalid types.
Explanation: The type of the input value is found not valid. The valid types are: String, Integer, Long, Float, Double, Boolean or DataObject
User Action: Check data input to make sure the input type is valid.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009