Guide to Planning a Workforce Central Installation

®

A guide to the requirements and features of the installation process for Workforce Central products, including Workforce Timekeeper and Workforce HR/Payroll.

Kronos Workforce Central Suite Version 6

Document Part Number: 4704223-001 Document Revision: A

The information in this document is subject to change without notice and should not be construed as a commitment by Kronos Incorporated. Kronos Incorporated assumes no responsibility for any errors that may appear in this manual. This document or any part thereof may not be reproduced in any form without the written permission of Kronos Incorporated. All rights reserved. Copyright 2009. Altitude, Altitude Dream, Cambridge Clock, CardSaver, Datakeeper, Datakeeper Central, eForce, Gatekeeper, Gatekeeper Central, Imagekeeper, Jobkeeper Central, Keep.Trac, Kronos, Kronos Touch ID, the Kronos logo, My Genies, PeoplePlanner, PeoplePlanner & Design, Schedule Manager & Design, ShiftLogic, ShopTrac, ShopTrac Pro, StarComm, StarPort, StarSaver, StarTimer, TeleTime, Timekeeper, Timekeeper Central, TimeMaker, Unicru, Visionware, Workforce Accruals, Workforce Central, Workforce Decisions, Workforce Express, Workforce Genie, and Workforce TeleTime are registered trademarks of Kronos Incorporated or a related company. Altitude MPP, Altitude MPPXpress, Altitude Pairing, Altitude PBS, Comm.Mgr, CommLink, DKC/Datalink, eDiagnostics, Experts at Improving the Performance of People and Business, FasTrack, Hireport, HR and Payroll Answerforce, HyperFind, Kronos 4500 Touch ID, Kronos 4500, Kronos 4510, Kronos Acquisition, Kronos e-Central, Kronos KnowledgePass, Kronos TechKnowledgy, KronosWorks, KVC OnDemand, Labor Plus, Momentum Essentials, Momentum Online, Momentum, MPPXpress, Overall Labor Effectiveness, Schedule Assistant, Smart Scheduler, Smart View, Start Quality, Start WIP, Starter Series, StartLabor, Timekeeper Decisions, Timekeeper Web, VisionPlus, Winstar Elite, WIP Plus, Workforce Acquisition, Workforce Activities, Workforce Analytics, Workforce Attendance, Workforce Central Portal, Workforce Connect, Workforce Employee, Workforce Forecast Manager, Workforce HR, Workforce Leave, Workforce Manager, Workforce MobileTime, Workforce Operations Planner, Workforce Payroll, Workforce Record Manager, Workforce Recruiter, Workforce Scheduler, Workforce Smart Scheduler, Workforce Tax Filing, Workforce Timekeeper, Workforce View, and Workforce Worksheet are trademarks of Kronos Incorporated or a related company. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http:// www.openssl.org). This product includes software written by Eric Young (eay@cryptsoft.com). Mozilla.org is a registered trademark of the Mozilla Foundation. All other trademarks or registered trademarks used herein are the property of their respective owners and are used for identification purposes only. When using and applying the information generated by Kronos products, customers should ensure that they comply with the applicable requirements of federal and state law, such as the Fair Labor Standards Act. Nothing in this Guide shall be construed as an assurance or guaranty that Kronos products comply with any such laws. Published by Kronos Incorporated 297 Billerica Road, Chelmsford, Massachusetts 01824-4119 USA Phone: 978-250-9800, Fax: 978-367-5900 Kronos Incorporated Global Support: 1-800-394-HELP (1-800-394-4357)

For links to information about international subsidiaries of Kronos Incorporated, go to http://www.kronos.com Document Revision History Document Revision A Product Version Workforce Central 6.1 Release Date January 2009

Contents

About This Guide Organization of this guide ........................................................................... 10 Using the Workforce Central installation documentation ........................... 11 Chapter 1: About Workforce Central Suite products .............................................................................................. 16 Suite system requirements ........................................................................... 18 VMware support .......................................................................................... 19 Hardware and software requirements ................................................... 19 Workforce Central products supported ................................................. 20 Workforce Central architecture ................................................................... 21 Client software ...................................................................................... 21 Workforce Central platform and applications ....................................... 22 Platform components....................................................................... 22 Workforce Central applications....................................................... 22 Database ................................................................................................ 23 Interapplication communication ........................................................... 23 Database support ......................................................................................... 25 Disk allocation ...................................................................................... 25 RAID considerations ....................................................................... 26 Multiple instances of Workforce Central products ...................................... 28 Configuration Manager ......................................................................... 29 Using Configuration Manager .............................................................. 30 General functionality ........................................................................... 30 Reports ......................................................................................................... 33

............................................................................................................................................................................41 Workforce Central Portal system requirements ........55 Application server options .........................................................................46 Authentication ..............................................................48 Database Manager ..................................................................51 Oracle initialization parameters ..................................................................................................................43 Workforce Worksheet system requirements .........66 4 Kronos Incorporated .........................................................................................................................Contents Chapter 2: Workforce Timekeeper and other Labor and Scheduling products System requirements ...........................................57 Configuration options .........................................................................................................................................................................52 SQL Server considerations ..........................................................................56 Apache web server................................................40 Database system requirements ......................................................................44 Network requirements ...55 Web server options ..........55 Operating system options .........................................47 Database options ...........................62 Workforce Timekeeper deployment ......................................6 ........46 Citrix MetaFrame support .....59 Custom server environment option .................................................................................................................................................................65 Configuration phase ..........................................................................................................................................................................38 Application software system requirements .........58 Typical and custom environment options .........................................65 Installation phase .....51 Using multiple schemas ...................................................................................56 Microsoft IIS web server (Windows Only) ..................................................................................................................................................45 Active Directory ..48 Oracle considerations ...........................................................................................................54 Workforce Timekeeper installation requirements ..........................37 Client software requirements .......................61 Installing Workforce Central products ...................................................................46 Java 1....................................................................59 Typical server environment option ..........

......................................................................................................................................................................................................................... 73 Language support ................................................................................................ 76 Load balancing .............................. 90 System requirements ..................................... two instances .............................................................. 79 Sample configurations .......... 71 Custom security extension.............................. 95 Workforce HR/Payroll Solution Manager ................................................................................................................................... 91 Reporting ................................... 105 Guide to Planning a Workforce Central Installation 5 ................... 82 Separation....................................................................................................................................... 70 Prerequisites ........................... 70 Advanced reporting ................................................................................................................ 70 Basic reporting ............. 81 Workforce Timekeeper with no separation or multiple instances ................................................................................................ 99 Chapter 4: Combined Workforce Timekeeper and Workforce HR/Payroll installation Workforce Central platform in an integrated environment ...................................... 81 No separation................ 96 Multiple instances in a Workforce HR/Payroll environment ........................................................................... 72 Using advanced reporting............ 104 Integrating Workforce HR/Payroll and Workforce Timekeeper .......................... 87 Chapter 3: Workforce HR/Payroll Overview ....................... two instances ....................... 84 Separation... 72 Custom reports ............................................................. 78 Background Processor ............ 73 Using Business Objects ..................................................................................................... 102 Requirements for a combined environment ....................... 103 System requirements ....................................................................................................................................................................... no multiple instances ... 85 Dedicating machines to certain functions .................................................................................................................................................................................................. 75 Service packs ........Contents Reports ..............

.............................................................................................................................................................121 Licensing process .................................0 .................................................................................110 Skills and certifications ........................................................................................118 Upgrading from v6..................................................................Contents Data synchronization ............................................................................107 Terminology . profiles................................................................ keys......................120 Suite product licenses ....113 System Queue Assistant...........119 Types of licenses ..................112 Synchronization processor ..................................................................................................112 Queue assistants ...............................................................................108 Licenses.....127 Chapter 6: SSL security considerations Implementing SSL with Workforce Central .......137 Configuring Workforce Central to use an SSL terminator .......................135 SSL and Workforce HR/Payroll .108 Employee personal data ......................................................................................................................................................................................... and primary accounts .................................114 Synchronizing data .........................115 Chapter 5: Licensing Workforce Central products Required licenses ......120 Suite interaction licenses ..............107 Scope of data synchronization ............133 Certificates ....................................................................................................................131 SSL secured data paths ...................................................................................118 Upgrading from v5........................................................124 Licensing Workforce HR/Payroll ............ and credential stores ..................................................................................126 Suite license interaction ..136 SSL and Workforce Timekeeper .............................................. roles...............138 6 Kronos Incorporated ..............................................................................................................................................................................................................................................................................................................2 ......................................................122 Licensing Workforce Timekeeper ................................................................................130 General considerations ......................109 Jobs and organizations .................134 Credential stores and keys ................................................................................................114 Employee Queue Assistant ...............................132 Certificates.................................................

.......................................... 148 Index Guide to Planning a Workforce Central Installation 7 ......................... 142 Workforce HR/Payroll ................. 146 Workforce Timekeeper installation worksheet .................................................................Contents Chapter 7: Preinstallation requirements and checklists Preinstallation requirements ......................................................... 145 Workforce HR/Payroll preinstallation worksheet ......................................................................................... 143 Preinstallation worksheets .............................. 142 Workforce Timekeeper .............................

Contents 8 Kronos Incorporated .

1 environment is important to a successful installation. It consists of a number of separate. developing. tracking. When you install your first Workforce Central base product (Workforce Timekeeper or Workforce HR/Payroll). the installation program delivers this common platform. .1 products. yet tightly integrated applications that are both extensible and unified to provide a centralized data repository and flexible self-service capabilities. and rewarding.1 supports different operating environments. application servers. Most Workforce Central products use a common software architecture platform. Planning your Workforce Central v6. and web servers. all configured in a number of different ways. Workforce Central v6.About This Guide The Kronos® Workforce Central® suite is a comprehensive solution for managing every phase of the employee relationship—staffing. deploying. This document describes the system requirements and background information that you need to know before you install any Workforce Central v6.

” on page 129 Chapter 7. “Preinstallation requirements and checklists.” on page 89 Chapter 4. “SSL security considerations.” on page 101 Chapter 5. “About Workforce Central.” on page 35 Chapter 3. “Combined Workforce Timekeeper and Workforce HR/Payroll installation.” on page 141 10 Kronos Incorporated .” on page 15 Chapter 2. “Workforce Timekeeper and other Labor and Scheduling products.” on page 117 Chapter 6. “Workforce HR/Payroll.About This Guide Organization of this guide This book consists of the following chapters: • • • • • • • Chapter 1. “Licensing Workforce Central products.

and Interface Designer. Installing Workforce Timekeeper describes how to install Workforce Timekeeper on a Windows machine that does not include Workforce HR/ Payroll or an earlier version of Workforce Timekeeper. You can download the instructions for installing or upgrading Workforce Timekeeper.1 on a machine that has Workforce HR/Payroll v5.1 and Workforce Payroll v6. Workforce HR/Payroll.Using the Workforce Central installation documentation Using the Workforce Central installation documentation You should review the content of this document before you install any Workforce Central products. select the applicable installation or upgrade scenario from the following books: Caution: Each scenario consists of step-by-step instructions.2 or v6. Although it may be possible to install the desired products in an order that is different from the documentation. Workforce Operations Planner. Workforce Forecast Manager. Workforce HR/Payroll. Workforce Activities. This is especially important in integrated environments that contain Workforce Timekeeper and Workforce HR/Payroll. or both. This book includes instructions for installing Workforce Scheduler.1 on a machine that does not include Workforce Timekeeper or an earlier version of Workforce HR/Payroll. • 11 . Workforce Attendance. • Upgrading Workforce HR/Payroll describes how to upgrade to Workforce HR/Payroll v6. Depending on the product or combination of products you are installing.0 installed. paying particular attention to the chapters about the base products that you are installing or upgrading—Workforce Timekeeper. • Installing Workforce HR/Payroll describes how to install Workforce HR v6. Workforce Leave. Workforce Integration Manager. the order presented in the scenarios has been tested. where the platform and single database may need to be built in a specific order. Process Designer. Workforce Device Manager. and other Workforce Central products from the Kronos web site.

0 to Workforce Timekeeper v6. and Interface Designer. Process Designer. connecting to the same database. connecting to the same database.2 or v6. It also includes instructions for upgrading: – – Data Collection Manager to Workforce Device Manager Workforce Connect to Workforce Integration Manager • Installing Workforce HR/Payroll and Workforce Timekeeper describes how to install Workforce HR/Payroll v6. Workforce Attendance. Workforce Operations Planner. This book includes instructions for upgrading or installing Workforce Scheduler. Workforce Activities. Workforce Forecast Manager. and then to install Workforce HR/Payroll v6.1 on the same machine. Workforce Leave. Workforce Forecast Manager. It also includes instructions for upgrading: – – Data Collection Manager to Workforce Device Manager Workforce Connect to Workforce Integration Manager • Upgrading Workforce HR/Payroll and Installing Workforce Timekeeper describes how to upgrade Workforce HR/Payroll v5.0 to Workforce HR/Payroll v6.1 on the same machine.0 to Workforce Timekeeper v6.1 and Workforce Timekeeper v6. Process Designer. connecting to the same database. Workforce Operations Planner. Workforce Operations Planner. This book includes instructions for upgrading or installing Workforce Scheduler.2 or v6. Workforce Forecast Manager. Workforce Activities. Workforce Forecast Manager. Workforce Attendance. and Interface Designer.2 or v6. and Interface Designer. • Upgrading Workforce Timekeeper and Installing Workforce HR/Payroll describes how to upgrade Workforce Timekeeper v5.1 on a Windows machine that does not include Workforce HR/Payroll. This book includes instructions for installing Workforce Scheduler. Workforce Activities. Workforce 12 Kronos Incorporated .1 on the same machine.1 and to install Workforce Timekeeper v6. This book includes instructions for installing Workforce Scheduler.About This Guide • Upgrading Workforce Timekeeper describes how to upgrade Workforce Timekeeper v5. Workforce Leave. Workforce Attendance. Workforce Operations Planner. Workforce Leave. Workforce Device Manager.1. Process Designer. Workforce Integration Manager.

• Upgrading Workforce HR/Payroll and Workforce Timekeeper describes how to upgrade from an integrated v5.0 installation of Workforce HR/ Payroll and Workforce Timekeeper to v6. Workforce Forecast Manager. Workforce Operations Planner.2 or v6. Process Designer. Workforce Leave. and Workforce Integration Manager. Workforce Integration Manager. Process Designer. Workforce Attendance. Workforce Operations Planner. and Interface Designer. Installing the Workforce Worksheet Installation Guide describes how to install the Workforce Worksheet plug-in to generate Workforce Timekeeper advanced reports and Workforce Genies with Microsoft Excel 2007. • Workforce Central Portal Installation Guide describes how to install and upgrade the Workforce Central Portal product for use with Microsoft SharePoint 2007. and Interface Designer. Workforce Forecast Manager. Workforce Activities. Workforce Device Manager. This book also includes instructions for upgrading or installing Workforce Scheduler. Workforce Record Manager Installation Guide describes how to install and upgrade Workforce Record Manager. Workforce Attendance. • • 13 . Workforce Attendance. It also includes instructions for upgrading: – – • Data Collection Manager to Workforce Device Manager Workforce Connect to Workforce Integration Manager Installing and Upgrading Workforce Timekeeper on UNIX describes how to install or upgrade Workforce Timekeeper on a Solaris or AIX machine. Workforce Activities. Workforce Leave. Workforce Activities. Workforce Device Manager.1.Using the Workforce Central installation documentation Leave. This book includes instructions for upgrading or installing Workforce Scheduler.

About This Guide 14 Kronos Incorporated .

Chapter 1 About Workforce Central This chapter provides an overview of Workforce Central and contains the following sections: • • • • • • • “Suite products” on page 16 “Suite system requirements” on page 18 “VMware support” on page 19 “Workforce Central architecture” on page 21 “Database support” on page 25 “Multiple instances of Workforce Central products” on page 28 “Reports” on page 33 Note: Because Workforce Timekeeper is a prerequisite for a number of Workforce Central product that can all be installed at the same time. Workforce Forecast Manager. Workforce Integration Manager. Workforce Leave. references to Workforce Timekeeper in this chapter also include Workforce Scheduler. Workforce Attendance. Workforce Operations Planner. Workforce Activities. Workforce Device Manager. .

track accruals. and provide for web-based configuration and communication that is integrated into Workforce Central and interfaces with multiple other applications. an industry-standard web browser is used to record employee time. using the latest technology.Chapter 1 About Workforce Central Suite products The Workforce Central suite contains a number products that can be organized into the following categories. Workforce Central utilities — Several utilities provide functionality that is common across the Workforce Central products. • Time and labor products — With Workforce Timekeeper and the optional Workforce Accruals. create schedules. Kronos 4500 Touch ID. Scheduling products — Although Workforce Timekeeper provides basic scheduling tools for employees who work predictable schedules. approve time. Workforce Forecast Manager. Workforce Device Manager. and Workforce TeleTime. generate reports. Workforce Record Manager provides the robust functionality needed to create an optimum archiving process. Data collection and self-service products — These scalable data collection solutions focus on flexible self-service for the hourly worker. Workforce Manager. Workforce Attendance. and Workforce Operations Planner products provide tools for more complex scheduling where requirements vary depending on business demand. And Workforce Integration Manager and Interface Designer provide an easy-to-use. the optional Workforce Scheduler. and much more. Products include Workforce Employee. flexible data integration tools that efficiently interfaces Kronos products with other critical business applications. Workforce HR and Workforce Payroll — These products deliver a complete infrastructure to help organizations optimize their workforce and enable communication and collaboration across the enterprise by streamlining the management of the employment life cycle by web-based self-service and reducing overhead by delivering content through a central portal. and Workforce Activities products. Workforce Leave. • • • • 16 Kronos Incorporated .

Guide to Planning a Workforce Central Installation 17 . It extracts data from the Workforce Central database and transforms the data into a target data warehouse model that is designed for optimal reporting and analytics.Suite products • Business intelligence and analysis products — Workforce Analytics is the foundation product of all analytics products from Kronos. and Workforce Analytics for Healthcare. Additional analytics products. Contact your Kronos Representative for more information about these Workforce Central products. such as Workforce Analytics for Retail. Workforce Analytics for Manufacturing. build on the features and functionality delivered with the core Workforce Analytics product.

1 applications require the following infrastructure: • • Operating system — All Workforce Central applications run on Windows. you must use a Windows system with a JBoss application server.Chapter 1 About Workforce Central Suite system requirements Workforce Central v6. • Note: If you use both Workforce Timekeeper and Workforce HR/Payroll. Database — All Workforce Central applications support a SQL Server database. 18 Kronos Incorporated . and SQL Server database. Microsoft IIS web server. Application server — Workforce Central requires a J2EE-compatible application server. • Web server — All Workforce Central applications use Microsoft IIS web server software. most of the products based on Workforce Timekeeper can also run on UNIX. The products that are based on Workforce Timekeeper can also use Apache (which may be installed by the Workforce Timekeeper installation program). See your Kronos Representative for more information. you can have the Workforce Timekeeper installation program install JBoss or you can use a preinstalled version of JBoss. Depending on your requirements. the products that are based on Workforce Timekeeper also support an Oracle database. Note: Workforce Timekeeper can also be installed and configured for other types of application servers.

Important: Do not “over commit” the server resources. By using virtualization software. taking default settings for system parameters and tuning options. Although VMware has a multitude of options for tuning workloads.1 applications can be run on VMware virtual machines. increasing the utilization and flexibility of hardware. Performance testing of Workforce Central in a VMware environment obtained optimal results when running VMware with an “out of the box” configuration. hard disk. Hardware and software requirements Performance testing of Workforce Central in a VMware environment used the following hardware and software.4 GHz Guide to Planning a Workforce Central Installation 19 . Kronos recommends that you keep the VMware configuration as simple as possible. Consult your Kronos Representative for the requirements specific to your environment. Hardware The following hardware represents the minimum requirement for running Workforce Central on VMware: • • • Dual-core systems based on Intel 5130 processor running at 2 GHz or greater Quad-core systems based on Intel 5335 processor running at 2 GHz or greater Dual-core systems based on AMD 2200 series processor running at 2. an IT department can transform or “virtualize” the hardware resources of an x86-based computer—including the CPU. RAM. be sure to reserve the CPU and memory resources required by Workforce Central so it cannot be allocated to other virtual machines or applications. and network controller—to create several fully functional virtual machines that can each run its own operating system and applications just like a “real” computer.VMware support VMware support Most Workforce Central v6. Virtualization is a software technology that makes it possible to run multiple operating systems and multiple applications on the same computer at the same time.

• • • • • • • • • • • • • • • Workforce Timekeeper Workforce Activities Workforce Attendance Workforce Accruals Workforce Leave Workforce Scheduler Workforce Forecast Manager Workforce Operations Planner Workforce Record Manager Workforce Integration Manager Workforce Device Manager Workforce Central Portal Reporting and Advanced Reporting (SSRS) Workforce Central database Workforce HR/Payroll Note: Workforce Analytics products are not supported on VMware.5 or 3i Workforce Central products supported The following products are supported on VMware ESX Server Version 3. 20 Kronos Incorporated .Chapter 1 About Workforce Central • • All AMD quad-core processor systems 4 GB memory per processor core (depending on the number and size of the virtual machines) Software • ESX Server 3.5 or later.

