WebSphere Process Server messages     Operating Systems: All supported
CWWBD0000E: The process model with name ''{0}'' and valid from date ''{1}'' already exists.
Explanation: A process model with the same name and valid from date has been deployed twice.
User Action: Change the name or valid from date, then deploy the process model again.

 

CWWBD0001W: FDML is not well-formed or is invalid: line: {0} column: {1}.
Explanation: The problem occurs during the parsing of the FDML. This indicates that the FDML document is not well-formed or is invalid.
User Action: Fix the problem within the FDML so that the document is well-formed and valid. The reason for the error will be reported by the nested message from the parser.

 

CWWBD0002E: FDML is not well-formed or is invalid: line: {0} column: {1}.
Explanation: The problem occurs during the parsing of the FDML. This indicates that the FDML document is not well-formed or is invalid.
User Action: Fix the problem within the FDML so that the document is well-formed and valid. The reason for the error will be reported by the nested message from the parser.

 

CWWBD0003W: ''{0}'' is missing implementation ''{1}''.
Explanation: This is a warning that the implementation is not specified within the scope of the FDML document. It is then necessary to deploy the missing implementation separately. If the missing implementation is not deployed before execution of the process, the process engine throws an exception during invocation.
User Action: Ensure that the implementation used by the process model is installed, or that it is part of the process archive.

 

CWWBD0004E: Activity ''{1}'' in process model ''{0}'' has no incoming control links.
Explanation: This is a warning that the specified activity will never be reached during the execution of the process.
User Action: Ensure that in the process model, a control link exists with the activity as the target.

 

CWWBD0005E: Activity ''{1}'' in process model ''{0}'' has no outgoing control links.
Explanation: This is a warning that the specified activity will not trigger any other activity because it has no outgoing control link.
User Action: Ensure that in the process model, a control link exists with the activity as the source.

 

CWWBD0006I: Terminal ''{1}'' of activity ''{2}'' in process model ''{0}'' has no incoming data link.
Explanation: This information indicates that the specified activity will not receive any data from any other activity.
User Action: No action is required.

 

CWWBD0007I: Terminal ''{1}'' of activity ''{2}'' in process model ''{0}'' has no outgoing data link.
Explanation: This information indicates that the specified activity will not route any data to any other activity.
User Action: No action is required.

 

CWWBD0008E: Terminal ''{1}'' of activity ''{2}'' in process model ''{0}'' has more than one incoming data link.
Explanation: The specified activity has more than one incoming data link.
User Action: You must use a data map to merge the data links, that is, insert a data map that joins the data from the data links.

 

CWWBD0009E: Cycle found within process model ''{0}'': ({1}).
Explanation: The graph of the process includes a cycle that can cause that the process never ends.
User Action: Remove the cycle.

 

CWWBD0010E: Source activity ''{1}'' not found in process model ''{0}''.
Explanation: A source activity specified in a control or data link cannot not be found.
User Action: Change the source activity of the control or data link or add the specified activity.

 

CWWBD0011E: Target activity ''{1}'' not found in process model ''{0}''.
Explanation: A target activity specified in a control or data link cannot be found.
User Action: Change the target activity of the control or data link or add the specified activity.

 

CWWBD0012E: Source terminal ''{1}'' not found in activity ''{2}'' and process model ''{0}''.
Explanation: An output terminal specified as source terminal of a control or data link cannot be found within the activity.
User Action: Change the source terminal of the control or data link or add the terminal to the activity.

 

CWWBD0013E: Target terminal ''{1}'' not found in activity ''{2}'' and process model ''{0}''.
Explanation: An input terminal specified as target terminal of a control or data link cannot be found within the activity.
User Action: Change the target terminal of the control or data link or add the terminal to the activity.

 

CWWBD0014W: Source terminal of activity ''{1}'' and target terminal of activity ''{2}'' in process model ''{0}'' have incompatible message types.
Explanation: The message types specified for the source and the target terminals of the named activities are incompatible. This can cause an error when the process model is run.
User Action: If the message types cannot be assigned, add a data map that assigns the data.

 

CWWBD0015W: Variable ''{1}'' is not updated in process model ''{0}''.
Explanation: There is no data map that updates the specified variable.
User Action: Ensure that the variable is set, otherwise it contains no information.

 

CWWBD0016I: Verified ''{0}'' successfully: {1} warnings, {2} errors.
Explanation: Summary of the successful verification of the process model.
User Action: No action is required.

 

CWWBD0017I: Verified ''{0}'' with failures: {1} warnings, {2} errors.
Explanation: Summary of the verification of the process model where errors were found.
User Action: Update the FDML to solve the problems and deploy again.

 

CWWBD0018I: Deployed ''{0}'' successfully.
Explanation: Summary of the successful deployment of the process model.
User Action: No action is required.

 

CWWBD0019I: Cannot deploy due to FDML verification errors.
Explanation: Deployment was canceled because verification errors were found in the FDML.
User Action: Update the FDML to solve the problems and deploy again.

 

CWWBD0020E: Cannot deploy a process model without a database connection.
Explanation: You tried to deploy an FDML persistently without having a database connection.
User Action: Make sure that you have a database connection.

 

CWWBD0021E: Cannot verify the FDML because validation is not enabled.
Explanation: You tried to deploy an FDML without XML validation but verification of the process model.
User Action: Always use XML validation.

 

CWWBD0022E: Plug-in type in ''{0}'' is missing.
Explanation: The element has no type system specified for the plug-in extensibility element.
User Action: Insert the missing type system for the plug-in.

 

CWWBD0023E: Plug-in value in ''{0}'' is missing.
Explanation: The element has no extensibility element for the plug-in specified.
User Action: Insert the missing value for the plug-in.

 

CWWBD0024E: Implementation of activity ''{0}'' is missing.
Explanation: There is a reference to an implementation that is not defined.
User Action: Insert the implementation or change the references.

 

CWWBD0025E: Subprocess definition of activity ''{0}'' is missing.
Explanation: There is a reference to a subprocess that is not defined.
User Action: Insert the subprocess or change the references.

 

CWWBD0026E: Process model ''{0}'' not found.
Explanation: There is a reference to a process model that is not defined.
User Action: Insert the process model or change the references.

 

CWWBD0027E: Element ''{0}'' not found.
Explanation: There is a reference to an element that is not defined.
User Action: Insert the element or change the references.

 

CWWBD0028E: Activity ''{0}'' not found.
Explanation: There is a reference to an activity that is not defined.
User Action: Insert the activity or change the references.

 

CWWBD0029E: Data link with {0} ''{1}'' not found.
Explanation: There is a reference to a data link that is not defined.
User Action: Insert the data link or change the references.

 

