Setting up a development environment where you can test, analyze, and develop your Identity Manager solution allows you to learn about each component of Identity Manager and find unforeseen issues that can arise. For example, when you synchronize information between different systems, the information is presented differently for each system. Changing the data to see how it synchronizes between these two systems allows you to see if this change affects other systems that use this same information.
Another major reason to set up a development environment is to make sure your solutions work before you apply them to live data. Identity Manager manipulates and deletes data. Having the test environment allows you to make changes without any loss to the data in your production environment. When you start the project with a reasonable deployment order, it allows you to gain significant value quickly, and helps you evaluate the changing needs of your implementation over time. This allows you to develop your environment for best performance and scalability. For example, you can start with deploying self-service and password management, and then follow it with other capabilities. This enables your organization to incrementally verify that the functions and capabilities of Identity Manager are installed, configured, and tested as expected before they are introduced to your production environment. Phased roll-out helps to deliver manageable change to your organization.
You use Designer to create a project plan that includes the business information as well as the technical information. It allows you to develop, test, and then deploy your solution in stages from the test environment to the production environment. For more information about Designer, see NetIQ Designer for Identity Manager Administration Guide.
Development: The implementation team develops detailed configurations for the solution based on the results of the previous phases of the life cycle. The solution is developed in a controlled environment that represents a production environment but is not actually a production environment. The implementation team develops installation and configuration scripts or procedures, builds detailed product and tool configurations, and prepares the required documentation and performance metrics. Supporting processes and organizational changes required by the identity management solution are the outcome of this stage. To set up your development environment, use the information in Section 1.0, How Identity Manager Solves Business Challenges. It is an installation checklist of all of the Identity Manager components. Use this list to make sure you have installed and configured all components for Identity Manager that you can use to develop a project plan. Use the information in Section 11.0, Technical Guidelines as you set up your development environment, so you can learn about technical considerations as you install and configure each component of Identity Manager.
Testing: The implementation procedures are validated in a controlled environment. The environment must qualify to test all aspects of the design prior to the production deployment. For example, the implementation team can apply a pilot project to a subset of the systems and applications in a production environment. This allows the team to make adjustments with minimal impact to your operations. Based on the outcome of the tests, the deployment team makes all required adjustments to either the implementation procedures or to the design, and then revalidates the procedures and configuration.
Deployment: The new design is fully deployed in the production environment. The implementation team uses the results of the testing stage to create an enterprise-wide plan. Any pending equipment procurement is finalized in this stage. The metrics developed in the development stage should be used to measure the success of the implementation. Towards the end of the initial deployment and before handing over to formal production, impart the required training for the operations and support staff. When deployment is completed, your organization will have a fully functional and documented production environment.
After the plan is implemented you are likely to make adjustments to the implementation due to organizational changes, performance issues, new technologies, or other factors. When you make adjustments to the plan, document the changes as part of a change control system that can be accessed and referenced by the appropriate members of the project team.