Server Installation

From EPOD
Revision as of 14:56, 3 April 2012 by Milesl (talk | contribs)

Required Components

  • Database
  • ASP .NET 2 - 3.5
  • IIS
  • External IP/URL
  • Access to the machine

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 Config

  • Install SQL Express - with Tools if required
  • Setup to use the default instance and default users
  • Enable TCP/IP
  • Enable PipedNames
  • Add firewall expections 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 MetaData sql 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 settup 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 annoymous access
  • Add Default document as login.aspx

ePOD_WebApp

  • Once all 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)
  • Setup the following data:
Site Configuration to Client
Job Groups Configuration to Client
Vehicle (ADM)
Users and User Access
Reason Code 

Miscellaneous

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