Workforce Central architecture Workforce Central architecture The Workforce Central suite is a Java 2 Enterprise Edition (J2EE) compatible set of applications that uses a three-tier structure: 1. Client software The client layer contains browsers. a Java Runtime Environment (JRE). Workforce Central platform and applications — Contains the common infrastructure. operating systems. 3. Guide to Planning a Workforce Central Installation 21 . The pages and applets connect to the webbased Workforce Central application. which means that applets are only downloaded the first time that the client accesses the applet. application server. Workforce Worksheet — An Excel 2007 plug-in that enables users to dynamically retrieve a number of Workforce Central reports and Genies using Microsoft Excel.jar files and use a sticky cache. The applets are downloaded via . Database — Stores all of the application data. applications. Any Excel worksheet created from this data can be refreshed on demand or dynamically with live data from Workforce Central. Interface Designer — The tool used to create custom interfaces for Workforce Integration Manager on a client machine. and other supporting technologies (such as Adobe Acrobat Reader). Application functions are implemented as Hypertext Markup Language (HTML) pages or Java applets. and web server. Several Workforce Central products operate at the client level: • • • Process Designer — The visual process design tool used to modify preconfigured process templates that are included with Process Manager. Client software — The client accesses a Workforce Central application through a Web Uniform Resource Locator (URL) using a browser. 2.

