This document describes the deployment procedures for the Project i am currently working on.
Creating a Deployment Project Plan comprises of:
• Creating a project plan outline.
• Deciding the appropriate timeline for the deployment.
• Planning the deployment, as defined in the general MOF guidelines.
• Determining resources.
• Gathering information about the current environment.
• Determining technical considerations and dependencies.
All the above mentioned factors have been considered and reviewed before considering deployment on the development and test servers.
There are currently 2 alternatives to deploy components:
a) Copy the components to the broker sever proxies bin directory (or root) the components will be loaded and registered with the available brokers using the standard Fusion (CLR Loader) policy. This means that the components will be locked for the duration the process is running
b) Copy the components to the path configured as the “Business Component Path” components loaded from this location are shadow copied so they can be replaced, additional the broker server proxy watches for changes to these files and reloads when a new version of the component is deployed to this location.
[NOTE: Do not use option (b) at the current time as there issues which we are currently resolving with this mechanism]
The deployment process is from the development machines to the test servers is carried out in three steps as mentioned below.
4.1 Deploying the build on local machine and verifying the work
A local instance of Service broker has been installed with the help of Framework team on every development PC.
The main steps involved in deploying the build on the local development Pc are:
• Configuring the ‘Mondial.Common.BrokerServiceHost.exe.config’ file for Service broker, Service Gateway and Data Access Service access.
• Configuring the client Config file for accessing the Service Broker on the appropriate server using the appropriate transport protocol.
• Deploying the relevant BPC’s and all other dependent DLL’s.
• Restarting the Windows Service:
Service Broker (Broker) and
Service Broker (Server) for new server registration files.
Note: If we need to re-deploy the BPCs then, you should stop the services and then copy the BPCs and then re-start the services.
Deploying the build on development server and verifying the work
After successful deployment of work on development machine, the solution is deployed on the development server. All the steps mentioned above for local machine deployment have to be followed in addition to the setting up of the environment for prime entity access.
MQ services have to be setup on the development server. A queue manager has to be created. The current queue manager on development server is: PHX.PHXSG.UAT.QM02
Additionally the local reply queue and clustered request queue has to be configured.
Deploying the Service Broker on test server
Deployment of Service Broker on Test Server is carried out by the Framework team. Only the Broker host is supported on test serer and there are different test servers, different components respectively
Deploying the build on test server and verifying the work
After successful deployment of work on development server, the solution is deployed on the test server. All the steps mentioned above for local machine deployment have to be followed in addition to the setting up of the environment for prime entity access.
For each deployment a MSI (UI installer with Build number) will be handed to test for installation of the client user interface. Test team will use different database for testing.
The MSI contains:
• All application files, in compressed mode.
• All options available through the installation process, when using either a graphical user interface or automatic unattended mode.
• Location of application files.
• User environment settings, such as Start-menu entries and desktop shortcuts and icons.
• Uninstall information.
• Registration requirements, if necessary.
• Other configuration settings required to successfully install and register the application.
Deployment is considered successful only if the client application works as desired on the test servers.