In a large enterprise environment, a pilot project may need to be conducted before upgrading to the new Active Roles. In a pilot project, you deploy components of the new version in your production environment side-by-side with the existing installation of the components you are going to upgrade, evaluate the results, and fix problems.
Normally, a pilot project is conducted with a small group of users in the production environment where select individuals perform particular tasks using the new Active Roles version. This demonstrates that the new version works as expected and that it meets the organization’s requirements.
A pilot project is a deployment of the new Active Roles version to a subset of the user group. Those who do not participate in the pilot project perform their regular, daily work using the earlier Active Roles version. This requires that the earlier version be up and running in the production environment side-by-side with the pilot deployment.
When the pilot project is deemed successful and ready for production, you can upgrade your existing production components to the new version.
Deploying a pilot project involves the following steps:
These steps are discussed in the sections that follow.
When deploying your pilot instance of the Administration Service, you need to ensure that it has the same configuration as your production instances of the Administration Service. You can achieve this as follows:
You can install the Administration Service of version Active Roles side-by-side with the Administration Service of version 6.9, on the same computer. Another option is to install the new Administration Service on a different computer.
You can import the configuration data using the Import Configuration wizard provided by Configuration Center. On the Source Database page in the Import Configuration wizard, specify the database used by your production Administration Service of the earlier Active Roles version. For detailed instructions, see Steps to deploy the Administration Service earlier in this document.
Optionally, you can import the management history data from the database of your production Administration Service, in addition to the configuration data (see Steps to deploy the Administration Service earlier in this document).
When performing a pilot deployment, you may want to have the new Administration Service version installed on a server running a newer version of the Windows operating system. Additionally, you may need the database of the new Administration Service to be hosted on a newer SQL Server version. You can meet these requirements as follows:
Once you have deployed the pilot Administration Service and updated its configuration, you can deploy the Web Interface for your pilot project. You have to ensure that your pilot instance of the Web Interface meets the following conditions:
You can address these conditions as follows:
You can identify your existing site configuration objects by using the Web Interface Sites Configuration wizard on the computer running your production Web Interface. For detailed instructions, see Upgrading the Web Interface earlier in this document.
You can install the Web Interface of version Active Roles side-by-side with the Web Interface of version 6.9, on the same computer. Another option is to install the new Web Interface on a different computer.
Optionally, delete the default sites that were created when you configured the Web Interface in Step 2. The default sites are unaware of your existing site customizations, and have the default configuration of menus, command, forms and other elements. For instructions on how to delete the default Web Interface sites, see Upgrading the Web Interface earlier in this document.
You need the Active Roles console of version 7.2 if you want the console to connect to the Administration Service of version Active Roles. As the console of version 7.2 does not connect to the Administration Service of earlier versions, the use of the console version Active Roles for your pilot project ensures that the console automatically connects to the pilot Administration Service.
For installation instructions, see Steps to install the console earlier in this document.