You have access to debug for analyzing issues within the replication project. By examining logs and error messages, you can identify root causes. The option to export the replication project generates a comprehensive package of the project's configuration, logs, and diagnostics, in a .zip file making it easier to share for further analysis.
Debug a replication project
When you enable debugging, project and SQL statement warnings, errors, and other details are collected for all kernel and listener processes on all runtime servers used by the project or for a single runtime server in the project, depending on how you configure debugging. The details are written to kernel logs, which are text files located in the software install kernel subdirectory on the runtime engine.
- Navigate to IntegrationContinuous Replication.
- Click the ellipses next to the project you wish to validate, then select Debug from the dropdown menu.
- The Debug Project dialog opens with the project name, description, and additional information about the runtime engine.
- Select one or all of the following options:
- Standard: View general replication project information.
- SQL: View specific information about SQL statements.
- Both: View debugging information about Standard and SQL.
- None: No debugging information is written to the kernel logs.. This is the default value.
- Click OK to save your debug selection and close the dialog.
Export project
- Navigate to IntegrationContinuous Replication.
- Select the project name check boxes that you want to export.
- Click the Export selected projects.
- Choose All projects or Selected projects to export.
- Check the Export user names option to export user names.
- Choose a zip file for export and click Export. Note: If only one project is selected for export, the default value is <ProjectName>-MMDDYYYY-HHMMSS. If more than one project is selected for export, the default value is ConnectConfiguration-MMDDYYYY-HHMMSS.Warning: You cannot export if the File name field is blank.