We have created an automated deployment process to simplify the actions needed to set-up the emdash™ environment and configure the infrastructure needed.
In order for the automated processes to run, the following information is needed from you:
- SQL Server instance that will hold the emdash™ database for both the ‘Production’ emdash™ instance and any Test environments you would like set up.
This is included in the emdash™ build that you will be provided with, so the installation process will reference that location.
You should also have the following details ready for the installation process:
- Service account name and password to run the emdash™ services;
- Infrastructure requirements available and configured as per Section 3;
- The user that runs the emdash™ installation script needs sysadmin on the SQL instance to create the emdash database;
- The user that runs the emdash™ installation script needs local admin access on the server that will run the emdash™ website and server-side components;
- The user that runs the emdash™ services needs to be granted 'Logon as a Service' rights in the local security policy on the server (Open Local Security Policy -> User Rights Assignment and find 'Grant Logon as a Service' option).
In additions, please check that the installation pre-requisites have been completed. Here is a checklist:
You will be provided with a powershell script called ‘emdashDeploy.ps1’ and credentials to access our build server. The deployment script will access this over the internet to download the build we specify for you using these credentials.
- Save the emdashDeploy.ps1 - emDashDeploy.ps1 - script into a folder called c:\emdash on the windows server that will run the emdash™ components;
- Execute this script as the user defined above. The script will prompt for the following information:
- Client Name. This will be provided to you.
- Emdash Environment. Prod / Test / other (if agreed with us)
- teamCity User / Password. This will be provided to you.
- Build Number. This will be provided to you.
- Service Account User / Password. This should be entered as a fully qualified user in the formal <domain>\<user>.
Once the data is input, the script will perform the following functions (with screenprints to show what you should check after the script has run):
- Download and unpack the build from our Build Server into c:\emdash;
Figure 4.1 - Build Pack
- Create the App Pool in IIS and set to run as the Service Account
Figure 4.2 - IIS Application Pool creation and configuration
- Create the IIS sites (emdashWeb, emdashWebApi, emdashServices);
Figure 4.3 - Create Web Sites
- Create the Windows Services (Workflow and Synthetic Workflow Services);
Figure 4.4 - Create emdash Windows Services
- Create a new database on the specified SQL instance;
- Populate the database with the base reference data;
- Upload the Workflows and Steps into the database;
Figure 4.5 - Validate workflow upload completed sucessfully
- At this point, you will be able to connect to the emdash™ website on your server at http://localhost/emdashweb which should look like this:
Figure 4.6 - emdash Portal