- CWWBM0000E: The conversion of the WebSphere MQ Workflow XML message ''{0}'' to a Service Data Object (SDO) failed. The contents of the ''{1}'' XML tag are not valid.
- Explanation: The contents of the XML tag in the MQ Workflow message caused the conversion to an SDO to fail.
- User Action: Check that the contents of the tag are valid. Also check that the tag has an equivalent member in the SDO.
- CWWBM0001E: Missing FDL input file parameter with option "{0}".
- Explanation: An FDL file name was not specified as an input parameter.
- User Action: Check the parameters given for the FDL to BPEL converter.
- CWWBM0002E: FDL input file "{0}" was not found.
- Explanation: The specified file could not be opened.
- User Action: Specify a valid file name, and check the access authorizations.
- CWWBM0003E: Cannot generate a valid WebSphere MQ Workflow XML message. The MessageType, ProcTemplName, and ActImplCorrelID data members are not set correctly.
- Explanation: The MessageContext data members MessageType, ProcTemplName and ActImplCorrelID are all null, or the MessageType is null but both ProcTemplName and ActImplCorrelID are set. Therefore the kind of WebSphere MQ Workflow XML message that is to be generated cannot be determined.
- User Action: Check that the data member MessageType of the MessageContext is set and one of the ProcTemplName, and ActImplCorrelID data members are set correctly in the Service Data Object (SDO).
- CWWBM0004E: Cannot generate a valid WebSphere MQ Workflow XML message ''{0}''. The parameter ''{1}'' is null or empty.
- Explanation: During the conversion from a WebSphere MQ Workflow XML message to an SDO, or vice versa, a required data member was missing from the SDO, or the data member is empty.
- User Action: Check the parameter ''{1}'' for the data member ''{0}'' and ensure that its definition conforms to the WebSphere MQ Workflow data structure definition.
- CWWBM0004I: Help:\n \t FDL2BPEL Converter, a tool to convert files in FDL (Flow Definition Language)\n \t to BPEL (Business Process Execution Language).\n \n \n \t Usage: FDL2BPELConverter <options>\n \t Options can be general options and optimization options:\n \n \n \n \t 1. General options\n \t ==================\n \n \t -h, -? Print this description\n \n \t -i <file name>\n \t Name of the FDL input file.\n \n \t -od <directory name>\n \t As output, the following files are generated:\n \t 1. An XSD (XML schema definition) file\n \t is generated with the same name as the FDL input file\n \t but with ".xsd" as extension.\n \t 2. A WSDL (Web Services Definition Language) file\n \t is generated with the same name as the FDL input file\n \t but with ".wsdl" as extension.\n \t 3. For each FDL process definition, a BPEL file is generated\n \t with the process name as the file name appended with\n \t ".bpel" as extension.\n \t 4. For each FDL process definition, a BPELEX file is generated\n \t with the process name as the file name appended with\n \t ".bpelex" as extension.\n \t 5. For each FDL process definition, a TEL file is generated\n \t with the process name as the file name appended with\n \t "_ATASK_PROC" as suffix and ".itel" as extension.\n \t 6. For each FDL process definition, a TEL file is generated\n \t with the process name as the file name appended with\n \t "_ATASK_ACT" as suffix and ".itel" as extension.\n \t 7. For each FDL program activity that translates to a BPEL\n \t human task (staff) activity, a TEL file is generated with\n \t a name derived from the activity name (using the process name\n \t as a prefix) and ".itel" as extension.\n \t 8. For each FDL activity another TEL file is generated with\n \t a name derived from the activity name (using the process name\n \t as a prefix and "_ATASK_ACT" as suffix) and ".itel" as extension.\n \t 9. For each FDL process definition, an SCA component file is\n \t generated with the process name as the file name appended\n \t with ".component" as extension.\n \t 10. For each FDL user-defined program execution server (UPES)\n \t definition that is referenced to in an FDL program activity,\n \t such that it translates to a "Service invocation activity",\n \t an SCA import file is generated with the server name as the\n \t file name appended with ".import" as extension.\n \t 11. For each FDL data structure that is output of an FDL program\n \t activity that translates to a "Service invocation activity" (UPES\n \t invocation), a Java file is generated with a name formatted as\n \t <FDL data structure name>_UPES_OUT_MSG_DataBindingImpl.java.\n \t 12. For each FDL process definition, a MON file is generated\n \t with the process name as the file name appended with\n \t "_bpel as suffix and ".mon" as extension.\n \t If this parameter is not specified, then the directory location of\n \t the input file is also used for the output files.\n \n \t -fc Treat name conflicts as errors.\n \t Due to different syntax rules, the FDL2BPEL converter might\n \t change names. This can lead to different FDL names being\n \t converted to the same BPEL name. The default behavior is that\n \t the FDL2BPEL converter appends suffixes to avoid this situation.\n \t If you are using the "-fc" option, the FDL2BPEL converter flags\n \t the name clashes as errors instead of appending suffixes.\n \t Use this option if you are interested in the interoperability\n \t between WebSphere MQ Workflow and WebSphere Process Server.\n \n \t -pi Initialize predefined data members _ACTIVITY, _PROCESS, and _PROCESS_MODEL.\n \t Note that you must not select option "-pn" at the same time.\n \n \t -pn Do not create predefined data members in BPEL. In WebSphere MQ Workflow,\n \t predefined data members always exist for data containers.\n \t Provided that your process does not use predefined data members, you can\n \t select this option in order to avoid unnecessary overhead in the migrated\n \t process model.\n \t Note that you must not select option "-pi" at the same time.\n \n \t -tx <namespace URI>\n \t Set this option if you need a special target namespace URI\n \t for the generated XML schema files.\n \t The default value is "{2}".\n \n \t -tw <namespace URI>\n \t Set this option if you need a special target namespace URI\n \t for the generated WSDL files.\n \t The default value is "{1}".\n \n \t -tb <namespace URI>\n \t Set this option if you need a special target namespace URI\n \t for the generated BPEL files.\n \t The default value is "{0}".\n \n \n \n \t 2. Optimization options\n \t =======================\n \n \t Business models that have been migrated without any optimization have a very similar\n \t structure to the original business model. This makes it easy to become familiar with\n \t the new appearance. Optimization can help you to reduce unnecessary structural\n \t complexity and to improve the runtime performance.\n \n \t -opt Optimize the migrated business process.\n \t The option "-opt" is equivalent to setting the three options\n \t "-mj", "-es", and "-ev".\n \t If option -opt is used then the tool applies the following\n \t optimization strategies:\n \n \t -mj Merge Java snippets.\n \t The option "-mj" is equivalent to setting the two options\n \t "-mjp" and "-mjs".\n \n \t -mjp Serialize multiple parallel Java snippets into one Java Snippet.\n \n \t -mjs Combine multiple serial Java snippets into one Java Snippet.\n \n \t -es Remove unnecessary structural elements:\n \t - Remove any "Sequence" that is nested into another "Sequence".\n \t - Remove any "Parallel Activities" that contain only one entity.\n \n \t -ev Allow sharing variables.\n \t The optimization algorithm observes the following preconditions\n \t (among others):\n \t - common data types\n \t - no default data values on the inputs and outputs of activities\n \t - no dynamically assigned activity properties\n \t (taken from predefined data members in the input)\n \n \t Warnings\n \t ========\n \n \t 1) Some opportunities for optimization might not be exploited.\n \t 2) If you think that there are more opportunities for sharing variables\n \t consider the additional optimization options below (for experts only).\n \n \n \n \t 3. Additional optimization options\n \t ===================================\n \n \t The following options can only be set if the option "-ev" is set.\n \n \t Sometimes, default data values and dynamically assigned properties are specified in\n \t the model without them ever being used. Therefore the opportunities for sharing\n \t variables can be increased if the optimization algorithm is made to tolerate such\n \t properties.\n \n \t Analyze the activity settings of your model with care and let the optimization\n \t algorithm tolerate the following model properties if you are sure that this will\n \t not have unwanted side effects on the runtime behavior of the business model.\n \n \t -id Tolerate the default data values on the inputs and outputs of activities.\n \n \t -ip Tolerate the dynamically assigned activitiy properties.\n \t The option "-ip" is equivalent to setting the three options\n \t "-ips", "-ipn" and "-ipp".\n \n \t -ips Tolerate property "Staff from predefined members".\n \n \t -ipn Tolerate property "Notification from predefined members".\n \n \t -ipp Tolerate property "Priority from predefined member".\n \n \n \n \t 4. Return codes\n \t ===============\n \n \t 0 Processing finished successfully without errors or warnings.\n \t 2 Processing finished successfully and warnings occurred.\n \t 4 Errors occurred.
- Explanation: None.
- User Action: None.
- CWWBM0005E: The ''{0}'' message type is not a valid WebSphere MQ Workflow message type or it is not supported yet.
- Explanation: The message type cannot be generated.
- User Action: The MQ Workflow API supports only a subset of the MQ Workflow message types. Correct the message type so that it is valid. Also ensure that the message type is supported.
- CWWBM0005I: Exit with return code {0}.
- Explanation: The FDL to BPEL converter completed with the given return code.
- User Action: Call the FDL to BPEL converter tool with option "-h" to get a list of possible return codes.
- CWWBM0006E: An error occurred during the deserialization of the Service Data Object (SDO) ''{0}''.
- Explanation: The SDO could not be deserialized.
- User Action: Check the log for more information about the error. Also check your SDO definition.
- CWWBM0006I: Caught exception:
- Explanation: In the FDL to BPEL converter, a Java exception was caught. The exception information could be helpful for problem analysis.
- User Action: No action is required.
- CWWBM0007I: Reading FDL input file "{0}".
- Explanation: None.
- User Action: No action is required.
- CWWBM0008E: No input data structure specified for activity "{0}". The default values cannot be set.
- Explanation: The FDL input file is inconsistent.
- User Action: Make sure that the FDL file is correctly exported. If you made manual changes to the FDL file, check the file against the FDL specification in WebSphere MQ Workflow manual "Getting started with Buildtime".
- CWWBM0009E: No output data structure specified for activity "{0}". The default values cannot be set.
- Explanation: The FDL input file is inconsistent.
- User Action: Make sure that the FDL file is correctly exported. If you made manual changes to the FDL file, check the file against the FDL specification in WebSphere MQ Workflow manual "Getting started with Buildtime".
- CWWBM0010E: No input data structure specified for process "{0}". The default values cannot be set.
- Explanation: The FDL input file is inconsistent.
- User Action: Make sure that the FDL file is correctly exported. If you made manual changes to the FDL file, check the file against the FDL specification in WebSphere MQ Workflow manual "Getting started with Buildtime".
- CWWBM0011E: No output data structure specified for process "{0}". The default values cannot be set.
- Explanation: The FDL input file is inconsistent.
- User Action: Make sure that the FDL file is correctly exported. If you made manual changes to the FDL file, check the file against the FDL specification in WebSphere MQ Workflow book "Getting started with Buildtime".
- CWWBM0012E: The XSLT file "{0}" was not found.
- Explanation: The specified XSLT file was not found.
- User Action: Either specify a valid file name and check access authorizations or do not use option "-s" with the FDL2BPEL converter.
- CWWBM0013E: The intermediate file "{0}" was not found.
- Explanation: The program tried to open the given file.
- User Action: Make sure that the program can write to the specified directory and that there is enough space to write the file.
- CWWBM0014I: Writing intermediate file "{0}".
- Explanation: None.
- User Action: No action is required.
- CWWBM0015E: Intermediate file "{0}" could not be opened for writing.
- Explanation: The program tried to open a file with the given file name.
- User Action: Specify a valid file name and check the access authorizations.
- CWWBM0016I: Writing output file "{0}".
- Explanation: None.
- User Action: No action is required.
- CWWBM0017E: {0}({1}:{2}): Migration is not possible without creating predefined data members, because a predefined data member is used in the FDL file.
- Explanation: The migration would be incorrect without the predefined data members.
- User Action: Check whether you can eliminate the use of predefined data members in your FDL file and try the migration again with the modified FDL file. Otherwise, do not deselect the option to create predefined data members.
- CWWBM0018E: {0} (line number {1} and following): Migration is not possible, because the specified input/output data types for process activity "{2}" are different from the input/output data types expected by the referenced subprocess "{3}".
- Explanation: Subprocess can only be migrated when the data types match.
- User Action: Check whether you can adapt the input/output data types of the incompatible process activity in your FDL file and try the migration again with the modified FDL file.
- CWWBM0019I: Using XSLT file "{0}" to convert the data.
- Explanation: None.
- User Action: No action is required.
- CWWBM0020W: {0} (line number {1} and following): No BPEL mapping is available for the FDL option "Keep finished processes for <duration>" (see the settings for process "{2}").
- Explanation: Cannot translate the option "Keep finished processes for <duration>" on the "Control" page of the process properties.
- User Action: Select either the option "Keep finished processes never" or "Keep finished processes forever".
- CWWBM0021W: {0} (line number {1} and following): Cannot decide whether the program activity "{2}" should be mapped to a BPEL "empty activity", "human task (staff) activity", or "service invocation activity" ("human task (staff) activity" assumed).
- Explanation: The problem occurs if the required FDL program activity settings are not available. These settings are used to determine how the program activity is mapped to a BPEL activity. A program activity maps to a BPEL "empty activity" if all of the following conditions apply: 1. The activity implementation is a program with the name "FMCINTERNALNOOP". 2. The execution mode is asynchronous ("SYNCHRONIZATION CHAINED" is specified for the activity). 3. Input and output data structures of the activity are the same. A program activity maps to a BPEL "service invocation activity" if a user-defined program execution server (UPES) is specified (see settings register "Execution"). A program activity maps to a BPEL "human task (staff) activity" if the start type is "manual" and the flag "Program activities can be checked" (see settings register "Control") indicates that it can be checked out from the run-time database.
- User Action: Use the IBM WebSphere MQ Workflow Buildtime program to check the FDL activity settings and adjust them to match the intended mapping to BPEL.
- CWWBM0022E: {0}({1}:{2}): Illegal data type "{3}" found.
- Explanation: The data type cannot be processed.
- User Action: Import your FDL file into the IBM WebSphere MQ Workflow Buildtime program and run the process verification.
- CWWBM0024W: {0} (line number {1} and following): Option "Priority from predefined member" of program activity "{2}" cannot be mapped to BPEL, because you deselected the option to generate predefined data members.
- Explanation: Cannot translate the option "Priority from predefined member" on the "Control" page of the FDL activity settings that you specified in IBM WebSphere MQ Workflow Buildtime, because the predefined data member "_ACTIVITY_INFO/Priority" does not exist.
- User Action: Select "Create predefined data members" from the WebSphere MQ Workflow Migration options (in the WebSphere Integration Developer migration wizard) or remove option "-pn" when you use the FDL2BPEL Converter command line tool (SupportPac WA73).
- CWWBM0025W: {0} (line number {1} and following): Cannot translate the logical composition of dynamic staff queries "Members of roles", "Organization", and "Level".
- Explanation: There is no people assignment criteria (staff verb) available that allows an equivalent mapping of the staff assignment.
- User Action: No action is required.
- CWWBM0026W: {0} (line number {1} and following): The BPEL mapping for the FDL staff query type "People" does not allow for more than three persons (see the settings for activity "{2}").
- Explanation: You assigned more than three persons to staff query "People" on the "Staff1" page of the FDL activity settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: No action is required.
- CWWBM0027W: File {0} (line number {1} and following): The Business Process Execution Language (BPEL) mapping for the FlowMark Definition Language (FDL) staff query type "Staff from predefined members" is limited to the member "Organization" (see the settings for the {2} process).
- Explanation: The full meaning of the staff query "Staff from predefined members" on the Staff page of the FDL process settings that you specified in the IBM WebSphere MQ Workflow Buildtime program cannot be translated.
- User Action: An alternative solution to this problem is to specify a data-driven staff assignment with the option "People from container" on the "Staff" properties page of an activity.
- CWWBM0028W: File {0} (line number {1} and following): The Business Process Execution Language (BPEL) mapping for the FlowMark Definition Language (FDL) staff query type "Staff from predefined members" is limited to member "Organization" (see the settings for the {2} activity).
- Explanation: The full meaning of the staff query "Staff from predefined members" on the "Staff" page of the FDL activity settings that you specified in the IBM WebSphere MQ Workflow Buildtime program cannot be translated.
- User Action: An alternative solution to this problem is to specify a data-driven staff assignment with the option "People from container".
- CWWBM0029W: {0} (line number {1} and following): The BPEL mapping for the FDL staff query type "Members of roles" does not allow more than three persons (see the settings for activity "{2}").
- Explanation: You assigned more than three persons to the staff query "Members of roles" on the "Staff2" page of the FDL activity settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: No action is required.
- CWWBM0030W: {0} (line number {1} and following): No BPEL mapping is available for the FDL staff query type "Level" (see the settings for activity "{2}").
- Explanation: Cannot translate the staff query "Level" on the "Staff2" page of the FDL activity settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: No action is required.
- CWWBM0031W: {0} (line number {1} and following): No BPEL mapping is available for the FDL staff query type "IncludeReportingManagers" (see the settings for activity "{2}").
- Explanation: Cannot translate the staff query "Level" on the "Staff2" page of the FDL activity settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: No action is required.
- CWWBM0032W: {0}({1}:{2}): No data mapping was found for the data flow from "{3}" to "{4}"
- Explanation: None.
- User Action: Check the mapping of the data connector in IBM WebSphere MQ Workflow Buildtime.
- CWWBM0033W: {0} (line number {1} and following): No BPEL mapping is available for the FDL staff autonomy flag in process "{2}".
- Explanation: Cannot translate the staff autonomy flag on the "Control" page of the FDL process settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: No action is required.
- CWWBM0034W: {0} (line number {1} and following): No BPEL mapping is available for the FDL notification autonomy flag in process "{2}".
- Explanation: Cannot translate the notification autonomy flag on the "Control" page of the FDL process settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: No action is required.
- CWWBM0035W: {0} (line number {1} and following): No BPEL mapping is available for the FDL administration autonomy flag in process "{2}".
- Explanation: Cannot translate the administration autonomy flag on the "Control" page of the FDL process settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: No action is required.
- CWWBM0038E: {0} (line number {1} and following): Migration is not possible: The required program execution server definition (UPES) "{2}" is referred to in activity "{3}", but it is not defined in the FDL input file.
- Explanation: Ensure that you select the program execution server when you export the FDL file from the IBM WebSphere MQ Workflow Buildtime program.
- User Action: Repeat the FDL export from MQ Workflow Buildtime with the correct export options.
- CWWBM0039W: {0} (line number {1} and following): The FDL attribute "valid from" was missing in process "{2}". A dummy value was created.
- Explanation: No value was specified for the "valid from" date on the "General" page of the FDL process settings in the IBM WebSphere MQ Workflow Buildtime program.
- User Action:
- CWWBM0040E: Parameter "{0}" missing in the XSLT style sheet "{1}".
- Explanation: The style-sheet processing was invoked without a mandatory parameter.
- User Action: Check the command procedure or the Java class that invokes the style-sheet processing.
- CWWBM0041E: {0}({1}:{2}): In the BPEL element "{3}" a reference to the FDL data structure member name "{4}" was found. The definition of this data structure member name was not found in the FDL file.
- Explanation: Either the input FDL file contains errors or it is incomplete.
- User Action: Check that the FDL file is correct and complete. For example, make sure that the FDL file was generated using the "export deep" option.
- CWWBM0042E: A target namespace is missing for the option "{0}". If you omit this option, the default "{1}" is used.
- Explanation: When you use this option, you must provide a JNDI name.
- User Action: Correct the command line options.
- CWWBM0044E: Illegal input file name ''{0}''.
- Explanation: The FDL file name is the same as an existing process name.
- User Action: Rename the FDL file.
- CWWBM0046E: Missing logging parameter.
- Explanation: The "-l" option requires a logging value.
- User Action: Specify a logging value, for example, "-l 3".
- CWWBM0047E: The option "{0}" is not a valid command-line option.
- Explanation: See the text following this message for a list of the available command-line options.
- User Action: Correct your command-line option accordingly.
- CWWBM0048E: The output directory "{0}" was not found.
- Explanation: During execution, the FDL2BPEL converter creates files which are written to the output directory.
- User Action: Specify a valid output directory or do not specify an output directory at all. If you do not specify a directory, the output files are written to the directory that contains the FDL input file.
- CWWBM0049E: Missing output directory parameter with the option "{0}".
- Explanation: During execution, the FDL2BPEL converter creates files which are written to the output directory.
- User Action: Specify a valid output directory or do not specify the "-o" option. If you do not specify the "-o" option, the files are written to the directory that contains the FDL input file.
- CWWBM0050E: A syntax error occurred in the FDL file.
- Explanation: The input FDL file could not be processed because a syntax error occurred.
- User Action: Check the exception information for the location and the expected input in the FDL file.
- CWWBM0051E: A default value was not found for the internal API option.
- Explanation: An internal error occurred.
- User Action: Report this error or try to change your input to avoid this problem.
- CWWBM0052E: Missing output directory parameter with the option "{0}".
- Explanation: See the help text of the FDL2BPEL converter for further information about the command-line options.
- User Action: Specify a valid output directory or do not specify this option.
- CWWBM0053E: The output file "{0}" could not be opened for writing.
- Explanation: The program tried to open a file with the specified file name.
- User Action: Specify a valid file name and check the access authorizations.
- CWWBM0054E: An XML parser could not be loaded, the error message is: {0}
- Explanation: The converter can work only with a suitable XML parser. The parser is usually located in the Java run-time environment.
- User Action: Check the FDL2BPEL converter prerequisites to ensure that you are using the correct JVM.
- CWWBM0055E: The specified logging level "{0}" is not valid. The value must be between "{1}" and "{2}".
- Explanation: None.
- User Action: Correct your command-line options.
- CWWBM0056I: {0}({1}:{2}): The FDL name "{3}" cannot be used because "{4}" is a reserved name.
- Explanation: FDL names are converted to valid BPEL names, for example, blanks are removed. The BPEL names are then checked to ensure that they are not the same as a reserved name.
- User Action: Only if you are using the "-fc" option, change the FDL name.
- CWWBM0057E: {0}({1}:{2}): Unknown data structure member name.
- Explanation: An unknown data structure member was found.
- User Action: Import your FDL file into IBM WebSphere MQ Workflow Buildtime and run the process verification.
- CWWBM0058E: {0} (line number {1} and following): Unsupported activity state: {2}
- Explanation: The activity state cannot be mapped to BPEL.
- User Action: Either change your FDL model so that you do not need this activity state or replace the XPath condition by a Java condition that uses an equivalent API, for example "ActivityInstanceData.STATE_FINISHED".
- CWWBM0059W: {0} (line number {1} and following): No BPEL mapping is available for the FDL staff query type "Coordinator of role" (see the settings for activity "{2}").
- Explanation: Cannot translate staff query "Coordinator of role" on the "Staff" page of the FDL activity settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: No action is required.
- CWWBM0060I: {0} (line number {1} and following): Migration is limited to the staff query type "Members of roles".
- Explanation: The staff assignment that you specified cannot be mapped to a corresponding people assignment criteria (staff verb). The people assignment criteria "Members of roles" was generated as a substitute.
- User Action: Consider choosing a different people assignment criteria (staff verb) or specify a customized people assignment criteria that matches your needs.
- CWWBM0061W: {0} (line number {1} and following): No BPEL mapping is available for the FDL staff query type "Manager of organization" (see the settings for activity "{2}").
- Explanation: Cannot translate the staff query "Manager of organization" on the "Staff" page of the FDL activity settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: No action is required.
- CWWBM0062I: {0} (line number {1} and following): Migration limited to staff query type "Organization".
- Explanation: The staff assignment that you specified cannot be mapped to a corresponding people assignment criteria (staff verb). The people assignment criteria "Organization" was generated as a substitute.
- User Action: Either choose a different people assignment criteria (staff verb) or specify a customized people assignment criteria that meets your needs.
- CWWBM0063W: {0} (line number {1} and following): No BPEL mapping is available for the FDL staff query type "Exclude starter of activity" (see the settings for activity "{2}").
- Explanation: Cannot translate the staff query "Exclude starter of activity" on the "Staff" page of the FDL activity settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: No action is required.
- CWWBM0064W: {0} (line number {1} and following): No BPEL mapping is available for the FDL staff query type "{2}" (see the settings for process "{3}").
- Explanation: Cannot translate the staff query "Exclude starter of activity" on the "Staff" page of the FDL process settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: No action is required.
- CWWBM0065W: {0} (line number {1} and following): No BPEL mapping is available for the FDL staff query type "{2}" (see the settings for activity "{3}").
- Explanation: Cannot translate the staff query "Exclude starter of activity" on the "Staff" page of the FDL activity settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: No action is required.
- CWWBM0066I: FDL2BPEL converter version {0}.
- Explanation: None.
- User Action: No action is required.
- CWWBM0067E: The options used with the FDL2BPEL converter are inconsistent. If you want to initialize the predefined data members, then these members must be defined.
- Explanation: WebSphere MQ Workflow provides predefined data members for each activity and each process. Some of these data members are updated by the system. Depending on the usage of these data members, they should be created and initialized in the BPEL file.
- User Action: Check the options of the FDL2BPEL converter and correct them.
- CWWBM0068E: The namespace "{0}" you specified as a parameter does not start with "http://".
- Explanation: None.
- User Action: No action is required.
- CWWBM0069E: {0}({1}:{2}): The data structure "{3}" is referenced but is not defined in the FDL input file.
- Explanation: The FDL input file does not contain all of the necessary definitions for the conversion to BPEL.
- User Action: Check that all of the data structures referred to in the FDL file are also defined. If you use the IBM WebSphere MQ Workflow Buildtime program, export process definitions using the "Export deep" option.
- CWWBM0070E: The target version is not correct. Allowed values are: {0}. The default value is "{1}".
- Explanation: The FDL2BPEL converter can produce output for different versions of WebSphere Application Server.
- User Action: Determine the correct version you need and set it or use the default by omitting this parameter.
- CWWBM0071E: The target version is missing for option "{0}". If you omit this option, the default value "{1}" is used.
- Explanation: You must specify a version with this option.
- User Action: Correct your command-line options.
- CWWBM0072E: The output directory is empty.
- Explanation: During execution, the FDL2BPEL converter creates files which are written to the output directory.
- User Action: The output directory is given as second parameter of the convert method. This parameter must not be null.
- CWWBM0073W: {0} (line number {1} and following): Option "Notification from container" of program activity "{2}" cannot be mapped to BPEL.
- Explanation: Cannot translate the option "Notification from container" on the "Notification" page of the FDL activity settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: You must select "Duration" and choose a time in the entry field.
- CWWBM0074W: {0} (line number {1} and following): There is no data connector in process "{2}" that distributes the process input data.
- Explanation: You did not attach an inbound data connector to the process source node in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: Check your process model and add data connectors that distribute the process input data appropriately to the activity nodes.
- CWWBM0075W: {0} (line number {1} and following): There is no data connector in process "{2}" that collects the process output data.
- Explanation: You did not attach an outbound data connector to the process sink node in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: Check your process model and add data connectors that collect the process output data from the appropriate activity nodes.
- CWWBM0076I: Using the default people assignment criteria (staff verb) "Everybody".
- Explanation: The staff assignment that you specified cannot be mapped to a people assignment criteria (staff verb). The people assignment criteria "Everybody" is being used.
- User Action: Either choose a different people assignment criteria (staff verb) or specify a customized people assignment criteria that meets your needs.
- CWWBM0077E: The option "-c" is used, but no codepage is specified.
- Explanation: If you want to process an FDL file in a codepage that is not the system codepage, use this option.
- User Action: Specify a valid codepage. For example "-c Cp1252" is a valid setting.
- CWWBM0078I: The following list contains the valid codepages in the following format: Canonic name of the codepage followed by an explanation string. Then, in the lines below, the aliases are listed. {0}
- Explanation: None.
- User Action: No action is required.
- CWWBM0079W: {0} (line number {1} and following): The following description or documentation text exceeds the maximum field length of {2} characters: "{3}".
- Explanation: Converting the FDL description or documentation text would have been longer that is allowed in BPEL.
- User Action: Check the generated description or documentation text which has been shortened so that it conforms to the length restriction.
- CWWBM0080W: {0} (line number {1} and following): The option "Program execution server from container" of the program activity "{2}" cannot be mapped to BPEL.
- Explanation: Cannot translate the option "Program execution server from container " on the "Execution" page of the FDL activity settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: Select "Server" and choose a Program execution server in the entry field.
- CWWBM0081E: The base queue name "{0}" exceeds the maximum length of {1} characters".
- Explanation: The base queue name derived from the WebSphere MQ queue name that is defined in the FDL file, exceeds the maximum length that is allowed for WebSphere Process Server.
- User Action: Check whether you can shorten the queue name.
- CWWBM0082W: {0} (line number {1} and following): No BPEL mapping is available for input data defaults of process "{2}".
- Explanation: Process input data defaults are not supported using BPEL assign activities.
- User Action: Add a Java snippet that sets process input data defaults.
- CWWBM0083W: The {0} is used at "{1}" of process "{2}", but is not defined in the FDL file.
- Explanation: There are definitions missing in your FDL file.
- User Action: Verify the FDL file using the IBM WebSphere MQ Workflow Buildtime program and export it using the "export deep" option.
- CWWBM0084W: The global container for process "{0}" is specified with an empty data structure ("{1}").
- Explanation: A global container must not have an empty data structure.
- User Action: Verify the FDL file using the IBM WebSphere MQ Workflow Buildtime program.
- CWWBM0085I: {0}({1}:{2}): The FDL activity name "{3}" and the process name "{4}" cannot be used without modification because both names map to the same BPEL name.
- Explanation: In the generated BPEL, activity and process names must be unique to avoid name clashes with variables.
- User Action: If you are using the "-fc" option, change the activity or process name in the FDL file.
- CWWBM0086E: {0} (line number {1} and following): Migration is not possible: The program "{2}" is referred to in activity "{3}", but it is not defined in the FDL file.
- Explanation: The FDL file does not contain all the necessary definitions for it to be converted to BPEL.
- User Action: Check that all programs that are referred to in the FDL file are defined. If you are using the IBM WebSphere MQ Workflow Buildtime program, export the process definitions using the "Export deep" option.
- CWWBM0087W: {0} (line number {1} and following): The option "Expiration from container" of program activity "{2}" cannot be mapped to BPEL.
- Explanation: Cannot translate the option "Expiration from container" on the "Exit" page of the FDL activity settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: Either select the option "No duration" or select "Duration" and choose a time in the entry field.
- CWWBM0088W: {0} (line number {1} and following): The option "Priority" of program activity "{2}" cannot be mapped to BPEL.
- Explanation: Cannot translate the option "Priority" on the "Control" page of the FDL activity settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: No action is required.
- CWWBM0089E: The options "-pi" and "-pn" cannot be used together. If you want to initialize the predefined data members, the members must be defined.
- Explanation: WebSphere MQ Workflow provides predefined data members for each activity and each process. Some of these data members are updated by the system. Depending on how the data members are used, they must be created and initialized in the BPEL file.
- User Action: Check the options of the FDL2BPEL converter program and correct them.
- CWWBM0090W: {0} (line number {1} and following): The option "Assign substitute for notification if user is absent" cannot be mapped to BPEL.
- Explanation: Cannot translate the option "Assign substitute for notification if user is absent" into BPEL. See either the "Control" page of the FDL activity settings or the "activity" page of the process settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: No action is required.
- CWWBM0091W: {0} (line number {1} and following): The option "Prefer local users" cannot be mapped to BPEL.
- Explanation: Cannot translate the option "Prefer local users" into BPEL. See either the "Control" page of the FDL activity settings or the "activity" page of the process settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: No action is required.
- CWWBM0092E: {0} (line number {1} and following): Cannot migrate because the specified input/output data type "{2}" of "{3}" is not defined in the FDL file.
- Explanation: The FDL input file does not contain all of the necessary definitions for the conversion to BPEL.
- User Action: Ensure that you exported the FDL file from the IBM WebSphere MQ Workflow Buildtime program using the "export deep" option.
- CWWBM0093E: {0} (line number {1} and following): Cannot migrate: The required process definition "{2}" is referred to in activity "{3}", but it is not defined in the FDL input file.
- Explanation: The FDL input file does not contain all of the necessary definitions for the conversion to BPEL.
- User Action: Ensure that you exported the FDL file from the IBM WebSphere MQ Workflow Buildtime program using the "export deep" option.
- CWWBM0094W: {0} (line number {1} and following): The option "Send second notification to same user" cannot be mapped to BPEL.
- Explanation: Cannot translate the option "Send second notification to same user" into BPEL. See either the "Control" page of the FDL activity settings or the "activity" page of the process settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: No action is required.
- CWWBM0095W: {0} (line number {1} and following): The option "Include process assignment" cannot be mapped to BPEL.
- Explanation: Cannot translate the option "Include process assignment" into BPEL. See either the "Control" page of the FDL activity settings or the "activity" page of the process settings that you specified in the IBM WebSphere MQ Workflow Buildtime program.
- User Action: No action is required.
- CWWBM0096W: File {0} (line number {1} and following): The staff assignment criteria for FlowMark Definition Language (FDL) staff query type "Exclude starter of activity" cannot be resolved (see the settings for the {2} activity).
- Explanation: The staff query "Exclude starter of activity"on the "Staff" page of the FDL activity settings that you specified in the IBM WebSphere MQ Workflow Buildtime program cannot be translated. The staff assignment criteria of the referenced activity are not compatible with a valid translation to people assignment criteria of type "Users by user ID without Named Users" or "Group Members without Named Users".
- User Action: No action is required.
- CWWBM0100I: Starting Business Process Choreographer migration from {0} to {1}.
- Explanation: Migration of the Business Process Choreographer configuration is starting.
- User Action: No action is required.
- CWWBM0101I: Invoking {0} with parameters: {1}.
- Explanation: The migration script was invoked with the parameters printed.
- User Action: No action is required.
- CWWBM0102I: Command {0} finished with return code {1}.
- Explanation: The migration script has finished with the return code printed.
- User Action: No action is required.
- CWWBM0104I: Finished Business Process Choreographer migration.
- Explanation: Migration of Business Process Choreographer has finished.
- User Action: No action is required.
- CWWBM0105E: {0}({1}:{2}): The name component "{3}" is referred to but is not defined in the FDL input file.
- Explanation: The FDL input file does not contain all of the necessary definitions for the conversion to BPEL.
- User Action: Check that all of the data structures referred to in the FDL file are also defined. If you are using the WebSphere MQ Workflow Buildtime program, export process definitions using the "Export deep" option.
- CWWBM0138E: {0}({1}:{2}): The input FDL file contains the activity names "{3}" and "{4}" which are both mapped to the same activity name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process must interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0139E: {0}({1}:{2}): The input FDL file contains the activity name "{3}" and process name "{4}" which are both mapped to the same activity name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0140E: {0}({1}:{2}): The input FDL file contains the activity name "{3}" and program name "{4}" which are both mapped to the same activity name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0141E: {0}({1}:{2}): The input FDL file contains the activity name "{3}" and server name "{4}" which are both mapped to the same activity name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0142W: {0}({1}:{2}): To avoid a name clash, the activity name "{3}" in FDL is converted to the activity name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed. So, it is possible that different FDL names are initially mapped to the same BPEL name. To avoid a name clash, one of the names is changed slightly.
- User Action: If you want to avoid name clashes, you can import your FDL file into WebSphere MQ Workflow using the "-x" option, which checks that names are BPEL-compliant.
- CWWBM0143I: {0}({1}:{2}): Converting the activity name "{3}" in FDL to the activity name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed.
- User Action: No action is required.
- CWWBM0144E: {0}({1}:{2}): The input FDL file contains the connector names "{3}" and "{4}" which are both mapped to the same link name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0145W: {0}({1}:{2}): To avoid a name clash, the connector name "{3}" in FDL is converted to the link name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed. So, it is possible that different FDL names are initially mapped to the same BPEL name. To avoid a name clash, one of the names is changed slightly.
- User Action: If you want to avoid name clashes, you can import your FDL file into WebSphere MQ Workflow using the option "-x", which checks that names are BPEL-compliant.
- CWWBM0146I: {0}({1}:{2}): Converting the connector name "{3}" in FDL to the link name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed.
- User Action: No action is required.
- CWWBM0147E: {0}({1}:{2}): The input FDL file contains the data structure member names "{3}" and "{4}" which are both mapped to the same variable name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, name clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0148W: {0}({1}:{2}): To avoid a name clash, the data structure member name "{3}" in FDL is converted to the variable name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed. So, it is possible that different FDL names are initially mapped to the same BPEL name. To avoid a name clash, one of the names is changed slightly.
- User Action: If you want to avoid name clashes, you can import your FDL file into WebSphere MQ Workflow using the option "-x", which checks that names are BPEL-compliant.
- CWWBM0149I: {0}({1}:{2}): Converting the data structure member name "{3}" in FDL to the variable name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed.
- User Action: No action is required.
- CWWBM0150E: {0}({1}:{2}): The input FDL file contains the organization names "{3}" and "{4}" which are both mapped to the same name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0151W: {0}({1}:{2}): To avoid a name clash, the organization name "{3}" in FDL is converted to the name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed. So, it is possible that different FDL names are initially mapped to the same BPEL name. To avoid a name clash, one of the names is changed slightly.
- User Action: If you want to avoid name clashes, you can import your FDL file into WebSphere MQ Workflow using the option "-x", which checks that names are BPEL-compliant.
- CWWBM0152I: {0}({1}:{2}): Converting the organization name "{3}" in FDL to the name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed.
- User Action: No action is required.
- CWWBM0153E: {0}({1}:{2}): The input FDL file contains the person names "{3}" and "{4}" which are both mapped to the same person name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0154W: {0}({1}:{2}): To avoid a name clash, the person name "{3}" in FDL is converted to the person name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed. So, it is possible that different FDL names are initially mapped to the same BPEL name. To avoid a name clash, one of the names is changed slightly.
- User Action: If you want to avoid name clashes, you can import your FDL file into WebSphere MQ Workflow using the option "-x", which checks that names are BPEL-compliant.
- CWWBM0155I: {0}({1}:{2}): Converting the person name "{3}" in FDL to the person name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed.
- User Action: No action is required.
- CWWBM0156E: {0}({1}:{2}): The input FDL file contains the process name "{3}" and activity name "{4}" which are both mapped to the same process name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0157E: {0}({1}:{2}): The input FDL file contains the process names "{3}" and "{4}" which are both mapped to the same process name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0158E: {0}({1}:{2}): The input FDL file contains the process name "{3}" and program name "{4}" which are both mapped to the same process name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0159E: {0}({1}:{2}): The input FDL file contains the process name "{3}" and server name "{4}" which are both mapped to the same process name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0160W: {0}({1}:{2}): To avoid a name clash, the process name "{3}" in FDL is converted to the process name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed. So, it is possible that different FDL names are initially mapped to the same BPEL name. To avoid a name clash, one of the names is changed slightly.
- User Action: If you want to avoid name clashes, you can import your FDL file into WebSphere MQ Workflow using the option "-x", which checks that names are BPEL-compliant.
- CWWBM0161I: {0}({1}:{2}): Converting the process name "{3}" in FDL to the process name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed.
- User Action: No action is required.
- CWWBM0162E: {0}({1}:{2}): The input FDL file contains the program name "{3}" and activity name "{4}" which are both mapped to the same name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0163E: {0}({1}:{2}): The input FDL file contains the program name "{3}" and process name "{4}" which are both mapped to the same name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0164E: {0}({1}:{2}): The input FDL file contains the program names "{3}" and "{4}" which are both mapped to the same name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0165E: {0}({1}:{2}): The input FDL file contains the program name "{3}" and server name "{4}" which are both mapped to the same name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0166W: {0}({1}:{2}): To avoid a name clash, the program name "{3}" in FDL is converted to the name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed. So, it is possible that different FDL names are initially mapped to the same BPEL name. To avoid a name clash, one of the names is changed slightly.
- User Action: If you want to avoid name clashes, you can import your FDL file into WebSphere MQ Workflow using the option "-x", which checks that names are BPEL-compliant.
- CWWBM0167I: {0}({1}:{2}): Converting the program name "{3}" in FDL to the name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed.
- User Action: No action is required.
- CWWBM0168E: {0}({1}:{2}): The input FDL file contains the role names "{3}" and "{4}" which are both mapped to the same name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0169W: {0}({1}:{2}): To avoid a name clash, the role name "{3}" in FDL is converted to the name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed. So, it is possible that different FDL names are initially mapped to the same BPEL name. To avoid a name clash, one of the names is changed slightly.
- User Action: If you want to avoid name clashes, you can import your FDL file into WebSphere MQ Workflow using the option "-x", which checks that names are BPEL-compliant.
- CWWBM0170I: {0}({1}:{2}): Converting the role name "{3}" in FDL to the name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed.
- User Action: No action is required.
- CWWBM0171E: {0}({1}:{2}): The input FDL file contains the structure names "{3}" and "{4}" which are both mapped to the same structure name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0172W: {0}({1}:{2}): To avoid a name clash, the structure name "{3}" in FDL is converted to the structure name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed. So, it is possible that different FDL names are initially mapped to the same BPEL name. To avoid a name clash, one of the names is changed slightly.
- User Action: If you want to avoid name clashes, you can import your FDL file into WebSphere MQ Workflow using the option "-x", which checks that names are BPEL-compliant.
- CWWBM0173I: {0}({1}:{2}): Converting the structure name "{3}" in FDL to the structure name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed.
- User Action: No action is required.
- CWWBM0174E: {0}({1}:{2}): The input FDL file contains the file names "{3}" and "{4}" which are both mapped to the same file name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0175W: {0}({1}:{2}): To avoid a name clash, the file name "{3}" in FDL is converted to the file name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed. So, it is possible that different FDL names are initially mapped to the same BPEL name. To avoid a name clash, one of the names is changed slightly.
- User Action: If you want to avoid name clashes, you can import your FDL file into WebSphere MQ Workflow using the option "-x", which checks that names are BPEL-compliant.
- CWWBM0176I: {0}({1}:{2}): Converting the file name "{3}" in FDL to the file name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed.
- User Action: No action is required.
- CWWBM0177E: {0}({1}:{2}): The input FDL file contains the server name "{3}" and activity name "{4}" which are both mapped to the same name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0178E: {0}({1}:{2}): The input FDL file contains the server name "{3}" and process name "{4}" which are both mapped to the same name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0179E: {0}({1}:{2}): The input FDL file contains the server name "{3}" and program name "{4}" which are both mapped to the same name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0180E: {0}({1}:{2}): The input FDL file contains the server names "{3}" and "{4}" which are both mapped to the same name "{5}" in BPEL. Consider switching off the "Treat name conflicts as errors" option (command line option "-fc").
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, naming clashes can occur when names are mapped from the FDL syntax to the BPEL syntax.
- User Action: To avoid name clashes, run the FDL2BPEL converter without the "-fc" option. If the resulting BPEL process is to interoperate with WebSphere MQ Workflow, change the FDL source file so that this error does not occur.
- CWWBM0181W: {0}({1}:{2}): To avoid a name clash, the server name "{3}" in FDL is converted to the name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed. So, it is possible that different FDL names are initially mapped to the same BPEL name. To avoid a name clash, one of the names is changed slightly.
- User Action: If you want to avoid name clashes, you can import your FDL file into WebSphere MQ Workflow using the option "-x", which checks that names are BPEL-compliant.
- CWWBM0182I: {0}({1}:{2}): Converting the server name "{3}" in FDL to the name "{4}" in BPEL.
- Explanation: FDL names can be modified by the FDL-to-BPEL converter so that they are valid BPEL names. For example, blanks are not allowed in BPEL names and are removed.
- User Action: No action is required.
- CWWBM0183I: Because errors occurred while migrating the FDL file to BPEL, the remaining migration steps will not be performed.
- Explanation: Skipping the remaining steps avoids generating follow-on error messages which are caused by previous errors.
- User Action: No action is required.
- CWWBM0184I: Because errors occurred while migrating the FDL file to BPEL, no project was created for the BPEL output.
- Explanation: A BPEL project is only created if no errors occurred during the conversion.
- User Action: No action is required.
- CWWBM0200E: Migration 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.
- CWWBM0201I: Migration 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.
- CWWBM0202W: Migration 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.
- CWWBM0203W: The application {0} was created with a deprecated version of the WebSphere Studio process editor. Use WebSphere Studio version 5.1 to migrate the application to BPEL.
- Explanation: The application contains deprecated process definitions.
- User Action: Migrate the application to BPEL using WebSphere Application Developer Studio Integration Edition Version 5.1.
- CWWBM0205E: If one of the options "-id", "-ip", "-ipn", "-ipp", or "-ips" is set, the option "-opt" or "-ev" must also be set.
- Explanation: The option "-id", "-ip", "-ipn", "-ipp", or "-ips" makes sense only if the option "-opt" or "-ev" is also used. In this case, it can increase the optimization effect.
- User Action: Either add "-opt" or "-ev" or remove the option "-id", "-ip", "-ipn", "-ipp", or "-ips".