but not universally used. Workforce Scheduler.1 provides the business logic and connections to the back-end database. such as database connectivity. business logic. GUIs. etc. Workforce HR/Payroll. yet tightly integrated. • Workforce Central applications The application layer (not part of the common platform itself). In order to make the Workforce Central products independent. and JSPs Kernel layer — Basic domain-independent components (logging. from lowest to highest: • • • J2EE layer — The Java runtime and J2EE application container services. installed as needed. API. Process Manager. and so forth) and business objects essential to the Kronos brand (HyperFind. session management. this tier of the suite architecture consists of three parts: • • • A base platform.) and the UI. Genies. code.) Shared business layer — Business objects shared by two or more applications. which consists of data. 22 Kronos Incorporated . Organizations.Chapter 1 About Workforce Central Workforce Central platform and applications The middle tier of Workforce Central v6. etc. and APIs A modular set of applications and components. and so forth) that are installed and licensed separately and use the platform functionality in the layers below. servlets. consists of major functional areas (Workforce Timekeeper. It consists of the following set of layers. and extensibility frameworks Core business layer — Business objects essential to all Kronos ERM applications (People. that use various extensibility mechanisms “Loosely coupled” integration technologies that connect these pieces with each other and with third-party applications Platform components A set of common components is installed automatically when you install the first base Workforce Central product (Workforce Timekeeper or Workforce HR/ Payroll). persistence.

• • Interapplication communication A complete installation of the Workforce Central suite includes many separate components that need to communicate with each other. the Workforce Central database—which must be SQL Server—contains the Workforce HR/Payroll tables. Database Workforce HR/Payroll and Workforce Timekeeper can use a single Workforce Central database. Process Manager RMI is managed completely by the Process Manager • Guide to Planning a Workforce Central Installation 23 . and also all the Workforce Timekeeper and platform tables (although the Workforce Timekeeper tables are not used). Java RMI — The Process Manager engine is the only component to use RMI. Because Workforce HR/ Payroll only supports SQL Server. When only Workforce HR/Payroll is installed. The Workforce HR/Payroll tables and application are not present. this database—which can be SQL Server or Oracle—contains the Workforce Timekeeper and platform tables. An application server component that contains all dynamic content and centralizes application services such as business components and access to back-end enterprise systems and uses technologies such as caching and connection pooling to improve resource use and application performance. • When only Workforce Timekeeper is installed. the schemas exist side-by-side in the database.Workforce Central architecture The application layer of a Workforce Central installation includes: • • A web server component that contains all static content and listens for browser requests and passes these requests to the application server. When both Workforce HR/Payroll and Workforce Timekeeper are installed. Each application is configured when it is installed with the location of its database. Depending on the component. Oracle is not supported for combined installations. the following types of communication are used: • Database access (by JDBC) — Database access is the most straightforward way for components to communicate.

If cookies are disabled. Workforce Timekeeper cookies are not encrypted in any way. The platform identifies the Workforce HR/Payroll server by using the same properties used by common logon. each application needs to identify the other to log on and maintain sessions between the two web servers. ensure that cookies are enabled in your browser. you can log on to Workforce Timekeeper. which locates other servers in its cluster from database tables in the Process Manager schema. • • 24 Kronos Incorporated . There is currently no other encryption of logon information. or other data. the cookie is gone.Chapter 1 About Workforce Central engine. Properties files (configured when Workforce HR/Payroll is installed) store the locations and protocols for the two servers. the caller needs to identify the location of the target (web server or application server). Workforce Timekeeper relies on cookies for session management. Cookies — A cookie is a small piece of information. For the common logon handshaking. often no more than a short session identifier. The cookies are strictly session cookies and are not persistent. that the server sends to the browser when the browser connects for the first time. but the default Genie will not load and the following error message will be generated: Cannot retrieve data from server. outside of an Secure Socket Layer (SSL) installation. To avoid this problem. After the user logs off.NET business objects. A cookie is simply loaded into the browser’s cache and is active only as long as the session is active. It uses cookies to track the user session ID and a Boolean logoff flag. cookies. If it is necessary to have any HTTP request or response information encrypted during transmission. • • XML APIs (using the HTTP protocol) — For XML APIs. which means that they are not stored on the user’s system. Common logon handshaking — Workforce HR/Payroll uses common logon handshaking to communicate with the platform using HTTP. Workforce HR/Payroll private web service — The Workforce HR/Payroll private web service is called by the platform when processing XML API requests implemented by Workforce HR/Payroll . you should implement SSL with the Workforce Timekeeper installation.

1. • • RAID storage — Your specific RAID implementation will determine how to allocate the required tablespaces. Unicode is an industry standard that was designed to allow text and symbols from all the writing systems of the world to be consistently represented and manipulated by computers. The following table lists the Kronos database documentation data type labels: Unicode Data Types SQL • • • • • • nChar nVarChar nText nChar nVarChar2 NCLOB • • Char VarChar2 • • Char VarChar Non-Unicode Data Types Oracle Disk allocation With Workforce Timekeeper v6.1 uses Unicode-compliant SQL Server and Oracle Relational Database Management Systems (RDBMS).Database support Database support Workforce Central v6. The Unicode Standard includes character properties that enable Kronos databases to convert existing non-Unicode text characters to multibyte characters that are used in any major language text. Non-RAID disk allocation — If you are not using RAID. Assign file groups tkcs1–tkcs9 to each disk. Guide to Planning a Workforce Central Installation 25 . The database installation and upgrade procedures are not affected by the use of the Unicode multibyte characters. you can specify the file groups that are needed for the installation or you can use RAID (Redundant Array of Independent Disks). Kronos recommends that you use at least nine disks when installing a Workforce Timekeeper database.

The following lists some sample RAID configurations for varying sized installations. (With SAN.000 employees) – A hardware RAID controller with at least three drives for the database storage. Although many RAID implementations are available. SAN storage also may be used for database disk storage. (Disk I/O performance improves as the number of disks increases.000–20. See your Kronos Representative for recommendations specific to your environment. One or more hardware RAID controllers with five or more disk drives for database storage. RAID considerations RAID (Redundant Array of Independent Disks) technology combines two or more physical hard disks into a single logical unit. disk I/O performance improves as the number of disks increases. (Disk I/O performance improves as the number of disks increases.) A logical drive created as a RAID partition with the available drives should be used for all the tablespaces in Oracle and file groups in SQL Server.) Log files should be located on logical units (LUNs) that are separate from the data LUNs. – • Medium installations (5.Chapter 1 About Workforce Central Refer to Installing Workforce Timekeeper for more information. Kronos recommends using hardware level RAID storage or SAN disk storage with production quality drives.) A logical drive created as a RAID partition with the available drives should be used for all the tablespaces in Oracle and file groups in SQL Server. • Small installation (fewer than 5.000 employees) – – – – 26 Kronos Incorporated .

000 employees) – One or more hardware RAID controllers with seven or more disk drives for database storage. (Disk I/O performance improves as the number of disks increases. Log files should be located on logical units (LUNs) that are separate from the data LUNs.) Log files should be located on drives that are separate from the data.) A logical drive created as a RAID partition with the available drives should be used for all the tablespaces in Oracle and file groups in SQL Server. disk I/O performance improves as the number of disks increases. (With SAN. SAN storage also may be used for database disk storage.Database support • Large installations (more than 20. – – – – Guide to Planning a Workforce Central Installation 27 .

Kronos provides hardware recommendations that are specific to your environment to accommodate the anticipated load on the system. Refer to your Hardware Recommendation Report or contact your Kronos Representative for guidelines specific to your environment. you cannot install a service pack only on one instance. If you have multiple instances of Workforce Central products that connect to different databases. do not need to include the same set of Workforce Central products as other machines in your environment. These instances can be installed on different physical machines or the same physical machine. you cannot install Workforce Timekeeper and Workforce HR/Payroll on one instance and Workforce Timekeeper and Workforce Scheduler on another instance if all instances use the same database. Likewise. This is true whether they are installed on separate machines or on the same machine. For example.Chapter 1 About Workforce Central Multiple instances of Workforce Central products Depending on the Kronos products that you purchased as well as a number of other factors. Multiple instances of Workforce Central products that connect to the same database must include the same Workforce Central products and service packs. Note: Dedicated Background Processor machines that are created by the Workforce Timekeeper installation program. 28 Kronos Incorporated . however. each instance can include different products and service packs. These recommendations may include installing more than one instance of your Workforce Central products. it must be installed on the Background Processor machine as well as all other machines in the Workforce Central environment. The only exception to this is that if you use Workforce Activities.

• • In an integrated Workforce HR/Payroll-Workforce Timekeeper environment. modify an instance. reports. modify.1. is used to create. but each instance is connected to a separate database. Each instance must run with the same version of third-party software. You can name new instances anything (maximum 50 characters). Configuration Manager is used to support: • Multiple databases — You can install several instances of Workforce Central products running on the same physical server. Multiple versions — You can run different service packs on different instances provided they point to different databases (Report constraint). or delete an instance (including the wfc instance). Multiple languages — You can install multiple instances of Workforce Timekeeper on the same physical server with each instance supporting a different language. Workforce HR/Payroll does not support multiple languages. and production. which is delivered when you install Workforce Timekeeper or Workforce HR/Payroll v6. you use this configuration when separate instances and databases are required for training. Guide to Planning a Workforce Central Installation 29 . All instances can point to the same database. Configuration Manager is typically used to support multiple databases. and remove multiple instances of Workforce Central products running on the same physical server: • • • Each instance is independent and does not share code or temporary files. The Workforce Timekeeper or Workforce HR/Payroll installation program creates the first instance of Workforce Central. You cannot rename this instance. By default. localized strings. Refer to “Language support” on page 75 for more information about non-English languages. testing.Multiple instances of Workforce Central products Configuration Manager Configuration Manager. log files. After the wfc instance is created. you can use Configuration Manager to create a new instance. Typically. this instance is named wfc. and so forth. Each instance has its own runtime directory area for storing objects such as custom properties files. Typically.

remove products that are prerequisites for other products nor can you add products that require products that are not installed. Workforce Leave. however. Workforce Attendance. Configuration Manager lists the products that are installed in the wfc instance. and Workforce Activities. Each instance must have its own complete copy of all static resources. HTML pages. you cannot remove Workforce Timekeeper from the following instance because it is a prerequisite for Workforce Scheduler. you can add or remove products from this list. In either case. You cannot. JavaScript files. and so forth. General functionality Guidelines to consider before installing multiple instances of Workforce Central include the following: • Instances do not share static application resources.jar files. When you modify an instance.Chapter 1 About Workforce Central Using Configuration Manager When you create an instance. Configuration Manager lists the products that are installed on the instance that you plan to modify. JRE plug-in. You cannot select these until all prerequisites are cleared. For example. 30 Kronos Incorporated . client . Static resources are served by the web server and include Help files. images. Gray text indicates that these are prerequisites to other products listed.

• • • • Guide to Planning a Workforce Central Installation 31 . you must also create a second instance on the web server. That means that user A can log on to instance 1 at the same time that user B logs on to instance 2. however. the user enters the default logon in the browser: http://server/wfc/logon To log on to a French version. The only restriction is that all languages must use the same code page when the instances are running concurrently. Users connect to each Workforce Central instance by a unique URL. If you want to install different products on different instances. Each instance of Workforce Timekeeper can support a different language. Kronos does not. All instances connected to the same database must have the same product set installed. the user enters the name that was applied when the second instance was created. • Each instance can be configured separately and independently by established configuration mechanisms such as System Settings and custom properties files. each instance must connect to a separate database. support multiple browsers that are open on the same physical machine. you cannot install one instance of Workforce Central to c:/ kronos/wfc and another to d:/kronos/wfc. For example. Multiple instances can run concurrently. to log on to an English version of Workforce Timekeeper. for example: http://server/french/logon • You cannot install multiple instances to different locations in the file system. For example. All instances must be installed under the initial Kronos installation directory—c:/kronos.Multiple instances of Workforce Central products This means that if the web server is on a machine that is separate from the application server and you create a second instance on the application server. because only one code page can be used by an application server at the same time.

Database functionality The following guidelines describe database functionality with the multiple instance capability: • Different instances can point to different databases that use the same database platform. For example. and instance 2 to an Oracle database. • • 32 Kronos Incorporated . If you create a new instance that points to a different database. instance 1 may point at SQL Server database “fred” and instance 2 at SQL Server database “mildred. For example. Each employee that uses the Workforce Central system must have a valid employee license for each product that the employee uses. instance 1 cannot point to a SQL Server database. License files are stored in the Kronos\instance_name\licensing folder.” Different instances can point to databases that use the same database platform. Important: Licenses are assigned per employee.Chapter 1 About Workforce Central Licensing multiple instances Each instance of Workforce Central requires separate license files and all instances that connect to the same database must include the same set of license files. instance 1 can point at SQL Server database “fred” on server 1 and instance 2 at database “fred” on server 2. For example. for example Kronos\wfc\licensing. The database servers must be at the same version. but are installed on different database servers. Different instances cannot point to different database platforms. you must obtain a new license from Kronos.

Workforce Timekeeper no longer supports Crystal reports. For more information about the Workforce Timekeeper reporting functionality. Workforce HR/Payroll uses Crystal reports as its reporting mechanism and does not use RDL or SSRS functionality.1 is based on the report definition language (RDL). Guide to Planning a Workforce Central Installation 33 .Reports Reports The reporting functionality of Workforce Timekeeper v6. refer to “Reports” on page 70. which is an XML schema from Microsoft for representing reports.

Chapter 1 About Workforce Central 34 Kronos Incorporated .

Therefore. operating systems. Workforce Activities. Workforce Timekeeper can be installed with a variety of configurations. and underlying software. Workforce Forecast Manager. Workforce Attendance. The following sections of this document describe the various installation options and requirements: • • • • • • • • • • “System requirements” on page 37 “Database options” on page 48 “Workforce Timekeeper installation requirements” on page 55 “Configuration options” on page 58 “Typical and custom environment options” on page 59 “Workforce Timekeeper deployment” on page 65 “Reports” on page 70 “Language support” on page 75 “Service packs” on page 76 “Load balancing” on page 78 . Workforce Integration Manager. Workforce Device Manager. it is important that you plan your environment before you start installing any products.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products Note: Because Workforce Timekeeper is a prerequisite for a number of Workforce Central product that can all be installed at the same time. Workforce Leave. Workforce Operations Planner. references to Workforce Timekeeper in this chapter also include Workforce Scheduler.

Chapter 2 Workforce Timekeeper and other Labor and Scheduling products • • • “Background Processor” on page 79 “Sample configurations” on page 81 “Dedicating machines to certain functions” on page 87 36 Kronos Incorporated .

and network requirements for Workforce Timekeeper and other Workforce Central products. all installed on one machine.1. 37 . which included thirdparty application server software and web server software. Although Workforce Timekeeper v6. Therefore. database. in Workforce Timekeeper v6. application.System requirements System requirements This section describes the client.6” on page 47 Note: Earlier versions of Workforce Timekeeper used the term application server to describe the entire Workforce Timekeeper application. it also allows you to install the application server and web server software on separate machines as well as to install multiple instances of the application on the same machine.1 continues to support this configuration. the term application server is only used in reference to the J2EE application server software—not the Workforce Timekeeper application. • • • • • • • • • “Client software requirements” on page 38 “Application software system requirements” on page 40 “Database system requirements” on page 41 “Workforce Central Portal system requirements” on page 43 “Network requirements” on page 45 “Active Directory” on page 46 “Authentication” on page 46 “Citrix MetaFrame support” on page 46 “Java 1.

Datacenter. Datacenter. Client software requirements Item Operating system Requirement Microsoft Windows Server 2003 (32-bit). service pack 1 — Standard.0_07 — ships with Workforce Timekeeper Recommended: 1. For less demanding system requirements.6. Enterprise. All Time & Attendance and Scheduling products have a Java user interface.0 (service pack 2 required for Windows XP and 32-bit Windows Server 2003) • Mozilla Firefox 2. and other supporting technologies. Workforce Timekeeper can optionally be run with an HTML user interface. Small Business Server Editions1 • Microsoft Windows Server 2008 • Microsoft Windows XP with service pack 21 • Microsoft Windows Vista1 • Microsoft Internet Explorer 6.0 GHz or better Intel Pentium III Minimum requirements: • • • • • • Windows XP: 333 MHz Windows Vista: 1 GHz Windows XP machines: 256 MHz (minimum) Windows Vista machines: 512 MHz (minimum) Recommended: 10 GB Minimum: 1. 7. a Java Runtime Environment (JRE).Chapter 2 Workforce Timekeeper and other Labor and Scheduling products Client software requirements The client layer of the Time & Labor and Scheduling products contains browsers.5 GB • Browser support JRE support Processor (Intel Pentium)2 RAM3 Hard disk space 38 Kronos Incorporated .0+ (service pack 2 required for Windows XP and 32-bit Windows Server 2003) Sun JRE 1. operating systems. Enterprise.x. Small Business Server Editions1 • Microsoft Windows Server 2003 (32-bit) R2 — Standard.

For Mac OS. No new Workforce Central release is necessary to support these updates. 39 . 56K dial-up or Frame relay Network bandwidth • • Other requirements • • • • • 56K dial-up or Frame relay 56K (minimum) Fractional T1 or T1–T3 (recommended) CD-ROM reader (or access to one on the network) Network card Non-persistent (session) cookies enabled JavaScript enabled Pop-up-blocking software configured to enable the Workforce Timekeeper server to show pop-up windows Java Client HTML Client 1. When selecting processor speed. If you need to move or copy and paste an organization map that is on the order of 30. 3. 16 colors are supported but the colors may not be ideal Adobe Acrobat Reader Adobe Acrobat Reader v6.0. Adobe Acrobat Reader v6.000 nodes or more. Workforce Central automatically supports security and bug service packs specific to these operating systems.0 • HTML Client Optimized for: • • 800 x 600 or 640 x 480 with scroll bars 256 colors. consider the processor recommended for the operating system and hardware that are used. 2. 16-bit resolution (recommended) • 800 x 600 with scroll bars (minimum) Note: The browser window must be maximized and no more than three rows of stacked browser toolbars should be visible in order to make all functions in the applets usable. may need to be set up as default application. Kronos recommends at least 512 MB of real memory and 256 MB of virtual memory.System requirements Item Display resolution and colors Requirement Java Client 1024 x 768.

2 (for both application and web server • machines) • • • • • • • Application server Network protocol Web server software (HTTP daemon) 40 Kronos Incorporated . Datacenter. such as an underscore. refer to your Hardware Recommendation Report and your Kronos Representative. v6. web server. and database components.0 (Windows Server 2008)2 Apache 2. Enterprise.3 TCP/IP Microsoft IIS 6. Small Business Server Editions Microsoft Windows Server 2008 Sun Solaris (SPARC) (32-bit and 64-bit) v10 IBM AIX (pSeries) (32-bit and 64-bit) v5.2. Workforce Timekeeper system requirements Item Operating system1 Requirement • Microsoft Windows Server 2003 (32-bit). System requirements for the Workforce Timekeeper application server and web server are outlined in the following table. For example. you might install Workforce Timekeeper and application server on two machines inside a firewall: one primary and one backup. Small Business Server Editions Microsoft Windows Server 2003 (32-bit) R2 — Standard. You might also have another machine with Workforce Timekeeper and application server software within the firewall for generating reports and one web server machine outside the firewall. Microsoft IIS 7.3. Enterprise. including the number of employees and users at a company. These components can be installed on the same machine or different components can be installed on separate machines. Datacenter.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products Application software system requirements Workforce Timekeeper consists of application server. Actual hardware requirements for the Workforce Timekeeper applications are based on many variables.0 (Windows Server 2003). For Kronos recommendations specific to your environment. service pack 1 — Standard.1‘ Red Hat JBoss AS 4. Process Manager may fail. Note: Server names must not include nonstandard characters. If a server name contains a nonstandard character.

Code pages — Because Workforce Timekeeper v6. Workforce Central automatically supports security and bug service packs specific to these operating systems.6. you should consider installing it on a separate machine. IIS versions are explicitly paired to the Windows operating system versions. multiple instances of most languages can coexist on a single database without regard to code page (such as Latin 1. Bidirectional character sets — Workforce Timekeeper does not support bidirectional character sets. No new Workforce Central release is necessary to support these updates.System requirements Item Server-side JRE support (bundled with JBoss installations) Requirement • • • Microsoft Windows: Sun JRE 6.0 IBM J9 SR2 1. Japanese.6.0_07 provided)3 Sun Solaris: Sun JRE 6.1 supports Unicode character encoding.6.0 family can be used Note: If you are using the Advanced Reporting capabilities of Workforce Timekeeper. such as Hebrew and Arabic. 3. including multibyte characters (such as Chinese. IIS 7 can only be used in conjunction with Windows Server 2008. and Latin 9.6. especially if the database is large. or Latin 9).the 2.0 (1.0 (1. General requirements and considerations include the following: • Installation machine — Oracle databases cannot be on the same machine as other Workforce Timekeeper components. • • • 41 . Later versions in the 1. For example. and Korean). Although you can install Workforce Timekeeper on the same machine as a SQL Server database. refer to “Reports” on page 70 for specific prerequisites and other considerations. Latin 2. Database system requirements The Workforce Timekeeper software requires an Oracle or Microsoft SQL Server database. When using Internet Information Server (IIS) as the web server. the Workforce Central installer automatically detects the Windows operating system version and applies the correct configuration scripts for IIS. Latin 2.0_07 provided)3 IBM AIX: J2RE 1. Multibyte character support — All databases support multibyte characters for any character set outside of Latin 1.

1. service pack 1 — Standard.1) or Oracle 11g (11. Workforce Analytics supports SQL Server 2005 only. service pack 23 or SQL Server 2008 Oracle 10g Rel 2 (10. Supported middleware is subject to change by the vendor.0) Enterprise or Standard Editions Multibyte characters TCP/IP • • • • • • • RDBMS • • Character set output • Network protocol • 1. Refer to your Hardware Recommendation Report and your Kronos Service Representative about ongoing space usage guidelines for your specific environment. Small Business Server Editions Microsoft Windows Server 2008 (32-bit and 64-bit) Sun Solaris (32-bit and 64-bit) IBM AIX 64-bit HP-UX 64-bit All other operating systems supported by Oracle. Database only. Disk space requirements Many variables determine disk space requirements for the Workforce Timekeeper database server. Note: All RDBMS and middleware versions identified in this chapter represent the minimum versions supported. Small Business Server Editions Microsoft Windows Server 2003 (64-bit)2 Microsoft Windows Server 2003 (32-bit) R2 — Standard. 2. Workforce Central automatically supports security and bug service packs specific to these operating systems.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products Database system requirements Item Operating system 1 Requirement • Microsoft Windows Server 2003 (32-bit). Enterprise. 42 Kronos Incorporated . SQL Server 2005. Datacenter. Enterprise. No new Workforce Central release is necessary to support these updates.2. Workforce Central must be installed on a separate Windows server running a 32bit version of Windows. Datacenter.0. including minor revisions. 3.

Workforce Central Portal system requirements The Workforce Central Portal for Microsoft® SharePoint 2007 organizes data from a Workforce Central system and displays it in a way that is easy for managers to read. Note that making major changes to the time on the database server may cause unpredictable behavior in various parts of Workforce Timekeeper. For this reason. After you install Workforce Timekeeper. From the upper-right corner of the Workforce Timekeeper workspace. or after periods of heavy activity. To accomplish this. you can access this option in the Clock Synchronization section of the Workforce Timekeeper System Settings as follows: 1. Kronos recommends that you restart the clock synchronize daemon by selecting the Threads tab in the System Settings. the Portal uses a set of preconfigured web 43 . especially if those changes are made just before.System requirements Machine time Workforce Timekeeper has the option of using the machine time on the database server to compute Time Stamp and other time-related values on the Workforce Timekeeper application server. When this option is enabled. When drastic changes are required and the Clock Synchronize option is enabled. click the Clock Synchronize tab. small adjustments to the date/time on your database server and not allow it to stray drastically from the true time. you should make every effort to keep the time on the database server as accurate as possible. Kronos recommends that you make frequent. From the System Settings workspace. 2. click Setup. This immediately resynchronizes the Workforce Timekeeper application server time-relative values to the time of the database server. and then select System Settings from the System Configuration box. during.

System requirements for Workforce Worksheet. you can take advantage of Workforce Worksheet. which is installed on a client machine include the following: • • Microsoft . which enables you to dynamically retrieve a number of Workforce Central reports and Genies using Microsoft Excel 2008. Workforce Worksheet system requirements If you use the advanced reporting (SSRS) option. 7. Microsoft Windows 2008 Server Microsoft Internet Information Server (IIS) 6.0 .NET Framework 3. refer to the Workforce Central Portal Installation Guide.0 or Microsoft SharePoint Portal Server 2007 Microsoft Office Web Components (OWC). Workforce Central Portal requires the following: • Kronos products (depending on the web parts you are deploying) – – – – • – – – – – Workforce Central v6.NET Framework version 2. which are modular components used within the SharePoint site to display information.0 (or higher) Microsoft Office Excel 2007 44 Kronos Incorporated .0 Microsoft Windows SharePoint Services 3. Setting up an environment for Workforce Worksheet requires both client and server activities: You must install Workforce Worksheet on applicable client machines and you must prepare the server so that Workforce Worksheet can connect to Workforce Central.0 or higher For Healthcare Web Parts: Workforce Scheduler For Retail Web Parts: Workforce Forecast Manager For Manufacturing Web Parts: Workforce Activities Microsoft Windows 2003 Server.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products parts.exe Microsoft software components: For more information.0. owc11.

Your choice of network and connecting hardware can affect the performance of your Workforce Timekeeper system. Each client must support Transmission Control Protocol/Internet Protocol (TCP/IP) as a transport protocol. The Microsoft Office 2007 installer delivers the interop assemblies by default if the computer has the . • For more information about Workforce Worksheet. Before you install your Workforce Timekeeper system.0. or by using the ping command in Run window (Start > Run on Windows machines) to locate the host server by its IP address. Check each application server and client workstation’s physical connection to the network. refer to Installing and Configuring the Workforce Worksheet.50272. Note: You do not need to install this package if you installed the .exe) (requires Microsoft Office product to be installed) This package can be downloaded from the Microsoft web site. Do this by creating a remote login session to your host server with Telnet. such as the application server and the Background Processor. 2. Verify that each application server and client workstation supports TCP/IP.891 (x86) (vstor.exe) This package can be downloaded from the Microsoft web site. Network requirements Workforce Timekeeper components. The number of nodes on your network and the transfer throughput are some of the external factors that can affect performance. 2007 Microsoft Office System Update: Redistributable Primary Interop Assemblies (PrimaryInteropAssembly.NET framework before you installed Microsoft Office 2007. communicate with the database server over a local area network (LAN). 45 . do the following: 1.NET Framework installed.System requirements • Microsoft Visual Studio 2005 Tools for Office Second Edition runtime (VSTOR 2005 SE). build 8.

sometimes described as a domain controller. It runs on a separate server. It supports the NT authentication protocol (also known as NTLM) used by Workforce Timekeeper. and Enterprise Edition) Operating System Microsoft Windows XP Microsoft Windows Server 2003 Microsoft Windows Server 2008 46 Kronos Incorporated . Advanced Edition. refer to Installing Workforce Timekeeper. using the RDBMS client software if required. Active Directory Active Directory is a Microsoft service that has long been used in Windows networks.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products 3. Support for Citrix browser-based UI MetaFrame Version XP Presentation Server (Standard Edition. Citrix MetaFrame support also enables diskless clients to access Workforce Timekeeper. Single Sign On (SSO) — Siteminder v6. Connect to your database server using your RDBMS SQL Query tools to verify that each application server and client workstation can connect to the host server. Active Directory also supports LDAP. Authentication Workforce Timekeeper supports the following authentication methods: • • • NT authentication LDAP authentication — For more information.1 supports Citrix MetaFrame to improve client performance for customers who use non-Pentium or low-end Pentium client machines. The Workforce Timekeeper application server communicates with Active Directory using the Windows NTLM challenge/response protocol. service pack 3 Citrix MetaFrame support Workforce Timekeeper v6.

Earlier versions of the plug-in are not supported for Workforce Timekeeper 6.6 JDK.System requirements Java 1.6 The Sun Java 1.1 as an executable file that is downloaded to the client when a Workforce Timekeeper applet is invoked. All Workforce Timekeeper Java components are compiled and built using the Sun Java 1. The Java 1.6 JDK are supported for Workforce Timekeeper 6.6 JDK is deployed on the Workforce Timekeeper server as part of the standard installation. The Firefox plug-in must be downloaded and installed separately.6 plug-in is provided with Workforce Timekeeper 6.6 plug-in and the Sun Java 1.1. The use of the plug-in download is strictly associated with the Microsoft Internet Explorer browser. The Firefox browser does not download the plug-in.1. The Sun Java 1. The Java plug-in is for use on the client side in conjunction with applets deployed by Workforce Timekeeper. Earlier versions are not supported. 47 .

which requires a SQL Server or Oracle database. Install Workforce Timekeeper on a Windows machine (even if you are using Workforce Timekeeper on UNIX). Running Database Manager Database Manager is used for new Workforce Timekeeper installations and for upgrades. Database Manager. It provides an automated means to install and upgrade the Workforce Central database schema. 48 Kronos Incorporated . is used to create. Create an empty database with designated Workforce Timekeeper users (TKCSOWNER. SUPRKRON.) New installations of Workforce Timekeeper To create a new Workforce Timekeeper database. It works with both SQL Server and Oracle databases. and so on). It is also used for Workforce HR/Payroll upgrades. or reconcile the Workforce Timekeeper database tables and keys. The following sections describe: • • • “Database Manager” on page 48 “Oracle considerations” on page 51 “SQL Server considerations” on page 54 Database Manager Database Manager is the Workforce Central database deployment tool. and a web server and then start Workforce Timekeeper in offline mode. Database Manager does not support service packs. keys. which is accessed from an HTML web page. uses a utility called Database Manager to create or upgrade the database objects (tables. stored procedures. 2. (A separate utility called the Patchelizer is used for service packs. triggers.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products Database options Workforce Timekeeper. an application server. you must do the following: 1. upgrade. and KRONREAD). You must also connect these user IDs to roles within the database that are assumed to be available for the grant scripts run by Database Manager.

While Database Manager is running. you must do the following: 1. Upgrading an existing Workforce Timekeeper database To update an existing Workforce Timekeeper database. it displays its current status and a progress description in the browser. Access Database Manager in a browser by entering the following URL: http://WebServer/instance_name/DBMgrLogonServlet where WebServer is the name of the machine where the application server is installed and instance_name is the name of the Workforce Timekeeper instance (such as wfc).and so forth). If necessary. Database Manager then installs the supporting scripts and control files in the directories for that instance of the application server. Access Database Manager in a browser by entering the following URL: http://WebServer/instance_name/DBMgrLogonServlet where WebServer is the name of the machine where the application server is installed and instance_name is the name of the Workforce Timekeeper instance (such as wfc).: a. All detail results are displayed in the wfc. version.log on the application server machine. The application server validates your selection before it starts. it provides a completion timestamp. 2. Run the Database Manager utility on a Windows machine to upgrade the database: a. it also provides SEQUENCE count repair. run the Database Manager utility on a Windows machine. Upgrade Workforce Timekeeper on a Windows machine (even if you are using Workforce Timekeeper on UNIX). 3. b. Workforce Scheduler. Select the components and versions to be installed and start the process. and so forth). Start the upgraded Workforce Timekeeper in offline mode. index. When Workforce Timekeeper is running in offline mode. As it completes each step. 49 .Database options 3. and object type (table. They are stored by component (Workforce Timekeeper.

This process starts when the installation or upgrade is finished. to validate that the database contains what it should. The results of the reconcile are written to the following log file. which is located on the application server machine in c:\Kronos\wfc\licensing: DBManager_timestamp.log where timestamp is the current date and time. SEQUENCE count repair Database Manager reconciles the SEQUENCE counter column for each table maintained in the SEQUENCE table against the actual maximum primary key of those tables. Note: The same information is also collected in the wfc. 50 Kronos Incorporated . it displays the anomaly along with repair SQL in the log. Select the components and versions to be installed and start the process. In addition to reporting this.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products b. Reconciliation component Database Manager supports reconciliation of the current database configuration to metadata supplied by each version/release of Workforce Timekeeper components. This allows you to: • • Monitor the progress of the upgrade Review the timestamp information of the SQL statements to identify statements that are taking a long time to run. This executes the SQL reported in the log against the out of SEQUENCE table rows. Database Manager provides an option to fix the SEQUENCE table automatically.log. The log file contains all of the information generated by Database Manager as well as each SQL statement (with timestamp) that is executed by Database Manager. You can also run this process on an ad hoc basis by logging on to Database Manager and clicking the Reconcile option. In cases where the counter column is less then the maximum primary key value for the table. The application server validates your selection before it starts.

Generally this varies depending on whether or not you use RAID (Redundant Array of Independent Disks). The recommended Oracle initialization parameters are included in the Installing Workforce Timekeeper and Upgrading Workforce Timekeeper books. Kronos has tested a number of parameter settings for optimal performance of an Oracle database with Workforce Timekeeper. You should be proficient with creating and managing an Oracle instance.1 supports Oracle 11g databases. Oracle initialization parameters A key to assuring optimal application performance with an Oracle platform is to minimize the amount of physical I/O required to process a query. and managing database accounts. The JDBC driver for Oracle supports both Oracle 10gR2 and 11g. you can specify the actual database segments (tablespaces in Oracle or file groups in SQL Server). 51 . The values identified should be set to assure optimal performance of Workforce Timekeeper. In Workforce Timekeeper v6.1. A Database Manager mapping workspace displays the virtual segment in the installation next to a mapping drop-down box that allows you to select where those objects should be installed. Workforce Timekeeper v6. Oracle considerations In addition to Oracle 10g R2 databases.1. With Workforce Timekeeper v6. With this in mind. Consult an Oracle database administrator’s guide if you are unfamiliar with these functions. this is no longer required. Oracle 10g R1 or earlier databases are not supported for Workforce Timekeeper 6.Database options Segment mapping Previous releases of Workforce Timekeeper required a specific group of segments to be defined in the tablespace.1. This means that segments defined to the application as TKCS1 could be installed in SYSTEM (Oracle) or PRIMARY (SQL Server) if you do not want to maintain separate segments. creating and updating tablespaces.

the maintenance tasks of the Oracle database instance. • In Workforce Timekeeper’s single schema model. an Oracle database instance can contain multiple users. Tables with the same name can reside in the same database instance if different users own them. views. such as table space allocation and backup/ restore. but the application connects to the database as different user. each in separate schemas. a schema called TKCSOWNER owns all Workforce Timekeeper tables. multiple schemas can be created within one instance. Because of this. application data sets can share the database instance. In Workforce Timekeeper’s multi-schema model. Each schema can own or maintain its own objects without knowledge of other schemas. These distinct user IDs have default access to their own objects. Using multiple schemas A schema is an Oracle database user that has the ability to create its own objects within a database.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products Other documented or undocumented Oracle initialization parameter settings that are not listed in the table should be left at the default setting. if you need to host data for multiple customers or maintain multiple variations of your application data. and other database objects. there is no guarantee that performance will be optimal. and the application connects to the database as TKCSOWNER as well. a schema called TKCSOWNER owns all of the tables. with each user having a distinct collection of tables. can be done once and applied uniformly for all schemas. The Oracle RDBMS is designed for multiple schemas to exist within a single database. SUPRKRON. However. and on internal customer and synthetic database testing. Although Workforce Timekeeper will function without setting these values. These recommendations were based on testing and resolution of customer escalation issues. • Most implementations of Workforce Timekeeper use the single schema model. With multiple schemas. Thus. The data set of a given application installation resides completely within a given schema (set of objects owned by one user). 52 Kronos Incorporated . This reduces some of the costs associated with data management.

A Workforce Timekeeper instance cannot access the data in any schema other than the one defined in the instance’s configuration. • • 53 . If you are using multiple schemas. Each schema is independent of any other schemas defined in the same database instance and can be at different versions of Workforce Timekeeper if required. • Combining currently independent databases as schemas within a new single database instance is a manual process. This information is maintained in encrypted form in the configuration files of the Workforce Timekeeper instance. Note: Database Manager does not recognize any schemas other than the one owned by the user ID used to log on to the database. When you install Workforce Timekeeper.Database options The use of multiple schemas is transparent to the main runtime components of the Workforce Timekeeper application code. The application components will connect to the correct schema indicated by the access rights of the database user ID used. you should consider the following: • • • Plan for the number of schemas required in each database instance ahead of time and define a dedicated database owner for each schema. You must create database user IDs as schema owners in the new target instance. you must enter the user ID and password to access the applicable schema. run Database Manager once for each schema to establish the tables and other database objects needed for the application instance. Manually create the database user IDs on the database before creating the Workforce Timekeeper schema. export the contents of each current database. After you create a Workforce Timekeeper instance for a specific schema. Install a separate Workforce Timekeeper instance for each schema. and import them into the schemas of the new database.

You should. obtain a copy of the Hardware Recommendation Report from your Kronos Representative. SQL Server for Workforce Timekeeper is installed with default settings. This document provides important space usage guidelines for your specific environment. be proficient with creating a database. however. Before you set up the database. Generally. consult the SQL Server Books Online. and managing logins. If you are unfamiliar with these functions. adding file groups.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products SQL Server considerations SQL Server databases do not require the same level of performance tuning as Oracle systems. 54 Kronos Incorporated . creating files.

1 uses a Red Hat JBoss application server. For more information refer to: • • Windows systems — Installing Workforce Timekeeper or Upgrading Workforce Timekeeper AIX or Solaris systems — Installing and Upgrading Workforce Timekeeper on UNIX. Note: Workforce Timekeeper v6.3 CP01 only. It is not supported on JBoss v4. which is required for Reports and Database Manager. JBoss is an open source application server that implements the complete Java 2 Enterprise Edition (J2EE) stack. If you use Workforce Timekeeper in a UNIX environment.1 is supported on Red Hat JBoss v4. It centralizes application services such as web server functionality. you must also install one Windows companion server.Workforce Timekeeper installation requirements Workforce Timekeeper installation requirements Workforce Timekeeper can be installed in several different configurations: • • • Operating system — Windows or UNIX Application server — JBoss (bundled or unbundled) Web server — Apache or Microsoft IIS Operating system options Workforce Timekeeper can be installed on Windows or UNIX (Solaris or AIX) systems. 55 .3 Community Edition. Workforce Timekeeper v6. including Java Server Pages (JSP). It uses technologies such as caching and connection pooling to improve resource use and application performance. and Enterprise JavaBeans (EJB). Application server options An application server is a software platform for developing and deploying multitier distributed enterprise applications. servlets. business components. and access to back-end enterprise systems.

help HTML files. The web server can also stream data back to clients more efficiently than the application server.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products The Workforce Timekeeper installation program will install JBoss or you can configure Workforce Timekeeper to work with a preinstalled version of JBoss. an application server thread will be occupied for a relatively long time. the application server can return the whole page to the web server as fast as possible. and applet JAR files are served by the web server. Note: Workforce Timekeeper can also be installed and configured for other application servers. style sheets. The Workforce Timekeeper installation program allows you to select any of the following web servers: • • Apache with or without SSL Microsoft IIS with or without SSL (Windows only) Apache web server The Workforce Timekeeper installation program installs the Apache web server if it is selected during the installation procedure. 56 Kronos Incorporated . you can install Workforce Timekeeper and manually configure the product to use the preinstalled version of Apache. This is because Java normally uses a blocking I/O model where each connection is serviced by a separate thread. The web server handles static pages so the application server does not have to waste cycles on them. If the client’s network connection is slow and/or if the page being downloaded is large. Web server options Workforce Timekeeper requires web server software. and the web server can then stream the data down to the slow client more efficiently. JBoss can be used on Windows or UNIX (Solaris or AIX) systems. All JavaScript files. in regular or secure (SSL) mode. If you have already have Apache installed on your system. See your Kronos Representative for more information. By sizing the buffers on the web server correctly.

you must have the key and certificate files before installing Workforce Timekeeper. Depending on the operating system of your web server machine. Note: Microsoft IIS is not supported on UNIX. 57 . the installation program automatically sets the IIS settings required by Workforce Timekeeper: • • • • • Read permission Scripts enabled Scripts folder present Anonymous access Mappings for .asp and . and news groups components. The installation procedure requires that you enter the location of these files. you should install IIS v6 (Windows Server 2003) or IIS v7 (Windows Server 2008). See “SSL security considerations” on page 129 for more information. Each machine must have its own key and certificate files and you must copy the files into a directory on the server. you must obtain the key and certificate files. When you run the Workforce Timekeeper installation program. Workforce Timekeeper only uses the web server component. Each machine must have its own key and certificate files and you must copy the files into a directory on the server. If you choose to use IIS.Workforce Timekeeper installation requirements Although Workforce Timekeeper will also properly configure Apache to run under SSL. you must install it before you install Workforce Timekeeper. Microsoft IIS web server (Windows Only) Microsoft Internet Information Server (IIS) is a Windows application that consists of FTP. e-mail. web server. using the default settings. See “SSL security considerations” on page 129 for more information.asa files If you are using IIS with SSL.

can be installed in any of three basic configurations: • • Combined installation — Workforce Timekeeper. and web server all on the same physical machine.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products Configuration options Workforce Timekeeper. Multiple instance installation — Multiple instances of Workforce Timekeeper on the same machine. refer to the Workforce Timekeeper installation documentation. This can be multiple instances of a combined or separated installation. along with application server and web server software. • For information about installing these configurations. Separated installation — The application server with Workforce Timekeeper dynamic information on one machine and the web server with the Workforce Timekeeper static information on another machine. 58 Kronos Incorporated . application server.

The Typical option is implemented differently depending on your operating system. However. It allows you to use a preinstalled JBoss application server and a preinstalled Apache or Microsoft IIS web server.Typical and custom environment options Typical and custom environment options The Workforce Timekeeper installation program allows you to select from a typical or custom installation: • A typical installation installs and configures Workforce Timekeeper and all the required components: JBoss application server software and Apache web server software. JBoss. If you are installing all Workforce Timekeeper components on the same machine. • Typical server environment option The most automated and simplest way to install Workforce Timekeeper is to use the Typical server environment option and install Workforce Timekeeper. (It also configures Microsoft IIS web server software. this installation option provides an EAR file and a ZIP file. and Apache on one machine. you can also use the Typical option for a separated application and web server installation. which you must configure manually: – – The EAR file contains server-side code (Workforce Central run-time code) The ZIP file contains static content (such as images and static HTML) and is used when you have separate web and application server machines. A custom installation does not install JBoss or web server software.) The typical option is the simplest and most automated way to install Workforce Timekeeper. if it is already installed on your machine. Essentially. which is everything you need to get the Workforce Timekeeper system up and running. 59 . the ZIP file is not used.

you could use the Workforce Timekeeper Typical server environment option to accommodate various installation configurations: • Combined web and application server – – – • Workforce Timekeeper application JBoss application server Microsoft IIS instead of Apache. which must be installed before you install Workforce Timekeeper. Combined web and application server — Installs Workforce Timekeeper. and Apache. JBoss. Machine 1: Workforce Timekeeper and JBoss application server Machine 2: Microsoft IIS.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products Windows machines The Typical server environment option enables you to select from the following: • • • Application server only — Installs Workforce Timekeeper dynamic data and JBoss application server Web server only — Installs Workforce Timekeeper static data and Apache. but can also use Microsoft IIS if it is already installed on the machine. Two instances of a combined Workforce Timekeeper. and Apache installation on the same machine Two instances of Workforce Timekeeper and JBoss on one machine and one instance of Apache or IIS on another machine Separated web/application servers – – • Multiple combined or separated instances – – 60 Kronos Incorporated . but you must install it before you install Workforce Timekeeper. but can also use IIS if it is already installed on the machine For example. JBoss.

and Apache Custom server environment option The Custom server environment option enables you to use a preinstalled JBoss application server. Configuring a custom installation is a three-step process: 1. Configure the application server connectors to work with an Apache (Windows or UNIX) or IIS web server (Windows only). Detailed instructions for configuring Workforce Timekeeper with a preinstalled JBoss application server are included in the Installing Workforce Timekeeper and Upgrading Workforce Timekeeper documents. but requires that you manually deploy and configure the application server and web server to work with Workforce Timekeeper. It also allows you to select from the following: • • • Application server only. 2. which installs Workforce Timekeeper dynamic data and JBoss application server Web server only. 3. selecting the Custom option. which installs Apache and Workforce Timekeeper static data Combined web and application server. Run the Workforce Timekeeper installation program.Kronos managed option on a UNIX machine installs a JBoss application server and an Apache web server. Deploy the Workforce Timekeeper EAR file to work with the preinstalled version of JBoss. 61 .Typical and custom environment options UNIX machines The Typical . JBoss. which installs Workforce Timekeeper.

query for employee information. Workforce Timekeeper is a prerequisite for all of the following Workforce Central products. Specific capabilities enable users to define pay policies. Workforce Forecast Manager requires that Workforce Scheduler is installed on the same machine. and storing time and attendance data. Workforce Attendance — An attendance-monitoring product that extracts Workforce Timekeeper attendance information for rules processing and generates the appropriate warnings and ill-treats for managers. manage employee time. as described in the Installing Workforce Timekeeper and Upgrading Workforce Timekeeper books: – Workforce Timekeeper — Workforce Timekeeper manages labor resources in real time by collecting.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products Installing Workforce Central products The Workforce Central installation kit is used to install the following: • Workforce Central Suite applications — The Kronos® Workforce Central®suite installation kit enables you to install the following products at the same time. Workforce Operations Planner requires that Workforce Scheduler is installed on the same machine. Workforce Operations Planner — A retail scheduling product that enables budget stakeholders to collaboratively develop and review the budget. It also generates a labor forecast in hours as well as dollars for a future fiscal period. create and maintain schedules. the number of staff needed to meet the level of service required in a grocery store on a given day. Workforce Leave — A time-off monitoring product that tracks the time that employees have taken off under a company’s leave policies. for example. maintain employee demographics. – – – 62 Kronos Incorporated . and generate reports. processing. Workforce Forecast Manager — A product typically used in retail environments when staffing requirements vary depending on business demand. – – Workforce Scheduler — An enhanced scheduling product used when staffing requirements vary depending on business demands.

or you can install them at a later date. but you will not be able to access them until you apply the license file. 63 . Interface programmers will use the client-side Interface Designer—which continues to use the Workforce Connect look-andfeel—to create and update data integration interfaces. to collect data at all stages of the production process and provide real-time information to help shop floor supervisors manage people and resources. Process Designer is a client application and can be installed on client machines. Workforce Integration Manager is a next-generation data integration tool that interfaces Workforce Central products with other business-critical applications. You cannot install any of these products without Workforce Timekeeper. Workforce Integration Manager — Replacing Workforce Connect. typically used in manufacturing environments.Installing Workforce Central products – Workforce Activities — A product. Important: All of these products except Workforce Device Manager require a separate license. Workforce Device Manager — A product that enables the flow of data between Workforce Central applications and data collection devices. which is an entirely Windows client-side utility. Unlike Workforce Connect. – – You can install one or more of these products at the same time that you install Workforce Timekeeper. Workforce Device Manager replaces Data Collection Manager. Workforce Integration Manager Integration Manager allows users to run and maintain interfaces from their Workforce Central web interface. the following additional products can be installed from the Workforce Central installation kit: – Process Designer — Process Designer is the visual process design tool used to modify preconfigured process templates that are included with Process Manager (which is part of Workforce Timekeeper). The installation program will let you install these products without a license. track progress. Although most Process Manager components are installed on the application server when you install Workforce Timekeeper. • Although not part of the suite installation. and resolve production issues as they occur.

For more information. Interface Designer does not require a separate license. Workforce Worksheet does not require a separate license. refer to Installing and Configuring Workforce Worksheet. Workforce Central Portal does not require a separate license. – Workforce Central Portal — Workforce Central Portal organizes data from your Workforce Central system and uses Microsoft SharePoint web parts to display the data in a way that is easy for managers to read. refer to the Workforce Central Portal Installation Guide. refer to Installing Workforce Timekeeper or Upgrading Workforce Timekeeper. Any Excel worksheet created from this data can be refreshed on demand or dynamically with live data from Workforce Central. – Workforce Record Manager — Workforce Record Manager . For more information. you must install Interface Designer in order to upgrade the Connect links to Workforce Integration Manager. For more information. refer to Installing Workforce Timekeeper or Upgrading Workforce Timekeeper. For more information. When upgrading from Workforce Connect. Workforce Record Manager requires a license and typically involves the installation of a test database and server. Workforce Worksheet requires Advanced Reporting (SSRS).Chapter 2 Workforce Timekeeper and other Labor and Scheduling products Process Designer does not require a separate license.Setup Data Manager is a separately installed component that allows you to archive and manage data. Instructions for installing Interface Designer are included in the Workforce Timekeeper installation documentation. – Interface Designer — Interface Designer is a client application used to create custom interfaces for Workforce Integration Manager. – Workforce Worksheet — Workforce Worksheet enables users to dynamically retrieve a number of Workforce Central reports and Genies from a client machine using Microsoft Excel 2007. 64 Kronos Incorporated . Refer to the Workforce Record Manager Installation Guide for more information about installing Workforce Record Manager.

Web server staging area — Contains all Java files used to configure the web server. Each product folder contains • Bill of materials (BOM) — Lists the files and directories for the staging areas of the application server and web server. The deployment area uses the following directory structure for each Workforce Central product installed: kronos deployments release wfp_staging app_server boms web_server wtk_staging app_server boms web_server wfc wfp_staging app_server applications WEB_INF wtk_staging The wfc folder is organized by product. the installer loads the required software from the installation CD to the deployment area on the host machine.Workforce Timekeeper deployment Workforce Timekeeper deployment The deployment process for Workforce Timekeeper uses the information that you provide when you run the InstallShield Wizard to install and configure the applicable products. and each product folder contains the non-Java properties files used by the product. The installation phase of the deployment process installs the applicable files on the host machine and the configuration phase makes the system ready to use. 65 . Application server staging area — Contains all Java files used to configure the application server. Installation phase Using the information collected by the InstallShield Wizard. • • The release folder is organized by product.

such as licensing. the following files are created during the installation phase: • install.dict — A text file that is populated by information entered by the user in the InstallShield Wizard and that contains a list of installed property names and values. install. • Configuration phase The configuration phase of the deployment process configures the system based on the features that were selected. database information that was provided. Non-Java components.html files. and .jsp files. including the following: • • • • • Creates a JBoss instance Creates an external instance directory for custom property files Configures JBoss connectors Configures JBoss for the instance Configures the products The configuration phase also creates and deploys the enterprise application archive (EAR) file for the selected products.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products In addition to installing files and directories.class files that make up the application’s business logic. settings that were specified.dict file created during the installation phase and the BOM files to create the supporting infrastructure.The EAR file is a read-only file that is used exclusively by the application server (such as JBoss). . The configuration phase uses the directory structure created by the installation phase to determine the files needed to build the EAR file.xml file) and a web application archive (WAR) file. It uses the install. and files that were installed during the installation phase. are deployed outside the WAR file in the runtime directory. It consists of a deployment descriptor (. With the exception of 66 Kronos Incorporated . The WAR file consists of the.txt —This file is created if there is a problem during the installation.

service pack. 67 .log — Is updated by every process that is running and includes the bill of materials (BOM) actions. the files are copied to the subdirectory that corresponds to the instance name (such as wfc or wfc1) and are modified before the EAR file is created. and ZIP files. otherwise the property files in release area are used. Property files are handled differently than other files because they require modification prior to installation. both of which are located in the Kronos\configuration folder: • • configuration_date. If property files are in the patch or service pack areas.Workforce Timekeeper deployment properties files.log — Logs DeployGen events. The instance name directory overrides the patch. the it uses files from each of the application directories using the following rules: • • • • Files located in the release directory are the first choice. Files in the patch directory override files in the service pack and release directories. instance_creation. DeployGen builds the EAR. Files in the service pack area override files in the release directory. and release directories. The configuration phase also creates two logs. WAR.

log and instance_create. the directory structure of a Workforce Central environment with a combined application/web server looks similar to the following: kronos ant apache configuration boms deployGen deployments flexlm help jboss jboss_connectors jdk reporting uninstall Files used to remove Workforce Central files Used by installation phase of deployment License manager files Online Help files JBoss application server (if selected) Files to connect JBoss to the web server Folder for Apache web server (if installed) Configuration folder that contains BOMs and DeployGen.log files 68 Kronos Incorporated .Chapter 2 Workforce Timekeeper and other Labor and Scheduling products When the configuration phase is complete. as well as configuration.

. Files (jars. the Workforce Central properties files are no longer directly accessible.. The external folder only contains files and folders that are truly needed to exist in the external folder. All other files are in the EAR file. including help. The wfc folder is considered the “external” directory because its contents are external to the Workforce Central J2EE application. etc) required within the J2EE application are included in the EAR file. licensing.1. properties. You do not have direct access to the deployed EAR file. bin licensing lm logs plugins properties reporting reports Note: With the implementation of J2EE compliance and EAR file packaging in v6. 69 .Workforce Timekeeper deployment wfc applications abk calendar dbmanager . which means that you cannot change the properties files that have been packaged in the EAR file. Files that are created at system startup or by modifying System Settings will still be located in the external directory. and log files. wtk The wfc folder contains all external files for the default wfc instance. All modifications to properties files must be made through the System Settings of the user interface.

Advanced reporting The advanced reporting functionality. you must install SQL Server 2005 for SSRS. Advanced reporting requires that you purchase and install Microsoft SQL Server 2005 Reporting Services. No additional setup is required. Additional setup is required to use Workforce Timekeeper with SSRS.1 is based on the report definition language (RDL). For more information.1 does not support Crystal Reports. Advanced reporting — Uses RDL-compliant report templates and the Microsoft SQL Server Reporting Services (SSRS) engine. Workforce Timekeeper supports SSRS on SQL Server 2005. which is based on the SSRS (SQL Server Reporting Services) solution. Basic reporting The basic reporting functionality that is delivered when you install Workforce Timekeeper is based on the Reports Definition Language Client and does not require any special setup. is the full.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products Reports The reporting functionality of Workforce Timekeeper v6. refer to Installing Workforce Timekeeper. robust Workforce Central reporting 70 Kronos Incorporated . which is an XML schema from Microsoft for representing reports. If you use SQL Server 2008 for your Workforce Central database. • Notes: Workforce Timekeeper v6. The standard reporting functionality is delivered when you install Workforce Timekeeper. It is appropriate for customers who do not use Microsoft SQL Server Reporting Services. Workforce Timekeeper supports two types of RDL reports: • Standard reporting — Uses RDL report templates and the Reports Definition Language Client (RDLC) engine.

the SSRS solution requires a SQL Server 2005 installation with Reporting Services enabled. you should be aware of the following: Note: Workforce Timekeeper v6.com • 71 .Reports solution. If you plan to install SSRS and SharePoint on the same server.1 Advanced Reporting requires SQL Server 2005. No other web server can be conflicting with IIS. for example. but after installing IIS. the Workforce Central installer or the SSRS installer (Microsoft SQL Server) will install it. the Apache web server. It also requires an IIS web server. • You must use Microsoft Internet Information Services (IIS) on the SSRS server. For example. – – – • • • IIS must be installed before SQL Server 2005 and SSRS.0 framework must be installed on the Workforce Central application server and the SSRS server.NET 2. open the command prompt and enter the following command: nslookup server_name.kronos. Because SSRS uses a reporting database that is separate from the Workforce Central database. (The Workforce Central database can be either SQL Server or Oracle and the Workforce Timekeeper web server can be either IIS or Apache. to check that a machine is registered in the corporate DNS. Microsoft SQL Server installations require Microsoft SQL Server 2005 service pack 2 or higher. The . you must install SharePoint before installing SQL Server 2005. If it is not present. It is not supported on SQL Server 2008.) Prerequisites Before you set up the SSRS server. The IIS and WWW Publishing Windows services must be running. Make sure each server and client that will access Advanced Reports is registered in the corporate Domain Name Server (DNS) with its fully qualified domain name.

com/wfc/logon The custom security extension only affects the Workforce Central logon when you are using Workforce Central and SSRS together. This change requires all URLs to use fully qualified domain names. in the past. This means that you must use the fully qualified domain name when you log on to Workforce Central if you plan to use advanced reports.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products where server_name is the name of the server that you are checking. Custom security extension The reporting change with the greatest impact on the installation. Internet Information Services. The security between the Workforce Central application server and the SSRS server uses domain cookies. Installers should have experience configuring Microsoft SQL Server. install Microsoft SQL Server 2005 on a newly installed Windows 2003 operating system with the latest service pack installed. you could access Workforce Timekeeper on the server named dynamo by using the following URL: http://dynamo/wfc/logon With the custom security extension. The custom security extension is an extension to the SSRS server that allows authentication and authorization of reporting users to occur on the Workforce Central application server. additional points to consider include the following: 72 Kronos Incorporated . you must access the same server using this URL: http://dynamo. you can log on Workforce Central using the server name. and use of Workforce Central with advanced reports is the addition of the custom security extension. Reporting Services. and Workforce Central. IIS. you must add it to the domain.kronos. Using advanced reporting If you are using advanced reporting with SSRS. and Workforce Central. configuration. SSRS Reporting is intended to be installed and configured by an administrator with knowledge of Microsoft SQL Server. For example. If you do not plan to use advanced reports. If the server cannot be found. • • For best results.

To access the reports server directly (without logging on to Workforce Central). a new capability to run legacy custom Crystal reports is being introduced.0 (BOE) and Crystal Reports Server 2008 (CRS). Therefore. Running Crystal reports requires using a thirdparty product from Business Objects Corporation ™. which is a subset of Business Objects Enterprise. you must log on to the SSRS server as an administrator and enter the following in a browser window: http://localhost/Reports • Custom reports If you are upgrading from a previous version of Workforce Timekeeper and you use custom reports that were created in Crystal Reports. Using Business Objects Workforce Central no longer supports custom Crystal reports out-of-the-box as they were in prior versions. If you try to log on to SSRS directly. To access the SSRS server. you must do one of the following: • • Convert your custom reports to RDL. add the SSRS server to your browser’s “trusted” zone. 73 . you only have access to reports that are in your report profile. After you are logged on. you will be redirected to the Workforce Central logon page. Two Business Objects products are supported for this release: BusinessObjects XI 3.Reports • • All application servers and SSRS servers must exist on the same Windows domain. the Crystal Reports Server 2008. and add the Kronos Business Objects Adapter as described in the Installing Workforce Timekeeper manual. If you suspect that authorization is failing because cookies are not being passed due to firewall or Internet Explorer security configurations. you must be logged on to Workforce Central as a valid user. Install Business Objects.

Administrator privileges to set up and configure the Crystal reports server.0 Yes CRS 2008 Yes Prerequisites Before installing the Crystal reports server. For more information. you need the following items: • • • • • A Crystal report designer tool that enables you to edit your Crystal RPT source code. refer to their web site and documentation. The Crystal Reports DataDirect drivers downloaded from the Business Objects website. Refer to Upgrading Workforce Timekeeper for more information. Supported Platforms and Versions The Crystal reports servers support the following operating system configurations: Platform and version Windows Server 2003 Windows Server 2008 BOE XI 3. which you can download from Microsoft. 74 Kronos Incorporated . A proper installation of Crystal reports server with no port conflicts with preexisting software.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products Successfully running your custom Crystal reports requires you to configure and use products from Business Objects Corporation. Microsoft Visual C++ 2005 SP1. such as Workforce Central.

question marks. or Latin 9). 75 . With v6. Some points to remember when using Workforce Timekeeper for non-English systems include the following: • Code pages — Because Workforce Timekeeper v6. Japanese.Language support Language support Workforce Timekeeper and other Time & Attendance and Scheduling products support a number of different languages. Bidirectional character sets — Workforce Timekeeper does not support bidirectional character sets. and French. They may appear as rectangles.1. Asian fonts — Asian fonts must be installed on all client machines that connect to a Workforce Central server that uses Asian locale or currency. Latin 2. or otherwise unrecognizable characters. such as Hebrew and Arabic. Multibyte character encoding is not supported with SQL Server or Oracle 10g Release 1.1 supports Unicode character encoding. Spanish. such as Chinese. as described in the Guide to Translating and Customizing Workforce Central. however. and Latin 9. Multibyte character support — If you want to support any character set outside of Latin 1. including multibyte characters (such as Chinese. you must use Oracle 10g Release 2. Other languages can also be accommodated. Latin 2. Kronos provides a language pack that includes language files for several languages. the Asian characters will be garbled. • • • Refer to Installing Workforce Timekeeper or Upgrading Workforce Timekeeper for instructions on configuring a Workforce Timekeeper system for non-English languages. If Asian fonts are not installed. and Korean). multiple instances of most languages can coexist on a single database without regard to code page (such as Latin 1. you must install Workforce Timekeeper in English first and then apply the applicable language files.

Chapter 2

Workforce Timekeeper and other Labor and Scheduling products

Service packs
Kronos periodically provides service packs to update, fix, and enhance Kronos products between releases. Some key points about service packs include the following: • • Service packs are cumulative. Each service pack includes all the fixes from every previous service pack release. If you are using multiple instances of Workforce Central, the service pack installation program will automatically invoke Configuration Manager so you can select the instance to which to apply the service pack. – All instances that use the same database must use the same service pack. You must stop all instances before you install a service pack, regardless of whether the instances are on different machines or the same machine. Instances that do not use the same database can use different service packs. For example, instance wfc1 can be running service pack 3 and instance wfc2 can be running service pack 1.

Exception: If there is only one instance (by definition, the wfc instance), the service pack will be applied to that instance automatically without user interaction. • Service packs typically include fixes and updates for all products in the Workforce Central suite. However, only the products that you currently have installed are upgraded when you apply a service pack. Exception: Help files, which are available to all products and all instances, may be updated for products that are not installed. For example, if a service pack includes help file updates for Workforce Activities, then those help files would be installed, even if you do not have Workforce Activities installed.

76

Kronos Incorporated

Service packs

If you add a product to an existing installation that contains a service pack, the installation program for the new product will apply the service pack automatically. For example, consider the following: You install Workforce Timekeeper and Workforce Scheduler and then apply service pack 6.1.0. A month later, you purchase Workforce Leave. When you install Workforce Leave, you can apply service pack 6.1.0 at the same time. The same is true if you add a second instance. When you create the second instance, Configuration Manager lets you apply any service packs that are installed on the system. You do not need to apply them separately.

If you install a service pack and then decide not to use it, you can roll it back or uninstall it. In either case, the product returns to the base v6.1 state. There are, however, differences between a rollback and an uninstall: – A rollback leaves the installed service pack in the Kronos\deployments directory and an uninstall removes the service pack installation from the deployments directory. With a rollback, you can remove a service pack from one instance and leave it on other instances. An uninstall removes the service pack from all instances. For example, if wfc5 and wfc7 have service pack 5 installed, the uninstall removes service pack 5 completely from those instances and reverts them to v6.1.0. It also removes service pack 5 from the system. If you do not want to remove a service pack from all instances, use Configuration Manager.

The service pack directory structure exists at the same level as the release, custom, patch, etc., directories. However, it has an additional sublevel, the SPx level, where each SPx directory contains a specific service pack. The structure under the SPx level is identical to that under the release, custom, etc. directories. It consists of *_staging areas, each of which contains an app_server and web_server subdirectory.

77

Chapter 2

Workforce Timekeeper and other Labor and Scheduling products

Load balancing
To accommodate large enterprise environments, Workforce Central can be scaled, or expanded, to handle increased usage or to provide fault tolerance. Generally, scaling can be categorized as: • • Horizontal scaling — Adding web server or application server machines Vertical scaling — Adding multiple instances of Workforce Central on the same machine

Horizontal and vertical scaling can also be combined to achieve the benefits of both. When a Workforce Central environment consist of some combination of multiple instances, web servers, and application servers, communication between users and the system must be distributed across all servers. Various load balancing solutions are available that distribute user requests evenly across these array of servers. For more information about load balancing, refer to the load balancing appendix in Installing Workforce Timekeeper or Upgrading Workforce Timekeeper.

78

Kronos Incorporated

configure rules. users can edit timecards or schedules. and so forth. stating that the user does not have permission to access this resource. The Workforce Timekeeper installation program enables you to select from the following: • Workforce Timekeeper application server only — Select this option if you are installing a machine that will function only as an application server (and web server if you are using a combined installation). Refer to Workforce Central System Administrator’s Guide—Timekeeping for more information. you 79 . To do this. and so forth. however. Because the Background Processor is a service of the Workforce Timekeeper application. no BGP will be running on this machine. configure rules. You can. However. it is not installed separately. The Background Processor requires a fully functional application server and cannot be run independently of the Workforce Timekeeper application. to have accurate data whenever you want to run them. The Workforce Central platform will be installed with only the Background Processor threads running. With this installation. • Workforce Timekeeper BGP Server Only — Select this option if you are installing a dedicated Background Processor machine. continually checking the database to keep employee totals up to date. The only functionality available with a BGP-only server is configuring the server itself—changing the BGP configuration parameters. run Genies. such as the reports process. users cannot log on to the web server to edit timecards or schedules.Background Processor Background Processor The Background Processor (BGP) is a service that runs as part of the Workforce Timekeeper application server. It runs constantly. a message appears. turn the BGP on at a later date if needed. This enables processes that require up-to-date totals. run reports. run reports. If a user attempts to log on. With this configuration. The Background Processor threads are disabled on this server.

you must uninstall the application and reinstall it. 80 Kronos Incorporated . configure rules. • Workforce Timekeeper with BGP (Single Server) — Select this option if you want to install the Workforce Timekeeper application with the Background Processor threads enabled. you do not need to install most Workforce Central products on this machine. including a BGP. Refer to the Workforce Central System Administrator’s Guide and the Workforce Central System Administrator’s Guide—Timekeeping for more information about managing the Background Processor. The Background Processor is managed through the Workforce Timekeeper system settings. and as well as change BGP configuration parameters. selecting one of the other options in this dialog box. Users can log in and edit timecards or schedules. however. This provides a complete Workforce Timekeeper server. respectively. the same Workforce Central products must be installed on all machines and instances that access the same database. If you later decide to use this server for end users. The BGP is enabled by default in this configuration. it must be installed on the BGP-only machine as well as all other machines that connect to the same Workforce Central database. Important: In most cases. The only exception to this is that if you use Workforce Activities. and perform group edits.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products must use the Offline logon URL to log on to a BGP-only machine. which is typically: http://serverName/instance_name/offlineLogon where serverName and instance_name are the names of the Workforce Timekeeper server and instance. run reports. Because a BGP-only server cannot be used by end users.

no multiple instances” on page 84 “Separation.Sample configurations Sample configurations The following sections describe some of the many possible configurations for a Workforce Timekeeper installation: • • • • “Workforce Timekeeper with no separation or multiple instances” on page 81 “No separation. The application server listens on a vendor-specific port for requests sent via the connector installed on the web server. two instances” on page 82 “Separation. it did so via the web server. two instances” on page 85 Workforce Timekeeper with no separation or multiple instances The simplest configuration is to install Workforce Timekeeper on one or more machines. each running one web server and one application server. 81 . When one application server needs to communicate with another application server. using either HTTP or HTTPS. • • The web server listens on the default HTTP port 80.

A URL for IPC (server-to-server communication. Web Server HTTPS host Name option name IPC IPC HTTPS host option name App URL Context prefix WFC WFC /wfc /wfc Web URL prefix /WFC /WFC IPC Port Server 1 HTTP or Server 1 HTTP or Server 1 80 HTTPS HTTPS Server 2 HTTP or Server 2 HTTP or Server 2 80 HTTPS HTTPS Example URLs: • • http://server1/WFC/applications/wtk/images/foo. the two instances are called Inst1 and Inst2. or multiple versions. two instances Multiple instances of Workforce Timekeeper on the same machine can be used to support multiple languages. normally but not necessarily to the application server directly) will look like the following (IPC HTTPS option): //(IPC Hostname):(IPC Port)/(App URL prefix)/(path) For example: http://server1:80/wfc/XmlService No separation.gif http://server2/wfc/applications/wtk/foo. There is a single web server listening on the default port (80 for HTTP. Because there are two application server processes.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products The WFCSERVER table contains the following:. Each instance has a unique context.jsp. The connector configurations know to send URLs with the first instance’s prefix (/inst1) to port 8009 on the local 82 Kronos Incorporated . multiple databases. In the following examples. 443 for HTTPS). each must listen on a unique port (8009 and 8010 in the example). and handling both application servers via two different connector configurations.

instance 1) http://server1/inst2/applications/wtk/foo. the WFCSERVER table contains: Web Server HTTPS host Name option name IPC IPC HTTPS host option name App URL Context prefix Inst1 Inst2 Web URL prefix IPC Port Server 1 HTTP or Server 1 HTTP or Server 1 80 HTTPS HTTPS Server 1 HTTP or Server 1 HTTP or Server 1 80 HTTPS HTTPS /inst1 /INST1 /inst2 /INST2 Example URLs: • • • • http://server1/INST1/applications/wtk/images/ foo.gif (static content. instance 2) 83 . instance 2) http://server1:80/inst1/XmlService (IPC.jsp (dynamic content. and with the second instance’s prefix (/inst2) to port 8010 on the local server. In this case.Sample configurations server. instance 1) http://server1:80/inst2/XmlService (IPC.

) For example. you could also have a single web server with multiple connector configurations. the installation process supports only HTTP for inter-server communication on port 8080. (The JBoss default HTTP port is 8080. In this case. the WFCSERVER table contains: Web Server HTTPS host Name option name IPC IPC HTTPS host option name App URL prefix Web URL prefix IPC Port Context Inst1 Inst2 Server 3 HTTP or Server 1 HTTP HTTPS only Server 4 HTTP or Server 2 HTTP HTTPS only Server 3 8080 Server 4 8080 /inst1 /INST1 /inst2 /INST2 84 Kronos Incorporated . Note that although the following example shows two separate web server computers. as in the previous example.1 also supports placing the web server and application server on separate machines.Chapter 2 Workforce Timekeeper and other Labor and Scheduling products Separation. In this configuration. it calls server 3 on port 8080. potentially with a firewall in between. In this case. no multiple instances Workforce Timekeeper v6. outbound connections from the application server to the web server through the firewall are avoided by having inter-server communication use a port on the application server directly. if the application server on server 4 wants to talk to the application server on server 3.

two instances Workforce Timekeeper v6. you could have two separate web servers as shown below. and 8080 and 8081 for HTTP IPC. instance 2) Separation. (As before. instance 2) http://server3:8080/inst1/XmlService (IPC. instance 1) http://server4:8080/inst2/XmlService (IPC. As before. or a single web server with multiple connector configurations. in this example.1 can also support the previous configuration. because there are two application server processes.Sample configurations Example URLs: • • • • http://server1/INST1/applications/wtk/images/ foo. 85 . instance 1) http://server2/inst2/applications/wtk/foo. there could be two separate web server machines.jsp (dynamic content. or only one. the ports are 8009 and 8010 for the connector.gif (static content.) Again. but with multiple application server instances installed on the same machine. each must listen on a unique port.

Chapter 2 Workforce Timekeeper and other Labor and Scheduling products In this case. instance 2) http://server3:8080/inst1/XmlService (IPC. instance 2) 86 Kronos Incorporated .jsp (dynamic content.gif (static content. the WFCSERVER table contains: Web Server HTTPS host Name option name IPC IPC HTTPS host option name App URL prefix Web URL prefix IPC Port Context Inst1 Inst2 Server 3 HTTP or Server 1 HTTP HTTPS only Server 3 HTTP or Server 2 HTTP HTTPS only Server 3 8080 Server 3 8081 /inst1 /INST1 /inst2 /INST2 Example URLs: • • • • http://server1/INST1/applications/wtk/images/foo. instance 1) http://server3:8081/inst2/XmlService (IPC. instance 1) http://server2/inst2/applications/wtk/foo.

