This procedure describes how to run a dynamic assembly simulation.
About this task
The Dynamic Assembly Simulator wizard is accessed from the Create
menu and enables you to specify the following items:
- Fabric project
- Namespace
- Label description (optional) - this field enables you to describe your
simulation and what it does.
- Dynamic Assembly Component (DAC) - this is selectable from a list of all
visible DACs.
- There is also a special entry for the Fabric Hub. The Context Specification
that will be used for the new simulation is either the Fabric Hub Context
if the Fabric Hub was selected for the DAC, or the Context Specification that
is associated with the DAC that was selected. You can view or edit this for
a DAC by using the DAC editor.
There are currently four supported simulation operations:
- Build policy context.
- Build selection policy.
- Find candidates.
- Select endpoint.
Detail Views
The Detail view has a General tab and
an Error tab. All detail views display the name of the DAC and the operation
in the upper left. The Errors tab lists all errors that occurred during that
operation.
The detailed views support the following operations:
- Merged Policy - This operation enables you to see what policy each assertion
came from, and the values associated with it. Clicking the policy link takes
you to the policy editor for that policy. Clicking the assertion type takes
you to the Assertion Type editor.
- Find Candidates - This operation employs three tabs:
- Candidate Endpoints displays endpoints that matched the policy
in the previous operation and their tier. Clicking the endpoint takes you
to the editor for that endpoint.
- Rejected Endpoints contains all the endpoints that were discarded
and the reason they were discarded. Clicking the endpoint take you to it’s
editor.
- Select Endpoint employs other tabs. If an endpoint was selected,
you would see it in an individual tab (not in the screen shot). You are able
to click the endpoint to get to its editor. The Propagated Policy tab contains
a view of the propagated policy, it is similar to the Composite Policy tab.
- Rejected Candidates - Rejected Candidates lists all possible candidates
that were not selected.
The following is a description of each tab by operation.
- Build Policy Context
- General – General statement regarding what Build Policy Context means
- Errors
- Build Selection Policy
- Composite Policy – Contains a list of all the assertions used in the simulation
as well as what policy the assertion came from and the values used during
the simulation.
- Errors
- Find Candidates
- Candidate Endpoints – Table of endpoints that meet the criteria from the
built selection policy as well as their tier. Tier is an integer value starting
at zero. Endpoints with a lower tier value are selected. Endpoints with the
same tier value will round-robin at runtime.
- Rejected Candidates – Endpoints that could service the request but were
rejected because of the selection policy. For your simulation, there are going
to be endpoints that support the specified interface. There are several reasons
why an Endpoint can be rejected at this phase including: Unsupported Address
Type, Filtered by Selection Policy, Filtered by Endpoint Requirement.
- Errors
- Select Endpoint
- Selected Endpoint – This tab only displays if there was a selected endpoint
and no error during this operation. It displays a link to the selected endpoint.
- Propagated Policy – This tab shows the policy that would be propagated
to the endpoint. This is configured using the Propagate Policy assertion.
This assertion states that an endpoint should receive a specific subset or
all of the selection policy. This result lets you see what policy data is
sent to your endpoint.
- Rejected Candidates – Displays a list of endpoints that were not selected
and the reason for not selecting them.
- Errors
To run a dynamic assembly simulation, complete the following steps: