Enterprise etime Installation Guide for Windows

Transcription

1 Enterprise etime Installation Guide for Windows A guide to installing Enterprise etime 5.0 time and labor management system for Windows systems. Enterprise etime Suite Version 5 Document Part Number: Document Revision: A

2 The information in this document is subject to change without notice and should not be construed as a commitment by ADP, Inc. ADP is not responsible for any technical inaccuracies or typographical errors which may be contained in this publication. Changes are periodically made to the information herein, and such changes will be incorporated in new editions of this publication. ADP may make improvements and/or changes in the product and/or the programs described in this publication at any time without notice. This document or any part thereof may not be reproduced in any form without the written permission of Kronos Incorporated. All rights reserved Kronos Incorporated. ADP provides this publication "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. The ADP Logo is a registered trademark of ADP of North America, Inc. etime is a registered trademark of Automatic Data Processing, Inc. 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, ShopTrac, ShopTrac Pro, StarComm, StarPort, StarSaver, StarTimer, TeleTime, Timekeeper, Timekeeper Central, TimeMaker, Visionware, Workforce Accruals, Workforce Central, Workforce Decisions, Workforce Express, Workforce Genie, and Workforce TeleTime are registered trademarks of Kronos Incorporated or a related company. Comm.Mgr, CommLink, DKC/Datalink, FasTrack, HyperFind, Improving the Performance of People and Business, Kronos 4500, Kronos 4500 Touch ID, Kronos e-central, KronosWorks, Labor Plus, Schedule Assistant, Smart Scheduler, Smart View, StartLabor, Start Quality, Start WIP, Starter Series, Timekeeper Decisions, Timekeeper Web, VisionPlus, Winstar Elite, WIP Plus, Workforce Activities, Workforce Connect, Workforce Employee, Workforce HR, Workforce Manager, Workforce MobileTime, Workforce Payroll, Workforce Record Manager, Workforce Recruiter, Workforce Scheduler, Workforce Smart Scheduler, Workforce Tax Filing, Workforce Timekeeper, and Workforce View are trademarks of Kronos Incorporated or a related company. 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 ADP, Inc. Automatic Data Processing, Inc. One ADP Boulevard Roseland, New Jersey For more information, see the following ADP, Inc. Web page: Document Revision History Document Revision Product Version Release Date A Enterprise etime 5.0 April 2004

3 Contents About This Guide Organization of This Guide... x Enterprise etime Documents...xii Chapter 1: Overview of Enterprise etime Enterprise etime Architecture Installable Components Totalizer Application Server Background Processor Enterprise etime Setup Client PCs Enterprise Scheduler Data Collection Manager Network Requirements Database Server System Requirements Application Server Background Processor Enterprise etime Setup Communication Application Server Database Support Java Client Enterprise etime Professional - HTML Client Microsoft Terminal Services Support

4 Contents Citrix MetaFrame Support Support for Enterprise etime Setup Support for Web Server Support for Web Client OEM Licensed Products Chapter 2: Preparing for Installation Security Considerations User Names and Passwords Cookies Web Server Security Web Server Options Gathering Installation Information Enterprise etime Installation Worksheet Reviewing the Preinstallation Requirements Chapter 3: Installing Enterprise etime Starting the Installation Program Installing a Single Server Using the Custom Option Installing the Application Server Installing the Background Processor Installing Additional Background Processors Installing Enterprise etime Setup Installing Kdemo Kdemo Prerequisites Installing Kdemo with Apache Web Server Software Installing Kdemo with IIS Web Server Software Installing Enterprise Scheduler iv ADP, Inc.

5 Contents Chapter 4: Using Kdemo Kdemo Components System Requirements Creating a Kdemo Database Attaching the Kdemo Database to the Database Server Starting the Database Server Attaching the Kdemo Database Changing the MSDE Password Detaching a Database Copying and Backing Up Kdemo Databases Upgrading the Kdemo Database Chapter 5: Installing Non-U.S. English Systems Character Set Designations Configure Application Server Settings Set Regional Information and Time Zone in Operating System Set Enterprise etime Local Values Replace Global Attributes File Create ADP Relogon Window Create Refresh Button Directory Set Up Online Help Files Set Up Reports Set Time Display Reboot Machine Troubleshooting Checklist Chapter 6: Starting Enterprise etime Starting and Stopping the Application Server Starting the Application Server Stopping the Application Server Starting and Stopping the Background Processor Accessing the Enterprise etime Professional - Java Client Accessing the Enterprise etime Professional - HTML Client Timecard and Time Stamp Quick Time Stamp Enterprise etime Installation Guide for Windows v

6 Contents Chapter 7: Changing System Account Passwords Standard System User Accounts Changing the SuperUser Password Online Mode Offline Mode Changing the Totalizer Password Changing the TaskRunner Password Changing the xmluser Password Changing the Password for the Import User Account Chapter 8: Installing Enterprise etime Clients Before You Access Enterprise etime JRE Plug-Ins Setting Up an Internet Explorer Browser Installing JRE Plug-in Installing JRE Plug-in on Windows 2000 Systems with Restricted User Rights Installing Adobe Acrobat Reader Installing and Setting Up a Netscape 7.0 Browser Netscape 7.0 for U.S. English Only Netscape 7.0 for International Use Installing Adobe Acrobat Reader Chapter 9: Uninstalling Enterprise etime Overview Exceptions Before Uninstalling Uninstalling Enterprise etime Uninstalling Enterprise Scheduler Only Troubleshooting vi ADP, Inc.

7 Contents Chapter 10: Upgrading Enterprise etime Before You Begin Task 1: Reconcile the Current Database Task 2: Back Up the Current Database Task 3: Uninstall Enterprise etime (v4.2 or earlier) Task 4: Install Enterprise etime v Task 5: Run the Database Manager for v Task 6: Install Enterprise etime on Additional Machines Chapter 11: Troubleshooting Common Installation Error Messages Changing User Privileges Changing JRun Service Password Creating the JRun Default Server Apache Service Not Registering as a Service Apache Uses a Different Port Setup Fails to Create Apache Service MSDE Installation Fails (Kdemo) Background Processor Does Not Start The kronos.exe Process Does Not Stay Loaded Application Server Starts in Offline Mode Exception Attempting to Connect to Database (Windows) Exception Loading Configuration (Oracle) Permission Denied Error Database Version Mismatch Memory Impact when Making Large Organization Map Changes Appendix: Enterprise etime Directory Structure Directory Structure...A-2 Application Subdirectory...A-3 Core Components...A-4 Index Enterprise etime Installation Guide for Windows vii

8 Contents viii ADP, Inc.

9 About This Guide This guide describes how to install Enterprise etime components in a Windows environment. It provides an overview of the Enterprise etime architecture, outlines the system requirements, and explains how to install the product s server and client components. This preface contains the following sections:! Organization of This Guide! Enterprise etime Documents

10 About This Guide Organization of This Guide This guide contains the following information:! Chapter 1, Overview of Enterprise etime, describes the basic concepts of the Enterprise etime architecture and identifies system requirements.! Chapter 2, Preparing for Installation, discusses security considerations and Web server options. This chapter also includes the installation worksheet, which you should complete before installing the Enterprise etime software.! Chapter 3, Installing Enterprise etime, explains how to install all the components on one machine or individual components on individual machines. This chapter also describes how to install Enterprise Scheduler, which is a separately licensed advanced scheduling add-on to Enterprise etime.! Chapter 4, Using Kdemo, describes how to configure and use the Kronos demonstration software, Kdemo, which enables you to run the entire Enterprise etime system on one PC for demonstration, training, and testing purposes.! Chapter 5, Installing Non-U.S. English Systems, provides an overview of additional considerations for non-u.s. English installations.! Chapter 6, Starting Enterprise etime, explains how to start the application server and the client machines (HTML Client and Java Client).! Chapter 7, Changing System Account Passwords, explains how to change the six standard application-level system-user names and passwords that are delivered by the installation program.! Chapter 8, Installing Enterprise etime Clients, explains how the Java Runtime Environment (JRE) software is automatically downloaded to each client machine the first time that the client machine accesses the Enterprise etime server. It also describes how to install and configure Adobe Acrobat Reader on client machines that print reports.! Chapter 9, Uninstalling Enterprise etime, explains how to remove Enterprise etime components, as well as Enterprise Scheduler, from your machine. x ADP, Inc.

11 Organization of This Guide! Chapter 10, Upgrading Enterprise etime, describes how to upgrade Enterprise etime v4 to Enterprise etime v5.0.! Chapter 11, Troubleshooting, describes how to address a number of possible installation problems that you might encounter.! Appendix, Enterprise etime Directory Structure, describes the directory structure of the files delivered by the Enterprise etime installation procedure. Enterprise etime Installation Guide for Windows xi

12 About This Guide Enterprise etime Documents The following documentation is available to help you install, maintain, and use the Enterprise etime database and software:! Enterprise etime Installation Guide for Windows provides an overview of the Enterprise etime architecture, outlines the system requirements, explains how to install the product s server and client components, and includes licensing and upgrade requirements.! Enterprise etime Installation Guide for UNIX describes how to install the Enterprise etime server on UNIX platforms. It provides an overview of the Enterprise etime architecture, outlines the system requirements, and explains how to install the Application Server and Background Processor on UNIX platforms.! Getting Started with Enterprise etime A Guide for Managers explains some of the most common tasks that managers are likely to perform. It summarizes key product features for people who access employee time and attendance information. The book also explains the various Enterprise etime components and the most common tasks that managers are likely to perform with each component.! Getting Started with Enterprise etime A Guide for Employees explains some of the most common employee tasks, which include using the Timecard and Time Stamp components, as well as viewing personal schedules and reports.! Getting Started with Enterprise etime A Guide for Employees (HTML version) explains some of the most common employee tasks in Enterprise etime Professional - HTML Client, which include using the Timecard, Time Stamp, and Quick Time Stamp components, as well as viewing personal reports.! Enterprise etime System Administrator s Guide describes the administrator s activities, such as system configuration and setup, and working with log reports, predefined data, and diagnostic tools.! Enterprise etime Database Tables Reference Guide contains details about the Enterprise etime database tables. xii ADP, Inc.

13 Enterprise etime Documents! Enterprise etime Database Views Reference Guide provides information and details about Views and how they are used as virtual tables in Enterprise etime.! Enterprise etime Database Installation Guide instructs customers and service personnel who install or upgrade Enterprise etime databases. Instructions include installing and setting up the Relational Database Management System (RDBMS) and ADP application database components, and upgrading your database components for compatibility with new versions of Enterprise etime products.! Enterprise etime Database Administrator s Guide explains how to maintain the Oracle and SQL Server 2000 databases for Enterprise etime. This guide includes procedures for backing up databases, restoring and recovering databases, adjusting performance, and using maintenance utilities.! Enterprise etime Import Guide: Table Format provides instructions and table data for Enterprise etime Import tables.! Enterprise etime Import User s Guide provides information about setting up and running XML and table imports for labor management systems. It describes the Transaction Assistant used to correct failed XML import data.! Enterprise etime XML Import Guide provides information that specifically addresses XML import issues, and includes descriptions of all of the tags, actions, and properties used by import transactions.! Guide to Translating and Customizing the Enterprise etime User Interface and Online Help provides instructions for editing the browser-based graphical user interface, the Setup applications user interface, and the associated browser-based Help files for Enterprise etime and Enterprise Scheduler.! Developer s Toolkit documentation: Enterprise etime includes an Application Program Interface (API) that you can use to access certain Enterprise etime features from application programs. The Enterprise etime Developer s Toolkit Programmer s Guide includes annotated sample programs that show how to use the API, and the Enterprise etime Developer s Toolkit Reference Guide provides detailed information about each element of the API. Enterprise etime Installation Guide for Windows xiii

14 About This Guide! Online Help for the Enterprise etime system is installed automatically with the product. To access online Help: click the Help link at the bottom of the navigation bar; click the Help icon in the component; or click the Help button in a dialog box.! Release notes provide additional information about Enterprise etime, including a list of new features, resolved issues, and late-breaking changes. xiv ADP, Inc.

15 Chapter 1 Overview of Enterprise etime Enterprise etime labor management software enables employees to use an Internet Explorer or Netscape browser to enter, review, change, and approve the time spent in a number of job-related activities. Managers can then review, change, or approve the employees time, as well as use the system to set schedules, generate reports, and transfer time information to their payroll system. This chapter describes the basic concepts of the Enterprise etime architecture as well as the system requirements. It contains the following sections:! Enterprise etime Architecture! Installable Components! System Requirements! Citrix MetaFrame Support! OEM Licensed Products

16 Chapter 1 Overview of Enterprise etime Enterprise etime Architecture Enterprise etime is the foundation of the Enterprise etime. It automates and streamlines the management, collection, and distribution of employee hours, and eliminates the use of manual timecards. Enterprise etime uses a three-tier client/ server application structure:! Tier 1 is the client software. The client accesses the Enterprise etime application through a Web Uniform Resource Locator (URL) using a browser. Application functions are implemented as Hypertext Markup Language (HTML) pages or Java applets. The pages and applets connect to the Webbased Enterprise etime application server. The applets are downloaded via a.jar file and use a sticky cache, which means that applets are only downloaded the first time that the client accesses the applet.! Tier 2 is the Enterprise etime application server, which implements the major parts of the application including the application logic. The second tier performs the real work of the application. The application server includes: A Web server component that listens for browser requests and passes these requests to the application server. The Totalizer, which executes the time and attendance business rules, using an object-oriented model of more than 100 different business rule and pay policy elements. Two Enterprise etime components use the Totalizer: the Callable Totalizer, which supports interactive requests for totals, and the Background Processor off-line computation engine.! Tier 3 is the database server, which stores all of the application data. 1-2 ADP, Inc.

17 Installable Components Installable Components The actual elements that a typical Enterprise etime installation comprises include the following, all of which are connected to a network. These elements are configured according to the size and requirements of each company. For example, small companies might install all components on one machine. Larger companies are likely to install each component on multiple machines. Note: Some of the Enterprise etime components can run on Windows or UNIX machines. Others can run only on Windows machines. For information about installing Enterprise etime components on UNIX systems, refer to the Enterprise etime Installation Guide for UNIX.! Data collection devices Timekeeper terminals (optional).! Data Collection Manager, or DCM Transfers information from the timeclocks into the database (optional). For more information about installing DCM, refer to the Data Collection Manager Installation Guide. DCM only runs on a Windows machine.! Application server Runs Web server software (Apache, Microsoft IIS, or Sun ONE) as well as the Enterprise etime programs and business logic. Most installations have at least two application servers, one as the primary device and the other for backup purposes. Additional application servers can be dedicated to specific functions, such as Event Manager or Reports, as described on page The application server can run on Windows or UNIX, although Event Manager and Reports can run only on the Windows companion server.! Background Processor Writes updated totals to the database at specified intervals to ensure that the database reflects up-to-date totaled data. The Background Processor can run on a Windows or UNIX machine.! Enterprise etime Setup Defines the Enterprise etime rules specific to each company. Enterprise etime Setup can run only on a Windows machine. Enterprise etime Installation Guide for Windows 1-3

18 Chapter 1 Overview of Enterprise etime! Client PCs Web browsers on Windows or Macintosh machines that interact with the Enterprise etime system.! Database server Uses a Microsoft SQL Server 2000 (Windows) or Oracle (Windows or UNIX) database to store all Enterprise etime data. For most installations, ADP recommends that the database server be a separate machine from the other Enterprise etime components. The following diagram shows each of these elements: Each Enterprise etime element can be a separate device, or the elements can be configured according to the size and requirements of your company. 1-4 ADP, Inc.

19 Installable Components Totalizer The Totalizer calculates totals in Enterprise etime. When time-related events occur, the Totalizer takes available employee data, applies the correct rules and policies, and computes totaled data, which ensures that pay rules are applied automatically and consistently across the organization. Two components access the Totalizer:! The Background Processor invokes the Totalizer offline and stores information in the database. The Background Processor runs independently of the application server to off-load computationally intensive work. By offloading computations to the Background Processor, the application server can be optimized for interactive use. Because the Background Processor prepares data ahead of time, the information is up to date when a user logs on to the application server.! The Callable Totalizer invokes the Totalizer interactively in the browser to total employees whose totals have not yet been computed by the Background Processor and are not up to date. It does not send the totals to the database. Totals that are generated online by the Callable Totalizer must be generated a second time by the Background Processor in order to save the values in the database. Application Server The application server is the intermediary between the browser-based front end and the back-end database. It contains the software that provides the business logic for the Enterprise etime components. The application server is also a Web server that uses the client/server model and Hypertext Transfer Protocol (HTTP) to serve the files that form Web pages to users whose computers contain HTTP clients that forward their requests. Software required by the Enterprise etime application server includes:! Web Server software Apache, Sun ONE, or Microsoft IIS, with or without Secure Sockets Layer (SSL) support. If you use Sun ONE or Microsoft IIS software, you must install it before you install Enterprise etime. If you do not have one of these Web servers on your system, the Enterprise etime installation program installs Apache software. Enterprise etime Installation Guide for Windows 1-5

20 Chapter 1 Overview of Enterprise etime! Java Runtime Environment (JRE) Consists of the Java virtual machine, the Java platform core classes, and supporting files. JRE is the runtime part of the Java Development Kit no compiler, no debugger, and no tools. JRE is the smallest set of executables and files that constitutes the standard Java platform. JRE is installed by the Enterprise etime installation program and is automatically downloaded to each PC the first time that the PC connects to the Enterprise etime application server.! Callable Totalizer A program installed by the Enterprise etime installation program that enables the application server to access to the Totalizer interactively. A Web browser provides the user interface for Enterprise etime. The Web browser forwards user requests to the application server, which returns a modified or new Web page to the user s browser. Application Server Configurations Many Enterprise etime installations include more than one application server. The actual number of application servers in your installation depends on many factors such as the number of employees and system usage. Other factors include the following:! If you use Enterprise etime with more than one language, a separate application server must be set up for each language.! If you have Enterprise etime application servers in different time zones and one of the time zones does not observe Daylight Saving Time (DST)*, you must configure an application server with the time zone that does not support DST. All client machines within the non-dst time zone should be directed to this non-dst application server. In addition, it is acceptable to configure a server time in different time zones (such as Eastern and Pacific) and allow a client machine set up for Eastern time to point to the server set up in a Pacific time zone, as well as a client set up with Pacific time pointing to a server in Eastern time. This is due to an issue within the JDBC driver. *Indiana and some parts of Arizona do not observe DST. 1-6 ADP, Inc.

21 Installable Components Using Single Servers In a Windows-only environment, you might be able to combine all components onto one PC, depending on your company s requirements, for example:! One application server! One or more Background Processors! Enterprise etime Setup! DCM software, if appropriate! SQL Server database Note: Oracle databases cannot be installed on the same machine as other Enterprise etime components. Using Multiple Servers Larger customers will typically install more than one application server. If you install multiple servers, you must also change a number of system settings on your primary server. Refer to the Enterprise etime System Administrator s Guide for more information. If you use multiple application servers and you want all users to access Enterprise etime by the same URL, you must install third-party load-balancing software. Enterprise etime and Third-Party Load Balancing Solutions Load balancing is a method of evenly distributing Web site traffic across multiple Web servers in order to enhance system performance and availability. By distributing user requests across an array of servers, an effective load balancing solution can relieve network traffic overload, reduce web server burden, and provide fault tolerance. Load balancing is a complex topic and many load balancing products are available. The choice of load balancing solution and the actual configuration used depend on your functional requirements and your LAN/WAN infrastructure. As such, ADP does not endorse any one solution. However, ADP recommends that Enterprise etime Installation Guide for Windows 1-7

22 Chapter 1 Overview of Enterprise etime you consider the following requirements and best practices for using a third-party load balancer with the Enterprise etime application. Note: The Enterprise etime application server contains a Web server component (Apache, Sun ONE, or IIS). Although this discussion refers to the application server, the load balancer is really using the Web server component. Three key points are important when considering load balancing solutions:! Session persistence! Load distribution method! Application awareness These points are discussed in the following sections. Session Persistence Load balancers can be either stateless or stateful. Stateless load balancing is when the load balancer distributes all the incoming traffic to available servers but does not keep track of individual sessions. If the load balancer keeps track of state information for every session and makes load-balancing decisions for each session, it is called stateful load balancing. Enterprise etime requires stateful load balancing. When an Enterprise etime session is initiated, the load balancer must determine the destination Web 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 a means to identify the user, recognize session initiation and termination, and be able to track each session. This is called session persistence, stickiness, or affinity. Load balancers can track traffic by using cookies, URL parsing, static and dynamic algorithms, source and destination addresses, and much more. 1-8 ADP, Inc.

23 Installable Components Although most load balancers solve the problem of balancing load across multiple servers, they do not all provide the persistence needs of Enterprise etime. The two common methods of ensuring persistence with Enterprise etime are cookiebased persistence and Secure Sockets Layer (SSL) session ID-based persistence.! Load balancers that use cookies for persistence can use either passive cookies or active cookie insertion. Passive cookies are found within the application. Active cookies are inserted by the load balancer. Load balancers that use passive cookies for persistence manage the session with a cookie found in the header of the initial logon screen and all subsequent screens until the session terminates. However, Enterprise etime does not insert a cookie on the logon screen. This means that the load balancer must use active cookie insertion by inserting its own cookie at logon (F5 Networks and Cisco ArrowPoint use this technique). Likewise, the Enterprise etime JRun session identifier cannot be used to maintain persistence because there is no session ID on the Enterprise etime logon page.! If you use SSL, the load balancer can use the SSL session identifier to maintain persistence. In an SSL session, the client and the Web server first exchange certain parameters for encryption and decryption. The Web server sends an SSL identifier as part of the negotiation. The load balancer stores the SSL session ID and its association with a Web server to ensure that all subsequent traffic with that SSL session ID is directed to the same Web server. Cisco and F5 can use the SSL session ID-based persistence. Load Distribution Methods Load balancers can use a variety of load distribution methods to allocate load to the various servers in the Enterprise etime environment. The load distribution algorithm directly impacts the effectiveness of the load balancing solution. Some of the most common load distribution methods are:! Round robin The load balancer assigns connections to each server in a set order and then starts again at the beginning of the order. Enterprise etime Installation Guide for Windows 1-9

24 Chapter 1 Overview of Enterprise etime! Least connections The load balancer keeps track of the total number of concurrent active connections on each server and sends a new request to the server with the least number of concurrent connections.! CPU utilization The load balancer detects the CPU utilization on each server and sends requests to the server with the lowest level of CPU utilization.! Packet based The load balancer bases the assignment of connections on client traffic and network throughput.! Response times The load balancer monitors incoming client requests and sends requests to the server that is providing the fastest response times. Application Awareness Performing various checks to determine system health is one of the most important benefits of a load balancer. Without a load balancer, a client request can be sent to a server that is down. However, not all load balancers check that the application is up. If a server is up, but the application is down, the load balancer should not attempt to make a connection. Load balancers that can detect the condition of both the server and the application are much more effective load balancing solutions. Load Balancers Used with Enterprise etime Although load balancing products are available in many forms, there are two basic types that are typically used with Enterprise etime:! IP-based load balancers run on the application servers themselves and execute algorithms to coordinate the load distribution process among them. Microsoft Network Load Balancing (formerly called Windows Load Balancing Software WLBS) is one of the most common IP-based load balancers used with Enterprise etime.! Hardware load balancers are black-box products that include the necessary hardware and software to distribute requests to multiple servers. Examples of hardware load balancers are those by Cisco Arrowpoint and F5 Networks ADP, Inc.

