Kourier Integrator Administration - Rebooting the ETL Server

Background

Normally, the Kourier Service Manager (KSM) is installed on the same server as your SQL database.  The KSM is responsible for connecting to your U2 server and running the scheduled services on each account.  These services run as phantom processes on the U2 server.  If the service that is running is designed to move data from U2 to SQL and you are using the Autorun SSIS Package feature, Kourier will envoke a web service on the ETL server to run the SSIS package associated with each export just prior the completing the service.  These SSIS packages run as background processes on the ETL Server.  Therefore, it is important to gracefully stop this process before rebooting the ETL Sever.

Rebooting Procedure

To stop the Kourier ETL process, do the following:

  1. Stop the Kourier Service Manager using the Windows Services application (e.g. Administrative Tools | Services).
  2. Determine if all SSIS packages have completed.  You can determine this in one of two ways:
    1. Using the Windows Explorer, make sure that the inbox folder in the staging area is empty.  If SSIS packages are still running, this folder will not be empty. Normally it takes just a few seconds for these files to be processed.
    2. Using the SQL Server Managment Studio, run the LIST_RUNNING_PACKAGES script in the target database.  If any row is listed, that SSIS package is still running.

Once step 1 and 2 are complete, it is safe to reboot the server.

See Also

Kourier Integrator Setup and Administration Guide

Kourier TCL Commands

User Guide - Table of Contents