Server Installation: Difference between revisions

From EPOD
(Slightly reformatted)
Line 2: Line 2:
*Database
*Database
*ASP .NET 2 - 3.5
*ASP .NET 2 - 3.5
*IIS
*Microsoft Internet Information Services (IIS)
*External IP/URL
*External IP/URL
*Access to the machine
*Access to the machine with administrative privilege.


==Installation Process==
==Installation Process==
Line 10: Line 10:
*Copy all installation files to the Remote Host, this should include ePOD_WebApp, a SQL Folder and a PDA Folder and any required installation files (wkhtmltopdf, xferapp, sqlexpress)
*Copy all installation files to the Remote Host, this should include ePOD_WebApp, a SQL Folder and a PDA Folder and any required installation files (wkhtmltopdf, xferapp, sqlexpress)


==SQL Server Config==
==SQL Server Configuration==
*Install SQL Express - with Tools if required
*Install SQL Express - with Tools if required
*Setup to use the default instance and default users
*Setup to use the default instance and default users
*Enable TCP/IP  
*Enable TCP/IP  
*Enable PipedNames  
*Enable PipedNames  
*Add firewall expections to the programs and ports (1433)
*Add firewall exceptions to the programs and ports (1433)


==Database Setup==
==Database Setup==
Line 24: Line 24:
*Run the SQL script within the SQL folder copied to the remote host.
*Run the SQL script within the SQL folder copied to the remote host.
*Grant the user created Owner rights to the database.
*Grant the user created Owner rights to the database.
*Create the default site (either through MetaData sql script or manually)
*Create the default site (either through a meta-data DQL script or manually)
*Create a default user of ADM for this site
*Create a default user of ADM for this site


==ASP. Net==
==ASP .NET==
*Copy all of the ePOD_WebApp folder to the desired hosting directory
*Copy all of the ePOD_WebApp folder to the desired hosting directory
*Install .Net 3.5 framework, the system will work fine on .Net 2
*Install .NET 3.5 framework, the system will work fine on .Net 2
*Check this has registered with IIS
*Check this has registered with IIS
*Open command prompt
*Open command prompt
*Navigate to the frameworks folder (C:\Windows\Microsoft.NET\Framework)
*Navigate to the frameworks folder (C:\Windows\Microsoft.NET\Framework)
*Select your versions folder
*Select your versions folder
*Run regiis -i
*Run ''regiis -i''
*Create a new application pool called ePOD and select the relevant framework
*Create a new application pool called ePOD and select the relevant framework
*Select advanced settings on the application pool and settup the applications pool identify, this should default to ApplicationPoolIdentify, which is fine
*Select advanced settings on the application pool and set up the applications pool identify, this should default to ApplicationPoolIdentify, which is fine
*Create the new .Net application, pointing to the ePOD_Webapp Folder, using the above application pool
*Create the new .Net application, pointing to the ePOD_Webapp Folder, using the above application pool
*Bind to a external IP/URL (depends on routing)
*Bind to a external IP/URL (depends on routing)
*Apply ASP user permissions (IIS_USRS) to all files in the directory
*Apply ASP user permissions (IIS_USRS) to all files in the directory
*Allow annoymous access  
*Allow anonymous access  
*Add Default document as login.aspx
*Add Default document as login.aspx


==ePOD_WebApp==
==ePOD_WebApp==
*Once all above is completed
Once all the above is completed
*Log on to the site using the external connection (if a GDI+ error occurs there and permission issues so revisit the above steps)
*Log on to the site using the external connection (if a GDI+ error occurs there are permission issues, so revisit the above steps)
*Setup the following data:
*Set up the following data:
Site Configuration to Client
** Site Configuration to Client
Job Groups Configuration to Client
** Job Groups Configuration to Client
Vehicle (ADM)
** Vehicle (ADM)
Users and User Access
** Users and User Access
Reason Code
** Reason Code


*If not previously specified set the vehicle checks on the site to the following:
*If not previously specified set the vehicle checks on the site to the following:
Line 80: Line 80:


