You can use the Runtime transfer process to deploy an application to a different Runtime machine without using Developer. It can also be used to redeploy an application on the local machine.
The runtime transfer process uses the concept of deployment units, which enables you to deploy a number of MSI or CAB packages at one time.
Right-click the runtime server node on which the required MSI packages are currently deployed.
Select All Tasks > Runtime Transfer.
The Initiate Runtime Transfer dialog box appears. It provides the following two options to select deployable units:
The Existing Deployment System option to select an existing deployed system on the local server.
The Custom Packaged System option to select MSI or CAB files to be deployed.
Select an option to initiate the runtime transfer process, and click OK.
The List of Deployment Packages dialog box appears.
From the Available Deployment Packages list, select the deployable packages that you want to deploy.
Click Add to add the selected packages to the Packages to Transfer and Deploy list.
Click OK.
If you did not enter a target deployment unit name to be used on the target runtime server, you will be asked if you want to use the existing deployment name or specify a new name.
Note: If you are redeploying to the local machine and you do not specify a new name, the existing package is overwritten.
Click Yes to retain the existing name.
Click No to enter a new unit name.
For each package in the deployment unit, the Deployment Settings for Package dialog box is displayed. You must specify the Target DB server registration and Target DB name for each package.
If you do not specify values for the remaining options, the values entered when the package was built are used.
Click Next when you have completed the options for each package.
When you specify the target server name as the same machine, you receive a warning message "The Source server is same as the Target server. The system is moved from Source database to Target database and is no longer accessible from the Source database". The warning is displayed because there can only be one instance of the system name allowed on a runtime host. Click Yes.
The Application User Details for Target Machine dialog box appears.
Specify the details of the Application User on the target machine.
Click Finish.
The progress information for the deployment is displayed in the Event Log node.
A cluster comprises of machines or nodes connected to each other. The Cluster software monitors the clustered processes and services running on each node and ensures that these processes and services are switched to another node in the cluster in the event of any failure.
The Runtime Transfer process is also used to deploy an application in a clustered environment, as you have to deploy the application to each Node in the cluster separately. It is recommended that you use a script for the deploy process as that ensures the same settings are used on each Node.
Note: During deployment, the location of the Extract Files is fixed. Hence for a cluster environment, a relative path should be used so that the extract files are places in the Data folder of the deployed application. For example, .\Data or ..\Data.
To deploy an application in a cluster, perform the following:
In the Runtime Administration Tool, right-click the Machine name/LOCALHOST node.
Note: You must copy the MSI files and the Resource Group to the cluster Node that you are deploying to.
Select All Tasks > Runtime Transfer.
The Initiate Runtime Transfer dialog box appears.
Select Custom Packaged System and in Select Package Folder enter the location of the folder that contains the MSI file.
Click Next.
The List of Deployment Packages dialog box appears.
From the Available Deployment Packages list, select all the MSI files and Cab files (if separate reports in IC1800 or higher) that you want to deploy.
Click Add to add the MSI or CAB files to the Packages to Transfer and Deploy list.
Complete the Deployment settings dialog as required. Click Next.
Note: The Target Server name must be Localhost.
Ignore the warning message and click Yes.
Complete the Application User Details dialog and click Finish.
After a few minutes an information dialog is displayed to indicate that the system has deployed successfully. If you selected additional report MSI files, then these are deployed now but you will only receive a success or failure message, not the information dialog.
Repeat this process on each of the other Nodes by first moving the Resource Group to the next Node and then repeating this procedure on that Node. Ensure exactly the same locations and values are used for the system.
After deploying the applications on all the Nodes, you can perform other configurations such as defining Views as in a non-clustered environment. The only difference is that the IP address or Network name to use is not one of the physical Node names but the IP address or Network name of the Resource Group that the Applications have been deployed under (that is, the network name of the Resource Group that the Protocol Adapters belong to).
Source Runtime Server Details
Source Server name
Displays the source Runtime server from where Runtime Transfer is initiated.
Existing Deployment System
Select this option to deploy a unit that has been deployed on the local machine. Select the required unit from the list.
Custom Packaged System
Select this option to deploy a unit that has been created from MSI packages that were not originally deployed together. Enter the path of the folder containing the required unit.
This dialog allows the user to customize the list of MSI packages for deployment.
Deployment Folder
Displays the selected Deployment folder path.
Available Deployment Packages
Lists all the MSI Packages present in the selected Deployment folder.
Packages to Transfer and Deploy
Lists all the MSI Packages selected by the user to be transferred and deployed.
Add->
The selected Packages from the Available Deployment Packages list are added to the Packages to Transfer and Deploy list.
Add All
All the MSI packages present in the selected Deployment folder are added to the Packages to Transfer and Deploy list.
<-Remove
The selected Package is removed from the Packages to Transfer and Deploy list.
Remove All
All the MSI Packages present in the Packages to Transfer and Deploy list are removed.
Move Up and Move Down
Provides provision to re-order the Packages to Transfer and Deploy list.
Notes:
Multiple Packages can be selected by using CTRL and SHIFT key.
Ensure that the Segment Package is deployed before any dependent Report Packages.
This dialog box is displayed for each MSI package in the selected unit. Click Next to move onto the next package.
Package Name
Displays the MSI package name, to be deployed.
Target Server Name
This is a mandatory field. Enter the name of the Runtime server to which you want to deploy. Enter “localhost” to redeploy to the local machine.
Target DB server registration
This is a mandatory field. Select the name of the server registration to which you want to deploy.
Target DB name
This is a mandatory field. Select the name of the database to which you want to deploy.
Deployment unit name
Displays the name given to the selected unit when it is deployed on the target machine. It can also be modified as per user wish.
Target application folder
Enter the path of the folder in which the deployed application files are stored. If you leave this field blank, the path defined when the package was originally built is used.
Target Winform folder
Enter the path of the folder in which the Winform files are to be stored. If you leave this field blank, the path defined when the package was originally built is used.
Retain existing database
Select this option if you want to retain the existing database when redeploying to the local machine.
The Application User account details are required to gain access to the target machine.
Name - Enter the name of the user account defined as the Application User.
Domain - Enter the domain name of the destination machine. Enter a period (.) if the target is the local machine.
Password - Enter the password defined for the Application User.