would not be available. The distribution is done “round robin. 87 . For more information about configuring an SSRS server. refer to Installing Workforce Timekeeper. Reports are queued for execution. The report executes. Reports If you use the advanced reporting functionality of Workforce Central v6. and batch processing on your main application servers (to make them as responsive as possible to real-time HTTP requests). With the exception of a dedicated Background Processor machine. or batch servers. you must have a Windows “companion server” to run nonJava technology such as reports. You can also run dedicated report servers. There is no weighting of report complexity or preferred servers supported. batch processing classes. For UNIX systems.1. Most of these services require the Workforce Central platform. report. you might choose to disable reports. and run these services instead on one or more separate servers that do not receive HTTP requests. dedicated Background Processor servers. or dedicated batch processing servers. the file is delivered from the server where the file is resident and is not passed between servers. etc. so the platform is installed on companion. the Background Processor. all other applications also need to be installed on these servers—otherwise the necessary report templates.Dedicating machines to certain functions Dedicating machines to certain functions Workforce Timekeeper supports several special-purpose server configurations. you can set up a dedicated SSRS server that provides the reporting engine for all application servers in your environment. producing a physical file that is stored on the server that executed the report request. The queue is stored in the database where the reports service retrieves the requests and allocates them to a server that runs reports. When the interactive user asks to view the report. For example.” where each server receives a request in turn.