CWWBD0030E: Data map ''{0}'' not found.
Explanation: There is a reference to a data map that is not defined.
User Action: Insert the data map or change the references.

 

CWWBD0031E: Message type ''{0}'' not found.
Explanation: A message type is used but not defined in the scope of a process model.
User Action: Insert the definition of the missing message type.

 

CWWBD0032E: No input terminal found in {0} ''{1}''.
Explanation: The specified node has no input terminal defined.
User Action: Insert the input terminal on the node.

 

CWWBD0033E: No output terminal found in {0} ''{1}''.
Explanation: The specified node has no output terminal defined.
User Action: Insert the output terminal on the node.

 

CWWBD0034E: No message type found in implementation ''{0}''.
Explanation: A message type is used but not defined in the scope of the process model.
User Action: Insert the definition of the missing message type.

 

CWWBD0035E: No {0} terminal found in activity ''{1}''.
Explanation: The activity has no output or fault terminal with the specified name.
User Action: Insert the terminal on the activity or change the name of the terminal on the data link.

 

CWWBD0036E: Subprocess {0} cannot be found.
Explanation: A process model references a subprocess by name (late binding) and the name of the subprocess is unknown.
User Action: Deploy the subprocess, then try again.

 

CWWBD0037E: Exception thrown by fault terminal ''{0}'' in activity ''{1}'' cannot be caught by a fault of the process model.
Explanation: The activity has an unconnected fault terminal and the exception thrown by this terminal cannot be caught by any fault of the process.
User Action: Insert a fault terminal on the process model that catches the exception or connect the fault terminal of the activity with a different activity.

 

CWWBD0038E: Class {0} is not serializable.
Explanation: A Java message type was encountered that is not serializable. Serializable classes are required so that messages can be written to the persistent store.
User Action: Make sure that you use only serializable classes as Java message types when deploying processes.

 

CWWBD0039E: ''{1}'' from terminal ''{2}'' at activity ''{3}'' to terminal ''{4}'' at activity ''{5}'' already exists in process model ''{0}''.
Explanation: The FDML contains an element that already exists.
User Action: Make sure that an FDML element exists only once.

 

CWWBD0040E: Element ''{2}'' of type ''{1}'' already exists in process model ''{0}''.
Explanation: The FDML contains an element that already exists.
User Action: Make sure that an FDML element exists only once.

 

CWWBD0041E: Element ''{2}'' of type ''{1}'' at activity ''{3}'' already exists in process model ''{0}''.
Explanation: The FDML contains an element that already exists.
User Action: Make sure that an FDML element exists only once.

 

CWWBD0042E: Input and output message types of empty activity ''{0}'' are not the same.
Explanation: The input and output message types of an empty activity must be equal.
User Action: Make sure that the input and output message types of the empty activity are equal.

 

CWWBD0043E: Empty activity ''{0}'' defines a fault terminal.
Explanation: The definition of a fault terminal for an empty activity is not allowed.
User Action: Make sure that the empty activity has no fault terminals.

 

CWWBD0044E: User input cannot be deployed.
Explanation: An error occurred during the deployment of user input.
User Action: Check the user input.

 

CWWBD0045E: Element ''{0}'' cannot be deployed transiently.
Explanation: The element cannot be deployed transiently.
User Action: Deploy the element persistently.

 

CWWBD0046E: Event ''{1}'' in process model ''{0}'' is specified in an event map but does not exist.
Explanation: The specified event is used in an event map but does not exist.
User Action: Make sure that the event is specified within the process model.

 

CWWBD0047E: Activity ''{1}'' in process model ''{0}'' is specified as target in an event map but does not exist.
Explanation: The target activity used in the event map does not exist.
User Action: Make sure that the target activity is specified within the process model.

 

CWWBD0048E: Event ''{1}'' in process model ''{0}'' is specified as target in an event map but does not exist.
Explanation: The target event used in the event map does not exist.
User Action: Make sure that the target event is specified within the target activity.

 

CWWBD0049E: Process model ''{0}'' cannot be deployed transiently because it contains elements that require persistence.
Explanation: The process model cannot be deployed transiently.
User Action: Deploy the process model persistently.

 

CWWBD0050E: Process model ''{0}'' requests a compensation process model and a compensation sphere at the same time.
Explanation: The specified process model requests that a compensation process model is to be used for compensation but also specifies that a compensation sphere is to be set up.
User Action: Either specify a compensation process model or request a compensation sphere.

 

CWWBD0051I: Process model or implementation ''{0}'' with valid-from date ''{1}'' is redeployed.
Explanation: Informs you that the process or implementation is redeployed persistently so that it can be run interruptibly. The previous version was only deployed transiently.
User Action: No action is required.

 

CWWBD0052E: Receive events cannot have exit or loop conditions.
Explanation: There is an exit condition or a loop specified on a receive event.
User Action: Make sure that a receive event has neither an exit condition nor a loop specified.

 

CWWBD0053E: Synchronous processes cannot have receive events or person activities.
Explanation: Use of receive events or person activities in a process model means that the process model cannot run synchronously.
User Action: Make sure that the process model is not said to run synchronously.

 

CWWBD0054E: Empty activities and subprocess activities cannot expire.
Explanation: There is an empty or subprocess activity that has an expiration date.
User Action: Make sure that neither empty nor subprocess activities specify an expiration date.

 

CWWBD0055E: Data map "{1}" in process model ''{0}'' has a target activity but no target terminal.
Explanation: A target activity must also define a target terminal.
User Action: Make sure that the data map defines the target terminal on the target activity.

 

CWWBD0056I: Process model "{0}" with valid from date "{1}" was not deployed because it was not found in ibm-flow.xmi.
Explanation: There is a process model in the FAR file that is not defined in the ibm-flow.xmi file.
User Action: Make sure that all process models that are part of the enterprise application are defined in the ibm-flow.xmi file.

 

CWWBD0057E: Process model "{0}" with valid from "{1}" defined in ibm-process.xmi is not found in FAR file.
Explanation: There is a process model defined in the ibm-process.xmi file that is not in the FAR file.
User Action: Make sure that all process models that are defined in the ibm-process.xmi file are part of the enterprise application.

 

CWWBD0058E: Duplicate implementation "{0}" with valid from "{1}" in FAR file.
Explanation: There are two implementations with the same name and valid-from time in the FAR file.
User Action: Make sure that all implementations are unique by name and valid-from time.

 

CWWBD0059E: Duplicate process model "{0}" with valid from "{1}" in FAR file.
Explanation: There are two process models with the same name and valid-from time in the FAR file.
User Action: Make sure that all process models are unique by name and valid-from time.

 

CWWBD0060E: An exit condition cannot be defined for a loop or event activity.
Explanation: There is a loop or event activity that has an exit condition defined.
User Action: Make sure that no exit conditions are defined for event and loop activities.

 

