Project Design Tutorial : Analyze and Validate the Project

Analyze and Validate the Project
In this task, you check the project for errors. If you have configured it correctly, you’ll see warnings but no errors. Warnings indicate potential issues, such as absence of default events. It’s always worth checking them. In the FraudDetection project, the warnings do not indicate any actual issues.
Learning Points
How can I validate that there are no basic errors in my code? To perform checks that don’t take project logic into account, use Project > Validate.
What if there are problems in my code?  You can debug it. BusinessEvents builds on the Eclipse debugger features to provide additional checks. Developers familiar with the Eclipse debugger will find it intuitive to use.
How can I analyze that the logic of my project is OK? For this kind of checking you use Project Analyzer or the Element Diagram or both. They work together to provide insights into your project. Project Analyzer is a document generated in the Problems view area. Element Diagram provides a visualization of the whole project or of selected project elements. It also shows all dependencies in a project. Project Analyzer and Element Diagram can be configured to run separately or together, using preferences.
How can I visualize different aspects of a project?  BusinessEvents provides diagrams similar to UML sequence diagrams, class diagrams, and dependency diagrams. They are modified a little from the strict UML to be more useful in the context of TIBCO BusinessEvents Monitoring and Management.
How can I change the names of project resources, or move them around?  Use the refactoring features. They ensure that changes you make are reflected throughout the project (with certain limitations).
More Information
In TIBCO BusinessEvents Developer’s Guide, see these sections:
Chapter 23, Testing and Debugging Projects in TIBCO BusinessEvents Developer’s Guide
Task Q Analyze and Validate the Project
1.
In Studio Explorer, highlight the project name, then from the top menus select Project > View. You see the project visualization in the main editor window.
You can see the dependencies and relationships between the project resources. You can jump to a resource editor by clicking the resource’s icon.
2.
The Type columns shows the type of check that resulted in the warning. You can sort by any column. Here are some warnings taken during project development. They are sorted by Resource and some columns are sized smaller to make others more visible.
3.
Close the FraudDetection.projectview tab. Diagrams are not saved. They are generated when needed.
Summary and Next Steps
Now you are ready to configure the Cluster Deployment Descriptor (CDD) and build the archive for deployment.