You can add profiling processes to any Quality project to profile output from Quality processes and analyze real and dynamic input data. The processes generate an output entity off of which other profiling processes can be added and run.
You can use one or more of the following profiling processes in a project:
- Analysis. Allows you to analyze attributes as part of a Quality process flow in the Control Center and in an exported batch script.
- Business Rules. Allows you to analyze entity business rules in a real input entity and view passing and failing rule results.
- Dependencies. Creates permanent dependencies on real input entities. Double-click the output entity to view rows that contain conflicts.
- Keys. Creates permanent keys on real input entities. Double-click the output entity to view rows that contain duplicate keys.
- Load. Allows you to analyze attributes in the output entity of a process, as well as discover keys and dependencies, re-analyze new or updated entity business rules, and load data into a dynamic entity.
- See other ways to use profiling processes:
-
- Create an empty Quality project, add profiling processes to it, then copy it
to the Project Library and use it as a profiling process template for future
projects. Note the following:
- Projects containing Business Rules processes cannot be copied to the Library.
- Analysis processes cannot be copied to the Library.
- Dependencies and Keys processes copied to the Library must have a Load process as input, and the Load process must also be copied to the Library.
- Add an Analysis process to the profiling workflow to create a Time Series Analysis project, then run the project to re-analyze the source data when it is updated or changed. This helps to track trends in your data over time and helps ensure your standards.
- Create an empty Quality project, add profiling processes to it, then copy it
to the Project Library and use it as a profiling process template for future
projects. Note the following:
Guidelines
- Batch only. The profiling processes are designed for batch only and cannot be deployed in a real-time environment. If a real-time project includes a profiling process, the process will be excluded when the project is deployed for use in real time.
- Add as branch only. You add profiling processes as a branch, they cannot be inserted into an existing project workflow.
- Deleting. If you delete a profiling process, the metadata generated when you ran the process (such as keys and dependencies) does not get deleted.
- Non-profiling Quality processes cannot follow a profiling process.
- Running in background not supported. Projects that contain profiling processes cannot be run in the background. You will be alerted to this when you add a profiling process to a Quality project.
- Using Pipes. The profiling processes do not take or generate piped output. Therefore, when you run a profiling process, or a project that includes profiling processes, using the Use Pipes option, the process that precedes the profiling process will generate a file and all profiling processes will generate an output file. (Pipes behavior differs in projects that do not include profiling processes, where data moves from process to process without creating interim output files.)
Note: To use pipes with profiling processes, the repository or system administrator must
first configure the repository. For information, see Configuring Repositories to use Profiling Processes
with Pipes.
-
Exporting. Note the following when exporting projects that include profiling
processes (except for Analysis):
- Because profiling processes are run on data specific to a repository, any exported Quality projects that include profiling processes cannot be imported into a different repository.
- After exporting a project that includes profiling processes, do not delete the original project; the exported processes retain a connection to the processes in the original project and are dependent on access to the original project in the original repository.
- Exported Quality projects with profiling processes can be exported for batch jobs, but the batch jobs cannot be used on another system.
- In Trillium-authenticated security environments, after you export a profiling project to a batch script, the repository administrator must edit the export batch script to include his or her password before the script can be run. These credentials are necessary for the export to run successfully. This does not have to be done if you use Window-authenticated security. For details, see Running a Batch Project.