CWWBD0061E: A process model defined as a non-interruptible process cannot contain event or person activities.
Explanation: A process model defined as a non-interruptible process contains event or person activities.
User Action: Make sure that the process model is defined as an interruptible process or do not use event and person activities.

 

CWWBD0062E: Control or subprocess activity "{0}" cannot expire.
Explanation: A control or subprocess activity has an expiration date defined.
User Action: Check that control and subprocess activities do not have expiration dates defined.

 

CWWBD0063E: Neither canRunSynchronous nor canRunInterrupted is set for process model "{0}".
Explanation: You have not defined whether the process model is an interruptible process or a non-interruptible process.
User Action: Make sure that every process model is defined as either an interruptible process or a non-interruptible process.

 

CWWBD0064W: Compensation for non-interruptible processes is not supported and will be ignored for process model "{0}".
Explanation: A process model that is defined as a non-interruptible process has compensation defined for it. Compensation will not be triggered for non-interruptible process.
User Action: To use compensation, make sure that the process model is defined as an interruptible process.

 

CWWBD0065E: The process model ''{0}'' can not be deployed because another process model with the same name but different target namespace already exists. The current target namespace is ''{1}''.
Explanation: There are three parameters used to decide between a new version of an already installed process model and a new process model. To install a new version of an already installed process model the name and target namespace must be the same, but the valid from different. To install a new process model the name of the process model must be different to all already deployed process models.
User Action: Depending on your scenario, change the target namespace and valid from to deploy a new version of an already installed process model or change the component name of the process component to install a new process model.

 

CWWBD0100E: Deployment error: ''{0}''. Error parameter(s): {1}.
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.

 

CWWBD0101I: Deployment information: ''{0}''. Information parameter(s): {1}.
Explanation: General purpose message used when the product is in service and a new message is needed.
User Action: No action is required.

 

CWWBD0102W: Deployment warning: ''{0}''. Warning parameter(s): {1}.
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.

 

CWWBD0103E: Validation error: ''{0}''. Error parameter(s): {1}.
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.

 

CWWBD0104I: Validation information: ''{0}''. Information parameter(s): {1}.
Explanation: General purpose message used when the product is in service and a new message is needed.
User Action: No action is required.

 

CWWBD0105W: Validation warning: ''{0}''. Warning parameter(s): {1}.
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.

 

CWWBD0200I: Deployed BPEL process model ''{0}'' successfully.
Explanation: Summary of the successful deployment of the process model.
User Action: No action is required.

 

CWWBD0201I: Cannot deploy process model ''{0}'' due to BPEL validation errors.
Explanation: Deployment was canceled because validation errors were found in the BPEL.
User Action: Update the BPEL to solve the problems and deploy again.

 

CWWBD0202I: Validated process model ''{0}'' successfully: {1} information, {2} warnings, {3} errors.
Explanation: Summary of the successful validation of the process model.
User Action: No action is required.

 

CWWBD0203I: Validated process model ''{0}'' with findings ( {1} information, {2} warnings, {3} errors ){4}
Explanation: Summary of the validation of the process model where errors were found.
User Action: Update the BPEL to solve the problems and deploy again.

 

CWWBD0204E: Activity ''{0}'' is part of a cycle found within process model ''{1}''.
Explanation: The graph of the process includes a cycle that can cause the process to never end.
User Action: Remove the cycle.

 

CWWBD0205E: Link ''{0}'' is part of a cycle found within process model ''{1}''.
Explanation: The graph of the process includes a cycle that can cause the process to never end.
User Action: Remove the cycle.

 

CWWBD0206E: Display ID ''{0}'' used more than once in BPEL file ''{1}''.
Explanation: Display IDs need to be unique in the context of a BPEL file.
User Action: Make sure that all display IDs are unique in the context of the BPEL file.

 

CWWBD0207E: Crossing link ''{0}'' found in flow ''{1}'' within process model ''{2}''.
Explanation: A link crosses the boundary of a structured activity. Crossing links are not allowed.
User Action: Remove the crossing link or define another link source or link target.

 

CWWBD0208E: Source missing for link ''{0}'' found in flow ''{1}'' within process model ''{2}''.
Explanation: Link cannot be navigated because a source is not defined.
User Action: Use the link in an activity's source element.

 

CWWBD0209E: Target missing for link ''{0}'' found in flow ''{1}'' within process model ''{2}''.
Explanation: A link without a target cannot be navigated.
User Action: Use the link in an activity's target element.

 

CWWBD0210W: Unused link ''{0}'' found in flow ''{1}'' within process model ''{2}''.
Explanation: A link is defined but never used.
User Action: Remove the link or use it in the process model.

 

CWWBD0211E: Link ''{0}'' does not link immediate children of flow ''{1}'' of process model ''{2}''.
Explanation: A link is only allowed to be used between immediate children of a flow, and not between grandchildren or great grandchildren.
User Action: Remove the link or link immediate children of the flow.

 

CWWBD0212E: Link ''{0}'' is not defined but referenced in activity ''{1}'' of process model ''{2}''.
Explanation: A link must be defined in a flow before it can be used.
User Action: Define the link.

 

CWWBD0213E: Link ''{0}'' is used outside of flow ''{1}'' of process model ''{2}''.
Explanation: A link can only be used inside a flow.
User Action: Use the link in the flow in which it is defined.

 

CWWBD0214E: Link ''{0}'' found in flow ''{1}'' has more than one source activity in process model ''{2}'': ''{3}''.
Explanation: Only one activity can be defined to be the source of a link.
User Action: Use only one activity from the list as the source of the link.

 

CWWBD0215E: Link ''{0}'' found in flow ''{1}'' has more than one target activity in process model ''{2}'': ''{3}''.
Explanation: Only one activity can be defined to be the target of a link.
User Action: Use only one activity as the target of a link.

 

CWWBD0216E: Process model ''{0}'' is abstract.
Explanation: Abstract processes are not allowed.
User Action: Declare the process as non-abstract.

 

CWWBD0217W: Resource from file ''{0}'' could not be loaded.
Explanation: The referenced resource might be needed when deploying and running the process model.
User Action: Check that the resource file is available and valid.

 

CWWBD0218E: Partner link type ''{0}'' used in partner link ''{1}'' of process model ''{2}'' not found.
Explanation: The partner link type used in the partner link have not been defined in the WSDL.
User Action: Check that the partner link type is defined and is correct in the WSDL.

 

CWWBD0219E: My role ''{0}'' used in partner link ''{1}'' of process model ''{2}'' not found.
Explanation: The role used in the partner link has not been defined in the WSDL.
User Action: Check that the role used is defined and is correct in the WSDL.

 

