TECH SUPPORT

How do I Install ChristianSteven Software in a Client Server Environment?

Follow

Installing ChristianSteven Software in a Client Server Environment

The following document describes how you can set up a Client-Server environment for CRD, MARS or SQL-RD. We will refer to each of these as "the software" for ease of documentation as the process is the same for each of them.

A client server environment allows you to have a setup where several users can create schedules held in a single database location and have a single server that executes them when due. This setup is useful as it may ease administration tasks such as backing up the system, user administration etc.

The objective will be to create an environment that allows the following:

 

- Several users should be able to create schedules on their individual workstations via the thick client

-Collaboration machines can be deploy for load balancing

- The schedules should all be run by central scheduler server

- The back end database will be stored in your own centralized SQL Server instance. This is to ensure greater stability for the system.

-A failover machine can be designated as the backup scheduler system

 Requirements:

- At least 3 installation licenses of CRD, SQL-RD or MARS

Setup Process:

Designate one Server installation as the “Server”. This will be the machine that will be responsible for running the scheduler. Any other installations of the software will work as clients.

 Getting Started

  1. The clients should be set to no scheduling.

 

  • In the software, go to the options menu. Select the scheduler tab.
  • Select “No Scheduling Required.”
  • Click on “Apply Setting” and then “apply” and “OK”

 

  1. Older versions of the software required a migration of the system file to ODBC/SQL on the "Server", the latest version of the software sets up a local SQL Server Express instance to hold the system files. If you have installed the latest version you will not need to do this unless you are planning to move to a different ODBC compliant database.

Note: This is a highly technical process. ChristianSteven Software does not provide technical support for SQL Server or any other ODBC-compliant database. Please ensure that the process is performed only by personnel who are fully qualified in the administration and maintenance of your database and data infrastructure.

*Please Read the entire document before beginning the process.*

Part 1: Migrating your existing Schedules

Before you can share this information with other installations you must migrate the schedule data to your ODBC-compliant database. This section explains how this is done. There are other ways in which the same results may be achieved, however this section details is our recommended method.

Preparing the database:

 

This can be done on the “Server” PC or you can designate another machine to be the “Database Server”.

 

Start by creating a new database. Use SQL Server Enterprise Manager, SQL Server Management Studio or the database management tool that comes with your database. The example database above is called “MyExample”.

Create a new login as shown above.

The example login has been named “CRDUser”.

- Give the login a password.

- The login must be set up using SQL authentication.

- Ensure that the Default database is set to the database you created (“MyExample”) as\ shown above.

Give the login sysadmin rights as shown above.

 

Map the login to the “MyExample” database and ensure that it has db_owner rights for

the database.

The database and the login are now set up.

Preparing the “Server” PC

 

On the “Server” PC, where the scheduling application is installed you will now need to set up a SYSTEM ODBC DSN connecting to MyExample and using CRDUser as the login.

Start by going to Windows Control Panel > Administrative tools and select Datasources (ODBC).

 

- Click on the System DSN tab and click Add.

- Select the database type you require (in our example this will be a SQL Server)

 

 

Enter a name for the DSN and select the server where the database is stored as shown above. Click Next.

Select SQL Server authentication and enter the Login ID and Password for the login we created previously. Continue the process to complete the setup of the DSN.

 

Migrating your schedule database to the new database

 

In the software, go to the Configuration Tab, then select “Migrate to ODBC”

(Users on CRD,SQL-RD and MARS versions previous to 7.0 will go to System à Migrate to SQL Server/ODBC)

- Follow wizard and ensure you select the DSN you set up previously.

- Enter the login details where prompted.

When the process is completed, the application will restart. The application will now be using the ODBC database.

Note: The ODBC information is stored in the application and it will log into the database automatically. If you change the login credentials or wish to use a different login, go to Configuration Tab à Update ODBC Login info.

Migrating schedules from the client installations

If you have existing schedules on the other to be clients, you can export the schedules from these systems to the "Server.” (System Tab à Export Schedules)

 

Part 2: Sharing the database with other installations.

This section explains how to get another installation of the scheduling application to “join” the “Server” system.

In this section we will refer to the original installation which was migrated in Part 1 as the “server installation.” We will refer to all other installations as the “client installations.”

The scheduler will only be enabled on the “server installation” and the client installations will be used to write and maintain schedules. All automated scheduling will be performed by the “server installation.”

Preparing the Server Installation

In addition to sharing the database, the client installation must also share some system files. To see where the shared system files are stored, go to the “server installation” and look in Options and select the System tab.

 

The number of system paths may vary depending on the application you are using.

The system paths must now be shared so that other users; the “client installations”, can access the files and subfolders.

Start off by sharing the Program Files\ChristianSteven folder.

 

Ensure to specify that Everyone is given Full Control as shown above.

If any of your system paths are in different folders to the ChristianSteven folder and subfolders then ensure you additionally share these folders and give everyone full control of them.

  1. Point all the clients to use the same ODBC/SQL system

For each of the client installations you will need to do the following:

 

- In the software, go to Configuration Tab à Login information

- Enter your DSN information making sure you are using a system DSN created on each client PC as was done for the “server installation.”

- In the software, go to Configuration Tab à Switch to ODBC

 

  1. Set all System paths for the clients to use the "server installation" system paths.

 

In the software, go to Options à System Tab. You will want to use the full UNC path to the server's directories, i.e.

\\myserver\c$:\program files\christiansteven software\

  1. Install the NT Service Scheduler on the "server installation.”

We recommend the NT Service Scheduler as the Background Application

Scheduler will require a user to be logged on the PC at the time schedules are due to run for the schedules to run automatically, the NT Service Scheduler will allow the schedules to run even when no user is logged on. The requirements and process for the installation of the NT Service Scheduler are similar on MARS and SQL-RD.

The NT service is a windows service. It installs into the windows "Services" control panel. Before installing this option, you must ensure that the following is already in place:

  • You are logged on as the NT service user
  • The above user has the following windows security rights on the PC you are installing it on:
  1. "Act as part of the operating system"
  2. "Log on as a service"
  3. Is a member of the "Local Administrators" security group
  4. If you are using MS Exchange Server, the above user must have full rights to the designated email account.

These security requirements are stipulated by Windows. If you are unsure how to set up Windows security settings, your system administrator will be able to help.

Once this is in place do the following:

- Go to Options and select the Scheduler tab.

- Select the “Use NT Service..” option as shown below.

 

- Enter the Domain, User Name and Password for the account that will run the service. If you are using MS Exchange Server, then this must be your network domain so that CRD can connect to your Exchange server.

  • Click on “Apply Setting.”

 

You will be prompted to ensure all the environmental prerequisites are met.

Click Proceed after checking all the requirements.

If you have configured the application to use MAPI Mail you will be prompted to select one of the following:

  • Outlook Standalone
  • Exchange Server

Select the type of email system you are using and follow the prompts to complete configuration of the service.

You will be prompted to optionally open the Services control panel.

Once the service is installed, the service will be visible in the windows "Services" control panel and will be known with the name of the scheduling application. E.g.

For CRD you will have a "CRD" Service and also visible will be a "CRD Monitor" Service which ensures that the CRD service is continually running.

Click the “Start Service” button to start the services. Alternatively you ca start the services from within the “Services” control panel administrative tool.

- Click “Apply” and “OK”

With the service installed, you should now be able to create schedules from any of the client installations. These will be run by the “server installation” and all the data will be kept in the database you configured above.

For additional Help you can consult the My ChristianSteven user forum (http://www.mychristiansteven.com/) or Log a support ticket in the support area (www.christiansteven.com).

Comments