Promote Project
You use Promote Project when you want to activate a project from one cluster to another. This might be required where you have separate clusters for test and production work. You create and test projects on the test cluster and then activate them to the production cluster when the project is ready to go live. Since activation is usually between clusters on different sites, you may hear this type of activation referred to as site to site activation.
You can also use Promote Project to activate projects over the internet when you do not have a direct connection to your cluster.
Email settings note
Email settings are not overwritten when a promoted project already exists on the destination cluster, and email settings are already defined for the project on the destination server. However, the source cluster’s email settings are retained (after promotion) when a project on the destination cluster does not include defined email settings.
Starting Promote Project
Select the project you want to activate and click Promote Project.
The Promote Project login dialog box is displayed.
Logging in to the destination server
In order for activation to work, you must be logged in to the Activate component on your current computer and the destination computer. When you start Promote Project, you must log in to the destination computer – that is, the project management server to which you want to activate.
The first time that you use Promote Project, you must complete all the fields on the login dialog box, but the values you used the previous time are filled in (except the password).
1 In Destination Server or UNICOM Intelligence URL, do one of the following:
▪If you are connected to your local network, type the name of the project management server on the cluster you want to activate to.
▪If you are not connected to your local network, you can activate across the internet by typing the URL for UNICOM Intelligence Interviewer Server - Admin on the cluster to which you want to activate.
2 In Destination User Name, enter the user name that you want to use for logging in on the destination server. In many cases, this will be the same as the UNICOM Intelligence Interviewer Server - Admin user name that you are currently using, but if you do not have access to the destination server using this name, enter a different name here.
3 In Destination User Password, type the password for this user.
4 In the
Authentication menu, select either
Interviewer Server Authentication or
Windows Authentication. For more information, see
Configuring for single sign-on.
5 Select the
Login using my Windows Account option to use your current Windows user name and password credentials. When this option is selected, the
Destination User Name and
Destination User Password options are not available. See
To configure the server domain controller for additional configuration steps required on server.
Note The destination server or cluster must have Integrated Windows Authentication enabled for this operation to function properly. Integrated Windows Authentication is typically configured during UNICOM Intelligence Interviewer - Server Admin installation, but can be enabled post-installation by setting the EnableWindowsLogin registry value to True at:
HKEY_LOCAL_MACHINE\SOFTWARE\SPSS\DimensionNet\InstallOptions
6 Click Login to log in to the destination server.
To configure the server domain controller
When the Login using my Windows Account option is enabled, the server or cluster’s domain controller must be configured as follows:
1 On each accessory server, register the service principal name (SPN) in Active Directory in order to associate the domain account with the HTTP service. Enter the following at a Windows command window, substituting <accessory_server> with the name of the accessory server, and <anonymous user> with the anonymous user name that was specified during the UNICOM Intelligence Interviewer - Server Admin installation.
setspn.exe –A http/<accessory_server> <anonymous_user>
2 Configure each server computer’s account for constrained delegation by selecting the Use Kerberos only setting in each server computer’s Properties > Delegation tab and adding the server names to the Services to which this account can present delegated credentials list.
3 Configure the anonymous user account for constrained delegation by selecting the Use Kerberos only setting for the anonymous user account Properties > Delegation tab and adding the server names to the Services to which this account can present delegated credentials list.
See also