Chapter 2 Workforce Timekeeper and other Labor and Scheduling products 88 Kronos Incorporated .

Chapter 3 Workforce HR/Payroll This chapter provides information about Workforce HR/Payroll and contains the following sections: • • • • • “Overview” on page 90 “System requirements” on page 91 “Reporting” on page 95 “Workforce HR/Payroll Solution Manager” on page 96 “Multiple instances in a Workforce HR/Payroll environment” on page 99 .

payroll engine. 90 Kronos Incorporated . • • • • You can choose a single-server or dual-server configuration: The configuration that is appropriate for your organization depends on many variables. and whether or not your organization plans to include Workforce Payroll. Dual servers—Web server installed on one computer and the payroll engine and database server installed on the another computer. Database server — Manages the Workforce HR/Payroll database Payroll engine — Processes all payroll-related functions Single server—Web.Chapter 3 Workforce HR/Payroll Overview Workforce HR and Workforce Payroll (referred to in this document as Workforce HR/Payroll) consists of three main components: • Web server — Provides the web browser user interface for the Workforce HR/Payroll administrative application and the Workforce Employee™ and Workforce Manager™ self-service application. including the number of employees and users. and database servers installed on one computer.

0 (Windows Server 2003) or v7.0 or later Microsoft .3 JRE 1. Datacenter. Small Business Server Editions Microsoft Windows Server 2008 (32-bit) JBoss 4. 7. service pack 1 — Standard. Datacenter. Enterprise. Datacenter.6.0_07 (1.0 (Windows Server 2008): • • • World Wide Web Server enabled SMTP Service enabled ASP. service pack 1 — Standard.System requirements System requirements Item Hardware Network connection Web browser Portal Virtualization Requirement See your Kronos representative. Small Business Server Editions Microsoft Windows Server 2008 (32-bit) Microsoft IIS v6.02 Other software • • Guide to Planning a Workforce Central Installation 91 . Small Business Server Editions Microsoft Windows Server 2003 (32-bit) R2 — Standard. Small Business Server Editions Microsoft Windows Server 2003 (32-bit) R2 — Standard.NET Framework 2. 100BASE-T connection for dual-server configurations recommended Microsoft Internet Explorer 6. Enterprise.0. Enterprise.5 Application server requirements1 Operating system • • • Application server Server JRE Microsoft Windows Server 2003 (32-bit).6) Web server requirements1 Operating system • • • Web server software Microsoft Windows Server 2003 (32-bit).0 Microsoft SharePoint 2007 ESX Server 3. Datacenter.NET must be installed for Windows Server 2003 Adobe Acrobat Reader 4. Enterprise.

NET framework if it is not present on the machine. service pack 1 — Standard. Enterprise. Small Business Server Editions Microsoft Windows Server 2008 (32-bit) Microsoft SQL Server 2005 with service pack 2 (32-bit) — compatibility level 80 only Microsoft SQL Server 2008 with service pack 2 (32-bit) — compatibility level 80 or 100 only Adobe Acrobat Reader 4.0 or later 1 2 Workforce Central automatically supports security and bug service packs specific to these operating systems. the Workforce HR/Payroll uninstall procedure does not remove. Small Business Server Editions Microsoft Windows Server 2003 (32-bit) R2 — Standard. NET. No new Workforce Central release is necessary to support these updates.Chapter 3 Workforce HR/Payroll Item Requirement Payroll engine and database server requirements1 Operating system • • • Database server software • • Other software • • • Microsoft Windows Server 2003 (32-bit).0 or later Microsoft. Datacenter.02 WinZip 7. if you want to remove it. Datacenter. you must do so manually. However. Workforce HR/Payroll automatically installs Microsoft .NET Framework 2. 92 Kronos Incorporated . Enterprise.

