- CWWBM0000E: Log file "{0}" could not be opened for writing.
- Explanation: The specified file could not be opened for writing.
- User Action: Specify a valid file name and check the access authorizations.
- 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: The directory "{0}" containing the style sheets was not found.
- Explanation: With the option "-s", the FDL to BPEL converter does not use the default stylesheets.
- User Action: Omit the option "-s" or specify a directory that contains the necessary stylesheets.
- CWWBM0004I: Help:\n\u0020 FDL2BPEL Converter, a tool to convert files in FDL (Flow Definition Language)\\u0020 to BPEL (Business Process Execution Language).\\\\u0020 Usage: FDL2BPELConverter <options>\\u0020 Options can be:\\\u0020 -h, -? Print this description\\\u0020 -i <file name>\\u0020 Name of the FDL input file.\\\u0020 -od <directory name>\\u0020 As output, the following files are generated:\\u0020 1. An XSD (XML schema definition) file\\u0020 is generated with the same name as the FDL input file\\u0020 but with ".xsd" as extension.\\u0020 2. A WSDL (Web Services Definition Language) file\\u0020 is generated with the same name as the FDL input file\\u0020 but with ".wsdl" as extension.\\u0020 3. For each process definition, a BPEL file is generated\\u0020 with the process name as the file name appended with\\u0020 ".bpel".\\u0020 4. For each FDL process definition that contains process\\u0020 activities, a BPELEX file is generated with the name of\\u0020 the referenced process as the file name and ".bpelex" as\\u0020 file extension.\\u0020 5. For each FDL program activity that translates to a BPEL\\u0020 staff activity, a TEL file is generated with a name derived\\u0020 from the activity name and ".itel" as file extension.\\u0020 If this parameter is not specified, then\\u0020 the directory location of the input file is also used for\\u0020 the output files.\\\u0020 -oe <directory name>\\u0020 The name of the WebSphere Integration Developer service project where you want\\u0020 to import the generated files for review and generation of the deploy code.\\u0020 This parameter is required if your FDL input file contains the definition of\\u0020 a process with subprocess invocations (process activities).\\\u0020 -fc Flag name clashes as errors.\\u0020 Due to different syntax rules, the FDL2BPEL converter\\u0020 might change names. This can lead to \\u0020 different FDL names being converted to the same BPEL\\u0020 name. The default behavior is that the FDL2BPEL\\u0020 converter appends suffixes to avoid this situation. If you\\u0020 are using the "-fc" option, the FDL2BPEL converter flags\\u0020 the name clashes as errors instead of appending suffixes.\\u0020 Use this option if you are interested in the interoperability\\u0020 between WebSphere MQ Workflow and WebSphere Process Server.\\\u0020 -pi Initialize the predefined data members _ACTIVITY, _PROCESS,\\u0020 and _PROCESS_MODEL.\\\u0020 -tx <namespace URI>\\u0020 Set this option if you need a special target namespace URI\\u0020 for the generated XML schema files.\\u0020 The default value is "{2}".\\\u0020 -tw <namespace URI>\\u0020 Set this option if you need a special target namespace URI\\u0020 for the generated WSDL files.\\u0020 The default value is "{1}".\\\u0020 -tb <namespace URI>\\u0020 Set this option if you need a special target namespace URI\\u0020 for the generated BPEL files.\\u0020 The default value is "{0}".\\\u0020 -v <version>\\u0020 This option allows you to produce output for different versions\\u0020 of WebSphere Process Server. Allowed values are "v51" and "v60" (default).\\\\u0020 Return codes:\\u0020 0 Processing finished successfully without errors or warnings.\\u0020 2 Processing finished successfully and warnings occurred.\\u0020 4 Errors occurred.
- Explanation: None.
- User Action: None.
- 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.
- 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: None.
- CWWBM0007I: Reading FDL input file "{0}".
- Explanation: None.
- User Action: None.
- 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 inWebSphere 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 inWebSphere 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 inWebSphere 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 inWebSphere 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: None.
- 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: None.
- CWWBM0017W: To avoid a name clash, the FDL name "{0}" is converted to the BPEL name "{1}".
- Explanation: None.
- User Action: None.
- CWWBM0018I: Converting FDL name "{0}" to BPEL name "{1}".
- Explanation: None.
- User Action: None.
- CWWBM0019I: Using XSLT file "{0}" for data conversion.
- Explanation: None.
- User Action: None.
- CWWBM0020W: No BPEL mapping is available for FDL option "Keep finished processes for <duration>" (see the settings for process "{0}").
- Explanation: Cannot translate option "Keep finished processes for <duration>" on page "Control" of the process properties.
- User Action: Select from options "Keep finished processes never" or "Keep finished processes forever".
- CWWBM0021W: Cannot decide whether program activity "{0}" should be mapped to a BPEL "empty activity", "staff activity", or "service invocation activity" ("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 maps to aBPEL 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 "staff activity" if the start type is "manual" and the flag"Program activities can be checked" (see settings register "Control") indicates that it canbe checked out from the run-time database.
- User Action: Use IBM WebSphere MQ Workflow Buildtime to check the FDL activity settings and adjust them to match the intended mapping to BPEL.
- CWWBM0022E: Illegal data type "{0}" found.
- Explanation: The data type cannot be processed.
- User Action: Import your FDL file into IBM WebSphere MQ Workflow Buildtime and run the process verification.
- CWWBM0024W: Option "Expiration from container" of program activity "{0}" cannot be mapped to BPEL.
- Explanation: Cannot translate option "Expiration from container" on page "Exit" of the FDL activity settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: Either select the option "No duration" or select "Duration" and choose a time in the entry field.
- CWWBM0025W: No BPEL mapping available for FDL staff query type "People from container" (see the settings for activity "{0}").
- Explanation: Cannot translate staff query "People from container" on page "Staff1" of the FDL activity settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: You can explicitly add people to the "People" list on page "Staff1".
- CWWBM0026W: BPEL mapping for the FDL staff query type "People" does not consider more than three persons (see the settings for activity "{0}").
- Explanation: You assigned more than three persons to staff query "People" on page "Staff1" of the FDL activity settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: None.
- CWWBM0027W: A BPEL mapping is not available for the FDL staff query type "Staff from predefined members" (see the settings for process "{0}").
- Explanation: Cannot translate staff query "Staff from predefined members" on page "Staff" of the FDL process settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: A possible 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: A BPEL mapping is not available for the FDL staff query type "Staff from predefined members" (see the settings for activity "{0}").
- Explanation: Cannot translate staff query "Staff from predefined members" on page "Staff" of the FDL activity settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: A possible solution to this problem is to specify a data-driven staff assignment with the option "People from container".
- CWWBM0029W: BPEL mapping for the FDL staff query type "Members of roles" will not consider more than three persons (see the settings for activity "{0}").
- Explanation: You assigned more than three persons to staff query "Members of roles" on page "Staff2" of the FDL activity settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: None.
- CWWBM0030W: No BPEL mapping is available for the FDL staff query type ''Level'' (see the settings for activity ''{0}'').
- Explanation: Cannot translate staff query "Level" on page "Staff2" of the FDL activity settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: None.
- CWWBM0031W: No BPEL mapping is available for the FDL staff query type "IncludeReportingManagers" (see the settings for activity ''{0}'').
- Explanation: Cannot translate staff query "Level" on page "Staff2" of the FDL activity settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: None.
- CWWBM0032W: No data mappings found for the data flow from ''{0}'' to ''{1}''
- Explanation: None.
- User Action: Check the mapping of the data connector in IBM WebSphere MQ Workflow Buildtime.
- CWWBM0033W: A BPEL mapping is not available for the FDL staff autonomy flag in process "{0}".
- Explanation: Cannot translate the staff autonomy flag on page "Control" of the FDL process settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: None.
- CWWBM0034W: A BPEL mapping is not available for the FDL notification autonomy flag in process "{0}".
- Explanation: Cannot translate the notification autonomy flag on page "Control" of the FDL process settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: None.
- CWWBM0035W: A BPEL mapping is not available for the FDL administration autonomy flag in process "{0}".
- Explanation: Cannot translate the administration autonomy flag on page "Control" of the FDL process settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: None.
- CWWBM0037W: A BPEL mapping is not available for the FDL option "Keep finished processes for <duration>" in process "{0}".
- Explanation: Cannot translate the "Keep finished processes for <duration>" on page "Control" of the FDL process settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: None.
- CWWBM0038E: A user defined program execution server (UPES) was not found.
- Explanation: Ensure that you select the program execution server option when you export from IBM WebSphere MQ Workflow Buildtime.
- User Action: Repeat the FDL export from MQ Workflow Buildtime with the correct export options.
- CWWBM0039W: The FDL attribute "valid from" was missing in process "{0}" (dummy value created).
- Explanation: You did not specify a "valid from" date on page "General" of the FDL process settings in IBM WebSphere MQ Workflow Buildtime.
- 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: Illegal FDL data structure member name "{0}" (Cannot generate data path expression in BPEL element "{1}").
- Explanation: Cannot translate an illegal FDL data path expression.
- User Action: Check your FDL for incorrect FDL data path expression. For instance, check that none of your data mapping and condition expressions refers to a missing data member.
- 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 your 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.
- CWWBM0045E: The input FDL file contains the names "{0}" and "{1}" which are both mapped to the same BPEL name "{2}". Consider switching off the "-fc" option.
- Explanation: The naming conventions in BPEL are more restrictive than in FDL. Therefore, names clashes can occur when names are mapped from the FDL 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.
- 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: The FDL name "{0}" cannot be used because "{1}" 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: Unknown data structure member name.
- Explanation: Unknown data structure member found.
- User Action: Import your FDL file to IBM WebSphere MQ Workflow Buildtime and run the process verification.
- CWWBM0058E: Unsupported activity state: {0}
- Explanation: The activity state cannot be mapped to BPEL.
- User Action: Check whether the activity state occurs as an exception that you can catch.
- CWWBM0059W: A BPEL mapping is not available for the FDL staff query type "Coordinator of role" (see the settings for activity "{0}").
- Explanation: Cannot translate staff query "Coordinator of role" on page "Staff" of the FDL activity settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: None.
- CWWBM0060W: A BPEL mapping is not available for the FDL staff query type "Coordinator of role from container" (see the settings for activity "{0}").
- Explanation: Cannot translate staff query "Coordinator of role from container" on page "Staff" of the FDL activity settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: None.
- CWWBM0061W: A BPEL mapping is not available for the FDL staff query type "Manager of organization" (see the settings for activity "{0}").
- Explanation: Cannot translate staff query "Manager of organization" on page "Staff" of the FDL activity settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: None.
- CWWBM0062W: A BPEL mapping is not available for the FDL staff query type "Manager of organization from container" (see the settings for activity "{0}").
- Explanation: Cannot translate staff query "Manager of organization from container" on page "Staff" of the FDL activity settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: None.
- CWWBM0063W: A BPEL mapping is not available for the FDL staff query type "Exclude starter of activity" (see the settings for activity "{0}").
- Explanation: Cannot translate staff query "Exclude starter of activity" on page "Staff" of the FDL activity settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: None.
- CWWBM0064W: A BPEL mapping is not available for the FDL staff query type "{0}" (see the settings for process "{1}").
- Explanation: Cannot translate staff query "Exclude starter of activity" on page "Staff" of the FDL process settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: None.
- CWWBM0065W: A BPEL mapping is not available for the FDL staff query type "{0}" (see the settings for activity "{1}").
- Explanation: Cannot translate staff query "Exclude starter of activity" on page "Staff" of the FDL activity settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: None.
- CWWBM0066I: FDL2BPEL converter version {0}.
- Explanation: None.
- User Action: None.
- 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 initializedin 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: None.
- CWWBM0069E: This structure "{0}" is referred to but 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, export process definitions with 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: Option "Notification from container" of program activity "{0}" cannot be mapped to BPEL.
- Explanation: Cannot translate option "Notification from container" on page "Notification" of the FDL activity settings that you specified in IBM WebSphere MQ Workflow Buildtime.
- User Action: You have to select "Duration" and choose a time in the entry field.
- CWWBM0074W: There is no data connector in process "{0}" that distributes the process input data.
- Explanation: You did not specify any inbound data connector attached to the process source node in IBM WebSphere MQ Workflow Buildtime.
- User Action: Check your process model and add data connectors that distribute the process input data to the respective activity nodes as required.
- CWWBM0075W: There is no data connector in process "{0}" that collects the process output data.
- Explanation: You did not specify any outbound data connector attached to the process sink node in IBM WebSphere MQ Workflow Buildtime.
- User Action: Check your process model and add data connectors that collect the process output data from the respective activity nodes as required.
- CWWBM0076I: Default staff verb "Everybody" used.
- Explanation: The staff assignment that you specified cannot be mapped to a corresponding staff verb. As a substitute the staff verb "Everybody" was generated.
- User Action: Consider choosing another staff verb or to specify a customized staff verb that better meets your needs.
- CWWBM0100I: Starting Business Process Choreographer migration from {0} to {1}.
- Explanation: Migration of the Business Process Choreographer configuration is starting.
- User Action: None.
- CWWBM0101I: Invoking {0} with parameters: {1}.
- Explanation: The migration script was invoked with the parameters printed.
- User Action: None.
- CWWBM0102I: Command {0} finished with return code {1}.
- Explanation: The migration script has finished with the return code printed.
- User Action: None.
- CWWBM0104I: Finished Business Process Choreographer migration.
- Explanation: Migration of Business Process Choreographer has finished.
- User Action: None.
- 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: None.
- 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.