25 Installable Components Best Practices! Set up your load balancing solution before you install Enterprise etime.! Ensure that the database traffic does not pass through the load balancer. Traffic must use a gateway address instead of the load balancer to access the database.! IP-based load balancers do not work with Enterprise etime if you use a proxy server because it looks like all requests are coming from the same IP address or group of IP addresses.! Do not use DNS round robin load balancing with Enterprise etime. It uses a function of DNS that allows more than one IP address to associate with a host name. It does not work with Enterprise etime.! If you use Microsoft Network Load Balancing, consider the following: Like all IP-based load balancers, Network Load Balancing does not work with Enterprise etime if you use a proxy server. In addition, do not use Class C filtering mode; it will route all requests to one web server. Because Network Load Balancing operates at the network layer and not at the application layer, it detects breaks in network connectivity, but does not detect an application-layer failure. So, if the Enterprise etime application is down but the Web server is up, Network Load Balancing will continue to send requests. Layer 2 switches, by default, prevent unicast Network Load Balancing from functioning correctly. Network Load Balancing is a round robin solution and does not determine the number of concurrent users per server. Network Load Balancing can only handle affinity (statefulness) on an IPspecific basis. Do not set affinity in the port rules to None. Any load balancing software or hardware combination used for an Enterprise etime environment must support sticky sessions and be configured as such. To configure Network Load Balancing to support this, the affinity setting must be set to Single. When the affinity is set to Single, it ensures that all of an end-user s transactions are handled by a single application server. Enterprise etime Installation Guide for Windows 1-11

26 Chapter 1 Overview of Enterprise etime Enterprise etime without Third-Party Load Balancing If you do not install a load balancer, each user must specify the URL of a specific application server. In this case, you can balance the workload by using dedicated servers for specific tasks, for example:! For Event Manager Events can be set up on any Windows server, but only the primary scheduler server can schedule the processing of these events. You must designate one server as the primary scheduler. This server can be the same one that runs other applications, or it can be a dedicated server. Before you designate a server as the primary scheduler, you must ensure that Microsoft Task Scheduler is installed. If you are using Windows 2000 or Windows 2003, Task Scheduler is installed with the operating system. If you are using Windows NT, you must install Task Scheduler. To install Task Scheduler: a. Install Internet Explorer 5.5 or 6.0. b. Select the Offline Editing Tools option. c. Install Task Scheduler as a service that starts automatically.! For Workflow Notifications The primary notification server keeps track of conditions for which a notification is requested and triggers the preparation of s when the condition is met. You must designate one server as the primary notification server. This server can be the same one that you use for other purposes, or it can be a dedicated server. Notifications can be configured on any server, but only the primary notification server can trigger the processing of them. Other properties must also be reconfigured for a multiserver environment. Refer to the Enterprise etime System Administrator s Guide for more information.! For Group Edits One server must be designated as the primary group edit server, which is the only server that is authorized to run the group edit recovery and delete threads.! For DCM A single DCM server can be configured on the same server that you use for other purposes or you can set up one or more dedicated DCM servers. No primary DCM server is needed ADP, Inc.

27 Installable Components! For the Background Processor ADP recommends that you run Totalizer instances on dedicated Background Processor servers, since running a Background Processor on an application server can cause load problems. You can set up multiple Background Processors on one server or many servers.! For reports If you generate many reports, you can improve system performance by creating one or more application servers dedicated to generating reports. When the primary application server receives a report request from a client, it always runs the report itself or always delegates the request to other servers. It does not have the discretion to run the report sometimes and to relay the request elsewhere at other times. It does, however, give every report server an equal opportunity of getting report requests. Therefore, to create a dedicated report server, you must disable the report service on the primary application server that handles user authentication and enable it on the application server on which you want to run reports: a. Install Enterprise etime. b. Select System Configuration > System Settings on the navigation bar. c. Select the Reports tab. d. Opposite site.reporting.engine.enable, click the Disable or Enable button according to the type of server that you are setting up. For more information about configuring reports in a multiserver environment, refer to the Enterprise etime System Administrator s Guide. Background Processor The Background Processor automatically calculates totals, such as hours worked and pay earned, from the data in the database. The Background Processor runs continuously as a background process and updates totals at specified intervals. For example, assume that the update interval of the Background Processor is 30 seconds. After remaining idle for 30 seconds, the Background Processor recalculates totals for all employees whose totals are not up to date. The Background Processor is then idle for 30 more seconds before it calculates totals again. The update interval can be set to as little as 1 second or as long as 99 hours. Enterprise etime Installation Guide for Windows 1-13

28 Chapter 1 Overview of Enterprise etime Enterprise etime Setup One or more PCs contain the Enterprise etime Setup component, which is a Windows application that does not have a browser interface. System administrators use the Enterprise etime Setup component to set up labor levels, pay rules, accruals, and comments for the Enterprise etime system. Client PCs Client PCs connect users to the Enterprise etime application server through an Internet Explorer or Netscape browser. By entering the URL of the application server, the Enterprise etime portal opens on the client PC and the user interacts with the Enterprise etime system according to his or her access rights. Enterprise etime provides two different types of client user interface:! Java-based client! HTML-based client The user interface in the HTML Client is not downloaded once and reused, as is the case with the Java Client. Each time data changes in the HTML Client, the page is rebuilt on the application server. Enterprise etime Manager or Enterprise etime Professional Java Client The Java Client interface is the full-function Java applet interface to Enterprise etime. The first time that a browser accesses the application server, a JRE plugin is downloaded to the browser. With the Java Client, employees and managers see the same timecard view when they access the employee s timecard ADP, Inc.

29 Installable Components Enterprise etime Professional - HTML Client The HTML Client option provides a client interface for employees who do not have the hardware required to run the Java Client option. The HTML Client does not download code to the client machine. With the Enterprise etime Professional - HTML Client, the employee views his or her timecard or Time Stamp in the HTML user interface, and the manager views the employee s timecard in the Java Client user interface. This option provides lower hardware and operating system requirements as outlined on page For information about accessing the Enterprise etime Professional - HTML Client, see Chapter 6. Enterprise Scheduler Although Enterprise etime includes a basic scheduling component, an optional advanced scheduling component called Enterprise Scheduler is also available. Enterprise Scheduler is a Web-based tool that is designed to assist managers in creating complex schedules and facilitate frequent changes that occur as the schedule is being worked. Enterprise Scheduler is delivered when you install the Enterprise etime application server, but is licensed separately. Data Collection Manager DCM is required if you use timeclocks to input time. If you do not use timeclocks, DCM is not required. For more information about installing DCM in an Enterprise etime environment, refer to the Data Collection Manager Installation Guide. Enterprise etime Installation Guide for Windows 1-15

30 Chapter 1 Overview of Enterprise etime Network Requirements Your choice of network and connecting hardware can affect the performance of your client and server machines. The number of nodes on your network and the transfer throughput are some of the external factors that can affect the performance of the Enterprise etime system. If the application server, Background Processor, Enterprise etime Setup, database server, and DCM are installed on separate machines, they must be located in close proximity to each other and connect to the same backbone of a local area network (LAN) using T1 to T10 lines. All client PCs must support Transmission Control Protocol/Internet Protocol (TCP/IP) as the transport protocol and be able to connect to the Internet; they do not have to connect to the local area network. Minimum throughput is:! 56K dialup for Java Client machines! 28.8K dialup for Enterprise etime Professional - HTML Client machines although 56K is recommended for HTML Client machines that use Quick Time Stamp Database Server The database server contains a Microsoft SQL Server 2000 or Oracle database for all of your time and attendance data. The database software must be installed before you can install Enterprise etime components. For more information, refer to the Enterprise etime Database Installation Guide. Note: Although you can install Enterprise etime on the same machine as a SQL Server database, you should consider installing it on a separate machine, especially if the database is large. Oracle databases cannot be on the same machine as other Enterprise etime components ADP, Inc.

31 System Requirements System Requirements This section describes system requirements for the following Enterprise etime components:! Application Server! Background Processor! Enterprise etime Setup! Communication Application Server! Database Support! Java Client! Enterprise etime Professional - HTML Client! Citrix MetaFrame Support! Microsoft Terminal Services Support Application Server The following information summarizes the minimum hardware and software that the Enterprise etime application server requires. Minimum Hardware Requirements Hardware requirements for the application server are based on many variables, including the number of employees and users at a company. For most implementations, ADP recommends that you dedicate at least two application servers for the Enterprise etime application: one as a primary server and the other as a backup server. Enterprise etime Installation Guide for Windows 1-17

32 Chapter 1 Overview of Enterprise etime Software Requirements The following table lists the software requirements for a Windows application server. Item Operating system* Microsoft Task Scheduler Network protocol Web server software (HTTP daemon) JRE support Minimum Recommendations One of the following:! Microsoft Windows 2003 Server! Microsoft Windows 2000 Server (service pack 1 or 2)! Microsoft Windows NT 4.0 Server (service pack 6a or higher) Windows 2000, Windows 2003: Task Scheduler is part of the operating system. Windows NT: Task Scheduler is not installed with the operating system and must be installed separately. It is delivered with the editing tools in Microsoft Internet Explorer 5.5 or 6.0. TCP/IP One of the following:! Apache HTTPS or HTTP daemon (shipped with Enterprise etime)! Microsoft IIS 6.0 for Windows 2003 Server, HTTPS or HTTP! Microsoft IIS 4.0 for Windows NT, HTTPS or HTTP! Microsoft IIS 5.0 for Windows 2000, HTTPS or HTTP! Sun ONE Web Server 6.0, service pack 2, HTTPS or HTTP IBM v1.3.0 * ADP only supports service packs to the specific release. It does not support subsequent point releases or subsequent full releases by the vendor. For example, Windows NT 4.0 Service Pack 6a means that ADP will support Windows NT 4.0 and all service packs made to Windows NT 4.0 service pack 6a or higher, such as Windows NT or It does not imply that Windows NT 4.1 or any other version of Windows NT is supported. See page 2-5 for more information about supported Web servers ADP, Inc.

33 System Requirements Background Processor Typically, the Background Processor is installed on a separate machine. Hardware requirements are based on many variables, including the number of employees and users at a company as well as a company s business practices. Software requirements are as follows: Item Operating system Network protocol Minimum Recommendations Any of the following:! Microsoft Windows 2003! Microsoft Windows 2000! Microsoft Windows NT 4.0 Workstation (service pack 6a or higher) TCP/IP Enterprise etime Setup The following table lists the software requirements for Enterprise etime Setup: Item Operating system Network protocol Minimum Recommendations Any of the following:! Microsoft Windows 2003! Microsoft Windows 2000! Microsoft Windows NT 4.0 Workstation (service pack 6a or higher)! Microsoft Windows XP TCP/IP Enterprise etime Installation Guide for Windows 1-19

34 Chapter 1 Overview of Enterprise etime Communication Application Server The communication application server runs DCM. Minimum Hardware Requirements The following table lists hardware requirements: Item CPU Number of CPUs RAM Hard disk capacity Monitor screen settings Network ports Minimum Recommendations Intel-based 550 MHz Pentium One 256 MB minimum recommended, but varies depending on the particular environment and usage If available disk space falls below 75 MB, DCM logs a warning, but continues to operate. If available disk space falls below 50 MB, DCM logs an error and shuts down the core DCM applications through the Sentinel service. 800 x 600 pixels with 256 colors (SVGA) Note: Some screens do not display optimally at this resolution. If your DCM configuration includes Series 4000 devices and communication PCs that are outside a corporate firewall, you must open ports as follows:! 8889 to support DCM messaging between communication PCs.! 8888 and 80 to support data collection from Series 4000 devices or communication PCs that are outside your firewall to the communication PC within your firewall.! UDP for Series 400 and Series 500 Ethernet support. Other! CD-ROM reader (or access to one on the network)! Network card 1-20 ADP, Inc.

35 System Requirements Software Requirements The following table lists the software requirements for a communication application server: Item Operating system Network protocol Minimum Recommendations One of the following:! Microsoft Windows 2003 Server! Microsoft Windows 2000 (service pack 1 or higher)! Microsoft Windows NT 4.0 Workstation (service pack 6a or higher)! Microsoft Windows 98 TCP/IP Enterprise etime Installation Guide for Windows 1-21

36 Chapter 1 Overview of Enterprise etime Database Support The Enterprise etime software requires an Oracle or Microsoft SQL Server database as outlined in the following table: Item Requirement Oracle Oracle Server Oracle 8i (8.1.7) Enterprise Edition* Operating system! HP-UX (32- and 64-bit)! IBM AIX (32-bit or 64-bit)! Sun Solaris (32-bit)! Windows 2003 Server! Windows 2000 Server, service pack 1! Windows NT Server 4.0, service pack 6a* Supported middleware Net not required Microsoft SQL Server* Oracle 9i (9.2) Enterprise or Standard Editions! HP-UX (64-bit)! IBM AIX (64-bit)! Sun Solaris (64-bit)! Windows 2003 Server! Windows 2000 Server, service pack 1! Windows NT Server 4.0, service pack 6a* Microsoft SQL Server Microsoft SQL Server 2000 (also called SQL Server 8.0) Operating system! Windows NT 4.0 (service pack 6a or higher*)! Windows 2000 Server! Windows 2003 Server Supported middleware NetLib 8.0 (DBSetup applicationslib 8.0) not required Microsoft Database Engine (Kdemo) MSDE Server MSDE 2000 Operating system! Windows NT 4.0 Professional, with service pack 6a or higher*! Windows 2000 Professional or Server, with service pack 1! Windows XP Professional, Windows 2003 Server * Enterprise etime v5.0 uses function-based indexes to improve performance in some specific areas of the application and Oracle Standard edition does not support function-based indexes. If you are currently running Oracle Standard edition, you must upgrade to either Oracle Enterprise edition or Oracle 9.2. ADP supports only Microsoft service packs for the specific release. It does not support subsequent point releases or subsequent full releases by the vendor. For example, Windows NT 4.0 Service Pack 6a means that ADP will support Windows NT 4.0 and all service packs made for Windows NT 4.0 service pack 6a or higher, such as Windows NT or It does not imply that Windows NT 4.1 or any other version of Windows NT is supported ADP, Inc.

37 System Requirements Java Client Java Client configurations vary, depending on the type of user. For planning purposes, consider the following three types of client configurations:! Client desktop for employees and supervisors This desktop system runs browser-based Enterprise etime employee or supervisory functions. Functions include the Timecard, QuickNavs, and Reports.! Client desktop for an IS administrator This desktop system runs all browser-based Enterprise etime supervisory and configuration functions, as well as the Windows client-based Enterprise etime Setup.! Kdemo PCs This desktop or laptop system runs all portions of the product needed to demonstrate Enterprise etime, including the browser and Windows-based applications, the Kdemo database, embedded application server, and the Background Processor. An Internet Explorer or Netscape browser must be installed on all client PCs that will access the Enterprise etime system. See Chapter 8 for more information about installing and configuring browsers. Requirements The specifications outlined in the following table assume that Enterprise etime is one of several applications running on the Java client machines used to connect to the Enterprise etime application server. The minimum recommendations listed are needed to ensure a reasonable level of performance and user satisfaction. Although Enterprise etime may technically run on lower specifications than listed in the table, performance may not be acceptable for some users. Enterprise etime Installation Guide for Windows 1-23

38 Chapter 1 Overview of Enterprise etime Java Client Specifications Item Client Desktop for Employee/Supervisor Client Desktop for IS Administrator Kdemo PC Processor 200 MHz (minimum); 400 MHz 300 MHz 450 MHz (Intel Pentium)* (recommended) (minimum) (minimum) RAM 64 MB (minimum) 128 MB (minimum) 256 MB (minimum) Hard disk space 20 MB 90 MB 1 GB Operating system Browser support JRE support Other requirements Network bandwidth One of the following:! Windows 98! Windows 2000 Professional or Server, service pack 1! Windows NT Workstation or Server 4.0, service pack 6a or higher! Windows XP Professional! Windows 2003 Server One of the following:! Windows 2000 Professional or Server, service pack 1! Windows NT Workstation or Server 4.0, service pack 6a or higher! Windows XP Professional! Windows 2003 Server One of the following:! Microsoft Internet Explorer 5.0, 5.5, or 6.0 for nonsecure mode (HTTP)! Microsoft Internet Explorer 5.5, service pack 1, or 6.0 for secure mode (HTTPS)! Netscape Navigator 7.0 (not supported on Microsoft Windows XP clients) Sun v1.3.1_02 (default) or Sun v1.4.1_05 (shipped with Enterprise etime)! CD-ROM reader (or access to one on the network)! Adobe Acrobat Reader v4.05, v5.0 (v4.5 not supported)! Network card! Monitor: 1024 x 768, 16-bit resolution is recommended, although minimum resolution is 800 x 600, but requires the user to scroll. Note also that 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.! Non-persistent (session) cookies must be enabled! JavaScript must be enabled! Pop-up-blocking software must be configured to enable the Enterprise etime server to show pop-up windows! 56K dialup or Frame relay 56K (minimum)! Fractional T1 or T1 T3 (recommended) * When selecting processor speed, consider the processor recommended for operating system and hardware used. If you need to move or copy and paste an organization map that is on the order of 30,000 nodes or more, ADP recommends at least 512 MB of real memory and 256 of virtual memory. See page for more information. ADP supports only Microsoft service packs to the specific release. It does not support subsequent point releases or subsequent full releases by the vendor. For example, Windows NT 4.0 Service Pack 6a means that ADP will support Windows NT 4.0 and all service packs made to Windows NT 4.0 service pack 6a or higher, such as Windows NT or It does not imply support for Windows NT 4.1 or any other version of Windows NT ADP, Inc.

39 System Requirements Enterprise etime Professional - HTML Client The following table lists the minimum requirements for Enterprise etime Professional - HTML Client machines. Support Requirement Hardware Processor Processor speed Memory Hard disk space Display resolution Colors Intel or non-intel, Pentium level 133 MHz (minimum); 200 MHz or higher (recommended) 32 MB None Optimized for 800 x 600 or 640 x 480 with scroll bars Optimized for 256; 16 colors are supported but the colors may not be ideal Operating system! Microsoft Windows 98 SE! Microsoft Windows 2000 Workstation! Microsoft Windows NT 4.0 Workstation (service pack 5 or higher)! Microsoft Windows XP! Apple Macintosh* v8, v9, OSX Browser support The following off-the-shelf (not customized) browser support is required: Internet Explorer v5.0, v5.5, and v6.0 Netscape v7 Internet Explorer for v5.2 and higher Macintosh* Netscape for Macintosh* v7 only Adobe Acrobat Reader Adobe Acrobat Reader 4.05 or 5.0 must be installed on all browser clients that are used to access reports. For Mac OS, you may need to set up Adobe Acrobat Reader as the default application. Minimum network 28.8K dialup bandwidth * SSL/HTTPS is not supported on Macintosh systems or Netscape browsers. Enterprise etime Installation Guide for Windows 1-25

40 Chapter 1 Overview of Enterprise etime Supported Enterprise etime Professional - HTML Client Configurations Client Hardware Operating System Browser Intel Processor 133 MHz, 32 MB RAM Microsoft Windows MHz, 96 MB RAM Microsoft Windows 95 Microsoft Windows 98 SE Internet Explorer 5.5 Microsoft Windows 2000 Internet Explorer 5.5 Workstation (with service pack 1) 166 MHz, 32 MB RAM Microsoft Windows 98 SE Internet Explorer MHz, 64 MB RAM Microsoft Windows 98 SE Internet Explorer 5.5 (with service pack 2) 200 MHz, 64 MB RAM Microsoft Windows NT 4.0 Internet Explorer 4.0 (with service pack 6) 300 MHz, 128 MB RAM Microsoft Windows NT 4.0 Internet Explorer 5.5 (with service pack 5 and higher) Microsoft Windows XP Internet Explorer MHz, 256 MB RAM Microsoft Windows 2000 Workstation (with service pack 1) Internet Explorer 6.0 Netscape 7 Macintosh Processor imac Power PC G3, Mac OS 8.6 Internet Explorer MHz, 128 MB RAM imac Power PC G3, Mac OS Internet Explorer MHz, 64 MB RAM imac Power PC G3, 400 MHz, 128 MB RAM Mac OSX 10.1 Internet Explorer 5.2 Netscape ADP, Inc.

41 System Requirements Microsoft Terminal Services Support With Microsoft Terminal Services running on a Windows 2000-based server, all client application execution, data processing, and data storage occur on the server. When used with Enterprise etime, Terminal Services enable the following:! IS staff can remotely access Enterprise etime Setup! Low-end and diskless clients can access the Enterprise etime Web interface Requirements for Microsoft Terminal Services support are as follows: Client Operating System Microsoft NT Workstation v4.0 with service pack 6a or higher Client Applications! Internet Explorer 5.0! Netscape Navigator 7! Enterprise etime Setup 5.0 Microsoft 2000 Professional! Internet Explorer 5.5 with service pack 1 or higher! Netscape Navigator 7! Enterprise etime Setup 5.0 Microsoft XP Professional! Internet Explorer 6.0! Netscape Navigator 7 Server Operating System! Windows NT Terminal Server Edition 4.0 with service pack 6a or higher! Windows 2000 Server with service pack 1 or higher! Windows NT Terminal Server Edition 4.0 with service pack 6a or higher! Windows 2000 Server with service pack 1 or higher! Windows NT Terminal Server Edition 4.0 with service pack 6a or higher! Windows 2000 Server with service pack 1 or higher Enterprise etime Installation Guide for Windows 1-27

42 Chapter 1 Overview of Enterprise etime Citrix MetaFrame Support Enterprise etime v5.0 supports Citrix MetaFrame to improve client performance for customers who use non-pentium or low-end Pentium client machines. Citrix MetaFrame support also enables diskless clients to access Enterprise etime. Citrix MetaFrame requirements vary for each Enterprise etime component as follows: Support for Enterprise etime Setup MetaFrame Version Operating System V1.8 Windows Microsoft Windows NT Microsoft Windows 2000 XP Microsoft Windows XP Support for Web Server MetaFrame Version Operating System V1.8 Windows Microsoft Windows NT Microsoft Windows 2000 V1.1 UNIX Sun Solaris 8 IBM AIX v5.1 HP-UX v ADP, Inc.