Important: Administrative users must have local administrator rights on their workstations.0.0.System requirements Administrative client workstation requirements Hardware CPU RAM Hard drive capacity Monitor Software Operating system1 • • • • • Web browser Client JRE Other software 1 Pentium II 400 Processor (minimum recommendation) 128 MB (minimum recommendation) 20 MB free disk space (minimum recommendation) • • SVGA high color (800 x 600) (minimum recommendation) Normal font size display (if you use large fonts. Small Business Server Editions Microsoft Windows Server 2003 (32-bit) R2 — Standard. Enterprise. some buttons are hidden) Microsoft Windows Server 2003 (32-bit). Guide to Planning a Workforce Central Installation 93 . Datacenter.6.6) Adobe Acrobat Reader 4. service pack 1 — Standard. Small Business Server Editions Microsoft Windows Server 2008 (32-bit) Windows XP Professional Microsoft Vista Microsoft Internet Explorer 6. 8. Enterprise.0_07 (1.0 JRE 1.0 or later Workforce Central automatically supports security and bug service packs specific to these operating systems. Datacenter. 7. No new Workforce Central release is necessary to support these updates.

Datacenter. Enterprise. Datacenter. 7.0.0 or later Microsoft Terminal Services supported on Windows 2000 Server with service pack 2 JRE 1.6) (Workforce Manager only) Workforce Central automatically supports security and bug service packs specific to these operating systems. some buttons are hidden) 20 MB free disk space (minimum recommendation) Microsoft Windows Server 2003 (32-bit). Enterprise.6.0 Adobe Acrobat Reader 4.0_07 (1. Small Business Server Editions Microsoft Windows Server 2003 (32-bit) R2 — Standard.Chapter 3 Workforce HR/Payroll Workforce Employee and Workforce Manager workstation requirements Hardware CPU RAM Hard drive capacity Monitor Software Operating system1 • • • • • Web browser Other software Optional component JRE 1 Pentium (minimum recommendation) • • • • Windows XP: 128 MB Windows Vista: 512 MB SVGA high color (800 x 600) (minimum recommendation) Normal font size display (if you use large fonts. service pack 1 — Standard. No new Workforce Central release is necessary to support these updates. Small Business Server Editions Microsoft Windows Server 2008 (32-bit) Windows XP Professional Windows Vista Microsoft Internet Explorer 6. 94 Kronos Incorporated .

Guide to Planning a Workforce Central Installation 95 .Reporting Reporting Workforce HR/Payroll uses Crystal reports as its reporting mechanism and does not use RDL or SSRS functionality.

Chapter 3

Workforce HR/Payroll

Workforce HR/Payroll Solution Manager
Solution Manager is the main interface for Workforce HR/Payroll configuration. It has two components: • • A graphical management console based on the Microsoft Management Console (MMC) framework A TCP/IP-based listener service (daemon), called the Workforce HR/Payroll IP Management Service (IPMS), that runs on all Workforce HR/Payroll servers to service remote configuration requests

All actual changes are made by the IP Management Service (IPMS). For tasks involving creating, deleting, and getting information about databases, the IPMS

96

Kronos Incorporated

Workforce HR/Payroll Solution Manager

uses the SQLDMO API to communicate with SQL Server. For upgrades and other changes to the content of a Workforce HR/Payroll database, the IPMS invokes BiDBWiz. Other changes involve changes to files or registry entries on the local machine. To edit the Workforce HR/Payroll configuration on a remote server, you must register the remote server with the Solution Manager GUI. Then, depending on the functions for which the server is responsible, the following actions are available: • Web servers – • Create and delete webs (virtual directories on a web server) — For Workforce HR/Payroll Administration, Self Service, and jobs sites. Create new database — Creates a blank database Backup/restore database — Similar to functions in SQL Server 2005 Management Studio, except that Solution Manager also fixes restored databases (see below). Change install code — Updates the Workforce HR/Payroll license. Build new database — Initializes a database from the Workforce HR/ Payroll .BAK file Copy database — Creates a blank database. Upgrade — Upgrades a Workforce HR/Payroll database to the latest version available on the database server. Fix restored database — Resets security permissions that may have been destroyed in a backup/restore cycle. Also drops users from the database who are not SQL Server users on the machine and creates or resets internally set user accounts. Resets the permissions of MSDB and MASTER database objects. Delete database

Database servers – –

– – – – –

– •

Application servers (payroll processing; usually on the same machine as the database server) – View legislative update logs.

Guide to Planning a Workforce Central Installation

97

Chapter 3

Workforce HR/Payroll

Solution Manager uses the command-line Visual Basic application (.exe) BiDBWiz to perform database operations on the local machine. BiDBWiz uses the Microsoft ADO API or the ISQL client program in order to send SQL to the RDBMS. It is installed on Workforce HR/Payroll database server machines only. BiDBWiz is driven by .ini files, which specify lists of SQL scripts to run. Different sections of the file can be run depending on the current Workforce HR/ Payroll database version number to accommodate patches. Script execution can be ordered so that dependencies are satisfied. The main functions of BiDBWiz are as follows: • Create a database backup file — A database backup file is created at build time and shipped with the application so that you do not need to process thousands of scripts at install time. Create an initialized database — A backup image is made and restored into an existing database. Then, BiDBWiz runs an upgrade on the database so that patches made since the backup was created are applied to the new database. Upgrade a database — Incremental changes are applied to bring a database up to the latest version on the machine. Any version of the Workforce HR/ Payroll database is upgradeable to the latest version, because BiDBWiz is driven by the .ini file that contains database changes for each major/minor release. BiDBWiz upgrades the database by comparing the database version that is stored internally in the database and the version that is stored in the Windows registry. Change install code (license) — Your installation code is updated if you purchased Workforce Payroll after you purchased and licensed Workforce HR.

98

Kronos Incorporated

but each instance is connected to a separate database. as explained in “Configuration Manager” on page 29. The most common use of multiple instances in a Workforce HR/Payroll environment is to have several instances of Workforce Central running on the same physical server.1 allows you to install multiple instances of the application on the same machine. The Configuration Manager utility lets you create. Guide to Planning a Workforce Central Installation 99 . A typical use of this configuration is separate instances and databases for training. or delete an instance of Workforce Central. modify.Multiple instances in a Workforce HR/Payroll environment Multiple instances in a Workforce HR/Payroll environment Workforce Central v6. testing. and production.

Chapter 3 Workforce HR/Payroll 100 Kronos Incorporated .

Chapter 4 Combined Workforce Timekeeper and Workforce HR/Payroll installation With Workforce Central v6.1. Workforce Device Manager. . Workforce Timekeeper and Workforce HR/Payroll can be installed on a single machine connected to a single database. Topics discussed in this chapter are: • • • • • • “Workforce Central platform in an integrated environment” on page 102 “Requirements for a combined environment” on page 103 “System requirements” on page 104 “Integrating Workforce HR/Payroll and Workforce Timekeeper” on page 105 “Data synchronization” on page 107 “Synchronizing data” on page 115 Note: Because Workforce Timekeeper is a prerequisite for a number of Workforce Central product that can all be installed at the same time. Workforce HR/Payroll sends these data changes to Workforce Timekeeper APIs. Workforce Integration Manager. Workforce Leave. Workforce Attendance. when a new employee is hired. references to Workforce Timekeeper in this chapter also include Workforce Scheduler. When Workforce HR/Payroll is running in an integrated environment with Workforce Timekeeper. the Workforce HR/Payroll system is considered the master. When events occur that might require Workforce Timekeeper data to change. Workforce Activities. Workforce HR/Payroll sends the employee’s demographic and other information to Workforce Timekeeper APIs that cause the same person to also appear in the Workforce Timekeeper database. Workforce Forecast Manager. Workforce Operations Planner. For example.

users can navigate between the Workforce HR/Payroll and Workforce Timekeeper applications without logging on a second time.1 also relies on the platform. primarily because it uses Process Manager as an integral component of its performance management and compensation management applications. The Workforce Central platform is only installed on a database server when the database server and the application server are the same physical machine. If you install the Workforce HR/Payroll Web Server on multiple machines. you must install the Payroll Engine and Database Server on the same machine as the database and the Web Server on the same machine as the Workforce Timekeeper application server and web server. the database can reside on a separate machine or on the same machine as the Workforce Central applications. you must also use network load balancing. If your database resides on a separate machine. You cannot configure Workforce Timekeeper to run with a separated web and application server. Workforce HR/Payroll v6. With an integrated Workforce HR/Payroll .Workforce Timekeeper environment. when you install Workforce HR/ Payroll. Other important points about an integrated Workforce HR/Payroll and Workforce Timekeeper environment are: • Workforce Timekeeper must be installed in a combined web and application server environment. • • • • 102 Kronos Incorporated . Workforce Timekeeper requires the Workforce Central platform for most of its functions.Chapter 4 Combined Workforce Timekeeper and Workforce HR/Payroll installation Workforce Central platform in an integrated environment When you install Workforce HR/Payroll and Workforce Timekeeper in an integrated environment.

Maintenance — Maintenance affects all Kronos applications.Requirements for a combined environment Requirements for a combined environment Requirements for a combined Workforce HR/Payroll . The database must be SQL Server 2005 or SQL Server 2008. you cannot install the Workforce Timekeeper web server and application server on separate machines. Because Workforce HR/ Payroll database queries are made directly from the web server (via . separation of the web and application servers on machines that include Workforce HR/Payroll do not provide security benefits.NET framework must installed on each server. The application server must be JBoss. if both machines use the same database. • No separation — In an integrated Workforce Timekeeper . it is applied to all Kronos servers.Workforce Timekeeper installation include the following: • Homogeneous servers — Each server in the your environment must be identical and run all of your Workforce Central applications. The Microsoft . When a service pack arrives from Kronos.asp and COM/.Workforce HR/ Payroll environment.NET components). You cannot install Workforce HR/Payroll on one machine and Workforce Timekeeper on another. • Guide to Planning a Workforce Central Installation 103 . The web server must be Microsoft IIS. System requirements — Combined Workforce Timekeeper and Workforce HR/Payroll installations require the following on each machine in your environment: – – – – – • The operating system must be Windows Server 2003 or Windows Server 2008.

6) TCP/IP Web server software Microsoft IIS v6. NET.NET framework if it is not present on the machine.0_07 (1. Small Business Server Editions Microsoft Windows Server 2003 (32-bit) R2 — Standard. Datacenter.Chapter 4 Combined Workforce Timekeeper and Workforce HR/Payroll installation System requirements If you are using both Workforce Timekeeper and Workforce HR/Payroll. and they must both be installed—along with the Workforce Central platform—on every machine in the environment (they cannot be separated). Enterprise.x. SQL Server 2008 • • Adobe Acrobat Reader 4. 2 Workforce HR/Payroll automatically installs Microsoft .NET must be installed for Windows Server 2003 Microsoft Internet Explorer 6.NET Framework 2. The database must be SQL Server. 104 Kronos Incorporated .0 (Windows Server 2008): • • • Client browser Database Other software World Wide Web Server enabled SMTP Service enabled ASP.0 (Windows Server 2003) or v7.0 or later Microsoft . Specific requirements are: Item Operating system1 Requirement • Microsoft Windows Server 2003 (32-bit).6. Datacenter. service pack 2+.02 installed on every machine 1 Workforce Central automatically supports security and bug service packs specific to these operating systems. the web server must be IIS. the Workforce HR/Payroll uninstall procedure does not remove. Enterprise.0 SQL Server 2005. service pack 1 — Standard. No new Workforce Central release is necessary to support these updates.3 JRE 1. Small Business Server Editions Microsoft Windows Server 2008 (32-bit) • • Application server Server JRE Network protocol JBoss 4. 7. However. the application server must be JBoss. you must do so manually. if you want to remove it.

1 products. scheduling. Workforce Guide to Planning a Workforce Central Installation 105 . Various Workforce HR/Payroll application pages provide a data entry interface to Workforce Timekeeper. This common data includes: • • • • • Employee badge numbers Employee personal information Labor management information Job and organization information (if organization mapping is enabled) Skills and certification information (if Workforce Scheduler is installed) Note: Workforce HR/Payroll v6.1 (timekeeping.Integrating Workforce HR/Payroll and Workforce Timekeeper Integrating Workforce HR/Payroll and Workforce Timekeeper Integrating Workforce HR/Payroll v6.1 with the time and labor components of Workforce Central v6. The integration of Workforce HR/Payroll and the time and labor components of Workforce Central consists of a combination of real-time application programming interfaces (APIs) and dedicated database views: • • A single database makes data easily accessible across applications. When you enter information on such pages. Real-time APIs handle the transfer of employee information from time and labor-specific pages in Workforce HR/Payroll to Workforce Central common database tables.1 can be integrated only with other Workforce Central v6. activities) enables you to use Workforce HR/Payroll to maintain a subset of data that is common across applications.

The information is then accessible to both applications. 106 Kronos Incorporated .Chapter 4 Combined Workforce Timekeeper and Workforce HR/Payroll installation Central APIs automatically update the appropriate Workforce Timekeeper database tables.

if Workforce Scheduler is installed (see “Skills and certifications” on page 112) Workforce HR/Payroll automatically updates the appropriate time and labor database tables using Workforce Central APIs. and primary accounts” on page 109) Job and organization information. and primary account information (see “Licenses. roles. Guide to Planning a Workforce Central Installation 107 .Data synchronization Data synchronization This section contains the following topics: • • • • • • • • “Scope of data synchronization” on page 107 “Terminology” on page 108 “Employee personal data” on page 108 “Licenses. and primary accounts” on page 109 “Jobs and organizations” on page 110 “Skills and certifications” on page 112 “Synchronization processor” on page 112 “Queue assistants” on page 113 Scope of data synchronization When Workforce HR/Payroll is integrated with the time and labor components of Workforce Central. profiles. profiles. profile. roles. the following data can be managed using Workforce HR/ Payroll: • • • • • Employee badge numbers A subset of employee personal information (see “Employee personal data” on page 108) License. role. if organization mapping is enabled (see “Jobs and organizations” on page 110) Skills and certification information.

Chapter 4

Combined Workforce Timekeeper and Workforce HR/Payroll installation

Terminology
Even though the same or similar concepts exist across Workforce Central products, some of the terminology varies between the products. The following table correlates the key integration-related terminology.
Workforce HR/Payroll Term employee position position organization type organization code employee skill skill code skill start date employee event of type certification certification event date compensation code attendance plan code Time and Labor Term job assignment job in an organizational map location type node in an organizational map person skill skill skill effective date certification certification grant date pay code accrual code

Employee personal data
In an integrated system, Workforce HR/Payroll stores the following basic employee personal information in Workforce Central platform database tables:
Employee ID First Name Middle Initial Last Name Nickname Hire Date Base Hourly Wage Telephone Number Address Type Street City State Postal Code Country

108

Kronos Incorporated

Data synchronization

Birth Date Employee Standard Hours Full Time Standard Hours Supervisor Full Name Telephone Contact Type

Email Type Email Address Employment Status Employment Status Effective Date

Note: In Workforce HR/Payroll, the Hours Per Week value on the Employee > Employment > Pay Status page maps to the Employee Hours value on the Leave Management time and labor page. In Workforce HR/Payroll, the Hours Per Year value divided by 52 on the Position Management > Position page maps to the Full-Time Hours value on the Leave Management time and labor page.

Licenses, profiles, roles, and primary accounts
In an integrated system, Workforce HR/Payroll stores the following license, profile, role, and primary account data in time and labor database tables:
License Types Pay Rule Wage Profile Worker Type Device Group Accrual Profile Schedule Group Schedule Rule Set (if Workforce Scheduler is installed) Pay Codes Profile (Manager Role) Work Rule Profile (Manager Role) Reports Profile (Manager Role) Organizational Group (Manager Role, if job and organization mapping is enabled) Job Transfer Set (Manager Role, if job and organization mapping is enabled) Schedule Group Profile Shift Template Profile Pattern Template Profile

Guide to Planning a Workforce Central Installation

109

Chapter 4

Combined Workforce Timekeeper and Workforce HR/Payroll installation

Activity Profile (if Workforce Activities is installed) Default Activity (if Workforce Activities is installed) Idle Time (if Workforce Activities is installed) Meal (if Workforce Activities is installed) Default Team (if Workforce Activities is installed) Login Profile Function Access Profile Display Profile

Availability Profile (if Workforce Scheduler is installed) Time Entry Method (Employee Role) Labor Level Transfer Set (Employee Role) Pay Codes Profile (Employee Role) Work Rule Profile (Employee Role) Job Transfer Set (Employee Role, if job and organization mapping is enabled) Primary Account Schedule Job List Seniority Dates (if job and organization mapping is enabled and Workforce Scheduler is installed) Pay Codes Profile (Manager Role)

Employee Group (Manager Role) Labor Level Transfer Set (Manager Role)

Jobs and organizations
When Workforce HR/Payroll is integrated with the time and labor components of Workforce Central, you can construct an organization tree in Workforce HR/ Payroll and share it with Workforce Central. This enables you to maintain job and organization information in one place. You can also specify that Workforce Central use its own organizational maps. In this case, organizational data is not shared between Workforce HR/Payroll and Workforce Central.

110

Kronos Incorporated

Note: Because all employees must be assigned to Workforce HR/Payroll positions. the system does not assign any employees to jobs in the time and labor organizational map.Data synchronization The following Workforce HR/Payroll system settings govern job/organization mapping: • • Workforce Timekeeper Organization Tree Workforce Timekeeper Job Labor Level Sharing an organization tree with Workforce Central is optional. Conversely. the system assigns all employees to jobs in the time and labor organizational map. Currently. If job and organization mapping is enabled. if you do not enable job and organization mapping. there is no way to assign some employees but not others to jobs in the time and labor organizational map. Workforce HR/Payroll stores the following job and organization data in time and labor database tables: Job Information Job Name Job Description Job Code Job Title Organization Information Change Date Location Number Parent Location Number Location Type Location Name Start Effective Date End Effective Date Description Labor Level Entry Labor Level Entry Name Labor Level Entry Description Job Status Sort Order Guide to Planning a Workforce Central Installation 111 . you can set up an integrated system without enabling this feature. if you enable job and organization mapping.

the following occurs: • If the information is current-dated. the update is immediately sent to the time and labor database tables.Chapter 4 Combined Workforce Timekeeper and Workforce HR/Payroll installation Skills and certifications If Workforce Scheduler is installed and integrated with Workforce HR/Payroll and Workforce Central. You must then assign skills and certifications to the appropriate employees. the update is immediately sent to the time and labor tables with an effective date of the current day. (Note that if the information is back-dated. event codes of type Certification. and employee skill and certification assignments using Workforce HR/Payroll. the update is immediately sent to the time and labor tables. and the time and labor tables can store the effective date.) If the information is future-dated. • 112 Kronos Incorporated . you can maintain skill codes. The change becomes effective on the designated date. When time and labor information is entered in Workforce HR/ Payroll. both the codes and employee attributes are stored in time and labor database tables. When this is complete. This information is stored in time and labor database tables. Maintaining skill and certification information involves two separate tasks: you must first populate the skill code table with skill codes and the event code table with events of type Certification. Workforce HR/Payroll stores the following skill and certification information in time and labor database tables: Skill Name Skill Effective Date Skill Expiration Date Skill Status Certification Name Certification Effective Date Certification Expiration Date Certification Number Synchronization processor A synchronization processor handles the transfer of information from Workforce HR/Payroll to time and labor database tables or Workforce Central platform database tables. If Workforce Scheduler is installed.

Data synchronization • If the information is future-dated. Synchronization processor system settings The following system settings determine how long entries stay in the synchronization processor queue. the update is placed in a queue and sent to the time and labor tables on its effective date. The HRIS manager can use the event log on the database server to investigate synchronization processor errors. • • Number of days to Purge Successful Transaction Number of days to Purge Error Transaction These settings enable items that require attention to remain in the queue longer than items that do not require attention. The synchronization processor periodically triggers a stored procedure to clean up the queue based on the current system parameter settings. Queue assistants Two queue assistants enable the HRIS manager to monitor the synchronization processor for errors: • • “System Queue Assistant” on page 114 “Employee Queue Assistant” on page 114 Guide to Planning a Workforce Central Installation 113 . but the time and labor tables cannot store the effective date. Even though the synchronization processor runs when an item is added to the synchronization processor queue. The SQL Enterprise Manager job must be set up to run the stored procedure sp_WTK_StartSyncProcess. it is recommended that the HRIS manager set up a scheduled job in SQL Enterprise Manager to start the processor early each morning to process requests that are to become effective that day.

To access the System Queue Assistant. You can view details of individual items in the form of XML files and delete individual items from the queue. the type of data to be updated. and an error description for items that could not be sent. select System > Queue Assistant in the Workforce HR/Payroll Administration navigation tree. To access the Employee Queue Assistant. transaction date and time for items successfully sent. and an error description for items that could not be sent. transaction date and time for items successfully sent. effective date. 114 Kronos Incorporated . You can view details of individual items in the form of XML files and delete individual items from the queue. effective date. date and time queued. The following information is shown for each item on the queue: item status. Employee Queue Assistant The Employee Queue Assistant shows items currently on the synchronization processor queue for a selected employee. you can place employee information for all employees in the queue to fully synchronize this information between Workforce HR/Workforce Payroll and Workforce Central. In addition. The following information is shown for each item on the queue: item status.Chapter 4 Combined Workforce Timekeeper and Workforce HR/Payroll installation System Queue Assistant The System Queue Assistant provides a view of all items currently on the synchronization processor queue. employee name and ID. select Employee > Workforce Timekeeper > Queue Assistant in the Workforce HR/Payroll Administration navigation tree. the type of data to be updated. date and time queued.

• • • • • Guide to Planning a Workforce Central Installation 115 . The APIs use this user name to move information between Workforce HR/Payroll and Workforce Timekeeper.Workforce HR/Payroll environment. Set up default labor management profiles initially. use the code “REG” (for regular pay) in both systems. Set up labor levels so that they represent GL accounts. the shift differential might be captured and reported as either “40 Regular and 40 Shift2” or “40 Regular 2. Do not use “REG” in one system and “REGULAR” in the other system. Assess the payroll GL account requirements of your accounting/payroll department. For example. This ensures that the employee position information is accessible in Workforce Timekeeper. you should be aware of the following implementation considerations: • The Workforce HR/Payroll user name (HRMSUSER) and password are automatically created when Workforce HR/Payroll is installed. For example. you must synchronize the data between the two systems when you install Workforce HR/Payroll v6. you must specify the new user name in the Labor Management API Login User Name system setting. Workforce HR/Payroll attendance plan codes must match Workforce Timekeeper accrual codes in order to successfully transfer accruals from Workforce HR/Payroll to Workforce Timekeeper. Although the process to synchronize data is described in detail in the Installing Workforce HR/Payroll and Workforce Timekeeper guide on the documentation CD. Make comparable compensation/pay codes the same in both Workforce HR/ Payroll and Workforce Timekeeper.1 and Workforce Timekeeper v6. then modify the information for individual employees as necessary. if an employee works 40 hours on Shift 2.” set up the Workforce Timekeeper pay code distribution to accommodate this.Synchronizing data Synchronizing data In an integrated Workforce Timekeeper .1 for the first time.” If the payroll department expects “40 Regular and 40 Shift2. If you change this user name. Determine how your payroll department captures and reports hours on pay stubs.

Workforce Timekeeper does not allow duplicate location types or codes in the same tree.Chapter 4 Combined Workforce Timekeeper and Workforce HR/Payroll installation • Workforce HR/Payroll accepts full-time equivalency (FTE) data based on ratios but not percentages. Editing and Deleting Menu and Menu Items” in Workforce HR/Payroll Administration Help. make all organization types and codes unique. Therefore. You can copy the relevant values from the Labor Management menu item (System > Self Service Settings> Self Service Editor > Role Editor tab > Employment Information > Labor Management). use only the Ratio FTE option. Workforce HR/Payroll does not display the labor account strings properly. if you change the way unspecified labor level entries are represented in labor account strings from a dash to some other character. In Workforce Timekeeper. • • • 116 Kronos Incorporated . in Workforce Timekeeper. do not change the way unspecified labor level entries are represented. When you set up an organization tree to send to Workforce Timekeeper. do not use the Percentage FTE option. Therefore. leave them as dashes. see “Adding. when entering FTE data in Workforce Timekeeper. For general instructions on creating an icon. The default Workforce Manager start page does not contain an icon for Labor Management.

In addition.Chapter 5 Licensing Workforce Central products You must license each Workforce Central product to enable it to support the functionality and capacities that you purchased with your system. This chapter contains the following sections: • • • • • • “Required licenses” on page 118 “Types of licenses” on page 120 “Licensing process” on page 122 “Licensing Workforce Timekeeper” on page 124 “Licensing Workforce HR/Payroll” on page 126 “Suite license interaction” on page 127 . the product license supports capacities or maximum number allowed for employees and managers. The type of license(s) assigned to each user defines the products available to the user and the scope of responsibility that the user can perform.

Chapter 5 Licensing Workforce Central products Required licenses If you are installing Workforce Central products for the first tim. A v6. you must acquire the applicable licenses from Kronos before you start the installation process. 118 Kronos Incorporated . administrative. Upgrading from v5.1 licenses before you start the installation procedure. • • • • • • • • • • • • • Workforce Timekeeper Workforce Scheduler Workforce Forecast Manager Workforce Operations Planner Workforce Leave Workforce Attendance Workforce Activities Workforce Integration Manager Workforce Record Manager Workforce Accruals Workforce Employee Workforce Manager Workforce Tips & Tokes Note: Workforce Device Manager does not require a separate license.2 If you are upgrading from v5.2 or v6. you must acquire the applicable v6.2.0.1 license is required for each product that you purchase. Product licenses also support capacities for the maximum number of employee. the licensing requirements vary depending on the version you are upgrading from. or manager users that are allowed. If you are upgrading from v5.

1.Required licenses Upgrading from v6. you must acquire a Workforce Integration Manager license. • Workforce HR/Payroll requires that you enter the license serial number and installation code during the installation procedure. Guide to Planning a Workforce Central Installation 119 . If you are installing Workforce Integration Manager.0: • • New licenses are not required to upgrade your current products. The applications in the Workforce Timekeeper installation kit do not require you to enter the license number during the installation procedure.0 If you are upgrading from v6. Workforce Connect licenses are not valid in v6. New licenses are required if you are adding a new product (such as Workforce Scheduler or Workforce HR/Payroll) or changing the employee or user capacities that the system allows.

you are granted one or more of the following employee-based product licenses: • • • • • • Workforce Timekeeper Workforce Accruals Workforce Scheduler Workforce Activities Workforce Integration Manager Workforce Device Manager 120 Kronos Incorporated . • Product — Allows you to purchase the rights for either a site or a number of people to access the overall functionality of one or more Workforce Central products. such as Workforce Timekeeper. There are two types of interactive licenses: – – Manager or Supervisor access license Employee access license • Suite product licenses Depending on the Workforce Central products that you purchase. Interactive — Allows you to purchase the rights for individual users to access the Workforce Central suite and to use the features of the products. Workforce Scheduler. or Workforce Activities. Workforce Central supports two main categories of licenses.Chapter 5 Licensing Workforce Central products Types of licenses The Workforce Central suite has several implementations to ensure that each product within the suite is properly licensed. Workforce HR/Payroll.

but may have both. – Any user of the Workforce Central suite must have at least one of the above interaction licenses. an employee who has a Workforce Manager license is not required to have additional product licenses. The functions that are available depend on the product licenses that have been installed. • Workforce Manager — The Workforce Manager license controls a user’s ability to access the Workforce Central suite and use the available manager functions. The employee self-service functions that are present depend on the products that have been purchased and for which employees they are licensed. – For Workforce Timekeeper. A person cannot log on to the Workforce Central suite without at least one of these licenses. For Workforce HR/Payroll. if you install both Workforce HR and Workforce Timekeeper. Guide to Planning a Workforce Central Installation 121 . self-service functions include all employee roles functions in Workforce HR and all employee time entry and reporting functions in Workforce Timekeeper. employees must split their role license into two distinct licenses. An employee who has a Workforce Employee license must also be assigned a suite product license. one for Workforce Employee and the other for Workforce Managers.Types of licenses Suite interaction licenses Suite interaction licenses control the ability of users to interact within the Workforce Central suite. Workforce Employee licenses can access Workforce Timekeeper with either a Java or HTML user interface. Workforce Accruals. There are two types of interaction licenses: • Workforce Employee — The Workforce Employee license controls a user’s ability to use all employee self-service functions available. Workforce Scheduler. For example. and Workforce Record Manager.

Verifying license information After you generate license files and install a Workforce Central application. you must also copy the new license to this folder. An existing feature license for the same product as long as the version within the license files are the same. This means that if you add to your license level to increase the number of employees licensed for a product. An incremental license increments in the following circumstances: • • Any incremental license for the same product as long as the version within the license files are the same.1 products. you only need to add the new license to the \Kronos\wfc\licensing folder. you should generate the applicable licenses on the Windows companion server first and then copy the licenses from the Windows machine to the UNIX machine. Log on to the Workforce Central system by entering the following in a browser: http://ServerName/wfc/logon where ServerName is the name of your web server. You should receive a license authorization number in an e-mail from Kronos when your licensed software is processed and completed. Upgrading license levels Workforce Central licenses are incremental. you must copy your product licenses to the following folder on all Workforce Central machines in your environment: \Kronos\wfc\licensing If you later add a product. After you install Workforce Central v6. 122 Kronos Incorporated .Chapter 5 Licensing Workforce Central products Licensing process A license authorization number is required to generate a license file for your software. you can verify the license information in the following way: 1. Note: If you are installing Workforce Timekeeper on a UNIX machine.

The following is an example listing of products and licensing information you might see: The Limit values represent the employee and manager capacities for each product and are controlled by the product’s license file that you generated. Guide to Planning a Workforce Central Installation 123 .Licensing process 2. These values should match the maximum number of employee licenses that you purchased. Specify that you are having trouble generating your licenses from the Kronos Licensing web page. click Setup. contact Kronos by e-mail at support@kronos. Contact information for licensing problems If you have problems with the licensing instructions.com. or call your local Kronos office or Kronos authorized dealer. Click the Licenses tab. and then select System Information from the System Configuration box. 3. 4. Log on to Workforce Central. From upper-left side of the Workforce Central workspace.

Chapter 5 Licensing Workforce Central products Licensing Workforce Timekeeper The Workforce Timekeeper v6. copy all licensing files to the \Kronos\wfc\licensing folder. you must manually copy all of the license files to each application and web server. Each product or product area may also choose to provide additional enforcement criteria for its license type. If you install Workforce Timekeeper on more than one server. Therefore. The following are special considerations for common Workforce Timekeeper configurations: • Multiple servers — Every server in your environment must include all license files in the Kronos\wfc\licensing directory.1 installation programs do not deliver a product license. you cannot enter people records into your system.1 by uninstalling the earlier version of Workforce Timekeeper. you must copy all licensing files to a temporary folder before you upgrade. The database is also used to count the number of licenses assigned for a seat-based model. for example). Although you can complete the installation process and start configuring your system without a license. When the upgrade is complete. the database. • 124 Kronos Incorporated . Upgrading — When you upgrade to v6. The platform interacts with the FlexLM manager to obtain the maximum allowed licenses by type and with the database to link the FlexLM entry to a type and model. properties and FlexLM software to implement the validation and assignment of licenses. Therefore. The Workforce Timekeeper licensing functionality uses plug-ins. Earlier versions of Time & Labor and Scheduling products may have placed licenses in the following folder: \Kronos\wfc\applications\xxx\licensing where xxx is the 3-character abbreviation of the application—wtk or wfs. all licensing directories are removed. The basic license handling is performed by the Workforce Central platform. you should obtain your license files early in the installation process.

1.Licensing Workforce Timekeeper With Workforce Central v6. log on to the UNIX server and copy the license file or files that you created for the Windows companion server to the UNIX server using FTP: cd /usr/kronos/wfc/licensing put filename.lic Repeat this for each license file. • UNIX installations — If you are installing Workforce Timekeeper on a UNIX machine. these individual application licensing folders have been eliminated and you must manually move all licensing files to \Kronos\wfc\licensing. Guide to Planning a Workforce Central Installation 125 .

The e-mail includes a serial number and an installation code. Workforce HR/Payroll does not use the FlexLM software to implement the validation and assignment of licenses. however. The Workforce HR/Payroll installation program requires you to enter this information before you can install the product.Chapter 5 Licensing Workforce Central products Licensing Workforce HR/Payroll You will receive the license authorization information in an e-mail after Kronos ships your order. a license called hrdefault.lic is delivered to the Kronos\wfc\licensing folder. This platform license is not an interactive license and is not be sent to Workforce Timekeeper or the platform as part of an employee request. 126 Kronos Incorporated . Unlike Workforce Timekeeper. but it must be present in the Kronos\wfc\licensing folder in the platform in order for an employee to be added to the platform. When you install Workforce HR/Payroll.

If Workforce HR/ Payroll does not have an interactive user component (employee self-service). this person must have a Workforce Timekeeper manager license as well.Suite license interaction Suite license interaction Manager and employee licenses are shared across the suite. Workforce HR/Payroll does not implicitly set licenses if Workforce HR/Payroll employee self-service is not installed. An employee in Workforce Timekeeper must also have an employee interactive Workforce Timekeeper license. As the following table shows. Licenses can be accessed either explicitly or implicitly: • • Explicit selection of a license is when a user navigates to the Profile control and selects the License check box. it should not set license information implicitly. This means that if a person is a manager in Workforce HR/Payroll. Manager License Scenario Workforce HR/Payroll only Employee self-service not installed Employee self-service installed No Yes No No No Yes No No Implicit Explicit Employee License Implicit Explicit Workforce HR/Payroll and Workforce Timekeeper Employee self service not installed Employee self service installed No Yes Yes Yes No Yes Yes No Guide to Planning a Workforce Central Installation 127 . Employee and manager licenses are interactive licenses. Implicit selection of a license means that an action in Workforce HR/Payroll causes a suite-wide license to be turned on or off for a particular employee.

Chapter 5 Licensing Workforce Central products Additional points to consider include the following: • Actions that implicitly turn on or off an employee license include the following: – – • When you hire an employee.). When you terminate an employee. an employee license is assigned to the employee. the employee license assignment is removed. Assigning employee A to report to employee B causes employee B’s manager license to be activated (if it is not already activated). This can happen when a single employee’s supervisor is changed or during a Mass Supervisor Change function. the license information for each employee who should have the manager license turned on or off is updated. However. a person can have a manager license in Workforce Timekeeper and not be a supervisor in Workforce HR/Payroll. This can also happen when a supervisor’s last employee is terminated or when the last employee now works for someone else (transfer. Actions that implicitly turn on or off a manager license include the following: – – – • When Workforce HR/Payroll and Workforce Timekeeper are both installed. this person must also have a manager license in Workforce Timekeeper. etc. If Workforce HR/Payroll self-service is installed and a person is a manager in Workforce HR/Payroll self-service. if HR self-service is not installed. • 128 Kronos Incorporated . When the “Change Supervisor” control is used to update a group of employees’ supervisor. Removing all employees who report to an employee with a manager license removes the employee’s manager license (unless the license has been explicitly turned on). employee and manager license information is sent as a part of every employee synchronization request. This is to maintain the manager license enforcement across the suite. promotion.

Typically. and data integrity. Public key cryptography and digital certificates are the basis for the security features of SSL. you can configure your server to use HyperText Transport Protocol Secure (HTTPS). HTTPS communication — HTTPS is simply the HTTP protocol secured with SSL. much of the data between users and the system is text-based and. therefore. Security-sensitive data such as user name and password are transmitted “in the clear” when using HTTP without SSL. a different port (port 443 instead of port 80 for HTTP) is used by the web server to listen for HTTPS communication. “Implementing SSL with Workforce Central” on page 130 “General considerations” on page 131 “SSL secured data paths” on page 132 “Certificates. It transmits data unencrypted. keys. SSL provides server authentication (and optional client authentication). With HTTP. easily readable. If you require greater security.Chapter 6 SSL security considerations The default communication method that Workforce Central uses is HyperText Transport Protocol (HTTP). which uses Secure Sockets Layer (SSL) to encrypt the data. privacy. Specific characteristics of each protocol include the following: • HTTP communication — HTTP is the primary communication protocol of the Web. and credential stores” on page 133 “SSL and Workforce HR/Payroll” on page 136 “SSL and Workforce Timekeeper” on page 137 “Configuring Workforce Central to use an SSL terminator” on page 138 • This chapter contains the following sections: • • • • • • • .

3. if you install Workforce Timekeeper in a typical environment. Install your Workforce Central application. you only need to provide the key and certificate files.Chapter 6 SSL security considerations Implementing SSL with Workforce Central In general. the Workforce Timekeeper installation program configures SSL automatically. If you install Workforce Timekeeper in a custom environment. This chapter provides background information and describes how to prepare for SSL before you install Workforce Central applications. 2. The actual configuration instructions are included with specific application installation documentation. 130 Kronos Incorporated . Acquire SSL key and certificate files. the process is more manual. For example. Configure your Workforce Central application for SSL. The complexity of these steps depends on your specific Workforce Central configuration and requirements. using SSL with Workforce Central is a three-step process: 1.

may require installation of certificates on all web browsers used with Workforce Central. depending on certificate choices. any password compromise resulting from the use of the non-secure system would allow access when using the SSL-protected system. you should evaluate the appropriate options. Greater configuration complexity — SSL configuration involves additional steps. Attempting to configure SSL and non-SSL servers in a multi-server environment is complex and may be difficult to manage. Multiple servers — If you use multiple servers and choose to use SSL. These procedures are potentially error prone and. If two servers are configured to use the same database (and thus have the same set of users). you should consider the following before you implement an SSL environment: • Network performance — SSL imposes a significant processing overhead on network communication. including the possible use of SSL hardware devices to offload Workforce Central servers. you must use SSL for all the servers in your environment. A primary benefit of using SSL with Workforce Central is to protect passwords when logging on to the system. Evaluate all impacts carefully before undertaking the implementation of SSL security. for the following reasons: – – Mixing secure and non-secure systems lowers the security of the combined systems to non-secured status. including the generation and installation of certificates. Kronos does not support mixing SSL and non-SSL servers in your Workforce Central environment. Depending on your particular security and scalability needs. • • – Guide to Planning a Workforce Central Installation 131 .General considerations General considerations Regardless of the Workforce Central application that you are installing.

The LDAP over SSL combination is known as the LDAPS protocol. and others. Currently. which can be used check the identity of any web server that is secured with SSL certificates issued by those same roots. and devices User logons that are configured to use an LDAP directory for authentication require password transmission between the Workforce Central server and the LDAP server. SSL is supported by all web browsers supported with Workforce Central 6. This communication can also be protected with SSL. Application servers can also contact other application servers using SSL for tasks such as executing events or running reports.1.Chapter 6 SSL security considerations SSL secured data paths The following data communication paths within Workforce Central can be secured with SSL: • Web browser to web server — This is the most commonly used communication path. Well known Certificate Authorities (CA) include Verisign. • Workforce Central application server to LDAP directory server — SSL-secured Lightweight Directory Access Protocol (LDAP) communication is also supported with Workforce Central v6. these SSL clients do not authenticate the server’s identity with trusted certificates. Web browsers are preconfigured with root certificates. services. much as HTTP over SSL is HTTPS. Workforce Central clients to web server or application server — Workforce Central components can use SSL to protect communications with the server. With LDAP. Equifax. Web browsers need to have or obtain trusted certificates to properly authenticate the web server.1. Thawte. a directory server runs on a host computer and various client programs that understand the protocol can log on to the server and look up entries. • 132 Kronos Incorporated .

Certificates, keys, and credential stores

Certificates, keys, and credential stores
Certificates can be obtained in a variety of ways. For testing, it is common to generate self-signed certificates. These certificates are easy to create and do not require an external certificate authority (CA), but in general, they are less secure than certificates signed by a CA. When configuring a web server for SSL, an additional consideration is the option to use certificates that are signed by root certificates that are “pretrusted” by popular browsers. The root certificates are maintained by well known public CAs, and by virtue of being preinstalled in browsers, they eliminate the need for browser users to import new roots, or to be confronted by warnings about untrusted certificates. Public CAs are typically accessible online. You generate certificate requests locally, then use a web site or e-mail to transmit the request to the CA for signing. You then copy the signed certificate to your target server and configure it for use. Because the Workforce Timekeeper installation program requires that you identify the location of the SSL key and certificate files, you should obtain the required files before installing Workforce Timekeeper. Methods to obtain these files before the installation include: • OpenSSL toolkit — OpenSSL is an open source toolkit for SSL that includes tools for managing keys and certificates. You can download the OpenSSL toolkit from: http://www.openssl.org/related/binaries.html The CA.sh or CA.pl certificate authority scripts are an easier-to-use interface for using OpenSSL as a certificate authority. • Java Keytool — The Java Keytool utility enables you to administer your own public/private key pairs and associated certificates for use with SSL. It also allows you to store the certificates of your communicating peers. Keytool stores the keys and certificates in a keystore or truststore: – Keystores — Used to store keys and certificates for Java-based SSL servers, like the JBoss application server. Keytool can generate keys and certificate requests and then import the signed certificate into the keystore.

Guide to Planning a Workforce Central Installation

133

Chapter 6

SSL security considerations

Truststores — Used by Java-based SSL clients such as application servers that initiate communication with other servers or LDAP directories. With basic forms of SSL, the client only needs to verify the certificate presented by the server. The truststore holds certificates used to perform this verification. Keytool is used to import the root certificates or server certificates of those servers that should be trusted.

IBM Keyman — Keyman is an IBM tool for managing credential stores. It is not needed to configure Workforce Central for SSL. It can be useful if you already have certificates in a file format that Keytool or OpenSSL do not support. For more information: http://www.alphaworks.ibm.com/tech/keyman/download

If you cannot obtain the key and certificate files before you install Workforce Timekeeper, you can install blank (empty) files and replace them with the correct files after you install Workforce Timekeeper by using the OpenSSL toolkit or Keytool that are delivered by the Workforce Timekeeper installation program: • OpenSSL toolkit is located in \Kronos\wfc\bin\openssl.exe. The CA.sh or CA.pl certificate authority scripts, however, are not provided; you must get them from an OpenSSL distribution. Keytool is located \Kronos\jre\bin\keytool.exe.

Certificates
The following types of certificates can be used with Workforce Central: • Self-signed certificate — Self-signed certificates are generally used in testing, because they are easier to generate, and security requirements are low. Both Java keytool and openssl can be used to generate self-signed certificates. Certificate Authority signed certificate — A Certificate Authority (CA) is generally used in production environments, for several reasons: – Stronger security — Unlike self-signed certificates, signing is controlled by a central authority that can require minimum standards of identification before issuing certificates. Hierarchical trust — Hierarchical Trust provides scalability. When a large number of servers use certificates issued by the same Certificate

134

Kronos Incorporated

Certificates, keys, and credential stores

Authority, only the single CA root certificate needs to be trusted by clients. This avoids the N*N certificates that would be configured (for N servers) with direct trust—not using a CA. – Public roots — Certificates can be purchased from well known public Certificate Authorities. These certificates are trusted by browsers by default, so no trust configuration is necessary at the client.

Certificate chains — A server that uses a certificate signed by a Certificate Authority is using a certificate chain of two certificates: 1. The CA’s self-signed root certificate 2. The server SSL certificate An arbitrary chain of trust can be created by CAs that issue other CA certificates, and so on. Trust is verified in any given certificate by verifying that it was signed by the CA certificate that issued it. An SSL server certificate is validated by verifying each link in the chain, starting at the server certificate and working up the chain to the root certificate (which must be trusted implicitly).

Note: Do not use SSL certificate key lengths larger than 4096 bits. This is the maximum supported by Java Cryptography Extension 1.5, which is used by Workforce Central v6.1.

Credential stores and keys
Credential stores are repositories for user credentials to be used during the user authentication transaction. The keys found in SSL credential stores are usually RSA public or private keys, although it is possible to use other public key systems such as DSA. When generating a certificate request, a matching public and private keypair must be generated. The private key is stored in the credential store and the public key is included in the certificate request. When the request is signed and then imported into the credential store, the public key in the signed request must match the private key already in the credential store. With Keytool, they must match or the import will fail, but even with Apache/OpenSSL key and certificate must match for SSL to function.

Guide to Planning a Workforce Central Installation

135

and then configure Workforce HR/ Payroll for SSL. acquire the key and certificate files. which means that you can install Workforce HR/ Payroll. Refer to one of the Workforce HR/Payroll scenarios (such as Install HR-Payroll or Upgrade HR-Payroll) within the Workforce Central installation documentation for instructions on configuring Microsoft IIS for SSL for use with Workforce HR/ Payroll. 136 Kronos Incorporated .Chapter 6 SSL security considerations SSL and Workforce HR/Payroll The Workforce HR/Payroll installation program does not require you to identify the SSL key and certificate files.

The LDAP over SSL combination is known as the LDAPS protocol. Microsoft IIS. Refer to the Workforce Timekeeper installation documentation for instructions on configuring SSL interprocess communication for JBoss.SSL and Workforce Timekeeper SSL and Workforce Timekeeper Because Workforce Timekeeper v6. – • Between application servers — Workforce Timekeeper v6.1 supports the ability to separate the web server and application server.1 supports SSL implementations for JBoss applications servers. and IBM HTTP Web Server require manual configuration for SSL when used with preinstalled JBoss application servers. This communication can also be protected with SSL. the following data paths can be secured with SSL: • Between the browser and web server — Workforce Timekeeper v6. Guide to Planning a Workforce Central Installation 137 . • Between application server and LDAP directory server — User logons that are configured to use an LDAP directory for authentication require password transmission between the Workforce Central server and the LDAP server. Refer to Installing Workforce Timekeeper for instructions on configuring an LDAP directory server for use with JBoss. Custom installation — Apache.1 supports web server SSL implementations for typical and custom installations: – Typical installation — Although you must supply the appropriate certificate and key files. much as HTTP over SSL is HTTPS. the Workforce Timekeeper installation program automatically configures Apache or Microsoft IIS with JBoss.

communication. b. click the Security tab. you can leave this setting blank.ssl. 138 Kronos Incorporated . select the Web & App Server tab.webserver. Click Save. site. Because you installed Workforce Timekeeper in non-SSL mode. you must change the following settings from http to https: site. an SSL handshake occurs and SSL generates bulk encryption and decryption for each read-write. From the System Settings workspace.host — Enter the name of the external SSL terminator device. site. Install Workforce Timekeeper in non-SSL mode as described in Installing Workforce Timekeeper.port — Enter the port number used by the SSL terminator device.security.protocol — Change this setting to https. If using the default SSL port 443. If you use an SSL terminator in your Workforce Central environment. click Setup. When Workforce Timekeeper is up and running: a. site.webserver. so that the web server does not have to perform decryption and the burden on its processor is relieved.applet. From the System Settings workspace. e.termination.Chapter 6 SSL security considerations Configuring Workforce Central to use an SSL terminator When an SSL connection is established.security. Log on to Workforce Timekeeper. you must configure Workforce Central to recognize the device properly: 1. An SSL terminator decrypts the SSL-encrypted data and then sends it to the web server in an unencrypted state.security. Because the performance cost of this SSL handshake can be significant.termination. d. c.ssl.communication. some companies install an SSL terminator device.ssl. From the upper-right corner of the workspace.protocol — Change this setting to https. 2.termination.on — Set to true. and then select System Settings from the System Configuration box. and edit the following settings: site.

Stop and restart Workforce Timekeeper. 3. you would enter: https://XYZ11/wfc/logon Guide to Planning a Workforce Central Installation 139 . if the SSL terminator name is XYZ11. The logon URL is: https://SSL_terminator/instance_name/logon For example. Click Save. you will access Workforce Timekeeper from the SSL terminator device instead of from the web server.Configuring Workforce Central to use an SSL terminator f. 4. After you make these changes and Workforce Timekeeper restarts.

Chapter 6 SSL security considerations 140 Kronos Incorporated .

This chapter describes prerequisites and provides a number of preinstallation worksheets that can streamline the installation process. you should collect all the information that is required by the installation program.Chapter 7 Preinstallation requirements and checklists Before you start installing Workforce Central products. Specific topics include: • • “Preinstallation requirements” on page 142 “Preinstallation worksheets” on page 145 .

4. enter the appropriate information for your environment and click Connect. 5.” on page 89 are met. which is usually one of the following: – – 1. right-click the server name. Close any Windows or DOS applications. The database must be SQL Server 2005 or SQL Server 2008. 2. “Workforce HR/Payroll. From Management Studio. Basically.Chapter 7 Preinstallation requirements and checklists Preinstallation requirements The the preinstallation requirements vary depending on whether you are installing or upgrading Workforce HR/Payroll only. One machine with the application and database installed One machine with the application and another with the database Make sure all users are logged off the servers that you plan to use. or combined Workforce HR/Payroll and Workforce Timekeeper. you must do the following before you start the Workforce HR/Payroll installation program: • Ensure that the system requirements as outlined in Chapter 3. Select Start > Programs > Microsoft SQL Server > SQL Server Management Studio.NET installed. c. 3. Verify that the SQL Server authentication is set up for mixed mode—SQL and Windows authentication—on all servers: a. select Properties. Understand the configuration that you will be setting up. • Back up your servers. Disable virus scan software to reduce installation time. In the Connect to Server dialog box. b. you need at least one computer running Windows Server 2003 or Windows Server 2008 with Microsoft IIS and Microsoft . 142 Kronos Incorporated . Workforce Timekeeper only. Workforce HR/Payroll If you are installing Workforce HR/Payroll without Workforce Timekeeper.

Close any Windows or DOS applications. Windows authentication is the default setting:. 5. Workforce Timekeeper logons— Guide to Planning a Workforce Central Installation 143 . 7. Disable virus scan software to reduce installation time. “Workforce Timekeeper and other Labor and Scheduling products. 6. Select Security from the left side of the Server Properties workspace. 4. AIX) JBoss application server: installed with the Workforce Timekeeper installation program or preinstalled Web server: Apache or Microsoft IIS Secure Socket Layer (SSL) Combined or separated installation Multiple instances 3. Ensure that the system requirements as outlined in Chapter 2. Understand the configuration that you will be setting up: – – – – – – Operating system: Windows or UNIX (Solaris. Back up your servers.” on page 35 are met. Verify that the SQL Server authentication is set up for mixed mode—SQL and Windows authentication—on all servers. 2.Preinstallation requirements d. Make sure all users are logged off the servers that you plan to use. and then click SQL Server and Windows Authentication mode. you must do the following before you start the Workforce Timekeeper installation program: 1. Workforce Timekeeper If you are installing Workforce Timekeeper.

and then click SQL Server and Windows Authentication mode. Windows authentication is the default setting:.Chapter 7 Preinstallation requirements and checklists TKCSOWNER. From Management Studio. select Properties. enter the appropriate information for your environment and click Connect. and KRONREAD—all require SQL Server authentication: a. 144 Kronos Incorporated . In the Connect to Server dialog box. SUPRKRON. right-click the server name. c. Select Security from the left side of the Server Properties workspace. Select Start > Programs > Microsoft SQL Server > SQL Server Management Studio. b. d.

Keep these documents in a secure location. Caution: These worksheets include entries for system passwords. you should complete the following worksheets and refer to them during the installation procedure. Guide to Planning a Workforce Central Installation 145 .Preinstallation worksheets Preinstallation worksheets Because the Workforce Central installation programs require you to enter specific information about the database and the application server. See your system administrator if you need help locating this information.

and database on same machine) Dual server (web server on one machine and Payroll engine and database on another machines) Select one of the following: Single server Machine name: __________________________ Dual server Web server name: __________________________ Database server name: __________________________ Licensing information The product serial number and product installation code was sent to you in an e-mail message when your product was shipped. Payroll engine. enter the domain: address. If you use HTTPS. you must HTTPS also enter the fully qualified domain or IP If HTTPS. Enter the following information: Serial number: _________________ Installation code: _______________ • Communication protocol Select one of the following: Workforce HR/Payroll can run with either HTTP or HTTPS communication HTTP protocol. 146 Kronos Incorporated . Password:____________________ Instructions for setting up this account are included in the installation instructions. __________________________ Required accounts and logon information HRPayrollService A Windows domain user account called account Enter the following information: HRPayrollService is used when User name: ___________________ installing Workforce HR/Payroll.Chapter 7 Preinstallation requirements and checklists Workforce HR/Payroll preinstallation worksheet Dialog box Description Information to enter General Workforce HR/Payroll information Type of installation You can install either of the following: • Single server (web server.

The default port number for SQL Server is 1433.Preinstallation worksheets Dialog box Description Information to enter Enter the following information: Password:____________________ HRMSSelfService You must enter a password for these two HRMSLogging database accounts during the installation accounts procedure. Enter the database name: _____________________________ Port number Enter the port number:___________ Enter the following information: User name:____________________ Password: ____________________ SQL Server system You must enter the SQL Server system administrator logon administrator logon (such as sa) during information the installation procedure. Database information Database name The installation program will create a database if one does not exist or you can use an existing Workforce HR/Payroll database. although you can use a different one. and (if applicable) standalone Solution Manager. You must use the same password for both accounts whenever you install any Workforce HR/Payroll application including the Payroll engine and database. Guide to Planning a Workforce Central Installation 147 . web.

Note. but you can change this. Select the licensed products you are installing from the list in the next column. however. and IIS web server. Workforce Timekeeper is installed in the C directory.Chapter 7 Preinstallation requirements and checklists Workforce Timekeeper installation worksheet Dialog box Description Information to enter General information Destination By default. Select one of the following: Typical Custom • 148 Kronos Incorporated . Custom — An installation that uses a preinstalled JBoss application server. regardless of separation or multiple instances. that you must have applicable license files to use these products. Enter the directory name where Workforce Timekeeper will be installed: ____________________________ Products to install The Workforce Timekeeper installation program allows to install additional Workforce Central products. you must select one of the following types of installation environments: • Typical — An installation that includes any combination of JBoss application server. Workforce Timekeeper Workforce Scheduler Workforce Forecast Manager Workforce Operations Planner Workforce Leave Workforce Attendance Workforce Activities Workforce Device Manager Workforce Integration Manager Process Designer Interface Designer Type of installation environment During the installation. Apache web server. A custom installation requires a significant amount of manual configuration.

you must use the fully qualified domain names: Enter the fully qualified domain name of the application server: _____________________________ Enter the fully qualified domain name of the web server: _____________________________ Guide to Planning a Workforce Central Installation 149 .Preinstallation worksheets Dialog box Setup type Description Information to enter During the installation. identify the location of the certificates and key files: __________________________ IIS (HTTP) IIS (HTTPS) If IIS-HTTPS. The Workforce Timekeeper installation program will install: • • Apache – regular mode (HTTP) Apache – secure mode (HTTPS). which requires secure-mode certificate and key files You can also use the following web server. you must select whether Select one of the following: you are installing: Combined web/application servers • The web server and application server combined on a single machine Separated web server and • A separate web or application server application server The type of web server software. this is the name of the Enter the AJP connector port: Windows companion server. enter the fully qualified name or IP address of the application server: _________________________ Web server information Application server name and AJP connector port If you are installing a separate web server. but they are not installed by the Workforce Timekeeper installation program: • Microsoft IIS – regular mode (HTTP) • Microsoft IIS – secure mode (HTTPS) You must install these applications (and SSL certificates if applicable) before you install Workforce Timekeeper. you Enter the application server machine name: must enter the name of the application server machine and the AJP connector port (which is _____________________________ 8009 by default) For a UNIX installation. _____________________________ Fully qualified If you are using SSRS advanced reporting domain names functionality. Select one of the following: Apache (HTTP) Apache (HTTPS) If Apache-HTTPS.

If you are using a different port number. The default is 1344 for SQL Server and 1521 for Oracle. This machine will function as a dedicated Background Processor machine. Information to enter Select one of the following: Workforce Timekeeper application server only Workforce Timekeeper BGP Server Only Workforce Timekeeper with BGP (Single Server) • • Database platform Workforce Timekeeper supports Oracle and SQL Server databases. Workforce Timekeeper with BGP (Single Server) — Installs Workforce Timekeeper application server with the Background Processor threads enabled.Chapter 7 Preinstallation requirements and checklists Dialog box Background Processor Description The installation program enables you to select how you want the Background Processor threads enabled on the application server. If you are using Oracle: Are you using multi-schema? Yes No Select the version: Oracle 10G Release 2 Oracle 11G SQL Server 2005 SQL Server 2008 Database server name Database port for JDBC Connection Name of the server on which the database is located. You can select from: • Workforce Timekeeper application server only — Disables the Background Processor threads. UNIX installations must use an Oracle database. Enter the database server name: ____________________________ Enter the port for JDBC connections: _____________________________ 150 Kronos Incorporated . Select one of the following: Oracle. enter it here. This machine will be used as a single server for all processes. This machine will function only as an application server Workforce Timekeeper BGP Server Only — Installs the Workforce Central platform with only the Background Processor threads running.

Kronos strongly recommends that you change all system passwords. Kronos strongly recommends that you change all system passwords. Kronos strongly recommends that you change all system passwords. you must change the SuperUser: password. _____________________________ Kronos strongly recommends that you change all system passwords. Kronos strongly recommends that you change all system passwords. Kronos strongly recommends that you change all system passwords.Preinstallation worksheets Dialog box Database server time zone Passwords SuperUser password WFAUser ConnectUser 4500User Import TELETIME XMLUSER MobileTime DCMSUser TaskRunner Totalizer Description Information to enter You must select the applicable time zone from a Enter the time zone: drop-down list in the installation program. ____________________________ The first time that you log on to Workforce Enter the new password for Timekeeper as SuperUser. Kronos strongly recommends that you change all system passwords. Kronos strongly recommends that you change all system passwords. Kronos strongly recommends that you change all system passwords. Kronos strongly recommends that you change all system passwords. Enter the new password: _____________________________ Enter the new password: _____________________________ Enter the new password: _____________________________ Enter the new password: _____________________________ Enter the new password: _____________________________ Enter the new password: _____________________________ Enter the new password: _____________________________ Enter the new password: _____________________________ Enter the new password: _____________________________ Enter the new password: _____________________________ Guide to Planning a Workforce Central Installation 151 .

Database logon The user name and password for SQL Server. TKCSOWNER. for example. User name: ____________________________ Password: ____________________________ Database schema logon Database logon The user name and password that your relational database requires. User name: ____________________________ Password: ____________________________ SQL Server information Database name The name of your database. User name and password of the owner of the database objects. for example. SUPRKRON. Chinese French Spanish 152 Kronos Incorporated . which Enter the Oracle SID: identifies the database instance that is ____________________________ associated with the Oracle executable. for example. SUPRKRON. web console Oracle information Oracle SID Enter the Oracle security identifier (SID).Chapter 7 Preinstallation requirements and checklists Dialog box Description Information to enter Enter the new password: _____________________________ JBoss JMX and You can change or reset this password. Enter your database name: ____________________________ User name: ____________________________ Password: ____________________________ Languages Languages Identify languages to install.

Preinstallation worksheets Dialog box Description Information to enter Multiple Instances If you are going to use multiple instances. identify the following: Instance name Instance 1 Instance 2 Instance 3 wfc Database name Language Products Service pack Guide to Planning a Workforce Central Installation 153 .

Chapter 7 Preinstallation requirements and checklists 154 Kronos Incorporated .

Index A advanced reporting definition 70 overview 70 using 72 AIX 55 Apache with SSL 57 application layer of Workforce Central architecture 22 application server definition 38 requirements 18 application server staging area 65 building a database RDBMS and middleware 42 business intelligence and analysis products business layer of Workforce Central architecture 22 16 C certificates and keys for implementing SSL 133 Chinese language support 75 Citrix configurations system requirements 46 clock synchronize on Workforce Timekeeper database server 43 code pages 41 combined web and application server Windows 60 common logon handshaking 23 communication HTTP and HTTPS 129 interapplication 23 companion server for UNIX environment of Workforce Timekeeper 87 Configuration Manager 29 general functionality 30 overview 28 using 30 configuration phase of deployment process configuration_date.log 67 B back up a database with Workforce HR/Payroll Solution Manager 97. 98 Background Processor dedicated 28 selecting options to install 79 basic reporting definition 70 overview 70 BiDBWiz used by Workforce HR/Payroll Solution Manager 97 bidirectional character sets 41. 75 bill of materials 65 66 .

Index cookies 24 copy a database with Workforce HR/Payroll Solution Manager 97. 98 credential stores and keys 135 Crystal reports 70 custom installation option 61 definition 59 disk space Workforce Timekeeper 42 documentation using the Workforce Central installation documentation 11 E EAR file 59. 66 employee data in an integrated environment 108 Employee Queue Assistant 114 error messages cannot retrieve data from server 24 D data collection products overview 16 database access by JDBC or ODBC 23 creating for Workforce Timekeeper 48 functionality with multiple instances 32 of Workforce Central architecture 23 options 48 reconciling for Workforce Timekeeper 50 requirements for Workforce Central suite 18 system requirement for Workforce Timekeeper 41 upgrading for Workforce Timekeeper 49 using database server machine time to compute time 43 Database Manager overview 48 reconciliation component 50 segment mapping 51 SEQUENCE count repair 50 using for new and upgraded installations 48 database support code pages 41. product 117 installation phase of deployment process installation scenarios overview 11 installation worksheet Workforce HR/Payroll 145 65 156 Kronos Incorporated . 61. 75 overview 25. 75 multibyte characters 41.txt 65 installation and configuration 65 installation code. 41 deployment configuration phase 66 directory structure 67 installation phase 65 deployment overview 66 F FlexLM 124 French language support 75 fully qualified domain names when using SSRS 72 H hardware and software requirements VMware 19 help files with service packs 77 horizontal scaling 78 HTTP and HTTPS communication 129 I IBM Keyman 134 install.dict 65 install.

Index instance_creation. Latin 2. 75 multiple instances Configuration Manager 29 database functionality 32 general functionality 30 implementing SSL 131 licensing 32 overview 28 requirements 28 service packs 76 with Workforce HR/Payroll 99 multi-schema considerations 53 Oracle 52 J J2EE layer of Workforce Central architecture 22 Java Keytool utility 133 Java RMI 23 jobs and organizations in an integrated environment 110 K Kernel layer of Workforce Central architecture 22 L languages using multiple languages 29 Latin 1. Latin 9 character sets 41.log 67 integrated environment components 105 licenses. profiles. 75 LDAP authentication 46 implementing with SSL 132 license authorization information 117 licensing 117 to 127 categories of licenses 120 if you have problems 123 in an integrated environment 109 N network performance considerations when implementing SSL 131 requirements 45 non-Java components 66 NT authentication 46 Guide to Planning a Workforce Central Installation 157 . roles. 41. and primary accounts 109 overview 105 requirements 103 skills and certificates 112 synchronizing data 115 integrating Workforce Timekeeper and Workforce HR/Payroll 101 to 116 interactive licenses 120 IP Management Service with Solution Manager 96 multiple instances 32 process 122 suite interaction licenses 121 suite product licenses 120 upgrading for Workforce Timekeeper 124 verifying license information 122 Workforce HR/Payroll 126 Workforce Timekeeper 124 Workforce Timekeeper for UNIX 125 M machine time Workforce Timekeeper 43 Microsoft IIS overview 57 middleware requirements 42 multibyte character support 25.

keys. requirements 42 operating systems supported Citrix 46 Oracle database using multi-schema databases 52 with Workforce Timekeeper 51 P preinstallation worksheet Workforce HR/Payroll Process Designer installing 63 Process Manager 23 product licenses 120 product licensing 117 Public CAs 133 145 Q Queue assistants 113 R reconcile option with Database Manager 50 report definition language definition 70 reporting functionality custom security extension 72 overview 70 S scaling horizontally and vertically scheduling products overview 16 78 security considerations 129 to 139 supported methods 46 segment mapping for Workforce Timekeeper 51 self-service products overview 16 separated web and application server Windows 60 SEQUENCE count repair with Database Manager 50 serial code. and credential stores 133 customer’s responsibilities 56 implementing 130 installing Workforce Timekeeper without certificate 134 overview 56 with Apache 56 with multiple instances 131 with Workforce HR/Payroll 136 with Workforce Timekeeper 137 158 Kronos Incorporated . product 117 service packs multiple instances 76 overview 76 rolling back 77 Single Sign On (SSO) 46 skills and certifications in an integrated environment 112 Solaris 55 Solution Manager BiDBWiz 97 overview 96 Spanish language support 75 SQL Server initial parameters 54 SQL Server 2005 and advanced reporting 70 SQL Server Reporting Services see advanced reporting 70 SSL certificates.Index O OpenSSL toolkit 133 operating system options Workforce Timekeeper 55 operating system.

Index SSRS overview 70 see advanced reporting 70 using fully qualified domain names 72 sticky cache 21 suite interaction licenses 121 suite product licenses 120 synchronization processor 112 synchronizing data in an integrated environment 107.ear file using in custom installation 59 using in custom installation option 61 wfc. 98 URL to connect to multiple instances 31 V vertical scaling 78 VMware hardware and software requirements 19 W WAR file 66 web server options 56 requirements 18 security 129 SSL data path 132 web server staging area 65 wfc.zip file using in custom installation 59 using in custom installation option 61 WFCAuth 46 Workforce Activities installing 62 Workforce Analytics overview 16 Workforce Attendance installing 62 Workforce Central APIs 105 architecture 21 client layer 21 deployment process 66 implementing SSL security 130 integrated environment important points interapplication communication 23 T Time & Labor and Scheduling products deployment 65 software system requirements 40 system requirements 38 time and labor products overview 16 typical installation option definition 59 UNIX machines 61 Windows machines 59 U Unicode character set and Oracle database 51 Unicode support 25. 115 System Queue Assistant 114 system requirements Citrix 46 client software for Time & Labor and Scheduling products 38 for integrated Workforce Timekeeper Workforce HR/Payroll 104 Workforce Timekeeper 40 Workforce Timekeeper database 41 Workforce Timekeeper network 45 upgrade a database with Workforce HR/Payroll Solution Manager 97. 41 UNIX typical installation option 61 102 Guide to Planning a Workforce Central Installation 159 .

no separation 82 two instances. 40 using Database Manager 48 web server options 56 Workforce Timekeeper database network requirements 45 operating system and middleware compatibility 42 X XML APIs 23 160 Kronos Incorporated .Index jobs and organizations in an integrated environment 110 licenses in an integrated environment 109 licensing 117 to 127 licensing Workforce HR/Payroll 126 licensing Workforce Timekeeper 124 overview 9 platform and applications 22 requirements for integrated environment 103 skills and certifications in an integrated environment 112 SSL secured data paths 132 suite license interaction 127 suite system requirements 18 synchronizing data in an integrated environment 115 system requirements for integrated environment 104 using the installation documentation 11 Workforce Central utilities overview 16 Workforce Connect overview 16 Workforce Employee license 121 Workforce HR/Payroll common logon handshaking 23 configuration options 90 dual server configuration 90 editing a configuration on a remote server 97 implementing SSL 136 licensing 126 multiple instances 99 overview 16 private web service 23 single server configuration 90 Solution Manager 96 system configuration options 90 Workforce Leave installing 62 Workforce Manager license 121 Workforce Record Manager overview 16 Workforce Scheduler installing 62 skills and certifications in an integrated environment 112 Workforce Timekeeper application server options 55 dedicating machines to certain functions 87 implementing SSL 137 installation options 55 installing 62 installing custom environment 61 installing SSL without certificate 134 licensing 124 multiple instances 29 Oracle considerations 51 reports server 87 sample configuration no multiple instances 84 no separation or multiple instances 81 two instances. separated 85 sample configurations 81 segment mapping the database 51 system requirements 38.

Sign up to vote on this title
UsefulNot useful