CWWBD0220E: Partner role ''{0}'' used in partner link ''{1}'' of process model ''{2}'' not found.
Explanation: The role used in the partner link has not been defined in the WSDL.
User Action: Check that the role used is defined and is correct in the WSDL.

 

CWWBD0221E: Neither my role nor partner role for partner link ''{0}'' of process model ''{1}'' have been defined.
Explanation: A partner link must have a definition for my role, partner role, or both.
User Action: Define my role, partner role or both for the partner link.

 

CWWBD0222E: Message type ''{0}'' used in variable ''{1}'' of process model ''{2}'' not found.
Explanation: The message type used in the variable has not been defined in the WSDL.
User Action: Check that the message type used is defined and is correct in the WSDL.

 

CWWBD0223E: No message type defined for variable ''{0}'' of process model ''{1}''.
Explanation: The message type is missing for the variable.
User Action: Define the message type for the variable.

 

CWWBD0224E: XSD type definition is not allowed as type of variable ''{0}'' of process model ''{1}''.
Explanation: An XSD type definition is not allowed as a type for a variable.
User Action: Use message type instead of type.

 

CWWBD0225E: XSD element declaration is not allowed as type of variable ''{0}'' of process model ''{1}''.
Explanation: An XSD element declaration is not allowed as a type for a variable.
User Action: Use message type instead of element.

 

CWWBD0226E: XSD type definition ''{0}'' used in variable ''{1}'' of process model ''{2}'' not found.
Explanation: The type used in the variable is not defined in the WSDL.
User Action: Check that the type used is defined and is correct in the WSDL.

 

CWWBD0227E: XSD element declaration ''{0}'' used in variable ''{1}'' of process model ''{2}'' not found.
Explanation: The element used in the variable is not defined in the WSDL.
User Action: Check that the element is defined and is correct in the WSDL.

 

CWWBD0228E: Type definition for variable ''{0}'' of process model ''{1}'' is missing.
Explanation: No type is defined for the variable.
User Action: Define the type.

 

CWWBD0229E: Type defined more than once for variable ''{0}'' of process model ''{1}''.
Explanation: The type of the variable was defined multiple times.
User Action: Define only one variable type per variable.

 

CWWBD0230E: Invoke ''{0}'' of process model ''{1}'' contains a Java script or human task (staff) activity but defines partner link ''{2}'' (''null'' expected).
Explanation: For a Java script or human task activity, the partner link must be 'null'.
User Action: Define the partner link to be 'null' for the Java script or human task activity.

 

CWWBD0231E: Invoke ''{0}'' of process model ''{1}'' contains a Java script activity but defines port type ''{2}'' (''wpc:null'' expected).
Explanation: For a Java script activity, the port type must be 'wpc:null'.
User Action: Define as the port type 'wpc:null' for the Java script activity.

 

CWWBD0232E: Invoke ''{0}'' of process model ''{1}'' contains a Java script activity but defines operation ''{2}'' (''null'' expected).
Explanation: For a Java script activity, the operation must be 'null'.
User Action: Define the operation as 'null' for the Java script activity.

 

CWWBD0233E: Partner link ''{0}'' used in activity ''{1}'' of process model ''{2}'' not found.
Explanation: The partner link used in the activity is not defined in the WSDL.
User Action: Make sure that the partner link used is correct and that it is defined in the WSDL.

 

CWWBD0234E: Port type ''{0}'' used in activity ''{1}'' of process model ''{2}'' not found.
Explanation: The port type used in the activity is not defined in the WSDL.
User Action: Make sure that the port type used is correct and that it is defined in the WSDL.

 

CWWBD0235E: Operation ''{0}'' used in activity ''{1}'' of process model ''{2}'' not found.
Explanation: The operation used in the activity is not defined in the WSDL.
User Action: Make sure that the operation used is correct and that it is defined in the WSDL.

 

CWWBD0236E: Variable ''{0}'' used in activity ''{1}'' of process model ''{2}'' not found.
Explanation: The variable used in the activity is not defined.
User Action: Check that the variable name used is correct and that it is defined.

 

CWWBD0237E: Message part ''{0}'' of variable ''{1}'' used in activity ''{2}'' of process model ''{3}'' not found.
Explanation: The message part of the variable used in the activity is not defined in the WSDL.
User Action: Check that the message part used is correct and that it is defined in the WSDL.

 

CWWBD0238E: Activity ''{0}'' of process model ''{1}'' is the target of link/links ''{2}'' but it is defined to create a new process instance or contains activities which are defined to create a new process instance.
Explanation: A pick or receive activity that is the target of one or more links cannot create a new process instance. In addition, a complex activity that contains a pick or receive activity, which is defined to create a new process instance must not have any incoming links.
User Action: Remove the incoming links or redefine the pick/receive activity so that it does not create a new process instance.

 

CWWBD0239E: The pick or receive activity ''{0}'' is defined to create a new process instance of process model ''{1}'' but is placed behind the activity/activities ''{2}''.
Explanation: A pick or receive activity that is preceded by any basic activity cannot create a new process instance.
User Action: Remove the preceding basic activities or change the pick/receive activity so that it does not create a new process instance.

 

CWWBD0240E: Process model ''{0}'' is not startable. No pick or receive activity was found that creates a new process instance and has no incoming links or preceding basic activities.
Explanation: A process is only startable when a pick 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: Make sure that all pick and receive activities are defined correctly or add a pick or receive activity which is able to create a new process instance.

 

CWWBD0241W: The potential owner role is not set in the human task (staff) properties of the {0} activity in the {1} process model. The Everybody role will be used by default.
Explanation: The specified activity requires a potential owner.
User Action: Define a potential owner for the activity.

 

CWWBD0242E: The mandatory parameter ''{0}'' for the client definition ''{1}'' has not been set in the client properties of the activity ''{2}'' in the process model ''{3}''.
Explanation: The client definition requires the parameter to be set.
User Action: Define the parameter for the client definition of the activity.

 

CWWBD0243E: The mandatory parameter ''{0}'' for the client definition ''{1}'' has not been set in the client properties of the process model ''{2}''.
Explanation: The client definition requires the parameter to be set.
User Action: Define the parameter for the client definition of the process model.

 

CWWBD0244E: The {0} mandatory parameter for the {1} verb definition ({2} role) is not set in the human task (staff) properties of the {3} activity in the {4} process model.
Explanation: The specified verb definition requires that the parameter be set.
User Action: Define the parameter for the verb definition of the role in the activity.

 

CWWBD0245E: The {0} mandatory parameter for the {1} verb definition ({2} role) is not set in the human task (staff) properties of the {3} process model.
Explanation: The specified verb definition requires that the parameter be set.
User Action: Define the parameter for the verb definition of the role.

 

