Please note the following considerations before deploying:
Complete necessary installations – The Deployment Server and all runtime infrastructure must be installed on the server to which you want to deploy. If it is not, and an application is manually deployed, deployment might appear to succeed, however is inoperable. The Builder factory for the target platform must also be installed on the Development environment.
Deployment Impersonation – By default, the Deployment Server running under the Application Administrative User identity impersonates the user that invokes the deployment action to access the MSI package. This requires the invoking user to be given administrative privileges in the runtime machine and the application administrative user to be given the Trust Account for Delegation privilege at the domain level when the development environment and runtime environment are on different machines. Refer to the Agile Business Suite Installation and Configuration Guide for more information on the delegation privileges.
An alternative method of deployment is by defining the values for the RuntimeServiceImpersonationLevel registry key where impersonation level is reduced. Refer to the Agile Business Suite Installation and Configuration Guide for more information on the various impersonation levels.
Ensure necessary files exist (applies to redeployments only) – Before rebuilding and redeploying your application, ensure that all files created with the previous deployment exist.
Ensure the target database and database server registrations are created successfully on the runtime server.
Stop the System – The system must be stopped before it is deployed. If the system is running when deployment is attempted, deployment aborts. Use the Admin Tool to stop a system.
Enable/Disable the System – To enable your application after deployment, ensure that is enabled before deployment. Likewise, if it is disabled before deployment, it is disabled after deployment.
Check database and application user details – To ensure a successful deployment, check that database and application user details are correct.
Checking database and application user details
If deployment is initiated using Builder or the Administration Tool, database and application user details entered (such as name, password, domain, etc) are checked. If they are incorrect, deployment aborts.
If deployment is performed manually, no checks are performed. If database and application user details entered are incorrect, deployment appears to succeed, however the application is inoperable.
If details entered are correct, and the database or Segment COM+ component is being deployed, the application must be manually stopped and disabled before deployment proceeds. You are unable to connect to the application until deployment has completed.
Deploying with Reduced Impersonation Level
If the RuntimeServiceImpersonationLevel registry key option is used for deploying a system, you can access the deployment package at the following two levels:
As an administrative user not having delegation privileges
As an application administrative user having delegation privileges
When you opt to install a package with an administrative user not having delegation privileges, the administrative user can access the MSI package without impersonating the user that invokes the deployment. If the Package Intermediate Directory is a local path in the developer environment or on the runtime server, no prior settings are required. However, access permissions should be explicitly provided to the administrative user if the Package Intermediate Directory is a shared network path. In the network path, you must provide the following privileges to an administrative user at the network location:
Permission to access (Read/Write) the shared builder output path from the network.
Add to the Network Access group of the remote computer
Note: You can add a user to the Network Access group from Control Panel > System and Security > Administrative Tools > Computer Management. In the Computer Management window, navigate to Local Users and Groups > Groups. Double-click Network Access and then click Add.
Have Access this computer from the network privilege
Note: You can grant a user Access this computer from the network privilege from Control Panel > System and Security > Administrative Tools > Local Security Policy. In the Local Security Policy window, navigate to Local Policies > User Rights Assignment. Double-click Access this computer from the network and then click Add User or Group.
When you opt to install a package with application administrative user having delegation privileges, the deployment process is initiated by the application administrative user that invokes the deployment process. If the Package Intermediate Directory is located on the runtime server or located on a shared network path, you must provide the following privileges to the application administrative user:
Permission to access (Read/Write) the shared package intermediate path from the network.
Add to the Network Access group of the remote computer
Have Access this computer from the network privilege.
Note: The privileges required for an administrative user without delegation privileges are same as those that are required for an application administrative user with delegation privileges, except the following privileges that needs to be provided:
Enable the computer and user accounts to be trusted for delegation
Impersonate a client after authentication
Rebuilding or redeploying
If you want to rebuild or redeploy in the future, do not delete files created in your deployment system directory. If files are deleted and cannot be recovered, your application must be removed using the Windows Installer CleanUp Utility.
To redeploy your application manually on Windows hosts, before redeploying perform the following:
Stop any builds.
Disable the system.
Use the Windows Installer Cleanup Utility.
Modify the NGRuntime.XML to remove the system entry.
Delete the COM+ component.