Business object probes have a close relationship with both business objects and the collaboration template. The following sections describe the impact of this inter-dependency on those components.
For more information on business probes, see the Collaboration Development Guide.
When updating the business object probe after deploying the collaboration template and collaboration objects to the server, you must redeploy to validate to the server.
When deleting the collaboration template, the associated business object probes are deleted as well. However, the server does not delete the associated business object probe run time data records in CxReposBOPInstanceData, CxReposBOPAttributeData and CxReposBOPAttributeLargeData. You can delete these records manually using System Monitor.
When changing business object probe information, you must update the collaboration template. The server deletes the old collaboration template information and inserts the new collaboration template. You can manage any historical business object probe data manually using System Monitor.
When deleting a business object probe, historical business object probe run-time data remains in the table (CxReposBOPInstanceData, CxReposBOPAttributeData and CxReposBOPAttributeLargeData). You can manage this historical data manually using System Monitor.
When deleting a business object, the server does not delete the associated business object probes. If a record exists for the business object in the table, the server displays a message warning that once you delete the existing business object, you will not be able to restructure the business object instance.
Updating a business object definition by deleting attributes or changing attribute names affects business object probes. To avoid problems, update and re-deploy the collaboration template.