3.3 How to Use Designer

3.3.1 Designing New Solutions

  1. Launch Designer.

  2. Using the New Project Wizard, open or create a project.

  3. Drag and drop items from the Modeler Palette.

  4. Edit the items’ settings and configurations (for example, names, IP addresses, and passwords).

  5. Using the Policy Builder and other policy editors, write a policy for sharing data between systems.

  6. Check your work.

  7. Use the Document Generator to generate project documentation, and review the documentation with others.

  8. Deploy the project to live systems.

3.3.2 Redesigning Existing Solutions

  1. Launch Designer.

  2. Open or create a new project.

  3. Import Identity Management elements (drivers, driver sets) from working directories.

  4. Edit the element settings and configurations (for example, names, IP addresses, and passwords).

  5. Using the Policy Builder and other policy editors, write a policy for sharing data between systems.

  6. Check your work.

  7. Use the Document Generator to generate project documentation, and review the documentation with others

  8. Deploy the project back to live systems.

3.3.3 Working on Live Systems

The fundamental model/paradigm of Designer is to import solutions, configure them locally in the Designer environment, and then deploy when a solution is ready. This approach was taken to optimize the experience for the following:

  • Off-line work

  • Highly productive development

  • A safer model of configuring and testing before touching your live system

The tool is aimed at developers and architects as the primary audience.

For convenience, Designer enables you to do key operations that a developer typically needs to do, so that the developer can be effective: browse live trees, check driver status, start/stop drivers, and configure driver security. Functionality in the Live Operations options takes immediate effect on the end systems. These operations are clearly grouped in the Designer UI, so that you can tell if you’re doing something live.