- CWWBW0001I: Validated process model ''{0}'' successfully: {1} warnings, {2} information.
- Explanation: The validated process model does not contain any validation errors. The installation of the application can be continued.
- User Action: Check any warnings or informational messages. These messages provide more information and any actions that you need to take.
- CWWBW0002E: Validated process model ''{0}'' with findings: {1} errors, {2} warnings, {3} information.
- Explanation: The validated process model contains one or more validation errors. The installation of the application cannot be continued.
- User Action: Correct all of the reported errors and re-install the application. The messages provide more information about the error and any actions that you need to take. If the application was created with the corresponding tool, ensure that the release levels of the tool and of the run time are compatible. If the application is installed in an ND environment, ensure that all of the servers are at the same release level.
- CWWBW0003E: Validated process model ''{0}'' with findings: {1} errors, {2} warnings, {3} information: {4}
- Explanation: The validated process model contains one or more validation errors. The installation of the application cannot be continued.
- User Action: Correct all of the reported errors and re-install the application. The messages provide more information about the error and any actions that you need to take. If the application was created with the corresponding tool, ensure that the release levels of the tool and of the run time are compatible. If the application is installed in an ND environment, ensure that all of the servers are at the same release level.
- CWWBW0004E: A syntactical error was found (row: {0}, column: {1}): {2}
- Explanation: The BPEL file does not validate against the schema.
- User Action: Ensure that the BPEL file is syntactically correct.
- CWWBW0005W: A syntactical warning was found (row: {0}, column: {1}): {2}
- Explanation: The BPEL file validates with warnings against the schema.
- User Action: Ensure that the BPEL file is syntactically correct.
- CWWBW0006E: The Business Process Execution Language (BPEL) file cannot be loaded.
- Explanation: The BPEL file cannot be validated because either the file is not valid or an internal problem occurred. If the errors are unrecoverable, for example, if the file is not well-formed, the file cannot be loaded.
- User Action: Correct all of the reported syntactical errors. If no other errors are reported and the problem persists, refer to the technical information databases on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/. If you cannot find the information that you need to solve the problem, contact your technical support provider or again refer to the WebSphere Process Server support site for information about IBM Software Support and Services.
- CWWBW0007E: The file could not be read. Detail message: ''{0}''.
- Explanation: The BPEL file could not be found or another error occurred when the file was read.
- User Action: Check the detail message.
- CWWBW0050E: BPEL validation error: {0}.
- Explanation: General purpose message used when the product is in service and a new message is needed.
- User Action: Check the error message for a description of the error.
- CWWBW0051W: BPEL validation warning: {0}.
- Explanation: General purpose message used when the product is in service and a new message is needed.
- User Action: Check the warning message for a description of the warning.
- CWWBW0052I: BPEL validation information: {0}.
- Explanation: General purpose message used when the product is in service and a new message is needed.
- User Action: No action is required.
- CWWBW0101E: The {0} process does not contain an activity; therefore, it cannot run.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, in the business process editor, right-click and select add from the drop-down menu. Choose an activity. The activity can be a structured activity, such as a parallel-activities activity, or a sequence activity. The structured activities can contain basic and structured activities, for example, receive activities, reply activities, assign activities, and scope activities.
- CWWBW0102E: Catch number {0} in the process fault handler does not contain an activity; therefore, it cannot run.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Business Process editor, add an activity to the catch by selecting an activity from the palette and dropping it onto the catch. Or right-click the catch and select delete to remove the catch.
- CWWBW0103E: The catch-all element does not contain an activity (process fault handler) it cannot run.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Business Process editor, add an activity to the catch-all by selecting an activity from the palette and dropping it onto the catch-all. Or right-click the catch-all and select delete to remove the catch-all.
- CWWBW0104E: The onEvent event must contain an activity (process event handler, onEvent event number {0}).
- Explanation: An empty onEvent event cannot run.
- User Action: Add an activity to the onEvent event or remove the event.
- CWWBW0105E: The timeout event must contain an activity (process event handler, timeout event {0}).
- Explanation: An empty timeout event cannot run.
- User Action: Add an activity to the timeout event or remove the event.
- CWWBW0106E: The partnerLinkType must be set (process partner ''{0}'').
- Explanation: The partnerLinkType defines up to two roles that a process can have when it interacts with other services.
- User Action: Set the partnerLinkType.
- CWWBW0107E: The partner for onEvent event number {0} is missing.
- Explanation: The partner must be specified for an onEvent event in the process event handler.
- User Action: In WebSphere Integration Developer, double-click the error message. Right-click the start node and open the event handler. Select the specified onEvent event. In the Properties view, on the Details tab, browse for and select a partner.
- CWWBW0108E: The operation in onEvent event number {0} in the process event handler is not set.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, set the operation.
- CWWBW0109E: The variable in the {2} parameter (parameter number {1} in the input or output element) of onEvent event number {0} in the process event handler is not set.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, set the variable.
- CWWBW0110E: The {0} correlation set does not refer to a correlation property.
- Explanation: Correlation sets must contain at least one correlation property.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Description tab, select an existing correlation property or create a new one. To define a new property, click the plus sign (+) in the correlation property category on the right side of the process editor screen.
- CWWBW0111E: The administrative task of the {0} process or the default activity administrative task is not set.
- Explanation: All administrative tasks must be set on a process.
- User Action: In WebSphere Integration Developer, click the start node. In the Properties view, on the Administration tab, set the administrative tasks.
- CWWBW0112E: The authorization task for onEvent event number {0} of the process event handler is not set.
- Explanation: The authorization task for the specified onEvent event must be set.
- User Action: In WebSphere Integration Developer, click the specified onEvent event. In the Properties view, on the Authorization tab, set the authorization task.
- CWWBW0113E: The duration of the {0} process timeout event is not set.
- Explanation: A timeout on an onAlarm event must define a duration.
- User Action: In WebSphere Integration Developer, click the process timeout event. In the Properties view, on the Details tab, set the duration of the timeout.
- CWWBW0114E: The correlation ''set'' attribute must be set (process event handler, onEvent event number {0}, correlation element number {1}).
- Explanation: The correlation set attribute must be set for all of the correlation elements.
- User Action: Set the set attribute.
- CWWBW0200E: Catch number {1} in the fault handler of the {0} activity does not contain an activity; therefore, it cannot run.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Business Process editor, add an activity to the catch by selecting an activity from the palette and dropping it onto the catch. Or right-click the catch and select delete to remove the catch.
- CWWBW0201E: The catch-all element does not contain an activity (fault handler of the {0} activity); therefore, it cannot run.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Business Process editor, add an activity to the catch-all by selecting an activity from the palette and dropping it onto the catch-all. Or right-click the catch-all and select delete to remove the catch-all.
- CWWBW0202E: The compensation handler must contain an activity (compensation handler of activity ''{0}'').
- Explanation: An empty compensation handler cannot run.
- User Action: Remove the compensation handler or add an activity to it.
- CWWBW0203E: The partner of the {0} activity is not set.
- Explanation: For invoke, receive, and reply activities, the partner must be set.
- User Action: In WebSphere Integration Developer, click the activity. In the Properties view, on the Details tab, set the partner.
- CWWBW0204E: The operation for the {0} activity is missing.
- Explanation: For invoke, receive, and reply activities, the operation must be specified.
- User Action: In WebSphere Integration Developer, double-click the error message and select the specified activity. In the Properties view, on the Details tab, browse for and select an operation.
- CWWBW0205E: The duration on the timeout of the {0} activity is not set.
- Explanation: A timeout on an expiration must define a duration.
- User Action: In WebSphere Integration Developer, click the activity. In the Properties view, on the Expiration tab, set the duration.
- CWWBW0206E: The variable of the {2} parameter (parameter number {1} in the input or output element) of the {0} activity is not set.
- Explanation: The specified variable for the activity is mandatory.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, set the variable.
- CWWBW0207E: The administrative task for the {0} activity is not set.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, click the activity. In the Properties view, on the Administration tab, set the administrative task.
- CWWBW0208E: The authorization task for the {0} activity is not set.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, click the activity. In the Properties view, on the Authorization tab, set the authorization task.
- CWWBW0209E: The correlation ''set'' attribute must be set (activity ''{0}'', correlation element number {1}).
- Explanation: The correlation set attribute must be set for all of the correlation elements.
- User Action: Set the set attribute.
- CWWBW0210E: An exception occurred when using the {0} XML Path Language (XPath) plug-in for the XPath expression on the {1} activity (exception {2}).
- Explanation: The plug-in cannot be used.
- User Action: Check the technical information databases on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/. If you cannot find the information that you need to solve the problem, contact your technical support provider or again refer to the WebSphere Process Server support site for information about IBM Software Support and Services.
- CWWBW0211E: The toVariable or fromVariable attribute in the fromPart or toPart element must be set ({0} activity, fromPart or toPart number {1}).
- Explanation: A mandatory fromPart or toPart attribute is not defined.
- User Action: Set the toVariable or fromVariable attribute.
- CWWBW0212E: The part attribute in the fromPart or toPart element must be set ({0} activity, fromPart or toPart number {1}).
- Explanation: A mandatory fromPart or toPart attribute is not defined.
- User Action: Set the part attribute.
- CWWBW0300E: The {0} assign activity does not contain a copy element.
- Explanation: The assign activity must contain one or more copy elements. These elements specify the data that is to be copied, its location, and the destination of the copied data.
- User Action: In WebSphere Integration Developer, click the specified assign activity. In the Properties view, on the Details tab, add a copy element.
- CWWBW0301E: Copy element number {1} in the {0} assign activity does not include a ''from'' element.
- Explanation: The copy element must contain one "from" element and one "to" element. These elements specify the data that is to be copied, its location, and the destination of the copied data.
- User Action: In WebSphere Integration Developer, click the specified assign activity. In the Properties view, on the Details tab, locate the copy element and add a "from" element to it.
- CWWBW0302E: Copy element number {1} in the {0} assign activity does not include a ''to'' element.
- Explanation: The copy element must contain one "from" element and one "to" element. These elements specify the data that is to be copied, its location, and the destination of the copied data.
- User Action: In WebSphere Integration Developer, click the specified assign activity. In the Properties view, on the Details tab, locate the copy element and add a "to" element to it.
- CWWBW0303E: The reference-scheme attribute must be set (assign activity ''{0}'', copy element number {1}, from-spec, serviceRef element).
- Explanation: The service reference element must define a reference-scheme.
- User Action: Set the reference-scheme attribute.
- CWWBW0304E: The serviceRef element cannot be empty (assign activity ''{0}'', copy element number {1}, from-spec, serviceRef element).
- Explanation: The serviceRef element must contain an element.
- User Action: Set any of the allowed elements.
- CWWBW0400E: The target on the {0} compensateScope activity is not set.
- Explanation: The compensateScope elements must define a target.
- User Action: In WebSphere Integration Developer, click the compensateScope activity. In the Properties view, on the Details tab, set the target activity.
- CWWBW0600E: The {0} parallel-activities activity does not contain an activity. An empty parallel-activities activity cannot run.
- Explanation: Each parallel-activities activity must contain an activity.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Business Process editor, add an activity to the parallel-activities activity by selecting an activity from the palette and dropping it onto the parallel-activities activity. Alternatively, remove the parallel-activities activity by right-clicking the activity and selecting Delete.
- CWWBW0650E: The generalized flow activity must contain an activity. Add an activity to it (generalized flow activity ''{0}'').
- Explanation: An empty generalized flow activity cannot run.
- User Action: Remove the generalized flow activity, or add an activity to it.
- CWWBW0700E: The partner for the compensation action in the {0} invoke activity is not set.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, click the specified invoke activity. In the Properties view, on the Compensation tab, set the partner attribute.
- CWWBW0701E: The operation on the compensation action in the {0} invoke activity is not set.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, click the invoke activity. In the Properties view, on the Compensation tab, set the operation attribute.
- CWWBW0702E: The variable in the {2} parameter for the compensation action is not set (parameter number {1} in the input or output element of the {0} invoke activity).
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, click the specified invoke activity. In the Properties view, on the Compensation tab, set the variable for the compensation action.
- CWWBW0800E: The {0} receive choice activity does not contain a receive element. An empty receive choice activity cannot run.
- Explanation: A receive choice activity must contain an activity.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Business Process editor, add a Receive Case by selecting "Add a Receive Case" from the action bar. Alternatively, remove the Receive Choice element by right-clicking it and selecting Delete.
- CWWBW0801E: Receive element number {1} of the {0} receive choice activity is missing an activity. An empty receive element cannot run.
- Explanation: A receive element must contain an activity.
- User Action: In WebSphere Integration Developer, double-click the error message and add an activity to the receive element by selecting the activity from the palette and dropping it onto the receive element. Alternatively, remove the receive element by right-clicking it and selecting delete.
- CWWBW0802E: The timeout event must contain an activity (receive choice activity ''{0}'', timeout event number {1}).
- Explanation: An empty timeout event cannot run.
- User Action: Add an activity to the timeout event or remove the event.
- CWWBW0803E: The partner for receive element number {1} in the {0} receive choice activity is missing.
- Explanation: The partner must be specified for a receive element.
- User Action: In WebSphere Integration Developer, double-click the error message and select the specified receive element. In the Properties view, on the Details tab, browse for and select a partner.
- CWWBW0804E: The operation for receive element number {1} in the {0} receive choice activity is missing.
- Explanation: The operation must be specified for a receive element.
- User Action: In WebSphere Integration Developer, double-click the error message and select the specified receive element. In the Properties view, on the Details tab, select an operation.
- CWWBW0805E: The variable of the {3} parameter is not set ({0} receive choice activity, input or output element of receive element number {1}, parameter number {2}).
- Explanation: A variable for the onMessage element on a receive choice must be defined.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, set the variable.
- CWWBW0806E: The authorization task for receive element number {1} of the {0} receive choice activity is not set.
- Explanation: The authorization task for specified receive element must be set.
- User Action: In WebSphere Integration Developer, click the receive element. In the Properties view, on the Authorization tab, set the authorization task.
- CWWBW0807E: The duration on the timeout element is not set ({0} receive choice activity, timeout event number {1}).
- Explanation: A timeout on an onAlarm event must define a duration.
- User Action: In WebSphere Integration Developer, click the timeout event of the receive choice activity. In the Properties view, on the Details tab, set the duration on the timeout.
- CWWBW0808E: The correlation ''set'' attribute must be set (pick activity ''{0}'', onMessage element number {1}, correlation element number {2}).
- Explanation: The correlation set attribute must be set for all of the correlation elements.
- User Action: Set the set attribute.
- CWWBW1200E: The {0} scope activity does not contain an activity; therefore it cannot run.
- Explanation: A scope activity must contain an activity.
- User Action: In WebSphere Integration Developer, double-click the error message and add an activity to the specified scope activity by selecting the activity from the palette and dropping it onto the scope element. Alternatively, remove the scope activity by right-clicking it and selecting Delete.
- CWWBW1201E: The onEvent event must contain an activity (event handler of scope activity ''{0}'', onEvent event number {1}).
- Explanation: An empty onEvent event cannot run.
- User Action: Add an activity to the onEvent event, or remove the event.
- CWWBW1202E: The timeout event must contain an activity (event handler of scope activity ''{0}'', timeout event {1}).
- Explanation: An empty timeout event cannot run.
- User Action: Add an activity to the timeout event, or remove the event.
- CWWBW1203E: The partner for onEvent event number {1} in the {0} scope activity is not set.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, click the onEvent event. In the Properties view, on the Details tab, set the partner.
- CWWBW1204E: The operation for onEvent event number {1} in the {0} scope activity is not set.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, click the onEvent event. In the Properties view, on the Details tab, set the operation attribute.
- CWWBW1205E: The variable is not set for the either input or output element of onEvent event {1} in the {0} scope activity (parameter number {2}, {3} parameter).
- Explanation: A mandatory variable for the onEvent element on a scope is not defined.
- User Action: In WebSphere Integration Developer, click the onEvent event. In the Properties view, on the Details tab, set the variable.
- CWWBW1206E: The authorization task for onEvent event {1} of the {0} scope activity is not set.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, click the onEvent event. In the Properties view, on the Authorization tab, set the authorization task.
- CWWBW1207E: The duration of {1} timeout event in the {0} scope activity is not set.
- Explanation: A timeout on an onAlarm event must define a duration.
- User Action: In WebSphere Integration Developer, click the scope timeout event. In the Properties view, on the Details tab, set the duration on the timeout.
- CWWBW1208E: The correlation ''set'' attribute must be set (scope event handler, of scope activity ''{0}'', onEvent event number {1}, correlation element number {2}).
- Explanation: The correlation set attribute must be set for all of the correlation elements.
- User Action: Set the set attribute.
- CWWBW1300E: The sequence activity must contain an activity (sequence activity ''{0}'').
- Explanation: An empty sequence activity cannot run.
- User Action: Remove the sequence activity, or add an activity to it.
- CWWBW1400E: The {0} choice activity does not contain a case. An empty choice activity cannot run.
- Explanation: A choice activity must contain an activity.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Business Process editor, add a Case by selecting "Add a Case" in the action bar. Alternatively, remove the Choice element by right-clicking it and selecting Delete.
- CWWBW1401E: Case number {1} in the {0} choice activity does not specify a condition.
- Explanation: The condition defines which case branch runs. The value of the condition is either true or false when it runs.
- User Action: Specify the case condition. In WebSphere Integration Developer, double-click the error message and select the specified case. In the Properties view, on the Details tab, specify a condition.
- CWWBW1402E: Case number {1} in the {0} choice activity does not contain an activity. An empty case cannot run.
- Explanation: A case must contain an activity.
- User Action: Add an activity to the case or remove the element. In WebSphere Integration Developer, double-click the error message and add an activity to the specified case element. Alternatively, remove the case element by right-clicking it and selecting Delete.
- CWWBW1403E: The otherwise branch does not contain an activity ({0} choice activity); therefore, it cannot run.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Business Process editor, add an activity to the otherwise by selecting an activity from the palette and dropping it onto the otherwise branch. Or right-click the otherwise and select delete to remove the Otherwise branch.
- CWWBW1500E: The {0} throw activity does not have a fault name.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, click the throw activity. In the Properties view, on the Details tab, set the fault name.
- CWWBW1700E: The ''{0}'' while loop activity does not specify a condition.
- Explanation: The condition specifies whether the activity will run again. When the condition runs, it holds either true or false.
- User Action: Specify a condition for the while loop activity. In WebSphere Integration Developer, select the specified while loop activity. In the Properties view, on the Details tab, and specify a condition.
- CWWBW1701E: The ''{0}'' while loop activity does not contain an activity. An empty while loop activity cannot run.
- Explanation: A while loop must contain an activity.
- User Action: Remove the while loop activity, or add an activity to it. In WebSphere Integration Developer, double-click the error message and add an activity to the specified while loop activity. Alternatively, remove the while loop activity by right-clicking it and selecting Delete.
- CWWBW1950E: The {0} forEach activity does not have an index-variable name.
- Explanation: The index-variable name must be set for a forEach activity.
- User Action: In WebSphere Integration Developer, click the forEach activity. In the Properties view, on the Details tab, set the index-variable name.
- CWWBW1951E: The {0} forEach activity does not contain a start value for the iteration.
- Explanation: A forEach activity must specify a start value in the iterator element.
- User Action: Remove the forEach activity, or ensure that it specifies a start value for the iteration. In WebSphere Integration Developer, click the specified forEach activity. In the Properties view, on the Details tab, specify the iteration condition.
- CWWBW1952E: The {0} forEach activity does not contain an end value for the iteration.
- Explanation: A forEach activity must specify an end value in the iterator element.
- User Action: Remove the forEach activity, or ensure that it specifies an end value for the iteration. In WebSphere Integration Developer, click the specified forEach activity. In the Properties view, on the Details tab, specify the iteration condition.
- CWWBW1953E: The {0} forEach activity does not contain a scope activity.
- Explanation: A forEach activity must contain a scope, and it can contain only one scope.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Business Process editor, add a scope by selecting the scope activity from the palette and dropping it onto the For Each. Alternatively, remove the For Each element by right-clicking it and selecting Delete.
- CWWBW2000E: The {0} RepeatUntil activity does not specify a condition.
- Explanation: The condition specifies whether the activity will run again. When the condition runs, it holds either true or false.
- User Action: Specify a condition for the RepeatUntil activity. In WebSphere Integration Developer, select the specified While activity. In the Properties view, on the Details tab, specify a condition.
- CWWBW2001E: The {0} RepeatUntil activity does not contain an activity. An empty RepeatUntil activity cannot run.
- Explanation: A RepeatUntil activity must contain an activity.
- User Action: Remove the RepeatUntil activity, or add an activity to it. In WebSphere Integration Developer, double-click the error message and add an activity to the specified RepeatUntil activity. Alternatively, remove the RepeatUntil activity by right-clicking it and selecting Delete.
- CWWBW3000E: The schemaLocation attribute is not set. It must be one of ''{0}''.
- Explanation: The schemaLocation attribute must be set in the process element otherwise the syntactical validation cannot be performed.
- User Action: Set the schemaLocation attribute to one of the supported values.
- CWWBW3001E: The value of the schemaLocation attribute is incorrect. It must be set to one of ''{0}'', or a value handled by a custom activity plug-in.
- Explanation: The value of the schemaLocation attribute must be correct, otherwise the syntactical validation cannot be performed.
- User Action: Set the schemaLocation attribute to one of the supported values.
- CWWBW3002E: The partnerLinkType ''{0}'' was not found (process partner ''{1}'').
- Explanation: The partnerLinkType referenced in the process partner is not defined in the WSDL interface.
- User Action: Check that the partnerLinkType is defined correctly in the WSDL interface.
- CWWBW3003E: The myRole role ''{0}'' was not found (process partner ''{1}'', partnerLinkType ''{2}'').
- Explanation: The role referenced in the partner is not defined in the partnerLinkType.
- User Action: Check that the role is defined correctly in the partnerLinkType.
- CWWBW3004E: The portType in the role ''{0}'' is not set (process partner ''{1}'', partnerLinkType ''{2}'').
- Explanation: The portType in the role is needed to access the operations.
- User Action: Ensure that the portType is set.
- CWWBW3005E: The {0} interface of the {1} process partner was not found ({2} partnerLinkType, {3} role).
- Explanation: The interface that is referred to in the role is not defined in the Web Services Description Language (WSDL) interface.
- User Action: In WebSphere Integration Developer, click the partner. In the Properties view, on the Details tab, set the interface.
- CWWBW3006E: The partnerRole role ''{0}'' was not found (process partner ''{1}'', partnerLinkType ''{2}'').
- Explanation: The role referenced in the partner is not defined in the partnerLinkType.
- User Action: Check that the role is defined correctly in the partnerLinkType.
- CWWBW3007E: Either the myRole role, the partnerRole role, or both must be defined (process partner ''{0}'').
- Explanation: A partner must have a definition for the myRole role, the partnerRole role, or both.
- User Action: Define the roles for the partner.
- CWWBW3008E: There are too many variable type definitions set for the process variable ''{0}'' (messageType ''{1}'', type ''{2}'', element ''{3}'').
- Explanation: The messageType, type, or element attributes define the type of a variable. Exactly one of these attributes must be set.
- User Action: Ensure that there is only one variable type definition set for the process variable.
- CWWBW3009E: The {0} process variable does not have a type.
- Explanation: The variable can point either to a data type (XML Schema Definition (XSD) type or XSD element) or to an interface message (WSDL message).
- User Action: In WebSphere Integration Developer, click the variable. In the Properties view, on the Details tab, select either a data type or an interface.
- CWWBW3010E: The {0} interface message in the {1} process variable was not found.
- Explanation: The message that is referred to in the process variable must be defined in a Web Services Description Language (WSDL) interface.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Description tab, select an existing Interface, Operation and Direction.
- CWWBW3011E: The {0} type, which is referred to in the {1} process variable, was not found.
- Explanation: The type that is referred to in the process variable must be a valid simple type, or it must be defined inline in an interface or a business object.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Description tab, browse for an existing Data Type.
- CWWBW3012E: The {0} element, which is referred to in the {1} process variable, was not found.
- Explanation: The element that is referred to in the process variable must be defined either inline in an interface or in a business object.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Description tab, browse for an existing Data Type.
- CWWBW3013E: The {0} process variable name is already used.
- Explanation: The name of a variable must be unique within its scope.
- User Action: In WebSphere Integration Developer, click the variable. In the Properties view, on the Details tab, specify another name.
- CWWBW3014E: Catch element number {0} in the process fault handler is missing a fault name or a fault variable with a type specification.
- Explanation: For a catch, the fault name, the fault variable with a type specification, or both must be set.
- User Action: In WebSphere Integration Developer, click the catch. In the Properties view, on the Details tab, specify a fault name, a fault variable, or both.
- CWWBW3015E: If the catch has the fault variable set, the fault variable must have a type (process fault handler, catch element number {0}, fault variable ''{1}'').
- Explanation: If a fault variable is set on a catch, the type of the variable must be set.
- User Action: In WebSphere Integration Developer, click the catch. In the Properties view, on the Details tab, specify a data-type variable or an interface variable.
- CWWBW3016E: The catch element cannot have the fault message type and the fault type set (process fault handler, catch element number {0}, fault message type ''{1}'', faultType ''{2}'').
- Explanation: Either the fault message type or the fault type can be set on the catch element.
- User Action: Either remove the fault message type or the fault type.
- CWWBW3017E: If the catch element has the fault message type set, it must also have a fault variable set (process fault handler, catch element number {0}, fault message type ''{1}'').
- Explanation: If the fault message type is set on the catch element, the fault variable must be set too.
- User Action: Define the fault variable.
- CWWBW3018E: If the catch element has the fault type set, it must also have a fault variable set (process fault handler, catch element number {0}, fault type ''{1}'').
- Explanation: If the fault type is set on the catch element, the fault variable must be set too.
- User Action: Specify a fault variable for the catch element.
- CWWBW3019E: The {0} interface message that is referred to in the {2} fault variable of catch element number {1} in the process fault handler was not found.
- Explanation: The specified message is not defined in the Web Services Description Language (WSDL) interface.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing Interface and Operation where a fault is defined.
- CWWBW3020E: The {0} data type that is referred to in the {2} fault variable of catch element number {1} in the process fault handler was not found.
- Explanation: The specified data type must be a valid simple type or it must be defined inline in an interface or a business object.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing Data Type.
- CWWBW3021E: The process fault handler does not contain a catch or a catch-all element.
- Explanation: A fault handler must have at least one catch or catch-all element.
- User Action: To add a catch or catch-all element, in WebSphere Integration Developer, click the process fault handler. From the action bar, select the appropriate entry and add a catch or catch-all element.
- CWWBW3023E: The display ID ''{0}'' is not unique.
- Explanation: The display ID is an identifier for the activities of a process model. This ID must be unique.
- User Action: Ensure that all of the display IDs are unique.
- CWWBW3024W: The microflow specifies that its life cycle is bound to the invoking business process (autonomy attribute). The setting will be ignored.
- Explanation: For a microflow, the autonomy is derived from the invocation circumstances of the microflow.
- User Action: Remove the autonomy attribute from the process. In WebSphere Integration Developer, click the start node. In the Properties view, on the Details tab, clear the "Bind the life cycle to the invoking business process" check box.
- CWWBW3025W: The long-running process specifies the compensationSphere attribute. The attribute will be ignored.
- Explanation: The compensationSphere attribute is has no meaning for long-running processes because long-running processes do not have an associated compensation sphere.
- User Action: In WebSphere Integration Developer, click the start node. In the Properties view, on the Details tab, remove the compensation sphere setting.
- CWWBW3026E: The process event handler does not contain an onEvent event or a timeout event.
- Explanation: An event handler must have at least one onEvent event or one timeout event.
- User Action: Define an onEvent event or a timeout event, or remove the event handler. To define an event in WebSphere Integration Developer, click the process event handler. From the action bar that appears, select an entry and add an onEvent event or a timeout event.
- CWWBW3027E: The {0} interface partner that is referred to in process onEvent event number {1} was not found.
- Explanation: The interface partner that is referred to in the specified onEvent event is Either not defined or it is incorrect.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing Partner, Interface and Operation.
- CWWBW3028E: The partner ''{0}'' does not define the myRole role (process onEvent event number {1}).
- Explanation: Partners must define the myRole role if these links are used in onEvent events.
- User Action: Define the myRole role for the partner or use a different partner.
- CWWBW3029E: The {0} interface that is referred to in the process onEvent event number {1} was not found.
- Explanation: The interface that is referred to in the specified onEvent event is either not defined in the Web Services Description Language (WSDL) interface or it is incorrect.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing Interface and Operation.
- CWWBW3030E: The interfaces that are referred to in process onEvent event number {0} and in the {1} myRole role are not the same ({2} partner, {3} partnerLinkType).
- Explanation: When the portType attribute is set, it must be the same in the myRole role as in the process onEvent event number.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing Partner, Interface and Operation.
- CWWBW3031E: The {0} operation of process onEvent event number {1} was not found.
- Explanation: The operation that is referred to in the onEvent event is not defined in the interface.
- User Action: In WebSphere Integration Developer, click the specified onEvent event in the process event handler. In the Properties view, on the Details tab, browse for and select another operation.
- CWWBW3032E: The input element is not defined in the {0} operation, which is referred to in process onEvent event number {1}.
- Explanation: The operation that is referred to in the onEvent event must have an input element.
- User Action: To specify another operation, in WebSphere Integration Developer, click the onEvent event in the process event handler. In the Properties view, on the Details tab, browse for and select another operation. To define an input for the operation, use the Interface editor.
- CWWBW3033E: The messageType is not set in the input element of the operation ''{0}'' (process onEvent event number {1}).
- Explanation: The input messageType must be set when the operation is used in this onEvent event.
- User Action: Set the input messageType or use a different operation.
- CWWBW3034E: The messageType ''{0}'' referenced in the operation ''{1}'' was not found (process onEvent event number {2}).
- Explanation: The messageType referenced must be defined when the operation is used in this onEvent event.
- User Action: Set the messageType, or use a different operation.
- CWWBW3035E: The messageType of variable ''{0}'' and the input element of the operation ''{1}'' must be the same (process onEvent event number {2}).
- Explanation: The messageType of the variable and the input element of the operation must be the same.
- User Action: Ensure that both the variable and the input element have the same messageType.
- CWWBW3036E: The variable for process onEvent event number {0} is not set.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, click the onEvent event in the process event handler. In the Properties view, on the Details tab, set a variable.
- CWWBW3037E: The messageType or element attribute is not set (process onEvent event number {0}).
- Explanation: A mandatory attribute (messageType or element) for the onEvent event is not defined.
- User Action: Define either the messageType or the element attribute.
- CWWBW3038E: The messageType ''{0}'' was not found (process onEvent event {1}).
- Explanation: The messageType referenced in the onEvent event is not defined in the WSDL interface.
- User Action: Check that the messageType is defined correctly in the WSDL interface.
- CWWBW3039E: The {0} correlation set, which is used in process onEvent event number {1}, was not found.
- Explanation: The correlation set that is used in the specified onEvent event is not defined.
- User Action: To define the correlation set, in WebSphere Integration Developer, click the onEvent in the process event handler. In the Properties view, on the Correlation tab, select a valid correlation set.
- CWWBW3040E: Process timeout event number {0} must specify at least a ''for'' expression, an ''until'' expression, or a repeatEvery expression.
- Explanation: The "for" expression defines the duration expression after which the event is signaled. The "until" expression specifies when the timeout event is fired. If the repeatEvery expression is specified, the timeout event is fired once each time the duration period expires. One of these three expressions or a repeatEvery expression with a "for" or "until" expression must be specified in a timeout event.
- User Action: In WebSphere Integration Developer, click the timeout in the process event handler. In the Properties view, on the Details tab, specify a "for" or "until" expression, or, on the Repeat tab, specify a repeatEvery expression.
- CWWBW3041E: Process timeout event number {0} must specify at least a ''for'' expression, an ''until'' expression, a timeout expression, or a repeatEvery expression.
- Explanation: The "for" expression defines the duration expression after which the event is signaled. The "until" expression specifies when the timeout event is fired. The timeout element specifies a timeout using either a calendar that is supplied by the WebSphere Application Server scheduling service or user-written calendars that adhere to the scheduling service conventions. If the repeatEvery expression is specified, the timeout event is fired once each time the duration period expires. One of these four expressions or a repeatEvery expression with a "for", "until", or timeout expression must be specified in a timeout event.
- User Action: In WebSphere Integration Developer, click the timeout in the process event handler. In the Properties view, on the Details tab, specify a "for", timeout, or "until" expression, or, on the Repeat tab, specify a repeatEvery expression.
- CWWBW3042E: Process timeout event number {0} cannot specify a ''for'' expression and a timeout expression or an ''until'' expression and a timeout expression.
- Explanation: The "for" expression defines the duration expression after which the event is signaled. The "until" expression specifies when the timeout event is fired. The timeout element specifies a timeout using either a calendar that is supplied by the WebSphere Application Server scheduling service or user-written calendars that adhere to the scheduling service conventions. If the repeatEvery element is specified, the timeout event is fired once each time the duration period expires. One of these four expressions or a repeatEvery expression with a "for", "until", or timeout expression must be specified in a timeout event.
- User Action: In WebSphere Integration Developer, click the timeout in the process event handler. In the Properties view, on the Details tab, specify a "for", timeout, or "until" expression, or, on the Repeat tab, specify a repeatEvery expression.
- CWWBW3043E: The expression language ''{0}'' is not supported. It must be one of ''{1}'' (process timeout event {2}).
- Explanation: The specified expression language is unknown. Expressions specified in this expression language cannot run.
- User Action: Use one of the supported expression languages.
- CWWBW3044E: The process query language ''{0}'' is not supported. It must be one of ''{1}''.
- Explanation: The specified query language is unknown. Queries specified in this query language cannot run.
- User Action: Use one of the supported query languages.
- CWWBW3045E: The process expression language ''{0}'' is not supported. It must be one of ''{1}''.
- Explanation: The specified expression language is unknown. Expressions specified in this expression language cannot run.
- User Action: Use one of the supported expression languages.
- CWWBW3046E: The {0} correlation property of the {1} process correlation set was not found.
- Explanation: The correlation property must be defined.
- User Action: In WebSphere Integration Developer, to define a property, click the plus sign (+) in the correlation property category on the right side of the process editor screen. Then add property to the specified correlation set. To remove the correlation property, select the correlation set. In the Properties view, on the Description tab, check the property to add it.
- CWWBW3047E: The type of the {0} correlation property of the {1} process correlation set is not set.
- Explanation: The type of the property must be set. Only XML schema simple types are allowed.
- User Action: In WebSphere Integration Developer, select the correlation property. In the Properties view, on the Description tab, browse for and select an XML simple type.
- CWWBW3048E: The {0} type of the {1} correlation property was not found or is not an allowed or valid XML schema simple type in this context ({2} process correlation set).
- Explanation: The type that is used in the property of the correlation set is not defined, not allowed (for example, it is a complex type, a list type, or a union type), or not valid (for example, a loop in the type definition). Allowed types are all of the XML schema primitive simple types and all simple types that are derived by restriction from a primitive simple type.
- User Action: In WebSphere Integration Developer, select the correlation property. In the Properties view, on the Description tab, browse and select for an XML simple type.
- CWWBW3049I: The {0} correlation set is not used.
- Explanation: No additional information is available.
- User Action: To use a correlation set, in WebSphere Integration Developer, select a messaging activity (such as Invoke, Receive, Reply). In the Properties view, on the Correlation tab, add the correlation set. To remove the correlation set from the model, select the correlation set in the correlation set category on the right side of the process editor screen and delete it.
- CWWBW3050E: The {0} correlation set is used, but it is not initiated.
- Explanation: A correlation set that is used must be initiated.
- User Action: Initiate the correlation set in the activity where the correlation set is first used. In WebSphere Integration Developer, select the activity (usually a Receive or a Receive Choice activity). In the Properties view, on the Correlation tab, select "yes" as the value for the initiation setting.
- CWWBW3051E: The {0} human task activity is used in a microflow (uninterruptible process).
- Explanation: Microflows must not contain asynchronous activities, such as human task activities or wait activities.
- User Action: Define the process as a long-running process, or remove the asynchronous activity. To define the process as long running, in WebSphere Integration Developer, click the start node of the process. In the Properties view, on the Details tab, select the "Process is long-running" check box. Alternatively, remove the human task activity by right-clicking it and selecting Delete.
- CWWBW3052E: The {0} wait activity is used in a microflow (uninterruptible process).
- Explanation: Microflows (uninterruptible processes) must not contain asynchronous activities, such as human task activities or wait activities.
- User Action: Define the process as a long-running process, or remove the asynchronous activity. To define the process as long running, in WebSphere Integration Developer, click the start node of the process. In the Properties view, on the Details tab, select the "Process is long-running" check box. Alternatively, remove the wait activity by right-clicking it and selecting Delete.
- CWWBW3053E: The timeout events in the {0} receive choice activity are used although the activity is in a microflow (uninterruptible process).
- Explanation: Receive choice activities that are in microflows cannot have timeout events.
- User Action: Remove the timeout events, or define the process as long running. To define the process as long running, in WebSphere Integration Developer, click the start node of the process. In the Properties view, on the Details tab, select the "Process is long-running" check box. Alternatively, remove the timout element by right-clicking it and selecting Delete.
- CWWBW3054E: A process that is not long running contains more than one receive choice or receive activity, which are {0}.
- Explanation: Processes that are not long running can have only one start point.
- User Action: To make the process long running, click somewhere in the white space of your canvas in WebSphere Integration Developer. In the Properties view, on the Details tab, select the "Process is long-running" check box. To define only one receive choice or receive activity, delete all of the specified receive choice and receive activities.
- CWWBW3055E: The process does not implement the {0} operation of the {1} interface.
- Explanation: The process model implements one or more operations of the interface but not the specified operation.
- User Action: In WebSphere Integration Developer, in the Business Process editor, add a receive or a receive choice activity by selecting a receive or a receive choice activity from the palette and dropping it onto the process. The Receive must use the specified operation. Alternatively, add an Event Handler on the process or an existing scope by clicking the process or scope and select "Add an Event Handler" in the action bar. The onEvent element must use the specified operation.
- CWWBW3056E: The process cannot start. No receive choice or receive activity was found that creates a new process instance and does not have incoming links or preceding basic activities.
- Explanation: A process can start only when a receive choice or receive activity is available that creates a new process instance and when this activity is not the target of any links or has any preceding basic activities.
- User Action: Ensure that all of the receive choice and receive activities are defined correctly, or add a receive choice or receive activity that can create a process instance.
- CWWBW3057E: The variable must not be set because an output element is available (process onEvent event number {0}, variable ''{1}'').
- Explanation: The data received by this onEvent event can be stored in the onEvent variable, which must be message-typed, or in one or more XSD-typed variables specified in the output element.
- User Action: Remove the variable attribute from the onEvent event.
- CWWBW3058E: Abstract processes are not supported.
- Explanation: Abstract process models are not supported because they cannot run.
- User Action: Declare the process model as non-abstract.
- CWWBW3059E: A data-type variable in process onEvent event number {1} is used for the {0} message.
- Explanation: The input message of the operation in the onEvent event cannot be used with the parameter extension. For example, if the message contains an array, it cannot be mapped to data-typed variables in the process.
- User Action: Either modify the message that is used with the parameter extension, or use an interface-type variable.
- CWWBW3060E: The parameter ''{0}'' is not mapped to an element or part. Map it to a valid element or part (process onEvent event number {1}, parameter number {2}).
- Explanation: A parameter has been found that does not map to an element in the wrapper or to a part in the message.
- User Action: Remove the parameter or map it to a valid element or part.
- CWWBW3061E: The {0} variable name has been used in parameter number {2}, which is contained in the output element of process onEvent event number {1}.
- Explanation: A variable name can be used only once in an output element.
- User Action: In WebSphere Integration Developer, select the onEvent in the event handler of the process. In the Properties view, on the Details tab, specify another variable name.
- CWWBW3062E: A matching correlation property alias definition was not found for the {0} property and the {1} message (process onEvent event number {2}, {3} correlation set).
- Explanation: A correlation property alias definition is needed to map the parts of a messageType property to the correlation properties.
- User Action: In WebSphere Integration Developer, select the specified correlation property. In the Properties view, on the Description tab, specify the correlation information for the operation that is associated with the specified onEvent event.
- CWWBW3063E: The part ''{0}'' referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' was not found (process onEvent event number {3}, correlation set ''{4}'').
- Explanation: The part must be defined for the messageType.
- User Action: Define the part, or use an existing part in the propertyAlias.
- CWWBW3064E: The part ''{0}'' referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' does not reference a valid XML schema simple type (process onEvent event number {3}, correlation set ''{4}'').
- Explanation: The selected part of the messageType must be an XML schema simple type because a property can only have XML schema simple types.
- User Action: Select a part that has an XML schema simple type.
- CWWBW3065E: The type of the part ''{0}'' of the messageType ''{1}'' and the type of the property ''{2}'' are not the same (process onEvent event number {3}, correlation set ''{4}'').
- Explanation: The selected part of the messageType in the propertyAlias does not have the same type as the property type.
- User Action: Select a part that has same XML schema simple type as the property type.
- CWWBW3066E: Multiple propertyAlias definitions were found for the property ''{0}'' and the messageType ''{1}'' (process onEvent event number {2}, correlation set ''{3}'').
- Explanation: A property-messageType pair can have only one propertyAlias definition.
- User Action: Ensure that only one propertyAlias is available for the property-messageType pair. If you need more than one part of a messageType as a property, create properties and propertyAlias definitions for additional parts of the same messageType.
- CWWBW3067E: The {0} human task, which is used as the administrative task for the process or as the default administrative human task, cannot be found.
- Explanation: The specified human task, which is referred to in the process adminTask or the activity AdminTask element, cannot be found.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Administration tab, remove the human task reference and add a new human task.
- CWWBW3068E: The {0} human task, which is used as the administrative task for the process or as the default administrative human task, is not an administration task.
- Explanation: The specified human task, which is referred to in the process adminTask or the activityAdminTask element, must be an administration task.
- User Action: In WebSphere Integration Developer, select the start node of the process. In the Properties view, on the Administration tab, specify the human task.
- CWWBW3069E: The {0} human task that is used for authorization in process onEvent event number {1} cannot be found.
- Explanation: The specified human task, which is referred to in the process onEvent event, cannot be found.
- User Action: To ensure that the human task is found, in WebSphere Integration Developer, select the onEvent event in the event handler of the process. In the Properties view, on the Authorization tab, specify a human task for authorization.
- CWWBW3070E: The {0} human task is not an invocation task. The onEvent event number is {1} in the process event handler.
- Explanation: No additional information is available
- User Action: In WebSphere Integration Developer, select the onEvent event in the event handler of the process. In the Properties view, on the Authorization tab, specify a human task for authorization.
- CWWBW3071E: The interface that is referred to in process onEvent event number {0} and in the {1} human task are not the same.
- Explanation: The interfaces must be the same.
- User Action: Ensure that the interfaces are the same.
- CWWBW3072E: The operation referenced in process onEvent event number {0} and in the human task ''{1}'' must be the same.
- Explanation: The operations must be the same.
- User Action: Ensure that the operations are the same.
- CWWBW3073E: The part is not set in the propertyAlias for the property ''{0}'' and the messageType ''{1}'' (process onEvent event number {2}, correlation set ''{3}'').
- Explanation: The part must be set in the propertyAlias.
- User Action: Set the part.
- CWWBW3074E: The query language ''{0}'' used in the propertyAlias is not supported. It must be one of ''{1}'' (process onEvent event number {2}, correlation set ''{3}'', propertyAlias for the property ''{4}'' and the messageType ''{5}'').
- Explanation: The specified query language is unknown. Queries specified in this query language cannot be run.
- User Action: Use one of the supported query languages.
- CWWBW3075E: The expression is not valid (process timeout event {0}, expression language ''{1}'').
- Explanation: The specified expression is not a valid expression for the specified expression language.
- User Action: Check the expression and the expression language.
- CWWBW3076E: A reply activity was not found that matches process onEvent event number {0}.
- Explanation: For every two-way operation onEvent event in the process event handler, the process must contain at least one reply activity with the same interface and operation as the one defined in the onEvent element.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, note the partner, interface and operation. Select the reply activity from the palette and drop it to the process. Use the same partner, interface and operation which has been specified on the onEvent element.
- CWWBW3077E: An event handler is used in a microflow (uninterruptible process).
- Explanation: Microflows must not contain event handlers, either on the process or on scope activities.
- User Action: Define the process as a long-running process, or remove the event handler. To define the process as long running, in WebSphere Integration Developer, click the start node of the process. In the Properties view, on the Details tab, select the "Process is long-running" check box.
- CWWBW3078E: An event handler is used in a microflow (uninterruptible process). The scope activity is {0}.
- Explanation: Microflows must not contain event handlers, either on the process or on scope activities.
- User Action: Define the process as a long-running process, or remove the event handler. To define the process as long running, in WebSphere Integration Developer, click the start node of the process. In the Properties view, on the Details tab, select the "Process is long-running" check box. To remove the event handler, select the event handler at the specified scope and delete it.
- CWWBW3079E: A compensation handler is used in a microflow (uninterruptible process). The activity is {0}.
- Explanation: Microflows must not contain compensation handlers, either on scope activities or on invoke activities. However, you can use the undo action on invoke activities in microflows.
- User Action: Define the process as a long-running process, or remove the compensation handler. To define the process as long running, in WebSphere Integration Developer, click the start node of the process. In the Properties view, on the Details tab, select the "Process is long-running" check box. To remove the compensation handler, select the compensation handler at the specified activity and delete it
- CWWBW3080E: An expiration is used in a microflow (uninterruptible process). The activity is {0}.
- Explanation: Microflows must not contain expiration elements.
- User Action: Define the process as a long-running process, or remove the expiration. To define the process as long running, in WebSphere Integration Developer, click the start node of the process. In the Properties view, on the Details tab, select the "Process is long-running" check box. To remove the expiration, select the specified activity. In the Properties view, on the Expiration tab, delete the expiration expression.
- CWWBW3081E: The {0} compensate activity is used in a microflow (uninterruptible process).
- Explanation: Microflows must not contain compensate activities.
- User Action: Define the process as a long-running process, or remove the compensate activity. To define the process as long running, in WebSphere Integration Developer, click the start node of the process. In the Properties view, on the Details tab, select the "Process is long-running" check box. To remove the compensate activity, select it and click delete.
- CWWBW3082W: The one-way process cannot bind its life cycle to its invoking process. (child autonomy). The setting will be ignored.
- Explanation: For a one-way process, the autonomy cannot be set to "child" because one-way processes are called asynchronously, not synchronously.
- User Action: Remove the autonomy attribute from the process, or set it to "peer". To make the task a peer of its invoking business process, in WebSphere Integration Developer, click the start node of the process. In the Properties view, on the Details tab, clear the "Bind the life cycle to the invoking business process" check box.
- CWWBW3083E: More than one variable type definition is set for the variable ''{0}''. Set only one (process onEvent event number {1}, parameter number {2}, type ''{3}'', element ''{4}'').
- Explanation: The type, or element attributes define the type of a variable. Exactly one of these attributes must be set.
- User Action: Ensure that there is only one variable type definition set for the variable.
- CWWBW3084E: The {0} data-type declaration was not found (process onEvent event number {1}, parameter number {2}, {3} variable).
- Explanation: The XML Schema Definition (XSD) element declaration that is referred to in the variable must be defined either inline in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, deselect and reselect "Use data type variables mapping". Add a new parameter.
- CWWBW3085E: The {0} data type definition was not found (process onEvent event number {1}, parameter number {2}, {3} variable).
- Explanation: The XML Schema Definition (XSD) type definition that is referred to in the variable must be a valid built-in XML schema simple type, or it must be defined inline in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, deselect and reselect "Use data type variables mapping". Add a new parameter.
- CWWBW3086E: The {0} variable does not have a type definition (process onEvent event number {1}, parameter number {2}).
- Explanation: The type or element attributes specify the type of a variable. You must set one (and only one) of these attributes.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, deselect and reselect "Use data type variables mapping". Add a new parameter.
- CWWBW3087E: The {0} type definition was not found (process onEvent event number {1}, parameter number {2}, matching part or element: {3}).
- Explanation: The XML Schema Definition (XSD) type definition that is referred to in the matching part or element must be a valid built-in XML schema simple type, or it must be defined inline in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referred to and that it is defined correctly.
- CWWBW3088E: The {0} data-type declaration was not found (process onEvent event number {1}, parameter number {2}, matching part or element: {3}).
- Explanation: The XML Schema Definition (XSD) element declaration that is referred to in the matching part or element must be defined either inline in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: Check that the XSD element declaration is correctly referred to and that it is defined correctly.
- CWWBW3089E: The {0} element cannot be assigned to the {1} variable because the data type does not match (process onEvent event number {2}, parameter number {3}).
- Explanation: The specified element and the variable are of incompatible types. Only compatible types can be assigned, for example, from xsd:string to xsd:string.
- User Action: Make the types compatible. In WebSphere Integration Developer, select the onEvent event in the event handler of the process. In the Properties view, on the Details tab, specify a compatible variable.
- CWWBW3090E: The {0} part cannot be assigned to the {1} variable because the data type does not match (process onEvent event number {2}, parameter number {3}).
- Explanation: The specified message part and the variable are of incompatible types. Only compatible types can be assigned, for example, from xsd:int to xsd:int.
- User Action: Make the types compatible. In WebSphere Integration Developer, select the onEvent event in the event handler of the process. In the Properties view, on the Details tab, specify a compatible variable.
- CWWBW3091E: The {0} data type is not mapped to a parameter (process onEvent event number {1}).
- Explanation: An XML Schema Definition (XSD) element in the wrapper does not map to a parameter.
- User Action: Remove the element or map it to a parameter. To map the element, in WebSphere Integration Developer, select the onEvent event in the event handler of the process. In the Properties view, on the Details tab, map it to a matching parameter. Alternatively, open the interface, right-click the element and select delete to remove the element.
- CWWBW3092E: The {0} message part is not mapped to a parameter (process onEvent event number {1}).
- Explanation: No additional information is available.
- User Action: Remove the message part or map it to a parameter. To map the message part, in WebSphere Integration Developer, select the onEvent event in the event handler of the process. In the Properties view, on the Details tab, map it to a matching parameter. Alternatively, open the interface, right-click the part and select delete to remove the part.
- CWWBW3093E: The process partner name {0} is already used.
- Explanation: The name of a partner must be unique in its scope.
- User Action: In WebSphere Integration Developer, select the partner in the interface or reference partner category on the right side of the process editor. In the Properties view, on the Description tab, change the name to a unique name.
- CWWBW3094E: The process correlation set name {0} is already used.
- Explanation: The name of a correlation set must be unique in its scope.
- User Action: In WebSphere Integration Developer, select the correlation set in the correlation set category on the right side of the process editor. In the Properties view, on the Description tab, change the name to a unique name.
- CWWBW3095E: The correlation set ''{0}'' is used already. It can only be used once (process onEvent event number {1}).
- Explanation: The correlation set can be used only once per event.
- User Action: Ensure the correlation set is used only once in the specified event.
- CWWBW3096E: The process custom property name {0} is used already.
- Explanation: The custom property names for the process element must be unique.
- User Action: Change the name of the process custom property. In WebSphere Integration Developer, select the start node of the process. In the Properties view, on the Environment tab, provide a unique name for each custom property.
- CWWBW3097E: Process onEvent event number {0} implements the {1} operation of the {2} interface, which is already implemented in another process onEvent event.
- Explanation: The same interface and operation can be implemented only once in the same event handler. If a message is received for a specific interface and operation, the executing engine must know which onEvent event in that instance of the process must run.
- User Action: Remove the onEvent event or change the operation. In WebSphere Integration Developer, select the onEvent in the event handler of the process. To remove the onEvent, click Delete. To change the operation, go the Properties view. On the Details tab, change the operation.
- CWWBW3098E: Process onEvent event number {0} is missing a correlation set.
- Explanation: If an onEvent event is used in a process model, it must use at least one correlation set. The correlation set ensures that the input messages can correlate with the process instance.
- User Action: In WebSphere Integration Developer, select the onEvent in the event handler of the process. In the Properties view, on the Correlation tab, specify a correlation set.
- CWWBW3099E: The {0} referenced query property was not found ({1} process variable, queryProperty number {2}).
- Explanation: The referenced query property must be defined.
- User Action: Define the referenced property, or remove the query property from the variable. In WebSphere Integration Developer, select the variable in the variable category on the right side of the process editor. In the Properties view, on the Query Properties tab, define or remove the query property.
- CWWBW3100E: The variable ''{0}'' is not defined (activity ''{1}'').
- Explanation: The variable used in the activity is not defined.
- User Action: Check that the variable name is defined correctly.
- CWWBW3101E: Catch number {1} does not specify a fault name, a fault variable with a type specification, or both (fault handler of the {0} activity).
- Explanation: For a catch, the fault name, the fault variable with a type specification, or both must be set.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, define a fault name, a fault variable with a type specification, or both. Alternatively, remove the catch element by right-clicking it and selecting Delete.
- CWWBW3102E: Catch number {1} has the fault variable set, but it does not have a type specification set (fault handler of the {0} activity, {2} fault variable).
- Explanation: If the fault variable is set on a catch, the type specification must be set too.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, specify either a data type or a interface variable for the catch.
- CWWBW3103E: Catch number {1} has both the fault message type and the fault type set (fault handler of the {0} activity, {2} fault message type, {3} fault type).
- Explanation: Either the fault message type or the fault type can be set on a catch, but not both.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select either a data type or a interface variable for the catch.
- CWWBW3104E: Catch number {1} has the fault message type set, but it does not have a fault variable set (fault handler of the {0} activity, {2} fault message type).
- Explanation: If the fault message type is set on a catch, the fault variable must be set too.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, define the fault variable.
- CWWBW3105E: Catch number {1} has the fault type set, but it does not have a fault variable set (fault handler of the {0} activity, {2} fault type).
- Explanation: If the fault type is set on a catch, a fault variable must be set too.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, specify a fault variable for the catch.
- CWWBW3106E: The {0} message was not found (fault handler of the {1} activity, catch number {2}, {3} fault variable).
- Explanation: The message type that is referred to in the catch is not defined in the Web Services Description Language (WSDL) interface.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing interface and operation.
- CWWBW3107E: The {0} type was not found (fault handler of the {1} activity, catch number {2}, {3} fault variable).
- Explanation: The type that is referred to in the catch is not defined in the Web Services Description Language (WSDL) interface.
- User Action: Check that the type is defined correctly in the WSDL interface.
- CWWBW3108E: The fault handler does not contain a catch or catch-all element (fault handler of the {0} activity).
- Explanation: A fault handler must have at least one catch or one catch-all element.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Business Process editor, add a catch or catch-all element by selecting "Add a Catch Element" or "Add a Catch All Element" in the action bar. Alternatively, remove the fault hanlder element by right-clicking it and selecting Delete.
- CWWBW3109E: The correlations element is not allowed for snippet, human task, or custom activity ({0} activity).
- Explanation: The correlations element is allowed only for invoke activities, not for snippet, human task, or custom activities.
- User Action: Remove the correlations element from the activity.
- CWWBW3110E: Fault handlers are not allowed for snippet, human task, or custom activities ({0} activity).
- Explanation: Fault handlers are allowed only for invoke activities.
- User Action: Remove the fault handlers from the activity.
- CWWBW3111E: Expiration, script, and undo elements are used in the {0} activity.
- Explanation: Expiration, script, and undo elements are allowed only in invoke activities.
- User Action: Remove the elements from the activity.
- CWWBW3112E: The {0} custom activity is used in the {1} activity.
- Explanation: The custom activity element is allowed only in invoke activities.
- User Action: Remove the custom activity element from the activity.
- CWWBW3113E: The task element cannot be used in the activity ''{0}''.
- Explanation: This element is usually only allowed in invoke and receive activities. However, the task element is also allowed in receive choice activities in the receive element.
- User Action: Remove the task element from the activity.
- CWWBW3114E: An annotation is used in the {0} activity.
- Explanation: The annotation element is allowed only in scope activities.
- User Action: Remove the annotation element from the activity.
- CWWBW3115E: A timeout is used in the {0} activity.
- Explanation: The timeout element is allowed only in wait activities.
- User Action: Remove the timeout element from the activity.
- CWWBW3116E: The input element cannot be used in the activity ''{0}''. This element is only allowed in invoke and reply activities.
- Explanation: The input element is only allowed in invoke and reply activities.
- User Action: Remove the input element from the activity.
- CWWBW3117E: The output element cannot be used in the activity ''{0}''. This element is only allowed in invoke and receive activities.
- Explanation: The output element is also allowed in receive choice activities in the receive element.
- User Action: Remove the output element from the activity.
- CWWBW3118E: A continueOnError is used in the {0} activity.
- Explanation: The continueOnError attribute is allowed only in invoke activities.
- User Action: Remove the attribute from the activity.
- CWWBW3120E: The compensable attribute is used in the {0} activity.
- Explanation: The compensable attribute is allowed only in scope and collaboration-scope activities.
- User Action: Remove the compensable attribute from the activity.
- CWWBW3121E: The script, task, and custom activity elements are mutually exclusive (invoke activity ''{0}'').
- Explanation: Invoke activities can be extended to a script activity using a script element, a human task activity using a task element, or a custom activity using an element from a different namespace. Combinations of these extension elements are not allowed.
- User Action: Ensure that only one of the extension elements is used in the invoke activity.
- CWWBW3122E: The link ''{0}'' is not defined (referenced in the activity ''{1}'').
- Explanation: A link must be defined in a parallel activities activity before it can be referenced in a different activity. Additionally, this activity must be nested in the parallel activities activity because links are visible only inside the defining parallel activities activity.
- User Action: Ensure that the referenced link is defined in one of the parent parallel activities activities.
- CWWBW3123E: The {0} link is parallel to the {1} link (from the {2} activity to the {3} activity).
- Explanation: Parallel links connect the same activities, but they are not allowed.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Business Process editor, remove the link by right-clicking it and selecting Delete.
- CWWBW3124E: The data-typed {1} variable is used in the {0} activity.
- Explanation: For the specified activity, only interface variables are allowed.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, specify an interface variable or use data type variables mapping.
- CWWBW3125E: The compensation action on the {0} activity is not allowed.
- Explanation: Compensation actions are allowed only for invoke activities, not for snippet, human task, or custom activities.
- User Action: Remove the compensation action from the activity. In WebSphere Integration Developer, select the activity. In the Properties view, on the Compensation tab, click "Clear Compensation".
- CWWBW3126E: An expiration is not allowed for the {0} activity.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, select the activity. In the Properties view, on the Expiration tab, remove the expiration expression.
- CWWBW3127W: The timeout fault handler is not defined for the expiration that is set for the {0} activity.
- Explanation: When the activity expires, a timeout fault is thrown. To handle this fault, you must set an appropriate timeout fault handler.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Business Process editor, add a fault handler by selecting "Add a Fault Handler" from the action bar. Click the catch element, in the Properties view, on the Details tab, select "Built-in" as fault type. Choose timeout in the drop-down box as fault name.
- CWWBW3128E: The partner ''{0}'' was not found (activity ''{1}'').
- Explanation: The partner referenced in the activity is not defined.
- User Action: Ensure that the partner used is correct and that it is defined.
- CWWBW3129E: The {0} partner of the {1} activity is not an interface partner.
- Explanation: Partners that are used in receive or reply activities must be be interface partners.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing interface partner, interface and operation.
- CWWBW3130E: The {0} interface was not found ({1} activity).
- Explanation: The interface that is referred to in the activity is not defined in the Web Services Description Language (WSDL) file.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing interface partner, interface and operation.
- CWWBW3131E: The interfaces that are referred to in the {0} activity and in the {1} role are not the same ({2} partner, {3} partnerLinkType).
- Explanation: The portType attribute in activities is optional. However, if the attribute is set, it must be the same as the portType attribute that is set for the role that is used in this activity in the partner.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing interface partner, interface and operation.
- CWWBW3132E: The {0} operation of the {1} activity was not found.
- Explanation: The operation that is referred to in the activity is not defined in the interface.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing interface partner, interface and operation.
- CWWBW3133E: No input is defined in the {0} operation of the {1} activity.
- Explanation: Operations that are used in invoke, human task, receive, or receive choice activities must have an input.
- User Action: Define an input, or use another operation.
- CWWBW3134E: No output is defined in the {0} operation of the {1} activity.
- Explanation: Operations that are used in this kind of activity must have an output.
- User Action: Define an output, or use another operation.
- CWWBW3135E: No type is set in the input of the {0} operation of the {1} activity.
- Explanation: The type of the input must be set when the specified operation is used in this kind of activity.
- User Action: Set the type of the input, or use another operation.
- CWWBW3136E: No type is set in the output of the {0} operation of the {1} activity.
- Explanation: The type of the output must be set when the specified operation is used in this kind of activity.
- User Action: Set the type of the output, or use another operation.
- CWWBW3137E: No type is set in the fault of the {0} operation of the {1} activity.
- Explanation: The type of the fault must be set when the specified operation is used in this kind of activity.
- User Action: Set the type of the fault, or use another operation.
- CWWBW3138E: The {0} data type that is referred to in the {1} operation of the {2} activity was not found.
- Explanation: The data type that is referred to must be defined when the specified operation is used in this kind of activity.
- User Action: Set the data type, or use another operation.
- CWWBW3139E: The type of the {0} interface variable and the type of the input of the {1} operation must be the same ({2} activity).
- Explanation: The type of the variable and the input of the specified operation must be the same.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an input variable of the same type or create a new variable.
- CWWBW3140E: The type of the {0} variable and the type of the output of the {1} operation must be the same ({2} activity).
- Explanation: The type of the variable and the output of the specified operation must be the same.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an output variable of the same type or create a new variable.
- CWWBW3141E: The type of the {0} variable and the type of the {1} fault of the {2} operation must be the same ({3} activity).
- Explanation: The type of the variable and the fault of the operation must be the same.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an fault variable of the same type or create a new variable.
- CWWBW3142E: The variable is not set (activity ''{0}'').
- Explanation: A mandatory variable for the activity is not defined.
- User Action: Define the mandatory variable.
- CWWBW3143E: The input variable for the ''{0}'' activity is not specified.
- Explanation: For some activities, the input variable is mandatory.
- User Action: Define the input variable. In WebSphere Integration Developer, double-click the error message and select the specified activity. In the Properties view, on the Details tab, specify an input variable.
- CWWBW3144E: The output variable of the {0} activity is not set.
- Explanation: The output variable is mandatory for request-response invoke activities.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing output variable.
- CWWBW3145E: The output variable ''{0}'' must not be set, because the operation is one-way (activity ''{1}'', operation ''{2}'').
- Explanation: A one-way operation does not return a message.
- User Action: Do not define an output variable or use a request-response operation instead of a one-way operation.
- CWWBW3146E: The correlation set ''{0}'' was not found (activity ''{1}'').
- Explanation: The correlation set used in the activity is not defined.
- User Action: Define the correlation set, or remove it from the activity.
- CWWBW3147E: Timeout event number {1} does not specify a ''for'' expression, an ''until'' expression, or a ''repeat'' expression ({0} activity).
- Explanation: The "for" expression defines the duration expression after which the timeout event is signaled. The "until" expression specifies when the timeout event is fired. If the "repeat" expression is specified, the timeout event is fired once each time the duration period expires. One of these three expressions or a "repeat" expression with a "for" or "until" expression must occur in a timeout event.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, specify a for expression, on the Repeat tab, specify a repeat expression.
- CWWBW3148E: Timeout event number {1} must specify at least a ''for'' expression, an ''until'' expression, a timeout expression, or a "repeat" expression ({0} activity).
- Explanation: The "for" expression defines the duration expression after which the event is signaled. The "until" expression specifies when the timeout event is fired. The timeout expression specifies a timeout using a calendar that is supplied by the WebSphere Application Server scheduling service or user-written calendars that adhere to the scheduling service conventions. If the "repeat" expression is specified, the timeout event is fired once each time the duration period expires. One of these four expressions or a "repeat" expression with a "for", "until", or timeout expression must occur in a timeout event.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, specify a for expression, on the Repeat tab, specify a repeat expression.
- CWWBW3149E: The timeout event cannot specify a ''for'' expression and a timeout expression, or an ''until'' expression and a timeout expression ({0} activity, timeout event number {1}).
- Explanation: The "for" expression specifies the duration expression after which the event is signaled. The "until" expression specifies when the timeout event is fired. The timeout expression specifies a timeout using a calendar that is supplied by the WebSphere Application Server scheduling service or user-written calendars that adhere to the scheduling service conventions. If the "repeat" expression is specified, the timeout event is fired once each time the duration period expires. One of these four expressions or a repeatEvery expression with a "for", "until", or timeout expression must occur in a timeout event.
- User Action: Specify a "for", "until", timeout, or "repeat" expression.
- CWWBW3150E: The expression language ''{0}'' is not supported. It must be one of ''{1}'' (activity ''{2}'', timeout event {3}).
- Explanation: The specified expression language is unknown. Expressions specified in this expression language cannot run.
- User Action: Use one of the supported expression languages.
- CWWBW3151E: A matching correlation property entry was not found for the {0} correlation property and the {1} message type ({2} activity, {3} correlation set).
- Explanation: A property alias definition is needed to map the parts of a message type to the correlation properties.
- User Action: In WebSphere Integration Developer, select the specified correlation property. In the Properties view, on the Description tab, specify the correlation information for the operation that is associated with the specified action.
- CWWBW3152E: The {0} part that is referenced in the property alias definition for the {1} correlation property and {2} message type was not found ({3} activity, {4} correlation set).
- Explanation: The specified part must be defined for the message type.
- User Action: In WebSphere Integration Developer, select the specified correlation property. In the Properties view, on the Description tab, correct the correlation information for the operation that is associated with the specified action.
- CWWBW3153E: The {0} part that is referred to in the property alias definition for the {1} correlation property and {2} message type does not refer to a valid simple data type ({3} activity, {4} correlation set).
- Explanation: The specified part of the message type must be an XML schema simple type because a property can have only XML schema simple types.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing operation where the type of the part is a valid XML schema simple type.
- CWWBW3154E: The type of the {0} part of the {1} message type and the type of the {2} correlation property are not the same ({3} activity, {4} correlation set).
- Explanation: The specified part of the message type in the property alias must be the same type as the type of the property.
- User Action: Select a part that has the same XML schema simple type as the property type.
- CWWBW3155E: Multiple propertyAlias definitions were found for the property ''{0}'' and the messageType ''{1}'' (activity ''{2}'', correlation set ''{3}'').
- Explanation: Every property-messageType pair can have only one propertyAlias definition.
- User Action: Ensure only one propertyAlias is available for the property-messageType pair. If more than one part of a messageType is needed as a property, create properties and propertyAlias definitions for other parts of the same messageType.
- CWWBW3156E: Because the receive choice or receive activity ''{0}'' creates a process instance, it cannot be placed after the activity or the activities ''{1}''.
- Explanation: A receive choice or receive activity that is preceded by any basic activity cannot create a process instance.
- User Action: Remove the preceding basic activities or change the receive choice or receive activity so that it does not create a process instance.
- CWWBW3157E: The activity ''{0}'' is the target of the link or links ''{1}'', but it can create a process instance or it contains activities that can create a process instance.
- Explanation: A receive choice or receive activity that is the target of one or more links cannot create a process instance. In addition, a complex activity that contains a receive choice or receive activity that can create a process instance must not have any incoming links.
- User Action: Remove the incoming links or redefine the receive choice or receive activity so that it does not create a process instance.
- CWWBW3158W: The while loop activity ''{1}'' contains the receive choice or receive activity ''{0}'' that creates a process instance. If the condition of the while loop activity is false when the condition is evaluated for the first time, the process does not run correctly.
- Explanation: If the condition of the while loop activity is not true when it is evaluated the first time, the receive choice or receive activity cannot be navigated. The process does not run correctly in this case.
- User Action: Put the receive choice or receive activity outside of the while loop activity.
- CWWBW3159E: The receive choice or receive activity ''{0}'' that creates a process instance cannot be contained in a catch, catch all, receive, onEvent, timeout, compensation handler, case, or otherwise element.
- Explanation: Activities that create process instances are not reachable in catch, catch all, receive, onEvent, timeout, compensation handler, case, and otherwise elements.
- User Action: Move the receive choice or receive activity to a reachable position, or change the receive choice/receive activity so that it does not create a new process instance.
- CWWBW3160E: The parallel activities activity ''{0}'' contains one or more activities that can start processes, but it also contains the activity ''{1}'' which cannot start a process.
- Explanation: An activity that can start a process can be: 1.A receive choice or receive activity that can create a process instance; 2.A complex activity that contains a receive choice or receive activity that can create a process instance. If a parallel activities activity contains at least one these types of activity, all of the activities without incoming links must activities that can start processes.
- User Action: Use only activities that can start processes as the starting points in the parallel activities activity or remove these activities from the parallel activities activity.
- CWWBW3161E: The {0} activity refers to the {1} partner.
- Explanation: For a custom or snippet activity, the partner must be "null".
- User Action: Use the "null" partner for the custom or snippet activity.
- CWWBW3162E: The {0} activity refers to the {1} interface.
- Explanation: For a custom or snippet activity, the interface must be wpc:null.
- User Action: Use the interface wpc:null for the custom or snippet activity.
- CWWBW3163E: The {0} activity refers to the {1} operation.
- Explanation: For a custom or snippet activity, the operation must be "null".
- User Action: Use the "null" operation for the custom or snippet activity.
- CWWBW3164W: The {0} variable attribute is not needed for the {1} activity.
- Explanation: The specified variable attribute in the custom or snippet activity will be ignored.
- User Action: Remove the specified variable attribute from the custom or snippet activity.
- CWWBW3165W: The input is not needed for the {0} activity.
- Explanation: The input in the custom or snippet activity will be ignored.
- User Action: Remove the input from the custom or snippet activity.
- CWWBW3166W: The output is not needed for the {0} activity.
- Explanation: The output in the custom or snippet activity will be ignored.
- User Action: Remove the output from the custom or snippet activity.
- CWWBW3167E: The output is set for the {1} operation is one way ({0} activity).
- Explanation: A one-way operation does not return a message; therefore, the output should not be set.
- User Action: Do not define an output element, or use a request-response operation instead of a one-way operation.
- CWWBW3168E: The {1} input variable is set ({0} activity).
- Explanation: The data that is sent by this invoke or human task activity can be identified by the input variable attribute, which must be of the message type, or by one or more XML Schema Definition (XSD)-type variables that are specified in the input.
- User Action: Remove the input variable from the activity.
- CWWBW3169E: The {1} output variable is set ({0} activity).
- Explanation: The data that is received by this invoke or human task activity can be stored in the outputVariable attribute, which must be message-typed, or in one or more XML Schema Definition (XSD)-typed variables that are specified in the output.
- User Action: Remove the output variable from the activity.
- CWWBW3170E: The {0} variable is not defined (input or output of the {1} activity, parameter number {2}).
- Explanation: The specified variable, which is used in the parameter extension, is not defined.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing variable.
- CWWBW3171E: The interface variable is used (input or output element of the {0} activity, parameter number {1}, {2} variable).
- Explanation: You can use only element-type or data-type variables in input and output elements.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing variable element-type or data-type variables.
- CWWBW3172E: The {0} variable is used more than once in the data-type variable mapping of the {1} activity (parameter number {2}).
- Explanation: A variable can be used only once in an input or output element.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select another existing variable.
- CWWBW3173E: The {0} human task, which is referred to in the {1} activity, cannot be found.
- Explanation: The human task that is referred to in the specified activity cannot be found.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, create a new human task. Alternatively, remove the human task activity by right-clicking it and selecting Delete.
- CWWBW3174E: The interface that is referred to in the {0} activity and in the {1} human task are not the same.
- Explanation: The interface must be the same.
- User Action: Ensure that the interfaces are the same.
- CWWBW3175E: The operation that is referenced in the activity ''{0}'' and in the human task ''{1}'' must be the same.
- Explanation: The operations must be the same.
- User Action: Ensure that the operations are the same.
- CWWBW3176E: The human task ''{0}'' is not an administration task (activity ''{1}'').
- Explanation: The human task that is referenced in the receive activity must be an administration task.
- User Action: Reference an administration task.
- CWWBW3177E: The part is not set in the correlation property entry for the {0} correlation property and the {1} message type ({2} activity, {3} correlation set).
- Explanation: The part must be set in the property alias.
- User Action: Set the part.
- CWWBW3178E: The query language ''{0}'' used in the propertyAlias is not supported. It must be one of ''{1}'' (activity ''{2}'', correlation set ''{3}'', propertyAlias for the property ''{4}'' and the messageType ''{5}'').
- Explanation: The specified query language is unknown. Queries specified in this query language cannot be run.
- User Action: Use one of the supported query languages.
- CWWBW3179E: The expiration does not specify a ''for'' expression, an ''until'' expression, or a timeout expression ({0} activity).
- Explanation: The "for" expression defines the duration expression after which the expiration is signaled. The "until" expression specifies when the expiration is fired. The timeout element specifies a timeout using a calendar that is supplied by the WebSphere Application Server scheduling service, or user-written calendars that adhere to those scheduling service conventions. One of these three expressions must occur in an expiration.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Expiration tab, specify an expression.
- CWWBW3180E: The {0} expression language of the expiration is not supported. The language must be one of {1} ({2} activity).
- Explanation: The specified expression language is unknown. Expressions that are specified in this expression language cannot run.
- User Action: Use a supported expression language.
- CWWBW3181E: The expression language ''{0}'' of the transition condition is not supported. It must be one of ''{1}'' (activity ''{2}'', source element number {3}, link ''{4}'').
- Explanation: The specified expression language is unknown. Expressions specified in this expression language cannot run.
- User Action: Use one of the supported expression languages.
- CWWBW3182E: The expression language ''{0}'' of the join condition is not supported. It must be one of ''{1}'' (activity ''{2}'').
- Explanation: The specified expression language is unknown. Expressions specified in this expression language cannot run.
- User Action: Use one of the supported expression languages.
- CWWBW3183E: The transition condition expression is not valid ({0} activity, source element number {1}, {2} link, {3} expression language).
- Explanation: The specified expression is not valid for the specified expression language, or it is not valid in this context. For example, if you use the built-in expression language in the transition condition, only the values wpc:true, wpc:false, and wpc:otherwise are allowed.
- User Action: Check the expression and the expression language.
- CWWBW3184E: The join condition expression is not valid ({0} activity, {1} expression language).
- Explanation: The specified expression is not valid for the specified expression language, or it is not valid in this context. For example, if you use the built-in expression language in the join condition, only the values wpc:true, wpc:false, wpc:all, and wpc:any are allowed.
- User Action: Check the expression and the expression language.
- CWWBW3185E: The data-type variable mapping is used for the {0} message ({1} activity ).
- Explanation: The input or output message of the operation of the activity cannot be used with the data-type variable mapping. For example, if the message contains an array, it cannot be mapped to data-typed variables in the process.
- User Action: Modify the message that is used with the data-type variable mapping, or use an interface variable.
- CWWBW3186E: The {0} data-type variable mapping parameter does not map to an element in the wrapper or to a part in the message. ({1} activity, parameter number {2}).
- Explanation: No additional information is available.
- User Action: Remove the data-type variable mapping parameter, or map it to a valid element or part.
- CWWBW3187E: The {0} data type was not found ({1} activity, parameter number {2}, matching part or element: {3}).
- Explanation: The XML Schema Definition (XSD) data type definition that is referred to in the matching part or element must be a valid built-in XML schema simple type, or it must be defined inline in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: Check that the XSD data type definition is correctly referred to and that it is defined correctly.
- CWWBW3188E: The {0} data-type element declaration was not found ({1} activity, parameter number {2}, matching part or element: {3}).
- Explanation: The XML Schema Definition (XSD) element declaration that is referred to in the matching part or element must be defined inline in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: Check that the XSD element declaration is correctly referenced and that it is defined correctly.
- CWWBW3189E: The variable ''{0}'' cannot be assigned to element or part ''{1}'' because the data type does not match (activity ''{2}'', parameter number {3}).
- Explanation: The selected element and the variable are of incompatible types. Only compatible types can be assigned, for example from xsd:string to xsd:string.
- User Action: Ensure the types are compatible.
- CWWBW3190E: The element or part ''{0}'' cannot be assigned to variable ''{1}'' because the data type does not match (activity ''{2}'', parameter number {3}).
- Explanation: The selected element and the variable are of incompatible types. Only compatible types can be assigned, for example from xsd:string to xsd:string.
- User Action: Ensure the types are compatible.
- CWWBW3191E: The {0} element-based data type is not mapped to a data-type variable mapping parameter ({1} activity).
- Explanation: Elements in the wrapper must map to a parameter.
- User Action: Remove the element, or map it to a parameter.
- CWWBW3192E: The message-part ''{0}'' is not mapped to a parameter (activity ''{1}'').
- Explanation: A message-part have been found in the wrapper that does not map to a parameter.
- User Action: Remove the message-part or map it to a parameter.
- CWWBW3193E: The correlation set ''{0}'' is used already. It can only be used once (activity ''{1}'').
- Explanation: The correlation set can be used only once per activity.
- User Action: Ensure the correlation set is used only once in the specified activity.
- CWWBW3194E: The custom property name ''{0}'' is used already. The name can only be used once (activity ''{1}'').
- Explanation: The custom property names per activity must be unique.
- User Action: Ensure the names of all custom properties of the activity are unique.
- CWWBW3195E: The {1} forEach activity contains the {0} receive choice or receive activity.
- Explanation: If the finalCounterValue is less than the startCounterValue at run time, no branch in the forEach activity will run, and the receive choice or receive activity, which can create a process instance, cannot be navigated. The process will not run correctly in this case.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Business Process editor, place the receive choice or receive activity outside of the forEach activity. Alternatively, in the Properties view, on the Details tab, uncheck the create instance setting.
- CWWBW3196E: The compensation handler is not allowed (activity ''{0}'').
- Explanation: Compensation handlers are only allowed for invoke activities, but not for script, human task, or custom activities.
- User Action: Remove the compensation handler from the activity.
- CWWBW3197E: The XPath transition condition is not valid: {0} (activity ''{1}'', source element number {2}, link ''{3}'').
- Explanation: The specified XPath transition condition is not syntactically valid.
- User Action: Ensure that the XPath transition condition is valid.
- CWWBW3198E: The XPath join condition is not valid: {0} (activity ''{1}'').
- Explanation: The specified XPath join condition is not syntactically valid.
- User Action: Ensure that the XPath join condition is valid.
- CWWBW3199E: The XML Path Language (XPath) query that is used in a correlation property entry of the {3} correlation property in the {2} correlation set is not syntactically valid ({1} activity, {4} message type). The error is {0}.
- Explanation: No additional information is available.
- User Action: Ensure that the XPath query in the correlation set propertyAlias property is valid.
- CWWBW3200E: The XPath for- or until-expiration-expression is invalid: {0} (activity ''{1}'').
- Explanation: The specified XPath for- or until-expiration-expression is not syntactically valid.
- User Action: Ensure that the XPath for- or until-expiration-expression is valid.
- CWWBW3201W: The XML Path Language (XPath) query that is used in a correlation property entry of the {2} correlation property in the {1} correlation set is empty ({0} activity, {3} message type).
- Explanation: The specified XPath query in the correlation set propertyAlias property is not syntactically valid.
- User Action: Ensure that the XPath query in the correlation set property propertyAlias is valid. Either add a query or remove the query element.
- CWWBW3202W: Assigning the xsd:anyType typed element or part ''{0}'' to the xsd:anySimpleType typed variable ''{1}'' might result in a runtime error (activity ''{2}'', parameter number {3}).
- Explanation: Assigning the selected element of type xsd:anyType and the variable of type xsd:anySimpleType might result in a runtime error.
- User Action: Ensure the types are compatible.
- CWWBW3203W: Assigning the xsd:anyType typed variable ''{0}'' to the xsd:anySimpleType typed element or part ''{1}'' might result in a runtime error (activity ''{2}'', parameter number {3}).
- Explanation: Assigning the selected variable of type xsd:anyType to the element or part of type xsd:anySimpleType might result in a runtime error.
- User Action: Ensure the types are compatible.
- CWWBW3204W: The XPath in the for-expiration expression or until-expiration expression for the ''{1}'' activity is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath for-expiration expression or until-expiration expression so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified activity. In the Properties view, select the Expiration tab and correct the XPath expression.
- CWWBW3207W: The XPath in the for- or until-expiration-expression for the ''{1}'' activity is not valid because the $ notation used to refer to a variable in the ''{0}'' XPath expression or query is not supported.
- Explanation: The $ notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath for-expiration expression or until-expiration-expression so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified activity. In the Properties view, select the Expiration tab and correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData() XPath function.
- CWWBW3208W: The XPath join condition in the ''{1}'' activity is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Ensure that the XPath join condition is valid. In WebSphere Integration Developer, in the business process editor, select the specified activity. In the Properties view, select the Join Behavior tab and correct the XPath expression.
- CWWBW3211W: The XPath join condition for the ''{1}'' activity is not valid because the $ notation that is used to refer to a variable in the ''{0}'' XPath expression or query is not supported.
- Explanation: The $ notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath join condition so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified activity. In the Properties view, select the Join Behavior tab and correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBW3212W: The XPath transition condition for the ''{3}'' link, starting from source element number {2} in the ''{1}'' activity, is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath transition condition so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified link. In the Properties view, select the Details tab and correct the XPath expression.
- CWWBW3215W: The XPath transition condition for the ''{3}'' link, starting from source element number {2} in the ''{1}'' activity, is not valid because the $ notation that is used to refer to a variable in the ''{0}'' XPath expression or query is not supported.
- Explanation: The $ notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath transition condition so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified link. In the Properties view, select the Details tab and correct the XPath expression without using $ notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBW3216W: The XPath correlation set property propertyAlias query is not valid: ''{0}'' (activity ''{1}'', correlation set ''{2}'', propertyAlias for the property ''{3}'' and the messageType ''{4}'').
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath query in the propertyAlias element so that it is valid. In WebSphere Integration Developer, in the business process editor, in the tray on the right side of the process, select the specified correlation property. In the Properties view, correct the XPath expression by selecting the appropriate row in the table and clicking Edit.
- CWWBW3219W: The XPath correlation set property propertyAlias query is not valid: The $ notation to reference a variable in the XPath expression or query ''{0}'' is not supported. (activity ''{1}'', correlation set ''{2}'', propertyAlias for the property ''{3}'' and the messageType ''{4}'').
- Explanation: The $ notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath query propertyAlias element so that it is valid. In WebSphere Integration Developer, in the business process editor, in the tray on the right side of the process, select the specified correlation property. In the Properties view, correct the XPath expression by selecting the appropriate row in the table and clicking Edit. Correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBW3220E: An administrative human task is used in the {0} activity.
- Explanation: Administrative human tasks are allowed only in invoke and scope activities.
- User Action: Remove the administrative human task from the activity.
- CWWBW3221W: Deprecation: The {0} expression or query language is deprecated. Use {1} instead (resource {2}).
- Explanation: The specified expression or query language is deprecated.
- User Action: Use the new expression or query language.
- CWWBW3222W: The {0} value of the direction in the {1} correlation element is deprecated ({3} invoke activity). Use one of the following direction values: {2}
- Explanation: No additional information is available.
- User Action: Use the new values of the pattern attribute.
- CWWBW3223E: The direction in the {0} correlation element of the {1} invoke activity is used for a one-way operation.
- Explanation: The direction of the invoke activity is allowed only for request-response operations; it is not allowed when a one-way operation is invoked.
- User Action: Remove the pattern attribute.
- CWWBW3224E: The {0} variable is not defined ({1} activity, fromPart or toPart number {2}).
- Explanation: The variable that is used in the fromPart or toPart element is not defined.
- User Action: Correct the variable name if it is not defined correctly.
- CWWBW3225E: The interface variable is used in the {0} activity (fromPart or toPart number {1}, {2} variable).
- Explanation: You can use only element-type or data-type variables in fromPart and toPart elements.
- User Action: Use an XML Schema Definition (XSD)-type variable.
- CWWBW3226E: The {0} variable cannot be used multiple times in the same fromParts or toParts element ({1} activity, fromPart or toPart number {2}).
- Explanation: A variable can be used only once in a fromParts or toParts element.
- User Action: Use another XSD-typed variable.
- CWWBW3227E: The {0} message part is not mapped to a fromPart or toPart element ({1} activity).
- Explanation: A message part was found that does not map to a fromPart or toPart element.
- User Action: Remove the message part or map it to an existing fromPart or toPart.
- CWWBW3228E: The {0} fromPart or toPart must be removed or mapped to an existing message part ({1} activity, fromPart or toPart number {2}).
- Explanation: A fromPart or toPart was found that does not map to a message part.
- User Action: Remove the fromPart or toPart or map it to a valid message part.
- CWWBW3229E: The fromParts or toParts element cannot be used for the {0} message ({1} activity).
- Explanation: The input or output message of the specified operation of the activity does not contain any message parts. Therefore, it cannot be used with the fromParts or toParts element.
- User Action: Either modify the message or use a message-type variable.
- CWWBW3230W: Assigning the {0} xsd:anyType typed message part to the {1} xsd:anySimpleType typed variable might result in a runtime error ({2} activity, fromPart/toPart number {3}).
- Explanation: If the xsd:anyType and the xsd:anySimpleType do not match, a runtime error might occur.
- User Action: Edit the types so that they are compatible at run time.
- CWWBW3231E: The {0} message part cannot be assigned to the {1} variable because the data type does not match ({2} activity, fromPart or toPart number {3}).
- Explanation: The type of the selected part and the variable are incompatible. Only compatible types can be assigned, for example, from xsd:string to xsd:string.
- User Action: Ensure that the types are compatible.
- CWWBW3232E: The {0} activity uses both the data-type variable mapping and the fromParts or toParts element.
- Explanation: Using the Business Process Execution Language (BPEL) fromParts or toParts element and the parameter extension on the same activity is not supported.
- User Action: Remove either the fromParts or toParts element or the data-type variable mapping.
- CWWBW3233E: The input variable is set although a toParts element is available ({0} activity, {1} input variable).
- Explanation: The data that is sent by this invoke or human task activity can be identified by the input variable attribute or the toParts elements. You can use either the inputVariable attribute or the toParts element, but not both.
- User Action: Remove the input variable from the activity.
- CWWBW3234E: The output variable is set although a fromParts element is available ({0} activity, {1} output variable).
- Explanation: The data that is received by this invoke or human task activity can be stored in the outputVariable attribute or the fromParts elements. You can use either the outputVariable attribute or the fromParts element, but not both.
- User Action: Remove the output variable from the activity.
- CWWBW3235E: The {1} variable is set although a fromParts element is available (process onEvent event number {0}).
- Explanation: The data that is received by this onEvent event can be stored in the onEvent variable or the fromParts elements. You can use either the onEvent variable attribute or the fromParts element, but not both.
- User Action: Remove the variable attribute from the onEvent event.
- CWWBW3236E: The fromParts element must not be set because this is a one-way operation ({0} activity, {1} operation).
- Explanation: A one-way operation does not return a message.
- User Action: Do not define a fromParts element, or use a request-response operation instead of a one-way operation.
- CWWBW3237E: The transition condition is on the {0} source activity with the fork gateway type (source element number {1}, {2} link).
- Explanation: A source link of the fork type must not have a transition condition.
- User Action: Remove the transition condition, or change the type of the gateway.
- CWWBW3238E: Transactional behavior is used in the {0} activity.
- Explanation: The transactionalBehavior attribute is allowed only in invoke, receive, and receive choice activities.
- User Action: Remove the transactional behavior setting from the activity.
- CWWBW3239E: The exit condition expression is not valid ({0} activity, {1} expression language).
- Explanation: The specified expression is not valid for the given expression language, or it is not valid in this context. For example, if you use the built-in expression language in the exit condition, only the values wpc:true, wpc:false, and wpc:otherwise are allowed.
- User Action: Check the expression and the expression language.
- CWWBW3240E: The {0} expression language of the exit condition is not supported ({2} activity). It must be one of {1}.
- Explanation: The specified expression language is unknown. Expressions that are specified in this expression language cannot run.
- User Action: Use one of the supported expression languages.
- CWWBW3241W: The XML Path Language (XPath) exit condition for the {1} activity, is not valid. The error is {0}
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath exit condition so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified activity. In the Properties view, click the Details tab and correct the XPath expression.
- CWWBW3242E: The XML Path Language (XPath) exit condition is not syntactically valid ({1} activity). The error is {0}
- Explanation: No additional information is available.
- User Action: Ensure that the XPath transition condition is valid.
- CWWBW3243E: The value of the executeAt attribute on an exit condition is BOTH or ENTRY on initiating the {0} receive activity.
- Explanation: Exit conditions that run at the entry are not allowed for initiating receive activities.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Exit Condition tab, select another evaluate condition.
- CWWBW3244E: The value of the executeAt attribute is not set for an exit condition ({0} activity).
- Explanation: Exit conditions require that the executeAt attribute be set.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Exit Condition tab, select an evaluate condition.
- CWWBW3245E: The otherwise transition condition expression is not valid in this context ({0} activity, source element number {1}, {2} link).
- Explanation: In sequential regions, the otherwise transition condition is allowed only for the last link.
- User Action: Either change the transition condition or move the link to the last position.
- CWWBW3246W: The {0} variable in the XML Path Language (XPath) expression contains the period (.) character ({1} activity).
- Explanation: The use of $ notation for variables that contain a period in the name is not supported and the behavior is undefined.
- User Action: Remove the period character from the variable name.
- CWWBW3300E: The from side of copy number {1} in the {0} assign activity is not allowed.
- Explanation: Only specific types of from specifications are allowed.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select a valid from specification. Alternatively, remove the Assign element by right-clicking it and selecting Delete.
- CWWBW3301E: The to side of copy number {1} in the {0} assign activity is not allowed.
- Explanation: Only specific types of to specifications are allowed.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select a valid to specification. Alternatively, remove the Assign element by right-clicking it and selecting Delete.
- CWWBW3302E: The combination of from side and to side of copy number {1} in the {0} assign activity is not allowed.
- Explanation: Only specific types of copy specifications are allowed.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, choose another from or to element.
- CWWBW3303E: The {0} variable that is used in the from side of copy number {2} in the {1} assign activity is not defined.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing Assign From variable.
- CWWBW3304E: The from-part ''{0}'' was not found (assign activity ''{1}'', copy element number {2}, variable ''{3}'').
- Explanation: The part must be defined in the messageType.
- User Action: Define the part, or use an existing part.
- CWWBW3305E: The {0} partner that is used in the from side of copy number {2} in the {1} assign activity is not defined.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing partner.
- CWWBW3306E: The {0} variable that is used in the to side of copy number {2} in the {1} assign activity is not defined.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing Assign To variable.
- CWWBW3307E: The to-part ''{0}'' was not found (assign activity ''{1}'', copy element number {2}, variable ''{3}'').
- Explanation: The part must be defined in the messageType.
- User Action: Define the part, or use an existing part.
- CWWBW3308E: The {0} partner that is used in the to side of copy number {2} in the {1} assign activity is not defined.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing partner.
- CWWBW3309E: The {0} partner that is used in the to side of copy statement {2} in the {1} assign activity is not a reference partner.
- Explanation: Partners in to specifications of assign activities must define the partnerRole role.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing partner.
- CWWBW3310E: The types of the {0} from variable and the {1} to variable are not the same ({2} assign activity, copy element number {3}, {4} from message type, {5} to message type).
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, ensure that both variables have the same message type.
- CWWBW3311E: The types of the {0} from variable and the {1} to variable are not the same ({2} assign activity, copy element number {3}, {4} from XSD type, {5} to XSD type).
- Explanation: The XML Schema Definition (XSD) type of the two variables must be the same.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, ensure that both variables have the same XSD type.
- CWWBW3312E: The data type of the {0} from variable and the {1} to variable are not the same ({2} assign activity, copy element number {3}, {4} from XSD type, {5} to XSD type).
- Explanation: The XML Schema Definition (XSD) element of the two variables must be the same.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, ensure that both variables have the same XSD element type.
- CWWBW3313E: The type of the from-part ''{0}'' and the to-part ''{1}'' must be the same (assign activity ''{2}'', copy element number {3}).
- Explanation: The type of the two parts must be the same.
- User Action: Ensure that the parts have the same type.
- CWWBW3314E: The {0} partner that is used in the from side of the {2} copy statement in the {1} assign activity is not an interface partner.
- Explanation: Partners that are used in from specifications of assign activities must define the role that is defined by the endpointReference attribute.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an existing partner.
- CWWBW3315E: The {0} partner that is used in the from side of the {2} copy statement in the {1} assign activity is not a reference partner.
- Explanation: Partners that are used in from specifications of assign activities must define the role that is defined by the endpointReference attribute.
- User Action: Define the partnerRole role for the partner, use another partner, or define an endpointReference attribute.
- CWWBW3316E: The interface of the {0} from role and the {1} to role are not the same ({2} assign activity, copy element number {3}, {4} from partner, {5} to partner).
- Explanation: The interface of the two roles must be the same.
- User Action: Change the interface of one of the roles, or use another partner.
- CWWBW3317E: The {0} interface variable that is used in the from side is assigned to the {1} data-type or element-type variable that is used in the to side ({2} assign activity, copy element number {3}, {4} from message type, {5} to type or element).
- Explanation: Interface variables can be assigned only to other interface variables of the same message type.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, ensure that both variables have the same message type.
- CWWBW3318E: The {0} data-type from variable is assigned to the {1} interface-type to variable ({2} assign activity, copy element number {3}, {4} from type, {5} to message type).
- Explanation: Data-type variables can be assigned only to data-type or element-type variables of the same type.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, ensure that both variables have the same type.
- CWWBW3319E: The element-type {0} ''from'' variable is assigned to the interface-type {1} ''to'' variable ({2} assign activity, copy element number {3}, {4} ''from'' element, {5} ''to'' message type).
- Explanation: Element-type variables can be assigned only to element-type or type-type variables of the same type.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, ensure that both variables have the same type.
- CWWBW3320E: The {0}:{1} literal type that is used in the from side of copy statement number {3} in the {2} assign activity is not allowed.
- Explanation: This type of literal is not supported.
- User Action: Use another literal type.
- CWWBW3321E: A literal value that is used in the from side of copy statement number {1} in the {0} assign activity is not defined.
- Explanation: A definition of a literal value is required in the from specification.
- User Action: Define a literal value of the selected type.
- CWWBW3322E: The literal type in the ''from'' element and the part type in the ''to'' element are not the same (assign activity ''{0}'', copy element number {1}).
- Explanation: The literal type and the part type must be the same.
- User Action: Select another literal type or another part.
- CWWBW3323E: A literal value that is used in the from side of copy statement number {2} in the {1} assign activity is not of the {0} type.
- Explanation: The literal value must be of the type that is specified in the "from" specification.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select another literal type, or ensure that the literal value is of the expected type.
- CWWBW3324E: The {0} business object definition was not found ({1} assign activity, copy element number {2}, {3} base type, type that refers to the type that was not found: {4}).
- Explanation: The XML Schema Definition (XSD) type definition that is referred to must be a valid built-in XML schema simple type, or it must be defined inline in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: Check that the XSD type definition is referenced correctly and that it is defined correctly.
- CWWBW3325E: The {0} business object definition is not valid ({1} assign activity, copy element number {2}).
- Explanation: The XML Schema Definition (XSD) type definition that is referred to in the assign activity cannot be used. The problem might be that loops were found in the type hierarchy.
- User Action: Correct the XSD type definition.
- CWWBW3326E: The query language ''{0}'' used in the propertyAlias is not supported. It must be one of ''{1}'' (assign activity ''{2}'', copy element number {3}, propertyAlias for the property ''{4}'' and the messageType ''{5}'').
- Explanation: The specified query language is unknown. Queries specified in this query language cannot be run.
- User Action: Use one of the supported query languages.
- CWWBW3327E: The part ''{0}'' referenced in the propertyAlias definition for the property ''{1}'' and messageType ''{2}'' must reference a valid XML schema simple type (assign activity ''{3}'', copy element number {4}).
- Explanation: The selected part of the messageType must be an XML schema simple type because a property can have only XML schema simple types.
- User Action: Select a part with an XML schema simple type.
- CWWBW3328E: The type of the part ''{0}'' of the messageType ''{1}'' and the type of the property ''{2}'' must be the same XML schema type (assign activity ''{3}'', copy element number {4}).
- Explanation: The selected part of the messageType in the propertyAlias is not of the same type as the type of the property.
- User Action: Select a part that has the same XML schema simple type as the property type.
- CWWBW3329E: The query language ''{0}'' is not supported. It must be one of ''{1}'' (assign activity ''{2}'', copy element number {3}, from-specification).
- Explanation: The specified query language is unknown. Queries specified in this query language cannot be run.
- User Action: Use one of the supported query languages.
- CWWBW3330E: The query language ''{0}'' is not supported. It must be one of ''{1}'' (assign activity ''{2}'', copy element number {3}, to-specification).
- Explanation: The specified query language is unknown. Queries specified in this query language cannot be run.
- User Action: Use one of the supported query languages.
- CWWBW3331E: The expression language ''{0}'' of the expression element is not supported. It must be one of ''{1}'' (assign activity ''{2}'', copy element number {3}).
- Explanation: The specified expression language is unknown. Expressions specified in this expression language cannot be run.
- User Action: Use one of the supported expression languages.
- CWWBW3332E: The {0} data-type variable cannot be used with a property specification. Use an interface variable ({1} assign activity, copy element number {2}).
- Explanation: Properties can be specified only for message-type variables.
- User Action: Use a message-type variable, or remove the property specification.
- CWWBW3333E: The property ''{0}'' was not found (assign activity ''{1}'', copy element number {2}).
- Explanation: The property used must be defined.
- User Action: Ensure the referenced property is defined or refer to another defined property.
- CWWBW3334E: A matching propertyAlias definition is needed for the property ''{0}'' and the messageType ''{1}'' (assign activity ''{2}'', copy element number {3}).
- Explanation: A propertyAlias definition is needed to map the parts of a messageType to the property.
- User Action: Define the propertyAlias.
- CWWBW3335E: The part must be set in the propertyAlias for the property ''{0}'' and the messageType ''{1}'' (assign activity ''{2}'', copy element number {3}).
- Explanation: The part must be set in the propertyAlias.
- User Action: Set the part.
- CWWBW3336E: The part ''{0}'' referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' was not found (assign activity ''{3}'', copy element number {4}).
- Explanation: The part must be defined for the messageType.
- User Action: Define the part, or use an existing part in the propertyAlias.
- CWWBW3337E: Multiple propertyAlias definitions were found for the property ''{0}'' and the messageType ''{1}'' (assign activity ''{2}'', copy element number {3}).
- Explanation: A property-messageType pair can have only one propertyAlias definition.
- User Action: Ensure that only one propertyAlias is available for the property-messageType pair. If you need more than one part of a messageType as a property, create properties and propertyAlias definitions for additional parts of the same messageType.
- CWWBW3338E: The {0} business object definition was not found ({1} assign activity , copy element number {2}, {3} variable, {4} part).
- Explanation: The XML Schema Definition (XSD) type definition that is referred to might not be a valid built-in XML schema simple type or it must be defined inline in a XML Schema Definition (XSD) interface or in an XML schema.
- User Action: Check that the XSD type definition is referenced correctly and that it is defined correctly.
- CWWBW3339E: The XSD element declaration ''{0}'' was not found (assign activity ''{1}'', copy element number {2}, variable ''{3}'', part ''{4}'').
- Explanation: The XSD element declaration that is referenced must be defined inline in a WSDL interface or in an XML schema.
- User Action: Check that the XSD element declaration is referenced correctly and that it is defined correctly.
- CWWBW3340E: The {0} data-type part cannot be assigned to the {1} interface-type to variable ({2} assign activity, copy element number {3}).
- Explanation: An XML Schema Definition (XSD)-type part can be assigned only to an XSD-type variable.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select a message-type variable on the from side, but not a part of this variable, or select an XSD-type variable on the to side.
- CWWBW3341E: The {0} interface-type from variable cannot be assigned to the {1} data-type part ({2} assign activity, copy element number {3}).
- Explanation: An interface variable can be assigned only to another interface variable.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, select an interface variable and a data-type part on the from side, or select an interface variable on the to side.
- CWWBW3342E: The {0} business object definition was not found ({1} assign activity, copy element number {2}, {3} variable, element that refers to the type that was not found: {4}).
- Explanation: The XML Schema Definition (XSD) type definition that is referred to is not a valid built-in XML schema simple type or it must be defined inline in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: Check that the XSD type definition is referenced correctly and that it is defined correctly.
- CWWBW3343E: The data type of the {0} from variable and the {1} to variable are not the same ({2} assign activity, copy element number {3}, {4} from XSD type, {5} to XSD element).
- Explanation: The type of the two variables must be the same.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, ensure that both variables have the same type.
- CWWBW3344E: The data type of the {0} from variable and the {1} to variable are not the same ({2} assign activity, copy element number {3}, {4} from XSD element, {5} to XSD type).
- Explanation: The type of the two variables must be the same.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, ensure that both variables have the same type.
- CWWBW3345E: The data type of the {0} from part and the {1} to variable are not the same ({2} assign activity, copy element number {3}, {4} from XSD type, {5} to XSD type).
- Explanation: The XML Schema Definition (XSD) type of the part and the variable must be the same.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, ensure that the part and the variable have the same type.
- CWWBW3346E: The type of the {0} from variable and the {1} to part are not the same ({2} assign activity, copy element number {3}, {4} from XSD type, {5} to XSD type).
- Explanation: The XML Schema Definition (XSD) type of the variable and the part must be the same.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, ensure that the variable and the part have the same type.
- CWWBW3347E: The type of the {0} from part and the {1} to part are not the same ({2} assign activity, copy element number {3}, {4} from XSD type, {5} to XSD type).
- Explanation: The XML Schema Definition (XSD) type of the two parts must be the same.
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, ensure that the two parts have the same type.
- CWWBW3348E: The query that is used in the from side of the {2} copy statement in the {1} assign activity is not syntactically valid. The error is {0}
- Explanation: No additional information is available.
- User Action: Ensure that the XPath "from" query is valid.
- CWWBW3349E: The query that is used in the to side of the {2} copy statement in the {1} assign activity is not syntactically valid. The error is {0}
- Explanation: No additional information is available.
- User Action: Ensure that the XPath "to" query is valid.
- CWWBW3350E: The from property propertyAlias query is not valid: {0} (assign activity ''{1}'', copy element number {2}, propertyAlias for the property ''{3}'' and the messageType ''{4}'').
- Explanation: The specified XPath query in the from property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the from property propertyAlias is valid.
- CWWBW3351E: The to property propertyAlias query is not valid: {0} (assign activity ''{1}'', copy element number {2}, propertyAlias for the property ''{3}'' and the messageType ''{4}'').
- Explanation: The specified XPath query in the to property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the to property propertyAlias is valid.
- CWWBW3352E: The expression that is used in the from side in the {2} copy statement in the {1} assign activity is not syntactically valid. The error is {0}
- Explanation: No additional information is available.
- User Action: Edit the XPath from expression so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified activity. In the Properties view, select the Details tab. In the table, select the from expression in the specified copy element and, from the menu, select XPath Expression. Correct the XPath expression.
- CWWBW3353W: The from property propertyAlias query must not be empty (assign activity ''{0}'', copy element number {1}, propertyAlias for the property ''{2}'' and the messageType ''{3}'').
- Explanation: The specified XPath query in the from property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the from property propertyAlias is valid. Either add a query construct or remove the query element.
- CWWBW3354W: The to property propertyAlias query must not be empty (assign activity ''{0}'', copy element number {1}, propertyAlias for the property ''{2}'' and the messageType ''{3}'').
- Explanation: The specified XPath query in the to property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the to property propertyAlias is valid. Either add a query construct or remove the query element.
- CWWBW3355W: Assigning the xsd:anyType typed from-variable ''{0}'' to the xsd:anySimpleType typed to-variable ''{1}'' might result in a runtime error (assign activity ''{2}'', copy element number {3}, from XSD type ''{4}'', to XSD type ''{5}'').
- Explanation: Assigning an xsd:anyType typed variable to an xsd:anySimpleType typed variable might result in a runtime error.
- User Action: Ensure that both variables have a compatible XSD type.
- CWWBW3356W: In the {1} assign activity, the from expression in the {2} copy element is not valid. The error is {0}
- Explanation: The specified XML Path Language (XPath) expression is not supported.
- User Action: Edit the XPath from expression so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified activity. In the Properties view, select the Details tab. In the table, select the from expression in the specified copy element and, from the menu, select XPath Expression. Correct the XPath expression.
- CWWBW3359W: In the ''{1}'' assign activity, the from-expression in copy element number {2} is not valid. The $ notation that is used to refer to a variable in the {0} XPath expression or query is not supported.
- Explanation: The $ notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath from-expression so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified activity. In the Properties view, select the Details tab. In the table, select the from-expiration expression in the specified copy element and, from the drop-down menu, select XPath Expression. Correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData()XPath function.
- CWWBW3360W: In the ''{1}'' assign activity, copy element number {2}, the XPath query used in the assign from property ''{3}'' is not valid: ''{0}'' (messageType {4}).
- Explanation: The specified XPath expression is not supported.
- User Action: Ensure that the XPath query in the from property propertyAlias is valid. In WebSphere Integration Developer, in the business process editor, select the specified assign activity. In the Properties view, select the Details tab. In the table, right-click the from-expression in the specified copy element and select Edit Query. Correct the XPath expression.
- CWWBW3363W: In the ''{1}'' assign activity, copy element number {2}, the XPath query used in the propertyAlias for the correlation property ''{3}'' is not valid because the $ notation that is used to refer to a variable in the ''{0}'' XPath expression or query is not supported ( messageType ''{4}'').
- Explanation: The $ notation to reference a variable is not supported in this XPath expression.
- User Action: Ensure that the XPath query in the from property propertyAlias is valid. In WebSphere Integration Developer, in the business process editor, select the specified assign activity. In the Properties view, select the Details tab. In the table, right-click the specified copy element and select Edit Query. Correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData()XPath function.
- CWWBW3364W: In the ''{1}'' assign activity, copy element number {2}, the from query is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Ensure that the XPath from-query is valid. In WebSphere Integration Developer, in the business process editor, select the specified activity. In the Properties view, select the Details tab. In the table, right-click the from-expression in the specified copy element and select Edit Query. Correct the XPath expression.
- CWWBW3367W: In the {1} assign activity, copy element number {2}, the from query is not valid because the $ notation that is used to refer to a variable in the {0} XML Path Language (XPath) expression or query is not supported.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, in the business process editor, select the specified assign activity. In the Properties view, select the Details tab. In the table, right-click the from expression in the specified copy element and select Edit Query. Correct the XPath query without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData()XPath function.
- CWWBW3368W: In the {1} assign activity, copy element number {2}, the XML Path Language (XPath) query that is used in the {3} assign-to property of a variable is not valid ({4} message type). The error is {0}
- Explanation: The specified XPath expression is not supported.
- User Action: In WebSphere Integration Developer, in the business process editor, select the specified assign activity. In the Properties view, select the Details tab. In the table, right-click the to expression in the specified copy element and select Edit Query. Correct the XPath expression.
- CWWBW3371W: In the {1} assign activity, copy element number {2}, the XML Path Language (XPath) query that is used in the {3} assign-to property of a variable is not valid because the $ notation that is used to refer to a variable in the {0} XPath expression or query is not supported ({4} message type).
- Explanation: No additional information is available.
- User Action: Edit the XPath query in the propertyAlias assign-to property so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified assign activity. In the Properties view, select the Details tab. In the table, right-click the to expression in the specified copy element and select Edit Query. Correct the XPath query without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData()XPath function. propertyAlias is valid.
- CWWBW3372W: In the ''{1}'' assign activity, copy element number {2}, the to-query is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath to query so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified assign activity. In the Properties view and select the Details tab. In the table, right-click the to-expression in the specified copy element and select Edit Query. Correct the XPath expression.
- CWWBW3375W: In the {1} assign activity, copy element number {2}, the to query is not valid because the $ notation that is used to refer to a variable in the {0} XML Path Language (XPath) expression or query is not supported.
- Explanation: No additional information is available.
- User Action: Edit that the XPath to query so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified assign activity. In the Properties view, select the Details tab. In the table, right-click the to expression in the specified copy element and select Edit Query. Correct the XPath query without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData()XPath function.
- CWWBW3376W: Deprecation: In the {0} assign activity, copy element number {1}, the ''from'' element uses the deprecated schema for literal values.
- Explanation: The "Assign from a literal" value requires a wrapper element called 'literal'.
- User Action: Add a "literal" element to the "from" element.
- CWWBW3378E: In the {0} assign activity, copy element number {1}, the ''from'' element uses both schemas for literal values.
- Explanation: The "Assign from a literal" value requires only a wrapper element called "literal".
- User Action: In WebSphere Integration Developer, double-click the error message. In the Properties view, on the Details tab, add a correct literal element.
- CWWBW3400E: The {0} compensate activity can be used only inside a fault handler or a compensation handler.
- Explanation: The specified compensate activity can be used only inside a fault handler or a compensation handler. Compensate activities invoke the compensation handlers of scope activities that complete when a fault occurs. So compensate activities can be used only inside fault handlers or compensation handlers.
- User Action: Remove the compensate activity, or move it to a fault handler or a compensation handler.
- CWWBW3401E: The {0} scope or invoke activity that is referred to in the {1} compensate activity was not found or cannot be referred to.
- Explanation: The scope or invoke activity reference from the compensate activity must be defined in the process and it must be contained in this scope. This scope defines a fault handler or compensation handler in which the compensate activity is contained. Additionally, the scope or invoke activity that is referred to must be immediately contained in this scope. For example, when Scope1 contains Scope2, which contains Scope3, Scope3 cannot be referred to from a compensate activity in the fault handler of Scope1. Scope3 can be referred to only if Scope2 is not compensable. However, other structured activities can come between these scope activities. For example, the compensate activity can refer to Scope2 if Scope1 contains Flow1, which then contains Scope2.
- User Action: Ensure that the scope or invoke activity is immediately contained in this scope and is defined in the process.
- CWWBW3402E: The {0} compensate activity cannot be contained in the {1} invoke activity.
- Explanation: Although the invoke activity is a basic activity, it cannot contain other scope or invoke activities that can be compensated. Therefore, do not place a compensate activity in the fault handler or compensation handler of the invoke activity.
- User Action: Remove the compensate activity from the invoke activity.
- CWWBW3403E: The {0} scope activity that is referred to from the {1} compensate activity cannot be compensated.
- Explanation: The specified scope activity cannot be compensated because it has the compensable attribute set to "no".
- User Action: Set the compensable attribute on the referenced scope activity to "yes", or refer to another scope activity.
- CWWBW3404E: The {0} invoke activity that is referred to from the {1} compensate activity does not have a fault or compensation handler set.
- Explanation: The specified invoke activity has no fault or compensation handler set; therefore, an enclosing scope activity for the invoke activity is not generated and the invoke activity cannot be compensated.
- User Action: Set a fault or compensation handler for the specified invoke activity, or refer to another scope or invoke activity.
- CWWBW3405E: The {0} invoke activity that is referred to from the {1} compensate activity does not have a fault or compensation handler or an undo action set.
- Explanation: The specified invoke activity has no fault or compensation handler or undo action set; therefore, an enclosing scope activity for the invoke activity is not generated and the invoke activity cannot be compensated.
- User Action: Set a fault or compensation handler or an undo action for the specified invoke activity, or refer to another scope or invoke activity.
- CWWBW3406E: The {0} activity name that is referred to in the {1} compensate activity is not unique.
- Explanation: The compensate activity refers to activities by name, so it must be clear which activity is referred to. The activity name must be unique.
- User Action: Ensure that the activity name is used only once.
- CWWBW3407E: The {0} compensate activity cannot be contained in the fault handler of the {1} non-compensable scope activity.
- Explanation: The compensable attribute is set to "no" in the specified scope activity, making it unavailable for compensation. However, the specified compensate activity is in the fault handler of that scope activity. Therefore, a compensate activity must not be in the fault handler of the scope activity.
- User Action: Remove the compensate activity from the non-compensable scope activity.
- CWWBW3408W: Deprecation: Using the scope attribute on the {0} compensate activity is deprecated. Use the compensateScope activity instead.
- Explanation: The compensateScope activity replaces the scope attribute of the compensate activity.
- User Action: Replace the compensate activity with the compensateScope activity.
- CWWBW3409E: The compensateScope activity can be used only inside a fault handler or a compensation handler ({0} compensate activity).
- Explanation: compensateScope activities are used to invoke the compensation handlers of scope activities that completed normally when a fault occurs. Therefore, compensateScope activities can be used only inside fault handlers or compensation handlers.
- User Action: Remove the compensateScope activity, or move it to a fault handler or a compensation handler.
- CWWBW3410E: The {0} scope or invoke activity, which is referred to from the {1} compensateScope activity, was not found or cannot be referred to.
- Explanation: The scope or invoke activity that is referred to from the specified compensateScope activity must be defined in the process, and it must be contained in this scope because this scope defines a fault handler or compensation handler in which the compensateScope activity is contained. For example, if this scope is Scope1 and it contains Scope2, which contains Scope3, Scope3 cannot be referred to unless Scope2 is not compensable. However, Scope2 can be referred to from the compensateScope activity if Scope1 contains Flow1, which then contains Scope2.
- User Action: Ensure that the scope or invoke activity is immediately contained in this scope and is defined in the process.
- CWWBW3411E: The {0} compensateScope activity cannot be contained in the {1} invoke activity.
- Explanation: A compensateScope activity cannot be in the fault handler or compensation handler of the invoke activity.
- User Action: Remove the compensateScope activity from the invoke activity.
- CWWBW3412E: The {0} scope activity, which is referred to from the {1} compensateScope activity, cannot be compensated.
- Explanation: The compensable attribute of the specified scope activity is set to "no". Therefore, the scope activity cannot be compensated.
- User Action: Set the compensate attribute of the referenced scope activity to "yes", or refer to another scope activity.
- CWWBW3413E: No fault or compensation handler is set on the {0} invoke activity, which is referred to from the {1} compensateScope activity.
- Explanation: Without a fault or compensation handler set on the invoke activity that is referred to from the compensateScope activity, an enclosing scope activity for the invoke activity is not generated. Therefore, the invoke activity cannot be compensated.
- User Action: Set a fault or compensation handler for the specified invoke activity, or refer to another scope or invoke activity.
- CWWBW3414E: No fault or compensation handler or compensation action is set on the {0} invoke activity, which is referred to from the {1} compensateScope activity.
- Explanation: Without a fault or compensation handler or compensation action set on the specified invoke activity, an enclosing scope activity for the invoke activity is not generated. Therefore, the invoke activity cannot be compensated.
- User Action: Set a fault or compensation handler or an undo action for the referenced invoke activity, or refer to another scope or invoke activity.
- CWWBW3415E: The {0} activity name, which is referred to in the {1} compensateScope activity, is not unique.
- Explanation: The compensateScope activity refers to activities that must be compensated by name; therefore, it must be clear which activity is referred to. The activity name must be unique.
- User Action: Ensure that the activity name is used only once.
- CWWBW3416E: The compensateScope activity cannot be contained in the fault handler of a non-compensable scope activity ({0} compensateScope activity, {1} scope activity).
- Explanation: The specified scope activity set the compensable attribute to 'no'. The specified compensate activity is contained in the fault handler of that scope activity. Because the scope activity is not compensable, it is invisible for compensation. Therefore, a compensate activity must not be contained in the fault handler of the scope activity.
- User Action: Remove the compensateScope activity from the non-compensable scope activity.
- CWWBW3600E: The {0} link crosses the boundary of the {1} while loop activity (the link is defined in the {2} parallel activities activity).
- Explanation: The source activity is nested in a while loop activity, and the target activity is not, or vice versa.
- User Action: Remove the link, or define another source or target activity for the link.
- CWWBW3601E: The {0} link cannot be used in the {1} while loop activity because it is defined outside of the while loop activity (the link is defined in the {2} parallel activities activity).
- Explanation: No additional information is available.
- User Action: Remove the link, or define another source or target activity for the link.
- CWWBW3602E: The {0} link crosses the boundary of the compensation handler of the {1} scope activity (the link is defined in the {2} parallel activities activity).
- Explanation: The source activity is nested in a compensation handler, and the target activity is not, or vice versa.
- User Action: Remove the link, or define another source or target activity for the link.
- CWWBW3603E: The {0} link is used in the compensation handler of the {1} scope activity. The link is defined in the {2} parallel activities activity.
- Explanation: The specified link cannot be used because it is defined outside of the scope activity.
- User Action: Remove the link, or define another source or target activity for the link.
- CWWBW3604E: The {0} link crosses the boundary of the compensation handler of the {1} invoke activity (the link is defined in the {2} parallel activities activity).
- Explanation: The source activity is nested in a compensation handler, and the target activity is not, or vice versa.
- User Action: Remove the link, or define another source or target activity for the link.
- CWWBW3605E: The {0} link is used in the compensation handler of the {1} invoke activity. The link is defined in the {2} parallel activities activity.
- Explanation: A link is used in the compensation handler of an invoke activity , but it is defined outside of the invoke activity.
- User Action: Remove the link, or define another source or target activity for the link.
- CWWBW3606E: The {0} link crosses the boundary of the event handler of the {1} scope activity (the link is defined in the {2} parallel activities activity).
- Explanation: The source activity is nested in an event handler, and the target activity is not, or vice versa.
- User Action: Remove the link, or define another source or target activity for the link.
- CWWBW3607E: The {0} link is used in the event handler of the {1} scope activity. The link is defined in the {2} parallel activities activity.
- Explanation: A link is used in an event handler of a scope activity, but it is defined outside of the scope activity. These links are not allowed.
- User Action: Remove the link, or define another source or target activity for the link.
- CWWBW3608E: The {0} inbound link crosses the boundary of the fault handler of the {1} scope activity (the link is defined in the {2} parallel activities activity).
- Explanation: The source activity is nested in a fault handler, and the target activity is not, or vice versa.
- User Action: Remove the link, or define another source or target activity for the link.
- CWWBW3609E: The {0} link is used in the fault handler of the {1} scope activity although it is defined outside of the scope activity (the link is defined in the {2} parallel activities activity).
- Explanation: No additional information is available.
- User Action: Remove the link, or define another source or target activity for the link.
- CWWBW3610E: The target of the {0} link is nested in the {1} scope activity because the source of the link is nested in the fault handler of the scope activity (the link is defined in the {2} parallel activities activity).
- Explanation: An outbound link crosses the boundary of a fault handler but not the boundary of the scope activity of the fault handler.
- User Action: Remove the link, or define another source or target activity for the link.
- CWWBW3611E: The {0} inbound link crosses the boundary of the fault handler of the {1} invoke activity (the link is defined in the {2} parallel activities activity).
- Explanation: No additional information is available.
- User Action: Remove the link, or define another source or target activity for the link.
- CWWBW3612E: The {0} link is used in the fault handler of the {1} invoke activity although it is defined outside of the invoke activity (the link is defined in the {2} parallel activities activity).
- Explanation: No additional information is available.
- User Action: Remove the link, or define another source or target activity for the link.
- CWWBW3613E: The {0} link crosses the boundary of two isolated scope activities ({1} source scope activity, {2} target scope activity, link defined in the {3} parallel activities activity).
- Explanation: No additional information is available.
- User Action: Remove the link, or define another source or target activity for the link.
- CWWBW3614E: The activity ''{0}'' cannot be part of a cycle.
- Explanation: The cycle prevents the process from ending.
- User Action: Remove the cycle.
- CWWBW3615E: The link ''{0}'' cannot be part of a cycle.
- Explanation: The cycle prevents the process from ending.
- User Action: Remove the cycle.
- CWWBW3616E: The source activity is missing for the {0} link (the link is defined in the {1} parallel activities activity, {2} target activity).
- Explanation: The link cannot be navigated because the source activity is not defined.
- User Action: Use the link in the source element of an activity.
- CWWBW3617E: The target activity is missing for the {0} link (the link is defined in the {1} parallel activities activity, {2} source activity).
- Explanation: A link cannot be navigated because the target activity is not defined.
- User Action: Use the link in the target element of an activity.
- CWWBW3618E: The {0} link is not used (the link is defined in the {1} parallel activities activity).
- Explanation: All of the links that are defined in a parallel activities activity must be used to connect one source activity to one target activity.
- User Action: Remove the link, or use it to connect two activities.
- CWWBW3619E: The {0} link has more than one source activity (the link is defined in the {2} parallel activities activity). The multiple activities are {1}.
- Explanation: Only one activity can be defined as the source of a link.
- User Action: Remove all except one activity from the list as the source of the link.
- CWWBW3620E: The {0} link has more than one target activity (the link is defined in the {2} parallel activities activity). The multiple activities are {1}.
- Explanation: Only one activity can be defined as the target of a link.
- User Action: Remove all except one activity from the list as the target of a link.
- CWWBW3621E: The source type of the {0} activity must not be {2} (source of standard flow link {1}).
- Explanation: All links that are defined in a standard flow activity must not have the source type attribute set.
- User Action: Remove the type attribute.
- CWWBW3622E: The target type of {0} activity must not be {2} (target of standard flow link {1}).
- Explanation: All links that are defined in a standard flow activity must not have the target type attribute set.
- User Action: Remove the type attribute.
- CWWBW3623E: The {0} link crosses the boundary of the {1} forEach activity (the link is defined in the {2} parallel activities activity).
- Explanation: The source activity is nested in a forEach activity and the target activity is not, or vice versa.
- User Action: Remove the link, or define another source or target activity for the link.
- CWWBW3624E: The {0} link is used in the {1} forEach activity although it is defined outside of the forEach activity (the link is defined in the {2} parallel activities activity).
- Explanation: No additional information is available.
- User Action: Remove the link or define another source or target activity for the link.
- CWWBW3625W: The type attribute of the sources or targets element is deprecated ({0} activity, {1} link).
- Explanation: The wpc:type is not supported on the Business Process Execution Language (BPEL) flow.
- User Action: Remove the type attribute.
- CWWBW3650E: The extension activity ''{0}'' is not supported. Only generalized flow activities are supported.
- Explanation: Only the generalized flow activity is supported as an extension activity.
- User Action: Either remove the extension activity or change it to an generalized flow activity.
- CWWBW3651E: The source type of the {0} activity is not a split, fork, or inclusive or (source of the {1} generalized flow link).
- Explanation: Links that are defined in a generalized flow activity must have a source activity of type split, fork, or inclusive or (ior).
- User Action: Define another source activity for the link, or change the source type to split, fork, or ior.
- CWWBW3652E: The target type of the {0} activity is not a merge, join, or ''inclusive or'' (target of the {1} generalized flow link).
- Explanation: Links that are defined in a generalized flow activity must have a target activity of type merge, join, or "inclusive or" (ior).
- User Action: Define another target activity for the link, or change the target type to merge, join, or ior.
- CWWBW3653E: The source activity ''{0}'' of the generalized flow link ''{1}'' must be directly nested in the generalized flow activity ''{2}''.
- Explanation: All links defined in a generalized flow activity must connect activities which are directly nested in the generalized flow activity.
- User Action: Either remove the link or move the activity so that it is directly nested in the generalized flow activity.
- CWWBW3654E: The target activity ''{0}'' of the generalized flow link ''{1}'' must be directly nested in the generalized flow activity ''{2}''.
- Explanation: All links defined in a generalized flow activity must connect activities which are directly nested in the generalized flow activity.
- User Action: Either remove the link or move the activity so that it is directly nested in the generalized flow activity.
- CWWBW3655E: The generalized flow activity ''{0}'' must contain exactly one start activity. Found start activities: ''{1}''.
- Explanation: A start activity is an activity that is not the target of links. A generalized flow activity must contain exactly one start activity.
- User Action: In case there is no start activity defined, add one. If no separate start activity is needed, an empty action activity can be used as start activity. In case there are multiple start activities defined, remove them except one.
- CWWBW3656E: The generalized flow activity ''{0}'' must contain at least one end activity.
- Explanation: An end activity is an activity which is not the source of links. A generalized flow activity must contain at least one end activity.
- User Action: Define an end activity. If no separate end activity is needed, an empty action activity can be used as end activity.
- CWWBW3657E: The {0} activity is unreachable from the {1} start activity of the {2} generalized flow activity.
- Explanation: Each activity that is directly contained in the generalized flow activity must be reachable from the start activity of the generalized flow activity. Otherwise, the generalized flow activity will contain multiple parallel graphs. Parallelism is not supported in generalized flow activities.
- User Action: Explicitly or implicitly connect the specified activity with the start activity of the generalized flow activity.
- CWWBW3658E: An end activity is unreachable from the {0} activity of the {1} generalized flow activity. Connect the activity to an end activity.
- Explanation: Each activity that is directly contained in the generalized flow activity must be able to navigate to an end activity of the generalized flow activity. If an activity is navigated that is not explicitly or implicitly connected with an end activity, the generalized flow activity cannot complete without an error.
- User Action: Explicitly or implicitly connect the specified activity with an end activity of the generalized flow activity.
- CWWBW3659E: The activity ''{0}'' must not specify a join condition, because it is part of a graph.
- Explanation: In a generalized flow activity, no activities will run in parallel, even if an activity is the source of multiple links. Thus, if an activity is the target of multiple links and only one of the links is navigated, the activity runs. Because parallelism is not supported, the other links cannot be navigated. Consequently, all activities that are part of a graph must not specify a join condition.
- User Action: Remove the join condition.
- CWWBW3660W: The {0} generalized flow link cannot be navigated because the previously referred to generalized flow link ({1}) does not specify a transition condition ({2} activity).
- Explanation: If no explicit transition condition is set, the default value "true" is used. Because in a generalized flow activity, only the first link that evaluates to "true" is navigated, the links following it are never navigated.
- User Action: Either remove the link, or specify a transition condition for the previous link.
- CWWBW3661E: The {0} link crosses the boundary of the {1} generalized flow activity (the link is defined in the {2} parallel activities activity).
- Explanation: The source activity is nested in a generalized flow activity, and the target activity is not, or vice versa.
- User Action: Remove the link, or define another source or target activity for the link.
- CWWBW3662E: The {0} link is used in the {1} generalized flow activity although it is defined outside of the generalized flow activity (the link is defined in the {2} parallel activities activity).
- Explanation: No additional information is available.
- User Action: Remove the link or define another source or target activity for the link.
- CWWBW3663E: The {0} flow activity is the source of multiple links but has no source type specified.
- Explanation: A flow activity that is the source of multiple links must define a source type. Possible values are split, fork, and ior.
- User Action: Specify a source type.
- CWWBW3664E: The {0} flow activity is the target of multiple links but has no target type specified.
- Explanation: A flow activity which is the target of multiple links must define a target type. Possible values are merge, join, and ior.
- User Action: Specify a target type.
- CWWBW3665W: The region analysis of the {0} flow activity cannot be used.
- Explanation: No additional information is available.
- User Action: Check the technical information databases on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/. If you cannot find the information that you need to solve the problem, contact your technical support provider or again refer to the WebSphere Process Server support site for information about IBM Software Support and Services
- CWWBW3666E: The fault link does not contain a catch or catch-all element ({0} source activity, fault source number {1}).
- Explanation: No additional information is available.
- User Action: Define a catch or catch-all element, or remove the fault source.
- CWWBW3667E: The fault link contains more than one catch or catch-all element ({0} source activity, fault source number {1})
- Explanation: A fault source must have only one catch element or one catch-all element.
- User Action: Remove a catch or catch-all element, or remove the fault link.
- CWWBW3668E: The {0} activity contains more than one fault link with a catch-all element.
- Explanation: An activity can define only one fault source with a catch-all element.
- User Action: Remove the catch-all elements from all except one fault link in the specified activity.
- CWWBW3669E: A fault link starting from the {0} activity is missing a fault name, a fault variable, or both (fault link number {1}).
- Explanation: The faultName attribute, faultVariable attribute, or both must be set for a fault source.
- User Action: Set the faultName attribute, faultVariable attribute, or both.
- CWWBW3670E: The {0} fault variable on a fault link of the {1} activity was not found (fault link number {2}).
- Explanation: The fault variable must be declared on a parent scope.
- User Action: Ensure that the fault variable is set.
- CWWBW3671E: The {0} source activity of a fault link is a structured activity, a throw activity, or a rethrow activity.
- Explanation: A source activity can be only a basic activity or a scope activity.
- User Action: Correct the source activity.
- CWWBW3672E: One region of the {0} generalized flow cannot be mapped (the region is formed by the following activities: {1}).
- Explanation: The generalized flow cannot be processed in the runtime environment.
- User Action: Correct the region types of the generalized flow.
- CWWBW3673E: The {0} link or activity is participating on a parallel region that contains a cycle ({1} generalized flow).
- Explanation: Cycles in parallel regions are not supported.
- User Action: Remove the cycle, or change the type of the region.
- CWWBW3674W: One region of the {0} generalized flow might cause errors during run time (the region is formed by the following activities: {1}).
- Explanation: No additional information is available.
- User Action: Correct region types of the generalized flow.
- CWWBW3675W: Fault source number {2} is missing a fault variable that is required because the {0} defined fault has associated fault data ({1} source activity).
- Explanation: If a fault has associated fault data it will only be caught by a fault link if this fault link specifies a matching fault name and a fault variable whose data type matches the type of the data associated with the fault.
- User Action: Ensure that the correct fault variable is set.
- CWWBW3676W: The {0} fault does not exist in the {1} operation ({2} source activity, fault source number {3}).
- Explanation: The fault must be specified on the operation. Otherwise, the default catch-all handler is selected if it is present at run time.
- User Action: Ensure that the correct fault exist on the operation.
- CWWBW3677W: The {0} fault variable is not of the fault data message type ({1} fault ({2} source activity, fault source number {3}).
- Explanation: No additional information is available.
- User Action: Ensure that the variable has the message type of the fault.
- CWWBW3700E: The {0} reference partner, which the compensate action of the {1} invoke activity refers to, was not found.
- Explanation: The partner that is referred to in the compensate (undo) action of the invoke activity is not defined.
- User Action: Ensure that the partner is correct and that it is defined.
- CWWBW3701E: The {0} interface, which the compensate action of the {1} invoke activity refers to, was not found.
- Explanation: The interface (port type) that is referred to in the compensate (undo) action of the invoke activity is not defined (or is defined incorrectly) in the Web Services Description Language (WSDL) interface.
- User Action: Define or correct the port type in the WSDL.
- CWWBW3702E: The {0} operation, which the compensate action of the {1} invoke activity refers to, was not found.
- Explanation: The operation that is referred to in the compensate (undo) action of the invoke activity is not defined (or is defined incorrectly) in the Web Services Description Language (WSDL) interface.
- User Action: Define or correct the operation in the WSDL interface.
- CWWBW3703E: The input is not defined for the {0} operation, which is referred to by the compensate action of the {1} invoke activity.
- Explanation: Operations that are used in this kind of activity must have an input.
- User Action: Define an input or use another operation.
- CWWBW3704E: The message type is not set in the input of the {0} compensate action operation ({1} invoke activity).
- Explanation: The message type must be set when the operation is used in this kind of activity.
- User Action: Set the message type or use another operation.
- CWWBW3705E: The {0} message type that is referred to in the input of the {1} operation must be defined. The operation is used in the compensate action of the {2} invoke activity.
- Explanation: The message type must be defined when the operation is used in this kind of activity.
- User Action: Set the message type, or use another operation.
- CWWBW3706E: The type of the {0} variable and the input of the {1} operation, which is used in the compensate action of the {2} invoke activity, are not the same.
- Explanation: The message type of the variable and the input of the operation must be the same.
- User Action: Ensure that the variable and the input have the same message type.
- CWWBW3707E: The {0} variable, which is used in the compensate action of the {1} invoke activity, is not defined.
- Explanation: No additional information is available.
- User Action: Check that the variable name is defined correctly.
- CWWBW3708E: The {0} data type variable is used in the compensate action of the {0} invoke activity.
- Explanation: For this activity, only interface variables are allowed.
- User Action: Use an interface variable.
- CWWBW3710E: An expiration is set for the compensate action of the {0} invoke activity.
- Explanation: An expiration cannot be set for a compensate (undo) action.
- User Action: Remove the expiration element.
- CWWBW3711E: The {0} partner, which is used in the compensate action of the {1} invoke activity, is not a reference partner.
- Explanation: Partners that are used in invoke activities must define the partnerRole role.
- User Action: Define the partnerRole role for the partner, or use another partner.
- CWWBW3712E: The interface that is used in the compensate action of the {0} invoke activity and the interface in the {2} partner are not the same ({1} partner role, {3} partnerLinkType).
- Explanation: The portType attribute in the compensate (undo) action is optional. However, if the attribute is set, it must be the same as the portType attribute that is set in the partnerRole role in the partner.
- User Action: Ensure that the portType attributes are the same.
- CWWBW3713E: The {0} partner of the {1} invoke activity is not a reference partner.
- Explanation: Partners that are used in invoke activities must define the partnerRole role.
- User Action: Define the partnerRole role for the partner, or use another partner.
- CWWBW3714E: The {1} input variable on the compensate action of the {0} invoke activity is set although a compensate action input is already available.
- Explanation: The data that is sent by this undo action can be identified by the inputVariable attribute, which must be a message type, or by one or more XML Schema Definition (XSD) type variables that are specified in the input element.
- User Action: Remove the inputVariable attribute from the undo action.
- CWWBW3715E: The {0} variable that is used as input to the compensate action in the {1} invoke activity is not defined (parameter number {2}).
- Explanation: No additional information is available.
- User Action: Check that the variable name is defined correctly.
- CWWBW3716E: The {0} invoke activity uses the {2} interface variable as input to the compensate action (parameter number {1}).
- Explanation: You can use data-type variables (element-type or type-type) in input elements.
- User Action: Use a data-type variable.
- CWWBW3717E: The {0} variable, which used as an input to the compensate action in the {1} invoke activity, is used multiple times in the same input element (parameter number {2}).
- Explanation: A variable can be used only once in an input element.
- User Action: Use another data-type variable.
- CWWBW3718E: The {0} invoke activity contains both a compensation handler and a compensation action.
- Explanation: For compensation, either a compensation handler or a compensation (undo) action can be used, but not both.
- User Action: Remove either the compensation handler or the compensation action.
- CWWBW3719E: The compensation action does not specify a variable although the {0} invoke activity specifies a variable by using the data-type variable mapping option.
- Explanation: The variable in the compensation action is optional only when the invoke activity refers to an interface variable.
- User Action: Specify a variable for the compensation action.
- CWWBW3720E: The data-type variable mapping is used in the compensation action of the {1} invoke activity. The error is {0}
- Explanation: The input message of the operation in the compensation action cannot be used with the data-type variable mapping option. For example, the message contains an array, which cannot be mapped to data-type variables in the process.
- User Action: Modify the message that is used with the data-type variable mapping option, or use an interface variable.
- CWWBW3721E: The {0} input, output, or fault that is used in the data-type variables mapping of the compensate action in the {1} invoke activity does not match the input, output, or fault of the associated operation (parameter number {2}).
- Explanation: The parameter must map to an element in the wrapper or to a part in the message.
- User Action: Remove the parameter, or map it to a valid element or part.
- CWWBW3722E: The {0} data-type definition, which is used in the compensation action of the {1} invoke activity, was not found (parameter number {2}, matching part or element {3}).
- Explanation: The XML Schema Definition (XSD) type definition that is referred to in the matching part or element must be either a valid built-in XML schema simple type or it must be defined inline in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: Define the data type and refer to it correctly.
- CWWBW3723E: The {0} data element declaration, which is used in the compensation action of the {1} invoke activity, was not found (parameter number {2}, matching part or element: {3}).
- Explanation: The XML Schema Definition (XSD) element declaration that is referred to in the matching part or element must be defined inline in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: Define the data type, and refer to it correctly.
- CWWBW3724E: The {0} variable, which is used in the compensate action of the {2} invoke activity, is assigned to the {1} element or part although the data type does not match (parameter number {3}).
- Explanation: The specified element and the variable are of incompatible types. Only compatible types can be assigned, for example, from xsd:string to xsd:string.
- User Action: Ensure that the types are compatible.
- CWWBW3725E: The {0} input, output, or fault element that is used in the data-type variables mapping of the compensate action in the {1} invoke activity does not match the input, output, or fault of the associated operation.
- Explanation: An XML Schema Definition (XSD) element in the wrapper does not map to a parameter.
- User Action: Remove the element, or map it to a parameter.
- CWWBW3726E: The {0} input, output, or fault that is used in the data-type variables mapping of the compensate action in the {1} invoke activity does not match the input, output.
- Explanation: A message part has been found in the wrapper that does not map to a parameter.
- User Action: Remove the message part, or map it to a parameter.
- CWWBW3727W: In the compensate action of the {2} invoke activity, parameter number {3}, which assigns the {0} xsd:anyType type variable to the {1} xsd:anySimpleType type element or part might cause a runtime error because the xsd:anyType variable and the xsd:anySimpleType element or part do not match.
- Explanation: No additional information is available.
- User Action: Edit the xsd:anyType and the xsd:anySimpleType so that they match.
- CWWBW3800E: The {2} data-type variable is used in receive number {1} of the {0} receive choice activity.
- Explanation: Only interface variables are allowed in receive choice activities.
- User Action: Use an interface variable.
- CWWBW3801E: The {0} reference partner, which is referred to in receive number {2} of the {1} receive choice activity, was not found.
- Explanation: The partner that is referred to in the receive choice activity is not defined.
- User Action: If the partner is correct, define it. Otherwise, use another reference partner.
- CWWBW3802E: The {0} partner, which is referred to in receive number {2} of the {1} receive choice activity, is not an interface partner.
- Explanation: Partners that are used in receive elements of a receive choice activity must define the myRole role.
- User Action: Define the myRole role for the partner, or use another partner.
- CWWBW3803E: The {0} interface, which is referred to in receive number {2} of the {1} receive choice activity, was not found.
- Explanation: The interface that is referenced in the activity is not defined.
- User Action: Ensure that the interface is correct and that it is defined.
- CWWBW3804E: The interface that is referred to in receive number {2} of the {0} receive choice activity and the interface that is referred to in the {3} interface partner are not the same. ({4} partnerLinkType).
- Explanation: The portType attribute in the receive element is optional. However, if this attribute is set, it must be the same as the portType attribute that is set in the myRole role in the partner.
- User Action: Ensure the port types are the same.
- CWWBW3805E: The {0} operation, which is referred to in receive number {2} of the {1} receive choice activity, was not found.
- Explanation: The operation that is referenced in the activity is not defined in the Web Services Description Language (WSDL) interface.
- User Action: Ensure that the operation is correct and that it is defined in the interface.
- CWWBW3806E: The input is not defined in the {0} operation that is referred to in receive number {2} of the {1} receive choice activity.
- Explanation: Operations that are used in this kind of activity must have an input element.
- User Action: Define an input element, or use another operation.
- CWWBW3807E: The type is not set in the input of the {0} operation, which is referred to in receive number {2} of the {1} receive choice activity.
- Explanation: The input message type must be set when the operation is used in a receive branch of a receive choice activity.
- User Action: Set the input message type, or use another operation.
- CWWBW3808E: The {0} type, which is used in the {1} operation, was not found. The operation is referred to in receive number {3} of the {2} receive choice activity.
- Explanation: The message type that is referred to must be defined when the operation is used in a receive element of a receive choice activity.
- User Action: Set the message type, or use another operation.
- CWWBW3809E: The type of the {0} interface variable and the type of the input of the {1} operation are not the same ({2} receive choice activity, receive number {3}).
- Explanation: The message type of the variable and of the input element of the operation must be the same.
- User Action: Ensure that the message type of the variable and the input operation are the same.
- CWWBW3810E: The variable for receive number {1} in the {0} receive choice activity is not set.
- Explanation: A mandatory variable for the onMessage element on a receive choice activity is not defined.
- User Action: Define the mandatory variable. In WebSphere Integration Developer, in the business process editor, select the specified receive element. In the Properties view, select the Details tab and specify a variable.
- CWWBW3811E: The {0} variable, which is referred to in receive number {2} of the {1} receive choice activity, is not defined.
- Explanation: No additional information is available.
- User Action: Check that the variable name is defined correctly.
- CWWBW3812E: The {0} correlation set, which is referred to in receive number {2} of the {1} receive choice activity, was not found
- Explanation: The correlation set that is used in the receive choice activity is not defined.
- User Action: Define the correlation set, or remove it from the receive element of the receive choice activity.
- CWWBW3813E: A matching propertyAlias definition was not found for the property ''{0}'' and messageType ''{1}'' (receive choice activity ''{2}'', receive element number {3}, correlation set ''{4}'').
- Explanation: A propertyAlias definition is needed to map the parts of a messageType to the correlation properties.
- User Action: Define the propertyAlias.
- CWWBW3814E: The part ''{0}'' referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' was not found (receive choice activity ''{3}'', receive element number {4}, correlation set ''{5}'').
- Explanation: The part must be defined for the messageType.
- User Action: Define the part, or use an existing part in the propertyAlias.
- CWWBW3815E: The part ''{0}'' referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' does not reference a valid XML schema simple type (receive choice activity ''{3}'', receive element number {4}, correlation set ''{5}'').
- Explanation: The selected part of the messageType must be an XML schema simple type because a property can have only XML schema simple types.
- User Action: Select a part that has an XML schema simple type.
- CWWBW3816E: The type of the part ''{0}'' of the messageType ''{1}'' and the property ''{2}'' is not the same (receive choice activity ''{3}'', receive element number {4}, correlation set ''{5}'').
- Explanation: The selected part of the messageType in the propertyAlias does not have the same type as the property type.
- User Action: Select a part that has same XML schema simple type as the property type.
- CWWBW3817E: Multiple propertyAlias definitions were found for the property ''{0}'' and the messageType ''{1}'' (receive choice activity ''{2}'', receive element number {3}, correlation set ''{4}'').
- Explanation: Every property-messageType pair can have only one propertyAlias definition.
- User Action: Ensure only one propertyAlias is available for the property-messageType pair. If more than one part of a messageType is needed as a property, create properties and propertyAlias definitions for additional parts of the same messageType.
- CWWBW3818E: Receive element number {0} in the {1} receive choice activity does not use a correlation set.
- Explanation: If more than one receive choice or receive activity is used in a process model, all of the receive elements of a receive choice activity must use at least one correlation set. The correlation set ensures that the input messages correlate with the process instance.
- User Action: Set at least one correlation set for the receive element. In WebSphere Integration Developer, in the process editor, select the specified receive element. In the Properties view, on the Correlation tab, add a correlation set.
- CWWBW3819E: A wrong set of correlation sets is used in the receive element number {0} of the receive choice activity ''{1}''. The expected set of correlation sets, as used in the activity ''{2}'', is: ''{3}''.
- Explanation: All of the receive choice or receive activities that create process instances must use the same set of correlation sets.
- User Action: Ensure that all of the receive and receive choice activities that create process instances use the same set of correlation sets.
- CWWBW3821E: The receive choice activity ''{0}'' can create process instances but it has timeout events.
- Explanation: If the receive choice activity creates process instances, timeout events are not allowed.
- User Action: Remove the timeout events or redefine the receive choice activity so that it does not create process instances.
- CWWBW3822E: A reply activity was not found that matches receive number {0} of the {1} receive choice activity.
- Explanation: For each two-way operation receive in a receive choice activity, the process must contain at least one reply activity with the same interface and operation.
- User Action: Add a reply activity to the process with the same port type and operation as the receive element of the receive choice activity.
- CWWBW3823E: The {2} variable, which is referred to in receive number {1} of the {0} receive choice activity, is set although an output is available.
- Explanation: The data that is received by this receive element can be stored in the activity variable, which must be an interface variable, or in one or more data-type variables that are specified in the output element.
- User Action: Remove the variable attribute from the receive.
- CWWBW3824E: The {0} variable, which is referred to the output of receive number {2} of the {1} receive choice activity, is not defined (parameter number {3}).
- Explanation: No additional information is available.
- User Action: Check that the variable name is defined correctly.
- CWWBW3825E: The {3} interface variable is in the data-type variable mapping of receive number {1} in the {0} receive choice activity (parameter number {2}).
- Explanation: You can use only element-type or type-type variables in output elements.
- User Action: Use a data-type variable.
- CWWBW3826E: The variable ''{0}'' cannot be used multiple times in the same output element (receive choice activity ''{1}'', output element of receive element number {2}, parameter number {3}).
- Explanation: A variable can be used only once in an output element.
- User Action: Use another XSD-typed variable.
- CWWBW3827E: The {0} human task, which is referred to in receive number {2} of the {1} receive choice activity, was not found.
- Explanation: No additional information is available.
- User Action: Remove the human task reference, or ensure that the human task can be found.
- CWWBW3828E: The {0} human task, which is referred to in receive number {2} of the {1} receive choice activity, is not an invocation task.
- Explanation: The human task that is referenced in the receive must be an invocation task.
- User Action: Make sure the receive references an invocation task.
- CWWBW3829E: The interface that is referred to in receive number {0} of the {2} receive choice activity and in the {1} human task are not the same.
- Explanation: The interfaces must be the same.
- User Action: Ensure that the interfaces are the same.
- CWWBW3830E: The operation that is referred to in receive number {0} of the {2} receive choice activity and in the {1} human task are not the same.
- Explanation: The operations must be the same.
- User Action: Ensure that the operations are the same.
- CWWBW3831E: The part is not set in the propertyAlias for the property ''{0}'' and the messageType ''{1}'' (receive choice activity ''{2}'', receive element number {3}, correlation set ''{4}'').
- Explanation: The part must be set in the propertyAlias.
- User Action: Set the part.
- CWWBW3832E: The query language ''{0}'' used in the propertyAlias is not supported. It must be one of ''{1}'' (receive choice activity ''{2}'', receive element number {3}, correlation set ''{4}'', propertyAlias for the property ''{5}'' and the messageType ''{6}'').
- Explanation: The specified query language is unknown. Queries specified in this query language cannot be run.
- User Action: Use one of the supported query languages.
- CWWBW3833E: The {1} timeout event of the {0} receive choice activity does not specify at least a ''for'' or ''until'' expression.
- Explanation: The "for" expression defines the duration expression after which the event is signaled. The "until" expression specifies when the alarm event is fired. One of these expressions must occur in a timeout event.
- User Action: Specify a "for" or "until" expression.
- CWWBW3834E: The {1} timeout event of the {0} receive choice activity does not specify at least a ''for'', ''until'', or timeout expression.
- Explanation: The "for" expression defines the duration expression after which the event is signaled. The "until" expression specifies when the alarm event is fired. The timeout specifies a timeout using a calendar that is supplied by the WebSphere Application Server scheduling service, or user-written calendars that adhere to those scheduling service conventions. One of these expressions must occur in a timeout event.
- User Action: Specify a "for", "until", or timeout expression.
- CWWBW3835E: The {1} timeout event of the {0} receive choice activity specifies a ''for'' expression and a timeout expression, or an ''until'' expression and a timeout expression.
- Explanation: The "for" expression defines the duration expression after which the event is signaled. The "until" expression specifies when the alarm event is fired. The timeout specifies a timeout using a calendar that is supplied by the WebSphere Application Server scheduling service, or user-written calendars that adhere to those scheduling service conventions. One of these expressions must occur in a timeout event.
- User Action: Specify a "for", "until", or timeout expression.
- CWWBW3836E: The repeatEvery expression in the {1} timeout event of the {0} receive choice activity is not useful.
- Explanation: The repeatEvery expression is useful only in event handlers.
- User Action: Use the "for" expression instead.
- CWWBW3837E: Receive number {0} of the {3} receive choice activity implements the {1} operation of the {2} interface, which is already implemented in another receive.
- Explanation: The same interface and operation can be implemented only once in the same receive choice activity. If a message is received for a specific port type and operation, the processing engine must know which receive element in that instance of the process must run.
- User Action: Remove the receive, or change the operation.
- CWWBW3838E: The data-type variable mapping is used in receive number {2} of the {1} receive choice activity. The error is {0}
- Explanation: The input message of the operation of the receive cannot be used with the data-type variable mapping. For example, the message might contain an array, which cannot be mapped to data-type variables in the process.
- User Action: Modify the message to use with the data-type variable mapping, or use an interface variable.
- CWWBW3839E: The {0} input, output, or fault that is used in the data-type variable mapping of receive number {2} in the {1} receive choice activity does not map to an input, output, or fault of the associated operation (parameter number {3}).
- Explanation: One of the parameters must map to an element in the wrapper or to a part in the message.
- User Action: Remove the data-type variable mapping, or map the parameter to a valid element or part.
- CWWBW3840E: The {0} data-type definition, which is referred to in receive number {2} of the {1} receive choice activity, was not found (parameter number {3}, matching part or element {4}).
- Explanation: The XML Schema Definition (XSD) data-type definition that is referred to in the matching part or element must be either a valid built-in XML schema simple type or it must be defined inline in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: Check that the data-type definition is correctly referred to and that it is defined correctly.
- CWWBW3841E: The {0} data element declaration, which is referred to in receive number {2} of the {1} receive choice activity, was not found (parameter number {3}, matching part or element: {4}).
- Explanation: The XML Schema Definition (XSD) element declaration that is referred to in the matching part or element must be either defined inline in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: Check that the XSD element declaration is correctly referenced and that it is defined correctly.
- CWWBW3842E: The {0} input, output, or fault that is used in the data-type variable mapping of receive number {3} in the {2} receive choice activity is assigned to the {1} variable although the data type does not match (parameter number {4}).
- Explanation: The element and the variable are of incompatible types. Only compatible types can be assigned, for example, from xsd:string to xsd:string.
- User Action: Ensure that the types are compatible.
- CWWBW3843E: The {0} input, output, or fault that is used in the data-type variable mapping of receive number {2} in the {1} receive choice activity is not mapped to an input, output, or fault of the associated operation.
- Explanation: An XML Schema Definition (XSD) element in the wrapper must be mapped to a parameter.
- User Action: Remove the element, or map it to a parameter.
- CWWBW3844E: The {0} input, output, or fault that is used in the data-type variable mapping of receive number {2} in the {1} receive choice activity is not mapped to an input, output, or fault of the associated operation.
- Explanation: A message part in the wrapper must be mapped to a parameter.
- User Action: Remove the message part, or map it to a parameter.
- CWWBW3845E: The {0} correlation set, which is referred to in receive number {2} of the {1} receive choice activity, is already used.
- Explanation: The correlation set can be used only once per receive.
- User Action: Ensure that the correlation set is used only once in the specified receive.
- CWWBW3846W: The receive choice activity ''{0}'' is contained in the parallel forEach activity ''{1}''. This can result in the standard fault ''bpws:conflictingReceive''.
- Explanation: The receive choice activity is contained in a parallel forEach activity. If multiple branches are created in the parallel forEach activity, the contained receive choice activity may lead to the standard fault 'bpws:conflictingReceive' during run time.
- User Action: Review and test the process carefully to ensure the parallel execution of the branches in the forEach activity will not result in the standard fault 'bpws:conflictingReceive'.
- CWWBW3847E: The same operation of the same interface is implemented by both event number {0} in the process event handler and receive number {2} of the {1} receive choice activity. This results in the standard fault bpws:conflictingReceive.
- Explanation: If the receive choice activity is enabled simultaneously with the onEvent event, the standard fault bpws:conflictingReceive is thrown because it is not clear to which of the two constructs an inbound message for that operation and interface (port type) must be delivered. The process is in an undefined status.
- User Action: Remove the receive choice activity, the receive element of the receive choice activity, or the process onEvent event, or change the implemented operation or interface of the receive element or onEvent event.
- CWWBW3848E: The same operation of the same interface is implemented by both event number {0} in the event handler of the {1} scope activity and receive number {3} of the {2} receive choice activity. This results in the standard fault bpws:conflictingReceive.
- Explanation: If the receive choice activity is enabled simultaneously with the onEvent event, the standard fault bpws:conflictingReceive is thrown because it is not clear to which of the two constructs an inbound message for that operation and interface must be delivered. The process is in an undefined status.
- User Action: Remove the receive choice activity, the receive of the receive choice activity, or the onEvent event, or change the implemented operation or interface of the receive element or onEvent event.
- CWWBW3849W: The receive choice activity ''{0}'' is contained in process onEvent event number {1}, which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
- Explanation: The receive choice activity is contained in an onEvent event, which implements a one-way operation. If this onEvent event runs multiple times in parallel, the contained receive choice activity may lead to the standard fault 'bpws:conflictingReceive' during run time.
- User Action: Review and test the process carefully to ensure the parallel execution of the onEvent event will not result in the standard fault 'bpws:conflictingReceive'.
- CWWBW3850W: The receive choice activity ''{0}'' is contained in onEvent event number {1} of the scope activity ''{2}'', which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
- Explanation: The receive choice activity is contained in an onEvent event, which implements a one-way operation. If this onEvent event runs multiple times in parallel, the contained receive choice activity may lead to the standard fault 'bpws:conflictingReceive' during run time.
- User Action: Review and test the process carefully to ensure the parallel execution of the onEvent event will not result in the standard fault 'bpws:conflictingReceive'.
- CWWBW3851E: The XML Path language (XPath) for or until expression that is used in timeout event number {2} of the {1} receive choice activity is not syntactically valid. The error is {0}
- Explanation: No additional information is available.
- User Action: Fix the syntax of the XPath for or until expression.
- CWWBW3852E: The XPath correlation set property propertyAlias query is not valid: {0} (receive choice activity ''{1}'', receive element number {2} correlation set ''{3}'', propertyAlias for the property ''{4}'' and the messageType ''{5}'').
- Explanation: The specified XPath query in the correlation set property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the correlation set property propertyAlias is valid.
- CWWBW3853W: The XPath correlation set property propertyAlias query must not be empty (pick activity ''{0}'', onMessage element number {1}, correlation set ''{2}'', propertyAlias for the property ''{3}'' and the messageType ''{4}'').
- Explanation: The specified XPath query in the correlation set property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the correlation set property propertyAlias is valid. Either add a query construct or remove the query element.
- CWWBW3854W: In the ''{2}'' receive choice activity (onMessage element number {3}, parameter number {4}), assigning the {0} xsd:anyType typed element or part to the ''{1}'' xsd:anySimpleType typed variable might cause a runtime error.
- Explanation: The xsd:anyType and xsd:anySimpleType must match.
- User Action: Edit the types so that they match.
- CWWBW3855W: The XPath for-expression or until-expression in timeout event number {2} of the ''{1}'' receive choice activity is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath for-expression or until-expression is valid. In WebSphere Integration Developer, in the business process editor, select the specified timeout in the specified receive choice activity. In the Properties view, select the Details tab and correct the XPath expression.
- CWWBW3862W: The XPath for-expression or until-expression in timeout event number {2} of the ''{1}'' receive choice activity is not valid because the $ notation that is used to refer to a variable in the {0} XPath expression or query is not supported.
- Explanation: The $ notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath for-expression or until-expiration-expression so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified timeout in the specified receive choice activity. In the Properties view, select the Details tab and correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBW3863W: The XPath correlation set property propertyAlias query is not valid: ''{0}'' (receive choice activity ''{1}'', receive element number {2}, correlation set ''{3}'', propertyAlias for the property ''{4}'' and the messageType ''{5}'').
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath query in the propertyAlias element so that it is valid. In WebSphere Integration Developer, in the business process editor, in the tray on the right side of the process, select the specified correlation property. In the Properties view, correct the XPath expression by selecting the appropriate row in the table and clicking Edit.
- CWWBW3866W: The XPath correlation set property propertyAlias query is not valid: The $ notation to reference a variable in the XPath expression or query ''{0}'' is not supported. (receive choice activity ''{1}'', receive element number {2}, correlation set ''{3}'', propertyAlias for the property ''{4}'' and the messageType ''{5}'').
- Explanation: The $ notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath query in the propertyAlias element so that it is valid. In WebSphere Integration Developer, in the business process editor, in the tray on the right side of the process, select the specified correlation property. In the Properties view, correct the XPath expression by selecting the appropriate row in the table and clicking Edit Correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBW3867W: Receive element number {0} in the ''{1}'' receive choice activity does not use a correlation set.
- Explanation: If more than one receive choice or receive activity is used in a process model, all of the receive elements of a receive choice activity must use at least one correlation set. The correlation set ensures that the input messages correlate with the process instance.
- User Action: Use at least one correlation set for the receive element. In WebSphere Integration Developer, in the business process editor, select the receive element. In the Properties view, select the Correlation tab and add a correlation set.
- CWWBW3868E: The variable must not be set because a fromParts element is available ({0} pick activity, onMessage element number {1}, {2} variable).
- Explanation: The data that is received by this onMessage element can be stored in the activity variable, which must be message-typed, or a message part is specified in the fromPart element.
- User Action: Remove the variable attribute from the onMessage element.
- CWWBW3900E: The {0} receive activity does not use a correlation set.
- Explanation: If more than one receive choice or receive activity is used in a process model, all of the receive activities must use at least one correlation set. The correlation set ensures that the input messages can correlate with the process instance.
- User Action: Set at least one correlation set for the receive activity.
- CWWBW3901E: An incorrect set of correlation sets is used in the {0} receive activity. The expected set of correlation sets, as used in the {1} activity, is {2}.
- Explanation: All of the receive choice or receive activities that create process instances must use the same set of correlation sets.
- User Action: Ensure that all of the receive and receive choice activities that create process instances use the same set of correlation sets.
- CWWBW3902E: A reply activity was not found that matches the {0} receive activity.
- Explanation: For each two-way operation receive activity, the process must contain at least one reply activity with the same port type and operation.
- User Action: Add a reply activity to the process with the same port type and operation as the receive activity.
- CWWBW3903E: The variable must not be set because an output element is available (receive activity ''{0}'', variable ''{1}'').
- Explanation: The data that is received by this receive activity can be stored in the activity variable, which must be message-typed, or in one or more XSD-typed variables specified in the output element.
- User Action: Remove the variable attribute from the receive activity.
- CWWBW3904E: The {0} authorization human task is not an invocation task ({1} receive activity).
- Explanation: The human task that is referred to in the receive activity must be an invocation task.
- User Action: Make sure that the receive activity references an invocation task.
- CWWBW3905W: The {0} receive activity is contained in the parallel {1} forEach activity, which can result in the standard fault bpws:conflictingReceive.
- Explanation: If multiple branches are created in the parallel forEach activity, the contained receive activity can cause the standard fault bpws:conflictingReceive in the runtime environment.
- User Action: Review and test the process to ensure that the parallel execution of the branches in the forEach activity does not cause the standard fault bpws:conflictingReceive.
- CWWBW3906E: The {1} receive activity and process onEvent event number {0} implement the same operation of the same interface. This results in the standard fault bpws:conflictingReceive.
- Explanation: If the receive activity is enabled at the same time as the onEvent event, the standard fault bpws:conflictingReceive is thrown because it is not clear to which of the two constructs an inbound message for that operation and port type must be delivered. The process is in an undefined status.
- User Action: Remove the receive activity or the process onEvent event, or change the implemented operation or port type of the receive activity or onEvent event.
- CWWBW3907E: The {2} receive activity and onEvent number {0} of the {1} scope activity implement the same operation of the same interface. This results in the standard fault bpws:conflictingReceive.
- Explanation: If the receive activity is enabled at the same time as the onEvent event, the standard fault bpws:conflictingReceive is thrown because it is not clear to which of the two constructs an inbound message for that operation and port type must be delivered. The process is in an undefined status.
- User Action: Remove the receive activity or the onEvent event, or change the implemented operation or port type of the receive activity or onEvent event.
- CWWBW3908W: The {0} receive activity is contained in process onEvent event number {1}, which implements a one-way operation, which can result in the standard fault bpws:conflictingReceive.
- Explanation: If this onEvent event runs multiple times in parallel, the contained receive activity can cause the standard fault bpws:conflictingReceive during run time.
- User Action: Review and test the process carefully to ensure that the parallel process of the onEvent event does not result in the standard fault bpws:conflictingReceive.
- CWWBW3909W: The {0} receive activity is contained in onEvent event number {1} of the {2} scope activity, which implements a one-way operation, which can result in the standard fault bpws:conflictingReceive.
- Explanation: If this onEvent event runs multiple times in parallel, the contained receive activity can lead to the standard fault bpws:conflictingReceive during run time.
- User Action: Review and test the process carefully to ensure that the parallel process of the onEvent event does not result in the standard fault bpws:conflictingReceive.
- CWWBW3910W: The {0} receive activity does not use a correlation set.
- Explanation: If more than one receive choice or receive activity is used in a process model, all of the receive activities must use at least one correlation set. The correlation set ensures that the input messages can correlate with the process instance.
- User Action: Use at least one correlation set for the receive activity.
- CWWBW3911E: The variable must not be set because a fromParts element is available ({0} receive activity, {1} variable).
- Explanation: The data that is received by this receive activity can be stored in the activity variable, which must be message-typed, or a message part is specified in the fromParts element.
- User Action: Remove the variable attribute from the receive activity.
- CWWBW4000E: The fault ''{0}'' was not found in the operation ''{1}'' (activity ''{2}'').
- Explanation: The fault used in the activity is not defined.
- User Action: Check that the fault name is correct and that it is defined.
- CWWBW4001E: The process is started using a one-way operation, but it contains the {0} reply activity .
- Explanation: A process that is triggered by a one-way operation invocation must not have a reply activity.
- User Action: Remove the reply activity.
- CWWBW4002E: No receive choice activity, receive activity, or onEvent event was found that matches the {0} reply activity.
- Explanation: For each two-way operation reply activity, the process must contain at least one receive choice activity, receive activity, or onEvent event with the same port type and operation.
- User Action: Add a receive choice activity, receive activity, or onEvent event to the process with the same port type and operation type as the reply activity.
- CWWBW4003E: The {1} variable is set although an input element is available ({0} reply activity).
- Explanation: The data that is sent by this reply activity can be identified by the variable, which must be a message-type variable, or by one or more XML Schema Definition (XSD) type variables that are specified in the input element; therefore, the specified variable should not be set.
- User Action: Remove the variable attribute from the reply activity.
- CWWBW4004E: The {1} variable is set although a toParts element is available ({0} reply activity).
- Explanation: The data that is sent by this reply activity can be identified by the variable or the toParts elements. Use either the variable attribute or the toParts element, but not both.
- User Action: Remove the variable attribute from the reply activity.
- CWWBW4100E: The {0} rethrow activity is used outside of a fault handler.
- Explanation: With a rethrow activity, the faults that are caught in a fault handler can be rethrown. Therefore, rethrow activities can be used only in a fault handler.
- User Action: Move the rethrow activity to a fault handler, or remove it.
- CWWBW4101E: The {0} rethrow activity is used in a scope activity.
- Explanation: With a rethrow activity, the faults that are caught in a fault handler can be rethrown. Therefore, rethrow activities can be used only in a fault handler.
- User Action: Move the rethrow activity to a fault handler, or remove the scope around the rethrow activity.
- CWWBW4200E: The isolated {0} scope activity is nested in the isolated {1} scope activity.
- Explanation: A serializable scope activity must not contain other serializable scope activities.
- User Action: Set the isolated attribute on one of the scope activities to "no".
- CWWBW4201E: Too many type definitions are set for the {0} scope variable ({1} scope activity, {2} message type, {3} type , {4} element).
- Explanation: The message type, type, or element attribute specifies the type of a variable. One (and only one) of them must be set.
- User Action: Ensure that there is only one variable type definition set for the scope variable.
- CWWBW4202E: The {0} scope variable does not have a type definition ({1} scope activity).
- Explanation: The message type, type, or element attribute specifies the type of a variable. One (and only one) of them must be set.
- User Action: Provide a variable type definition for the variable.
- CWWBW4203E: The {0} message type definition was not found ({1} scope activity, {2} scope variable).
- Explanation: The message type definition that is referred to in the scope variable must be defined in a Web Services Description Language (WSDL) interface.
- User Action: Check that the message type definition is referenced correctly and that it is defined correctly in an accessible WSDL interface.
- CWWBW4204E: The {0} XML Schema Definition (XSD) type definition was not found ({1} scope activity, {2} scope variable).
- Explanation: The XSD type definition that is referred to in the scope variable must be a valid built-in XML schema simple type, or it must be defined in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: Check that the XSD type definition is referenced correctly and that it is defined correctly.
- CWWBW4205E: The {0} XML Schema Definition (XSD) element declaration was not found ({1} scope activity, {2} scope variable).
- Explanation: The XSD element declaration that is referred to in the scope variable must be defined in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: Check that the XSD element declaration is referenced correctly and that it is defined correctly.
- CWWBW4206E: The {0} scope variable name is already used ({1} scope activity).
- Explanation: The name of a variable must be unique in its scope.
- User Action: Use another variable name.
- CWWBW4207E: The event handler of the {0} scope activity does not contain an onEvent event or a timeout.
- Explanation: An event handler must have at least one onEvent event or one timeout event.
- User Action: Define an onEvent event or a timeout event, or remove the event handler.
- CWWBW4208E: The {0} partner was not found ({1} scope activity, onEvent event number {2}).
- Explanation: The partner that is referred to in the onEvent event is not defined.
- User Action: Ensure that the partner is correct and that it is defined.
- CWWBW4209E: The {0} partner is not an interface partner ({1} scope activity, onEvent event number {2}).
- Explanation: Partners used in onEvent events must define the myRole role.
- User Action: Define the myRole role for the partner, or use another partner.
- CWWBW4210E: The {0} interface was not found ({1} scope activity, onEvent event number {2}).
- Explanation: The interface (also called a port type) that is referred to in the onEvent event is not defined in the Web Services Description Language (WSDL) interface.
- User Action: Ensure that the specified interface is correct and that it is defined in the WSDL interface.
- CWWBW4211E: The interface that is referred to in onEvent event number {0} and in the {1} myRole role are not the same ({2} scope activity, {3} partner, {4} partnerLinkType).
- Explanation: The interface (portType attribute) in the onEvent event is optional. However, when it is set, it must be the same as the interface (portType attribute) that is set in the myRole role in the partner.
- User Action: Ensure that the interfaces are the same.
- CWWBW4212E: The {0} operation was not found ({1} scope activity, onEvent number {2}).
- Explanation: The operation that is referred to in the onEvent event is not defined in the Web Services Description Language (WSDL) interface.
- User Action: Ensure that the specified operation is correct and that it is defined in the WSDL interface.
- CWWBW4213E: The input is not defined for the {0} operation ({1} scope activity, onEvent number {2}).
- Explanation: The operation that is referenced in the onEvent event must have an input element.
- User Action: Define an input element, or use another operation.
- CWWBW4214E: The type is not set in the input for the {0} operation ({1} scope activity, onEvent number {2}).
- Explanation: The input message type must be set if the operation is used in this onEvent event.
- User Action: Set the input message type, or use another operation.
- CWWBW4215E: The {0} type that is referred to in the {1} operation was not found ({2} scope activity, onEvent number {3}).
- Explanation: The message type that is referred to must be defined if the operation is used in this onEvent event.
- User Action: Set the message type, or use another operation.
- CWWBW4216E: The type of the {0} variable and the type of the input to the {1} operation are not the same ({2} scope activity, onEvent number {3}).
- Explanation: The message type of the variable and of the input element to the operation must be the same.
- User Action: Ensure that the variable and the input element have the same message type.
- CWWBW4217E: The variable is not set ({0} scope activity, onEvent number {1}).
- Explanation: A mandatory variable for the onEvent event is not defined.
- User Action: Define the mandatory variable.
- CWWBW4218E: The messageType or element is not set ({0} scope activity, onEvent event number {1}).
- Explanation: A mandatory attribute (messageType or element) for the onEvent event is not defined.
- User Action: Define either the messageType or element attribute.
- CWWBW4219E: The {0} type was not found ({1} scope activity, onEvent number {2}).
- Explanation: The message type that is referred to in the onEvent event is not defined in the Web Services Description Language (WSDL) interface.
- User Action: Check that the message type is defined correctly in the WSDL interface.
- CWWBW4220E: The {0} correlation set was not found ({1} scope activity, onEvent number {2}).
- Explanation: The correlation set that is used in the onEvent event is not defined.
- User Action: Define the correlation set, or remove it from the onEvent event.
- CWWBW4221E: The variable must not be set because an output element is available (scope activity ''{0}'', onEvent event number {1}, variable ''{2}'').
- Explanation: The data that is received by this onEvent event can be stored in the onEvent variable, which must be message-typed, or in one or more XSD-typed variables specified in the output element.
- User Action: Remove the variable attribute from the onEvent event.
- CWWBW4222E: The compensable attribute on the {0} scope activity cannot be compensated.
- Explanation: The compensable attribute on the specified scope activity is set to "no"; therefore, it cannot have a compensation handler and cannot be compensated.
- User Action: Remove the compensation handler, or set the compensable attribute to "yes".
- CWWBW4223E: The data-type variable mapping is used for the {0} message ({1} scope activity, onEvent number {2}).
- Explanation: The input message of the operation in the onEvent event cannot be used with the parameter extension. For example, the message might contain an array, which cannot be mapped to data-type variables in the process.
- User Action: Modify the message that is used with the parameter extension, or use a message type variable.
- CWWBW4224E: The {0} input that is used in the data-type variable mapping of the onEvent event is not mapped to an input of the associated operation ({1} scope activity, onEvent number {2}, input number {3}).
- Explanation: One parameter does not map to an element in the wrapper or to a part in the message.
- User Action: Remove the parameter, or map it to a valid element or part.
- CWWBW4225E: The {0} variable is already used in the same onEvent event ({1} scope activity, onEvent number {2}, input number {3}).
- Explanation: A variable name can be used only once in an output element.
- User Action: Use another variable name.
- CWWBW4226E: A matching property alias definition was not found for the {0} correlation property and {1} type ({2} scope activity, onEvent number {3}, {4} correlation set).
- Explanation: A property alias definition is needed to map the parts of a message type to the correlation properties.
- User Action: Define the property alias.
- CWWBW4227E: The {0} part that is referred to in the property alias for the {1} correlation property and the {2} type was not found ({3} scope activity, onEvent event number {4}, {5} correlation set).
- Explanation: The part must be defined for the message type.
- User Action: Define the part, or use an existing part in the property alias.
- CWWBW4228E: The {0} part that is referred to in the property alias for the {1} correlation property and the {2} type do not refer to a valid XML schema simple type ({3} scope activity, onEvent event number {4}, {5} correlation set).
- Explanation: The specified part of the message type must be an XML schema simple type because a property can have only XML schema simple types.
- User Action: Select a part that has an XML schema simple type.
- CWWBW4229E: The type of the {0} part of the {1} messageType and the type of the {2} correlation property are not the same. ({3} scope activity, onEvent event number {4}, {5} correlation set)
- Explanation: No additional information is available.
- User Action: Select a part that has same XML schema simple type as the property type.
- CWWBW4230E: Multiple property alias definitions were found for the {0} correlation property and the {1} type ({2} scope activity, onEvent event number {3}, {4} correlation set).
- Explanation: A property-message type pair can have only one property alias definition.
- User Action: Ensure that only one property alias is available for the property-message type pair. If you need more than one part of a message type as a property, create properties and property alias definitions for the additional parts of the same message type.
- CWWBW4231E: The {0} authorization human task was not found ({1} scope activity onEvent event number {2}).
- Explanation: The human task that is referenced in the scope activity onEvent event cannot be found.
- User Action: Remove the human task reference, or ensure that the human task can be found.
- CWWBW4232E: The {0} authorization human task is not an invocation task ({1} scope activity, onEvent event number {2}).
- Explanation: The human task that is referred to in the scope activity onEvent event must be an invocation task.
- User Action: Make sure that the scope activity references an invocation task.
- CWWBW4233E: The interface that is referred to in onEvent event number {0} and in the {1} authorization human task are not the same ({2} scope activity).
- Explanation: The interfaces must be the same.
- User Action: Ensure that the interfaces are the same.
- CWWBW4234E: The operation that is referenced in onEvent event number {0} and in the {1} authorization human task are not the same ({2} scope activity).
- Explanation: The operations must be the same.
- User Action: Ensure that the operations are the same.
- CWWBW4235E: The part is not set in the property alias for the {0} correlation property and the {1} type ({2} scope activity, onEvent event number {3}, {4} correlation set).
- Explanation: The part must be set in the property alias.
- User Action: Set the part.
- CWWBW4236E: The {0} query language that is used in the property alias is not supported. It must be one of {1} ({2} scope activity, onEvent event number {3}, {4} correlation set, property alias for the correlation property: {5}, {6} type).
- Explanation: The specified query language is unknown. Queries that are specified in this query language cannot be run.
- User Action: Use one of the supported query languages.
- CWWBW4237E: A reply activity was not found that matches onEvent event number {0} of the {1} scope activity.
- Explanation: For each two-way operation onEvent event in a scope activity, the process must contain at least one reply activity with the same port type and operation.
- User Action: Add a reply activity to the process with the same port type and operation as the onEvent event of the scope activity.
- CWWBW4238E: The expression is not valid for the {2} expression language ({0} scope activity, timeout number {1}).
- Explanation: No additional information is available.
- User Action: Check the expression and the expression language.
- CWWBW4239E: Too many variable type definitions are set for the {0} variable ({1} scope activity, onEvent event number {2}, input number {3}, {4} type, {5} element).
- Explanation: The type or element attributes define the type of a variable. One (and only one) of these attributes must be set.
- User Action: Ensure that there is only one variable type definition set for the variable.
- CWWBW4240E: The {0} XML Schema Definition (XSD) element declaration was not found ({1} scope activity, onEvent event number {2}, input number {3}, {4} variable).
- Explanation: The XSD element declaration that is referred to in the variable must be defined inline in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: Check that the XSD element declaration is correctly referenced and that it is defined correctly.
- CWWBW4241E: The {0} XML Schema Definition (XSD) type definition was not found ({1} scope activity, onEvent event number {2}, input number {3}, {4} variable).
- Explanation: The XSD type definition that is referred to in the variable must be a valid built-in XML schema simple type or it must be defined inline in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBW4242E: The {0} variable does not have a variable type definition ({1} scope activity, onEvent event number {2}, input number {3}).
- Explanation: The type or element attributes are used to specify the type of a variable. One (and only one) of these attributes must be set.
- User Action: Provide a variable type definition for the variable.
- CWWBW4243E: The {0} XML Schema Definition (XSD) type definition was not found ({1} scope activity, onEvent event number {2}, input number {3}, input of the associated operation: {4}).
- Explanation: The XSD type definition that is referred to in the matching part or element must be a valid built-in XML schema simple type or it must be defined inline in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBW4244E: The {0} XML Schema Definition (XSD) element declaration was not found ({1} scope activity, onEvent event number {2}, input number {3}, input of the associated operation: {4}).
- Explanation: The XSD element declaration that is referred to in the matching part or element must be defined inline in a Web Services Description Language (WSDL) interface or in an XML schema.
- User Action: Check that the XSD element declaration is correctly referenced and that it is defined correctly.
- CWWBW4245E: The {0} input that is used in the data-type variable mapping is assigned to the {1} variable although the data type does not match ({2} scope activity, onEvent event number {3}, input number {4}).
- Explanation: The element and the variable are incompatible. Only compatible types can be assigned, for example, from xsd:string to xsd:string.
- User Action: Ensure that the types are compatible.
- CWWBW4246E: The {0} input that is used in the data-type variable mapping is assigned to the {1} variable although the data type does not match ({2} scope activity, onEvent event number {3}, input number {4}).
- Explanation: The message part and the variable are incompatible. Only compatible types can be assigned, for example, from xsd:int to xsd:int.
- User Action: Ensure the types are compatible.
- CWWBW4247E: The {0} input of the associated operation is not mapped to an input in the data-type variable mapping ({1} scope activity, onEvent event number {2}).
- Explanation: An element in the wrapper does not map to a parameter.
- User Action: Remove the element, or map it to a parameter.
- CWWBW4248E: The {0} input of the associated operation is not mapped to an input in the data-type variable mapping of onEvent event number {2} ({1} scope activity).
- Explanation: A message part in the wrapper does not map to a parameter.
- User Action: Remove the message part, or map it to a parameter.
- CWWBW4249E: The {0} correlation set is already used ({1} scope activity, onEvent event number {2}).
- Explanation: The correlation set can be used only once per event.
- User Action: Ensure that the correlation set is used only once in the specified event.
- CWWBW4250W: The {0} scope activity defines event handlers and is contained in the parallel {1} forEach activity, which can result in the standard fault bpws:conflictingReceive.
- Explanation: If multiple branches are created in the parallel forEach activity, the contained event handlers of the scope activity can cause the standard fault bpws:conflictingReceive during run time.
- User Action: Review and test the process to ensure that the parallel execution of the branches in the forEach activity does not result in the standard fault bpws:conflictingReceive.
- CWWBW4251E: onEvent event number {0} implements the {1} operation of the {2} interface, which is already implemented in another onEvent event ({3} scope activity).
- Explanation: The same interface (port type) and operation can be implemented only once in the same event handler. If a message is received for a specific interface (port type) and operation, the processing engine must know which onEvent event in that instance of the process must run.
- User Action: Remove the onEvent event, or change the operation.
- CWWBW4252E: onEvent event number {0} does not use a correlation set ({1} scope activity).
- Explanation: If an onEvent event is used in a process model, it must use at least one correlation set. The correlation set ensures that the input messages can correlate with the process instance.
- User Action: Set at least one correlation set for the onEvent event.
- CWWBW4253E: The same operation of the same interface is implemented by the process onEvent event number {0}, which can result in the standard fault bpws:conflictingReceive ({1} scope activity, onEvent event number {2}).
- Explanation: If the scope activity is enabled simultaneously with the process onEvent event, the standard fault bpws:conflictingReceive is thrown because it is not clear to which of the two events an inbound message for that operation and interface (port type) should be delivered. The process is in an undefined status.
- User Action: Remove the scope activity, the onEvent event of the scope activity, or the process onEvent event, or change the implemented operation or interface of one of the onEvent events.
- CWWBW4254E: The same operation of the same interface is implemented by onEvent event number {0} of the {1} outer scope activity, which can result in the standard fault bpws:conflictingReceive ({2} nested Scope activity, onEvent event number {3}).
- Explanation: If the inner scope activity is enabled simultaneously with the onEvent event of the outer scope activity, the standard fault bpws:conflictingReceive is thrown because it is not clear to which of the two events an inbound message for that operation and port type should be delivered. The process is in an undefined status.
- User Action: Remove the inner scope activity, the onEvent event of the inner scope activity, or the onEvent event of the outer scope activity, or change the implemented operation or port type of one of the onEvent events.
- CWWBW4255W: The {0} scope activity defines event handlers and is contained in process onEvent event number {1}, which implements a one-way operation. This can result in the standard fault bpws:conflictingReceive.
- Explanation: If the process onEvent event runs multiple times in parallel, the defined event handlers in the scope activity can lead to the standard fault bpws:conflictingReceive during run time.
- User Action: Review and test the process to ensure that the parallel processing of the onEvent event does not result in the standard fault bpws:conflictingReceive.
- CWWBW4256W: The {0} nested scope activity defines event handlers and is contained in onEvent event number {1} of the {2} outer scope activity, which implements a one-way operation and might result in the standard fault bpws:conflictingReceive.
- Explanation: If the outer onEvent event runs multiple times in parallel, the defined event handlers in the scope activity can lead to the standard fault bpws:conflictingReceive during run time.
- User Action: Review and test the process to ensure that the parallel processing of the onEvent event does not result in the standard fault bpws:conflictingReceive.
- CWWBW4257E: Query properties are allowed only for process variables ({0} scope activity, {1} local variable).
- Explanation: The query properties extension is for identifying process instances on variable values. Therefore, the extension is allowed only for global variables that are defined on the process element.
- User Action: Remove the query properties extension that is defined for the scope variable.
- CWWBW4258E: The XML Path Language (XPath) date or duration is not valid ({1} scope activity, timeout number {2}). The error is {0}.
- Explanation: The specified XPath for, until, or repeatEvery expression is not syntactically valid.
- User Action: Ensure that the XPath "for", "until", or repeatEveryexpression is valid.
- CWWBW4259E: The XML Path Language (XPath) property alias query is not syntactically valid. The error is {0} ({1} scope activity, onEvent event number {2}, {3} correlation set, {4} property alias for the correlation property, {5} type).
- Explanation: No additional information is available.
- User Action: Ensure that the XPath query in the correlation set property propertyAlias is valid.
- CWWBW4260W: The XML Path Language (XPath) property alias query is empty ({0} scope activity, onEvent event number {1}, {2} correlation set, {3} property alias for the correlation property, {4} message type).
- Explanation: The specified XPath query in the correlation set property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the correlation set property propertyAlias is valid. Add a query construct, or remove the query element.
- CWWBW4261W: Assigning the {0} xsd:anyType type element to the {1} xsd:anySimpleType type variable might result in a runtime error ({2} scope activity, onEvent event number {3}, parameter number {4}).
- Explanation: No additional information is available.
- User Action: Ensure that the types are compatible.
- CWWBW4262W: Assigning the {0} xsd:anyType typed part to the {1} xsd:anySimpleType type variable might result in a runtime error ({2} scope activity, onEvent event number {3}, parameter number {4}).
- Explanation: No additional information is available.
- User Action: Ensure that the types are compatible.
- CWWBW4263W: The XML Path Language (XPath) date or duration in timeout number {2} of the {1} scope activity is not valid. The error is: {0}
- Explanation: The specified XPath expression is not supported.
- User Action: In WebSphere Integration Developer, in the business process editor, select the specified scope activity. Open the associated event handler and select the specified timeout. In the Properties view, on the Details tab, correct the XPath for, until, or repeatEvery expression.
- CWWBW4266W: The XML Path Language (XPath) date or duration in timeout number {2} of the {1} scope activity is not valid because the $ notation that is used to refer to a variable in the {0} XPath expression or query is not supported.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, in the business process editor, select the specified scope activity. Open the associated event handler and select the specified timeout. In the Properties view, on the Details tab, correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBW4267W: The XML Path Language (XPath) property alias query is not valid ({1} scope activity, onEvent event number {2}, {3} correlation set, {4} property alias for the correlation property, {5} type). The message is {0}
- Explanation: The specified XPath expression is not supported.
- User Action: In WebSphere Integration Developer, in the business process editor, in the tray on the right side of the process, select the specified correlation property. In the Properties view, correct the XPath expression by selecting the appropriate row in the table and clicking Edit.
- CWWBW4270W: The XML Path Language (XPath) property alias query is not valid. The $ notation for referencing a variable in the {0} XPath expression or query is not supported ({1} scope activity, onEvent event number {2}, {3} correlation set, {4} property alias for the correlation property, {5} type).
- Explanation: The $ notation for referencing a variable is not supported in this XPath expression.
- User Action: Edit the XPath query in the specified element (propertyAlias) so that it is valid. In WebSphere Integration Developer, in the business process editor, in the tray on the right side of the process, select the specified correlation property. In the Properties view, select the appropriate row in the table, click Edit, and correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBW4271E: Both the element and type attributes for the {1} onEvent event ({0} scope activity) are specified.
- Explanation: The OnEvent element can specify either an element attribute or a messageType attribute, but not both.
- User Action: Remove the element or the messageType attribute.
- CWWBW4272E: The {0} element was not found ({1} scope activity, onEvent event number {2}).
- Explanation: The element that is referred to in the onEvent event is not defined in the Web Services Description Language (WSDL) interface.
- User Action: Modify the element if it is not defined correctly in the WSDL interface.
- CWWBW4273E: The variable is set although a fromParts element is available ({0} scope activity, onEvent event number {1}, {2} variable).
- Explanation: The data that was received by this onEvent event can be stored in the onEvent variable, which must be a message-type variable, or a message part is specified in the fromParts element.
- User Action: Remove the variable attribute from the onEvent event.
- CWWBW4400E: The {0} expression language of the condition is not supported. It must be one of {1} ({2} choice activity, case number {3}).
- Explanation: The specified expression language is unknown. Expressions that are specified in this expression language cannot run.
- User Action: Use one of the supported expression languages.
- CWWBW4401E: The condition is not valid ({0} choice activity, case number {1}, {2} expression language).
- Explanation: The specified expression is not valid for the specified expression language, or it is not valid in this context. For example, if you use the built-in expression language in the case condition, only the values wpc:true and wpc:false are allowed.
- User Action: Check the expression and the expression language.
- CWWBW4402E: The XML Path Language (XPath) condition is not syntactically valid ({1} choice activity, case number {2},). The error is {0}
- Explanation: No additional information is available.
- User Action: Ensure that the XPath case condition is valid.
- CWWBW4403W: The XML Path Language (XPath) case in case number {2} of the {1} choice activity is not valid. The error is {0}
- Explanation: The specified XPath expression is not supported.
- User Action: In WebSphere Integration Developer, in the business process editor, select the specified choice activity. In the Properties view, on the Details tab, correct the XPath expression.
- CWWBW4406W: The XML Path Language (XPath) condition in case number {2} of the {1} choice activity is not valid because the $ notation that is used to refer to a variable in the {0} XPath expression or query is not supported.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, in the business process editor, select the specified choice activity. In the Properties view, on the Details tab, correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData() XPath function.
- CWWBW4500E: The {0} fault variable is not defined ({1} throw activity).
- Explanation: The fault variable that is used in the throw activity must be defined.
- User Action: Check that the fault variable name is defined correctly.
- CWWBW4600E: The {0} wait activity does not specify a date or a duration.
- Explanation: The "for" expression specifies the duration expression after which the event is signaled. The "until" expression specifies when the timeout event is fired. One of these expressions must occur in a wait activity.
- User Action: Specify a "for" or "until" expression.
- CWWBW4601E: The {0} wait activity specifies both a date and a duration.
- Explanation: The "for" expression specifies the duration expression after which the event is signaled. The "until" expression specifies when the timeout event is fired. Only one of these expressions can occur in a wait activity.
- User Action: Remove either the "for" or "until" expression.
- CWWBW4602E: The {0} wait activity does not specify a date.
- Explanation: The "for" expression specifies the duration expression after which the event is signaled. The "until" expression specifies when the timeout event is fired. The timeout expression specifies a timeout using a calendar that is supplied by the WebSphere Application Server scheduling service, or user-written calendars that adhere to those scheduling service conventions. One of these expressions must occur in a wait activity.
- User Action: Specify a "for", "until", or timeout expression.
- CWWBW4603E: The {0} wait activity specifies more than one expression.
- Explanation: The "for" expression specifies the duration expression after which the event is signaled. The "until" expression specifies when the timeout event is fired. The timeout expression specifies a timeout using a calendar that is supplied by the WebSphere Application Server scheduling service, or user-written calendars that adhere to those scheduling service conventions. One of these expressions must occur in a wait activity.
- User Action: Specify a "for", "until", or timeout expression.
- CWWBW4604E: The {0} expression language is not supported ({2} wait activity). The language must be one of {1}.
- Explanation: Expressions that are specified in this expression language cannot run.
- User Action: Use one of the supported expression languages.
- CWWBW4605E: The XML Path Language (XPath) date or duration is not syntactically valid ({1} wait activity). The error is {0}
- Explanation: No additional information is available.
- User Action: Ensure that the XPath for or until expression is valid.
- CWWBW4606W: In the {1} wait activity, the XML Path Language (XPath) date or duration is not valid. The error is {0}
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, in the business process editor, select the specified wait activity. In the Properties view, on the Details tab, correct the XPath expression.
- CWWBW4609W: In the {1} wait activity, the XML Path Language (XPath) date or duration is not valid because the $ notation that is used to refer to a variable in the {0} XPath expression or query is not supported.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, in the business process editor, select the specified wait activity. In the Properties view, on the Details tab, correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBW4700E: The {0} expression language of the condition is not supported. It must be one of {1} ({2} while loop activity).
- Explanation: Expressions that are specified in this expression language cannot run.
- User Action: Use one of the supported expression languages.
- CWWBW4701E: The condition is not valid ({0} while loop activity, {1} expression language).
- Explanation: The specified expression is not valid for the specified expression language, or it is not valid in this context. For example, if you use the built-in expression language in the while loop condition, only the values wpc:true and wpc:false are allowed.
- User Action: Check the expression and the expression language.
- CWWBW4702E: The XML Path Language (XPath) condition is not syntactically valid ({1} while loop activity). The error is {0}
- Explanation: No additional information is available.
- User Action: Ensure that the XPath while loop condition is valid.
- CWWBW4703W: In the {1} while loop activity, the XML Path Language (XPath) condition is not valid. The error is {0}
- Explanation: The specified XPath expression is not supported.
- User Action: In WebSphere Integration Developer, in the business process editor, select the specified while loop activity. In the Properties view, on the Details tab, correct the XPath expression.
- CWWBW4706W: In the {1} while loop activity, the XML Path Language (XPath) condition is not valid because the $ notation that is used to refer to a variable in the {0} XPath expression or query is not supported.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, in the business process editor, select the specified while loop activity. In the Properties view, on the Details tab, correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBW4800E: The namespace of the custom activity ''{0}'' is not valid: ''http://'' is missing or ''http:///'' is used (used namespace ''{1}'', element name ''{2}'').
- Explanation: The namespace of the custom activity must start with 'http://', but not with 'http:///'.
- User Action: Ensure that the namespace starts with 'http://'.
- CWWBW4801E: The plug-in for the custom activity ''{0}'' does not implement the expected interface (found plug-in ''{1}'').
- Explanation: The plug-in must implement the correct interface.
- User Action: Ensure that the plug-in implements the correct interface.
- CWWBW4802E: An exception occurred when the plug-in for the custom activity ''{0}'' was loaded (exception ''{1}'').
- Explanation: The plug-in could not be instantiated.
- User Action: Ensure that the plug-in is in the class path and that it is accessible.
- CWWBW4803E: {0} (custom activity ''{1}'', plug-in ''{2}'').
- Explanation: The plug-in for the custom activity reported the specified error.
- User Action: Fix the reported error.
- CWWBW4804W: {0} (custom activity ''{1}'', plug-in ''{2}'').
- Explanation: The plug-in for the custom activity reported the specified warning.
- User Action: Fix the reported warning.
- CWWBW4805I: {0} (custom activity ''{1}'', plug-in ''{2}'').
- Explanation: The plug-in for the custom activity reported the specified information message.
- User Action: No action is required.
- CWWBW4806E: The result returned from the plug-in validation is not valid: {0} (custom activity ''{1}'', plug-in ''{2}'').
- Explanation: The plug-in validation must return ValidationMessages.
- User Action: Contact the plug-in owner.
- CWWBW4900E: The interface is not set ({0} human task activity).
- Explanation: The interface (port type) is needed to access the operations.
- User Action: Ensure that the interface is set.
- CWWBW4901E: The administration task is assigned to the {0} human task activity.
- Explanation: AdminTask elements are allowed only for invoke, script, and custom activities, but not for human task activities.
- User Action: Remove the adminTask element from the human task activity.
- CWWBW4902E: The {0} human task is not a to-do task ({1} human task activity).
- Explanation: The human task that is referred to in the human task activity must be a to-do task.
- User Action: Make sure that the human task activity refers to a to-do task.
- CWWBW4903E: The name of the {0} human task activity and the referred-to {1} human task are not the same.
- Explanation: The names must be the same.
- User Action: Rename the human task activity or the participating human task so that the names are the same.
- CWWBW4904E: The {1} operation is not a request-response operation ({0} human task activity).
- Explanation: Human task activities must invoke a request-response participating task, which specify an input and an output message. The specified operation does not specify the output message.
- User Action: Specify the output message for the operation, or use another request-response operation.
- CWWBW4905E: The process contains a human task activity that contains errors ({0} human task).
- Explanation: No additional information is available.
- User Action: Refer to the human task errors and correct them.
- CWWBW5000E: The {0} expression language of the start expression is not supported. It must be one of {1} ({2} forEach activity).
- Explanation: Expressions that are specified in this expression language cannot run.
- User Action: Use one of the supported expression languages.
- CWWBW5001E: The {0} expression language of the end expression is not supported. It must be one of {1} ({2} forEach activity).
- Explanation: Expressions that are specified in this expression language cannot run.
- User Action: Use one of the supported expression languages.
- CWWBW5002E: The {0} expression language of the early exit criterion expression is not supported. It must be one of {1} ({2} forEach activity).
- Explanation: Expressions that are specified in this expression language cannot run.
- User Action: Use one of the supported expression languages.
- CWWBW5003E: A variable with the {0} name is defined on the {1} scope activity although a variable with that name is defined on that scope activity implicitly in the {2} forEach activity.
- Explanation: The forEach activity specifies a counter name, which is an implicit variable declaration on the directly enclosed scope activity. Therefore, the in the forEach activity directly enclosed scope activity must not define a variable with a name that is the same as the counter name.
- User Action: Remove the variable from the scope activity, rename it, or rename the counter name in the specified forEach activity.
- CWWBW5004E: The XML Path Language (XPath) start expression is not syntactically valid ({1} forEach activity). The error is {0}
- Explanation: No additional information is available.
- User Action: Ensure that the XPath startCounterValue expression is valid.
- CWWBW5005E: The XML Path Language (XPath) end expression is not syntactically valid ({1} forEach activity). The error is {0}
- Explanation: No additional information is available.
- User Action: Ensure that the XPath finalCounterValue expression is valid.
- CWWBW5006E: The XML Path Language (XPath) early exit criterion expression is not syntactically valid ({1} forEach activity). The error is {0}
- Explanation: No additional information is available.
- User Action: Ensure that the XPath completionCondition expression is valid.
- CWWBW5007W: In the {1} forEach activity, the XML Path Language (XPath) early exit criterion expression is not valid. The error is {0}
- Explanation: The specified XPath expression is not supported.
- User Action: In WebSphere Integration Developer, select the specified forEach activity. In the Properties view, on the Details tab, open the Early Exit Criterion section. Correct the XPath expression.
- CWWBW5010W: In the {1} forEach activity, the XML Path Language (XPath) early exit criterion expression is not valid because the $ notation that is used to refer to a variable in the {0} XPath expression or query is not supported.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, select the specified forEach activity. In the Properties view, on the Details tab, open the Early Exit Criterion section. Correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBW5011W: In the {1} forEach activity, the XML Path Language (XPath) end expression is not valid. The error is {0}
- Explanation: The specified XPath expression is not supported.
- User Action: In WebSphere Integration Developer, select the specified forEach activity. In the Properties view, on the Details tab, open the Iteration section. Correct the XPath expression.
- CWWBW5014W: In the {1} forEach activity, the XML Path Language (XPath) end expression is not valid because the $ notation that is used to refer to a variable in the {0} XPath expression or query is not supported.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, select the specified forEach activity. In the Properties view, on the Details tab, open the Iteration section. Correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBW5015W: In the {1} forEach activity, the XML Path Language (XPath) start expression is not valid. The error is {0}
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, select the specified forEach activity. In the Properties view, on the Details tab, open the Iteration section. Correct the XPath expression.
- CWWBW5018W: In the {1} forEach activity, the XML Path Language (XPath) start expression is not valid because the $ notation that is used to refer to a variable in the {0} XPath expression or query is not supported.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, select the specified forEach activity. In the Properties view, on the Details tab, open the Iteration section. Correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBW6000E: The data-type variable can use only inline-defined query properties ({0} process variable, query property number {1}, {2} referenced correlation property).
- Explanation: Referenced properties can be used as query properties only in the context of message-type variables.
- User Action: Define an inline query property, or remove the queryProperty element from the variable.
- CWWBW6001E: The {0} correlation property is already used as a query property in this variable ({1} process variable, query property number {2}).
- Explanation: Properties, whether they are referred to or defined inline, can be used as query properties only once per variable.
- User Action: Remove the queryProperty element from the variable.
- CWWBW6002E: The {0} correlation property is referred to for use as a query property, but one or more of the name, type, and part attributes, a query expression, or both are specified ({1} process variable, query property number {2}).
- Explanation: A queryProperty element can refer to an existing property or it can define an inline property by specifying one or more of the name, type, and part attributes, a query expression, or both.
- User Action: Ensure that either an existing property is referenced or an inline property is specified.
- CWWBW6003E: The query property number {0} does not refer to an existing correlation property or define an XML Path Language (XPath) query ({1} process variable).
- Explanation: A queryProperty element can either refer to an existing property or it can define an inline property by specifying one or more of the name, type, and part attributes, a query expression, or both.
- User Action: Ensure that either an existing property is referenced or an inline property is specified.
- CWWBW6004E: The query property does not specify a name ({0} process variable, query property number {1}).
- Explanation: An inline-defined query property must specify the name attribute.
- User Action: Set the name attribute.
- CWWBW6005E: The {0} query property does not specify a type ({1} process variable, query property number {2}).
- Explanation: An inline-defined query property must specify the type attribute.
- User Action: Set the type attribute.
- CWWBW6006E: The type of the {0} referenced correlation property is not set ({1} process variable, query property number {2}).
- Explanation: The type of the referenced property must be set. Only XML schema simple types are allowed. List types and union types are not allowed.
- User Action: Set the XML schema simple type for the property.
- CWWBW6007E: The {0} type of the {1} referenced correlation property was not found or is not an allowed or valid XML schema simple type in this context ({2} process variable, query property number {3}).
- Explanation: The type that is used in the specified property is not defined, not allowed (for example, it is a complex type, a list type, or a union type), or not valid (for example, a loop in the type definition). Allowed types are all of the XML schema primitive simple types and all simple types that are derived by restriction from a primitive simple type.
- User Action: Select an allowed XML schema simple type.
- CWWBW6008E: A matching property alias definition was not found for the {0} referenced correlation property and the {1} type ({2} process variable, query property number {3}).
- Explanation: A property alias definition is needed to map the parts of a message type to the specified property.
- User Action: Define the propertyAlias property.
- CWWBW6009E: The {0} part was not referred to in the property alias for the {1} referenced correlation property and the {2} type ({3} process variable, query property number {4}).
- Explanation: The part must be defined in the message type.
- User Action: Define the part, or use another existing part in the propertyAlias property.
- CWWBW6010E: The {0} part does not refer to a valid XML schema simple type ({1} process variable, query property number {2}, part referenced in the property alias for the referenced correlation property: {3}, {4} type).
- Explanation: The selected part of the message type must be an XML schema simple type because a query property can only be of an XML schema simple type.
- User Action: Select a part that is of an XML schema simple type.
- CWWBW6011E: The type of the {0} part of the {1} type and the {2} correlation property are not the same ({3} process variable, query property number {4}).
- Explanation: The selected part of the message type must have the same type as the property.
- User Action: Select a part that has the same XML schema simple type as the property.
- CWWBW6012E: Multiple property alias definitions were found for the {0} referenced correlation property and the {1} type ({2} process variable, query property number {3}).
- Explanation: Every property-message type pair can have only one property alias definition.
- User Action: Ensure only one property alias definition is available for the property-message type pair. If more than one part of a message type is needed as a property, create a new property and property alias definition.
- CWWBW6013E: The part is not set in the property alias for the {0} referenced correlation property and the {1} type ({2} process variable, query property number {3}).
- Explanation: The part must be set in the propertyAlias property.
- User Action: Set the part.
- CWWBW6014E: The {0} query language that is used in the property alias is not supported. It must be one of {1} ({2} process variable, query property number {3}, property alias for the referenced correlation property {4}, {5} type).
- Explanation: Queries that are specified in this query language cannot be run.
- User Action: Use one of the supported query languages.
- CWWBW6015E: The {0} type was not found or is not an allowed or valid XML schema simple type in this context ({1} process variable, query property number {2}, {3} inline-defined query property).
- Explanation: The type that is specified for the inline-defined query property is not defined, not allowed (for example, it is a complex type, a list type, or a union type), or not valid (for example, a loop in the type definition). Allowed types are all of the XML schema primitive simple types and all simple types that are derived by restriction from a primitive simple type.
- User Action: Select an allowed XML schema simple type.
- CWWBW6016E: The {0} inline-defined query property does not specify the part because the variable is a message-type variable ({1} process variable, query property number {2}, {3} type).
- Explanation: The part attribute must be set if the variable is a message-type variable.
- User Action: Set the part attribute.
- CWWBW6017E: The {0} inline-defined query property specifies a part, but the variable is not a message-type variable ({1} process variable, query property number {2}).
- Explanation: A part is not available if the variable is type-type or element-type.
- User Action: Remove the part attribute.
- CWWBW6018E: The {0} part was not found in the {1} type ({2} process variable, query property number {3}, {4} inline-defined query property).
- Explanation: The part must be defined in the messageType property.
- User Action: Define the part, or use another existing part.
- CWWBW6019E: The {0} part does not refer to a valid XML schema simple type ({1} process variable, query property number {2}, {3} inline-defined query property, {4} type).
- Explanation: The selected part of the message type must be an XML schema simple type because it is a query property.
- User Action: Select a part that is of an XML schema simple type.
- CWWBW6020E: The {0} query language is not supported. It must be one of {1} ({2} process variable, query property number {3}, {4} inline-defined query property).
- Explanation: Queries that are specified in this query language cannot be run.
- User Action: Use one of the supported query languages.
- CWWBW6021E: The part is not the same as the {0} part that is specified in the {1} process variable in query property number {2} ({3} process variable, query property number {4}, {5} inline-defined query property).
- Explanation: The same inline-defined query property is specified in two message-type variables of the same message type. Therefore, the part specified in the inline-defined query property must be the same.
- User Action: Ensure that the part of both query property definitions is the same.
- CWWBW6022E: The query is not the same as the query that is specified in the {0} process variable in query property number {1} ({2} process variable, query property number {3}, {4} inline-defined query property).
- Explanation: The same inline-defined query property is specified in two variables of the same message type, XSD type, or XSD element. Therefore, the query specified in the inline defined query property must be the same.
- User Action: Ensure that the query of both query property definitions is the same.
- CWWBW6023E: The property type of the {0} inline-defined query property is not {1}, as specified in the {2} process variable in query property number {3} ({4} process variable, query property number {5}).
- Explanation: The same name is specified in two inline query property definitions in two variables, but the type is different.
- User Action: Ensure that the type of both query property definitions is the same.
- CWWBW6024E: The XML Path Language (XPath) property alias query is not syntactically valid ({1} process variable, query property number {2}, {3} property alias for the referenced correlation property, {4} type). The error is {0}.
- Explanation: No additional information is available.
- User Action: Ensure that the XPath query in the queryProperty propertyAlias property is valid.
- CWWBW6025E: The XML Path Language (XPath) query of the query property is not syntactically valid ({1} process variable, query property number {2}, {3} inline-defined query property). The error is {0}.
- Explanation: No additional information is available.
- User Action: Ensure that the XPath query in the queryProperty is valid.
- CWWBW6026E: The XML Path Language (XPath) date or duration is not valid (process timeout {1}). The error is {0}.
- Explanation: The specified XPath for, until, or repeatEvery expression is not syntactically valid.
- User Action: Ensure that the XPath "for", "until", or repeatEvery expression is valid.
- CWWBW6027E: The XML Path Language (XPath) property alias query is not syntactically valid (process onEvent event number {1}, {2} correlation set, {3} property alias for the correlation property, {4} type). The error is {0}.
- Explanation: No additional information is available.
- User Action: Ensure that the XPath query in the correlation set propertyAlias property is valid.
- CWWBW6028W: The XML Path Language (XPath) property alias query is be empty ({0} process variable, query property number {1}, {2} property alias for the referenced correlation property, {3} type).
- Explanation: The specified XPath query in the propertyAlias query property is not syntactically valid.
- User Action: Either add a query construct, or remove the query element.
- CWWBW6029W: The XML Path Language (XPath) property alias query is empty (process onEvent event number {0}, {1} correlation set, {2} property alias for the correlation property, {3} type).
- Explanation: The specified XPath query in the correlation set property is not syntactically valid.
- User Action: Either add a query construct, or remove the query element.
- CWWBW6030W: In process timeout number {1}, the XML Path Language (XPath) date or duration is not valid: {0}.
- Explanation: The specified XPath expression is not supported.
- User Action: In WebSphere Integration Developer, in the business process editor, go to the start node. Open the event handler and select the specified timeout event. In the Properties view, on the Details tab, correct the XPath expression.
- CWWBW6033W: In process timeout number {1}, the XML Path Language (XPath) date or duration is not valid because the $ notation that is used to refer to a variable in the {0} XPath expression or query is not supported.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, in the business process editor, go to the start node. Open the event handler and select the specified timeout event. In the Properties view, on the Details tab, correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBW6034W: In the {1} process variable, query property number {2} points to an XML Path Language (XPath) query ({3} property alias for the referenced correlation property) that is not valid ({4} message type). The error is: {0}.
- Explanation: The specified XPath expression is not supported.
- User Action: In WebSphere Integration Developer, in the business process editor, select the specified process variable. In the Properties view, select the Query Properties tab. In the table, select the specified query property element and click Edit. Correct the XPath expression.
- CWWBW6037W: In the {1} process variable, query property number {2} points to an XML Path Language (XPath) query ({3} property alias for the referenced correlation property) that is not valid because the $ notation that is used to refer to a variable in the {0} XPath expression or query is not supported. ({4} message type).
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, in the business process editor, select the specified process variable. In the Properties view, select the Query Properties tab. In the table, select the specified query property element and click Edit. Correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBW6038W: In the {1} process variable, query property number {2} points to the {3} inline-defined query property, which is not valid. The error is {0}
- Explanation: The specified XML Path Language (XPath) expression is not supported.
- User Action: In WebSphere Integration Developer, in the business process editor, select the specified process variable. In the Properties view, select the Query Properties tab. In the table, select the specified queryProperty element and click Edit. Correct the XPath expression.
- CWWBW6041W: In the {1} process variable, query property number {2} points to the {3} inline-defined query property, which is not valid because the $ notation that is used to refer to a variable in the {0} XPath expression or query is not supported.
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, in the business process editor, select the specified process variable. In the Properties view, select the Query Properties tab. In the table, select the specified queryProperty element and click Edit. Correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBW6042W: The XML Path Language (XPath) property alias query is not valid (process onEvent event number {1}, {2} correlation set, {3} property alias for the correlation property, {4} type). The error is {0}.
- Explanation: The specified XPath expression is not supported.
- User Action: In WebSphere Integration Developer, in the business process editor, in the tray on the right side of the process, select the specified correlation property. In the Properties view, select the appropriate row in the table and click Edit. Correct the XPath expression.
- CWWBW6045W: The {0} XML Path Language (XPath) property alias query is not valid because the $ notation that refers to a variable in it is not supported (process onEvent event number {1}, {2} correlation set, {3} property alias for the correlation property, {4} message type).
- Explanation: No additional information is available.
- User Action: In WebSphere Integration Developer, in the business process editor, in the tray on the right side of the process, select the specified correlation property. In the Properties view, correct the XPath expression without using the $ notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBW6046W: The administration task in the {0} activity is used in the microflow (not a long-running process).
- Explanation: Microflows (uninterruptible processes) must not contain asynchronous activities, such as administration tasks, human task activities, or wait activities.
- User Action: Define the process as a long-running process, or remove the asynchronous activity.
- CWWBW6047E: The value of the "Continue On Error" setting is not valid ({0} activity). Only the value "yes" or "no" is allowed.
- Explanation: No additional information is available.
- User Action: Use one of the valid values.
- CWWBW6048W: Deprecation: The {0} role defines a portType element. This use is deprecated. Use the portType attribute instead. ({1} process partnerLink, {2} partnerLinkType).
- Explanation: The portType element is deprecated.
- User Action: Use the portType attribute.
- CWWBW6049E: The {0} role defines a portType element and a portType attribute. You must use only a portType attribute. ({1} process partnerLink, {2} partnerLinkType)
- Explanation: The role uses the old and new schemas of the portType definition on a role. This is not supported.
- User Action: Use only the portType attribute.
- CWWBW6050E: The {0} element was not found (process onEvent event {1}).
- Explanation: The element that is referenced in the onEvent event is not defined in the Web Services Description Language (WSDL) interface.
- User Action: Modify the element if it is not defined correctly in the WSDL interface.
- CWWBW6051E: The onEvent element cannot specify both element and messageType attributes. Remove one of the attributes (process onEvent event {0}).
- Explanation: The onEvent element can specify either an element attribute or a messageType attribute but not both.
- User Action: Remove either the element or the messageType attribute.
- CWWBW6052W: Catch element number {2} requires a fault variable because the {0} fault has associated fault data ({1} fault handler of the activity).
- Explanation: If a fault has associated fault data it will only be caught by a fault link if this fault link specifies a matching fault name and a fault variable whose data type matches the type of the data associated with the fault.
- User Action: Ensure that the correct fault variable is set.
- CWWBW6053W: The {0} fault does not exist in the {1} operation ({2} fault handler of the activity, catch element number {3}).
- Explanation: The fault must be specified on the operation. Otherwise, the default catch-all handler is selected if it is present at run time.
- User Action: Ensure that the correct fault exists on the operation.
- CWWBW6054W: The {0} fault message type does not match the message type of the fault data of the {1} fault ({2} fault handler of the activity, catch element number {3}).
- Explanation: The fault message type must be the same as the fault data message type .
- User Action: Ensure that the fault message type is correct.
- CWWBW6300E: The {0} expression language of the condition is not supported. It must be one of {1} ({2} RepeatUntil loop activity).
- Explanation: Expressions that are specified in this expression language cannot be processed.
- User Action: Use one of the supported expression languages.
- CWWBW6301E: The condition is not valid ({0} RepeatUntil loop activity, {1} expression language).
- Explanation: The specified expression is not valid for the expression language, or it is not valid in this context. For example, if you use the built-in expression language in the RepeatUntil condition, only the values wpc:true and wpc:false are allowed.
- User Action: Check the expression and the expression language, and modify them if they are not valid.
- CWWBW6302E: The XML Path Language (XPath) condition is not syntactically valid ({1} RepeatUntil loop activity). The error is {0}.
- Explanation: No additional information is available.
- User Action: Correct the XPath RepeatUntil condition so that it is valid.
- CWWBW6303W: In the {1} RepeatUntil loop activity, the XML Path Language (XPath) condition is not valid. The error is {0}
- Explanation: The specified XPath expression is not supported.
- User Action: In WebSphere Integration Developer, in the business process editor, select the specified RepeatUntil activity. In the Properties view, on the Details tab, correct the XPath expression.
- CWWBW9000I: The validation of the {0} process component completed with no errors: {1} informational messages, {2} warnings, {3} errors.
- Explanation: This is an informational message that summarizes the validation of the specified process component model.
- User Action: No action is required.
- CWWBW9001I: The validation of the {0} process component completed with the following errors: {1} informational messages, {2} warnings, {3} errors.
- Explanation: This is an informational message that summarizes the unsuccessful process component model.
- User Action: Modify the process component model to solve the problems.
- CWWBW9002I: The validation of the {0} process component completed with the following errors: {1} informational messages, {2} warnings, {3} errors: {4}
- Explanation: This is an informational message that summarizes the unsuccessful process component model.
- User Action: Modify the process component model to solve the problems.
- CWWBW9050E: Process component validation error: ''{0}''. Error parameters: {1}.
- Explanation: This is a general-purpose message for use when the product is in service and a new error message is needed.
- User Action: Check the error message for a description of the error.
- CWWBW9051W: Process component validation warning: ''{0}''. Warning parameters: {1}.
- Explanation: This is a general-purpose message for use when the product is in service and a new warning message is needed.
- User Action: Check the warning message for a description of the warning.
- CWWBW9052I: Process component validation information: ''{0}''. Information parameters: {1}.
- Explanation: This is a general-purpose message for use when the product is in service and a new information message is needed.
- User Action: No action is required.
- CWWBW9100E: The {0} process component file contains at least one interface of the wrong type.
- Explanation: You must use only Web Services Description Language (WSDL) interfaces (port types).
- User Action: Correct the process component file so that it contains only WSDL interfaces.
- CWWBW9101E: The {1} reference in the {0} process component file does not specify an interface.
- Explanation: A reference in a process component file must always have an interface associated with it.
- User Action: Correct the process component file so that all of the references have exactly one interface.
- CWWBW9102E: The {1} reference in the {0} process component file specifies more than one interface.
- Explanation: A reference in a process component file can have only one interface associated with it.
- User Action: Correct the process component file so that all of the references have only one interface.
- CWWBW9103E: The {1} reference in the {0} process component file has at least one interface of the wrong type.
- Explanation: Use only Web Services Description Language (WSDL) interfaces (port types).
- User Action: Correct the process component file so that it contains WSDL interfaces only.
- CWWBW9104E: The {1} reference in the {0} process component file specifies an interface that is different from the one specified by the corresponding reference partner in the process implementation.
- Explanation: The process component file must contain a reference with the same name and interface as the corresponding outbound partner in the process implementation.
- User Action: Correct the process component file or the process implementation file so that both files contain the same interface for matching references to outbound partners.
- CWWBW9105E: The {1} interface in the {0} process component file does not have a corresponding interface partner in the process implementation file.
- Explanation: The process component file contains an interface with a signature that is not in the process implementation file.
- User Action: Correct the process component file or the process implementation file so that both files contain an interface and an inbound partner that match.
- CWWBW9106E: The {1} reference in the {0} process component file does not have a corresponding reference partner in the process implementation.
- Explanation: The process component file contains a reference with an interface signature that is not in the process implementation file.
- User Action: Correct the process component file or the process implementation file so that both files contain a reference and an outbound partner that match.
- CWWBW9107E: The {0} process component file does not contain an interface that corresponds to the {1} interface partner in the process implementation.
- Explanation: No additional information is available.
- User Action: Add an interface to the process component file that matches the signature of the partner.
- CWWBW9108E: The {0} process component file does not contain a reference that corresponds to the {1} reference partner in the process implementation.
- Explanation: No additional information is available.
- User Action: Add a reference to the process component file that matches the signature of the partner.
- CWWBW9200E: The {1} interface in the {0} process component file does not specify the "async" value for the preferredInteractionStyle attribute.
- Explanation: This attribute with the value "async" is mandatory for long-running processes.
- User Action: Add the preferredInteractionStyle attribute with the value "async" to the interface in the process component file.
- CWWBW9201E: The {0} process component file requires either the transaction or activity session implementation qualifier.
- Explanation: A process component file must specify whether a global transaction or an activity session is used.
- User Action: Add either the transaction or activity session implementation qualifier to the process component file. For long-running processes, only the transaction implementation qualifier is allowed.
- CWWBW9202E: The {1} interface in the {0} process component file does not specify the mandatory join transaction interface qualifier.
- Explanation: No additional information is available.
- User Action: Add the join transaction interface qualifier to the interface.
- CWWBW9203E: The {2} operation of the {1} interface in the {0} process component file does not specify the join transaction interface qualifier.
- Explanation: Process component files that run in a global transaction must specify the join transaction interface qualifier.
- User Action: Add the join transaction interface qualifier to the interface.
- CWWBW9204E: The {1} interface in the {0} process component file does not specify the join transaction interface qualifier with the value ''false''.
- Explanation: Process component files that run in a global transaction and do not specify a long-running process must contain the join transaction interface qualifier with the value "false".
- User Action: Change the value of the join transaction interface qualifier to "false".
- CWWBW9205E: The {2} operation of the {1} interface in the {0} process component file does not specify the join transaction interface qualifier with the value ''false''.
- Explanation: Process component files that run in a global transaction and do not specify a long-running process must contain the join transaction interface qualifier with the value "false".
- User Action: Change the value of the join transaction interface qualifier to "false".
- CWWBW9206E: The {1} interface in the {0} process component file does not specify the join transaction interface qualifier with the value ''true''.
- Explanation: Process component files that run in a global transaction and specify a long-running process must contain the join transaction interface qualifier with value of "true".
- User Action: Change the value of the join transaction interface qualifier to "true".
- CWWBW9207E: The {2} operation of the {1} interface in the {0} process component file does not specify the join transaction interface qualifier with the value ''true''.
- Explanation: Process component files that run in a global transaction and specify a long-running process must contain the join transaction interface qualifier with the value "true".
- User Action: Change the value of the join transaction interface qualifier to "true".
- CWWBW9208E: The {1} interface in the {0} process component file specifies the join transaction interface qualifier.
- Explanation: Process component files that run in an activity session cannot use the join transaction interface qualifier.
- User Action: Remove the join transaction interface qualifier from the interface.
- CWWBW9209E: The {2} operation of the {1} interface in the {0} process component file specifies the join transaction interface qualifier.
- Explanation: Process component files that run in an activity session cannot use the join transaction interface qualifier.
- User Action: Remove the join transaction interface qualifier from the interface.
- CWWBW9210E: The {1} reference in the {0} process component file specifies the suspend transaction reference qualifier.
- Explanation: Process component files that run in an activity session cannot use the suspend transaction reference qualifier.
- User Action: Remove the suspend transaction reference qualifier from the reference.
- CWWBW9211E: The {0} process component file does not contain the transaction implementation qualifier with the value ''global''.
- Explanation: Process component files that run in a global transaction must contain the transaction implementation qualifier with the value "global".
- User Action: Add the implementation qualifier with the value "global".
- CWWBW9212E: The {0} process component file does not contain the transaction implementation qualifier with the value ''global''.
- Explanation: Process component files that run in a global transaction must contain the transaction implementation qualifier with the value "global".
- User Action: Change the implementation qualifier so that it is set to "global".
- CWWBW9213E: The {0} process component file does not specify the transaction implementation qualifier with the value ''local'' and the local transaction boundary setting with the value ''activity session''.
- Explanation: For process component files that run in an activity session, you must set the value of the transaction implementation qualifier to "local" and the value of the local transaction boundary to "activity session".
- User Action: Add the transaction implementation qualifier with the specified settings.
- CWWBW9214E: The {0} process component file does not specify the transaction implementation qualifier with the value ''local'' and the activity session qualifier with the value ''activity session''.
- Explanation: For process component files that run in an activity session, you must set the value of the transaction implementation qualifier to "local" and the value of the local transaction boundary to "activity session".
- User Action: Change the specified implementation qualifier.
- CWWBW9215E: The {1} interface in the {0} process component file specifies the join activity session interface qualifier.
- Explanation: Process component files that specify long-running processes cannot use the join activity session interface qualifier.
- User Action: Remove the join activity session interface qualifier from the interface.
- CWWBW9216E: The {1} interface in the {0} process component file specifies the join activity session interface qualifier.
- Explanation: Process component files that run in a transaction cannot use the join activity session interface qualifier.
- User Action: Remove the join activity session interface qualifier from the interface.
- CWWBW9217E: The {1} interface in the {0} process component file does not specify the join activity session interface qualifier.
- Explanation: Process component files that run in an activity session must specify join activity session interface qualifier.
- User Action: Add the join activity session interface qualifier to the interface.
- CWWBW9218E: The {1} interface in the {0} process component file does not contain the join activity session interface qualifier with the value ''true''.
- Explanation: Process component files that run in an activity session must contain a join activity session interface qualifier with the value "true".
- User Action: Change the value of the join activity session interface qualifier to "true".
- CWWBW9219E: The {2} operation of the {1} interface in the {0} process component file specifies the join activity session interface qualifier.
- Explanation: Process component files that run in a transaction cannot use the join activity session interface qualifier.
- User Action: Remove the join activity session interface qualifier from the operation and the interface.
- CWWBW9220E: The {2} operation of the {1} interface in the {0} process component file specifies the join activity session interface qualifier.
- Explanation: Process component files that specify long-running processes cannot use the join activity session interface qualifier.
- User Action: Remove the join activity session interface qualifier from the interface.
- CWWBW9221E: The {2} operation of the {1} interface in the {0} process component file does not specify the join activity session interface qualifier.
- Explanation: Process component files that run in an activity session must specify the join activity session interface qualifier.
- User Action: Add the join activity session interface qualifier to the operation and interface.
- CWWBW9222E: The {2} operation of the {1} interface in the {0} process component file does not contain the join activity session interface qualifier with the value ''true''.
- Explanation: Process component files that run in an activity session must contain a join activity session interface qualifier with the value "true".
- User Action: Change the value of the join activity session interface qualifier to "true".
- CWWBW9223E: The {1} reference in the {0} process component file specifies the suspend activity session reference qualifier.
- Explanation: Process component files that run in a transaction cannot use the suspend activity session reference qualifier.
- User Action: Remove the suspend activity session reference qualifier from the reference.
- CWWBW9224E: The {0} process component file specifies the activity session implementation qualifier.
- Explanation: Process component files that specify long-running processes cannot use the activity session implementation qualifier.
- User Action: Remove the activity session implementation qualifier.
- CWWBW9225E: The process component file ''{0}'' specifies the ActivitySession implementation qualifier although it is not allowed in processes that run in a transaction.
- Explanation: Process component files that run in a transaction cannot use the ActivitySession implementation qualifier.
- User Action: Remove the ActivitySession implementation qualifier.
- CWWBW9226E: The {0} process component file does not specify the activity session implementation qualifier.
- Explanation: Process component files that run in an activity session must specify the activity session implementation qualifier.
- User Action: Add the activity session implementation qualifier to the interface.
- CWWBW9227E: The {0} process component file does not contain an activity session implementation qualifier with the value ''true''.
- Explanation: Process component files that run in an activity session must contain an activity session implementation qualifier with the value "true".
- User Action: Change the value of the activity session implementation qualifier to "true".
- CWWBW9228E: The interface ''{1}'' of the process component file ''{0}'' specifies the interface qualifier ''{2}'' more than once.
- Explanation: Interface qualifiers must not be specified more than once for each interface.
- User Action: Ensure that there is only one occurrence of the interface qualifier.
- CWWBW9229E: The reference ''{1}'' of the process component file ''{0}'' specifies the reference qualifier ''{2}'' more than once.
- Explanation: Reference qualifiers must not be specified more than once for each reference.
- User Action: Ensure that there is only one occurrence of the reference qualifier.
- CWWBW9230E: The process component file ''{0}'' specifies the implementation qualifier ''{1}'' more than once.
- Explanation: Implementation qualifiers must not be specified more than once.
- User Action: Ensure that there is only one occurrence of the implementation qualifier.
- CWWBW9231E: The {1} reference in the {0} process component file does not have the asynchronous invocation reference qualifier with the value ''commit''.
- Explanation: The specified reference in the task component file must contain the specified reference qualifier with the correct value.
- User Action: Add the specified reference qualifier to the reference in the process component file.
- CWWBW9232E: The reference ''{1}'' in the process component file ''{0}'' specifies a multiplicity other than ''1..1''. This is not supported for process component files.
- Explanation: Process component files allow a multiplicity of '1..1' only.
- User Action: Select a multiplicity of '1..1' for the reference.
- CWWBW9300E: The process implementation file ''{1}'' referenced by the process component file ''{0}'' was not found.
- Explanation: The process component file contains a reference to a process implementation file. This reference is present, but the referenced file cannot be found.
- User Action: Correct the process component file so it points to an existing process implementation file.
- CWWBW9301W: The reference ''{1}'' in the process component file ''{0}'' is wired to another component, but this component is ignored because the corresponding partner has a process template specified.
- Explanation: The partner in the process implementation file specifies a process template. Therefore, the specified partner is chosen during runtime and the wired component is ignored.
- User Action: Remove the wire from the indicated reference to avoid confusion for other users who read the assembly. Alternatively, if you like to explicitly wire the components, remove the process template specification from the partner in the process implementation file.
- CWWBW9302W: In the process event handler, in onEvent event number {2}, parameter number {3}, assigning the ''{0}'' xsd:anyType typed element to the ''{1}'' xsd:anySimpleType typed variable might cause a runtime error.
- Explanation: The xsd:anyType and the xsd:anySimpleType variable must match.
- User Action: Edit the types so that they match.
- CWWBW9303W: In the process event handler, in onEvent event number {2}, parameter number {3}, assigning the ''{0}'' xsd:anyType typed part to the ''{1}'' xsd:anySimpleType typed variable might cause a runtime error.
- Explanation: The part of the xsd:anyType and the variable of the xsd:anySimpleType must match.
- User Action: Edit the types so that they match.
- CWWBW9304I: The activity name ''{0}'' is used already.
- Explanation: A duplicate activity name was found.
- User Action: You may change the activity name to be unique.