43 Citrix MetaFrame Support Support for Web Client Client Operating System Microsoft NT Workstation v4.0 with service pack 6a Microsoft 2000 Professional with service pack 1 Microsoft XP Professional Client Applications Citrix Server Operating System! Internet Explorer 5.0 Microsoft NT! Netscape Navigator 7 Server v4.0 with! Enterprise etime Setup 5.0 service pack 6a Microsoft 2000 Server service pack 1! Internet Explorer 5.5 Microsoft NT! Netscape Navigator 7 Server v4.0 with! Enterprise etime Setup 5.0 service pack 6a Microsoft 2000 Server with service pack 1! Internet Explorer 5.5 Microsoft 2000! Netscape Navigator 7 Server with service pack 1 Citrix MetaFrame MetaFrame 1.8 for Windows NT, Terminal Server Edition MetaFrame 1.8 for Windows 2000 Server MetaFrame 1.8 for Windows NT, Terminal Server Edition MetaFrame 1.8 for Windows 2000 Server MetaFrame XPa and XPe for Windows Enterprise etime Installation Guide for Windows 1-29

44 Chapter 1 Overview of Enterprise etime OEM Licensed Products Enterprise etime uses the following original equipment manufacturer (OEM) licensed products: Vendor Adobe OpenText Apache Crystal Decisions DataDirect Globetrotter IBM i-net Software InstallShield itext Jbuilder KLGroup Macromedia (formerly Allaire Corp.) Microsoft mod_ssl OpenSSL Oracle Red Hat RSA Inc. Sun Microsystems Embedded Component Acrobat Reader AML Apache, XML4J, Log4J Crystal Reports Open Database Connectivity (ODBC) Drivers FlexLM JRE VA Server VA Smalltalk JDBC Drivers for Microsoft SQL Server (i-net SPRINTA) FOSITEX JDBC Text Driver for Microsoft Windows InstallShield Multi-Platform itext BoxLayout2.class UI Widgets JRun ADO, ADSI comctl32.dll, comctl32.ocx MSDE and associated tools mod_ssl OpenSSL JDBC Driver for Oracle cygwin1.dll Jsafe, C Library JRE 1-30 ADP, Inc.

45 Chapter 2 Preparing for Installation Before you install Enterprise etime, you must identify the type of security that you require and the type of Web server software that you want to use. You also need to collect information that the installation program will require. This chapter contains the following sections:! Security Considerations! Web Server Options! Gathering Installation Information! Reviewing the Preinstallation Requirements

46 Chapter 2 Preparing for Installation Security Considerations Security requirements are an important consideration for your Enterprise etime installation. Areas of particular importance are:! User Names and Passwords! Cookies! Web Server Security User Names and Passwords When Enterprise etime is installed, a number of system-level user names and passwords are set by default. After you install and configure the software, ADP strongly recommends that you change the passwords for these user accounts. See Chapter 7 for more information. Cookies A cookie is a small piece of information, often no more than a short session identifier, that the server sends to the browser when the browser connects for the first time. Enterprise etime relies on cookies for session management. It uses cookies to track the user s JRun user session ID and a Boolean logoff flag. The cookies are strictly session cookies and are not persistent, which means that they are not stored on the user s system. A cookie is simply loaded into the browser s cache and is active only as long as the session is active. After the user logs off, the cookie is gone. Enterprise etime cookies are not encrypted in any way. There is currently no other encryption of logon information, cookies, or other data, outside of an SSL installation. If it is necessary to have any HTTP request or response information encrypted during transmission, you should implement SSL with the Enterprise etime installation. 2-2 ADP, Inc.

47 Security Considerations If cookies are disabled, you can log on to Enterprise etime, but the default QuickNav will not load and the following error message is generated: Cannot retrieve data from server. To avoid this from happening, ensure that cookies are enabled in your browser. Web Server Security The default communication method that Enterprise etime uses is HyperText Transport Protocol (HTTP). With HTTP, much of the data between users and the system is text-based and, therefore, easily readable. If you require greater security, you can configure your Web server to use HyperText Transport Protocol Secure (HTTPS), which uses a Secure Sockets Layer (SSL) to encrypt the data with a digital certificate technique. Specific characteristics of each protocol include the following:! HTTP communication This technology uses the directory structure of the Web server content. Typically, all files in the same directory are configured with the same access rights. A requesting user provides a recognized user ID and password to gain access to files in a given directory. HTTP is supported by any standards-compliant Web browser. HTTP is the default setting of Enterprise etime.! HTTPS communication This technology uses public key cryptography. Certificate authorities (CAs) are used to verify the relationship between users and organizations.! Implementing SSL for Enterprise etime is a customer responsibility. Integrating Enterprise etime into an environment using SSL can have many different variables. You must understand the technology that you have chosen to use. Note: If you use Enterprise etime in an SSL 3.0 environment and you use an Internet Explorer browser, you must use Internet Explorer 5.5 with a minimum of service pack 2 or Internet Explorer 6.0 with a minimum of service pack 1. If you use Internet Explorer 5.5 or 6.0 with earlier service packs, you might encounter navigation errors. Enterprise etime Installation Guide for Windows 2-3

48 Chapter 2 Preparing for Installation If you choose to use SSL, the manner in which SSL is implemented for Enterprise etime differs depending on the type of Web server software used:! Apache with SSL You must obtain the key and certificate files and place them in a directory on the Enterprise etime application server before you install Enterprise etime. The Enterprise etime installation program requires that you enter the location of this directory. If selected, the Enterprise etime installation program properly configures Apache to run under SSL.! Microsoft IIS or Sun ONE with SSL You must configure SSL before you install Enterprise etime using the appropriate Web-server documentation. Note: SSL is not supported on Macintosh systems or Netscape browsers. 2-4 ADP, Inc.

49 Web Server Options Web Server Options Enterprise etime requires that Web server software, in regular or secure (SSL) mode, be installed on every Enterprise etime application server. Web server software cannot be installed on a standalone machine and mapped to application servers. The Enterprise etime installation program allows you to select any of the following Web servers:! Apache with or without SSL! Sun ONE with or without SSL! Microsoft IIS with or without SSL Note: SSL support is the customer s responsibility. The integration of Enterprise etime into a customer environment using SSL can have many different variables. Apache Web Server The Enterprise etime installation program will install Apache if selected during the installation procedure. Although it will also properly configure Apache to run under SSL, you must have the key and certificate files before installing Enterprise etime. Each machine must have its own key and certificate files and you must copy the files into a directory on the server. The installation procedure requires that you enter the location of these files. Microsoft IIS Web Server Microsoft Internet Information Server (IIS) is a Windows application that consists of FTP, , Web server, and news groups components. Enterprise etime uses only the Web server component. If you choose to use IIS, you must install it before you install Enterprise etime. Enterprise etime Installation Guide for Windows 2-5

50 Chapter 2 Preparing for Installation Note: ADP has tested Enterprise etime with an IIS installation that uses all default settings. Because of this, ADP recommends that you use default IIS settings. If you use IIS with non-default settings, you may need to experiment with the settings or contact TLM Support for assistance. For systems that use IIS, the Enterprise etime installation procedure makes the following settings: 1. Sets the wfc.bat file to point to the IIS service. 2. Creates an alias in the registry for online Help. 3. Creates an alias in the registry for LIB. 4. Sets up the JRun connectors by modifying certain parameters in CONNECT_INPUT.TXT and setting the scripts location to one of the following:! C:\Inetpub\scripts! The value of the \SCRIPTS string value under HKEY_LOCAL_MACHINE\Services\CurrentControlSet\W3SVC\ parameters\virtual Roots. 5. Runs <targetdir>\wfc\bin\connect_to.bat. 6. Sets IIS to start automatically. Using SSL Protocol If you want to run IIS with SSL protocol, you must copy the key and certificate files to the machine before you install Enterprise etime. Each machine must have its own key and certificate files. For more information, refer to the documentation supplied with the IIS software. 2-6 ADP, Inc.

51 Web Server Options IIS Requirements for Enterprise etime Enterprise etime requires that IIS have Read permission, Scripts enabled, Scripts folder present, anonymous access, and mappings for.asp and.asa files. You make these settings from the IIS Administration Web site: 1. Depending on your operating system, access the following:! On Windows NT systems, select Start > Programs > Administrative Tools > Computer Management.! On Windows 2000 or 2003 systems, select Start > Settings > Control Panel > Administrative Tools > Computer Management. 2. In the tree directory on the left, select Services and Applications > Internet Information Services, then right-click Default Web Site and select Properties. 3. In the Default Web Site Properties dialog box: a. Select the Home Directory tab and ensure that, at a minimum, Read permission is enabled. Also, ensure that Scripts are permitted. b. Select the Directory Security tab, click the Edit button under Anonymous Access and authentication control, then select the Anonymous access check box and click OK. c. Click OK again to exit. Using the IIS Lockdown Tool You can use the IIS lockdown tool for everything except the Scripts directory. Enterprise etime requires a Scripts directory for installation and run time of the JRun connectors. The Enterprise etime installation procedure creates a Scripts directory (adp\wfc\scripts) with Read privileges. After you install Enterprise etime, you can remove the Web server s Scripts directory, but you must leave the ADP Script directory intact. Enterprise etime Installation Guide for Windows 2-7

52 Chapter 2 Preparing for Installation Managing Virtual Directories With IIS, Enterprise etime sets up the following virtual directories: Virtual Directory wfc help lib relogon Points To C:\adp\wfc\html C:\adp\wfc\html\help C:\adp\wfc\lib C:\adp\wfc\html\relogon If you uninstall Enterprise etime, you must remove these directories manually. Change System Settings The Enterprise etime installation procedure supplies localhost as the site.eventmanager.hostname in the Event Manager tab of the system settings. If you use IIS with lockdown scripts, you must change this setting to the machine name of the Event Manager server. If you do not make this change, scheduled events will not work. To make this change: 1. Install Enterprise etime. 2. From the Enterprise etime navigation bar, select System Configuration > System Settings. 3. Select the Event Manager tab. 4. Change site.eventmanager.hostname from localhost to the name of the machine of the Event Manager server. Sun ONE Web Server If you choose Sun ONE Web server software, regular mode or SSL mode, you must install it before you install Enterprise etime. If you want to run your Web server with SSL protocol, you must install the key and certificate files before installing Enterprise etime. Each machine must have its own key and certificate files. Copy the files into a directory on the server. For more information, refer to the documentation supplied with the Sun ONE software. 2-8 ADP, Inc.

53 Gathering Installation Information Gathering Installation Information Because the Enterprise etime installation program requires you to enter information about the database and the application server, you should complete the following worksheet and refer to it during the installation procedure. See your system administrator if you need help locating this information. Enterprise etime Installation Guide for Windows 2-9

54 Chapter 2 Preparing for Installation Enterprise etime Installation Worksheet Database Information Character set The character set that Enterprise etime uses. Choose from:! Windows: the Microsoft standard, which includes the same printable characters as the ISO character set, as well as some nonstandard characters (recommended for Windows installations)! ISO: the global standard for communications and information exchange (required for UNIX installations) Database platform Oracle multischema database Database schema logon The database type used by the Enterprise etime applications. Choose from SQL Server or Oracle. Indicate whether or not you are using Oracle s multi-schema database functionality. User name and password of the owner of the database objects, for example, TKCSOWNER. If you are using Oracle s multischema database functionality, enter the logon information for each schema. Database logon The user name and password that your relational database requires, for example, SUPRKRON (not applicable if you are using Oracle s multi-schema database functionality). Database name The name of your database. ODBC data source name (DSN) All Enterprise etime components must use the same ODBC DSN. The application server, Background Processor, and Enterprise etime Setup installation programs request this information. If this is a new installation, you can enter any name because the name does not exist until the installation program creates it. Server name Name of the server on which the database is located. Port Port number on the database server that will accept JDBC connections. See your database administrator for the port number. Oracle SID (Oracle only) Enter the Oracle security identifier (SID), which identifies the database instance that is associated with the Oracle executable ADP, Inc.

55 Gathering Installation Information Windows Application Server Information Server name Server type The name of the machine on which the application server resides. The type of Web-server software. The Enterprise etime installation program will install:! Apache regular mode! Apache secure mode (SSL), which requires secure-mode certificate and key files You can also use the following Web servers, but they are not installed by the Enterprise etime installation program:! Microsoft IIS regular mode! Microsoft IIS secure mode (SSL)! Sun ONE regular mode! Sun ONE secure mode (SSL) Apache SSL certificate and key files You must install these applications (and SSL certificates if applicable) before you install Enterprise etime. If you request that the Enterprise etime installation program install Apache secure mode, enter the location of the certificate and key files. Note: SSL is not supported on Macintosh systems or Netscape browsers. Printer name The name of the local default printer. NT user name and password The Windows user name and password used to launch events (must have local administrator rights). Web-server software Background Processor The Web-server software and version numbers, if previously installed on the system; for example, IIS or Sun ONE. If no Webserver software is previously installed, the Enterprise etime installation program installs the Apache Web server. The amount of time in seconds that you want for the Background Processor s refresh interval. Destination Destination for software (drive). Enterprise etime Installation Guide for Windows 2-11

56 Chapter 2 Preparing for Installation Reviewing the Preinstallation Requirements Before you start the Enterprise etime installation program, review the following checklist to ensure that all preinstallation tasks are completed: " Install or upgrade the database as necessary. For more information, refer to Chapter 10 and the Enterprise etime Database Installation Guide. " Review the hardware and software requirements for the installation as outlined in Chapter 1 of this book. " Set the application server s display resolution to 1024 by 768 pixels (or a minimum of 800 by 600 pixels). " Identify the Web-server software to use with the application server and install it, if necessary: Web Sever Apache Apache with SSL Microsoft IIS Microsoft IIS with SSL Sun ONE Sun ONE with SSL Installation Requirements Installed by the Enterprise etime installation program. Installed by the Enterprise etime installation program, but you must enter the location of the certificate and key files. Must be installed before you install Enterprise etime. Must be installed before you install Enterprise etime. " Stop all background processes. " Check disk space ADP, Inc.

57 Chapter 3 Installing Enterprise etime Many of the Enterprise etime components depend on other system components. If you select a component for which another component is required, the required component is selected automatically to ensure that a valid configuration is maintained. The Enterprise etime installation program delivers the core components that are required for an Enterprise etime system on a Windows machine. The program prompts you to select the Enterprise etime components to deliver, the delivery location, and the configuration. The installation program then delivers the specified components to your computer. Because some sites require multiple dedicated machines for each Enterprise etime component and other sites require multiple components to reside on the same machine, the installation program allows you to choose from a number of options. This chapter describes each installation option. It contains the following sections:! Starting the Installation Program! Installing a Single Server! Using the Custom Option! Installing the Application Server! Installing the Background Processor! Installing Enterprise etime Setup! Installing Kdemo! Installing Enterprise Scheduler

58 Chapter 3 Installing Enterprise etime If you install one of these Enterprise etime components and later need to install another component on the same machine, you must uninstall the first component and then use the Custom option to install all the components required on the machine. You can, however, install Enterprise Scheduler at a later date without uninstalling other Enterprise etime components. For more information, see page Typically, you will use the Single Server option to install the application server, Background Processor, and the Enterprise etime Setup on the first machine. Then you can install these same components individually on other machines. Note: Although you can install Enterprise etime on the same machine as a SQL Server database, you should consider installing it on a separate machine, especially if the database is large. Oracle databases cannot be on the same machine as other Enterprise etime components. For more information, refer to the Enterprise etime Database Installation Guide. Some components of Enterprise etime are OEM-licensed products that are included with the ADP software. In most cases, these installation programs run within the Enterprise etime installation program. Note: Enterprise etime 5.0 installs JRun 4.0, which does not have a graphical user interface. If you need to access JRun (to change the default logout time or to change a network password, for example), you must use the command line. If JRun 4.0 from Macromedia is installed on your machine, you must uninstall it manually before you install Enterprise etime. If you do not, the Enterprise etime installation procedure will not run properly. 3-2 ADP, Inc.

