To determine how a selected element is used by other elements on the server, you can find dependents of the selected element. A dependent is an element that uses a selected element. For example, suppose that the flow service ServiceA invokes the flow service receivePO. The ServiceA service uses the receivePO service. This makes ServiceA a dependent of the flow service receivePO. If you delete receivePO, ServiceA will not run.

During debugging, you might want to locate all of the dependents of a given service or IS document type. Or, before editing an IS document type, you might want to know what elements, such as specifications, webMethods Messaging Triggers, or flow services, will be affected by changes to the IS document type.

In addition to finding a dependent IS element, Designer also finds the Dynamic Server Pages (DSPs) that depend on the service. For example, suppose that the DSP page myPage.dsp resides in Integration Server_directory \instances\instance_name\packages\myPackage\pub and uses the service myFolder:submitMyPage. If you find dependents for the myFolder.submitMyPage service, Designer also returns the following as a dependent:

Integration Server_directory \instances\instance_name\\packages\myPackage\pub\myPage.dsp