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 2007. 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 HR, Workforce Leave, Workforce Manager, Workforce MobileTime, Workforce Operations Planner, Workforce Payroll, Workforce Record Manager, Workforce Recruiter, Workforce Scheduler with Optimization, Workforce Scheduler, Workforce Smart Scheduler, Workforce Tax Filing, Workforce Timekeeper, and Workforce View are trademarks of Kronos Incorporated or a related company. 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 Portal 6.0 Release Date June 2007
Contents
Overview of the Workforce Central Portal System requirements ..................................................................................... 6 Installing on a Microsoft SharePoint portal server ........................................ 8 Installing Microsoft SharePoint Services ................................................ 8 Installing Microsoft Office Web Components ........................................ 9 Configuring Microsoft SharePoint Services ......................................... 10 Required configuration with Kronos applications ................................ 12 Installing the Workforce Central Portal ................................................ 14 Enabling Workforce Central users to access SharePoint Services ........ 15 Additional configurations with different domains ................................ 17 Upgrading from an earlier version .............................................................. 20 Uninstalling the Workforce Central Portal ............................................ 20 Installing Workforce Central Portal v6.x .............................................. 21 Using Workforce Central Portal to view Workforce Central data ............... 22 Kronos web parts and sample pages ............................................................ 24 Descriptions of sample Kronos portal pages ........................................ 28 Load balancing with the Workforce Central Portal ..................................... 32 Overview of load balancing configuration ........................................... 32 Typical load balancing configurations .................................................. 34
Contents
Kronos Incorporated
The Workforce Central Portal organizes important Workforce Central data and displays it in a way that is easy for managers to read. To accomplish this, the Workforce Central Portal uses web parts. A set of web parts comes with the Workforce Central Portal. Each web part displays data that is provided by the APIs that are installed with the Workforce Timekeeper application. Some web parts are associated with a pre-configured XSLT file that formats the data in a table or chart format. The data and the presentation of specific Kronos web parts are configurable. System administrators can choose from the Workforce Central Portal web parts or they can create custom web parts, and integrate them into an existing portal. System administrators can also customize the sample portal pages that are included in the Workforce Central Portal installation. The Workforce Central Portal is compatible with Microsoft SharePoint portal servers on Microsoft operating systems. The Workforce Central Portal supports multiple languages. The Workforce Central Portal does not support single sign-on. The following APIs are provided by the Workforce Timekeeper application and are used by pre-configured Workforce Central Portal web parts: Hour Summary API HPPD API (Hours Per Patient Day) Open Shifts API Projecting Overtime API Schedule Coverage API Staffing Requirements API Volume Data API
System requirements
System requirements
Workforce Central Portal for SharePoint requires the following software components: Kronos software components: Kronos Workforce Central v6.0 or higher Kronos Workforce Scheduler v6.0 or higher Kronos Workforce Scheduler with Optimization v6.0 or higher Microsoft Windows 2003 Server Microsoft Internet Information Server (IIS) 6.0 Microsoft Windows SharePoint Services 2.0 or Microsoft SharePoint Portal Server 2003 Minimum patch required: Service Pack 2, Patch KB924881 (DST) Microsoft Office Web Components (OWC), owc11.exe
Kronos Incorporated
System requirements
Note the following information about the Workforce Central Portal installation: You are not required to install the Workforce Central Portal server on a separate machine. However, the steps for configuring the installation differ, depending on where the components are installed. The Workforce Central application server: Supports combined and separate web and application servers. Supports SSL and non-SSL environments. Does not support multiple instances of the Workforce Central application server.
The Workforce Central Portal server requires that the client Web browser be configured to accept cookies. The Workforce Central Portal does not support Windows Integrated Authentication.
Important: Kronos recommends that the Workforce Central application server and the SharePoint Services portal server reside in the same domain. If the servers do not reside in the same domain, you need to perform additional configuration procedures after you install the Workforce Central Portal. Related Topics Configuring Microsoft SharePoint Services on page 10 Additional configurations with different domains on page 17
Kronos Incorporated
10
Kronos Incorporated
d. In the Identity tab of the Properties dialog box, make sure that the Application pool identity is Predefined and set to Network Service. Do this for the App and the Admin application pool entries.
e. If the Application pool identity is not set to Network Service, consult your SharePoint administrator or visit Microsofts support Web site for information about running Windows SharePoint Services using Kerberos authentication. 3. If the Workforce Central web server and SharePoint Services are installed on the same machine, you must enable anonymous access for the default web site. a. Go to Start > Control Panel > Administrative Tools > Internet Information Services (IIS) Manager. b. In the IIS Manager window, expand the contents of the local computer and click the Web Sites folder. c. Right-click Default Web Site and select Properties. d. Open the Directory Security tab and click Edit in the Authentication and access control group box. e. In the Authentication Methods dialog box, select the Enable anonymous access check box. f. Click OK.
11
12
Kronos Incorporated
6. Perform this step only if Workforce HR/Workforce Payroll was installed before Microsoft SharePoint Services on the same machine: a. In the web.config file located in <root directory>\Inetpub\wwwroot, add the following within the <system.web><httpHandlers> tags: <add verb="*" path="*.aspx" type="System.Web.UI.PageHandlerFactory, System.Web, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> b. In the web.config file, add the following within the <system.web><httpModules> tags: <add name="Session" type="System.Web.SessionState.SessionStateModule" /> <add name="FormsAuthentication" type="System.Web.Security. FormsAuthenticationModule" /> <add name="PassportAuthentication" type="System.Web.Security. PassportAuthenticationModule"/> <add name="UrlAuthorization" type="System.Web.Security.UrlAuthorizationModule" /> <add name="FileAuthorization" type="System.Web.Security.FileAuthorizationModule " /> If you receive the error message The module module_name is already in the program and cannot be added again, you can omit the <add> tag that represents that module. c. In the web.config file, enable sessions by changing the enableSessionState value of the <system.web><pages> tag to true and the enableViewStateMac value to false. 7. Restart the IIS Services.
13
14
Kronos Incorporated
15
7. In the Step 2: Choose Site Groups section, select the site group to which you want to add the users, then click Next. Most users will require Reader access only. 8. In the Step 3: Confirm Users section, verify the e-mail addresses, user names, and display names. 9. In the Step 4: Send E-mail section, select Send the following e-mail to let users know they have been added, then type the subject and body text. 10. Click Finish.
16
Kronos Incorporated
17
Editing hosts files on the servers and client machines You must edit the hosts file on the application server, web server, and client machines that will access the Workforce Central Portal, so that communications can be established. In the hosts file for the application server, you must add the following information: IP address and fully qualified domain name of the SharePoint server IP addresses and fully qualified domain names of each client machine that will access the Workforce Central Portal IP address and fully qualified domain name of the Workforce Central application server IP address and fully qualified domain name of each client that will access the Workforce Central Portal
In the hosts file for the web server, you must add the following information:
If the Workforce Central Portal is installed on a separate machine (not on the web server), you must add the following information in the hosts file: IP address and fully qualified domain name of the Workforce Central application server IP address and fully qualified domain name of the Workforce Central web server IP address and fully qualified domain name of each client that will access the Workforce Central Portal
In the hosts file for each client machine that will access the Workforce Central Portal, you must add the following information: IP address and fully qualified domain name of the Workforce Central application server IP address and fully qualified domain name of the SharePoint server
18
Kronos Incorporated
To edit the hosts file: 1. Locate the hosts file. Typically, the file is in ..\WINDOWS\system32\drivers\etc. 2. Open the file with a text editor. 3. Follow the instructions in the file for adding IP addresses and host names. Add the appropriate IP addresses and host names, depending on which hosts file you are editing (application server, web server, or client). 4. After you finish editing the file, save and close the file.
19
20
Kronos Incorporated
To uninstall the Workforce Central Portal: 1. On the portal server, go to Start > Settings > Control Panel > Add/Remove Programs. 2. Highlight Workforce Central Portal for SharePoint, then click Add/Remove. 3. When you are asked if you want to remove the selected application and all its components, click OK. To restore the old site to a new location, enter the following command: stsadm -o restore -url new_site_url -filename backup_file_name where new_site_url is the URL for the restored site. Once the site is restored, you can retrieve the items that you need and copy them to another SharePoint site.
21
3. Select the web part page that you want to view. Bookmark this page for future access. 4. When the web part page appears, click one of the links that enables you to enter your credentials. 5. When the Workforce Central logon screen appears, enter your Workforce Central user name and password, and click OK. 6. The portal page that you selected appears. Use the navigator web part to select the data that you want to view.
22
Kronos Incorporated
Notes: Your Workforce Central Function Access Profile must allow access to the XML APIs in order for you to view Workforce Central data in the portal. If you do not have this access, contact your Workforce Central system administrator. A Workforce Central user name or password that contains special characters, such as &, %, #, or @, will cause an error that prevents the user from viewing Workforce Central data in the portal. Ask a Workforce Central system administrator to change your user name, password, or both, if you encounter this problem. For system administrators only: Refer to the Workforce Central System Administrators Guide for information about configuring the appearance of the default Web part pages, the Kronos web parts, and the information that appears in each Web part.
23
24
Kronos Incorporated
Web part
Description
Kronos Process Manager In Box Enables users to view the number of actions and notifications that are stored in their Process Manager inboxes. Kronos XML API XSLT Table Enables system administrators to configure tables to display Workforce Central data, including custom Key Performance Indicators (KPIs) and Workforce Timekeeper Genies. Users can view the tables in the portal. Enables system administrators to configure charts to display Workforce Central data, including custom Key Performance Indicators (KPIs) and Workforce Timekeeper Genies. Users can view the charts in the portal.
25
Kronos Productivity Monitor Table Kronos Productivity Monitor Chart Kronos Key Performance Indicators
26
Kronos Incorporated
Description Enables users to view the amount of projected overtime for employees in a health care location. The data is based on the thresholds for overtime qualification that system administrators set in the Workforce Timekeeper application. Uses the Projected Overtime API. Enables users to view total per pay code, for a specific health care location. Uses the Hours Summary API. Enables users to view data from the Volume tab in the Workload Planner. Data can include the actual, budgeted, and projected volume of patients at a specific health care location. Uses the Volume API. Enables users to a view a list of shifts that have not yet been assigned to employees. Uses the Open Shifts API. Enables users to view the number of hours worked, scheduled, or budgeted, per patient per day. Uses the HPPD API.
27
Sample Genie portal page The following illustration shows the sample Genie portal page that is included with the Workforce Central Portal installation. The page contains web parts that display Genie data. The web parts are created using the Kronos XML API XSLT Chart and Kronos XML API XSLT Table web parts that are installed as part of the Workforce Central Portal installation. The page is configurable.
28
Kronos Incorporated
Sample Retail portal page The following illustration shows the sample Retail portal page that is included with the Workforce Central Portal installation. Note the following about this portal page: The page includes the Kronos Productivity Monitor Navigator and retail web parts that enable users to view and interact with Workforce Central data. All web parts in the portal page are pre-configured and are installed as part of the Workforce Central Portal installation. The Daily Sales and Daily Labor charts (right side of the screen) use the Kronos XML API XSLT Chart web part that is installed as part of the Workforce Central Portal installation. You can use the Kronos XML API XSLT Chart and Kronos XML API XSLT Table to create web parts to display relevant data. The page is configurable.
29
Sample Health Care Manager portal page The following illustration shows the sample Health Care Manager portal page that is included with the Workforce Central Portal installation. Note the following about this portal page: The page includes the Kronos Navigator and health care web parts that display data for health care managers to view and manipulate. All web parts in the portal page are pre-configured web parts that are installed as part of the Workforce Central Portal installation. The page is configurable.
30
Kronos Incorporated
Sample Health Care Staffing portal page The following illustration shows the sample Health Care Staffing portal page that is included with the Workforce Central Portal installation. Note the following about this portal page: The page includes the Kronos Navigator and health care web parts that display data for health care staffing managers, to view and manipulate. All web parts in the portal page are pre-configured web parts that are installed as part of the Workforce Central Portal installation. The page is configurable.
31
Important: If the system consists of separate application, web, and portal server machines, all machines must be in the same domain to implement load balancing. If the machines are not in the same domain, refer to Additional configurations with different domains on page 17; you must perform these configuration procedures so that load balancing will work.
32
Kronos Incorporated
Workforce Timekeeper and Workforce Central Portal require stateful load balancing. When a Workforce Timekeeper session is initiated, the load balancer must determine the destination server and send all connections from a given user to the same server for the duration of the session. This means that the load balancer must have the means to identify the user, to recognize session initiation and termination, and to track each session. This is called session persistence, stickiness, or affinity. Load balancers can track sessions by using cookies, URL parsing, static and dynamic algorithms, source and destination addresses, and other means. Although most load balancers solve the problem of balancing a load across multiple servers, they do not all provide the persistence needs of Workforce Timekeeper. The two common methods of ensuring persistence with Workforce Timekeeper are cookie-based persistence and Secure Sockets Layer (SSL) session ID-based persistence.
33
34
Kronos Incorporated
Load balancing configuration with the Workforce Central Portal The following illustration shows a typical load balancing configuration when Workforce Timekeeper is installed with the Workforce Central Portal. The web server, portal server, and application server are shown as logically distinct, but the image applies to combined and separate web/application servers. Note: Separating the portal server is not mandatory. Depending on the configuration and the load, this configuration may be altered. Contact your Kronos Service Representative for best practices when configuring your server topology with Workforce Central Portal. In most cases, communication to the portal server is distributed using a hardware load balancer, as is communication from the portal server to the Workforce Timekeeper web server. The hardware load balancers for the portal server and the web server are shown as logically distinct, but a single hardware-based load balancer is capable of load balancing both servers. The image shows two portal servers, two web servers, and two application servers, but these numbers are arbitrary. For example, you could have two portal servers, seven web servers, and five application servers. The exact number of each type of server depends on your load requirements and is not constrained by any requirement of Workforce Central Portal.
35
36
Kronos Incorporated