CWWBD0246E: The parameter ''{0}'' for the client definition ''{1}'' has an invalid value in the client properties of the activity ''{2}'' in the process model ''{3}''. The value is not of type ''{4}''.
Explanation: The value of the parameter must match the defined data type.
User Action: Change the value of the parameter to match the data type.

 

CWWBD0247E: The parameter ''{0}'' for the client definition ''{1}'' has an invalid value in the client properties of the process model ''{2}''. The value is not of type ''{3}''.
Explanation: The value of the parameter must match the defined data type.
User Action: Change the value of the parameter to match the data type.

 

CWWBD0248E: The {0} parameter for the {1} verb definition ({2} role)has a value in the human task (staff) properties of the {3} activity of the {4} process model that is not valid. The value is not of {5} type.
Explanation: The value of the specified parameter must match the defined data type.
User Action: Change the value of the parameter to match the data type.

 

CWWBD0249E: The {0} parameter for the {1} ({2} role) verb definition has a value in the human task (staff) properties of the {3} process model that is not valid. The value is not of the {4} type.
Explanation: The value of the specified parameter must match the defined data type.
User Action: Change the value of the parameter to match the data type.

 

CWWBD0250E: Long-running subprocess ''{0}'' must not have basic activity ''{1}'' after reply activity ''{2}''.
Explanation: Basic activities after a reply activity are not allowed in long-running subprocesses.
User Action: Remove the basic activity or move it to before the reply activity.

 

CWWBD0251E: Non-interruptible process ''{0}'' must not contain asynchronous activity ''{1}''.
Explanation: Microflows must not contain asynchronous activities like human task, wait, and so on.
User Action: Define the process as a long running process or remove the asynchronous activity.

 

CWWBD0252E: Non-interruptible process ''{0}'' must not contain more than one pick or receive activity: ''{1}''.
Explanation: Microflows can only have one start point.
User Action: Either define only one pick/receive activity or define the process as long running.

 

CWWBD0253E: Non-interruptible process ''{0}'' contains pick activity ''{1}'' with one or more on alarm elements.
Explanation: Picks in microflows are not allowed to have any alarm elements.
User Action: Remove the on alarm elements or define the process as long running.

 

CWWBD0254E: One-way operation triggered process ''{0}'' contains reply activity ''{1}''.
Explanation: A process that is triggered by a one-way operation invocation, must not have a reply activity.
User Action: Remove the reply activity.

 

CWWBD0255E: Compensation handlers defined in process model ''{0}'' are not allowed.
Explanation: Compensation handlers are currently not allowed.
User Action: Remove the compensation handlers.

 

CWWBD0256E: Event handlers defined in process model ''{0}'' are not allowed.
Explanation: Event handlers are currently not allowed.
User Action: Remove the event handlers.

 

CWWBD0257E: Compensate activities used in process model ''{0}'' are not allowed.
Explanation: Compensate activities are currently not allowed.
User Action: Remove the compensate activities.

 

CWWBD0258E: A fault handler for invoke activity ''{0}'' found in process model ''{1}'' is not allowed.
Explanation: Fault handlers for invoke activities are currently not allowed.
User Action: Remove the fault handler.

 

CWWBD0259E: Non-supported scope variables are defined in scope ''{0}'' of process model ''{1}''.
Explanation: Scope variables are currently not allowed.
User Action: Remove the scope variables.

 

CWWBD0260E: Assign activity ''{0}'' is a not allowed type of assign found in process model ''{1}''.
Explanation: Only specific types of assign activities are allowed.
User Action: Use another type of assign or remove the assign activity.

 

CWWBD0261W: Variable ''{0}'' used in script activity ''{1}'' of process model ''{2}'' is not needed.
Explanation: The variable used in the script activity will be ignored.
User Action: Remove the variable attribute.

 

CWWBD0262E: Mandatory variable for activity ''{0}'' of process model ''{1}'' is missing.
Explanation: A mandatory variable for the activity is not defined.
User Action: Define the mandatory variable.

 

CWWBD0263E: A mandatory input variable for activity ''{0}'' of process model ''{1}'' is missing.
Explanation: A mandatory input variable for the activity is not defined. For human task (staff) and invoke activities the input variable is mandatory.
User Action: Define the mandatory input variable.

 

CWWBD0264E: A mandatory output variable for activity ''{0}'' of process model ''{1}'' is missing.
Explanation: A mandatory output variable for the activity is not defined. For human task (staff) activities and synchronous invoke activities the output variable is mandatory.
User Action: Define the mandatory output variable.

 

CWWBD0265E: Activity ''{0}'' of process model ''{1}'' invokes one-way operation ''{2}'' but defines output variable ''{3}''.
Explanation: A one-way operation does not have a return value.
User Action: Use a request-response operation or do not define an output variable.

 

CWWBD0266E: Undo action is not allowed for the activity ''{0}'' of process model ''{1}''.
Explanation: Undo actions are only allowed for invoke activities, but not for script or human task (staff) activities.
User Action: Remove the undo action from the activity.

 

CWWBD0267E: Syntactical error found in BPEL file ''{0}'' (row: {1}, column: {2}). Detail message: {3}
Explanation: The BPEL file does not validate against the BPEL+ XML schema.
User Action: Ensure the syntactical correctness of the BPEL file.

 

CWWBD0268W: Syntactical warning found in BPEL file ''{0}'' (row: {1}, column: {2}). Detail message: {3}
Explanation: The BPEL file validates with warnings against the BPEL+ XML schema.
User Action: Ensure the syntactical correctness of the BPEL file.

 

CWWBD0269E: Cannot load and validate BPEL resource ''{0}''.
Explanation: Validation was canceled because of invalid BPEL resource.
User Action: Update the BPEL resource to solve the problems and deploy again.

 

CWWBD0270E: The verb ''{0}'' of role ''{1}'' is not defined in verb set file.
Explanation: The verb must be defined in verb set file.
User Action: Use a verb which is defined in verb set file.

 

CWWBD0271E: The parameter ''{0}'' of the verb definition ''{1}'' (Role: ''{2}'') is not defined in verb set file.
Explanation: The named parameter is not defined in the verb set file.
User Action: Remove value of named parameter and use another parameter from parameter table.

 

CWWBD0272W: Settings for role ''{0}'' found for process model ''{1}''.
Explanation: The role cannot be defined for the process.
User Action: Use text editor to remove named role settings from process.

 

CWWBD0273W: Settings for role ''{0}'' found for activity ''{1}''.
Explanation: The role cannot be defined for the activity.
User Action: Use a text editor to remove named role settings from the activity.

 

