Difference between revisions of "Services"

Revision as of 01:24, 12 June 2009

What is a Windows Service?

Possibly the biggest new feature of DLS IV is the service-based architecture.

On Microsoft Windows operating systems, a Windows service is a long-running executable that performs specific functions and which is designed not to require user intervention. Windows services can be configured to start when the operating system is booted and run in the background as long as Windows is running, or they can be started manually when required.

There are many advantages to this architecture: - DLS IV does not rely on the current user's permissions - Allows effective integration with SQL Server Express - Allows operations to continue in the background AFTER the application has been closed.

DLS IV Services

The following are services which DLS IV uses and requires to run:

MCPH

The Multi-Comm Port Handler is the service component that handles the comm port assignment of each job. This service allows Comm Port Sharing, without requiring any extra user intervention.

Thanks to the MCPH, it's a one-time setup per connection type in the Modem Manager.

DLS Authentication Service

The Authentication service is DLS IV's padlock. This service ensures that your database will never fall into the wrong hands. The Security Stamp and Hardware Key are both processed by the authentication service on every login attempt.

DLS Communication Service

The Communication service is the workhorse that performs all communication jobs. This service receives each communication job, converts to panel-friendly commands, and executes your upload/download. Having the communication service allows you to submit many jobs in queue, close down the DLS IV application and walk away. The Communication service executes the jobs silently in the background, storing detailed information about each job in the database for your later review.

DLS Application Service

The Application service is DLS IV's engine. This service is at the core of every operation in DLS IV. It controls all traffic to-and-from the database, it builds up each communication job and checks the job's status as it's processed,

Managing Services

Service based architecture is becoming more and more mainstream, but is still relatively new to many PC users. DLS IV Services are set to launch "Automatically" on startup. This means that DLS IV, regardless of the permissions of the current PC user, will launch as a fully-functioning application every time Windows starts.

This startup routine, though robust, is not perfect. You may find that your PC has difficulty starting some services from time to time. Here are a couple of quick tips to help you manage your services:

DLS IV Launch

If any DLS IV service is not in a working state when the DLS IV application is launched, DLS IV will automatically try to start the services for you. This function will execute successfully for admin level users.

Services Manager

Access the Windows Services Manager by:

- Right-click "My Computer"

- Click "Manage"

- Browse to "Service and Applications" and then "Services"

You'll see a comprehensive list of all the service based applications installed on the PC, and each service's current state.

From here you can see the state of all DLS IV services, and correct any issues. Remember, when starting the DLS Services, start them in this order:

1. Authentication Service

2. Application Service

3. Communications Service

4. MCPH Service

Rebooting Your PC

It's an age-old solution to PC problems, but it works. Rebooting your PC will close any conflicting applications and will allot the proper resources to the DLS IV services on startup. It also allows each service to restart with the designed System privileges.