59 Starting the Installation Program Starting the Installation Program To start the Enterprise etime installation program: 1. Insert the Enterprise etime CD into the CD-ROM drive and select Start > Run. 2. In the Run dialog box, select the CD device, for example, D:\. 3. Select Launch.exe and click OK. The Product Installation dialog box appears. This dialog box has five buttons:! Install Products Displays the names of the applications that you can install! Browse Contents Displays the files that the installation programs use! View ADP Web Site Opens the ADP Web site ( in your default browser! Contact ADP Displays addresses, telephone numbers, and URLs that you can use to contact ADP! Exit 4. Click Install Products. 5. In the next dialog box, click Enterprise etime Applications. The Welcome dialog box appears. Click Next. 6. In the Select Language dialog box, select the language of the Enterprise etime user interface from English or Spanish; click Next. Note: If you are running an English version of the Windows NT operating system and you select a non-english language for the Enterprise etime system, then some button labels will appear in English; for example, OK, Cancel, Yes, and No. These buttons are labeled by the operating system based on the operating system version itself; not on the regional settings. See Chapter 5 for more information about non-english installations. If necessary, you can change these settings from the Enterprise etime System Settings after you install the product. For more information, refer to the Enterprise etime System Administrator s Guide. Enterprise etime Installation Guide for Windows 3-3

60 Chapter 3 Installing Enterprise etime 7. In the Choose Destination Location dialog box, do one of the following:! Click Next to accept the default destination folder (C:\ADP).! Click Browse to select a new destination folder, then click Next. 8. In the Setup Type dialog box, select the component you want to install, then click Next:! Application Server Installs only the application server! Background Processor Installs only the Background Processor! Custom Lets you install more than one component on one machine! Kdemo Installs only the Kdemo demonstration software! Setup Applications Installs only Enterprise etime Setup! Single Server Installs the application server, Background Processor, and Enterprise etime Setup on a single machine Note: If you install one component and later need to install another component on the same machine, you must uninstall the first component and then use the Custom option to install all the components required on the machine. At this point, the installation procedure varies, depending on the selections that you make in the Setup Type dialog box.! If you selected Single Server, go to the next section, Installing a Single Server.! If you selected Custom, which enables you to install more than one component on a single machine, go to page 3-17.! If you selected the application server, go to page 3-18.! If you selected the Background Processor, go to page 3-30.! If you selected Setup Applications, go to page 3-37.! If you selected Kdemo, go to page ADP, Inc.

61 Installing a Single Server Installing a Single Server The Single Server option installs the application server, Background Processor, and Enterprise etime Setup on a single machine. When you install the application server, the installation program also installs the Callable Totalizer. After completing the steps described in Starting the Installation Program on page 3-3 and using the installation worksheet that you completed on page 2-10, provide the data requested in the following dialog boxes. Click Next after you input the required information. 1. Select Program Folder Do one of the following:! Click Next to accept the default program folder (ADP Enterprise etime).! Enter a new program folder name and click Next. The program folder name is the application path name on the Start menu. 2. Choose Java Plugin version You must select one of the following:! JRE 1.3 U.S. English (default)! JRE 1.3 International! JRE 1.4 U.S. English! JRE 1.4 International The selection that you make here determines which JRE plug-in is downloaded and installed on each client PC that accesses the system. For more information, see page 8-5. Although the international version of the plug-in works for all languages including U.S. English, it is larger and slower to download than the U.S. English version. If you are only using U.S. English, you can avoid the overhead by selecting the U.S. English version. The International version, however, is required for systems that use anything other than standard U.S. English and date formats. After you install a version of the plug-in on your system, the only way to switch versions is to manually uninstall the plug-in from your client machines and reconnect to a server that contains the other version of the plug-in. The system will download a new version of the plug-in from the new server. Enterprise etime Installation Guide for Windows 3-5

62 Chapter 3 Installing Enterprise etime 3. Choose Character Set In the Character Set dialog box, select the character set for Enterprise etime to use. You can select from:! Windows: The Microsoft standard, which includes the same printable characters as the ISO character set, as well as some Windows-specific characters. This is the recommended setting for installations that only use Windows application servers.! ISO: The global standard for communications and information exchange. This the required setting if you are installing a Windows companion server for use with a UNIX application server. 4. Choose Database Platform Select the database platform that your Enterprise etime application uses, then click Next.! SQL Server 2000! Oracle Note: The database software must be installed before you install Enterprise etime components. Although you can install Enterprise etime on the same machine as a SQL Server database, you should consider installing it on a separate machine, especially if the database is large. Oracle databases cannot be on the same machine as other Enterprise etime components. 5. Configure Multi-Schema Database Support If you selected Oracle in the Choose Database Platform dialog box, the following message appears: If you are using Oracle s multi-schema database option, click Yes; otherwise click No. For more information about the multi-schema database option, refer to the Enterprise etime Database Installation Guide. 3-6 ADP, Inc.

63 Installing a Single Server 6. Choose Web Server Platform Select one of the Web servers listed. The installation program responds differently depending on the selection that you make in this dialog box:! Apache The Enterprise etime installation program installs Apache Web server software if it is not already installed on the machine.! Apache with SSL support The Enter SSL Certificate File dialog box appears. You must enter the location of the SSL certificate file here.! Sun ONE The Enterprise etime installation program does not install Sun ONE Web-server software. If you use Sun ONE, you must install it on your machine and ensure that it is running before you install Enterprise etime. For more information, see page 2-8.! Sun ONE with SSL support Secure mode (SSL support) requires certificates in order to work. If you do not have the required certificates for secure mode, select regular mode. SSL is not supported if you use Netscape or Macintosh systems for your Web browser. For more information about SSL and other security options, see page 2-10.! Microsoft IIS The Enterprise etime installation program does not install Microsoft IIS Web-server software. If you use IIS, you must install it on your machine and ensure that it is running before you install Enterprise etime. For more information, see page 2-5. If IIS is installed on your machine and you select IIS in the Choose Web Server dialog box, the Select IIS Web Site dialog box appears. If IIS is not present on your machine, the installation program generates an error message and will not let you continue with the installation.! Microsoft IIS with SSL support Secure mode (SSL support) requires certificates in order to work. If you do not have the required certificates for secure mode, select regular mode. SSL is not supported if you use Netscape or Macintosh systems for your Web browser. For more information about SSL and other security options, see page Enterprise etime Installation Guide for Windows 3-7

64 Chapter 3 Installing Enterprise etime 7. Enter Application Server Name Enter the name of the machine on which the application server is installed. 8. If you selected Sun ONE or Sun ONE with SSL Support in the Choose Web Server Platform dialog box, additional dialog boxes open:! If you selected Sun ONE, an additional Application Server Name dialog box appears. You must enter the name of your Sun ONE Web Server service here. If you do not provide this information, or if Sun ONE is not present on your machine, the installation program generates an error message and does not let you continue with the installation.! If you selected Sun ONE with SSL support, two Enter Domain Name dialog boxes open. You must enter the fully qualified domain name or IP address in the first dialog box and you must enter the name of your Sun ONE Web Server service in the second dialog box. If you do not provide this information, the installation program generates an error message and does not let you continue with the installation. 9. Enter Domain Name If you selected Microsoft IIS with SSL support in step 7, you need to enter the fully qualified domain name or IP address of the application server. 3-8 ADP, Inc.

65 Installing a Single Server 10. Enter ODBC Data Source Name The same ODBC data source name is required by the application server, Background Processor, and Enterprise etime Setup. If you are using DCM, you must also use the same data source name that you use for Enterprise etime. If you have not installed any Enterprise etime components, you can enter any name here because the name does not exist until the installation program creates it. After you select a name, write it down because you must enter the same ODBC data source name for all components that request it. If you already installed other components, you must enter the same ODBC data source name for all components. 11. Enter Database Server Name Enter the name of the machine on which the database software is installed. Enterprise etime Installation Guide for Windows 3-9

66 Chapter 3 Installing Enterprise etime 12. Select Database Server Time Zone Select the time zone in which the database server resides from the drop-down list. Although the Enterprise etime system uses a complex algorithm to generate time stamps, the most important component of this algorithm is the time of the database server. If you are in a different time zone than the database server, the system converts the database server s time to your local time zone when it displays the time on your browser. Users cannot change the time recorded by adjusting the time on their PCs. 13. Enter Port Number The default port number is 1433 for a SQL Server 2000 database and1521 for an Oracle database. Because the port number can vary from company to company, however, ask your network or system administrator for this information ADP, Inc.

67 Installing a Single Server 14. Enter Oracle SID If you are using an Oracle database, you must enter the Oracle SID, which identifies the database instance that is associated with the Oracle executable. 15. Enter Database Schema User Name and Password If you are using an Oracle database, the following dialog box appears. Enter the user name and password of the owner of the database objects. The information that you enter here depends on whether you are using Oracle s multi-schema database capabilities or not.! In a multi-schema database environment, enter the logon that you created for the schema. See the Enterprise etime Database Installation Guide for more information.! In a non-multi-schema database environment, this logon is typically TKCSOWNER. Enterprise etime Installation Guide for Windows 3-11

68 Chapter 3 Installing Enterprise etime 16. Enter Database User Name and Password If you are using an Oracle database without the multi-schema database capabilities, the following dialog box appears next. You must enter the user name and password that the application will use to connect to the database. This should be a different logon than the schema owner, for example, SUPRKRON. However, if you are installing the application server to point to an archive database and you plan to use Enterprise Archiver on the application server, you must use TKCSOWNER as the database user name in this dialog box and when you install Enterprise Archiver. 17. Enter Database Name If you are using SQL Server, you must enter the name of the database in this dialog box. See your database administrator if you do not know the name of the database. This dialog box does not appear if you are using an Oracle database ADP, Inc.

69 Installing a Single Server 18. Enter Database User Name and Password If you are using SQL Server, you must enter the appropriate logon information for your database in the following dialog box. ADP recommends that you use SUPRKRON as the database user name. However, if you are installing the application server to point to an archive database and you plan to use Enterprise Archiver on the application server, you must use TKCSOWNER as the database user name in this dialog box and when you install Enterprise Archiver. 19. Enter Printer Name Enter the name of the local default printer to be used by the application server. Although you can later configure printers with the Enterprise etime Setup component, the printer that you enter here becomes the default for the Event Scheduler or other application server processes. Enterprise etime Installation Guide for Windows 3-13

70 Chapter 3 Installing Enterprise etime 20. Enter User Name and Password Enter your full Windows user name and password, then click Next. If you use domain security, enter the domain name before your user name. For example, enter your_domain\your user_name in the User Name box. This user requires local administrator rights, and the password cannot be null (blank). Note: If you do not enter a user name and password here, you will not be able to schedule reports or any other event such as import. 21. Enter Background Processor Interval Enter the amount of time in seconds that the Background Processor is idle between processing ADP, Inc.

71 Installing a Single Server 22. Install Scheduler The following message box appears next. If you have purchased the advanced Enterprise Scheduler product, click Yes; otherwise click No. You will need the appropriate licenses in order to activate the product. Note: If you install Enterprise Scheduler at a later date, you can do so without reinstalling Enterprise etime. See page 3-51 for more information. 23. Start Copying Files Review your settings in the Start Copying Files dialog box before you continue with the installation program. If your settings are not correct, click Back until you locate the dialog box that you need to correct. If your settings are correct, click Next; the Enterprise etime installation program installs the components. Although the installation program displays its progress as it installs the requested components, little user interaction occurs. On a Windows NT 4.0 system that has never had ADSI installed, ADSI is installed first. On a Windows 2000 or Windows 2003 system, ADSI is included with the operating system and is not installed by the Enterprise etime installation program. Then, the files for the required Enterprise etime components are installed in the following order:! Java Runtime Environment (JRE)! Background Processor executable files! Callable Totalizer executable files! Enterprise etime Setup executable files! ODBC driver files! JRun application server Enterprise etime Installation Guide for Windows 3-15

72 Chapter 3 Installing Enterprise etime If your machine has no Web-server software installed or if you identified Apache Web server, the installation program installs the Apache Web-server program files. If Sun ONE or Microsoft IIS Web-server software is already installed on your machine, the installation program does not install Apache. The final components to be installed are the Enterprise etime application server files. Then you will see messages that the installation program is:! Modifying Apache configuration! Modifying ADP configuration! Creating Program Shortcuts 24. InstallShield Wizard Complete When the installation is finished, the InstallShield Wizard Complete dialog box appears. You must restart your computer to complete the installation. Caution: Before you reboot, make sure no other processes are running. If you are ready to reboot your system, select Yes, I want to restart my computer now and click Finish. If you need to stop other processes, select No, and reboot your machine after you stop the other processes. 25. After you reboot your system, you must stop and start the Enterprise etime application server manually by clicking the Stop icon and then clicking the Start icon. For more information, refer to Chapter ADP, Inc.

73 Using the Custom Option Using the Custom Option The Custom option enables you to install more than one Enterprise etime component on the same machine. Select as many of the following as necessary, then click Next.! Background Processor! Setup Applications! Demo Environment (Kdemo)! Application Server After completing the steps described in Starting the Installation Program on page 3-3 and using the installation worksheet that you completed on page 2-10, provide the data requested in the dialog boxes that appear. Click Next after you input the required information. The dialog boxes that appear in a Custom installation depend on the options that you select. For example, if you choose to install the Background Processor and Setup Applications, you will see all the dialog boxes that are described in Installing the Background Processor and Installing Enterprise etime Setup. If you need more information about a specific dialog box, refer to the appropriate topic. Enterprise etime Installation Guide for Windows 3-17

74 Chapter 3 Installing Enterprise etime Installing the Application Server This section describes how to install the application server separately, without the other components that are listed in the installation program. When you install the application server, the installation program also installs the Callable Totalizer. After completing the steps described in Starting the Installation Program on page 3-3 and using the installation worksheet that you completed on page 2-10, provide the data requested in the following dialog boxes. Click Next after you input the required information. 1. Select Program Folder Do one of the following:! Click Next to accept the default program folder (ADP Enterprise etime).! Enter a new program folder name and click Next. The program folder name is the application path name on the Start menu. 2. Choose Java Plugin version You must select one of the following:! JRE 1.3 U.S. English (default)! JRE 1.3 International! JRE 1.4 U.S. English! JRE 1.4 International The selection that you make here determines which JRE plug-in is downloaded and installed on each client PC that accesses the system. For more information, see page 8-5. Although the international version of the plug-in works for all languages including U.S. English, it is larger and slower to download than the U.S. English version. If you are only using U.S. English, you can avoid the overhead by selecting the U.S. English version. The International version, however, is required for systems that use anything other than standard U.S. English and date formats. After you install a version of the plug-in on your system, the only way to switch versions is to manually uninstall the plug-in from your client machines and reconnect to a server that contains the other version of the plug-in. The system will download a new version of the plug-in from the new server ADP, Inc.

75 Installing the Application Server 3. Choose Character Set In the Character Set dialog box, select the character set for Enterprise etime to use. You can select from:! Windows: The Microsoft standard, which includes the same printable characters as the ISO character set, as well as some Windows-specific characters. This is the recommended setting for installations that only use Windows application servers.! ISO: The global standard for communications and information exchange. This the required setting if you are installing a Windows companion server for use with a UNIX application server. 4. Choose Database Platform Select the database platform that your Enterprise etime application uses, then click Next.! SQL Server 2000! Oracle Note: The database software must be installed before you install Enterprise etime components. Although you can install Enterprise etime on the same machine as a SQL Server database, you should consider installing it on a separate machine, especially if the database is large. Oracle databases cannot be on the same machine as other Enterprise etime components. 5. Configure Multi-Schema Database Support If you selected Oracle in the Choose Database Platform dialog box, the following message appears: If you are using Oracle s multi-schema database option, click Yes; otherwise click No. For more information about the multi-schema database option, refer to the Enterprise etime Database Installation Guide. Enterprise etime Installation Guide for Windows 3-19

76 Chapter 3 Installing Enterprise etime 6. Choose Web Server Platform Select one of the Web servers listed. The installation program responds differently depending on the selection that you make in this dialog box:! Apache The Enterprise etime installation program installs Apache Web server software if it is not already installed on the machine.! Apache with SSL support The Enter SSL Certificate File dialog box appears. You must enter the location of the SSL certificate file here.! Sun ONE The Enterprise etime installation program does not install Sun ONE Web-server software. If you use Sun ONE, you must install it on your machine and ensure that it is running before you install Enterprise etime. For more information, see page 2-8.! Sun ONE with SSL support Secure mode (SSL support) requires certificates in order to work. If you do not have the required certificates for secure mode, select regular mode. SSL is not supported if you use Netscape or Macintosh systems for your Web browser. For more information about SSL and other security options, see page 2-5.! Microsoft IIS The Enterprise etime installation program does not install Microsoft IIS Web-server software. If you use IIS, you must install it on your machine and ensure that it is running before you install Enterprise etime. For more information, see page 2-5. If IIS is installed on your machine and you select IIS in the Choose Web Server dialog box, the Select IIS Web Site dialog box appears. If IIS is not present on your machine, the installation program generates an error message and will not let you continue with the installation.! Microsoft IIS with SSL support Secure mode (SSL support) requires certificates in order to work. If you do not have the required certificates for secure mode, select regular mode. SSL is not supported if you use Netscape or Macintosh systems for your Web browser. For more information about SSL and other security options, see page ADP, Inc.

77 Installing the Application Server 7. Enter Application Server Name Enter the name of the machine on which the application server is installed. If you selected Sun ONE or Sun ONE with SSL Support in the Choose Web Server Platform dialog box, additional dialog boxes open:! If you selected Sun ONE, an additional Application Server Name dialog box appears. You must enter the name of your Sun ONE Web Server service here. If you do not provide this information, or if Sun ONE is not present on your machine, the installation program generates an error message and does not let you continue with the installation.! If you selected Sun ONE with SSL support, two Enter Domain Name dialog boxes open. You must enter the fully qualified domain name or IP address in the first dialog box and you must enter the name of your Sun ONE Web Server service in the second dialog box. If you do not provide this information, the installation program generates an error message and does not let you continue with the installation. 8. Enter Domain Name If you selected Microsoft IIS with SSL support in step 7, you need to enter the fully qualified domain name or IP address of the application server. Enterprise etime Installation Guide for Windows 3-21

78 Chapter 3 Installing Enterprise etime 9. Enter ODBC Data Source Name The same ODBC data source name is required by the application server, Background Processor, and Enterprise etime Setup. If you are using DCM, you must also use the same data source name that you use for Enterprise etime. If you have not installed any Enterprise etime components, you can enter any name here because the name does not exist until the installation program creates it. After you select a name, write it down because you must enter the same ODBC data source name for all components that request it. If you already installed other components, you must enter the same ODBC data source name for all components. 10. Enter Database Server Name Enter the name of the machine on which the database software is installed ADP, Inc.

79 Installing the Application Server 11. Select Database Server Time Zone Select the time zone in which the database server resides from the drop-down list. Although the Enterprise etime system uses a complex algorithm to generate time stamps, the most important component of this algorithm is the time of the database server. If you are in a different time zone than the database server, the system converts the database server s time to your local time zone when it displays the time on your browser. Users cannot change the time recorded by adjusting the time on their PCs. 12. Enter Port Number The default port number is 1433 for a SQL Server 2000 database and 1521 for an Oracle database. Because the port number can vary from company to company, however, ask your network or system administrator for this information. Enterprise etime Installation Guide for Windows 3-23

80 Chapter 3 Installing Enterprise etime 13. Enter Oracle SID If you are using an Oracle database, you must enter the Oracle SID, which identifies the database instance that is associated with the Oracle executable. 14. Enter Database Schema User Name and Password If you are using an Oracle database, the following dialog box appears. Enter the user name and password of the owner of the database objects. This value is put into the Windows registry and is used by the Background Processor. The information that you enter here depends on whether you are using Oracle s multi-schema database capabilities or not.! In a multi-schema database environment, enter the logon that you created for the schema. See the Enterprise etime Database Installation Guide for more information.! In a non-multi-schema database environment, this logon is typically TKCSOWNER ADP, Inc.

81 Installing the Application Server 15. Enter Database User Name and Password If you are using an Oracle database without the multi-schema database capabilities, the following dialog box appears next. You must enter the user name and password that the application will use to connect to the database. This should be a different logon than the schema owner, for example, SUPRKRON. However, if you are installing the application server to point to an archive database and you plan to use Enterprise Archiver on the application server, you must use TKCSOWNER as the database user name in this dialog box and when you install Enterprise Archiver. Enterprise etime Installation Guide for Windows 3-25

82 Chapter 3 Installing Enterprise etime 16. Enter Database Name If you are using a SQL Server database, you must enter the name of the database in this dialog box. See your database administrator if you do not know the name of the database. This dialog box does not appear if you are using an Oracle database. 17. Enter Database User Name and Password If you are using SQL Server, you must enter the appropriate logon information for your database in the following dialog box. ADP recommends that you use SUPRKRON as the database user name. However, if you are installing the application server to point to an archive database and you plan to use Enterprise Archiver on the application server, you must use TKCSOWNER as the database user name in this dialog box and when you install Enterprise Archiver ADP, Inc.

83 Installing the Application Server 18. Enter Printer Name Enter the name of the local default printer to be used by the application server. Although you can later configure printers with the Enterprise etime Setup component, the printer that you enter here becomes the default for the Event Scheduler or other application server processes. 19. Enter User Name and Password Enter your full Windows user name and password, then click Next. If you use domain security, enter the domain name before your user name. For example, enter your_domain\your user_name in the User Name box. This user requires local administrator rights, and the password cannot be null (blank). Note: If you do not enter a user name and password here, you will not be able to schedule reports or any other event such as import. Enterprise etime Installation Guide for Windows 3-27

84 Chapter 3 Installing Enterprise etime 20. Install Scheduler The following message box appears next. If you have purchased the advanced Enterprise Scheduler product, click Yes; otherwise click No. You will need the appropriate licenses in order to activate the product. Note: If you decide to install Enterprise Scheduler at a later date, you can do so without reinstalling Enterprise etime. See page 3-51 for more information. 21. Start Copying Files Review your settings in the Start Copying Files dialog box before you continue with the installation program. If your settings are not correct, click Back until you locate the dialog box that you need to correct. If your settings are correct, click Next. Although the installation program displays its progress as it installs the requested components, no user interaction is necessary.! The Java Runtime Environment (JRE) is installed first.! The Background Processor executable files are installed.! The Callable Totalizer executable files are installed.! The ODBC drivers files are installed.! The JRun application server is installed.! If your machine has no Web-server software or if you identified the Apache Web server, the installation program installs Apache Web server. If you have an Sun ONE or Microsoft IIS Web server installed on your machine, the installation program does not install Apache.! The final components to be installed are the Enterprise etime Server program files ADP, Inc.

85 Installing the Application Server Then you will see messages that the installation program is modifying:! Apache configuration! JRun configuration! ADP configuration 22. InstallShield Wizard Complete When the installation is finished, the InstallShield Wizard Complete dialog box appears. You must restart your computer to complete the installation. Caution: Before you reboot, make sure no other processes are running. If you are ready to reboot your system, select Yes, I want to restart my computer now and click Finish. If you need to stop other processes, select No, and reboot your machine after you stop the other processes. 23. After you reboot your system, you must stop and start Enterprise etime manually by clicking the Stop icon and then clicking the Start icon. For more information about starting Enterprise etime, refer to Chapter 6. Enterprise etime Installation Guide for Windows 3-29

86 Chapter 3 Installing Enterprise etime Installing the Background Processor This section describes how to install only the Background Processor. After completing the steps described in Starting the Installation Program on page 3-3 and using the installation worksheet that you completed on page 2-10, provide the data requested in the following dialog boxes. Click Next after you input the required information. 1. Choose Database Platform Select the database platform that your Enterprise etime application uses, then click Next.! SQL Server 2000! Oracle Note: The database software must be installed before you install Enterprise etime components. Although you can install Enterprise etime on the same machine as a SQL Server database, you should consider installing it on a separate machine, especially if the database is large. Oracle databases cannot be on the same machine as other Enterprise etime components. 2. Application Server Protocol Select the protocol used by your application server: Secure Hypertext Transfer Protocol, HTTPS (SSL) or Hypertext Transfer Protocol, HTTP (non-ssl). HTTPS is the Secure Sockets Layer (SSL), which encrypts and decrypts user page requests, as well as the pages that the Web server returns. Note: SSL is not supported if you use Netscape or Macintosh systems for your Web browsers ADP, Inc.

87 Installing the Background Processor 3. Enter Application Server Name Enter the name of the machine on which the application server is installed. 4. Enter ODBC Data Source Name The same ODBC data source name is required by the application server, Background Processor, and Enterprise etime Setup. If you are using DCM, you must also use the same data source name that you use for Enterprise etime. If you have not installed any Enterprise etime components, you can enter any name here because the name does not exist until the installation program creates it. After you select a name, write it down because you must enter the same ODBC data source name for all components that request it. If you already installed other components, you must enter the same ODBC data source name for all components. Enterprise etime Installation Guide for Windows 3-31

88 Chapter 3 Installing Enterprise etime 5. Enter Database Server Name Enter the name of the machine on which the database software is installed. 6. Enter Port Number The default port number is 1433 for a SQL Server 2000 database and 1521 for an Oracle database. Because the port number can vary from company to company, however, ask your network or system administrator for this information ADP, Inc.

89 Installing the Background Processor 7. Enter Oracle SID If you are using an Oracle database, you must enter the Oracle SID, which identifies the database instance that is associated with the Oracle executable. 8. Enter Database Schema User Name and Password If you are using an Oracle database, the following dialog box appears. Enter the user name and password of the owner of the database objects. This value is put into the Windows registry and is used by the Background Processor. The information that you enter here depends on whether you are using Oracle s multi-schema database capabilities or not.! In a multi-schema database environment, enter the logon that you created for the schema. See the Enterprise etime Database Installation Guide for more information.! In a non-multi-schema database environment, this logon is typically TKCSOWNER. Enterprise etime Installation Guide for Windows 3-33

90 Chapter 3 Installing Enterprise etime 9. Enter Database User Name and Password If you are not using Oracle s multi-schema database capabilities, you must enter the user name and password that you would like the application to use to connect to the database. This should be a different logon than the schema owner, for example, SUPRKRON. However, if you are installing the application server to point to an archive database and you plan to use Enterprise Archiver on the application server, you must use TKCSOWNER as the database user name in this dialog box and when you install Enterprise Archiver. 10. Enter Database Name If you are using a SQL Server, you must enter the name of the database in this dialog box. See your database administrator if you do not know the name of the database. This dialog box does not appear if you are using an Oracle database ADP, Inc.

91 Installing the Background Processor 11. Enter Background Processor Interval Enter the amount of time in seconds that the Background Processor is idle between processing. 12. Start Copying Files Review your settings in the Start Copying Files box before you continue with the installation program. If your settings are not correct, click Back until you locate the dialog box that you need to correct. If your settings are correct, click Next. Although the installation program displays its progress as it installs the requested components, little user interaction occurs.! The Background Processor executable files are installed.! The Background Processor is configured as a service.! The ODBC driver files are installed. 13. InstallShield Wizard Complete When the installation is finished, the InstallShield Wizard Complete dialog box appears. You must restart your computer to complete the installation. Caution: Before you reboot, make sure no other processes are running. If you are ready to reboot your system, select Yes, I want to restart my computer now and click Finish. If you need to stop other processes, select No, and reboot your machine after you stop the other processes. 14. After you reboot your system, you must stop and start Enterprise etime manually by clicking the Stop icon and then clicking the Start icon. For more information about starting Enterprise etime, refer to Chapter 6. Enterprise etime Installation Guide for Windows 3-35

92 Chapter 3 Installing Enterprise etime Installing Additional Background Processors After you install a primary Background Processor, you can use the Background Processor Registry Editor to install one or more additional Background Processors on the same machine. The Background Processor Registry Editor executable file, BGPRegEdit.exe, is delivered by the installation program in the same directory as the primary Background Processor. The default location is C:\adp\wfc\bgp. To access the Background Processor Registry Editor: 1. Start Windows Explorer. 2. Double-click adp\wfc\bgpregedit.exe. Follow the online Help that is available through the Background Processor Registry Editor user interface. The online Help also explains how you can use the Background Processor Registry Editor to remove secondary Background Processors, edit the parameters of an existing Background Processor, or change the URL of the application server. You can also use the Background Processor Registry Editor to change the password of the Totalizer. For more information, see Chapter ADP, Inc.

93 Installing Enterprise etime Setup Installing Enterprise etime Setup Enterprise etime Setup is a Windows component that does not have a browser interface. The Enterprise etime Setup component must be installed on at least one Windows PC connected to the local area network. In most cases, you will install Enterprise etime Setup on a relatively small number of machines, compared to the overall user population. Typical users who require Enterprise etime Setup include:! System administrators from your IS staff! ADP implementation staff! For some companies, a small number of payroll staff After completing the steps described in Starting the Installation Program on page 3-3 and using the installation worksheet that you completed on page 2-10, provide the data requested in the following dialog boxes. Click Next after you input the required information. 1. Select Program Folder Do one of the following:! Click Next to accept the default program folder (ADP Enterprise etime).! Enter a new program folder name and click Next. The program folder name is the application path name on the Start menu. 2. Choose Database Platform Select the database platform that your Enterprise etime application uses, then click Next.! SQL Server 2000! Oracle Note: The database software must be installed before you install Enterprise etime components. Although you can install Enterprise etime on the same machine as a SQL Server database, you should consider installing it on a separate machine, especially if the database is large. Oracle databases cannot be on the same machine as other Enterprise etime components. Enterprise etime Installation Guide for Windows 3-37

94 Chapter 3 Installing Enterprise etime 3. Application Server Protocol Select the protocol used by your application server: Secure Hypertext Transfer Protocol, HTTPS (SSL) or Hypertext Transfer Protocol, HTTP (non-ssl). HTTPS is the Secure Sockets Layer (SSL), which encrypts and decrypts user page requests, as well as the pages that the Web server returns. 4. Enter Application Server Name Enter the name of the machine on which the application server is installed. Note: SSL is not supported if you use Netscape or Macintosh systems for your Web browsers. 5. Enter ODBC Data Source Name The same ODBC data source name is required by the application server, Background Processor, and Enterprise etime Setup. If you are using DCM, you must also use the same data source name that you use for Enterprise etime. If you have not installed any Enterprise etime components, you can enter any name here because the name does not exist until the installation program creates it. After you select a name, write it down because you must enter the same ODBC data source name for all components that request it ADP, Inc.

95 Installing Enterprise etime Setup If you already installed other components, you must enter the same ODBC data source name for all components. 6. Enter Database Server Name Enter the name of the machine on which the database software is installed. 7. Enter Port Number The default port number is 1433 for a SQL Server 2000 database and 1521 for an Oracle database. Because the port number can vary from company to company, however, ask your network or system administrator for this information. Enterprise etime Installation Guide for Windows 3-39

96 Chapter 3 Installing Enterprise etime 8. Enter Oracle SID If you are using an Oracle database, you must enter the Oracle SID, which identifies the database instance that is associated with the Oracle executable. 9. Enter Database Schema User Name and Password If you are using an Oracle database, the following dialog box appears. Enter the user name and password of the owner of the database objects. This value is put into the Windows registry and is used by the Background Processor. The information that you enter here depends on whether you are using Oracle s multi-schema database capabilities or not.! In a multi-schema database environment, enter the logon that you created for the schema. See the Enterprise etime Database Installation Guide for more information.! In a non-multi-schema database environment, this logon is typically TKCSOWNER ADP, Inc.

97 Installing Enterprise etime Setup 10. Enter Database User Name and Password If you are not using Oracle s multi-schema database capabilities, you must enter the user name and password that you would like the application to use to connect to the database. This should be a different logon than the schema owner, for example, SUPRKRON. However, if you are installing the application server to point to an archive database and you plan to use Enterprise Archiver on the application server, you must use TKCSOWNER as the database user name in this dialog box and when you install Enterprise Archiver. 11. Enter Database Name If you are using a SQL Server database, you must enter the name of the database in this dialog box. See your database administrator if you do not know the name of the database. This dialog box does not appear if you are using an Oracle database. Enterprise etime Installation Guide for Windows 3-41

98 Chapter 3 Installing Enterprise etime 12. Start Copying Files Review your settings in the Start Copying Files dialog box before you continue with the installation program. If your settings are not correct, click Back until you locate the dialog box that you need to correct. If your settings are correct, click Next. The Enterprise etime installation program installs the Enterprise etime Setup executable files and the ODBC drivers. Although the installation program displays its progress as it installs the requested components, little user interaction occurs. 13. InstallShield Wizard Complete When the installation is finished, the InstallShield Wizard Complete dialog box appears. You must restart your computer to complete the installation. Caution: Before you reboot, make sure no other processes are running. If you are ready to reboot your system, select Yes, I want to restart my computer now and click Finish. If you need to stop other processes, select No, and reboot your machine after you stop the other processes. 14. After you reboot your system, you must stop and start Enterprise etime manually by clicking the Stop icon and then clicking the Start icon. For more information about starting Enterprise etime, refer to Chapter ADP, Inc.

99 Installing Kdemo Installing Kdemo Kdemo enables you to run Enterprise etime on one PC for demonstration, training, and testing purposes. Software that is normally present on separate database servers, Web or application servers, Background Processors, and browser-based clients resides on one PC. Kdemo Prerequisites Kdemo is supported on the following:! Windows only! SQL Server database (Kdemo cannot use an Oracle database)! Apache or IIS Web server software The process for installing Kdemo is different depending on whether you are using Apache or IIS. Installing Kdemo with Apache Web Server Software Note: If you do not have SQL Server 2000 installed on your PC, the Kdemo installation procedure installs MSDE. The MSDE installation will fail, however, if you have monitoring tools such as antivirus software or Belarc BellManage running on your PC. You must disable these tools before MSDE is installed and restore them after the installation. After completing the steps described in Starting the Installation Program on page 3-3 and using the installation worksheet that you completed on page 2-10, provide the data requested in the following dialog boxes. Click Next after you input the required information. 1. Enter Printer Name You can accept the printer path that appears, enter a different path, or leave it blank; then click Next. The name that appears is the local default printer that Kdemo will use. You can configure additional printers with the Enterprise etime Setup component at a later time. Enterprise etime Installation Guide for Windows 3-43

100 Chapter 3 Installing Enterprise etime 2. Enter User Name and Password Enter your full Windows user name and password, then click Next. If you use domain security, enter the domain name before your user name. For example, enter your_domain\your user_name in the User Name box. This user requires local administrator rights, and the password cannot be null (blank). Note: If you do not enter a user name and password here, you will not be able to schedule reports or any other event such as import. 3. Install Scheduler The following message box appears next. If you want to use the advanced Enterprise Scheduler product, click Yes; otherwise click No ADP, Inc.

101 Installing Kdemo 4. Start Copying Files Review the settings information Some of this information is provided by default and other information is provided based on your input. For example: Line in Dialog Box Source 1 Language The information you entered in step 6 on page Files will be copied to The information you entered in step 7 on page Java Plugin version The information you entered in step 3 on page Character Set Vendor The systems selects the Windows character set. 5 Database Platform ODBC Datasource Name Shortcut folder The system provides this information. If you are installing DCM, make a note of the ODBC Datasource Name. You need to enter this information when you install DCM. 6 Enterprise etime Server used for configuration Database Server Name Port No. The system provides this information. The Enterprise etime server and the database server are the name of the computer on which Kdemo is installed. If you are installing DCM, make a note of these names. You need to enter this information when you install DCM. Enterprise etime Installation Guide for Windows 3-45

102 Chapter 3 Installing Enterprise etime Line in Dialog Box Source Printer Name The information you entered in step 4 on page NT User Name The information you entered in step 5 on page BGP interval in seconds The system sets the Background Processor refresh interval to 5 seconds. Web Server platform used for The system selects Apache Web Server software. configuration Setup Type selected The system adds this information based on your selection of Kdemo as an installation option. The system also lists the individual components that will be installed as part of the Kdemo installation:! Microsoft ADSI! Java Runtime Environment! Background Processor! Callable Totalizer! Enterprise etime Setup! Merant ODBC Drivers! Jrun Application Server! Apache Web Server! Demo Environment (Kdemo)! Application Server! Required Components To change a setting, click Back until you reach the dialog box that contains the information that you want to change. Change the information and click Next until the Start Copying Files window appears. Click Next to continue. The Setup Status window appears to show information about Enterprise etime components being installed. Note: If you click the Cancel button while the MSDE installation wizard is running, it can take up to 5 minutes for the installation to cancel and return to its original state ADP, Inc.

103 Installing Kdemo 6. When the installation is completed, the InstallShield Wizard Complete dialog box appears. If you are not installing DCM, select Yes, I want to restart my computer now. Click Finish to complete the installation. If you are installing DCM on the same system as Kdemo, select No, I will restart my computer later, and click Finish. Install DCM according to the Data Collection Manager Installation Guide. 7. After you reboot your system, you must stop and start Enterprise etime manually by clicking the Stop icon and then clicking the Start icon. For more information about starting Enterprise etime, refer to Chapter 6. For more information about configuring and using Kdemo, refer to Chapter 4. Installing Kdemo with IIS Web Server Software Note: If you are going to use Kdemo with IIS, you must install SQL Server 2000 on your PC. The installation procedure will not install MSDE. If IIS Web server software is already installed on your demo machine and you want to configure the Kdemo database to use IIS instead of Apache, complete the following steps: 1. Start the Enterprise etime installation program as described on page 3-3, but select the Single Server option instead of Kdemo in the Setup Type dialog box. Then complete the following steps, clicking Next after you input the required information. 2. Select Program Folder Click Next to accept the default program folder (ADP Enterprise etime) or enter a new program folder name and click Next. Enterprise etime Installation Guide for Windows 3-47

104 Chapter 3 Installing Enterprise etime 3. Choose Java Plugin version Select one of the following:! JRE 1.3 U.S. English (default)! JRE 1.3 International! JRE 1.4 U.S. English! JRE 1.4 International 4. Choose Character Set Select the Windows character set for Enterprise etime to use. 5. Choose Database Platform Select SQL Server as the database platform that your Enterprise etime application uses. Note: SQL Server must be installed before you install Enterprise etime components. 6. Choose Web Server Platform Select IIS from of the Web servers listed. 7. Enter Application Server Name Enter the name of your machine. 8. Enter ODBC Data Source Name Enter the ODBC data source name of the Kdemo database: WTK_kdemo_database. 9. Enter Database Server Name Enter the name of your machine. 10. Select Database Server Time Zone Select the time zone in which the database server resides from the drop-down list. 11. Enter Port Number Accept the default. 12. Enter Database Name Enter kdemo as the name of the database in this dialog box. 13. Enter Database User Name and Password Enter the following:! Database User Name: sa! Password: demo 14. Enter Printer Name Enter the name of the local default printer to be used by the application server. Although you can later configure printers with the Enterprise etime Setup component, the printer that you enter here becomes the default for the Event Scheduler or other application server processes ADP, Inc.

105 Installing Kdemo 15. Enter User Name and Password Enter your Windows user name and password, then click Next. This user requires local administrator rights, and the password cannot be null (blank). The simplest thing to enter here is the Administrator logon of your machine. If you use domain security, enter the domain name before your user name. For example, enter your_domain\your user_name in the User Name box. Note: If you do not enter a user name and password here, you will not be able to schedule reports or any other event such as import. 16. Enter Background Processor Interval Enter the amount of time in seconds that the Background Processor is idle between processing. 17. Install Scheduler The following message box appears next. Click Yes if you want to install Enterprise Scheduler; otherwise click No. Note: If you install Enterprise Scheduler at a later date, you can do so without reinstalling Enterprise etime. See page 3-51 for more information. 18. Start Copying Files Review your settings in the Start Copying Files dialog box before you continue with the installation program. If your settings are not correct, click Back until you locate the dialog box that you need to correct. If your settings are correct, click Next; the Enterprise etime installation program installs the components. 19. InstallShield Wizard Complete When the installation is finished, the InstallShield Wizard Complete dialog box appears. You must restart your computer to complete the installation. Caution: Before you reboot, make sure no other processes are running. Select Yes in this dialog box to reboot your system. Enterprise etime Installation Guide for Windows 3-49

106 Chapter 3 Installing Enterprise etime 20. Get a copy of the Kdemo database files (kdemo.mdf and kdemo.ldf) from your TLM Representative and copy them to ADP\wfc\kdemo. Then reboot your machine again. 21. After you reboot your system, you must stop and start the Enterprise etime application server manually by clicking the Stop icon and then clicking the Start icon ADP, Inc.

107 Installing Enterprise Scheduler Installing Enterprise Scheduler The Enterprise Scheduler add-on application is included on the Enterprise etime CD. Although you can install Enterprise Scheduler at the same time that you install the Enterprise etime application server or single server option, you can also install this add-on product after you complete the Enterprise etime installation. To install Enterprise Scheduler after you have installed Enterprise etime: 1. Click the Stop icon to ensure that Enterprise etime is not running. 2. Insert the Enterprise etime CD into the CD-ROM drive and open Windows Explorer. 3. In Windows Explorer, navigate to your CD-ROM drive and double-click WFS\setup.exe. 4. In the Enterprise Scheduler Setup dialog box, click Next. 5. Enterprise Scheduler is installed. Click Finish when the InstallShield Wizard Complete dialog box appears. 6. Although you do not need to reboot your system, you must stop and restart the Enterprise etime application server by clicking the Stop icon and then the Start icon. For more information about starting Enterprise etime, refer to Chapter 6. Enterprise etime Installation Guide for Windows 3-51

108 Chapter 3 Installing Enterprise etime 3-52 ADP, Inc.

109 Chapter 4 Using Kdemo Kdemo is a set of software components that enables you to run the entire Enterprise etime system on one Windows PC for demonstration, training, and testing purposes. Software that is normally present on separate database servers, Web or application servers, Background Processors, and browser-based clients resides on one PC. If you use timeclocks, you can also install Data Collection Manager (DCM) software to be used with the Kdemo database and software. DCM is software that transfers information from the timeclocks into the database. The Kdemo software is installed using the standard Enterprise etime installation program as described on page This chapter describes how to configure and use Kdemo. It contains the following sections:! Kdemo Components! Creating a Kdemo Database! Attaching the Kdemo Database to the Database Server! Detaching a Database! Detaching a Database! Copying and Backing Up Kdemo Databases! Upgrading the Kdemo Database

110 Chapter 4 Using Kdemo Kdemo Components Kdemo requires Microsoft SQL Server 2000 database software or Microsoft Database Engine 2000 (MSDE 2000); it cannot use an Oracle database. MSDE is the foundation of the SQL Server 2000, but does not contain or support high-end database tools, such as data replication; MSDE is not packaged with a user interface. You must either install Microsoft SQL Server 2000 before you install Kdemo or if SQL Server is not installed on the PC, the installation procedure installs MSDE Kdemo includes:! The Enterprise etime, Enterprise etime Accruals, Enterprise etime Professional, Enterprise etime Manager, and Enterprise Scheduler products. These products, which are part of the Kdemo installation, contain the required Enterprise etime Background Processor and Enterprise etime Setup components.! The Enterprise etime server, including an embedded Apache Web server and application server.! Sample license key (75 employees and 20 managers).! MSDE 2000, which is installed if Microsoft SQL Server 2000 is not already present on the machine.! Empty (unpopulated) database! Licensed OEM products! Kdemo Database Utility that allows you to attach and detach a database to MSDE or SQL Server The following required SQL Server middleware that supports client/server communication is on the CD and is installed as part of the MSDE installation:! SQL Server 2000 Network Libraries! Microsoft Data Access Components (MDAC) v ADP, Inc.

111 System Requirements System Requirements The following outlines the system requirements for Kdemo: Item Processor (Intel Pentium) RAM Hard disk space Operating system Browser support JRE support Specification 450 MHz (minimum) 256 MB (minimum) 560 MB One of the following:! Windows 2000 Professional or Server, service pack 3*! Windows NT Workstation or Server 4.0, service pack 6a or higher! Windows XP Professional! Windows 2003 Server One of the following:! Microsoft Internet Explorer 5.0, 5.5, or 6.0 for nonsecure mode (HTTP)! Microsoft Internet Explorer 5.5 with service pack 1, or 6.0 for secure mode (HTTPS)! Netscape Navigator 7.0 Note: Netscape is not supported on Microsoft Windows XP clients. v1.3.1_02 or v1.4 (shipped with the product) Other requirements! CD-ROM reader (or access to one on the network)! Adobe Acrobat Reader v4.05, v5.0 (v4.5 is not supported)! Network card! Monitor: 1024 x 768, 16-bit resolution is recommended. Minimum resolution is 800 x 600, but requires the user to scroll.! The following must be enabled: Non-persistent (session) cookies JavaScript! Pop-up-blocking software must be configured to enable the Enterprise etime server to show pop-up windows * ADP supports only service packs to the specific release. It does not support subsequent point releases or subsequent full releases by the vendor. For example, Windows NT 4.0 Service Pack 6a means that ADP will support Windows NT 4.0 and all service packs made to Windows NT 4.0 service pack 6a or higher, such as Windows NT or It does not imply that Windows NT 4.1 or any other version of Windows NT is supported. Enterprise etime Installation Guide for Windows 4-3

112 Chapter 4 Using Kdemo Creating a Kdemo Database When you install Kdemo, the installation program includes two Kdemo database files kdemo.mdf, which is a data file, and kdemo.ldf, which is a log file. These files are delivered to the \kdemo directory (C:\ADP\wfc\kdemo) on your hard drive. This Kdemo database, however, is empty; it does not include any labor levels, people, or other configuration information. You must create a database by accessing Enterprise etime Setup and creating labor levels, work rules, access profiles, and other configuration information. Then, through the Enterprise etime browser interface, you can add people and data.you cannot access Enterprise etime Setup through a browser; you must log on to it from the system where it is installed. To access Enterprise etime Setup: 1. Select Start > Programs > ADP Enterprise etime > Enterprise etime Setup. 2. Enter your user name and password, then select WTK_kdemo_database as the data source name (DSN) and click OK. 4-4 ADP, Inc.

113 Creating a Kdemo Database The Enterprise etime Setup window appears and you can create the necessary labor levels, work rules, and so forth. Refer to the Enterprise etime Setup online help for more information. If you do not want to manually populate the Kdemo database that is delivered by the installation program, you may order a sample Kdemo database from your TLM Representative. By default, the names of the database files that Kdemo uses are kdemo.mdf/ kdemo.ldf. The easiest way to use the sample database is to: 1. Rename the kdemo files delivered by the installation program to something like kdemo_empty.mdf and kdemo_empty.ldf. 2. Copy the kdemo.mdf and kdemo.ldf files provided by your TLM Representative to C:\ADP\wfc\kdemo on your local system. Do not change the file names. Note: Both the.mdf and.ldf files are required. Enterprise etime Installation Guide for Windows 4-5

114 Chapter 4 Using Kdemo Attaching the Kdemo Database to the Database Server Before you can use Kdemo, you must first connect or attach your database files to SQL Server by running the Demo Database Utility supplied with the Kdemo software. Using this utility, you can attach or detach one or more databases from the database server. Before you can attach the Kdemo database, start the database server and select the database. Starting the Database Server You can determine whether the database server is running from the SQL Server Service Manager icon located in the tool tray at the right of the Windows task bar. If the icon shows a green triangle, then the database server is running; if the icon shows a red box, then the database server is stopped. To start the database server: 1. Double-click the SQL Server Service Manager icon. The SQL Server Service Manager dialog box appears. 4-6 ADP, Inc.

115 Attaching the Kdemo Database to the Database Server 2. Select the database server from the Server drop-down list. This selection is usually the name of the system where Kdemo is installed. 3. Select SQL Server from the Services drop-down list. 4. Select the Auto-start service when OS check box if you want the server to start automatically when you restart your computer. 5. Click Start/Continue. Note: If the Server Manager icon contains a green arrow pointing to the right, your default server is already running and the Start/Continue button is not available. Click the X in the upper-right corner to close the dialog box. Attaching the Kdemo Database After the database server is running, you attach a Kdemo database: 1. From the Start menu, select Programs > ADP Enterprise etime > KDemo DB Attach. The database Login dialog box appears. 2. If you are using your own Microsoft SQL Server 2000 software, accept the default in the Userid box and enter the password. If you are using the MSDE software supplied by the Kdemo installation, accept the default information: sa in the Userid box and demo as the password. You can change the password later; see page 4-9 for more information. Enterprise etime Installation Guide for Windows 4-7

116 Chapter 4 Using Kdemo 3. Click OK. The Demo Database Utility dialog box appears: Under Attach Database, in the Database Location text box, enter a path or use Browse to select the path of the empty database. The default location is C:\ADP\wfc\kdemo\kdemo.mdf. 4. Click Attach. When the database is attached successfully, a confirmation message box appears. 5. Click OK, then click Exit in the Demo Database Utility dialog box. Note: Although the number of databases that can be attached to the database server is unlimited, each attached database requires that the database server uses a certain amount of memory and processing power, which might slow the performance on your PC. Therefore, attach only the databases you need for a particular demonstration and detach the databases that are not needed. 4-8 ADP, Inc.

117 Attaching the Kdemo Database to the Database Server Changing the MSDE Password If you use MSDE 2000, you can change the default password as follows: 1. Navigate to adp\wfc\kdemo. 2. Double-click ChangePassword.exe. The following dialog box appears: 3. Enter the password, demo, in the Password box and click Login. 4. In the Change SA Password dialog box, enter the name of the existing password, demo. Then enter the new password and confirm the new password. Click Change Pwd when finished. 5. When complete, the Password Changed message box appears to notify you that the SA password has been successfully changed. Click OK. Enterprise etime Installation Guide for Windows 4-9

118 Chapter 4 Using Kdemo Detaching a Database You must detach any database used with Kdemo before you copy it or run the Enterprise etime uninstall program. To detach a database: 1. Stop Enterprise etime by clicking the Stop icon. 2. From the Start menu, select Programs > ADP Enterprise etime > Kdemo DB Attach. The database Login dialog box appears. 3. Specify the database server to which the database is attached. 4. Accept the default in the Userid text box and enter the password. 5. Click OK. The Demo Database Utility dialog box appears ADP, Inc.

119 Detaching a Database 6. Below Detach Database, select the database that you want to detach in the Database Name drop-down list. 7. Click Detach. When the database is successfully detached, a confirmation message box appears. 8. Click OK. Then click Exit in the Demo Database Utility dialog box. Note: If you see an error message that the Demo Database Utility could not detach from SQL Server, make sure that Enterprise etime has stopped and repeat the detach process. Enterprise etime Installation Guide for Windows 4-11

120 Chapter 4 Using Kdemo Copying and Backing Up Kdemo Databases If you use several demonstration databases for a variety of purposes, then you need to copy your Kdemo database and back up all of your databases. A single process can accomplish both tasks. You can copy and back up your databases by copying the two database files (*.mdf and *.ldf), and then renaming both files in the Kdemo database. The Kdemo databases are located in C:\ADP\wfc\kdemo. Caution: Shut down the database server and detach your database before you copy the database files. Database files that are copied while attached to the database server (even if the database server is down) cannot be attached to a database using this utility. Failure to detach a database from the server prior to copying the database files can result in serious damage to your database. Copy the files using the file maintenance utility of your choice, such as Windows Explorer, which is provided with the Windows operating system. Remember the following points when you copy or back up databases:! Copy both the data (.mdf) and log files (.ldf) or data loss will occur.! Ensure that the file name used in the copy process is exactly the same for both files, and that both files are located in the same file directory.! When you change the name of the copied files, the names for each of the files must be exactly the same. Do not change the file extensions. To use the copied database files, attach the database to the server using the Demo Database Utility ADP, Inc.

121 Copying and Backing Up Kdemo Databases Example of Copying Database Files Using Windows Explorer The following procedure illustrates how to copy files using Windows Explorer. You also follow this procedure to back up a database. 1. Open the Windows Explorer utility. 2. Open the directory that contains the Kdemo databases: In this example, the Kdemo databases are located in C:\ADP\wfc\Kdemo. The two database files are kdemo.mdf and kdemo.ldf. 3. Press Ctrl and select both database files. Then select Edit > Copy, followed by Edit > Paste. The copied files appear in the contents box with the names Copy of kdemo.mdf and Copy of kdemo.ldf. 4. Select each of the copied files, and then select File > Rename. Change the file name to the name of the new database. Verify that each file is exactly the same name and do not change the file extensions. In this example, the renamed files are Customer.mdf and Customer.ldf. Enterprise etime Installation Guide for Windows 4-13

122 Chapter 4 Using Kdemo Upgrading the Kdemo Database There are two ways to upgrade Kdemo from Enterprise etime v4 to v5, depending on your current version of Enterprise etime:! If you are currently running Enterprise etime v4.3, you can upgrade your 4.3 database and install Kdemo v5.0 without uninstalling v4.3.! If you are currently running a pre-4.3 version of Enterprise etime, you must uninstall the current version before you can install Kdemo v5.0. The process for upgrading Kdemo is essentially the same as for upgrading any other Enterprise etime components. For more information, see Chapter ADP, Inc.

123 Chapter 5 Installing Non-U.S. English Systems The Enterprise etime software, online Help, and much of the documentation is available in two languages: English and Spanish. During the installation procedure, you must select one of these languages. When you select the language, Enterprise etime also sets the country, time zone, currency, and date format as shown in the following table: Date Formats Language Country Time Zone Currency Long Short English U.S. Eastern U.S. dollars M/dd/yyyy M/dd Spanish Mexico Hora de la zona Mexican pesos dd/m/yyyy dd/m oriental If you want to install anything other than these default settings, additional steps are required. This chapter provides an overview of the additional considerations for non-u.s. English installations and contains the following sections:! Character Set Designations! Configure Application Server Settings! Troubleshooting Checklist For more information about configuring non-english systems, see the Enterprise etime System Administrator s Guide and Guide to Translating and Customizing the Enterprise etime User Interface and Online Help.

124 Chapter 5 Installing Non-U.S. English Systems Character Set Designations Character set designations for non-english languages may require additional configuration. Enterprise etime supports three character sets:! Latin-1 (Western European)! Latin-2 (Central European)! Latin-9 (Western European with the Euro symbol) Note: Enterprise etime supports Latin-9 character sets only on the Windows platform, not on UNIX. For Windows installations, the following table summarizes the corresponding code pages and databases supported for each character set: Character Set ISO Series Windows Code Page Database Platforms Supported Latin-1 ISO CP1252 Oracle, SQL Server Latin-2 ISO CP1250 Oracle, SQL Server Latin-9 ISO CP1252 Oracle, SQL Server Important: If you use the Euro character on Windows NT 4.0, be sure to load the NT Euro patch on your server. Also, remember that the Euro is not contained in the ISO character set. It is contained in the CP 1250/CP1252 and ISO character sets. However, it is mapped to different positions in the ISO code page versus the Windows code pages. This can cause difficulty with the Euro if you have a mixed environment of code pages. It is always best to standardize on one code page, if possible. 5-2 ADP, Inc.

125 Character Set Designations An Enterprise etime database can only support one character set. For example, a company that uses English and Spanish can use the same database for both languages because they are both Latin-1 languages. A company that uses English and Romanian, however, would need to use two databases because English is part of the Latin-1 character set and Romanian is part of the Latin-2 character set. Note: Whether you use Windows or ISO is important it must be consistent throughout all of the settings. For more information, refer to the Enterprise etime System Administrator s Guide. Enterprise etime Installation Guide for Windows 5-3

126 Chapter 5 Installing Non-U.S. English Systems Configure Application Server Settings If you are installing a non-u.s. English language, you must modify some or all of the server settings described in the following sections, specifically: 1. Set Regional Information and Time Zone in Operating System 2. Set Enterprise etime Local Values 3. Create ADP Relogon Window 4. Set Up Online Help Files 5. Set Up Reports 6. Set Time Display After you finish these steps, reboot the machine and restart your Enterprise etime application server. Set Regional Information and Time Zone in Operating System To set the regional settings of your application server to the appropriate country before you install Enterprise etime: 1. Select Start > Settings > Control Panel > Regional Options. The Regional Options dialog box appears. 5-4 ADP, Inc.

127 Configure Application Server Settings 2. Select the appropriate country from the Your locale (location) drop-down list. 3. Select the appropriate language in the Language Settings for the System box. 4. Click the Set default button and click OK. To set the correct time zone for your application server: 1. Select Start > Settings > Control Panel > Date/Time. 2. Click Time Zone in the Date/Time Properties dialog box. 3. Select the appropriate time zone from the drop-down list. 4. Click OK. Set Enterprise etime Local Values The Enterprise etime installation program will install the following countrylanguage combinations:! U.S.-English! Mexico-Spanish If you are installing anything other than these combinations (for example, Great Britain-English, Hungary-Hungarian), you must change the local values in your application server. 1. Log on to Enterprise etime as superuser or an administrator. 2. From the navigation bar, select System Configuration > System Settings, then select the Locale tab. 3. At a minimum, you must change the following local values:! site.local.timezone! site.local.short_date! site.local.long_date! site.local.language! site.local.country! site.local.currency.language! site.local.currency.country Enterprise etime Installation Guide for Windows 5-5

128 Chapter 5 Installing Non-U.S. English Systems! site.local.charset.encoding! site.local.timestamp.serverdateformat Note: If the format of this value is not correct, no date appears on the Time Stamp view. For example, for Czechoslovakia-Czech, you would set: Setting site.local.timezone site.local.timestamp.serverdateformat site.local.short_date site.local.long_date site.local.language site.local.country site.local.currency.language site.local.currency.country site.local.charset.encoding Value (GMT +01:00) Prague EEEE, d. MMM yyyy E d.m d.m.yyyy CS CZ cs CZ Eastern European (Windows CP1250) or Eastern European (ISO ) For more information about setting local values, refer to the Enterprise etime System Administrator s Guide. 5-6 ADP, Inc.

129 Configure Application Server Settings Replace Global Attributes File When Enterprise etime is installed, several.jsp files are installed on your system. Web pages use these files to determine the appropriate encoding to use. The files that the installation procedure delivers are appropriate for Latin-1 languages, but if you are installing a Latin-2 or Latin-9 language, you must replace the default files. Note: If you are using a Latin-1 language, you can ignore this step. 1. Open the adp\wfc\html directory. 2. Rename the existing global-attributes.jsp file to global-attributes-old.jsp. 3. For Latin-2 languages, copy the appropriate Latin-2 adp\wfc\html\globalattributes_xxx.template file over the existing global-attributes.jsp file where:! The file global-attributes_windows-1250.template uses the Windows Latin-2 code page.! The file global-attributes_iso template uses the ISO Latin-2 code page. 4. Ensure that you are using the correct Latin-2 character set.! Windows = windows-1250! ISO = iso Enterprise etime Installation Guide for Windows 5-7

130 Chapter 5 Installing Non-U.S. English Systems Create ADP Relogon Window You must create a relogon window for the appropriate country and language. To do this: 1. Open the adp\wfc\html\relogon directory. 2. Copy one of the existing files (_en, _es) to: adp-relogon-window_xxxx_zz-.html where:! XXXX = Latin-2 code page ID to be used! ZZ = the 2-character language code for your Latin-2 country For example, for Czech, the file name would be: adp-relogon-window_iso _cs.html Important: To ensure that you are using the correct Latin-2 character set, make sure Windows = Windows-1250 and ISO = iso ADP, Inc.

131 Configure Application Server Settings 3. Open the file with a text editor and edit the first two lines to reference the correct code page and language or country code. For example, for Czech, the two lines would be: <META HTTP-EQUIV="Content-Language" content="cs"> <META HTTP-EQUIV="Content-Type" content="text/ html;charset=windows-1250"> Create Refresh Button Directory Note: If you are using English or Spanish, you can ignore this step. You must create a refresh button directory and place a corresponding refresh button.gif file in that directory. By default, en and es are created by the installation procedure within the adp\wfc\html\images directory. You will see the default, en and es subdirectories, and within them the corresponding.gif file for the language being supported. Language Directory Refresh_button.gif English adp\wfc\html\images\en Spanish adp\wfc\html\images\es If you are installing a system in a language other than English or Spanish: 1. Create a.gif file in the appropriate language. Refer to the Guide to Translating and Customizing the Enterprise etime User Interface and Online Help for more information. 2. Copy the Spanish directory and rename the directory you copied to the language you are setting up. For example, if you are setting up a Czech installation, you would name the subdirectory cs for the Czech Republic. Enterprise etime Installation Guide for Windows 5-9

132 Chapter 5 Installing Non-U.S. English Systems Note: The name of the subdirectory must match the appropriate ISO twocharacter language abbreviation. To check the abbreviations, select System Configuration > System Settings from the Enterprise etime navigation bar and then select Local Settings. The abbreviations are listed in the drop-down list of site.local.language. When you are in System Configuration and the Refresh button is displayed, it will be displayed in the language that you copied. If you do not create the refresh button directory with the correct.gif file, a red X will be displayed instead of a button. Set Up Online Help Files You must create a help directory and place the necessary help files in that directory. By default, en and es subdirectories are created by the installation procedure in the ADP\wfc\help directory. Within each subdirectory is the corresponding help files for the language being supported. If you are installing a system in a language other than English or Spanish: 1. Copy the Spanish directory, and rename the directory you copied to the language you are setting up. For example, if you are setting up a Czech installation, you would name the subdirectory cs for Czech. 2. If you are using a language other than U.S.-English or Mexico-Spanish, you must also translate and customize the online Help files as explained in the Guide to Translating and Customizing the Enterprise etime User Interface and Online Help. After you complete the previous tasks, the Enterprise etime online Help appears in the language that you copied. If you do not complete these tasks, an error message appears. Set Up Reports For Enterprise etime v5.0, report strings have been externalized to the u2li18n.ini file. Each area of the application, for example, Enterprise etime 5-10 ADP, Inc.

133 Configure Application Server Settings and Enterprise Scheduler, has its own.ini file in the adp\wfc\applications directory, so there may be more than one on a reporting server. As an example, the files for Enterprise etime are found in the adp\wfc\applications\wtk\properties directory. Each instance of the file is duplicated and renamed to u2li18n_xx.ini, where xx is the 2-digit lowercase value for site.local.language property from System Settings, then placed in the same directory as the original u2li18n.ini file. You will see the default en, es and fr u2li18n.ini files to use as an example for the file name: Again, the language code that is added to the file name must be 2-character, lowercase. Note: This is required on every server that is set up as a reporting server. Set Time Display If you want the time to appear in 24-hour format within Enterprise etime, you must modify Enterprise etime Setup. Within Enterprise etime Setup, you need to modify the applicable display profile to use 24-hour format instead of 12-hour format. Enterprise etime Installation Guide for Windows 5-11

134 Chapter 5 Installing Non-U.S. English Systems Reboot Machine After your Enterprise etime application server is configured for the appropriate language: 1. Reboot the machine on which the application server is installed. 2. Stop the application server by clicking the Stop icon or by selecting Start > Programs > ADP Enterprise etime > Stop Enterprise etime. 3. Restart the application server by clicking the Start icon or selecting Start > Programs > ADP Enterprise etime > Start Enterprise etime. Note: It is extremely important that you stop and restart the Enterprise etime server after rebooting the machine. This stop/start must be done from the desktop icons (or from the Start > Programs menu). Do not use the Restart link in the System Setting page of the Enterprise etime portal to restart the server. Doing so may cause your server to come up with incorrect locale information ADP, Inc.

135 Troubleshooting Checklist Troubleshooting Checklist If you experience problems with your installation, verify that the following information and settings have been made correctly: # Operating system matches the locale version of the Enterprise etime installation. # Regional Settings of all server computers are set to the appropriate language settings. # Regional Settings of all client computers are set to the appropriate language settings. # The international version of the JRE is installed on the server. # If using Latin-2, the database is also set for Latin-2. # The Enterprise etime Local Values tab has the correct settings for the following:! Language settings! Time zone! Date formats Enterprise etime Installation Guide for Windows 5-13

136 Chapter 5 Installing Non-U.S. English Systems 5-14 ADP, Inc.

137 Chapter 6 Starting Enterprise etime This chapter contains the following sections:! Starting and Stopping the Application Server! Starting and Stopping the Background Processor! Accessing the Enterprise etime Professional - Java Client! Accessing the Enterprise etime Professional - HTML Client

138 Chapter 6 Starting Enterprise etime Starting and Stopping the Application Server Although the application server starts automatically when you start the computer on which it is located, you must stop it and then start it manually after Enterprise etime is initially installed and when you install:! Any Enterprise etime add-on application! An Enterprise etime service pack! A patch After the application server is running, you can access the Enterprise etime user interface from the machine on which the application server resides or from a client machine. Starting the Application Server You can start the application server in either of the following ways:! Click the Go icon on your desktop.! From the Windows Start menu, select Start > Programs > ADP Enterprise etime > Start Enterprise etime. 6-2 ADP, Inc.

139 Starting and Stopping the Application Server Depending on the speed of your computer, it might take several minutes for all the Enterprise etime processes to start. Because all Enterprise etime processes must start before you can access the application server in a browser, you should check the status of the processes using Windows Task Manager. The following explains how to do this with a Windows NT system; the process with other Windows operating systems varies slightly. 1. Press the Ctrl-Alt-Delete keys to open the Security dialog box. 2. Click the Task Manager button, then select the Processes tab. Enterprise etime Installation Guide for Windows 6-3

140 Chapter 6 Starting Enterprise etime The following processes should appear in the list:! jrun.exe JRun server executable! javaw.exe Java Runtime Environment! Apache.exe Apache Web server software, if installed (listed twice) Note: If your installation uses Microsoft IIS or Sun ONE Web server software, Apache is not listed.! Kronos.exe Enterprise etime application server executable! lmgrd.exe GlobeTrotter licensing executable! totalizer.exe Executable that launches the Callable Totalizer Depending on the speed of your machine, it could take several minutes for all of the Enterprise etime processes to start. Click the Performance tab and watch the CPU usage. Several spikes should occur from 0 to 100%. If the CPU usage remains at 0% before all of the processes in this list start, a problem has occurred. Stopping the Application Server To stop the application server, click the Stop icon on your desktop or select Start > Programs > ADP Enterprise etime > Stop Enterprise etime. This process may take several minutes. You can observe the process of the application server shutting down, by accessing Task Manager and watching the Enterprise etime processes shut down. 6-4 ADP, Inc.

141 Starting and Stopping the Background Processor Starting and Stopping the Background Processor Generally, the Background Processor starts automatically when Enterprise etime starts up. However, there may be times when you need to start or stop it manually. To start the Background Processor on a Windows 2000 system: 1. Select Start > Settings > Control Panel. 2. From the Control Panel, select Administrative Tools > Services. 3. In the Services dialog box, right-click ADP Enterprise etime Background Processor and select Properties from the drop-down list. 4. In the Properties dialog box, select the General tab and click Start. To stop the Background Processor, repeat steps 1 3 and in the Properties dialog box, click Stop. Enterprise etime Installation Guide for Windows 6-5

142 Chapter 6 Starting Enterprise etime Accessing the Enterprise etime Professional - Java Client To start the Enterprise etime Professional - Java Client user interface from the machine on which the application server resides, click the Enterprise etime icon: This opens your default browser and the Enterprise etime logon page. To start Enterprise etime from a client machine: 1. Start your browser. 2. Enter the Enterprise etime URL. The default URL is <AppServer>/wfc/logon where <AppServer> is the name of the machine on which the application server resides. Note: Do not use a fully qualified name in the Web browser unless a Domain Name System (DNS) entry that maps the name is in the DNS server. For example, connects, but logon does not connect. 6-6 ADP, Inc.

143 Accessing the Enterprise etime Professional - HTML Client Accessing the Enterprise etime Professional - HTML Client You access the Enterprise etime Professional - HTML Client components by entering a specific URL that is provided by default for the following:! Timecard and Time Stamp! Quick Time Stamp Timecard and Time Stamp The Time Stamp component for the Enterprise etime Professional - HTML Client does not allow you to enter a user name and password on the same screen; it is generally used by employees with dedicated PCs. The Timecard component for the Enterprise etime Professional - HTML Client allows employees to enter, review, edit, and approve the time that they spend in job-related activities. The default URL for Timecard and Time Stamp for Enterprise etime Professional - HTML Client is: where <AppServer> is the name of your application server. Quick Time Stamp The Quick Time Stamp component for the Enterprise etime Professional - HTML Client is similar to punching in at a data collection device, such as a timeclock. With Quick Time Stamp, users log in and enter a punch at a shared PC. The default URL for basic Quick Time Stamp is: where <AppServer> is the name of your application server. Enterprise etime Installation Guide for Windows 6-7

144 Chapter 6 Starting Enterprise etime In addition to basic Quick Time Stamp, there are a number of optional parameters for Quick Time Stamp. To access these parameters, you append the URL suffix listed in the following table to the end of the basic Quick Time Stamp URL after a question mark (?). You can include more than one add-on by connecting them with an ampersand (&). Optional Parameter Description URL Suffix Select Transfer Cancel Meal Deduction Security Timeout Confirmation Timeout Adds the Select Transfer text box and search icon to the Quick Time Stamp Displays the Cancel all meal deductions check box in the Quick Time Stamp. Sets the inactivity time period each user has prior to automatic logoff Sets the redirect timer on the Quick Time Stamp - Time Recorded page. transfer=yes cancel_deduct=yes s_timeout=xxx where xxx is the security time out in minutes c_timeout=xxx where xxx is the confirmation timeout in seconds For example:! To display the Select Transfer text box and search icon on the Quick Time Stamp, enter: To display the Cancel all meal deductions check box in the Quick Time Stamp, enter: quick-ts.jsp?cancel_deduct=yes! To display the Cancel all meal deductions check box, the Select Transfer text box, and the search icon in the Quick Time Stamp, enter: quick-ts.jsp?transfer=yes&cancel_deduct=yes 6-8 ADP, Inc.

145 Accessing the Enterprise etime Professional - HTML Client! To set the Quick Time Stamp logoff timer to 5 minutes, enter: quick-ts.jsp?s_timeout=5! To set the Quick Time Stamp redirect timer to 4000 seconds and to display the Select Transfer text box and Search icon, enter: quick-ts.jsp?c_timeout=4000&transfer=yes Note: You can set the confirmation timeout and the security timeout in two ways: by the URL or by accessing the systems settings on the Enterprise etime navigation bar: System Configuration > System Settings > Security. The URL overrides the system settings. Enterprise etime Installation Guide for Windows 6-9

146 Chapter 6 Starting Enterprise etime 6-10 ADP, Inc.

147 Chapter 7 Changing System Account Passwords Enterprise etime and Data Collection Manager install a number of standard application-level system-user names and passwords. These user accounts have preconfigured profiles that allow system administrators to carry out required system operations. These profiles cannot be modified. This chapter contains the following sections:! Standard System User Accounts! Changing the SuperUser Password! Changing the Totalizer Password! Changing the TaskRunner Password! Changing the xmluser Password! Changing the Password for the Import User Account

148 Chapter 7 Changing System Account Passwords Standard System User Accounts The following table describes the standard system user accounts: User name SuperUser Totalizer TaskRunner xmluser Import dcmsuser mobiletime Description Privileged system user account with unrestricted access to all files and commands; used by the Enterprise etime system administrator System user account used by the Background Processor System user account used by the Event Manager to start Enterprise etime Events on the companion Windows server System user account used for server-to-server communications and API System user account used by the Enterprise etime system administrator to import data System user account used for DCM access to submit punches through the XML API (password change not permitted) System user account used for mobiletime access (password change not permitted) Note: ADP strongly recommends that you change the passwords for the system user accounts after you install and configure Enterprise etime. 7-2 ADP, Inc.

149 Changing the SuperUser Password Changing the SuperUser Password The Super User system user account, SuperUser, is the highest-priority system user account that the Enterprise etime system administrator uses. A limited number of users should know of and use this account. Note: The SuperUser name is case-sensitive unless you are using a SQL Server 2000 database: Online mode: SuperUser Offline mode: superuser Online Mode To change the SuperUser password in online mode: 1. Log on to Enterprise etime at: where <AppServer> is the name of the application server machine. 2. Enter the default logon with the user name, SuperUser, and default password, kronites. 3. Click the Change Password link, enter the user name, old password, and the new password. Make subsequent logins as SuperUser using the new password. Enterprise etime Installation Guide for Windows 7-3

150 Chapter 7 Changing System Account Passwords Offline Mode To change the superuser password in offline mode: 1. Log on to the Enterprise etime offline page at: where <AppServer> is the name of the application server machine. 2. Enter the default logon with the user name, superuser, and default password, kronites. 3. From the navigation bar, select System Configuration > System Settings. 4. Click the Security tab. 5. Change the site.security.authentication.offline. password value. 6. Click Save. Make subsequent logins as superuser using the new password. 7-4 ADP, Inc.

151 Changing the Totalizer Password Changing the Totalizer Password Each machine or machines that has a Background Processor installed is assigned the totalizer user name and default password. To change the password of the totalizer account on a Windows machine, you must access the Background Processor Registry Editor: 1. Stop the Background Processor service, if necessary, from the Services dialog box in the Control Panel as described on page In Windows Explorer, navigate to adp\wfc\bgp, then double-click BGPRegEdit.exe. 3. In the Background Processor Configuration dialog box, click Edit. 4. In the Background Processor Properties dialog box, enter the new password and click OK. Then, click OK in the Background Processor Configuration dialog box to exit the Background Processor Registry Editor. 5. Log on to Enterprise etime as totalizer. 6. Click the Change Password link. 7. Enter the user name, old password, and the new password for totalizer. 8. From the navigation bar, click Logoff. 9. Stop and restart the application server. 10. Restart the Background Processor server. Enterprise etime Installation Guide for Windows 7-5

152 Chapter 7 Changing System Account Passwords Changing the TaskRunner Password The TaskRunner system user account is used by the Enterprise etime Event Manager to start events such as running reports. To change the default password: 1. Log on to Enterprise etime at: where <AppServer> is the name of the machine on which the application server resides. 2. Log on as SuperUser. 3. From the navigation bar, select System Configuration > System Settings and click the Event Manager tab. 4. Enter the new password for TaskRunner into the site.eventmanager.wfc.pwd cell, and click Save. 5. From the navigation bar, click Logoff. 6. Log on to Enterprise etime as TaskRunner. 7. Click the Change Password link. 8. Enter the user name, old password, and the new password for TaskRunner. 9. From the navigation bar, click Logoff. 10. Stop and restart the application server. 7-6 ADP, Inc.

153 Changing the xmluser Password Changing the xmluser Password The XML system user account, xmluser, is used for server-to-server communications and the API. To change the xmluser password: 1. Log on to Enterprise etime at: where <AppServer> is the name of the machine on which the application server resides. 2. Log on as SuperUser using the superuser password. 3. From the navigation bar, select System Configuration > System Settings and click the Global Values tab. 4. Enter the new password for xmluser into the global.xmlservice.login.password cell, and click Save. 5. From the navigation bar, click Logoff. 6. Log on the Enterprise etime as xmluser. 7. Click the Change Password link. 8. Enter the user name, old password, and the new password for xmluser. 9. From the navigation bar, click Logoff. 10. Stop and restart the application server. Enterprise etime Installation Guide for Windows 7-7

154 Chapter 7 Changing System Account Passwords Changing the Password for the Import User Account The Import system user account, import, is used by the Enterprise etime system administrator to import data. Using the import user name when importing data improves performance by making data import faster: the system bypasses the security privileges check associated with other user names. Refer to the Enterprise etime System Administrator s Guide for more information about importing data. To change the import password: 1. Log on to Enterprise etime with the user name import. 2. Click on the Change Password link. 3. Enter the user name, old password, and the new password. Note: Import users, such as A-Connect, will now need to submit the new password. 7-8 ADP, Inc.

155 Chapter 8 Installing Enterprise etime Clients The Enterprise etime system uses a client PC that runs a Netscape or Internet Explorer browser through which users interact with the Enterprise etime system. To access Enterprise etime from an Internet or Netscape browser, the following must be installed on the client PC:! The Java Runtime Environment (JRE) or 1.4 plug-in! Adobe Acrobat Reader The method used to install the plug-in and Acrobat Reader depends on the operating system of the client machine and the type of browser used on the client machine: Internet Explorer or Netscape. Note: If you are only using Enterprise etime Professional - HTML Client, the JRE plug-in and Acrobat Reader do not need to be installed. This chapter contains the following sections:! Before You Access Enterprise etime! JRE Plug-Ins! Setting Up an Internet Explorer Browser! Installing and Setting Up a Netscape 7.0 Browser

156 Chapter 8 Installing Enterprise etime Clients Before You Access Enterprise etime The following must be enabled in every browser that accesses Enterprise etime:! Non-persistent cookies,* which are also called session or temporary cookies, must be enabled. Unlike a persistent cookie, which is stored as a file on your computer, a non-persistent cookie is stored in memory only for your current browsing session. It is deleted from memory when you log off or close your browser.! JavaScript, which is a compact, object-based scripting language for developing client and server Internet applications, must be enabled. In addition, the following types of software require special consideration if they are installed on your PC:! Pop-up-blocking software must be properly configured to allow the Enterprise etime application server to open pop-up windows.! Third-party automatic download software, such as WinAmp, must be disabled before you log on to the Enterprise etime server for the first time. After the system installs the JRE software, as described in the next section, you can reactivate the automatic download software. Note: Third-party automatic download software is any program that intercepts the browser s normal download process. Such software does not include programs such as File Transfer Protocol (FTP). * A cookie is a small text file that contains a unique identification number that a Web site sends to your computer s web browser. 8-2 ADP, Inc.

157 JRE Plug-Ins JRE Plug-Ins The Java Runtime Environment (JRE) provides the minimum requirements for executing a Java application; it consists of the Java Virtual Machine (JVM), core classes, and supporting files. The JRE plug-in is required on every PC that accesses the Java components of Enterprise etime through a browser. Two versions of the JRE plug-in are supported with Enterprise etime v5.0:! JRE 1.3.1! JRE 1.4 When you install the Enterprise etime application server, you select the JRE version to install. Note: If you have multiple versions of the Sun JRE plug-in on your client machines, your users should close the browser window before they launch an applet that requires a version of the plug-in that is different from the one used by the Enterprise etime applets. Enterprise etime Installation Guide for Windows 8-3

158 Chapter 8 Installing Enterprise etime Clients Setting Up an Internet Explorer Browser For PCs that use Internet Explorer to access Enterprise etime, the method used to install the JRE plug-in depends on the operating system:! On Windows NT or Windows 98 client systems, the Enterprise etime application server automatically downloads and installs the components required by the browser clients. For more information, see Installing JRE Plug-in on page 8-5.! On Windows 2000 systems, the JRE plug-in downloads automatically for Administrators or Power Users. For Restricted Users, however, you must manually install the plug-in as described in Installing JRE Plug-in on Windows 2000 Systems with Restricted User Rights on page 8-7. Caution: Because the components of the browser clients are downloaded from a single server to each client PC individually, too many PCs that attempt downloads at the same time could cause a large resource hit on the server. To prevent overload, coordinate the downloads so that they are grouped in small, staggered batches. 8-4 ADP, Inc.

159 Setting Up an Internet Explorer Browser Installing JRE Plug-in If the JRE plug-in is not present on the PC the first time that you access Enterprise etime in an Internet Explorer browser, the system automatically downloads and installs it. Note: The JRE installation is a one-time process for each client PC. You interact with the JRE installation program in the following way: 1. When the Security Warning dialog box appears, asking you if you want to install and run JRE, click Yes. The Java 2 splash screen appears briefly. Enterprise etime Installation Guide for Windows 8-5

160 Chapter 8 Installing Enterprise etime Clients 2. Review the Software License Agreement and click Yes. 3. Select Typical in the Setup Type dialog box and click Next. The JRE installation program runs and notifies you when it is finished. 8-6 ADP, Inc.

161 Setting Up an Internet Explorer Browser Installing JRE Plug-in on Windows 2000 Systems with Restricted User Rights Windows 2000 supports three levels of user rights: Administrator, Power User, and Restricted User. Depending on the rights used, JRE might not download automatically from the application server.! If users have Administrator or Power User rights, JRE will download automatically as described on page 8-5.! If users have Restricted User rights, JRE will not download automatically. The Restricted User rights prohibits users from installing software that alters the computer s Windows Registry. This prevents Enterprise etime from automatically installing JRE. If your Windows 2000 users have Restricted User rights, you can use the Microsoft Software Installation (MSI) application to install the JRE plug-in on client machines from a central or remote location. In this scenario, a repackaged file with a.msi extension, is generated which, in turn, assigns the JRE software application to the client workstation using Group Policies. Note: If your client computers run Windows 2000 where the user has Administrator or Power User rights, Windows NT, or Windows 98, the JRE plugin is downloaded automatically from the application server. You do not need to use MSI. Using MSI To Install JRE Installing the JRE plug-in on Windows 2000 client machines using Microsoft Software Installation (MSI) is a two-step process: 1. Create a repackaged MSI file and use the silent install parameter on JRE. 2. Set up a Group Policy on the server where the JRE install file resides. The Group Policy will assign the software package to the computers. Note: To complete both steps of the JRE installation using MSI, you must have domain administrator rights. Enterprise etime Installation Guide for Windows 8-7

162 Chapter 8 Installing Enterprise etime Clients Each step is described in the following sections. Step 1: Create a Repackaged MSI File You use the Microsoft WinINSTALL application to create a repackaged MSI file. With WinINSTALL, you take a before snapshot of the existing workstation, install the application or package, and then take an after snapshot of the workstation. The before snapshot is a collection of settings, drive, file, and folder information that shows the state of the workstation before the application is installed. This information is then compared to the after snapshot to build the MSI file necessary for the installation of the package. Use the DiscoZ.exe program to create the before and after snapshots. The following steps describe how to create a repackaged MSI file: 1. Create a directory on the server where the MSI file will reside. Create a subdirectory within the directory that you just created. Give both directories share permissions so that users can install software from the network. 2. Copy the JRE install file (j2re-1_4_1-win.exe) to the second directory that you created. Note: Enterprise etime v5.0 uses the JRE install file j2re-1_4_1-win.exe. Future releases of Enterprise etime may, however, require a newer version of the install file. Consult the target release documentation of Enterprise etime to determine the appropriate version of the JRE install file to use. 3. Load a clean copy of Windows 2000 Server on a different PC and configure it for the network. Do not load any additional software. 4. Install WinINSTALL LE from the Windows 2000 server CD (\valuadd\3rdparty\mgmt\winstle\swtadmle.msi) to the server where the JRE install file resides. 5. Right-click the swtadmle.msi file and select Install. Follow the installation instructions that appear on your screen. 8-8 ADP, Inc.

163 Setting Up an Internet Explorer Browser 6. From the clean server, locate the DiscoZ.exe file via the network to the server where the JRE install file resides. a. Double-click the DiscoZ.exe file to start the before snapshot. b. Give the package a name and specify the path and file name for the MSI file. c. Use the path to the JRE install file and change its extension from.exe to.msi. For example: \\servera\jre install\silent\j2re-1_4_1-win.exe d. Specify C: to store temporary files and C: again in the WinInstall Discover dialog box. e. Click Next to start the before snapshot. f. When discover is finished, click Cancel in the Launch Application Setup Program dialog box. 7. Create a JRE silent install file on the server where JRE resides: j2re-1_4_1-win.exe a r f1c:\setup.iss Follow the installation prompts. When finished, the silent install file, setup.iss, will be on the C:\ drive and contain the information needed to perform a silent install. 8. Map a drive to the JRE install file on the clean server and install JRE on the clean server using the silent install feature of JRE: j2re-1_4_1-win.exe s a s f1c:\setup.iss The installation will complete silently, without user intervention. 9. From the clean server, locate the DiscoZ.exe file from the network on the server where the JRE install file resides. 10. Double-click the DiscoZ.exe file to take the after snapshot. When the after snapshot is finished, check the location (for example, \\servera\jre install\silent\j2re-1_4_1-win.exe) to ensure that the MSI file has been created (for example, J2re-1_4_1-win.msi). Enterprise etime Installation Guide for Windows 8-9

164 Chapter 8 Installing Enterprise etime Clients Step 2: Set Up a Group Policy on the Server where the JRE Install File Resides The Group Policy will assign the software package to the computers. 1. Log on to the server as Domain Administrator. 2. Select Start > Programs > Administrative Tools > Active Directory and Computers. 3. Right-click the domain or organization unit, then select Properties > Group Policy tab. 4. Click New and give the Group Policy a name. Then click the Group Policy name again. 5. Click Edit and then select Computer Configuration > Software Settings. 6. Right-click Software Installation and select New Package. 7. Browse from the network to the JRE MSI file (J2re-1_4-1-win.msi) and then click Open. 8. Right-click on the Group Policy, select Properties, make sure Assign is selected, and click OK. The Group Policy is now set up and ready to test. Reboot a Windows 2000 Pro PC that is in the domain and look for the Java Runtime Installation message when the PC restarts. Ensure that the JRE application is on the Start > Programs menu. When the browser first accesses the Enterprise etime application, the JRE application will complete its installation as described in Installing JRE Plug-in on page 8-5. Troubleshooting If the JRE application does not install correctly: 1. Ensure that you followed the instructions in Step 2: Set Up a Group Policy on the Server where the JRE Install File Resides on page The Group Policy will only work on Windows 2000 Pro Workstations. Other operating systems, such as Windows NT, must use their own operating system Group Policies ADP, Inc.

165 Setting Up an Internet Explorer Browser 2. Make sure that the Windows 2000 Professional workstation is in the domain where the server resides. 3. If you verified the information in steps 1 and 2 of this procedure, and the Group Policy does not seem to be applied to the Windows 2000 Professional Workstation, view the Event Viewer Application Log by selecting Start > Settings > Control Panel > Administrative Tools > Event Viewer > Application Log. If the following error appears in the log, your DNS server might not support Service (SRV) records: Windows cannot determine the user or computer name, Event Source: Userenv. For more information, refer to the knowledge database articles: Q and Q Turn on SRV records on your DNS server; or, if needed, install a DNS that uses SRV resource records on the domain server. For more information, see Configure Your Computer as a DNS Server in the Q document. If DNS is activated on the server, ensure that the client Windows 2000 Pro Workstations have their primary DNS set to the server s IP address. 5. For detailed instructions about creating a Windows 2000 Group Policy, go to > support > knowledge base. Note: The JRE application can be stored on any shared network drive. To filter the Group Policy to limit access, select the Properties > Security tab on the Group Policy dialog box. To make the Group Policy apply to a specific group, select the Apply Group Policy check box. Enterprise etime Installation Guide for Windows 8-11

166 Chapter 8 Installing Enterprise etime Clients Installing Adobe Acrobat Reader Adobe Acrobat Reader 4.05 or 5.0 must be installed on all browser clients that are used to access reports. If it is not already installed, you can copy Acrobat Reader from the Enterprise etime CD or download it from the following Web site: If you use Internet Explorer, you must configure Acrobat Reader as a helper application instead of a plug-in. If you install Acrobat Reader as a plug-in, then.pdf files appear as blank pages. To configure Adobe Acrobat Reader as a helper application in version 4.05: 1. Make sure that Adobe Acrobat Reader is installed on the PC. If not, install it. 2. Start Acrobat Reader. 3. Select File > Preferences > General. 4. Clear the Web Browser Integration check box from the Options section and click OK. 5. Exit from the Acrobat Reader and restart Internet Explorer. To configure Adobe Acrobat Reader as a helper application in version 4.5: 1. Make sure that Adobe Acrobat Reader is installed on the PC. If not, install it. 2. Start Acrobat Reader. 3. Select Edit > Preferences > Options > Web Browser Options. Do not select Display PDF in Browser. 4. Exit from the Acrobat Reader and restart Internet Explorer. The next time you select a link to a.pdf file in Internet Explorer, a dialog box will prompt you to specify what to do with the file.! If you select Open this file from its current location, Internet Explorer opens the.pdf file in the Acrobat Reader as a helper application.! If you select Save this file to disk, Internet Explorer saves the.pdf file to your hard disk, where you can open it later ADP, Inc.

167 Installing and Setting Up a Netscape 7.0 Browser Installing and Setting Up a Netscape 7.0 Browser If you use Netscape as your Enterprise etime browser, you must manually install the JRE plug-in if it is not already on the client machine. The installation process varies depending on whether you require the U.S. English-only or International version of the plug-in. Note: The international version of the plug-in is larger and, therefore, slower to download than the English version; but this version is required for systems that use anything other than standard U.S. English and date formats. Netscape 7.0 for U.S. English Only To install Netscape 7.0 for U.S. English only: 1. Verify whether the JRE plug-in is installed as follows: a. Select Start > Settings > Control Panel > Add/Remove Programs. b. Double-click the Java icon labeled Java Plug-in. c. In the Java Plug-in Control Panel dialog box, click the About tab. The version number appears at the bottom of the window. 2. Install Netscape using the Recommended type of setup. Note that the installation program states that Java is not included. Enterprise etime Installation Guide for Windows 8-13

168 Chapter 8 Installing Enterprise etime Clients 3. At the Select Additional Components dialog box, deselect the Java plug-in that is already installed on the client machine. This precaution prevents the installation of the old version of the JRE plug-in. If the required JRE plug-in is already installed on the client machine, the installation program will automatically add support for the currently installed JRE plug-in version. After the Netscape installation finishes, you can use the Netscape browser to access an Enterprise etime server (the logon form fields will be enabled). If the JRE plug-in is not on the client machine: 1. Start the Netscape browser and navigate to the following URL to download the Sun Java Plug-in v1.4.1: Name>/adp/plugins/j2re-1_4_1-win.exe 2. In Netscape s Download dialog box, select a directory location to store the downloaded file. Write this file name down because you will need it to run the installer. 3. In the Save As dialog box, click the Save button to begin downloading the Sun Java Plug-in to the client machine. 4. Netscape 7.0 will now start to download the file. The Download dialog box will be replaced by a Netscape 7.0 Saving File dialog box, which displays a progress indicator. 5. After the download is complete, the Saving File dialog box will remain open. Click the Reveal Location button in the Netscape 7.0 Saving File dialog box to open a Windows Explorer window at the location where the file was downloaded. 6. Close the Netscape 7.0 Saving File dialog box and the Netscape 7.0 browser. 7. To install the Java Plug-in, double-click on the j2re-1_4_1-win.exe file that is listed in the Windows Explorer. 8. The Sun Java Plug-in begins its installation. Part of its installation will prepare Netscape 7.0 to use the plug-in. 9. If you successfully installed the Sun Java Plug-in, start Netscape 7.0 and navigate to the Enterprise etime logon page. The JRE plug-in should now load and allow you to log on to the Enterprise etime server ADP, Inc.

169 Installing and Setting Up a Netscape 7.0 Browser After the Enterprise etime logon page has fully loaded, the form fields should be enabled. This loading indicates that the JRE plug-in was successfully installed and is running. You can now close the Windows Explorer window. Netscape 7.0 for International Use To install Netscape 7.0 for international use, first verify whether the JRE plug-in is installed as follows: 1. Select Start > Settings > Control Panel > Add/Remove Programs. 2. Double-click the Java icon labeled Java Plug-in. 3. In the Java Plug-in Control Panel dialog box, click the About tab. The version number appears at the bottom of the window. Enterprise etime Installation Guide for Windows 8-15

170 Chapter 8 Installing Enterprise etime Clients If the JRE plug-in is already installed on the client machine: 1. Install Netscape using the Custom setup. Note that the installation program states that it is for users with specific international language package requirements. 2. At the Select Additional Components dialog box, deselect the Java plug-in that is already installed on the client machine. This precaution prevents the installation of the old version of the JRE plug-in. The installation program will automatically add support for the currently installed JRE plug-in version. After the Netscape installation finishes, you can use the Netscape browser to access an Enterprise etime server (the logon form fields will be enabled). If the JRE plug-in is not on the client machine: 1. Install Netscape using the Recommended type of setup. Note that the installation program states that Java is not included. 2. Start the Netscape browser and navigate to the following URL to download the Sun Java Plug-in v1.4.1: Server Name>/adp/plugins/j2re-1_4_1-win-i.exe 3. In Netscape s Download dialog box, select a directory location to store the downloaded file. Write this file name down because you will need it to run the installer. 4. In the Save As dialog box, click the Save button to begin downloading the Sun Java Plug-in to the client machine. 5. Netscape 7.0 will now start to download the file. The Download dialog box will be replaced by a Netscape 7.0 Saving File dialog box which displays a progress indicator. 6. After the download is complete, the Saving File dialog box will remain open. Click the Reveal Location button in the Netscape 7.0 Saving File dialog box to open a Windows Explorer window at the location where the file was downloaded. 7. Close the Netscape 7.0 Saving File dialog box and the Netscape 7.0 browser. 8. To install the Java plug-in, double-click the j2re-1_4_1-win-i.exe file listed in the Windows Explorer ADP, Inc.

171 Installing and Setting Up a Netscape 7.0 Browser 9. The Sun Java Plug-in begins its installation. Part of its installation will prepare Netscape 7.0 to use the plug-in. 10. If you successfully installed the Sun Java Plug-in, start Netscape 7.0 and navigate to the Enterprise etime logon page. The JRE plug-in should now load and allow you to log on to the Enterprise etime server. After the Enterprise etime logon page has fully loaded, the form fields should be enabled. This indicates that the JRE plug-in was successfully installed and is running. You can now close the Windows Explorer window. Installing Adobe Acrobat Reader Adobe Acrobat Reader 4.05 or higher must be installed on all browser clients that you use to access reports. If it is not already installed, you can copy Acrobat Reader from the Enterprise etime CD or you can download it from the following Web site: Netscape does not require any additional configuration for Acrobat Reader. Enterprise etime Installation Guide for Windows 8-17

172 Chapter 8 Installing Enterprise etime Clients 8-18 ADP, Inc.

173 Chapter 9 Uninstalling Enterprise etime The InstallShield Uninstall facility reads the log that was created during the installation of Enterprise etime and performs operations to restore the system to its previous state. For example, if a registry entry was created, the entry is deleted. If a file was delivered or a shortcut created, the file or shortcut is deleted. Note: Sometimes, configuration items are not logged automatically and you must manually uninstall the items that are not removed as part of the InstallShield Uninstall procedure. The Enterprise etime installation procedure installs a number of OEM licensed components using vendor installation programs. To uninstall these components, the Enterprise etime uninstall program might invoke the vendor s uninstall program. This chapter contains the following sections:! Overview! Before Uninstalling! Uninstalling Enterprise etime! Uninstalling Enterprise Scheduler Only! Troubleshooting

174 Chapter 9 Uninstalling Enterprise etime Overview Enterprise etime components are uninstalled by using the standard Windows Add/Remove Programs capability. You can uninstall either of the following:! Enterprise etime, with or without the add-on product, Enterprise Scheduler. Note: If Enterprise Scheduler is installed, and you uninstall only Enterprise etime, Enterprise Scheduler will not work.! Enterprise Scheduler only The uninstall procedure removes:! All ADP files, shortcuts, registry entries, and configuration data from the computer.! All files, shortcuts, registry entries, and configuration data for OEM licensed components explicitly installed as part of the ADP Enterprise etime installation. Exceptions The Enterprise etime uninstall procedure does not remove the following components:! If you use Microsoft IIS Web server software, the uninstall procedure does not remove virtual directories that are defined in the IIS software. You must manually remove these virtual directories after you uninstall Enterprise etime.! The Enterprise etime uninstall procedure does not remove secondary Background Processors. If you used the Background Processor Registry Editor to install additional Background Processors on your server, you must also use the Background Processor Registry Editor to remove them. See page 3-36 for more information. 9-2 ADP, Inc.

175 Before Uninstalling Before Uninstalling All global settings for Enterprise etime are stored in the database, which updates properties files. All local information is stored in properties files. If you are uninstalling and reinstalling Enterprise etime, you should do the following before uninstalling: 1. From the Enterprise etime navigation bar, select System Configuration > System Settings and select the Local values tab. 2. Make note of all the settings. After you uninstall and reinstall Enterprise etime, you can re-enter the settings from step 2. Caution: If you are uninstalling a Kdemo installation, you must detach the existing Kdemo database files before uninstalling the product as described on page Also, if you want to save your Kdemo database, you must copy the Kdemo.mdf and the Kdemo.ldf files. If you do not copy these files, they will be deleted when you uninstall the application. Enterprise etime Installation Guide for Windows 9-3

176 Chapter 9 Uninstalling Enterprise etime Uninstalling Enterprise etime To uninstall Enterprise etime components: 1. Stop the application server by clicking the Stop button. 2. Select Start > Settings > Control Panel. 3. Double-click Add/Remove Programs. The Add/Remove Programs dialog box appears. 4. Select ADP Enterprise etime and click Change/Remove. 5. When you are prompted to confirm the deletion, click OK 6. When removing Enterprise etime, the system also prompts you to uninstall JRun. Click OK. 9-4 ADP, Inc.

177 Uninstalling Enterprise etime 7. After the UninstallShield splash screen appears, the Remove Programs From Your Computer status dialog box appears. When complete, the following message appears at the bottom of the dialog box 8. Click OK. 9. The Enterprise etime uninstall procedure uninstalls all necessary components. When the uninstall procedure is finished, it prompts you to restart your computer. Enterprise etime Installation Guide for Windows 9-5

178 Chapter 9 Uninstalling Enterprise etime Uninstalling Enterprise Scheduler Only To uninstall Enterprise Scheduler without also uninstalling Enterprise etime: 1. Stop the application server by clicking the Stop button. 2. Select Start > Settings > Control Panel. 3. Double-click Add/Remove Programs. 4. In the Add/Remove Programs dialog box, select Enterprise Scheduler and click Change/Remove. 5. When you are prompted to confirm the deletion, click OK: 6. Click Finish when the Maintenance Complete box appears. You do not need to reboot your system, but you will need to restart the application server. 9-6 ADP, Inc.

179 Troubleshooting Troubleshooting If you cannot uninstall Enterprise etime on a Windows 2000 system using Add/ Remove Programs, it is probably because of a corrupted installation log file called setup.ilg. To fix the problem, you must replace the corrupted setup.ilg file with a clean copy of setup.ilg. To do this, copy setup.ilg from C:\adp to C:\Program Files\InstallShield Installation Information\{AC40B27F-844F-4915-B267-9A6274F377CE} Note: The C:\Program Files\InstallShield Installation Information folder might be hidden by default. If it does, you have to clear the Hide extensions for known file types in the View tab under Folder options. Enterprise etime Installation Guide for Windows 9-7

180 Chapter 9 Uninstalling Enterprise etime 9-8 ADP, Inc.

181 Chapter 10 Upgrading Enterprise etime Upgrading from Enterprise etime v4 to v5.0 upgrades the database as well as installs the new version of the Enterprise etime product. Note: Before starting the upgrade, you should be proficient with backing up a schema (Oracle) or a database (SQL Server 2000). If you are not familiar with these functions, consult the database administrator s guide for your database software. This chapter describes how to upgrade to Enterprise etime v5.0 from Enterprise etime v4 and includes the following sections:! Task 1: Reconcile the Current Database! Task 2: Back Up the Current Database! Task 3: Uninstall Enterprise etime (v4.2 or earlier)! Task 4: Install Enterprise etime v5.0! Task 5: Run the Database Manager for v5.0! Task 6: Install Enterprise etime on Additional Machines Note: This chapter does not describe how to migrate from Enterprise etime 3.x to Enterprise etime 5.0. For information about migrating from version 3.x, contact TLM Support.

182 Chapter 10 Upgrading Enterprise etime Before You Begin Before you begin the upgrade process: 1. Stop Enterprise etime and ensure that no users are using the system. You should also allow adequate time to complete the upgrade. Although the actual time that the upgrade will take depends on the size of your database and the number of Enterprise etime machines that need to be upgraded, the following are some general guidelines for each of the upgrade tasks: Important: Before you begin the upgrade, stop all services. Task Approximate Time 1. Reconcile the current database. 10 to 30 minutes for a typical database although it could be longer for very large databases. This process can run unattended. 2. Back up the current database. Can vary from less than an hour to several hours depending on the database size and backup tools used. 3. Install one Enterprise etime v5.0 1/2 hour application server. 4. Run the Database Manager for v Install Enterprise etime on additional machines. This process can run unattended and the actual time depends on the database size. 1/2 hour per machine 6. Run stats and recompile database. Depends on the size of the database. Note: You do not need to generate new licenses if you are upgrading from Enterprise etime v4 to Enterprise etime v ADP, Inc.

183 Before You Begin 2. If you are using a SQL Server database, you should truncate the existing transaction log by doing the following: a. Open a command window by selecting Start > Run and enter Command in the Open box. b. Enter the following at the command prompt: backuplog <dbname> with truncate_only c. Identify the database logical name by entering: sp_helpdb<dbname> d. Enter the following: dbcc shrinkfile ( LogicalName ) For more information, refer to SQL Server Books Online for assistance. 3. When you make a change to the System Settings in the Enterprise etime user interface, a custom properties (for example, custom_wfc.properties) is created. If you are upgrading Enterprise etime from v4 to v5.0 or if you are installing a v5.0 service pack, it is possible that a custom file that you created in v4 will be modified as part of the upgrade. To ensure that the settings in these custom files are maintained, do the following: a. Before you install Enterprise etime v5.0 or a v5.0 service pack, print out all custom properties files and review their content. b. After you install v5.0 or a v5.0 service pack, compare the copy of the custom properties files that you created in step a to the custom files currently installed. c. If necessary, manually modify the custom files. Enterprise etime Installation Guide for Windows 10-3

184 Chapter 10 Upgrading Enterprise etime Task 1: Reconcile the Current Database You must now use the Reconcile Database function in the Database Manager v4.x program to verify that your existing Enterprise etime database contains all of the necessary database objects. Be sure to use the Reconcile Database function in the Database Manager program that was installed with your current version of Enterprise etime, not the version to which you are upgrading. To identify your current version of Enterprise etime, select System Configuration > System Information in the Enterprise etime navigation bar, then select the Applications tab. Note: You access the Database Manager, which is located on the application server, through the browser. You must start the application server before running Database Manager. To run the Database Manager Reconcile Database option: 1. Start your browser and enter the following URL: //<AppServer>/wfc/html/dbmgr.jsp where <AppServer> is the name of your application server. The Database Manager logon window appears: 2. Enter the database logon and password in the appropriate text boxes, for example, TKCSOWNER. If you are using a Kdemo database, select the Click if you are using a Kdemo database button ADP, Inc.

185 Task 1: Reconcile the Current Database Caution: You must select this check box if you are using Kdemo for the correct scripts to be run against the Kdemo database. If you do not select the check box, a different set of scripts will be run, and the database will become unstable. When finished, click Log on. 3. In the main Database Manager dialog box, select the current Data Collection and Enterprise etime versions that you want to reconcile and click Reconcile from the menu at the top of the dialog box to begin the operation. 4. Click View Status to monitor the progress of the reconcile, refreshing the screen as necessary. 5. When the reconcile process is finished, check the Enterprise etime log (ADP\wfc\log\wfc.log) to view the output of the reconcile. DBManager does not report install or upgrade errors interactively. You must review the wfc.log file carefully to ensure that the upgrade was truly Enterprise etime Installation Guide for Windows 10-5

186 Chapter 10 Upgrading Enterprise etime successful. A clean reconcile does not guarantee a successful upgrade of your Enterprise etime database. Caution: If the wfc.log file contains errors, contact TLM Support. Do not continue with the upgrade ADP, Inc.

187 Task 2: Back Up the Current Database Task 2: Back Up the Current Database Ensure that all users are logged off from the system, then back up your current Enterprise etime database before completing the remaining tasks in this chapter. The upgrade process does not allow you to return your database to its original state if a problem arises. Failure to back up your database properly could result in the permanent loss of data. If you are using a Kdemo database, you must detach the database before starting the upgrade procedure as described on page Enterprise etime Installation Guide for Windows 10-7

188 Chapter 10 Upgrading Enterprise etime Task 3: Uninstall Enterprise etime (v4.2 or earlier) Whether or not you need to manually uninstall Enterprise etime v4.x depends on the operating system and version of Enterprise etime installed.! If you are upgrading from Enterprise etime v4.2 or earlier, you must uninstall your current version of Enterprise etime before you can install v5.0. See Chapter 9 for more information. When you upgrade in this way, the licensing directory is removed. Therefore, you must copy the.lic file to a temporary folder before you upgrade. When the upgrade is complete, copy the files back to the \adp\wfc\licensing directory and delete the generic adp.lic file that was installed during the upgrade.! If you are upgrading from Enterprise etime v4.3 to v5.0, you do not have to uninstall Enterprise etime before you start the upgrade process. Move to Task ADP, Inc.

189 Task 4: Install Enterprise etime v5.0 Task 4: Install Enterprise etime v5.0 Now, you are ready to install a Enterprise etime v5.0 application server as described on page 3-3. If your installation includes additional application servers, Background Processors, or Enterprise etime Setup machines, you need to install the product on each machine, but that can be done after the database is upgraded. Note: If you are upgrading from Enterprise etime v4.3, you do not need to uninstall the Enterprise etime v4.3 software before you install the v5.0 software. When you start the installation procedure, click Yes when the following message appears: If you are upgrading from Enterprise etime v4.2 or earlier, you must uninstall the current version before upgrading to Enterprise etime v5.0. Additionally, if you are upgrading from v4.2, you must create two additional file groups (SQL Server) or tablespaces (Oracle): tkcs6 and tkcs7. See the Enterprise etime Database Installation Guide for information about creating file groups. Enterprise etime Installation Guide for Windows 10-9

190 Chapter 10 Upgrading Enterprise etime Task 5: Run the Database Manager for v5.0 The next step is to run Database Manager again, this time using Enterprise etime v5.0, which you just installed. 1. Start your browser and enter the following URL: //<AppServer>/wfc/html/dbmgr.jsp where <AppServer> is the name of your application server that is running Enterprise etime v In the Database Manager logon window, enter the database logon and password in the appropriate text boxes, for example, TKCSOWNER. If you are upgrading a Kdemo database, select the Click if you are using a Kdemo database button. Caution: You must select this check box if you are using Kdemo for the correct scripts to be run against the Kdemo database. If you do not select the check box, a different set of scripts will be run, and the database will become unstable. When finished, click Log on. 3. In the main Database Manager dialog box, select the Data Collection and Enterprise etime versions that you installed in Task 3 and click Run from the menu at the top of the dialog box to begin the operation ADP, Inc.

191 Task 5: Run the Database Manager for v Click View Status to monitor the progress of the reconcile, refreshing the screen as necessary. 5. When the process is finished, the database upgrade is complete. Check the Enterprise etime log (ADP\wfc\log\wfc.log) to view the output of the reconcile. DBManager does not report installation or upgrade errors interactively. You must review the wfc.log file carefully to ensure that the upgrade was truly successful. A clean reconcile does not guarantee a successful upgrade of your Enterprise etime database. Caution: If the wfc.log file contains errors, contact TLM Support. Do not continue with the upgrade. 6. When you are finished using Database Manager, close your browser to exit. 7. Stop and start the Enterprise etime application. 8. Verify that all the processes are running as described on page 6-4. Enterprise etime Installation Guide for Windows 10-11

192 Chapter 10 Upgrading Enterprise etime Task 6: Install Enterprise etime on Additional Machines If your Enterprise etime environment includes multiple application servers, Background Processors, or Enterprise etime Setup machines, you should now upgrade the application on each of these machine as described in Chapter 3. Note: If you are upgrading from Enterprise etime v4.3, you do not need to uninstall the Enterprise etime v4.3 software before you install the v5.0 software. When you start the installation procedure, click Yes when the following message appears: If you are upgrading from Enterprise etime v4.1 or v4.2, you must uninstall the current version before upgrading to Enterprise etime v ADP, Inc.

193 Chapter 11 Troubleshooting If you encounter problems installing Enterprise etime or you cannot successfully connect to the server from your browser, check the issues described in this chapter. If you are still having problems, contact TLM Support. This chapter explains how to address the following installation issues:! Common Installation Error Messages! Apache Service Not Registering as a Service! MSDE Installation Fails (Kdemo)! Background Processor Does Not Start! The kronos.exe Process Does Not Stay Loaded! Application Server Starts in Offline Mode! Memory Impact when Making Large Organization Map Changes

194 Chapter 11 Troubleshooting Common Installation Error Messages Although not an exhaustive list, you may encounter one of the following error messages when you are entering information to the Enterprise etime installation procedure: Message Host name does not match the local server name Local server name cannot be resolved. User name specified does not exist. Explanation/Solution Re-enter the correct local server name and continue with the installation. Re-enter local server name and continue with the installation. Enter valid user name and continue with the installation. Other installation error messages may appear after the installation; these errors must be corrected manually. Some possible messages include: Message Explanation Solution Cannot set SeTcbPrivilidge on the account specified. Cannot set SeServiceLogonRight on this account. Cannot open a connection to the service controller. Cannot open JRun Default Service service. This is the highest of all Windows NT privileges. It allows a user to have total control over a local server. The user account that starts up JRun must have this privilege. This privilege allows a user to start up an NT service. This error is highly unlikely. It basically means that Windows API failed to fetch a handle to a Windows NT service. JRun service has not been configured by the installation. Grant this privilege to the user as described on page Grant this privilege to the user as described on page Check if the user account has SeServiceLogon privilege as described on page Create a default JRun service as described on page ADP, Inc.

195 Common Installation Error Messages Message Explanation Solution Cannot assign the specified user account to JRun Default Service service (invalid password). The JRun user name and/or password are not valid. Check the password or user name as described on page Changing User Privileges To change user privileges: 1. Select Start > Settings > Control Panel > Administrative Tools > Local Security Policy. 2. In the Local Security Settings box, right-click Log on as a service and select Security. 3. In the Local Security Policy Setting box, select Add. 4. In the Select Users or Groups dialog box, select the appropriate user and click OK. Enterprise etime Installation Guide for Windows 11-3

196 Chapter 11 Troubleshooting Changing JRun Service Password This error usually appears if your PC or network logon password changed after Enterprise etime was installed. To edit the JRun Default Server Service to allow logons to occur with the correct password: 1. Select Start > Settings > Control Panel. 2. Double-click Administrative Tools, then double-click Services. 3. Double-click JRun Default Server. 4. Select the Log On tab. 5. Edit the Password and Confirm Password fields with the correct password. Click Apply and OK to save changes and exit. 6. Close the Services window and the Control Panel window. 7. Depending on your configuration, the service may need to be shut down and restarted. If the password change is allowed, a restart is generally not necessary ADP, Inc.

197 Common Installation Error Messages Creating the JRun Default Server To create a JRun default service if there is no JRun Default Service in the Service Manager: 1. Open a command window by selecting Start > Run and enter command in the Open box. 2. In the command window, change the active folder by entering the text in bold at the c:\> prompt: c:\> cd C:\ADP\JRun\bin 3. Creates a JRun default server by entering the following bold text: C:\ADP\JRun\bin> jrunsvc -install default 4. Change the active folder by entering the following bold text: C:\ADP\JRun\bin> cd C:\ADP\wfc\bin 5. Set up the user account for JRun default server by entering the following bold text: C:\ADP\wfc\bin> jrunupdate -u <NT_username> <NT_password> where <NT_username> is your user name and <NT_password> is your password. If you prefer, you can set the password as described on page Enterprise etime Installation Guide for Windows 11-5

198 Chapter 11 Troubleshooting Apache Service Not Registering as a Service The Hypertext Transfer Protocol (HTTP) uses port 80 by default. If another application or service is using port 80 when you install the Enterprise etime application server using Apache as the web server, the installation program tries ports 81 through 100.! If the installation program is able to use a port other than port 80, the following message appears:! If ports 81 through 100 are all busy, the installation program returns to port 80 and issues the following message: What you do next depends on which error message you see. Apache Uses a Different Port If the Apache service is using a port other than port 80, the default URL to Enterprise etime will not work. You must enter the port number in use after the server name in order to log on to Enterprise etime. For example: ADP, Inc.

199 Apache Service Not Registering as a Service To avoid entering the port number in the URL, you must first stop or disable the other services using port 80, then change the port number back to port 80 by doing the following: 1. Open a command window. You can do this by selecting Start > Run and then entering Command in the Open box. 2. Stop Apache by entering the following bold text in the command window: C:\> cd c:\adp\apache\bin C:\adp\APACHE\BIN> Apache -k uninstall -n Apache 3. In a text editor (such as NotePad), open C:\ADP\Apache\conf\httpd.conf and do the following: Find the following Replace with Listen xx Listen 80 ServerName yy:xx ServerName yy:80 where xx is a port number and yy is the machine name. 4. Return to the command window to restart the Apache service by entering the following: C:\adp\APACHE\BIN> Apache -k install -n Apache. Setup Fails to Create Apache Service If the installation procedure fails to create the Apache service because ports 80 through 100 are in use, you must determine what applications or services are listening on open ports, then follow the procedure in the preceding section to have Apache listen on the appropriate port. Note: Fport for Windows systems or LSOF or Netstat for UNIX systems are two commonly available applications that identify open ports and the applications or services bound to them. Enterprise etime Installation Guide for Windows 11-7

200 Chapter 11 Troubleshooting MSDE Installation Fails (Kdemo) If you do not have SQL Server 2000 installed on your PC, the installation program installs MSDE as part of the Kdemo installation process. The MSDE installation will fail, however, if you have monitoring tools such as antivirus software or Belarc BellManage running on your PC and you will see the following message: You must disable these tools before MSDE is installed and restore them after the installation ADP, Inc.

201 Background Processor Does Not Start Background Processor Does Not Start If the Background Processor service does not start, or starts but will not stay running, do the following: 1. For a Background Processor on Windows, check the Windows Application Event Viewer for error messages from a source of Enterprise etime. Address any errors found here and retry the Background Processor startup. 2. When the Background Processor service starts, the Enterprise etime application server attempts to log on to it using the totalizer account. Ensure that this can happen by doing the following:! Use a Web browser to connect to the Enterprise etime logon page with the user name of totalizer and the password set up for this account. If this fails, verify that the totalizer user account exists and verify the user account s password.! Refer to Chapter 7 for more information about user and database accounts and how to correctly change their passwords. 3. If the connection as totalizer succeeds, the Background Processor will attempt to connect to the database with ODBC, using the data source name entered during installation (or one that has been subsequently entered using the Background Processor Registry Editor). Verify that this stage will work by testing the connection to the database as follows: a. On the Background Processor system, open Windows ODBC Administrator. (On a Windows 2000 system, you do this by selecting Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC). b. On the System DSN tab, highlight the data source used by Background Processor and click Configure. c. Click TEST. Enterprise etime Installation Guide for Windows 11-9

202 Chapter 11 Troubleshooting d. Enter the database account and password used by this data source. Note: To verify which database account is used by a data source, open Enterprise etime in your browser, select System Configuration > System Settings from the navigation bar, and click the Data Source tab. Verify that all information on this tab is correct. If it is correct, use the database account name listed as the dsnnamen.usr for the data source for the test connection. e. If the ODBC test fails, ensure that it is configured properly. Also verify that the database account and password can connect to the database with some RDBMS-specific means (for example, for Oracle, verify that the account can connect using SQL*Plus). 4. Read the WFCauthentication.log file for any errors that may also give clues as to why the Background Processor will not start ADP, Inc.

203 The kronos.exe Process Does Not Stay Loaded The kronos.exe Process Does Not Stay Loaded If you start the Enterprise etime application server and javaw seems to load only to around 57MB, Kronos.exe briefly loads, but then disappears, and other processes such as totalizer.exe do not load, do the following: 1. Check the licensing.log in the \adp\wfc\logs directory. If you see the error cannot open lock file c:\flexlm\adp, the problem is probably related to folder permissions. 2. Check the permissions for the folder drive:\flexlm (typically, installed on the root or C drive). If the Everyone group does not have full control, allow full control. 3. Restart Enterprise etime. You may need to experiment to see how restrictive permissions can be. Enterprise etime Installation Guide for Windows 11-11

204 Chapter 11 Troubleshooting Application Server Starts in Offline Mode If you install Enterprise etime successfully, but the application server does not start in online mode, you should check the wfc.log file. Some of the more common errors that can cause this behavior include:! Exception Attempting to Connect to Database (Windows)! Exception Loading Configuration (Oracle)! Permission Denied Error! Database Version Mismatch Exception Attempting to Connect to Database (Windows) If the application server attempts to connect to a SQL Server 2000 database during startup and fails to authenticate, the application server will start in offline mode. Within the wfc.log, a line reports: WFC.PROPERTIES system 1 ERROR Exception attempting to connect to database, url = jdbc:inetdae7:payroll:1433?database=tkcsdb java.sql.sqlexception: []Login failed for user 'tkcsowner'. Reason: Not associated with a trusted SQL Server connection. This occurs when SQL Server 2000 is configured to accept Windows authentication only. SQL Server must be configured to authenticate via SQL server authentication. To change the server authentication: 1. Open SQL Server Enterprise Manager and select the SQL Server PC. 2. Right-click and select Properties. 3. Open the Security tab. 4. Ensure the SQL Server and Windows authentication mode is selected and not Windows Only. 5. Restart the SQL Server Services and then the Enterprise etime services ADP, Inc.

205 Application Server Starts in Offline Mode Exception Loading Configuration (Oracle) If the database account executing a SELECT statement does not have permissions to access the table in question, the following error will appear in the wfc.log file: ERROR SQLException trying to load configuration WtkGlobalSetting from database, query = SELECT NAME, CONTENT FROM WTKGLOBALSETTING java.sql.sqlexception: ORA-00942: table or view does not exist The error log indicates that the startup process began normally and successfully loaded the first six properties files. This error occurred when attempting to read data from the WTKGLOBALSETTINGs in the database. An ORA error usually means one of two things:! The table or view mentioned truly does not exist in the database! The database account performing the SELECT statement does not have permissions to access the table in question To correct this problem: 1. Use Oracle s DBA Studio utility to check the database schema and determine if the TKGLOBALSETTING table exists. 2. If that table (or others) do not exist, the database installation may not have been completed properly. Ensure that key steps were followed correctly (for example, ensure that the required tablespaces (tkcs1 tkcs5) are created with the correct names). 3. If you find errors in the tablespace names, rebuild the empty database and rerun Database Manager to build the empty database. 4. Restart the Enterprise etime application server. For more information about setting up an Oracle database, refer to the Enterprise etime Database Installation Guide. Enterprise etime Installation Guide for Windows 11-13

206 Chapter 11 Troubleshooting Permission Denied Error During the startup, the server issues a SELECT from the VU_METAJOINPARAM view, but it fails for the reason shown in the wfc.log file: WFC.STARTUP system 1 ERROR java.sql.sqlexc eption: [NH-WS01]SELECT permission denied on object 'VU_METAJOINPARAM', database 'tkcsdb', owner 'dbo'. Other symptoms may include:! Not all Enterprise etime services start! JAVAW does not start up completely To resolve permission problems, do the following: 1. Run a database reconcile. The reconcile will reveal errors, such as SELECT permissions missing for the VU_METAJOINPARAM view, as well as every other view in the Enterprise etime database. Permissions may also be incorrect for all stored procedures and tables. 2. Restore the missing permissions to these database objects by running the WTKGRT.SQL script. This is located under the WFC\SCRIPTS directory hierarchy on the application server where Enterprise etime is installed. 3. Run a new database reconcile to confirm all previously reported errors database errors have been resolved. 4. Restart the Enterprise etime application server. It should successfully start in online mode so users are able to log on ADP, Inc.

207 Application Server Starts in Offline Mode Database Version Mismatch When the application server detects a problem when it validates, at startup, that the Enterprise etime database is the correct version for the application server software, a review of the wfc.log log shows the following error: WFC system 3 INFO JDBC Driver name and version: i-net SPRINTA WFC.STARTUP system 1 ERROR *** Failed to start service ServiceSphere: com.kronos.wfc.persistence.persistenceexception: Database version mismatch WFC.STARTUP system 1 ERROR at com.kronos.wfc.persistence.internal.database.validatedbversi on(database.java:1649) Other symptoms may include:! Not all Enterprise etime services start! JAVAW does not start up completely To troubleshoot this error: 1. Verify that the database is the correct version. Use the following database query: SELECT * FROM KCSCURRENTVERSION 2. Verify the version of Enterprise etime application server software installed on the application server. The database and application server may be different versions if a restore was recently performed using an old database backup file. 3. If a discrepancy is found, replace the database with the correct version. 4. Restart the Enterprise etime application server. It should start up successfully in online mode. Enterprise etime Installation Guide for Windows 11-15

208 Chapter 11 Troubleshooting Memory Impact when Making Large Organization Map Changes If you move or copy/paste an organization map that is on the order of 30,000 nodes or more, the following message appears, warning you that you are about to embark on a memory-intensive operation. A large number of locations or jobs was selected for pasting. This operation may require additional system resources. Please increase your browser's memory to at least 512 MB if the system experiences difficulties. Go to Windows Control Panel > Java Plug-in. Type "-Xmx512M" into the "Java Runtime Parameters" field and select Apply. The client machine should have at least 512 MB of memory and 256 MB of virtual memory. To increase virtual memory on a Windows browser: 1. Select Start > Settings > Control Panel > Java Plug-in. 2. Enter -Xmx512M into the Java Runtime Parameters box. 3. Click Apply. You do not need to adjust the virtual memory on Macintosh browsers running Mac OS 10.2 and higher. If you attempt to move or copy/paste a large organization map without adequate memory, an error message appears, and you cannot complete the operation. You can, however, continue to access different parts of the application after the out-ofmemory exception ADP, Inc.

209 Appendix Enterprise etime Directory Structure The Enterprise etime directory structure is designed to support separately installed Enterprise etime applications and application extensions as well as core components such as infrastructure, UI framework, and basic business functions. The directory structure facilitates the installation of additional Enterprise etime applications in such a way that all of their installed subcomponents are contained in one application-specific subdirectory. This not only makes the installation and removal processes simpler and more robust, but also improves the reliability of the runtime discovery processes necessary to load an extension into Enterprise etime. This appendix describes the directory structure of the files delivered by the Enterprise etime installation procedure.

210 Appendix Enterprise etime Directory Structure Directory Structure The following figure illustrates the Enterprise etime directory structure. Thirdparty components such as Apache (if installed) and JRun are listed first, then the wfc directory appears. Within the wfc directory are all of the core and application components used by Enterprise etime products. Third-party components Enterprise etime applications Core components Appendix-2 ADP, Inc.