CWWBD0274W: Not equal message type of variable ''{0}'' and input element of operation ''{1}'' found in activity ''{2}'' of process model ''{3}''.
Explanation: The message type of the variable and the input element of the operation must be the same.
User Action: Ensure they both have the same message type.

 

CWWBD0275W: Not equal message type of variable ''{0}'' and output element of operation ''{1}'' found in activity ''{2}'' of process model ''{3}''.
Explanation: The message type of the variable and the output element of the operation must be the same.
User Action: Ensure they both have the same message type.

 

CWWBD0276E: Pick or receive activities ''{0}'' are defined to create a process instance of process model ''{1}'' but a different correlation set is specified.
Explanation: Pick/receive activities which are defined to create a process instance must use the same correlation set.
User Action: Ensure that all pick/receive activities with attribute createInstance set to 'yes' use the same correlation set.

 

CWWBD0277E: The pick or receive activity ''{0}'' of process model ''{1}'' must define a correlation set because more than one pick/receive activity is contained in the process.
Explanation: If more than one pick or receive activity is used in a process model all pick/receive activities must have set a correlation set so that they correlate with the process instance.
User Action: Set for each pick/receive activity a correlation set.

 

CWWBD0278E: Process model ''{0}'' does not support compensation but defines a compensation pair at invoke activity ''{1}''.
Explanation: The process model does not support compensation but an invoke activity with undo was found (compensation pair).
User Action: Activate compensation for the process or remove the undo action from the invoke activity.

 

CWWBD0279W: Non-interruptible process ''{0}'' defines autonomy. Setting will be ignored.
Explanation: For a non-interruptible process, the autonomy is derived from its invocation circumstances.
User Action: No action is required.

 

CWWBD0280E: Non-interruptible process ''{0}'' contains an undo action in invoke activity ''{1}'' for which the ''compensation is transacted'' setting is activated.
Explanation: For microflows, undo actions with the setting 'compensation is transacted' are not allowed.
User Action: Deactivate the 'compensation is transacted' setting or define the process as long running.

 

CWWBD0281E: Fault variable ''{0}'' of process model ''{1}'' used multiple times.
Explanation: Fault variables should only be used in the catch clause.
User Action: Use the variable only in the catch clause.

 

CWWBD0282E: Element ''{0}'' is not allowed in activity ''{1}'' of process model ''{2}''.
Explanation: The given element is not allowed in this type of activity.
User Action: Remove the element from the activity.

 

CWWBD0283E: Attribute ''{0}'' is not allowed in activity ''{1}'' of process model ''{2}''.
Explanation: The given attribute is not allowed in this type of activity.
User Action: Remove the element from the activity.

 

CWWBD0284E: Pick activity ''{0}'' is defined to create a new process instance of process model ''{1}'' but has alarms.
Explanation: No alarms are allowed if the pick activity is defined to create a new process instance.
User Action: Remove the alarms or redefine the pick activity so that it does not create a new process instance.

 

CWWBD0285W: The pick or receive activity ''{0}'' is defined to create a new process instance of process model ''{1}'' and is contained in the while activity ''{2}''. If the condition of the while activity is false when it is evaluated for the first time, the process will not run correctly.
Explanation: If the condition of the while activity does not hold true when it is evaluated the first time, the pick/receive activity can not be navigated. The process will not run correctly in this case.
User Action: Place the pick/receive activity outside of the while activity.

 

CWWBD0286E: The pick or receive activity ''{0}'' is defined to create a new process instance of process model ''{1}'', but is contained in a catch, catch all, on message, on alarm, compensation handler, case or otherwise element.
Explanation: Activities which are defined to create a new process instance are not reachable in catch, catch all, on message, on alarm, compensation handler, case and otherwise elements when starting a new process instance.
User Action: Move the pick or receive activity to a reachable position, or change the pick/receive activity so that it does not create a new process instance.

 

CWWBD0287E: Flow ''{0}'' of process model ''{1}'' contains one or more process starting activities, but it also contains activity ''{2}'' which cannot start the process.
Explanation: A process starting activity can be a pick or receive activity that is defined to create a new process instance or it can be a complex activity that contains a pick or receive activity which is defined to create a new process instance. If a flow contains at least one process starting activity, all activities with no incoming links must be process starting activities.
User Action: Only use process starting activities as starting points in the flow or remove the process starting activities from the flow.

 

CWWBD0288E: Correlation set ''{0}'' used in activity ''{1}'' of process model ''{2}'' was not found.
Explanation: The correlation set used in the activity has not been defined.
User Action: Either define the correlation set or do not use it in the activity.

 

CWWBD0289E: Wrong correlation set or sets used in pick/receive activity ''{0}'' of process model ''{1}''. Expected correlation set/sets as used in activity ''{2}'': ''{3}''.
Explanation: All pick or receive activities that are defined to create a new process instance must use the same correlation set or sets.
User Action: Ensure all receive and pick activities that are defined to create a new process instance use the same correlation set or sets.

 

CWWBD0290E: Link ''{0}'' is a parallel link to link ''{1}''. Both links are linking activity ''{2}'' and activity ''{3}'' of process model ''{4}''.
Explanation: Parallel links are links which connect the same activities. Parallel links are not allowed.
User Action: Remove one of the two parallel links.

 

CWWBD0291E: The combination of autonomy and compensation sphere in process model ''{0}'' is not allowed.
Explanation: Valid combinations are: autonomy = 'peer' -> compensation sphere = 'requires new' or 'not supported', autonomy = 'child' -> compensation sphere = 'required' or 'supports'.
User Action: Use a valid combination.

 

CWWBD0292E: Fault ''{0}'' used in activity ''{1}'' of process model ''{2}'' was not found.
Explanation: The fault used in the activity is not defined.
User Action: Check that the fault name used is correct and that it is defined.

 

CWWBD0293E: Process or activity ''{0}'' of process model ''{1}'' contains an empty fault handler.
Explanation: A fault handler must have at least one catch element or a catchAll element.
User Action: Either define a catch or catchAll element, or remove the fault handler.

 

CWWBD0294E: Process or activity ''{0}'' of process model ''{1}'' contains a catch element without fault name and fault variable.
Explanation: For a catch element either the fault name, fault variable or both must be set.
User Action: Define a fault name or a fault variable or remove the catch element.

 

CWWBD0295W: Long-running subprocess ''{0}'' contains reply activity ''{1}'' which is contained in the while activity ''{2}''. If the condition of the while activity evaluates to true after the reply has been navigated, the process will not run correctly.
Explanation: Long-running subprocesses must not have a basic activity after the reply activity. If the condition of the while activity is true after the reply activity has been navigated, there will be a basic activity after the reply activity. In this case, the process will not run correctly.
User Action: Move the reply activity outside the while activity.

 