==Miscellaneous==
==Miscellaneous==
*Ensure MS Excel is installed - only for legacy versions
*Ensure Microsoft Excel is installed - only for legacy versions
*Setup Mail Server Configuration within the Web.config file
*Set up Mail Server Configuration within the Web.config file
*Setup scheduled service for auto export - only if required
*Set up scheduled service for auto export - only if required
*Insert any client details into the support log that are required (Site, User, Password)
*Insert any client details into the support document that are required (Site, User, Password)


[[Category:WI 287575 EPOD Development and Release Process|500]]
[[Category:WI 287575 EPOD Development and Release Process|500]]

Revision as of 17:28, 10 April 2012

Required Components

  • Database
  • ASP .NET 2 - 3.5
  • Microsoft Internet Information Services (IIS)
  • External IP/URL
  • Access to the machine with administrative privilege.

Installation Process

  • Access the machine via RDP
  • Copy all installation files to the Remote Host, this should include ePOD_WebApp, a SQL Folder and a PDA Folder and any required installation files (wkhtmltopdf, xferapp, sqlexpress)

SQL Server Configuration

  • Install SQL Express - with Tools if required
  • Setup to use the default instance and default users
  • Enable TCP/IP
  • Enable PipedNames
  • Add firewall exceptions to the programs and ports (1433)

Database Setup

  • On the selected database.
  • Create User - epod / eP0D1234.
  • Open the SQL script within the SQL folder copied to the remote host.
  • Check the two file paths at the top of this file match the directories for the install (only appliable to SQL Server installations).
  • Run the SQL script within the SQL folder copied to the remote host.
  • Grant the user created Owner rights to the database.
  • Create the default site (either through a meta-data DQL script or manually)
  • Create a default user of ADM for this site

ASP .NET

  • Copy all of the ePOD_WebApp folder to the desired hosting directory
  • Install .NET 3.5 framework, the system will work fine on .Net 2
  • Check this has registered with IIS
  • Open command prompt
  • Navigate to the frameworks folder (C:\Windows\Microsoft.NET\Framework)
  • Select your versions folder
  • Run regiis -i
  • Create a new application pool called ePOD and select the relevant framework
  • Select advanced settings on the application pool and set up the applications pool identify, this should default to ApplicationPoolIdentify, which is fine
  • Create the new .Net application, pointing to the ePOD_Webapp Folder, using the above application pool
  • Bind to a external IP/URL (depends on routing)
  • Apply ASP user permissions (IIS_USRS) to all files in the directory
  • Allow anonymous access
  • Add Default document as login.aspx

ePOD_WebApp

Once all the above is completed

  • Log on to the site using the external connection (if a GDI+ error occurs there are permission issues, so revisit the above steps)
  • Set up the following data:
    • Site Configuration to Client
    • Job Groups Configuration to Client
    • Vehicle (ADM)
    • Users and User Access
    • Reason Code
  • If not previously specified set the vehicle checks on the site to the following:
<VEHICLE_CHECK FREQ="1">
 <QUESTION ID="0001">
   <TEXT>Please check the following items.</TEXT>
   <FORMAT>X</FORMAT>
   <SKIPABLE>N</SKIPABLE>
   <ITEMS>
     <ITEM>Oil Level</ITEM>
     <ITEM>Tyres</ITEM>
     <ITEM>Brakes</ITEM>
     <ITEM>Water</ITEM>
     <ITEM>Lights</ITEM>
   </ITEMS>
 </QUESTION>
 <QUESTION ID="0002">
   <TEXT>Please enter any comments.</TEXT>
   <FORMAT>T</FORMAT>
   <SKIPABLE>Y</SKIPABLE>
 </QUESTION>
 <QUESTION ID="0003">
   <TEXT>What is the current Mileage?</TEXT>
   <FORMAT>N</FORMAT>
   <SKIPABLE>N</SKIPABLE>
 </QUESTION>
</VEHICLE_CHECK>

Miscellaneous

  • Ensure Microsoft Excel is installed - only for legacy versions
  • Set up Mail Server Configuration within the Web.config file
  • Set up scheduled service for auto export - only if required
  • Insert any client details into the support document that are required (Site, User, Password)