MPAY Millennium 3, SQL Server 2008 R2, 2008 R2 Express Edition, 2005 Express Edition database software Installation Guide
Reklam
Reklam
Installation Guide for Service Bureaus
Notice
The information in this document is subject to change without notice. MPAY Inc. shall not be liable for any technical or editorial errors contained herein or for incidental or consequential damages resulting from the performance, furnishing, or use of this publication.
The software described in this document is furnished under license and may be used or copied only in accordance with the terms of that license.
No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including (but not limited to) photocopying, recording, scanning, or retrieval system, for any reason other than the purchaser’s personal use without the express written permission of MPAY Inc. The company data contained in the examples within this text is fictitious and any resemblance to real people, places, or companies is purely coincidental.
MPAY, Millennium, and payentry.com are trademarks of MPAY Inc. Windows, Windows 2000, Windows XP,
Windows Vista, and Windows 7 are registered trademarks of Microsoft, Inc. All other brand and product names are trademarks or registered trademarks of their respective owners.
Corporate Headquarters:
9920 West Kincey Avenue
Suite 120
Huntersville, NC 28078
Phone: 781‐810‐9009 http://www.mpay.com
Copyright © 2012 by MPAY, Inc
Version: April, 2012
Document Number: M3‐Install‐GD‐SB‐647‐01
All rights reserved
Printed in the United States of America
TOC
Table of Contents
Release 3.29
iii
Table of Contents
When should your end‐client have a dedicated processing machine? . . . . . . . . . . . . . 58
iv Millennium 3 Installation
Table of Contents
Additional Registry Keys to Allow End‐Users to Save Preferences . . . . . . . . . . . . . . .122
Release 3.29
v
Table of Contents vi Millennium 3 Installation
Chapter 1
Introduction
This chapter provides you with a general overview of Millennium 3.
What Are the Components of Millennium 3?
A summary explanation of the components of the Millennium system are as follows:
A. The Millennium 3 application
This is the primary application. It is the one in which you enter employee and company information, process money transfers, and process taxes.
B. The Process Server application
This is the next most important application. Many people use the term “process server” to describe a separate computer that performs a function. This is a misnomer. A computer functions as a processing machine when it is running the
Process Server application ( processserver.exe
).
The Process Server application is responsible for ensuring any job that appears in the Millennium job queue is processed. If you do not have a computer running the
Process Server application, all jobs will simply sit in an Active state—nothing will get processed.
In the Millennium 3 system, the processing machines handle the job of building and printing reports, checks, and tax forms. They also process the end data transfer jobs to and from the end clients; these are known as synchronization jobs.
C. The Synchronization Server application
Like the term “Process Server,” many people mistakenly use this term to refer to a separate machine that performs a function. The Synchronization Server application is the part of the Millennium 3 system that is responsible for receiving synchronization requests from downstream sites.
This application—and the machine it runs on—becomes the conduit for data transfers between the service bureau and end clients. The Synchronization Server machine is the only Millennium 3 component that needs to be accessible to/from
the Internet. Even though the access is strictly limited, a qualified network administrator should assist with the configuration as router and firewall changes will be necessary.
D. Other applications are packaged with the system, but they are outside the scope of this document.
Release 3.29
7
8
Chapter 1
E. MPAY occasionally creates utilities you can use with the Millennium 3 system to make specific bulk changes (for example, change EFile status, Employee Import, and so on). These utilities are usually distributed via knowledge base articles.
For an explanation of the system components, see the Millennium 3 System Architecture document.
The document is available in Knowledge Base article 1165.
What Are the Prerequisites?
If you have not done so already, please read the Millennium 3 System Requirements document, which provides information on hardware and networking requirements.
The document is available in Knowledge Base article 1165.
IMPORTANT
MPAY offers some specific information and steps concerning other products as a helpful gesture to assist you; however, such instruction goes beyond the scope of MPAY’s business.
If you have questions beyond what is provided here, or need assistance with purchasing, setting up, running, or maintaining your organization's computer systems—hardware, software (including Microsoft), and networking—please seek help from sources that provide those services.
Once you have confirmed that all prerequisites are met, you can install Millennium 3.
Millennium 3 Installation
M3-Install-GD-SB-647-01
Part 1 — SQL Server 2008
The chapter contained in this part of the book concerns the installation of Microsoft SQL
Server 2008 for use with the Millennium 3 system.
Release 3.29
•
•
•
•
9
1 SQL Server 2008
10
•
•
•
•
Installation Guide
Installing SQL Server 2008 R2
Chapter 2
This chapter describes the steps you must take to install and configure SQL Server 2008
R2 for use with Millennium 3. This chapter includes the following subjects:
•
Requirements for SQL Server 2008 R2
•
Select the Edition of SQL Server
•
Note
Any links provided in this chapter were current as of the time of this writing. Microsoft and other vendor sites change URLs without notice; therefore, be prepared to use an online search engine if a link fails.
Requirements for SQL Server 2008 R2
Make sure to visit Microsoft’s Web site and verify you have met all the requirements needed to install and run this application: http://msdn.microsoft.com/en‐us/library/ms143506.aspx
Select the Edition of SQL Server
The web site for family of SQL Server products is found on Microsoft’s site: http://www.microsoft.com/sqlserver/en/us/default.aspx
Microsoft has several editions of SQL Server: Enterprise, Standard, Compact, and so on.
Choose the one that’s right for your organization. When you download the files, do not run the installation from the Microsoft site. You should save the files first, then run/open the files for installation.
Important
MPAY recommends you consult with an IT expert about selecting and installing SQL
Server. Whether they are a member of your staff or a consultant, it is important you make the correct choice and get help with a proper installation & setup.
Release 3.29
11
Chapter 2
Installation
Again, MPAY recommends you have an IT expert install SQL Server for you.
Once the installation is complete, proceed to the next chapter.
12 Millennium 3 Installation
M3-Install-GD-SB-647-01
Part 2 — Millennium 3
The chapters contained in this part of the book concern the installation of the various components of the Millennium 3 system.
Release 3.29
•
•
•
•
13
2 Millennium 3
14
•
•
•
•
Installation Guide
Chapter 3
Overview of Millennium 3 Installation
This chapter describes the steps you must take to install and configure Millennium 3. It includes the following subjects:
•
What Type of Installation Are You Doing?
•
Service Bureau Installation Process
•
End‐Client Installation Process
What Type of Installation Are You Doing?
There are two primary types of installations:
• Service bureau
• End‐client
Demo setups used by service bureau sales personnel are usually similar to an end‐ client installation.
Each installation has its own typical needs, which are explained in the sections that follow.
Service Bureau Installation Process
When you install the system for a service bureau, follow these major tasks:
A.
B.
Set Up Your File and Print Server
C.
Download the Millennium 3 Installation Package
D.
E.
F.
G.
Set Up Your Processing Machines
H.
Setting Up a Synchronization Server
I.
Setting Up Other Workstations in Your Organization
The sections that follow explain the detailed steps for each major task.
Release 3.29
15
Chapter 3
Set Up Your Database Server
This is usually done by a qualified network or database administrator.
Set Up Your File and Print Server
This is usually done by a qualified network or database administrator.
End-Client Installation Process
For this procedure, see
Chapter 9, “Installing End‐Clients.”
16 Millennium 3 Installation
Chapter 4
Installing Millennium 3
This chapter describes the steps you must take to install and configure Millennium 3. It includes the following subjects:
•
Download the Millennium 3 Installation Package
•
Download the Millennium 3 Installation Package
To download the Millennium 3 installation program, perform the following steps:
1. Go to www.mpaysoftware.com
and log in.
2. Navigate to
Support > Product Updates > Millennium 3 > Download Latest Version
.
The site displays the Download Latest Version page, as shown in
Release 3.29
17
Chapter 4
Figure 1: Download Latest Version page
18
You will download (save) the Millennium 3 installation file to your file server.
Saving it to the server’s hard drive allows you to run the installation file on multiple computers without the need to download it multiple times.
3. Click the
Download Millenn3nnn.exe
link (where nnn is the minor version number of the current Millennium 3 release).
The site displays the Download page, as shown in Figure 2 :
Millennium 3 Installation
Figure 2: Download page
Installing Millennium 3
If your download doesn’t automatically start after 30 seconds, click the
here
link shown above.
When the site begins to download the file, your browser will display a pop‐up window, similar to the one shown in
:
Figure 3: Opening MillennXXXXX.exe dialog
Release 3.29
4. Click the Save button and save the file to a location where it can be accessed by other computers on your network.
If you intend to install Millennium 3 on just one workstation, you can save the file to the desktop, the Downloads folder, or whatever location is easiest for you to remember.
shows an example of saving the file to your desktop:
19
Chapter 4
Figure 4: Choose a download location
5. Choose your location to save the file.
The download begins. When the download is complete, you can either run the program or close the window and run the install file later.
Install Millennium 3
To install Millennium 3, perform the following steps:
1. Ensure you have your Millennium 3 license key handy.
2. Double‐click the downloaded file to launch the Millennium 3 installation on the first workstation.
The Windows operating system displays the following warning:
Figure 5: Open File - Security Warning dialog
20
It is safe to continue the installation.
3. Click the Run button.
Millennium 3 Installation
Figure 6: Welcome page of the Millennium 3 Installer dialog
Installing Millennium 3
4. At the Welcome screen, press the Next button to continue the installation.
The installation program displays the Customer Information page:
Figure 7: Customer Information page of the Millennium 3 Installer dialog
Release 3.29
5. Fill in the User Name, Organization, and Serial Number fields.
6. Click the Next button.
The installation program displays the Destination Folder page:
21
Chapter 4
Figure 8: Destination Folder page
7. Select your destination folder (or keep the default setting shown above) and click the Next button.
The installation program displays the Ready to Install the Program page:
Figure 9: Ready to Install the Program page
22
Millennium 3 now has all the information it needs to complete the installation on the first workstation. You can click the Back button to change any previous selections, or press the Install button to continue the installation.
Millennium 3 Installation
Installing Millennium 3
8. One the install is complete, click the Finish button.
This concludes the third major task in the installation process. You are ready to proceed with creating your Millennium database.
Release 3.29
23
Chapter 4
24 Millennium 3 Installation
Chapter 5
Creating the Millennium Database
This chapter describes the steps you must take to install and configure Millennium 3.
It includes the following subjects:
•
•
Create the Database
To create and configure your production Millennium database from the workstation used in the preceding section, perform the following steps:
1. Open Millennium 3 on the first workstation.
The system displays a dialog similar to the following:
Figure 10: Create New Database dialog
2. Click the Yes button to create the database.
The system displays the Specify the SQL Server Computer page:
Release 3.29
25
Chapter 5
Figure 11: Specify the SQL Server Computer page
26
3. Select your SQL Server computer (the SQL Instance name) from the Server drop‐ down list.
Even though you can type the name of the SQL Instance name into the field provided, you should select it from the drop‐down list. If the SQL Instance name does not appear, that is an indication that:
• Something is not ready with SQL, –and–
• You should cancel the database creation process until you have remedied the situation with the SQL Instance
4. Click the Next button.
The system displays the Specify the Millennium Database page:
Millennium 3 Installation
Release 3.29
Creating the Millennium Database
Figure 12: Specify the Millennium Database page
5. Select the Create a new Millennium database radio button.
6. Enter the name of the new database in the Database text field.
7. Click the Next button.
The system displays the Login to the SQL Server page:
Figure 13: Login to the SQL Server page
27
Chapter 5
Before you can create your database, you must log into the SQL Instance with a username and password that has “System Administrator” level rights to SQL.
The default username is sa. You would have defined the sa password during setup if you used one of the following:
•
Chapter B, “Installing SQL Server 2008 R2 Express Edition SP1”
–or–
•
Appendix A, “Installing SQL Server 2005 Express Edition SP4”
Otherwise, check with the network or database administrator for this password.
If you see an error dialog that mentions “password validation failed,” check your
SQL error log. The error log will be in a sub‐folder where SQL was installed; for example:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG
The error log will record failed logins by default. The error will most likely look something like the following:
2011‐11‐18 09:07:20.55 Logon Error: 18456, Severity: 14, State: 5.
2011‐11‐18 09:07:20.55 Logon Login failed for user 'Millennium'. [CLIENT: 192.168.1.127]
SQL 2008 automatically tries to create any new user with the “Enforce Password
Policy” option enabled, and the password for the “Millennium” SQL account does not meet this requirement. At this point, someone must manually create the
“Millennium” SQL account, assign it a password, and remove all three check marks from the password policy check boxes. Once this is done, you will need to cancel and then restart the database creation process from the beginning of this section.
After you have successfully logged into SQL and the user called “Millennium” has been created, you are prompted to enter a database name (the default name is
Millennium
).
8. Click the Next button to continue.
The system displays the Specify Data Source Name (DSN) page:
28 Millennium 3 Installation
Release 3.29
Figure 14: Specify Data Source Name page
Creating the Millennium Database
Next, you must specify the data source name (DSN). For simplicity of naming, the
DSN usually has the same name as your new database.
9. Enter a name in the Database (DSN) text field.
10. Click the Next button.
The system displays the QuickStart File page:
Figure 15: QuickStart File page
29
Chapter 5
The Millennium 3 uses the QuickStart file (QSF) to:
• Create your database
• Set up the database structure
• Begin to populate the database with data
• Establish a two‐way trust to a specific upstream synchronization site
The example in Figure 15 on page 29 is the default QSF used for service bureau
installations that is bundled in Millennium 3.
11. Either use the default QSF or click the Browse button to locate another QSF.
12. Click the Next button.
Once the database has been created, the system displays the Specify Shared File
Location page:
Figure 16: Specify Shared File Location page
30
You must specify a place to put the shared system files that Millennium requires.
These files are usually placed on your file server.
Note
Whoever is doing the initial installation of Millennium 3 must have “Full Share” permissions as well as “Full File and Folder” rights to the selected folder.
13. Use the Browse button to select the appropriate folder.
14. Click the Next button.
Millennium 3 Installation
Creating the Millennium Database
Once the files has been copied, the system displays the Millennium Server Setup
Complete page:
Figure 17: Millennium Server Setup Complete page
Your setup of the Millennium database is now complete. The next steps in the process are to configure the system so it is ready to use.
15. Click the Finish button.
Configure the Database
1. Log into Millennium 3 with the initial default username and password of Admin.
2. Go to
System > Setup > Online Help info
tab.
The system displays the Online Help Information page:
Release 3.29
31
Chapter 5
Figure 18: Online Help Information page
3. Click the Import Help Information button.
The system displays the Open dialog:
Figure 19: Open dialog
32
4. Navigate to the following folder and open the M3Doc file, as shown in Figure 19 :
C:\Program Files\Millennium 3\Server\Quickstarts
If you skip this step, the system will have no help text available.
5. Select the
Server Info
tab.
The system displays the Server Information page:
Millennium 3 Installation
Figure 20: Server Information page
Creating the Millennium Database
Release 3.29
6. Fill in the Description/Name field.
7. Put a check in the This site is a processing site check box.
8. Select the
SB Info
tab.
The system displays the SB Info page:
33
Chapter 5
Figure 21: SB Info (service bureau information) page
34
9. Complete the fields under each sub‐tab, as necessary.
10. Select the
System > Synchronization > Upstream Site
tab.
The system displays the Upstream Synchronization Site page:
Millennium 3 Installation
Creating the Millennium Database
Figure 22: Upstream Synchronization Site page
Release 3.29
11. Click the Synchronize Now button perform the initial syncUP with MPAY.
For more information on the next three steps, see the Security Guide.
12. Select the
System > Security > Users
tab.
The system displays the Users page:
35
Chapter 5
Figure 23: Users page
36
13. Change the default administrator password by highlighting the Admin user (as shown in
) and clicking the Change Password button.
14. [Optional] Add more initial users and roles to Millennium 3.
Millennium 3 Installation
Chapter 6
Setting Up Dedicated Process Servers
This chapter describes the steps you must take to install and configure Millennium 3. It includes the following subjects:
•
Set Up Your Processing Machines
•
Set Up Multiple Services with Unique Names
•
Set Up Printers for the Processing Machines
•
Restart the Process Server Service
Set Up Your Processing Machines
To set up your processing machines, perform the following steps:
1. Choose one username that will run the Millennium 3 Process Server service.
This username should be a network (domain) administrator‐level account with a password that does not expire.
2. Log onto the machine that will become a Process Server, using the username you chose in the previous step.
You must stay logged onto the computer with this account for the rest of this section.
3. Install Millennium 3 on the computer that will become a processing machine.
4. Once Millennium is installed, go through the same database setup that you did on
the first workstation ( Chapter 5, “Creating the Millennium Database”
)—but this time, select an existing database.
Ensure you can log into Millennium before proceeding.
5. Set up the
ProcessServer.exe
application to run as a service: a. In the Windows operating system, open a command window (run cmd.exe).
The system displays the command window:
Release 3.29
37
Chapter 6
Figure 24: Command window (cmd.exe) b. Change the directory to the folder where you installed Millennium 3.
c. To see all the options available to the process server command, you can type the following at the command line:
processserver /?
The system displays the options:
Figure 25: processserver /?
38
You can install more than one Process Server service on a single machine. For
more details, see “Set Up Multiple Services with Unique Names” on page 40
.
d. If you have called your database Millennium, install the service by typing the command below and pressing the
[Enter]
key:
Millennium 3 Installation
Setting Up Dedicated Process Servers
processserver /I
The system displays the following warning and message:
Figure 26: processserver /i
Release 3.29
If you have named your database something else, use the following command instead, substituting databasename with the actual name of your database:
processserver /I /D databasename e. Type exit and press the
[Enter]
key to close the command window.
f. In the Windows operating system, select
Start > Control Panel > Administrative
Tools > Services
.
The system displays the Services window.
g. Scroll down and locate the Millennium Process Server line, as shown in
Figure 27: Services window
39
Chapter 6 h. Right‐click on the Millennium Process Server line.
The system displays the Millennium Process Server Properties dialog.
i. Select the
Log On
tab, as shown in
:
Figure 28: Process Server Properties dialog
40 j. Select the This account radio button, as shown in
.
k. Enter the account you chose in
step 1 on page 37 in the text field next to the
Browse button.
l. Enter the account’s password in the Password and Confirm password fields.
m. Click the OK button.
n. Do not close the Services window; it is required in a subsequent step.
Set Up Multiple Services with Unique Names
You can install more than one Process Server service, each with a unique name. This allows you to install it multiple times on a single machine.
Millennium 3 Installation
Setting Up Dedicated Process Servers
Note
Any existing installation of the Process Server service must be uninstalled from its machine before the new Service Name and Service Display Name options can be used.
When you install more than one Process Server service:
• Provide each instance with a unique service name and service display name.
• As shown in
• Specify the service name using the /ServName option.
• Specify the service display name using the /ServDisplayName option.
Here is an example of installation commands for three unique services:
Processserver /I /ServName M3Proc01 /ServDisplayName Millennium Process Server 1
Processserver /I /ServName M3Proc02 /ServDisplayName Millennium Process Server 2
Processserver /I /ServName M3Proc03 /ServDisplayName Millennium Process Server 3
Set Up Printers for the Processing Machines
1. Choose one username that will run the Millennium 3 Process Server service.
This username should be a network (domain) administrator‐level account with a password that does not expire.
2. Log onto the machine that will become a Process Server, using the username you chose in the previous step.
You must stay logged onto the computer with this account for the rest of this section.
3. Add all printers that will be used by Millennium 3 as Windows printers: a. Ensure you set the Windows default printer to a physical printer.
b. Log in to Millennium 3.
c. In Millennium, select
System > Setup > Printers
tab.
d. To add a printer, click the yellow star button in the page header:
Figure 29: Yellow star button to add an item
The system displays a pop‐up window in which you type in a printer code:
Release 3.29
41
Chapter 6
Figure 30: Please Enter a Printer Code dialog e. Enter the printer’s ID and click the OK button.
The system adds the printer to the items list.
f. Enter the appropriate information in the Description field.
g. Select the appropriate printer from the Physical Printer drop‐down list.
h. Be sure to specify one printer as the Millennium default printer by putting a check in the Default Printer check box.
i. Repeat these steps to add more printers, as necessary.
Restart the Process Server Service
4. Return to the Services window and start the Millennium Process Server service, as shown in
:
Figure 31: Services window
42
5. Close the Services window.
6. Repeat the steps in this section for each additional processing machine.
Millennium 3 Installation
Setting Up Dedicated Process Servers
Specifying the Name of the Service
Installation of Millennium 3 servers (Process Server and SyncServer) accept two optional arguments that control the name of the service being installed, as well as the name that is displayed in the service control panel.
Install service
ProcessServer.exe /I [/N username] [/P password] [/ServName <service name>]
[/ServDisplayName <service description>] [args]
Uninstall service
ProcessServer.exe /U [/ServName <service name>]
Query service
ProcessServer.exe /Q [/ServName <service name>]
Release 3.29
43
Chapter 6
44 Millennium 3 Installation
Chapter 7
Setting Up a Synchronization Server
This chapter describes the steps you must take to install and configure Millennium 3. It includes the following subjects:
•
Prepare Your Synchronization Server Machine
•
Set Up Your Synchronization Server as a Service
•
Set Up Multiple Services with Unique Names
•
Start the Synchronization Server Service
Prepare Your Synchronization Server Machine
First, you must prepare your synchronization server by performing the following steps:
1. Choose the username that will run the Millennium Synchronization Server service.
This username should be a network (domain) administrator‐level account with a password that does not expire.
2. Log onto the machine that will become a Sync Server, using the username you chose in the previous step.
You must stay logged onto the computer with this account for the rest of this section.
3. Install Millennium 3 on the computer that will become a processing machine.
Set Up Your Synchronization Server as a Service
Next, you must set up the
SyncServer.exe
application to run as a service:
1. In the Windows operating system, open a command window (run cmd.exe).
The system displays the command window:
Release 3.29
45
Chapter 7
Figure 32: Command window (cmd.exe)
2. Change the directory to the folder where you installed Millennium 3.
3. To see all the options available to the synchronization server command, you can type the following at the command line:
syncserver /?
The system displays the options:
Figure 33: syncserver /?
46
You can install more than one Synchronization Server service on a single machine.
For more details, see
“Set Up Multiple Services with Unique Names” on page 49 .
4. If you have called your database Millennium, install the service by typing the command below and pressing the
[Enter]
key:
syncserver /I
Millennium 3 Installation
Setting Up a Synchronization Server
The system displays the following warning and message:
Figure 34: syncserver /i
Release 3.29
If you have named your database something else, use the following command instead, substituting databasename with the actual name of your database:
syncserver /I /D databasename
If you want to use a TCP/IP port other than 80, use the following command instead, substituting portnum with the actual port number:
syncserver /I /O portnum
Note
The default TCP/IP port 80 is the same port used for web browsing. It is often the best port to use because your clients will not need to make any firewall changes of their own.
However, this also means that the machine running
SyncServer.exe
:
• Must have its own public TCP/IP address
• Cannot run a web server
5. Type exit and press the
[Enter]
key to close the command window.
6. In the Windows operating system, select
Start > Control Panel > Administrative
Tools > Services
.
The system displays the Services window.
7. Scroll down and locate the Millennium Synchronization Server line, as shown in
47
Chapter 7
Figure 35: Services window
8. Right‐click on the Millennium Synchronization Server line.
The system displays the Millennium Synchronization Server Properties dialog.
9. Select the
Log On
tab, as shown in
Figure 36: Synchronization Server Properties dialog
48
10. Select the This account radio button, as shown in Figure 36
.
11. Enter the account you chose in step 1 in the text field next to the Browse button.
12. Enter the account’s password in the Password and Confirm password fields.
Millennium 3 Installation
Setting Up a Synchronization Server
13. Click the OK button.
Set Up Multiple Services with Unique Names
You can install more than one Synchronization Server service, each with a unique name. This allows you to install it multiple times on a single machine.
Note
Any existing installation of the Synchronization Server service must be uninstalled from its machine before the new Service Name and Service Display Name options can be used.
When you install more than one Synchronization Server service:
• Provide each instance with a unique service name, service display name, and port number.
• As shown in
• Specify the service name using the /ServName option.
• Specify the service display name using the /ServDisplayName option.
• Specify the port number using the /O option.
Here is an example of installation commands for three unique services:
Syncserver /I /ServName M3Sync01 /ServDisplayName Millennium Synchronization Server 1 /O 81
Syncserver /I /ServName M3Sync02 /ServDisplayName Millennium Synchronization Server 2 /O 82
Syncserver /I /ServName M3Sync03 /ServDisplayName Millennium Synchronization Server 3 /O 83
Start the Synchronization Server Service
Next, run the synchronization server as a service:
1. Return to the Services window.
2. Start the Millennium Synchronization Server service, as shown in
Release 3.29
49
Chapter 7
Figure 37: Services window
3. Close the Services window.
4. Log in to Millennium 3.
5. Select
System > Synchronization > Downstream Sites
tab.
The system displays the Downstream Synchronization Site page:
Figure 38: Downstream Synchronization Site page
50
6. Fill in the Sync Hostname field with the publicly accessible item assigned by your network administrator, which is either a:
Millennium 3 Installation
Setting Up a Synchronization Server
• Hostname (for example, sync.myservicebureau.com
)
–or–
• TCP/IP address (for example,
24.25.26.27
)
7. Enter in the TCP/IP port number specified in step 4 on page 46
.
If you did not specify that setting (see page 47
), the default is port 80.
Note
Your network administrator will need to make the necessary network changes to ensure the synchronization server is accessible from the Internet at the address and port number specified.
Release 3.29
51
Chapter 7
52 Millennium 3 Installation
Chapter 8
Setting Up Other Workstations in Your
Organization
The last step is to install Millennium 3 on the rest of your organization’s computers, as necessary.
Note
If you are going to set up a computer as a dedicated or local process server for a user
who is not a local administrator, see Appendix E, “Minimum Process Server User
Release 3.29
53
Chapter 8
54 Millennium 3 Installation
Chapter 9
Installing End-Clients
This chapter describes the steps you must take to install and configure Millennium 3. It includes the following subjects:
•
End‐Client Installation Process
•
Optional End‐Client Installation Steps
End-Client Installation Process
Note
This section assumes that your end‐client has decided to use Millennium 3 instead of
Payentry.com.
End‐client installations have similar prerequisites to service bureau installations.
However, the process differs in several key ways. Often good communication early in the process is the key to a successful end‐client installation.
1. Determine how your end‐client will use Millennium 3.
• How many people will be using it?
• Are the users at a single or multiple locations?
Users at multiple locations may require some type of remote access solution like Microsoft Terminal Server or a Citrix product. Remote access solutions are
briefly discussed in “Optional End‐Client Installation Steps” on page 58 .
• How many company codes and employees will be loaded in their system?
2. Determine you end‐client’s level of “technology preparedness.” This is especially important for end‐clients with multiple users. Find out the following:
• Does the end‐client have an existing IT staff that you can work with? If not, who is available to make firewall or network security changes?
• Does the end‐client have an existing server they use to share files? If not, whose computer will be the main “Millennium” computer?
• Do they have an existing server with SQL2005 or SQL2008 on it? If not, do they have an existing server where they will allow you to install SQLExpress?
Keep in mind that you may have to install SQLExpress on someone’s workstation.
Release 3.29
55
Chapter 9
• Are the end‐client’s users allowed to be local administrators of their own workstations? That is, do they have full and complete rights to install or run anything they want to on their computer?
If not, you may need to install the Millennium Process Server service on someone’s computer.
3. Create a QSF with your end‐client’s data.
Note
This process begins at your organization once your implementation staff has created the company in Millennium 3.
If you are unsure how to perform the steps that follow, contact your service team.
a. Create a QSF at your organization for the first end‐client company code. This
QSF will be used to create the Millennium database at the end‐client.
b. Log into Millennium 3 at your organization.
You must use the tree view to create a QSF.
c. In the tree view, select
System > Conversions > CreateQS
.
d. Enter the full path and filename of the QSF in the Filename field (for example,
\\myserver\m3files\abc.qsf
).
e. Complete the Companies field with the list of company codes you will be installing.
It is recommended that you enter a maximum of 10 company codes in a single
QSF. You can add more company codes via the synchronization process using the Full download option.
f. Complete the Destination Site Name field.
This is the name that will appear in your list of downstream sites, so should be meaningful to you.
Note
Leaving this field blank will result in a downstream site name of Unknown Site.
g. Click the Create Local File button.
The system displays the following message box:
56 Millennium 3 Installation
Figure 39: VBScript dialog
Installing End-Clients h. Click the OK button.
The system displays the following message box:
Figure 40: ActiveX dialog
Release 3.29
i. Click the Yes button to start the process.
Depending on the amount of data stored, the QSF can take anywhere from 30 seconds to 15 minutes to create. Do not use Millennium 3 until you receive another message box indicating that your quick start file has been created.
j. Copy all the information needed for the end‐client install to some place where you can retrieve them during the actual install. These include:
• The QSF you just created.
• The Millennium 3 installation file that matches version of Millennium 3 that you used to create the QSF.
• The SQLExpress installation file or files, if necessary.
• The Millennium 3 end‐client license key.
4. Install the Millennium 3 install file on your end‐client’s first workstation using the
same process detailed in “Install Millennium 3” on page 20 .
5. Create the Millennium database on the end‐client’s side using a similar to (but
more limited than) process detailed in “Create the Database” on page 25 .
a. Follow the same process detailed in step 1 and step 2 on page 25
.
b. Log into Millennium 3 with a valid service bureau username.
c. Follow the same process detailed in the Service Bureau Installation process steps 4d.
57
Chapter 9 d. Go to
System > Synchronization > Upstream Sites
tab, and click the Synchronize
Now button perform the initial syncUP with your service bureau.
e. End‐clients can usually print reports by previewing them first, then printing them from Adobe Reader. If they need to run reports or print checks, you must set up a Millennium 3 printer for them.
Optional End-Client Installation Steps
When should your end-client have a dedicated processing machine?
When should your end‐client have a computer set up as a dedicated processing machine?
The main reason to make an end‐client machine a dedicated processing machine is in the case where your end‐client’s IT staff doesn’t allow the end users to be local administrators of the computer(s) where they will run Millennium 3 from.
If this is the case, follow the same process detailed in
Chapter 6, “Setting Up Dedicated
End-clients with users at multiple locations
End‐clients with users at multiple locations present a complex set of issues and from a technical perspective are best served when using Payentry.com. However, some organizations may still request the Millennium 3 product.
In this case, a shared remote access solution like Microsoft Terminal Server or a Citrix product is a good candidate.
It is important to remember that installations such as these can be very successful.
However, shared environments usually require more time and cost to initially set up.
Maintaining proper security and controls while still allowing adequate application access can be a challenging balancing act.
The key is having an IT staff that is well‐versed in remote access solutions, as well as the technical needs of Millennium 3 at your organization, who can implement and support this type of environment.
58 Millennium 3 Installation
M3-Install-GD-SB-647-01
Part 3 — Synchronization
The chapter contained in this part of the book comprehensively explains the subject of synchronization within the Millennium 3 system.
Release 3.29
•
•
•
•
59
3 Synchronization
60
•
•
•
•
Installation Guide
Chapter 10
Synchronization
This chapter explains database synchronization in Millennium 3. Synchronization is the process of keeping portions of two or more Millennium databases “in sync” with each other through the exchange of data and structure changes.
The synchronization in Millennium has the following basic properties:
• Efficiency — Only data changes are sent between sites rather than full tables, allowing small file sizes. In addition, compression is used to further reduce file sizes.
• Reliability — A large number of verifications are performed against many aspects of both databases during each synchronization, ensuring a reliable and consistent synchronization process. Automated conflict resolution is used to handle any single piece of data that is changed differently at two sites.
• Security — Triple DES encryption and internal consistency checks are used to ensure data in transit cannot be viewed by any party except the destination site.
• Scalability — An arbitrary number of synchronization levels can be used to create a large network of sites communicating with each other.
• Compatibility — The synchronization protocol uses HTTP to communicate between sites, ensuring easy traversal of most networks and a high probability of getting through firewalls and proxy servers.
• Ease of Use — Synchronization is easy to configure, execute and monitor. In addition, useful management information is automatically maintained on the various parties synchronizing with each other.
This chapter provides the following:
•
•
The Mechanics of Synchronization
•
•
•
•
•
Synchronizing with MPAY for Hosted Millennium Licensees
Release 3.29
61
Chapter 10
Basic Operation
This section provides a basic understanding of where synchronization is configured at a site and how it is initiated.
Upstream and Downstream Sites
A site is an installation of Millennium on a series of computers, all centered around a single database. A site can have only one upstream partner, but an unlimited number of downstream partners.
From the service bureau perspective, the MPAY data center is the upstream site, and the remote data entry clients are the downstream sites. In this case, Payentry.com is also considered a remote data entry client site.
The synchronization system allows for unlimited levels of sites to communicate with each other. This means the service bureau can have an unlimited number of downstream sites, and in addition those sites can have their own downstream sites.
For more information, see the System Architecture for Service Bureaus reference document.
Installation
When a new downstream site is installed:
A. The upstream site extracts a QuickStart file (QSF).
The QuickStart file contains a copy of all the system and company data needed by the downstream site.
B. The upstream site uses the QSF to install the downstream site.
The QuickStart file also includes the address of the upstream site’s synchronization server; after installing a new downstream site, the downstream site will immediately be ready to synchronize with the upstream site.
From the Downstream Site Looking Upstream
To view a site’s upstream site information in Millennium, select the
System >
Synchronization > Upstream Site
tab.
The system displays the Upstream Synchronization Site page, as shown in Figure 41
:
62 Millennium 3 Installation
Figure 41: Upstream Synchronization Site page
Synchronization
At a service bureau, the upstream site is the MPAY data center. At a remote client site, the upstream site is typically the service bureau.
Explanations of the fields on this page are as follows:
Description
This field is automatically filled in by the upstream site.
Sync Hostname
If the upstream site’s synchronization server address changes, the downstream site can adjust its settings to match. Normally, the upstream site will automatically send its synchronization server information to the downstream sites, so this change does not need to be made at the downstream site.
Port
This field should have the value 81.
Last Transmit, Last
Receive
These fields are automatically filled in. They display the date‐time stamps from the last synchronization:
• Last Transmit is when the last upload was sent to the upstream site
• Last Receive is when the last download was received from the upstream site
Company
The list of companies shows the companies from the downstream site that are being synchronized with the upstream site.
Release 3.29
63
Chapter 10
The downstream site can make modifications to the company list, but the upstream site will override any changes made:
• If a company is removed from Company (the downstream site list), the upstream site will send a new copy of that company during the next synchronization process.
• If a company is added to Company (the downstream site list), the new company will be removed from the downstream site list during the next synchronization process—however, the company data will not be removed from the downstream site.
Full Download
The Full Download check box is empty by default, which indicates the company is being synchronized normally; that is, only changes to the data are exchanged.
If the downstream site put a check in this check box for any company, the upstream site will download a full copy of that company during the next synchronization process.
Synchronize Now,
Test Connection
The Synchronize Now and Test Connection buttons create synchronization jobs that run a complete synchronization or just test the connection to the upstream synchronization server, respectively.
After creating a job using either button, go to the
System > Operations
> Job Queue
tab to monitor the progress of the synchronization or test job.
From the Upstream Site Looking Downstream
To view a site’s downstream site information in Millennium, select the
System >
Synchronization > Downstream Site
tab.
The system displays the Downstream Synchronization Site page, as shown in Figure 42 :
64 Millennium 3 Installation
Figure 42: Downstream Synchronization Site page
Synchronization
At a service bureau, the downstream sites are all the remote client sites, including
Payentry.com. At a client site, the downstream sites list is usually empty because end clients do not require any sites to syncUP to them. However, it is possible for an end client to have satellite offices that are synchronizing through the home office.
Local Site Details
Use the Local Site Details area of the Downstream Synchronization Site page ( Figure 42
) to specify the local site’s description, as well as the synchronization server’s hostname and port.
These values are automatically included in all QuickStart files created at the local site.
This allows for easy setup of downstream sites, ensuring a new downstream site is automatically initialized with the upstream site’s location.
Downstream sites will automatically change the synchronization server address they use to match the synchronization server specified under Local Site Details at their upstream site. This allows the upstream site to easily change to a new synchronization server by installing the new server at the new address then updating the server address under Local Site Details.
Release 3.29
65
Chapter 10
The downstream sites will continue to synchronize with the old server at the old address; but as each one is synchronized, it will pick up the new address and use it on subsequent synchronizations. Once all downstream sites have synchronized and picked up the new address, the old server can be disabled.
If a bad value is entered for the synchronization server, all downstream sites will take the new (bad) value and will no longer be able to synchronize. To resolve this issue, fix the bad value at the upstream site first, then fix the value at each downstream site.
Downstream Site List
The downstream sites that are synchronizing with the local site are listed in the items list in the middle of the page (
). Included are the columns are the last synchronization times (more details below) and some system information about the downstream site’s installation.
A downstream site is automatically added to the upstream site’s list whenever the downstream site first synchronizes with its upstream site. The downstream site will only be allowed to synchronize if it was created using a QuickStart from the upstream site, but any site can automatically begin synchronizing with an upstream site using a
QuickStart file from that upstream site.
Because the downstream sites are automatically created from any upstream QuickStart file, a QuickStart file containing company information must only be provided to authorized sites, otherwise anyone can install a new site and make changes to the upstream server’s copy of the companies in the QuickStart.
Deleting a downstream site from the list of sites does not prevent the site from synchronizing with the upstream site. In fact, the downstream site will automatically be reconnected the next time it synchronizes, just as when the site was first created. To prevent a site from synchronizing, use the Disabled check box under the
Additional
Information
tab.
Company List
The company list is a list of company codes that are synchronized with the downstream site. Modifications to the company list at the upstream site generally override changes made by the downstream site. If a company is added to the list a full copy will be sent downstream during the next synchronization. If a company is removed from the list the company will be disconnected (but not deleted from the downstream site).
Normally the Full Download check box is cleared, indicating that the company is being synchronized normally. The upstream site can set this check box for any company and a full copy of the company will be download with the next synchronization. More information on this is provided below.
Additional Information
Additional system information on each downstream site list is stored and updated each time the site synchronizes.
66 Millennium 3 Installation
Synchronization
The product version is the highest version of Millennium that is running at the downstream site. Note that not all computers at the downstream site may be running this version, but at least one of them was.
The database version is the schema version of the database, which is independent of the product version. This cannot be higher at the downstream site than at the upstream site.
The downstream site will automatically receive schema updates from the upstream site, so all active sites are typically at the same schema version.
The SQL server computer name and the database name are also obtained from the downstream site. This is very handy when a technician needs to make system changes at the downstream site.
The license key is also listed for each downstream site, greatly simplifying license management.
Running Synchronization
Initiating a Synchronization
Synchronization is always initiated by the downstream site, never the upstream site. The downstream site can “pull” updates from the upstream, but the upstream cannot “push” updates to the downstream.
A synchronization can be initiated in one of three ways: by explicitly requesting a synchronization with the upstream site, by submitting a payroll for processing at a non‐ processing site, or via a scheduled synchronization.
An explicit synchronization can be initiated via the company main menu or through the upstream synchronization screen.
Submitting a payroll at a non‐processing site will also initiate a synchronization. The upstream site will receive the data then submit the payroll for processing. If the upstream site is also not a processing site it will synchronize with its upstream site. The payroll will continue to be submitted and synchronized upstream until a processing site receives it.
If you have a dedicated process server, you can use a job schedule to automate the synchronization process on a scheduled basis. The job schedule should be for a SyncUp job, and no properties need to be set. Beware that setting scheduled synchronizations to run at client sites can cause a heavy load on the upstream site’s synchronization server once many downstream sites are installed. It most cases it is recommended that service bureaus do not configure scheduled synchronizations at remote client sites unless absolutely necessary.
Release 3.29
67
Chapter 10
Synchronization Jobs
At the downstream site a single SyncUp job is used to implement the synchronization with the upstream site. This job will connect to the upstream site, verify the synchronization can be run, exchange and merge data changes, and confirm the synchronization. The job results show the number and type of changes made during the synchronization.
At the upstream site three individual SyncDown jobs are used to implement the synchronization. These three jobs correspond to the extract, merge and confirm steps of the synchronization. Separate jobs are used in case the downstream site disconnects abnormally from the synchronization server and does not reply to one of the stages. The
SyncDown jobs list the site name they are running for. Because a single SyncDown job may be synchronizing multiple companies, the SyncDown job does not list a company code.
Versions and Synchronization
Database Version Updates Sent Downstream
The synchronization process requires that any two databases that are synchronizing have exactly the same structure. This ensures the same tables and fields will be updated at both sides. The particular database structure in use at a site is tracked using the database schema version. Note that this is not the same thing as the Millennium program version, which changes independently of the database schema version.
Schema updates are automatically sent from an upstream site to its downstream sites during a synchronization. This automatically upgrades a downstream site to the same schema version as its upstream site and ensures the downstream site can always synchronize properly, regardless of the program version in use at either site. Schema updates originate at MPAY and are sent downstream throughout the entire synchronization network.
Note
A downstream site cannot have a higher schema version than its upstream site.
If this occurs, the downstream site will not be able to synchronize with the upstream until the upstream is upgraded to at least the same schema version as the downstream site. This is because schema updates are only sent downstream.
68 Millennium 3 Installation
Synchronization
Keeping the Service Bureau Updated
A downstream site will not be able to synchronization with its upstream site if the downstream site has a higher schema version than the upstream site. This can happen if the upstream site has not been synchronizing with its upstream partner and the downstream site is upgraded to the latest program version, which in turn upgrades the downstream site to the latest schema version.
To avoid this scenario occurring between a service bureau and its clients, every service bureau site should synchronize with its upstream site (MPAY) after a new release is made available. This ensures the service bureau is always running at the latest schema version and thus can synchronize with a site running any program version.
If the service bureau is always running the latest schema version, no downstream client site can upgrade its schema beyond what the service bureau is running, and thus the service bureau can always synchronize with any site running any program version.
This is especially important for service bureaus using Payentry.com. The Payentry.com site is a downstream site to a service bureau and is regularly updated to the latest program version and schema version.
If the service bureau is not at the latest schema version, an update at Payentry.com may cause the synchronization between the service bureau and payentry.com to fail.
If the service bureau synchronizes with MPAY whenever new releases are made available (and is always running the latest schema version), Payentry.com will always be able to synchronize with the service bureau.
The Mechanics of Synchronization
The following section explains what data is exchanged between two sites and how it flows between the sites.
What Data is Exchanged
The synchronization process works by exchanging all updates made by two sites between those two sites. During a synchronization, each site extracts and sends the other site a list of the changes that were made, then receives and merges changes made by the other site.
Changes made at a site will propagate throughout the synchronization network via all of a site’s upstream and downstream partners. For example, if two remote client sites both share a company code, employee changes made at one site will be synchronized upstream to the service bureau, then downstream to the other site.
All data is filtered through the company list, so only data relevant to the companies being synchronized by both sites is exchanged.
In general, system level data is sent from upstream to downstream only. Thus changes made at a downstream site are not sent upstream and are ignored. In general, company and employee level data is exchanged in both directions.
Release 3.29
69
Chapter 10
The MPAY data center is the upstream site for all service bureaus. Tax data and other important system data is sent to all service bureaus via synchronization, and from the service bureaus the changes are then propagated to client sites and any other sites connected to the sync network.
For a list of tables that are:
•
Exchanged, see Appendix C, “Database Tables: Synchronized”
• Not exchanged, see
Appendix D, “Database Tables: Not Synchronized”
The User Who Made a Change
Changes made at a site are always logged with name of the user who made the change.
When changes are transmitted through synchronization the log stores the remote site
ID as the user who made the change. The individual at the remote site who made the change is not logged at the local site, although the original name is still logged at the remote site.
Last Transmit and Receive Times
Data is sent from one site to another based on the time when it was changed. All data that has been modified since the last time a synchronization was run successfully will be sent to the remote site.
The Last Transmit and Last Receive synchronization times (see
) indicate the times when data was last sent from one site to the other. The Last Transmit time on an upstream site’s record is the same as the Last Receive time at the downstream site, and vice‐versa.
shows the synchronization times as stored at two sites:
Figure 43: Sync times as stored at two sites
70
The times are always stored in the sender’s time zone:
Millennium 3 Installation
Synchronization
• The Last Transmit time is always the time (in the local time zone) that the local site last sent data to the remote.
• The Last Receive time is always the time (in the remote time zone) that the remote site last sent data to the local.
The synchronization times are automatically maintained by the synchronization process. The times should never be changed manually. In the event that the times disagree, the Last Receive time at the receiver’s site has precedence over the Last
Transmit at the transmitter’s site.
, it appears a two hour two minute discrepancy exists between the Transmit and Receive times. If these two computers are in time zones that place them two hours apart, the difference is really only two minutes.
Verification and Security
Many checks are performed during synchronization to verify the integrity of the databases being synchronized as well as the identity of the sites synchronizing.
Each site is assigned a unique identifier that is placed into a QuickStart file when it is created. A new downstream site created with the QuickStart file can only synchronize to the site that created the QuickStart file. The upstream’s unique ID is used as a key to ensure that only downstream sites that have the key can be synchronized to the upstream site. Both sites must always have each other’s key before the synchronization can proceed.
Before any data is synchronized both sides must agree on the schema (structure) of the databases they are synchronizing. An upstream site will automatically send schema changes to its downstream sites to ensure they are both using the same schema and thus synchronizing the same tables and fields.
During synchronization, each field in each table synchronized is compared to ensure the same fields exist at both sides and each field has the same type. This guarantees data will not be lost due to changes in field types, or the addition or deletion of fields in a table.
The data files in transit are encrypted using Triple‐DES and can only be read by the remote site receiving the files. Triple‐DES is a widely recognized encryption standard that uses 168‐bit keys and provides a high degree of security.
Conflict Resolution
This section describes how conflicts are resolved during synchronization.
What Conflicts Are Recognized
A conflict occurs when two sites synchronizing data make different changes to one piece of data. For example, an employee’s middle name may be changed to “Sean” at the upstream site, but “Shawn” at the downstream site. The conflict must be found and resolved to ensure data integrity between the two sites.
Release 3.29
71
Chapter 10
Millennium recognizes data that ultimately exists at both sites but has different values for at least one field. If a record is updated differently at the two sites, or the same record was created differently at two sites, a conflict occurs. If a record is deleted at one site and changed at the other, the delete prevails and the record is always removed. This case is not considered a conflict.
Millennium uses a unique identifier to distinguish each record in a table internally. This identifier is typically used to recognize that the same record was changed at both sites.
In addition to the unique identifier, the conflict resolution system can identify when two records have been added that have different identifiers (as they always will if they are created at different sites) but represent the same record.
For example, if employee 5 is added to a company at two different sites, the identifiers will be different—but the two records still represent the same employee and must be checked for conflicts.
How Conflicts Are Resolved
Conflicts are automatically resolved by selecting the upstream or downstream site as having precedence based on the data being changed. In general the downstream site has precedence for all employee setup data. Employee setup data includes any employee level information that is used for all payrolls, such as demographics, rates, deductions, taxes, direct deposit, and so on. The upstream site has precedence for all other data, including all system and company level data, as well as historical employee data such as payroll history.
When conflicts are found during synchronization, both sites will log the table and record where the conflict occurred. Each field that is in conflict will be logged in the SyncUp and SyncDown jobs using the unique identifier. In addition, both field values that are in conflict will be logged at both sites in an internal table that can be reported on. You can use the Synchronization Conflict Resolution report (available for Millennium 3 only, not
Payentry.com) to determine what conflicts occurred and how they were resolved, including what field values were not used.
Working With Conflict Resolution
Conflicts can be easier to create than first imagined. If one site makes a modification to a record then restores the original value, the change will still be sent to the remote site when synchronizing. If the remote site were to change the same field, a conflict will occur.
For example, if the upstream site changes a calendar from the Open to the Closed state, then resets it to Open, the final change sent downstream will be to Open. The upstream site may have only been testing or verifying that the calendar can be closed. At the same time, the downstream site may change the calendar from Open to Closed in preparation to submit the calendar.
When the synchronization is run, the calendar will end up in the Open state after resolving the conflicting change (Open at the upstream vs. Closed at the downstream) in favor of the upstream (which has precedence for all company‐ level data).
72 Millennium 3 Installation
Synchronization
Beware that other changes that may appear to be handled by the conflict resolution may not be. When creating records many tables only require unique identifiers on records, allowing them to be otherwise identical. Records created at two sites with different identifiers in these kinds of tables are not considered in conflict and will coexist.
For example, an employee deduction can be created at two sites at the same time with identical values, except for the internal unique identifier. When these changes are synchronized each site will end up with two identical deductions, since each site asked for a the same deduction to be created without knowledge of the other site having done so.
This problem is further complicated when trying to delete the duplicate records. If each site deletes only one record, but they each delete a different a record
(upstream deletes the first copy, downstream deletes the second) both records will end up being deleted when the synchronization runs next.
The problem of duplicate records being created is especially sensitive with respect to starting a payroll. Only one site should ever start a payroll on a calendar entry. If both sites start the payroll the calendar will have duplicate checks for each employee.
The easiest way to avoid these issues is for only one site to make updates to a given table.
Although either site can make a change and synchronization it to the other at any time, if only one site typically makes changes to a particular tables, the chances of conflicting changes and duplicate records are greatly reduced.
Caveats
The following are caveats in synchronization that may cause errors or problems if not handled carefully.
Starting Payroll
Starting Payroll creates the data entry checks along with the default details, and sets the payroll and batches to the Open status.
Synchronization will send the new check records to any synchronization partner when synchronizing. If a synchronization partner also performs a Start Payroll on the same payroll, they will create their own new check records (with unique IDs). The new check records will then be exchanged between the partners, and each site will end up with double the expected number of checks.
This is normal, since each site started payroll and created checks independently. To avoid this situation, be sure to always run Start Payroll at only one location for any given payroll.
New Hires
Each new employee created in Millennium is given the next available employee ID number. If two synchronization partners each enter a new employee in the same company, the two different employees will each be assigned the same ID number.
Release 3.29
73
Chapter 10
When synchronizing, the ID numbers will cause a database error, since each employee must have a different ID.
To avoid this situation, either enter new employees in only one location, or be sure to use different employee ID ranges at each site.
Manual Checks
When creating manual checks, Millennium automatically creates a VM batch to contain the checks. If two synchronization partners each create a manual check in the same payroll, they will each create a VM batch.
When synchronizing, the two conflicting new VM batches are resolved into one, but the checks in the VM batch at the downstream site are deleted when the VM batch conflict is resolved. The checks from the downstream site are correctly uploaded to the upstream site and can be processed, but the entry checks will not appear at the downstream site.
To avoid this situation, always enter manual checks at only one location.
Deleting and Recreating Data
Millennium tracks all changes to records based on their internal unique identifier. If a record is deleted and recreated, the new record will have a different unique identifier.
The identifier of the new record will always be different, even if the new record has the same field values as the old record. The old identifier can not be reused in the new record.
Synchronization will transmit a delete of the old record and an insert of the new record.
This is normally not a problem, but in some cases the deletion of the old record at a synchronization partner may cause the deletion of records that were dependent on the deleted record. These dependent records may have been created at a synchronization partner and may not exist at the site where the record is initially deleted and recreated.
This is a problem with payroll batches in particular, as mentioned above with VM batches.
To avoid this situation, do not delete an recreate records unless deleting the record is known to be safe.
Full Company Downloads
The full company download feature of synchronization allows all the data associated with a company to be sent downstream during a synchronization. A new company can be sent to a downstream site who has not had a copy of the company before, or an existing synchronized company can be sent downstream to overwrite the existing data.
74 Millennium 3 Installation
Synchronization
Sending a New Company
Sending a new company downstream downloads all data associated with a company to the downstream site when that downstream has not previously had a copy of the company. The company does not have be a new company, just a company that a particular downstream site has not seen before.
Only the upstream site can send a new company downstream. If the downstream site tries to add the company the request will be declined and the company removed from the synchronized company list at the downstream site.
To send a new company downstream, select the company list for the downstream partner and add the company code to the list. After adding the company code check the
Full Download check box. This must always be checked when adding a company to a downstream site company list.
During the next synchronization all data associated with the company will be sent to the downstream site. The downstream site will then have a full copy of the company and the company will be synchronized the same as all other companies.
Resending an Existing Company
Resending an existing company will download all data associated with a company to the downstream site, overwriting all data currently at the downstream site. This can be used to refresh a copy of the company at the downstream site if it has become corrupt or if the downstream site has made changes they do not want sent upstream.
Either the upstream or downstream site can request that a new copy of the company be sent downstream during the next synchronization.
To resend an existing company downstream, select the company list for the remote partner (either upstream or downstream depending on who makes the request) and check the Full Download check box for the company code in the list.
Simplifying New Downstream Site Installation
The ability to send a new company downstream coupled with the ability to create a single QuickStart file for use in installing multiple downstream sites means a service bureau can greatly simplify new client installations if it is willing to send all companies via sync. A simple QuickStart file can be created at the service bureau that contains only sample companies. The simple QuickStart file can then be used to create multiple downstream sites which each then receive the appropriate companies via synchronization.
This allows a sales person to initially install Millennium as a demo system and not sync with the service bureau, although the capability is already there via the sync settings sent in the QuickStart file. The new site can create a test company for use in evaluation.
If the site is to become a live site, the company can be created at the service bureau then synced down to the downstream site.
Release 3.29
75
Chapter 10
Future versions of synchronization will also include an upload feature that will allow new companies created at a downstream site to be uploaded to the service bureau. This will allow the sales rep to create a more realistic company for the new client and upload it immediately should they agree to become a customer.
Disconnecting a Company
If a company should no longer be synchronized it should be removed from the company list at the upstream site. This will cause the company to stop being synchronized, although an orphaned copy of the company will still reside at the downstream site.
Adding the company back to the list at the upstream site will cause a new copy of the company to be sent back downstream and again synchronized.
Note that removing the company from the company list at the downstream site, or even deleting the company at the downstream site, will NOT disconnect the company. During the next sync the upstream site will have precedence and will realize it should be syncing the company with the downstream site, causing a new copy to be sent downstream. To remove a company from a downstream site, first remove the company from the company list at the upstream site, then optionally delete the company at the downstream site.
Network and Protocol Details
This section describes the synchronization protocol in more depth in order to help technical personnel implement the system and troubleshoot any problems.
Underlying HTTP Protocol
Synchronization uses the HTTP protocol to transport data between the upstream and downstream sites. HTTP is a very common protocol that allows connections to be made reliably between the two sites.
The Millennium synchronization server acts exactly like a web server in that it responds to HTTP requests, although it only understands the requests used by synchronization. A web browser can be used to verify that a synchronization server is operating by connecting directly to the synchronization server itself.
Synchronization only requires connectivity between the process server at the downstream site running the SyncUp job, and the synchronization server at the upstream site. Typically this is done over the Internet, since each site only needs access to the Internet rather than direct access to each other.
For increased security and privacy, a connection can be made directly between the downstream client and the upstream synchronization server using dial up modem lines or other direct connection methods. The only requirement is that the connection be able to handle TCP/IP and HTTP traffic.
76 Millennium 3 Installation
Synchronization
Synchronization uses the standard HTTP 1.1 protocol but uses URLs and request and reply content that is specific to synchronization. Previous versions of synchronization used proprietary headers for additional information; however, these are no longer in use, allowing synchronization requests to easily traverse proxy servers and firewalls.
Some downstream sites may implement restrictive proxy servers that filter access to certain web sites or hosts on the Internet. Since the upstream synchronization server is often reached through the Internet, any proxy servers at a downstream site will need to allow access to the synchronization server via HTTP.
Many proxy servers automatically forward traffic destined for port 80 and using the
HTTP protocol. For this reason, it is highly recommended that the upstream synchronization server be running on port 80.
Synchronization uses the standard Microsoft libraries at the downstream site when accessing the synchronization server. This means any configuration done at the downstream site to connect through proxy servers, and so on, will automatically be used by the downstream site when it attempts to contact the upstream synchronization server.
In addition, any firewalls in use at the downstream site must be configured to allow access from inside the downstream network to the synchronization server.
Files Exchanged During Synchronization
During synchronization the upstream and downstream sites exchange a series of files to verify a synchronization can occur and to transfer the data. The exchange of files is shown in the diagram below:
Figure 44: The exchange of files during synchronization
Release 3.29
The upstream site uses three jobs to implement a synchronization. Each job runs in response to a single request from the downstream site. The three jobs cannot be combined into a single job because the downstream site is not guaranteed to follow one request with another, and the HTTP protocol can disconnect between requests. The upstream site cannot grantee it will ever see a follow request from the downstream site, so it does not leave the SyncDown job running for an arbitrarily long time.
77
Chapter 10
The downstream site runs the entire synchronization process in a single SyncUp job.
The downstream site first requests a synchronization be started by sending a Start file upstream. The Start file contains relevant information about the downstream site. The upstream verifies the contents of the file and sends a Start confirmation back downstream in response. The Start confirmation may contain schema updates and other data. After the downstream site verifies the Start Confirmation file, both sites are ready to exchange data.
Each site then extracts the data changes that have not been seen by the other site and exchanges them using the Upload and Download files. A series of verifications are performed again before merging the changes from the remote site. After the verifications are complete, each site merges the actual data changes from the other site.
Once the merging of data is complete a confirmation is generated by each site and sent to the other site. The confirmation allows each site to know that the data it sent was successfully received by the other site.
If at any point the synchronization process is interrupted, both sites can just run a subsequent synchronization to pick up where they left off. Any lost data files or confirmations are automatically regenerated during the next synchronization.
Synchronizing with MPAY for Hosted Millennium
Licensees
After an upgrade of Millennium is complete, all service bureaus using Citrix must synchronize with MPAY to receive the latest tax updates. This section explains that procedure.
To synchronize with MPAY, perform the following steps:
1. Log into each of your databases.
2. In each instance of Millennium, select
System > Synchronization > Upstream site
tab.
3. Click the Synchronize Now button.
4. Select
System > Operations > Job Queue
tab.
5. Wait for the SyncUp and UpdateYTD jobs to complete successfully.
6. Select the
System > Operations > Processing Machines
tab.
7. Delete the process servers that are shown in the
System > Operations > Processing
Machines
tab.
8. After 2–3 minutes, click the refresh icon.
When your process servers reappear with an updated start time, you have completed the synchronization process.
78 Millennium 3 Installation
M3-Install-GD-SB-647-01
Part 4 — Appendices
The chapters contained in this part of the book concern useful and supportive information about the Millennium 3 system.
Release 3.29
•
•
•
4 Appendices
80
•
•
•
•
Installation Guide
Appendix A
Installing SQL Server 2005 Express
Edition SP4
This appendix describes the steps you must take to install and configure SQL Server
2005 Express Edition Service Pack 4 for use with Millennium 3. It is recommended that
you install the 2008 R2 Express Edition. For those instructions, see Chapter B
.
This appendix includes the following:
•
•
•
Note
Any links provided in this appendix were current as of the time of this writing.
Microsoft and other vendor sites change URLs without notice; therefore, be prepared to use an online search engine if a link fails.
Requirements & Download
Requirements for SQL Server 2005 Express
Make sure to visit Microsoft’s Web site and verify you have met all the requirements needed to install and run this application: http://www.microsoft.com/sqlserver/2005/en/us/system‐requirements.aspx
Download SQL Server 2005 Express
After the requirements have been met, download the SQL Server 2005 Express Edition
SP4 from Microsoft’s site: http://www.microsoft.com/download/en/details.aspx?id=184
Microsoft has two versions: one is for 32‐bit versions of Windows, and another is for
64‐bit versions of Windows. Make sure you download the correct version for your edition of Windows.
Release 3.29
81
Appendix A
This chapter was written with screen shots from the 32‐bit version of SQL 2005
Express. The install process for the 64‐bit version of SQL 2005 Express is the same.
When you download the files mentioned above, do not run the installation from the
Microsoft site. You should save the files first, then run/open the files for installation.
You may also want to install the graphical management tools as this will help with troubleshooting. Download and install SQL Server Management Studio Express SP4 from the Microsoft site.
Note
You should carefully consider your Millennium security rules before installing SQL
Server Management Studio Express at a client site. The graphical tool gives you the ability to directly query the database and all its tables using standard SQL queries. Server
Management Studio Express requires the computer to have MSXML 6.0 installed first.
Installation
To install SQL Server 2005 Express Edition, perform the following steps:
1. Locate the file you downloaded in the previous section (for example,
SQLEXPR32.EXE
).
2. Double‐click the downloaded file to launch the SQL Server installation.
The Windows operating system displays the following warning:
Figure 45: Open File - Security Warning dialog
82
It is safe to continue the installation.
3. Click the Run button.
Millennium 3 Installation
Installing SQL Server 2005 Express Edition SP4
The installation program displays the End User License Agreement page in the
Microsoft SQL Server 2005 Setup dialog:
Figure 46: End User License Agreement dialog
4. Read and accept the license agreement to continue.
5. Click the Next button.
The installation program displays the Installing Prerequisites page, as shown in
Figure 47: Installing Prerequisites page
Release 3.29
6. Click the Next button.
83
Appendix A
The installation program scans your system’s configuration, then displays the
Welcome page:
Figure 48: Welcome page
7. Click the Next button.
The installation program searches your system for potential problems, then displays the System Configuration Check page:
Figure 49: System Configuration Check page
84
8. Each line should have a status of Success. If not, you should read the message(s) and fix the problems before continuing. Once any problems are fixed, proceed to the next step.
Millennium 3 Installation
Installing SQL Server 2005 Express Edition SP4
9. Click the Next button.
The installation program displays the Registration Information page:
Figure 50: Registration Information page
10. Enter the appropriate information in the Name and Company text fields.
11. Ensure the Hide advanced configuration options check box is empty.
12. Click the Next button.
The installation program displays the Feature Selection page:
Figure 51: Feature Selection page
Release 3.29
13. Click on the X icon next to Connectivity Components.
85
Appendix A
14. Select the
Will be installed on the local hard drive
option to leave the defaults:
Figure 52: Feature Selection page
You should see the following in the dialog:
Figure 53: Feature Selection page
86
15. Click the Next button.
The installation program displays the Instance Name page:
Millennium 3 Installation
Installing SQL Server 2005 Express Edition SP4
Figure 54: Instance Name page
Release 3.29
This screen allows you change the name of the SQL Server instance. This can be helpful if you already have a previous version of SQL installed on the same machine.
The server name that appears when you run Millennium Server Setup to connect to the database ( Chapter 3, “Installing Millennium 3” ) depends on the option you select on this page. If you select the:
•
Default instance
option (the default value), the server name will appear as the
COMPUTER name
•
Named instance
option (as in Figure 54 above), the server name will appear as
COMPUTER\SQLEXPRESS (or COMPUTER\< whatever
you
type
in
the
text
box
>)
In this example, the instance is named SQLExpress2005.
You can normally use the default selection.
16. Click the Next button.
The installation program displays the Service Account page:
87
Appendix A
Figure 55: Service Account page
17. In most cases, you can leave the Service section setting as the default option of Use
the built-in System account, unless otherwise requested to do so.
The only other account type that should be used is a local or domain administrator account.
18. Ensure you put a check mark in the box under the Start services at the end of setup
section (as in Figure 55 above).
19. Click the Next button.
The installation program displays the Authentication Mode page:
Figure 56: Authentication Mode page
88 Millennium 3 Installation
Installing SQL Server 2005 Express Edition SP4
20. Select Mixed Mode in the top section.
21. Enter an sa (system administrator) password in the two text fields in the lower section.
WARNING
It is very important to remember this password. The password should have a mix of letters and numbers.
22. Click the Next button.
The installation program displays the Collation Settings page:
Figure 57: Collation Settings page
Release 3.29
23. Use the default settings (don’t change them).
24. Click the Next button.
The installation program displays the Configuration Options page:
89
Appendix A
Figure 58: Configuration Options page
25. Remove the check mark from the Enable User Instances check box.
26. Click the Next button.
The installation program displays the Error and Usage Report Settings page:
Figure 59: Error and Usage Report Settings page
90
27. Use the default settings (don’t change them).
28. Click the Next button.
The installation program displays the Ready to Install page:
Millennium 3 Installation
Installing SQL Server 2005 Express Edition SP4
Figure 60: Ready to Install page
29. Click the Install button.
The installation program displays the Setup Progress page.
Once the installation has completed, it displays the following:
Figure 61: Setup Progress page
Release 3.29
30. Click the Next button.
The installation program displays the Completing Microsoft SQL Server 2005 Setup page:
91
Appendix A
Figure 62: Completing Microsoft SQL Server 2005 Setup page
31. Click the Finish button.
Configuration
This section is especially important if you will have more than one computer accessing the Millennium database.
After the installation, perform the following steps:
1. In Windows, select
Start > All Programs > Microsoft SQL Server 2005 > Configuration
Tools > SQL Server Configuration Manager
.
The system displays the SQL Server Configuration Manager window.
2. In the left pane, expand
SQL Server 2005 Network Configuration
.
3. Highlight
Protocols for SQLEXPRESS
(or whatever you named the instance).
In this example, the instance is named SQLExpress2005, so the selection that is highlighted is
Protocols for SQLEXPRESS2005
.
4. Highlight and right‐click
TCP/IP
.
5. Select the
Enable
option (as shown in
Figure 63 ) to enable access via TCP/IP:
92 Millennium 3 Installation
Installing SQL Server 2005 Express Edition SP4
Figure 63: SQL Server Configuration Manager window
Once you have enabled TCP/IP, you must restart both SQL Server services.
6. In the left pane, expand
SQL Server 2005 Services
.
7. Highlight and right‐click
SQL Server Browser
.
8. Select the
Start
option (as shown in
) to start the service:
Figure 64: SQL Server Configuration Manager window
Release 3.29
9. Highlight and right‐click
SQL Server (SQLEXPRESS)
(or the named instance).
10. Select the
Restart
option to restart the service.
93
Appendix A
Once both services have restarted, your window should look like the example in
Figure 65: SQL Server Configuration Manager window
94
Note
The default Start Mode setting for SQL Server Browser is Manual. To change it, right‐ click on that line, select
Properties > Service
tab, then select Automatic from the Start
Mode drop‐down list.
11. You are finished with the SQL Express installation and can close the SQL Server
Configuration Manager.
12. Once all SQL Express components have been installed and configured, you should reboot the computer where you installed SQL Express, if possible.
Millennium 3 Installation
Appendix B
Installing SQL Server 2008 R2 Express
Edition SP1
This appendix describes the steps you must take to install and configure SQL Server
2008 R2 Express Edition Service Pack 1 for use with Millennium 3. This appendix includes the following subjects:
•
•
•
Note
Any links provided in this appendix were current as of the time of this writing.
Microsoft and other vendor sites change URLs without notice; therefore, be prepared to use an online search engine if a link fails.
Requirements & Download
Requirements for SQL Server 2008 Express
Visit Microsoft’s Web site and verify you have met all the requirements needed to install and run this application: http://www.microsoft.com/sqlserver/2008/en/us/system‐requirements.aspx
Download SQL Server 2008 Express
After the requirements have been met, download the SQL Server 2008 R2 Express
Edition SP1 from Microsoft’s site: http://www.microsoft.com/download/en/details.aspx?id=26729
Microsoft has two versions of SQL 2008 Express: one for 32‐bit versions of Windows, and another for 64‐bit versions of Windows. Be sure you download the correct version for your edition of Windows.
Release 3.29
95
This appendix was written with screen shots from the 32‐bit version of SQL 2008
Express. The installation process for the 64‐bit version of SQL 2008 Express is the same.
When you download the files mentioned above, do not run the installation from the
Microsoft site. You should save the files first, then run/open the files for installation.
Installation
To install SQL Server 2008 Express Edition, perform the following steps:
1. Locate the file you downloaded in the previous section (for example,
SQLEXPR32_x86_ENU.EXE
).
2. Double‐click the downloaded file to launch the SQL Server installation.
The Windows operating system displays the following warning:
Figure 66: Open File - Security Warning dialog
96
It is safe to continue the installation.
3. Click the Run button.
The installation program displays the SQL Server Installation Center dialog, beginning with the Planning page:
Millennium 3 Installation
Installing SQL Server 2008 R2 Express Edition SP1
Figure 67: SQL Server Installation Center, Planning page
4. Select the
Installation
option.
The installation program displays the Installation page:
Figure 68: SQL Server Installation Center, Installation page
Release 3.29
5. Select the
New SQL Server stand-alone installation
option.
97
The installation program checks your machine for possible problems, then displays the Setup Support Rules page in the SQL Server 2008 Setup dialog:
Figure 69: Setup Support Rules page
If the program detected failures or warnings, review the details or report. Ensure all problems are solved before running this installation program again.
6. If no issues are detected, click the OK button.
The installation program displays the Setup Support Files page:
Figure 70: Setup Support Files page
98
7. Click the Install button.
Millennium 3 Installation
Release 3.29
Installing SQL Server 2008 R2 Express Edition SP1
The installation program performs another check for potential problems, then displays the Setup Support Rules page:
Figure 71: Setup Support Rules page
If the program detected failures or warnings, review the details or report. Ensure all problems are solved before running this installation program again.
8. If you are ready to proceed, click the Next button.
The installation program displays the Installation Type page:
Figure 72: Setup Support Rules page
99
This page allows you to choose between installing a new instance of SQL Server
2008 or adding features to an existing one.
9. Select the appropriate radio button and click the Next button.
In this example, Perform a new installation of SQL Server 2008 is selected.
The installation program displays the Product Key page:
Figure 73: Product Key page
100
This page allows you to choose between installing a free edition of SQL Server
2008 or entering a product key.
10. Select the Specify a free edition button and select Express from the drop‐down list.
11. Click the Next button.
The installation program displays the License Terms page:
Millennium 3 Installation
Installing SQL Server 2008 R2 Express Edition SP1
Figure 74: License Terms page
12. Read and accept the license agreement to continue.
13. Click the Next button.
The installation program displays the Feature Selection page:
Figure 75: Feature Selection page
Release 3.29
14. Put a check in the Database Engine Services check box, as shown in
101
Figure 76: Feature Selection page
You do not need to check any additional boxes.
15. Click the Next button.
The installation program displays the Instance Configuration page:
Figure 77: Instance Configuration page
102
This screen allows you change the name of the SQL Server instance. This can be helpful if you already have a previous version of SQL installed on the same machine.
Millennium 3 Installation
Installing SQL Server 2008 R2 Express Edition SP1
The server name that appears when you run Millennium Server Setup to connect to the database ( Chapter 3, “Installing Millennium 3” ) depends on the option you select on this page. If you select the:
•
Default instance
option (the default value), the server name will appear as the
COMPUTER name
•
Named instance
option (as in Figure 77 above), the server name will appear as
COMPUTER\< whatever
you
type
in
the
text
box
>
In this example, the instance is named SQLExpress2008.
You can normally use the default selection.
16. Click the Next button.
The installation program displays the Disk Space Requirements page:
Figure 78: Disk Space Requirements page
Release 3.29
17. If you are satisfied with amount of free space and your selection of the installation location, click the Next button.
The installation program displays the Server Configuration page, beginning with the
Service Accounts
tab:
103
Figure 79: Server Configuration page, Service Accounts tab
104
18. In most cases for the SQL Server Database Engine, you can select the built‐in
System account by selecting NT AUTHORITY\SYSTEM under the Account Name column, unless otherwise requested to do so.
The only other account type that should be used is a local or domain administrator account.
19. For the SQL Server Browser service, select Automatic under the Startup Type column.
Note
The value of the Startup Type column for both services should be Automatic.
There is no need to click the
Collation
tab because you will use the default settings
(don’t change them).
20. Click the Next button.
The installation program displays the Database Engine Configuration page, beginning with the
Account Provisioning
tab:
Millennium 3 Installation
Installing SQL Server 2008 R2 Express Edition SP1
Figure 80: Database Engine Configuration page, Account Provisioning tab
Release 3.29
21. Select the Mixed Mode radio button.
22. Enter a password in the two text fields.
This will be automatically assigned to the sa (system administrator) account.
WARNING
It is very important to remember this password. The password should have a mix of letters and numbers.
23. Click the Add Current User button.
Add other Windows user accounts, as necessary.
24. Click the
User Instances
tab:
105
Figure 81: Database Engine Configuration page, User Instances tab
25. Remove the check mark from the Users are allowed to run a separate instance of
the Database Engine check box.
26. Click the Next button.
The installation program displays the Error and Usage Reporting page:
Figure 82: Error and Usage Reporting page
106
27. Use the default settings (don’t change them).
28. Click the Next button.
Millennium 3 Installation
Installing SQL Server 2008 R2 Express Edition SP1
The installation program checks your machine for potential issues that would block the installation, then displays the Installation Rules page:
Figure 83: Installation Rules page
If the program detected failures or warnings, review the details or report; then ensure all problems are solved before proceeding.
29. If no issues are detected, click the Next button.
The installation program displays the Ready to Install page:
Figure 84: Ready to Install page
Release 3.29
30. Click the Install button.
107
The installation program displays the Installation Progress page. Once the installation has completed, it displays the following:
Figure 85: Installation Progress page
31. Click the Next button.
The installation program displays the Complete page:
Figure 86: Complete page
108
32. Click the Close button.
Millennium 3 Installation
Installing SQL Server 2008 R2 Express Edition SP1
Configuration
This section is especially important if you will have more than one computer accessing the Millennium database.
After the installation, perform the following steps:
1. In Windows, select
Start > All Programs > Microsoft SQL Server 2008 > Configuration
Tools > SQL Server Configuration Manager
.
The system displays the SQL Server Configuration Manager window.
2. In the left pane, expand
SQL Server Network Configuration
.
3. Highlight
Protocols for SQLEXPRESS
(or whatever you named the instance).
In this example, the instance is named SQLExpress2008, so the selection that is highlighted is
Protocols for SQLEXPRESS2008
.
4. Highlight and right‐click
TCP/IP
.
5. Select the
Enable
option (as shown in
Figure 87 ) to enable access via TCP/IP:
Figure 87: SQL Server Configuration Manager window
Release 3.29
Once you have enabled TCP/IP, you must restart both SQL Server services.
6. In the left pane, expand
SQL Server Services
.
7. Highlight and right‐click
SQL Server Browser
.
8. Select the
Start
option (as shown in
) to start the service:
109
110
Figure 88: SQL Server Configuration Manager window
9. Highlight and right‐click
SQL Server (SQLEXPRESS)
(or the named instance).
10. Select the
Restart
option to restart the service.
Once both services have restarted, your window should look like the example in
Figure 89: SQL Server Configuration Manager window
Millennium 3 Installation
Installing SQL Server 2008 R2 Express Edition SP1
11. You are finished with the SQL Express installation and can close the SQL Server
Configuration Manager.
12. Once all SQLExpress components have been installed and configured, you should reboot the computer where you installed SQL Express, if possible.
Release 3.29
111
112 Millennium 3 Installation
Appendix C
Database Tables: Synchronized
Release 3.29
This appendix lists the Millennium 3 database tables that are included in synchronization exchanges between upstream and downstream machines.
The following tables are exchanged during synchronization:
Table 1: Tables sent downstream from MPAY to all other sites
Tables Sent Downstream from MPAY
SBankFileEntryType
SCalcCodes
SChildEnumFilter
SDepositMethods
SMiscTaxableBenefits
SNewHireInfo
SReciprocal
SSbUserDefAcct
SService
SServiceLevel
SSpec
SSuppCheck
STaxCodeDetails
STaxCodes
STaxDepositDates
STaxDepositFreq
STaxFormDef
STaxFormField
STaxForms
STaxTable
STaxTaskSched
STaxTaskSchedData
STaxTaskSchedForm
STaxW2Field
STransfer
STransferDates
STransferMethods
WStep
WTemplate
Table 2: Tables sent downstream from a service bureau to all other sites
Tables Sent Downstream from Service Bureaus
SBankAccount SRole a
SZipCodes
SBankAccountDetail b
SRoleRule CJEntries
SBanks SRoleRuleCondition CMiscCheckHist
SGenders
SHolidays
SInvoiceDetail
SInvoices
SMaritalStatus
SProducts
SRatePer
SSalesTaxCode
SSbInfo
SScripting
SStates
SUserRule
SUserRuleCondition
SUsers c
CTaxLiability
EAccrHist
ELaborDist
EPayHist
EPayHistDetail
EWorkComp a. System roles get sent downstream only.
b.
SBankAccountDetail
is sent downstream. Deletions are not sent upstream.
c. System users are sent downstream only (no deletions sent upstream). Company users are sent both ways between non-MPAY sites.
113
Appendix C
Table 3: Tables sent both upstream and downstream
C401kFund
C401kMatch
C401kSource
C401kStatus
CAccr
CAccrChart
CAgency
CAutoPost
CBankAccount
CBilling
CBillingCommission
CBillingDetail
CCalcCodes
CCalendar
CCalendarDetail
CCalendarDetailImport
CCalendarSchedule
CCalendarScheduleDetail
CCalendarScheduleMove
CCheckAttribute
CCheckAttributeDetail
CChildEnumFilter
CCodeGroup
CCodeGroupDetail
CDed
Tables Sent Both Upstream and Downstream
CDept1
CDept2
CDept3
CDept4
CDept5
CEarn
CEEOClass
CEmpFilter
CEmpStatus
CEmpType
CEthnicity
CEventCodes
CFreq
CGeoPref
CGLAccounts
CGLRules
CInfo
CInsPlan
CInsPlanRate
CInterviewType
CJob
CLogDisplay
CLookup
CPayGrades
CPayGroups
CPayrollGroup
CPosition
CRaiseReasons
CRateCodes
CRefTypes
CRept
CReptGroup
CReviewCodes
CScripting
CService
CShiftCodes
CSkillCodes
CSupervisors
CTax
CTermReasons
CTestCodes
CTransfer
CUnions
CWCCodes
CWCRates
E401k
EAccr
EAutoPay
ECheckAttribute
EDed
EDep
EDept
EDirDep
EEdu
EEmerg
EEvent
EFringe
EInfo
EIns
EInsCoveredDep
EPayEntry
EPayEntryDetail
EPrevEmpl
ERate
EReview
ESkill
ETax
LEmployeePayrollGroup
LScheduleBatchPayrollGroup
SUserRule
SUserRuleCondition
SUsers a a. System users are sent downstream only (no deletions sent upstream). Company users are sent both ways between non-MPAY sites.
For a list of tables that are not sent, please see
Appendix D, “Database Tables: Not
114 Millennium 3 Installation
Appendix D
Database Tables: Not Synchronized
This appendix lists the Millennium 3 database tables that are excluded from synchronization exchanges between upstream and downstream machines.
The following tables are not exchanged during synchronization:
Table 4: Company tables that are not sent upstream or downstream
Company Tables
CAchTransfers
CAchTransfersFile
CBatchTotals
CF1099M
CInsurance
CNotes
CUserPreferences
Table 5: Employee tables that are not sent upstream or downstream
Employee Tables
EPicture
EPayManual
EPayManualDetail
EPayPrecalc
EPayPrecalcDetail
EYtd
Release 3.29
115
Appendix D
Table 6: Report tables that are not sent upstream or downstream
Report Tables
RPhysicalReport
RPropertyrptVersions
RReport
RReportType
RRWField
RRWFilter
RRWReport
RRWSort
Table 7: System and TNode-related tables that are not sent upstream or downstream
System and TNode-related Tables
SAchFilter
SAchSetup
SAttachments
SBillingTable
SFilterType
SHTML
SJob
SJobClass
SBillingTableDetail
SCashReceipt
SJobDependent
SJobResults
SCompanySet SJobSchedule
SCompanySetDetail SJobSite
SCSRInfo
SDataQueue
SFilter
SPath
SPrinters
SRept
SReptGroup
SJobSiteCap SSbGLBB
SJobSiteCapMask SServerInfo
SMessage SStats
SSyncDbDetail
SSyncDbInfo
STaxCheckFilter
SUserPref
SRestore
SRetention
TAntiNode
TFolder
SSbClearCashImport TNode
SSbEntries TNodeType
TPage
TPageElement
TShortcut
For a list of tables that are sent, please see Appendix C, “Database Tables:
116 Millennium 3 Installation
Appendix E
For Dedicated & Local Process Server Users
Minimum Process Server User Rights
Release 3.29
This chapter describes the steps you must take to create a user with minimum rights on a dedicated or local process server. A very small percentage of installations require these instructions.
A dedicated process server should usually be a computer that does nothing other than process Millennium jobs. Usually, it should not be installed on a computer that someone uses as their regular workstation.
When you set up one or more dedicated process server, it is recommend that, on each dedicated process server, you ensure that the value of the Startup Type column for the
Millennium Process Server service is set to Automatic (see Figure 27 on page 39
) and
the login account has administrative privileges (see Figure 28 on page 40 ). For more
information, see Chapter 6, “Setting Up Dedicated Process Servers.”
Note
This does not mean that customers should use the network
Administrator
account. You should create a separate account for the Process Server service only.
The steps that follow explain how to create a reasonably “locked down” account. For this example, it is assumed you are working with a Windows Active Directory domain.
1. Create a user (for example,
ProcSrv
) and add this user to the “Domain Admins” group, which should also be the user’s primary group.
2. Go to the
Account
tab and set the Log On To option so that this account is only allowed to log on to the computers designated as a dedicated process server.
3. Select the option Password never expires and User cannot change password.
4. Go to the
Terminal Services Profile
tab and remove the check next to the Allow logon
to terminal server option.
5. Go to the
Dial-in
tab and select the Deny access radio button.
6. Make sure that the user ID created in step 1 is a member of the local
administrators group on the computer that will be running the Process Server
Service. This should be done by username—not by inheriting this access through the Domain Admins group.
This will ensure that the account created is only used for the Process Server(s).
117
Appendix E
The service account created in step 1 above will also need access to the following areas:
• Share points (shared folder objects and printer objects)
The login will require full share access to any folder and printer objects used by
Millennium.
• Files and folders
The login will require full file and folder access to the files and folders used in
Millennium. This can include:
• The default Millennium system directories (Archive, Reports, Temp, TaxForms,
ACH, Storeroom, and so on)
• A directory used for logos and signatures.
• A directory used for storing created Quickstart files
• If you will be doing any Millennium 2 (M2) to Millennium 3 (M3) conversions, the Process Server will also need to have M2 installed and have the same access to the M2 file directories as your M2 users.
Note
The versions of Crystal reports used on M2 and M3 are different. For this reason, any process server that is doing M2 conversions should not be allowed to process the
CRWPrint job class.
• Printers
• The login will require
access to the printers defined in Millennium. The
Creator
Owner
group should also have privileges to
,
Manage
Printers
, and
Manage
Documents
(this is the Windows default).
If the above settings still do not meet the security concerns, you may want to try making some additional changes to the account security as follows:
1. Change the service account from a member of Domain Admins to Domain Users.
2. Grant additional windows security policy privileges.
This is usually located within a Domain Security Policy under
Security Settings >
Local Policies
.
Note
These rights and privileges must be effective on each computer that will be acting as a process server.
3. The login will require the following User Rights Assignment: Log on as a service
4. Under Administrative tools, open Component Services, expand
Component Services
> Computers > My Computer > DCOM Config
.
118 Millennium 3 Installation
Minimum Process Server User Rights a. Right‐click Millprocdao; select
Properties
; then click on the
Security
tab.
b. Change Launch and Activation Permissions to Customize c. Click the Edit button and add the process server’s service account to the list of authorized users.
d. Give the process server’s account full permissions.
e. Click OK to save the change.
for Millprocrept.
Release 3.29
119
Appendix E
120 Millennium 3 Installation
Appendix F
For End-Users Who Are Note Local Administrators
Millennium 3 Registry Warning
This chapter describes the steps you must take to solve a Millennium 3 registry warning.
There may be times in which a user logs into Millennium 3 and receives a warning that the registry cannot be updated. You can resolve this issue one of two ways:
A.
Add the User as a Local Administrator
B.
Edit the Registry to Grant Full Control to Specific Registry Keys
Add the User as a Local Administrator
The easiest method is to add the user’s network account to the “Local Administrator” group on the computer that is running Millennium 3.
Note
Domain controllers do not have local groups. The only types of computers that have local groups are: member servers, stand‐alone servers, and workstations.
Edit the Registry to Grant Full Control to Specific
Registry Keys
The other method of resolving the registry warning involves editing the Windows registry.
Grant the Millennium 3 users “Full Control” of the following registry keys on the computer running Millennium:
Note
Members of the “Power Users” group may not inherently be granted sufficient rights to all eight registry keys. You will need to verify group permissions on all 8 registry keys.
The Permissions option is under the Edit menu. You may have to use REGEDT32 to set registry permissions in some versions of Windows.
Release 3.29
121
Appendix F
HKEY_CLASSES_ROOT\AppID\Millennium.EXE
HKEY_CLASSES_ROOT\AppID\{EDB460B8‐952F‐11D2‐BD06‐000000000000}
HKEY_CLASSES_ROOT\CLSID\{806269A8‐62E9‐11D2‐BCB0‐0000E82BB3D3}
†
HKEY_CLASSES_ROOT\CLSID\{9A8E5DFA‐5262‐11D3‐AA54‐00105ACE4928}
†
HKEY_CLASSES_ROOT\CLSID\{CD2425E4‐8141‐11D0‐8CE4‐444553540000}
†
HKEY_CLASSES_ROOT\Millennium.Document
HKEY_CLASSES_ROOT\Millennium.MillenniumContext
HKEY_CLASSES_ROOT\Millennium.MillenniumContext.1
†
The 64‐bit versions of windows have these keys duplicated in the following node:
\HKEY_CLASSES_ROOT\Wow6432Node\CLSID
. You must set permissions on these duplicated keys in addition to the ones listed above.
Additional Registry Keys to Allow End-Users to Save Preferences
Millennium 3 allows end users to control certain aspects of how Millennium 3 looks and acts. Settings for toolbars, icons, autosave, colors, and so on are contained in the
Millennium 3 > Tools > Preferences section. These settings are saved in the following registry area:
HKEY_CURRENT_USER\Software\MPI Software\Millennium Payroll
If you want your end users to be able to save their preferences, you must also grant them full access to this area of the registry.
122 Millennium 3 Installation
İndir
Herkese açık bağlantı güncellendi
Sohbetinize giden herkese açık bağlantı güncellendi. You may view and manage your chat links after registration here.
Belge herkese açık bağlantısı
Reklam
