Server Installation: Difference between revisions
From EPOD
(Slightly reformatted) |
(Updated with far more detail) |
||
Line 9: | Line 9: | ||
*Access the machine via RDP | *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) | *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) | ||
All files can be found in ''P:\EPOD\_Development\_Releases\''. Latest development releases are in Development sub-folder. | |||
==SQL Server Configuration== | ==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 | * Through SQL Server Configuration Manager | ||
*Enable | ** For all the native and network clients | ||
*** Enable TCP/IP | |||
*** Enable Named Pipes | |||
** Restart service if required, by clicking on SQL Server Services, choosing the database (usually MSSQLSERVER or SQLEXPRESS) and clicking stop then start from the toolbar. | |||
*Add firewall exceptions to the programs and ports (1433) | *Add firewall exceptions to the programs and ports (1433) | ||
** Server Manager, Configuration, Windows Firewall with Advanced Security, Inbound Rules | |||
** Check whether the exception for the port already exists. If not, add a new exception with the New Rule link, then select Port, TCP, Specific Local Port 1433, Allow the Connection, for all network types. Give this a reasonable name (e.g. SQL Server). | |||
==Database Setup== | ==Database Setup== | ||
*On the selected database. | *On the selected database (through SQL Server Management Studio). | ||
*Create User - epod | *Create User, through Security, Logins, right-click, New User. Login Name: epod, SQL Server Authentication, password: eP0D1234. Default database should be left as Master. Uncheck 'Enforce Password Policy'. | ||
*Open the SQL script within the SQL folder copied to the remote host. | *Open the SQL script ''Script.SQL'' within the ''SQL/Create'' folder copied to the remote host (''File/Open/File'''). | ||
*Check the two file paths at the top of this file match the directories for the install (only | *Check the two file paths at the top of this file match the directories for the install (only applicable to SQL Server installations). I.e.: | ||
* | * If you are running the 32bit version on 64Bit Windows: | ||
*Grant the user created Owner rights to the database. | CREATE DATABASE [EPOD_TEST] ON PRIMARY | ||
*Create the default site | ( NAME = N'EPOD', FILENAME = N'c:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\EPOD.mdf' , SIZE = 70656KB , MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB ) | ||
*Create a default user of ADM for this site | LOG ON | ||
( NAME = N'EPOD_log', FILENAME = N'c:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\EPOD_log.ldf' , SIZE = 136064KB , MAXSIZE = 2048GB , FILEGROWTH = 10%) | |||
* Otherwise: | |||
CREATE DATABASE [EPOD_TEST] ON PRIMARY | |||
( NAME = N'EPOD', FILENAME = N'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\EPOD.mdf' , SIZE = 70656KB , MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB ) | |||
LOG ON | |||
( NAME = N'EPOD_log', FILENAME = N'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\EPOD_log.ldf' , SIZE = 136064KB , MAXSIZE = 2048GB , FILEGROWTH = 10%) | |||
* Note for Full/Standard/Web Edition/Enterprise, replace SQLEXPRESS with MSSQLSERVER | |||
*Execute the SQL script through the Execute button. | |||
*Grant the user created Owner rights to the database: | |||
** Database/EPOD/Security/Users, double-click 'epod' user. | |||
** On the ''Database Role Membership'' pane, ensure '''DB Owner''' is checked, then click '''OK'''. | |||
*Create the default site, either through a meta-data SQL script or manually through right-clicking on table EPOD_SITE, select ''Edit Top 200 Rows'', populate SITE_ID, DESCRIPTION, everything else will default. | |||
*Create a default user of ADM for this site, either through a meta-data SQL script or manually through right-clicking on table EPOD_USER, select ''Edit Top 200 Rows'', populate SITE_ID, USER_ID, USER_PASSWORD, USER_NAME, USER_ADMIN = Y, USER_ACTIVE = Y, everything else will default. | |||
==ASP .NET== | ==ASP .NET== |
Revision as of 14:21, 24 July 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)
All files can be found in P:\EPOD\_Development\_Releases\. Latest development releases are in Development sub-folder.
SQL Server Configuration
- Install SQL Express - with Tools if required
- Setup to use the default instance and default users
- Through SQL Server Configuration Manager
- For all the native and network clients
- Enable TCP/IP
- Enable Named Pipes
- Restart service if required, by clicking on SQL Server Services, choosing the database (usually MSSQLSERVER or SQLEXPRESS) and clicking stop then start from the toolbar.
- For all the native and network clients
- Add firewall exceptions to the programs and ports (1433)
- Server Manager, Configuration, Windows Firewall with Advanced Security, Inbound Rules
- Check whether the exception for the port already exists. If not, add a new exception with the New Rule link, then select Port, TCP, Specific Local Port 1433, Allow the Connection, for all network types. Give this a reasonable name (e.g. SQL Server).
Database Setup
- On the selected database (through SQL Server Management Studio).
- Create User, through Security, Logins, right-click, New User. Login Name: epod, SQL Server Authentication, password: eP0D1234. Default database should be left as Master. Uncheck 'Enforce Password Policy'.
- Open the SQL script Script.SQL within the SQL/Create folder copied to the remote host (File/Open/File').
- Check the two file paths at the top of this file match the directories for the install (only applicable to SQL Server installations). I.e.:
- If you are running the 32bit version on 64Bit Windows:
CREATE DATABASE [EPOD_TEST] ON PRIMARY ( NAME = N'EPOD', FILENAME = N'c:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\EPOD.mdf' , SIZE = 70656KB , MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB ) LOG ON ( NAME = N'EPOD_log', FILENAME = N'c:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\EPOD_log.ldf' , SIZE = 136064KB , MAXSIZE = 2048GB , FILEGROWTH = 10%)
- Otherwise:
CREATE DATABASE [EPOD_TEST] ON PRIMARY ( NAME = N'EPOD', FILENAME = N'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\EPOD.mdf' , SIZE = 70656KB , MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB ) LOG ON ( NAME = N'EPOD_log', FILENAME = N'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\EPOD_log.ldf' , SIZE = 136064KB , MAXSIZE = 2048GB , FILEGROWTH = 10%)
- Note for Full/Standard/Web Edition/Enterprise, replace SQLEXPRESS with MSSQLSERVER
- Execute the SQL script through the Execute button.
- Grant the user created Owner rights to the database:
- Database/EPOD/Security/Users, double-click 'epod' user.
- On the Database Role Membership pane, ensure DB Owner is checked, then click OK.
- Create the default site, either through a meta-data SQL script or manually through right-clicking on table EPOD_SITE, select Edit Top 200 Rows, populate SITE_ID, DESCRIPTION, everything else will default.
- Create a default user of ADM for this site, either through a meta-data SQL script or manually through right-clicking on table EPOD_USER, select Edit Top 200 Rows, populate SITE_ID, USER_ID, USER_PASSWORD, USER_NAME, USER_ADMIN = Y, USER_ACTIVE = Y, everything else will default.
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)