Aracılığıyla paylaş


How to: Delegate Application System Behavior to Members

In System Designer, you can specify which member provides or consumes behavior for an application system. You can perform this task by delegating that system's endpoint behavior to its members. This action copies the endpoint from the system definition's boundary to the member, creates a proxy endpoint on the system definition, and connects the proxy endpoint to the new member endpoint.

Note

Your system definition must have an endpoint before you can delegate its behavior to a member. For more information, see How to: Add Endpoints to Application Systems. You can also expose member behavior outside of a system, if that member already has an endpoint. For more information, see How to: Expose Behavior of Members in Application Systems.

Before you can successfully validate a particular system definition for deployment, you must eventually delegate endpoint behavior on that system definition and on all systems included in that system definition.

To delegate application system behavior to a member

  1. On the system definition's boundary, click the endpoint whose behavior you want to delegate.

  2. On the Diagram menu, click Delegate.

    The Delegate Behavior to System Member dialog box appears. Under Delegate to, the Application/System list displays available members.

  3. From the Member list, select a compatible member to delegate the endpoint's behavior, and click OK.

    Note

    You can complete this task only by selecting a compatible member. To display only compatible members, select the List compatible members only box (if not already selected).

    The endpoint whose behavior you delegated now appears on the member. A proxy endpoint appears on the system definition. A connection appears between the proxy endpoint and the member endpoint.

    Tip

    You can also press the ALT key and drag a delegation from the system endpoint to the member.

See Also

Tasks

How to: Add Members to Application Systems

Concepts

Delegation and Exposure of Application System Behavior