CWWBD0296I: Expiration is set for activity ''{0}'' of process model ''{1}''. It is recommended to set an appropriate timeout fault handler.
Explanation: When the activity expires a timeout fault handler will be thrown. To be able to handle this, it is recommended to set an appropriate timeout fault handler.
User Action: It is recommended to set an appropriate timeout fault handler.

 

CWWBD0297E: Property ''{0}'' not found referenced in correlation set ''{1}'' of process model ''{2}''.
Explanation: The property used must be defined.
User Action: Either define the property, or do not reference it in the correlation set.

 

CWWBD0298E: No matching property alias definition found for property ''{0}'' and message ''{1}'' - correlation set ''{2}'', activity ''{3}'', process model ''{4}''.
Explanation: A property alias is needed to map the parts of a message to the correlation properties.
User Action: Define the property alias.

 

CWWBD0299E: Part ''{0}'' is not an XML Schema simple type used in the property alias defined for property ''{1}'' and message ''{2}'' - correlation set ''{3}'', activity ''{4}'', process model ''{5}''.
Explanation: The selected part of the message is not an XML Schema simple type. Other types are not allowed.
User Action: Select an XML Schema simple type part.

 

CWWBD0300E: Type mismatch found between part ''{0}'' of message ''{1}'' and property ''{2}'' - correlation set ''{3}'', activity ''{4}'', process model ''{5}''.
Explanation: The selected part of the message in the property alias is not of the same type as the property.
User Action: Select a part that is of the same XML Schema simple type as the property.

 

CWWBD0301E: Not allowed type ''{0}'' used in property ''{1}'' referenced in correlation set ''{2}'' of process model ''{3}''.
Explanation: The type used in the property of the correlation set is not allowed. Allowed types are all XML Schema simple types except for 'xsd:integer'.
User Action: Select an allowed XML Schema simple type.

 

CWWBD0302E: Part ''{0}'' not found in message ''{1}'' referenced in property alias for property ''{2}'' - correlation set ''{3}'', activity ''{4}'', process model ''{5}''.
Explanation: The part used must be defined for the message.
User Action: Define the part or use another existing part in the property alias.

 

CWWBD0303E: Multiple property alias definitions found for property ''{0}'' and message ''{1}'' - correlation set ''{2}'', activity ''{3}'', process model ''{4}''.
Explanation: Every property-message pair can only have one property alias definition. If more than one part from a message is needed as a property, one property per part must be created.
User Action: Ensure only one property alias is available for the property-message pair. If needed, create new properties and property alias definitions for further parts of the same message.

 

CWWBD0304I: Correlation set ''{0}'' is defined, but not used in process model ''{1}''.
Explanation: An unused correlation set was found in the process model.
User Action: It is recommended to either use the correlation set in an activity, or to remove it.

 

CWWBD0305E: Correlation set ''{0}'' is used, but never initiated in process model ''{1}''.
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.

 

CWWBD0306E: Properties missing for correlation set ''{0}'' of process model ''{1}''.
Explanation: At least one property must be used in a correlation set.
User Action: In the correlation set, use an existing property or create a new one.

 

CWWBD0307E: Aggregate message variable ''{0}'' used in ''{1}'' of process model ''{2}''.
Explanation: Aggregate message variables can only be used as an input variable in invoke/transform activities and in Java snippets.
User Action: Use another variable in this activity/process model.

 

CWWBD0308E: Not allowed type of literal ''{0}:{1}'' used in activity ''{2}'' of process model ''{3}''.
Explanation: This type of literal is not supported.
User Action: Use another literal type.

 

CWWBD0309E: No literal value defined in activity ''{0}'' of process model ''{1}''.
Explanation: A definition of a literal value is expected in the given activity.
User Action: Define a literal value of the selected type.

 

CWWBD0310E: Not equal literal type in from element and part type in to element used in activity ''{0}'' of process model ''{1}''.
Explanation: The literal type and part type must be the same.
User Action: Select another literal type or another part.

 

CWWBD0311E: Literal value is not of type ''{0}'' found in activity ''{1}'' of process model ''{2}''.
Explanation: The literal value must be of the type specified in the given activity.
User Action: Select another literal type or ensure the literal value is of the expected type.

 

CWWBD0312E: My role missing for partner link ''{0}'' used in activity ''{1}'' of process model ''{2}''.
Explanation: A my role is expected for the partner link but none was found.
User Action: Define a my role for the partner link or select another partner link.

 

CWWBD0313E: Partner role missing for partner link ''{0}'' used in activity ''{1}'' of process model ''{2}''.
Explanation: A partner role is expected for the given partner link but none was found.
User Action: Define a partner role for the partner link or select another partner link.

 

CWWBD0314E: Not equal port types of partner link ''{0}'' and partner link ''{1}'' used in activity ''{2}'' of process model ''{3}''.
Explanation: The port type of the two partner links must be the same.
User Action: Change the port type of one of the partner links, or use a different partner link.

 

CWWBD0315E: Not equal message type of variable ''{0}'' and variable ''{1}'' used in activity ''{2}'' of process model ''{3}''.
Explanation: The message type of the two variables must be the same.
User Action: Change the message type of one of the variables, or use a different variable.

 

CWWBD0316E: Not equal part type of part ''{0}'' and part ''{1}'' used in activity ''{2}'' of process model ''{3}''.
Explanation: The type of the two parts must be the same.
User Action: Change the type of one of the parts, or use a different part.

 

CWWBD0317E: Expiration is not allowed for activity ''{0}'' of process model ''{1}''.
Explanation: For the given activity, an expiration element is not allowed.
User Action: Remove the expiration element.

 

CWWBD0318E: Not allowed XPath expression used in activity ''{0}'' of process model ''{1}''.
Explanation: XPath expressions are not allowed for this activity.
User Action: Remove the XPath expression and use the designated substitution.

 

CWWBD0319E: No reply activity found matching pick/receive activity ''{0}'' of process model ''{1}''.
Explanation: For each two-way operation pick/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 given pick/receive activity.

 

CWWBD0320E: No pick/receive activity found matching reply activity ''{0}'' of process model ''{1}''.
Explanation: For each two-way operation reply activity the process must contain at least one pick/receive activity with the same port type and operation.
User Action: Add a pick/receive activity to the process with the same port type and operation type as the reply activity.

 

CWWBD0321E: Process model ''{0}'' must implement operation ''{1}'' of port type ''{2}''.
Explanation: The process model currently implements one or more operations of the given port type, but not the given operation.
User Action: Either add a pick/receive activity with the given port type and operation to the process or remove this operation from the port type.

 

CWWBD0322E: Compensation sphere setting for process model ''{0}'' is not valid in this context. For microflows only ''required'' or ''supports'' is allowed.
Explanation: For microflows only 'required' or 'supports' is allowed.
User Action: Use one of the allowed values.

 

