After the dataflow designer designs your data flow model, the metaverse planner plans the
Microsoft\u00ae Identity Integration Server (MIIS) 2003 metaverse. During this process, the
metaverse planner transforms the information contained in the dataflow design document from a
logical view of the metadirectory to a physical design, producing a metaverse design
specification that will be used by the rules planner to complete the rules document.

Overview of Metaverse Planning.............................................. ................3 Metaverse Concepts............................................................................. ....6 Process Steps for Planning the Metaverse....................................... .......14 Summary................................................................. ..............................36

Planning the
Metaverse for
MIIS 2003

Overview of Metaverse Planning.............................................. ................3
Metaverse Concepts............................................................................. ....6
Metaverse Schema.......................................................................... ..6

Attribute Flow Rules................................................... .....................12
Determining Precedence Order..................................... ..................12
Impact of Flow Rule Changes on Precedence..................................13

Preparing for Metaverse Planning...................................................16
Step 1: Collect Your Planning Documents and Worksheets..............17
Step 2: Review How to Choose Names for Object Types and Attributes

Refining the Dataflow Design........................................... ...............19
Step 3: Establish Object-Level Policies............................................20
Step 4: Establish Outbound Flow................................................ .....23
Step 5: Establish Metaverse Attributes........................................... .24
Step 6: Establish Inbound Flow.......................................................26

Reviewing and Refining Your Decisions...........................................28
Step 7: Review All Precedence Policies....................................... .....29
Step 8: Review and Adjust Outbound Transformations....................29
Step 9: Review and Adjust the Join Attributes.................................33
Step 10: Consider Storage Limits................................... .................34
Step 11: Complete the Metaverse Attribute Design worksheet.......35
Step 12: Document the Reasons for Your Changes..........................35

The dataflow model \u2014 that is, the logical metadirectory design \u2014 is a set of policies that you
need to implement in order to achieve your solution proposal. The design of a system dataflow
model that was presented in the previous topic is a complete design of the object types and
attributes that are required to meet your business objectives. However, you can implement that
logical design in different ways, resulting in solutions that do the same job but have different
characteristics for storage, performance, and coding.

One important task of metaverse planning is to turn related policies into a plan that describes the
required metaverse objects and attributes, and their related flow rules, in order to address your
identified requirements. The primary task of the metaverse planner is to analyze the gathered
policies and determine the most appropriate implementation of the metaverse plan, turning the
logical design into an efficient physical design \u2014 preferably, the optimal design.

Dataflow design policies are simple statements of the business requirements that are defined in your solution proposal and that drive the functional requirements of the solution. The dataflow design policies are at a logical level, rather than a physical level. You refine each statement so that it evolves into a precise policy of your business requirements. After you implement these policies, more specifically, after you plan and implement the metaverse and synchronization rules, the policies become physical level.

As you design the dataflow model (or metadirectory design), the policy evolves into a
statement of your functional requirements: \u201cContracted labor will not be included in the
metadirectory\u201d or \u201cContracted labor will be provisioned to the telephone system but not
human resources.\u201d

During the current design stage \u2014 the metaverse design stage \u2014 you refine the statement to
become a physical-level policy. Assuming you took the first choice at the logical level, the
business policy might become: \u201cContracted labor will be excluded by the WHERE clause of
the delta import View in Lotus Notes\u201d or \u201cContracted labor will be trapped by a Connector
Filter on the Lotus Notes management agent.\u201d

The collection of such policies guides the design of the metaverse and the synchronization rules.
Unlike the dataflow designer, the metaverse planner must be aware of technical issues, such as
the maximum row length in the HR SQL Server database table; the planner modifies the
worksheets that were started earlier in the design process to reflect any changes made due to
technical considerations. The major factors to consider are: