- CWWIC0000E: The XML input file at {0} was not parsed.
- Explanation: The processing of the XML file at the specified location cannot continue. A likely reason for the problem is that the input file does not exist or is not in the correct location, or that the XML code in the file is not valid.
- User Action: If you cannot locate the file, create a valid XML file and place it in the expected location. If the file exists, open it in a Web browser to check that the XML code is valid. If the XML code is not valid, the file does not open properly in the browser. Fix the XML code. If the file exists and the XML code is valid, but the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC0001E: The XML input string {0} was not parsed.
- Explanation: The processing of the specified XML string cannot continue. A likely reason for the problem is that the XML code in the string is not valid.
- User Action: Fix the XML code for the input string. If the XML code is valid, but the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC0002E: The XML file from the class InputStream cannot be parsed.
- Explanation: Template and conversion files that specify translation rules are used when translating WebSphere InterChange Server XML to WebSphere Process Server Java snippets. The default template or conversion files packaged with the migration tool cannot be read.
- User Action: Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC0003E: The data {1} cannot be written to the file {0}.
- Explanation: The problem might be that the destination directory does not have write access.
- User Action: Change the permission on the directory of the destination file to give the user write access. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC0004E: The XML document cannot be serialized.
- Explanation: The processing of the XML document into a string cannot continue. A likely reason for the problem is that the input document is empty or is not valid.
- User Action: Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC0005E: The XML document cannot be serialized to the file {0}.
- Explanation: The processing of the XML document to a file cannot continue. A likely reason for the problem is that the XML document is not valid or the target directory does not have write permission.
- User Action: Change the permission on the directory of the target file to give the user write access. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC0006E: The reposMigrate command is missing required arguments.
- Explanation: The two required arguments for the reposMigrate command (the input .jar file and the output directory) are missing from the command line.
- User Action: Specify the locations for the input .jar file and the output directory, and run the reposMigrate command again.
- CWWIC0007E: The -td flag of the reposMigrate command does not have the required directory argument.
- Explanation: The template directory flag (-td) was specified, but it did not include the required directory as an argument.
- User Action: Specify the location of the template directory, then run the command again.
- CWWIC0008E: The flag {0} is unknown.
- Explanation: The specified flag is not a recognized option of the reposMigrate command.
- User Action: Run the reposMigrate command again without the specified flag. For information on the valid flags for the reposMigrate command, execute the reposMigrate command without any parameters. The returned display lists the valid arguments.
- CWWIC0009E: The argument {0} is unknown.
- Explanation: The specified argument is not recognized by the reposMigrate command.
- User Action: Run the reposMigrate command again without the specified argument. For information on the valid arguments for the reposMigrate command, execute the reposMigrate command without any parameters. The returned display lists the valid arguments.
- CWWIC0010E: The wizard parameter {0} is unknown.
- Explanation: The WebSphere Integration Developer wizard passed a migration parameter to the migration code that was not valid.
- User Action: Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC0011E: The following unexpected exception occurred during the migration process: {0}
- Explanation: An unexpected exception occurred during the migration process.
- User Action: Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC0012E: The directory {0} cannot be found.
- Explanation: Two directories are used during migration: a temporary directory that contains the WebSphere InterChange Server source files and an output directory that contains the migration output. Within the migration tool, the values of these two directory paths are empty.
- User Action: Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC0013E: The directory {0} was not created.
- Explanation: Two directories are used during migration: a temporary directory that contains the WebSphere InterChange Server source files and an output directory that contains the migration output. One of these directories or its subdirectories cannot be created. A likely reason is that the parent directory of the specified path has incorrect permission.
- User Action: Change the permission on the parent directory of the specified path to grant user access. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC0014E: The file {0} was not deleted.
- Explanation: A temporary directory that contains the WebSphere InterChange Server source files cannot be deleted. A likely reason is that the user access changed during migration, or the specified file was deleted by another user or program during migration.
- User Action: Give the user access and delete the temporary directory. Run the migration process again. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC0015E: The directory {0} was not deleted.
- Explanation: A temporary directory that contains the WebSphere InterChange Server source files cannot be deleted. A likely reason is that the user access changed during the migration or the directory was deleted by another user or program during migration.
- User Action: Give the user access and delete the temporary directory. Run the migration process again. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC0016E: The source directory {0} was not copied to {1}.
- Explanation: The source directory, the target directory, or both have incorrect permission, so the source directory cannot be copied to the target directory.
- User Action: Change the permission on one or both directories.
- CWWIC0017E: The source file {0} was not copied to {1}.
- Explanation: The source file, the target file, or both have incorrect permission, so the source file cannot be copied to the target file.
- User Action: Change the permission on one or both files.
- CWWIC0018E: The contents of the file {0} cannot be extracted to the directory {1}.
- Explanation: The problem might be that the .jar file is corrupted or that the target directory has incorrect access.
- User Action: Check the .jar file to make sure it is well-formed and modify it if necessary. Change the access of the target directory if it does not already have write access. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC0019E: The contents of the directory {0} cannot be archived to the file {1}.
- Explanation: At the end of the migration process, all the migration-generated files are packaged into one or more .jar files. The problem might be that the contents of the directory are corrupted or that the directory is empty.
- User Action: Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.Make sure that the contents of the specified directory are valid.
- CWWIC0020I: The input repository {0} is being read.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0021I: The input repository has been read successfully.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0022E: No artifacts were found in the input repository.
- Explanation: The input repository must contain at least one artifact.
- User Action: Place at least one artifact in the input repository.
- CWWIC0100I: The following business objects were found in the input repository: {0, number, integer}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0101I: The following relationships were found in the input repository: {0, number, integer}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0102I: The following maps were found in the input repository: {0, number, integer}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0103I: The following collaboration templates were found in the input repository: {0, number, integer}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0104I: The following collaboration objects were found in the input repository: {0, number, integer}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0105I: The following connectors were found in the input repository: {0, number, integer}
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0106I: The following database connections were found in the input repository: {0, number, integer}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0107I: The following schedules were found in the input repository: {0, number, integer}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0108I: The following business object is being migrated: business object {0, number, integer} of {1, number, integer}: {2}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0109I: The following relationship is being migrated: relationship {0, number, integer} of {1, number, integer}: {2}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0110I: The following map is being migrated: map {0, number, integer} of {1, number, integer}: {2}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0111I: The following collaboration template is being migrated: collaboration template {0, number, integer} of {1, number, integer}: {2}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0112I: The following collaboration object is being migrated: collaboration object {0, number, integer} of {1, number, integer}: {2}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0113I: The following connector is being migrated: connector {0, number, integer} of {1, number, integer}: {2}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0114I: The following database connection is being migrated: database connection {0, number, integer} of {1, number, integer}: {2}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0115I: The following schedule is being migrated: schedule {0, number, integer} of {1, number, integer}: {2}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0116I: The artifact {0} has been migrated successfully.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0117E: The migration failed for {0}.
- Explanation: The specified artifact failed to migrate successfully.
- User Action: Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC0118I: The migration of the modules is completing.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0119I: The migration is complete.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0120E: While parsing data for an adapter configuration, the migration utility encountered a format that is not valid. Data in a format that is not valid: {1}. Expected format: {2}.
- Explanation: The artifact that is migrated contains data that is in a format that is not valid.
- User Action: Change the format of the data to match the expected format that is referenced in the error message.
- CWWIC0200I: The migration utility is migrating the InterChange Server repository.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0201I: The migration utility is copying artifacts to the target library.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0202I: The migration utility is creating the module {0}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0203I: The migration utility is copying artifacts to the module {0}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0204I: The following options were set for the {0} connector: target binding = {1}; generate skeleton data handler = {2}.
- Explanation: This is an informational message.
- User Action: No action is required.
- CWWIC0300E: The following exception was thrown during the parsing of customized code: {0}
- Explanation: An exception was thrown while trying to parse the WebSphere InterChange Server Java snippet code into XML. Common errors are the inclusion of static variable declarations and inner class definitions.
- User Action: Change the customized code to follow the WebSphere InterChange Server migration best practices and run the migration again, or set the "Warn in case of Java parsing errors" flag during migration to treat the Java parsing errors as warnings.
- CWWIC0302W: Interface declarations are not allowed in custom snippets.
- Explanation: According to the WebSphere InterChange Server migration best practices, custom snippets cannot have interface declarations.
- User Action: Remove the interface declaration from the custom snippet and run the migrate again, or migrate the WebSphere InterChange Server repository file using the "Warn in case of Java parsing errors" flag, and modify the resulting snippets in the Business Process Execution Language (BPEL) components or map components so that they no longer use interface declarations.
- CWWIC0303W: Class declarations are not allowed in custom snippets.
- Explanation: According to the WebSphere InterChange Server migration best practices, custom snippets cannot contain class declarations.
- User Action: Remove the class declaration from the custom snippet and run the migration again, or migrate the WebSphere InterChange Server repository file using the "Warn in case of Java parsing errors" flag, and modify the resulting snippets in the Business Process Execution Language (BPEL) components or map components so that they no longer use class declarations.
- CWWIC0304W: Method declarations are not allowed in custom snippets.
- Explanation: According to the WebSphere InterChange Server migration best practices, custom snippets cannot contain method declarations.
- User Action: Remove the method declaration from the custom snippet and run the migration again, or migrate the WebSphere InterChange Server repository file using the "Warn in case of Java parsing errors" flag, and modify the resulting snippets in the Business Process Execution Language (BPEL) components or map components so that they no longer use method declarations.
- CWWIC0305W: A static initializer is not allowed in custom snippets.
- Explanation: According to the WebSphere InterChange Server migration best practices, custom snippets cannot contain static initializers.
- User Action: Remove the static initializer from the custom snippet and run the migration again, or migrate the WebSphere InterChange Server repository file using the "Warn in case of Java parsing errors" flag, and modify the resulting snippets in the Business Process Execution Language (BPEL) components or map components so that they no longer use static initializers.
- CWWIC0306W: An instance initializer is not allowed in custom snippets.
- Explanation: According to the WebSphere InterChange Server migration best practices, custom snippets cannot contain instance initializers.
- User Action: Remove the instance initializer from the custom snippet and run the migration again, or migrate the WebSphere InterChange Server repository file using the "Warn in case of Java parsing errors" flag, and modify the resulting snippets in the Business Process Execution Language (BPEL) components or map components so that they no longer use instance initializers.
- CWWIC0307W: The "static" modifier is not allowed in custom snippets.
- Explanation: According to the WebSphere InterChange Server migration best practices, custom snippets cannot contain "static" modifiers.
- User Action: Remove the "static" modifier from the custom snippet and run the migration again, or migrate the WebSphere InterChange Server repository file using the "Warn in case of Java parsing errors" flag, and modify the resulting snippets in the Business Process Execution Language (BPEL) components or map components so that they no longer use "static" modifiers.
- CWWIC0308W: The "final" modifier is not allowed in custom snippets.
- Explanation: According to the WebSphere InterChange Server migration best practices, custom snippets cannot contain "final" modifiers.
- User Action: Remove the "final" modifier from the custom snippet and run the migration again, or migrate the WebSphere InterChange Server repository file using the "Warn in case of Java parsing errors" flag, and modify the resulting snippets in the Business Process Execution Language (BPEL) components or map components so that they no longer use "final" modifiers.
- CWWIC0309W: The "transient" modifier is not allowed in custom snippets.
- Explanation: According to the WebSphere InterChange Server migration best practices, custom snippets cannot contain "transient" modifiers.
- User Action: Remove the "transient" modifier from the custom snippet and run the migration again, or migrate the WebSphere InterChange Server repository file using the "Warn in case of Java parsing errors" flag, and modify the resulting snippets in the Business Process Execution Language (BPEL) components or map components so that they no longer use "transient" modifiers.
- CWWIC0310W: The "volatile" modifier is not allowed in custom snippets.
- Explanation: According to the WebSphere InterChange Server migration best practices, custom snippets cannot contain "volatile" modifiers.
- User Action: Remove the "volatile" modifier from the custom snippet and run the migration again, or migrate the WebSphere InterChange Server repository file using the "Warn in case of Java parsing errors" flag, and modify the resulting snippets in the Business Process Execution Language (BPEL) components or map components so that they no longer use "volatile" modifiers.
- CWWIC0400E: The following JDBC URL format is either not valid or not recognized: {0}.
- Explanation: The specified JDBC URL must be a valid DB2, MSSQL, or Oracle JDBC URL to be supported by the migration.
- User Action: Change the JDBC URL to a valid DB2, MSSQL, or Oracle JDBC URL for the database.
- CWWIC0500E: The relationship {0} encountered the following error during migration: {1}.
- Explanation: The specified InterChange Server relationship is missing at least one required attribute.
- User Action: In WebSphere Interchange Server Relationship Designer, open the relationship and add the missing attribute. Update the WebSphere Interchange Server repository file with this change and run the migration again.
- CWWIC1000E: The template named {0} cannot be found.
- Explanation: An XML translation template must be used when translating WebSphere InterChange Server XML stored snippets to WebSphere Process Server Java snippets. A default template is provided, but it can be overwritten using the "Template Directory" parameter during migration. Neither the default template nor the custom template can be found.
- User Action: Pass in a directory containing valid templates when using the "Template Directory" parameter during migration. Or use the default XML standard template by omitting the "Template Directory" flag. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1001E: The XML standard template document {0} cannot be loaded.
- Explanation: An XML translation template must be used when translating WebSphere InterChange Server XML stored snippets to WebSphere Process Server Java snippets. A default template is provided but cannot be loaded from the migration package.
- User Action: Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1002E: The XML document {0} contains no valid templates.
- Explanation: An XML translation template must be used when translating WebSphere InterChange Server XML stored snippets to WebSphere Process Server Java snippets. The specified XML document is not a translation template.
- User Action: Pass in a directory containing valid templates when using the "Template Directory" parameter during migration. Or use the default XML standard template by omitting the "Template Directory" flag. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1003E: The custom template directory {0} cannot be found.
- Explanation: An XML translation template must be used when translating WebSphere InterChange Server XML stored snippets to WebSphere Process Server Java snippets. A default template is provided, but it can be overwritten using the "Template Directory" parameter during migration. The directory passed in for the "Template Directory" flag does not exist.
- User Action: Pass in a valid directory with template files to the "Template Directory" parameter.
- CWWIC1004E: The XML conversion template cannot be found.
- Explanation: An XML translation template must be used when translating WebSphere InterChange Server XML stored snippets to WebSphere Process Server Java snippets. The XML type conversion template is packaged with the migration tool but cannot be found.
- User Action: Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1005W: A template named {0} already exists. The new template information will overwrite the existing template.
- Explanation: This is a warning message.
- User Action: No action is required.
- CWWIC1006E: The XML document typesConversion {0} did not load.
- Explanation: An XML translation template must be used when translating WebSphere InterChange Server XML stored snippets to WebSphere Process Server Java snippets. The XML type conversion template is packaged with the migration tool but cannot be loaded.
- User Action: Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1007E: The types conversion rule for XML type {0} cannot be found.
- Explanation: An XML translation template must be used when translating WebSphere InterChange Server XML stored snippets to WebSphere Process Server Java snippets. The XML type conversion template is packaged with the migration tool and contains rules for converting from an XML type to a Java type. The specified XML type conversion rule cannot be found in the types conversion file.
- User Action: The default action of the migration utility is to ignore the type that cannot be found. If the type should not be ignored, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1008E: The types conversion rule for XML type {0} to Java type {1} was not found.
- Explanation: An XML translation template must be used when translating WebSphere InterChange Server XML stored snippets to WebSphere Process Server Java snippets. The XML type conversion template is packaged with the migration tool and contains rules for converting from an XML type to a Java type. The specified XML type to Java type conversion rule cannot be found in the types conversion file.
- User Action: The default action of the migration utility is to ignore the type that cannot be found. If the type should not be ignored, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1009E: The Java type value is not valid: {0}.
- Explanation: An XML translation template must be used when translating WebSphere InterChange Server XML stored snippets to WebSphere Process Server Java snippets. The Java type conversion template is packaged with the migration tool and contains rules for converting from an XML type to a Java type. The specified Java type cannot be found in the types conversion file.
- User Action: The default action of the migration utility is to ignore the type that cannot be found. If the type should not be ignored, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1010E: The XML type value is not valid: {0}.
- Explanation: An XML translation template must be used when translating WebSphere InterChange Server XML stored snippets to WebSphere Process Server Java snippets. The XML type conversion template is packaged with the migration tool and contains rules for converting from an XML type to a Java type. The specified XML type cannot be found in the types conversion file.
- User Action: The default action of the migration utility is to ignore the type that cannot be found. If the type should not be ignored, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1011E: You do not have read privileges to the resource {0}.
- Explanation: The specified resource requires the read level of privilege.
- User Action: Check that the specified resource exists. If it does not exist, create it. If the resource exists, check that the current user has read level privileges, and give the current user read privilege if the level is not correct. If the resource exists, the current user has the correct level of privilege, and the problem persists, refer to the troubleshooting guide on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1015E: The object of type {0} was found, but it is undefined, so it cannot be evaluated.
- Explanation: During the migration of a WebSphere InterChange Server assembly diagram XML snippet to a WebSphere Process Server Java snippet, the InterChange Server snippet is read in for translation. The snippet is an XML document and, while it was read in, an unrecognized XML type was encountered.
- User Action: In WebSphere InterChange Server Process Designer, fix parsing errors found in the snippet. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1016E: The XML snippet fragment is empty.
- Explanation: During the migration of a WebSphere InterChange Server assembly diagram XML snippet to a WebSphere Process Server Java snippet, the InterChange Server snippet is read in for translation. The XML snippet to be translated is either null or empty.
- User Action: In WebSphere InterChange Server Process Designer, fix parsing errors found in the snippet. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1017E: The XML snippet type {0} is not valid.
- Explanation: During the migration of a WebSphere InterChange Server assembly diagram XML snippet to a WebSphere Process Server Java snippet, only XML snippets from collaboration templates and maps can be translated within the migration tool.
- User Action: Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1018E: Because the type {0} is not a valid type to be converted to its primitive, no evaluation occurred.
- Explanation: During the migration of a WebSphere InterChange Server assembly diagram XML snippet to a WebSphere Process Server Java snippet, the migration tool attempts to convert some snippet part types to their primitive equivalents (for example, it tries to convert Integer to int). After retrieving the type from the snippet for translation, the value of the type was changed to null.
- User Action: Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1020E: The snippet that was passed in to the EvaluateSnippetWithTemplateAndTypesConversion constructor is empty.
- Explanation: The snippet class must be instantiated to the currently translated WebSphere InterChange Server snippet.
- User Action: Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1021E: The node passed in to the SnippetHandler createSnippet method is null.
- Explanation: The specified method takes an XML snippet that is a string and places it in a document object. From the document object, a list of all the nodes of the XML formatted string is returned. Each node is used to create the snippet object. However, in this case, a null value was passed into the snippet handler for creation.
- User Action: Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1022E: A child of the type {0} was not found. It is not valid and will not be migrated.
- Explanation: The migration of a WebSphere InterChange Server assembly editor XML snippet to a WebSphere Process Server Java snippet failed because the specified child type is not valid. A likely cause of the problem is that the child type was defined as an unsupported WebSphere Process Server class.
- User Action: Change the child to a supported type or remove the child to be migrated. If the problem persists, refer to the troubleshooting guide on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1025E: The assembly editor XML cannot be converted to Java code because of the following error: {0}
- Explanation: During the migration of a WebSphere InterChange Server assembly diagram XML snippet to a WebSphere Process Server Java snippet, the InterChange Server snippet is read in for translation. However, the snippet cannot be translated because of the specified error.
- User Action: Open the collaboration template or map in Process Designer and check the snippet for errors. If no errors exist and the problem persists, refer to the troubleshooting guide on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC1026W: The constant named {0} cannot be found. {0} will be returned rather than the value.
- Explanation: This is a warning message.
- User Action: No action is required.
- CWWIC1027W: The type of the constant that the parameter {0} references cannot be found. The type of the parameter will be returned.
- Explanation: This is a warning message.
- User Action: No action is required.
- CWWIC2000W: The collaboration object {0} has multiple triggering ports and a correlation set with an Async In operation.
- Explanation: For correlations sets with Async In operations, the migration utility can manage only one triggering port.
- User Action: For correlations sets with Async In operations and multiple triggering ports, manually create and wire the Service Component Architecture components after the migration.
- CWWIC2001E: The referenced collaboration template {1} cannot be found for the collaboration object {0}.
- Explanation: The specified collaboration template does not exist in the WebSphere InterChange Server repository file.
- User Action: Update the WebSphere InterChange Server repository file with the missing collaboration template, or remove the collaboration object if it is unnecessary, and run migration again.
- CWWIC3001E: The WebSphere InterChange Server collaboration template being migrated does not have a defined triggering port.
- Explanation: There must be at least one triggering port when migrating collaboration templates.
- User Action: In Process Designer, open the collaboration template and add a triggering port. If the problem persists, refer to the troubleshooting guide on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/.
- CWWIC3002W: The correlation sets set up for the process {0} might not work as expected.
- Explanation: This is a warning message.
- User Action: No action is required.
- CWWIC4000W: The explicitly bound map {0} cannot be found, so pass-through is assumed.
- Explanation: This is a warning message.
- User Action: No action is required.
- CWWIC4001W: No implicit output map was chosen for the input {0} because multiple qualifying maps were found.
- Explanation: This is a warning message.
- User Action: No action is required.
- CWWIC4002W: No implicit map was chosen to convert business object {0} to business object {1} because multiple qualifying maps were found.
- Explanation: This is a warning message.
- User Action: No action is required.
- CWWIC4003W: The implicit map for converting the business object {0} cannot be found, so the business object will be treated as natively supported by connector {1}.
- Explanation: This is a warning message.
- User Action: No action is required.
- CWWIC5001E: The business object of type {0}, which is referenced by {1}, cannot be found. Event sequencing might not be set up correctly. Validate your input migration jar and the final migrated artifacts to insure that this BO is not required.
- Explanation: Because a child business object definition cannot be found, event sequencing keys cannot be resolved during migration.
- User Action: If event sequencing is not needed, turn it off during migration. If event sequencing is needed, either include the child business object definition in the WebSphere InterChange Server source repository file or remove the child business object definition from the parent business object.
- CWWIC5002W: The business object of type {0}, which is referenced by {1}, cannot be found. Validate your input migration jar and the final migrated artifacts to insure that this BO is not used.
- Explanation: A child business object definition cannot be found. The input migration jar needs to be validated prior to migration or if the child BO is not used then remove the child business object definition from the parent business object
- User Action: Validate your input migration jar and the final migrated artifacts to insure that this BO is not used. Either include the child business object definition in the WebSphere InterChange Server source repository file or remove the child business object definition from the parent business object.