CWWBD0323E: Long-running subprocess ''{0}'' contains reply activity ''{1}'' which is the source of the following links: ''{2}''. Reply activities of long-running subprocesses must not be the source of links.
Explanation: Reply activities belonging to long-running subprocesses (autonomy is set to 'child') must not be the source of links.
User Action: Make sure that the reply activity does not have source links.

 

CWWBD0324E: Not allowed part type ''{0}:{1}'' used in variable ''{2}'' of process model ''{3}''.
Explanation: The given part type is not allowed. For example 'xsd:integer' is not allowed. Use 'xsd:int' instead.
User Action: Use a different part type.

 

CWWBD0325E: Variable ''{0}'' of process model ''{1}'' is a BPEL extensions variable, which are not allowed.
Explanation: BPEL extensions variables are not allowed.
User Action: Use a BPEL variable instead.

 

CWWBD0326E: Variable ''{0}'' of process model ''{1}'' is defined multiple times.
Explanation: Variable names must be unique.
User Action: Use a different variable name.

 

CWWBD0327E: Required input element is missing in operation ''{0}'' used in activity ''{1}'' of process model ''{2}''.
Explanation: Operations used in this kind of activity must have an input element.
User Action: Define an input element or use a different operation.

 

CWWBD0328E: Required output element is missing in operation ''{0}'' used in activity ''{1}'' of process model ''{2}''.
Explanation: Operations used in this kind of activity must have an output element.
User Action: Define an output element or use a different operation.

 

CWWBD0329E: Required message not set in input/output/fault element of operation ''{0}''. This operation is used in activity ''{1}'' of process model ''{2}''.
Explanation: The message must be set when the operation is used in this kind of activity.
User Action: Set the message or use a different operation.

 

CWWBD0330E: Message ''{0}'' is not defined, but it is used in operation ''{1}''. This operation is used in activity ''{2}'' of process model ''{3}''.
Explanation: The message must be defined when the operation is used in this kind of activity.
User Action: Set the message or use a different operation.

 

CWWBD0331E: No port type defined for activity ''{0}'' of process model ''{1}''.
Explanation: A port type is needed for this activity.
User Action: Specify the port type.

 

CWWBD0332E: No operation is defined for activity ''{0}'' of process model ''{1}''.
Explanation: An operation is needed for this activity.
User Action: Specify the operation.

 

CWWBD0333E: The deployment of human task (staff) activity ''{0}'' failed with exception: ''{1}''.
Explanation: The human task (staff) declaration of the specified activity is not valid.
User Action: Fix the human task (staff) declaration on the specified activity, as described in the exception text.

 

CWWBD0334E: The deployment of human task (staff) on process ''{0}'' failed with exception: ''{1}''.
Explanation: The human task (staff) declaration of the specified process is not valid.
User Action: Fix the human task (staff) declaration on the specified process, as described in the exception text.

 

CWWBD0335W: Not equal message type of variable ''{0}'' and fault ''{1}'' of operation ''{2}'' found in activity ''{3}'' of process model ''{4}''.
Explanation: The message type of the variable and the fault of the operation must be the same.
User Action: Ensure the message type is the same.

 

CWWBD0336E: Operation ''{0}'' of port type ''{1}'' is implemented multiple times within pick activity ''{2}'' of process model ''{3}''.
Explanation: An operation can only be implemented once in a pick activity.
User Action: Ensure only one onMessage element of the pick activity implements this operation.

 

CWWBD0337E: The graphical process model plug-in ''{0}'' tried to create a duplicate entry for process ''{1}'', source ''{2}'', and kind ''{3}''.
Explanation: The plug-in tried to create more than one entry for the same process, source, and kind.
User Action: Ensure that all registered graphical process model plug-ins do not create more than one entry for the same process, source, and kind.

 

CWWBD0338E: The compilation of the Java code for the BPEL file ''{0}'' failed. The Java compiler produced the following output: ''{1}''
Explanation: Two Java classes are generated for embedded Java code in business processes. The compilation of these classes failed.
User Action: Check the compiler output and correct the Java code in the BPEL file.

 

CWWBD0339E: Cannot delete a process template that was not created with the createProcessTemplate API.
Explanation: You cannot delete process templates that were not created with the createProcessTemplate API.
User Action: Ensure that the process template ID belongs to a process template that was created with the createProcessTemplate API.

 

CWWBD0340E: Cannot generate an SVG representation for the BPEL process.
Explanation: Cannot generate an SVG representation for the BPEL process.
User Action: Ensure that the BPEL file is correct.

 

CWWBD0341E: Cannot uninstall an enterprise application that contains dynamically installed process templates.
Explanation: You cannot uninstall an enterprise application that contains dynamically installed process templates because they cannot be stopped using the administrative console and they can still have process instances that are running.
User Action: Ensure that all of the dynamically installed process templates are deleted before uninstalling the enterprise application to which they belong.

 

CWWBD0342E: The application ''{0}'' does not contain a component with the name ''{1}''.
Explanation: The component name used for the dynamic installation of a process template does not exist in the specified enterprise application.
User Action: Ensure that the component specified for the dynamic installation of a process template exists in the specified enterprise application.

 

CWWBD0343E: The process template ''{0}'' does not have a service with the name ''{1}''.
Explanation: A service with the specified name cannot be found in the context of the process template.
User Action: Ensure that the service is present in the specified process template.

 

CWWBD0344E: The process template ''{0}'' does not have a partner link with the name ''{1}''.
Explanation: A partner link with the specified name cannot be found in the context of the process template.
User Action: Ensure that the partner link is present in the specified process template.

 

CWWBD0451E: A people (staff) query (sub-) element with the name ''{0}'' was found ''{1}'' times. The expected maximum is ''{2}'' times.
Explanation: A referenced people (staff) query element (or sub-element) was found too many times.
User Action: Adjust the element count to conform to the maximum that is allowed.

 

CWWBD0901E: Generator usage: Mandatory parameter ''{0}'' was not specified.
Explanation: You did not specify a mandatory parameter.
User Action: Specify the parameter on the command line.

 

CWWBD0902E: Generator usage: File or directory ''{0}'' does not exist or cannot be read.
Explanation: You have specified a file as parameter that cannot be found or read.
User Action: Check the input parameters for the code generator.

 

CWWBD0904E: Generator error: ''{0}''. Error parameters: {1}.
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.

 

CWWBD0905I: Generator information: ''{0}''. Information parameters: {1}.
Explanation: General purpose message used when the product is in service and a new message is needed.
User Action: No action is required.

 

CWWBD0906W: Generator warning: ''{0}''. Warning parameters: {1}.
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.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009