This project has moved. For the latest updates, please go here.

Download the Homelidays Session Service setup file

Choosing between 32 bits vs 64 bits of Homeidays Sessions Service depends on the IIS application pool (w3wp.exe) beeing 32 or 64 bits. Check the "Enable 32-bit applications" option of the IIS application pool :

  • If your application pool is running inside a 32 bits process (i.e "Enable 32-bit applications" is set to true), you should install the 32 bit version of HomelidaysSessionService.
  • If your application pool is running inside a 64 bits process (i.e "Enable 32-bit applications" is set to false), you should install the 64bit version of HomelidaysSessionService.

Depending if you are targeting a 32 bits or a 64 bits application pool, download the Homelidays Session Service from http://sessionservice.codeplex.com/releases.

Install the setup by following the wizard

The Homelidays Session Service installer needs to be installed on every web server where it needs to run.

The Session Service isntaller will:

  1. Create a folder in C:\Program Files\Homelidays and copy its files in it
  2. Register the COM component for Classic ASP in the registry
  3. Install .NET Library in the Global Assembly Cache (GAC)

Double click on the setup.exe (not setup.msi) file and follow the wizard:

If needed setup.exe will install the "Microsoft Visual 2008 C++ Redistributable ..." while setup.msi won't. Once this prerequisite installed, you should go through the following:

image

image

image

 

image

image

 

Change the connection string

For ASP configure the ADO connection string

Open the C:\Program Files\Homelidays\Session Service\AspSessionServiceConfig.xml file and edit you connection string.

The file should looks like:

<?xml version="1.0"?>
<Partitions>
    <Partition>
        <ConnectionString>Provider=SQLOLEDB.1;Data Source=.\;Initial Catalog=tempdb;</ConnectionString>
        <Login>sa</Login>
        <Password>123456</Password>
    </Partition>
</Partitions>

By default for performance reason we choose to use the tempdb database as it is a memory database.

The database schema will be created by the Session Service automatically so the database user should have the right to execute “CREATE TABLE” statements.

Integrated security has not been tested yet so I don't know if it works.

For ASP.NET configure the ADO.NET connection string

In the installation folder (C:\Program Files\Homelidays\Session Service), edit the AspSessionServiceConfigAdo.Net.xml and configure your connection string.

The file should looks like:

<?xml version="1.0"?>
<Partitions>
    <Partition>
        <ConnectionString>Data Source=.\;Initial Catalog=tempdb;</ConnectionString>
        <Login>sa</Login>
        <Password>123456</Password>
    </Partition>
 </Partitions>

Integrated security has not been tested yet so I don't know if it works.

Install the SQL job that clears expired session

A SQL job should be install to clear expired session every minute.

Open the C:\Program Files\Homelidays\Session Service\01 Job.sql file and set:

  1. The job owner name (@owner_login_name);
  2. The database name (@database_name).

Run the script to install the job.

Make sure the Sql Agent is started (and ensure he is configured to automatically start at boot time ;-).

Add some more writes as long as issue #933 is not resolved

The installation folder need some more writes so that Session Service COM component (used for Classic ASP) can write its logs.

The account that runs the Classic ASP application pool needs to have write access to the Session Service installation folder eithe :

  • C:\Program Files\Homelidays\Session Service
  • C:\Program Files\Homelidays\Session Service x64

IISReset

You may need to perform an IISReset before using the Homelidays Session Service.

Use the session service in classic ASP code

Use the session service in ASP.NET code

Last edited Jul 21, 2016 at 11:01 AM by Yanal, version 15

Comments

No comments yet.