IBM Kenexa LMS Version Installation Guide. October 2015 IBM

Transcription

1 IBM Kenexa LMS Version Installation Guide October 2015 IBM

2

3 IBM Kenexa LMS Version Installation Guide October 2015 IBM

4 Note Before using this information and the product it supports, read the information in Notices on page 51. This edition applies to the October 2015 release of LMS, and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Terms and conditions for product documentation Permissions for the use of these publications are granted subject to the following terms and conditions. Applicability These terms and conditions are in addition to any terms of use for the IBM website. Personal use You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these publications, or any portion thereof, without the express consent of IBM. Commercial use You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of IBM. Rights Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any information, data, software or other intellectual property contained therein. IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by IBM, the above instructions are not being properly followed. You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations. IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE. Copyright IBM Corp iii

6 iv IBM Kenexa LMS Version 4.2.4: Installation Guide October 2015

7 Contents Terms and conditions for product documentation iii Chapter 1. Requirements Web/Application Server Database Server Learner Software Requirements Learner Hardware Requirements Compatible Browsers for Learners User Interface Languages Mobile User Requirements (Optional) Mobile App Delivery Requirements Chapter 2. Configure MS SQL Server 2008/ Software Requirements Chapter 3. Configure Oracle 10g or 11g 7 Software Requirements Installation Prerequisites File Inventory Chapter 4. Installing LMS on Windows 2008 Server Chapter 5. Upgrading to LMS from Versions Prior to Setting Up the Installation Site Upgrading to LMS Chapter 6. Removing an LMS Site Chapter 7. Software Release Definitions 37 Chapter 8. Verifying Mixed Mode Authentication Chapter 9. Start Services Chapter 10. Configuring McAfee to Allow Mass s in LMS Chapter 11. Defining a Local Security Policy Chapter 12. Removing Old LMS Services Chapter 13. Configuring Settings for IE Notices Trademarks Copyright IBM Corp v

8 vi IBM Kenexa LMS Version 4.2.4: Installation Guide October 2015

9 Chapter 1. Requirements The following section lists the requirements for the different components of an LMS installation. Web/Application Server LMS operates on a Windows based web/application server. Table 1. Window-based requirements. The following table displays the software and hardware requirements for the web/application server. Software Requirements Hardware Requirements v v v v v v Operating System Windows Server 2012 (LMS version 3.5 and higher) Windows Server 2008 R2 (32 bit or 64 bit) Application Server Tomcat (bundled on the installation CD-ROM) Database Drivers-Oracle Oracle 10g or 11g Native OCI Driver, with client installed (the version of Oracle client drivers must exactly match the version of the server) Database Drivers-SQL Server jtds JDBC driver (bundled on the LMS installation CD-ROM) IBM JDK Version 6 (bundled on the installation CD-ROM) TCP/IP v 2.0 GHz Xeon class processor or higher v Minimum 200 GB hard disk space v Minimum 8.0 GB RAM Database Server The database server must be installed on a separate server and NOT on any servers that are running instances of the LMS Application software. Note: IBM does not provide Oracle or MS SQL server databases or server software. Table 2. Database Requirements. The following table displays the software and hardware requirements for the MS SQL and Oracle database servers. Software Requirements Hardware Requirements v v MS SQL Server SQL Server 2012 SQL Server 2008 (32 bit and 64 bit) SQL Server 2008 R2 and PPT import/export. Oracle Server Oracle 10g ( ) or Oracle 11g ( ) Oracle 11g Release 2 v See DB vendor for DB server hardware requirements. v * MS SQL Server 2005 no longer supported Copyright IBM Corp

10 Learner Software Requirements Java Runtime Environment 6 or 7is required for survey authoring, available to the System Administrator, Training Administrator, and Manager roles. Learner Hardware Requirements Specifies the hardware requirements for learners who are accessing courses. v 1024 x 768 resolution (or higher) v 256K Internet connection (or higher) v Sound card and speakers (if required by the content) Compatible Browsers for Learners Learner access is supported by different browsers on different Operating Systems. Table 3. Learner Delivery Software Requirements.. The following table displays the software requirements for learners who are accessing courses through the LMS. Browser Windows XP Windows 7 Windows 8* Windows 8** Mac OSX IE 8.x X X IE 9.x IE 10 X X IE 11 X X X Firefox 38 X X X Chrome 45 X X X Safari 8 X v Windows 8* Standard Browser Window v Windows 8** Metro-Style with touchscreen support User Interface Languages The LMS interface can be translated into various languages. Table 4. Available user interface languages. The following table displays the languages available for the LMS interface. Included Braz-Portuguese English French German Italian Spanish (Latin-Am) Optional Japanese Thai Polish French Canadian Dutch Chinese (Traditional) Chinese (Simplified) Mobile User Requirements (Optional) Native web browser that is installed by default on supported mobile devices. 2 IBM Kenexa LMS Version 4.2.4: Installation Guide October 2015

11 Mobile App Delivery Requirements There are software and hardware requirements for accessing LMS through the mobile app. Table 5. Mobile app requirements. The following table displays the mobile requirements for LMS. Software Requirements Hardware Requirements v v v iphone (Student Only) Operating System: ios 4.0+ ipad Mobile (Students and Instructors) Operating System: ios 4.0+ Android Mobile Operating System: Android 2.2+ v Mobile device requires an SD card Chapter 1. Requirements 3

12 4 IBM Kenexa LMS Version 4.2.4: Installation Guide October 2015

13 Chapter 2. Configure MS SQL Server 2008/2012 Before you install the LMS, you must have a properly configured SQL Server 2008/2012 instance. The SQL Server instance must meet the following requirements: v Have an SA password configured (never leave blank). v Be configured with mixed mode authentication (see Chapter 8, Verifying Mixed Mode Authentication, on page 39). v Have the instance name set to the default or the same as the hostname - named instances are not supported. v Be configured with a case insensitive collation, such as sql_latin1_general_cp1_ci_as. The following diagram illustrates how MS SQL Server interacts with the various components of the LMS. Figure 1. Interaction between MS SQL Server and LMS Components Software Requirements Lists the software requirements for MS SQL. v Microsoft SQL Server 2008, LMS SQL Server 2008 R2, or MS SQL Server 2012 installed on server v MDAC v2.6 or greater on Client and Server (automatically installed with SQL Server) v Microsoft SQL Server ODBC driver software that is installed on authoring clients When SQL Server is properly configured, proceed to Chapter 4, Installing LMS on Windows 2008 Server, on page 11. Copyright IBM Corp

14 6 IBM Kenexa LMS Version 4.2.4: Installation Guide October 2015

15 Chapter 3. Configure Oracle 10g or 11g Before you install the LMS, you must have a properly configured Oracle 10g or 11g instance. Note: If the LMS webserver will be installed on a different machine than the Oracle database (recommended), the Oracle client software must be installed on the machine where the webserver resides. The Oracle database: v Should be exclusive to the LMS application - there should be no other applications using it. v Should not contain any data from any previous applications and should be completely blank other than the seed data that Oracle installs. The following diagram illustrates how Oracle interacts with the various components of LMS. Figure 2. Interaction between MS SQL Server and LMS Components Software Requirements Lists the software that is needed to run the LMS. v Oracle , or 11.2 must be installed on the server (32 or 64-bit version). v Oracle 10g or 11g Client Software must be installed on the webserver (32 or 64-bit version). v The database must be created using the AL32UTF8 character set to support globalization. v The setting blank_trimming=true must be set in the init.ora or spfile.ora file. v The setting nls_length_semantics=char must be set in the init.ora or spfile.ora file. v The default setting for Oracle is 150 processes. To check the parameter setting for # of processes, open SQLplus and query show parameters processes. The number of Oracle processes needs to be twice the number of Apache Tomcat Threads. v To set this, open SQLPlus and run: alter system set processes=900 scope=both; The number of Oracle processes must be twice the number of Apache Tomcat Threads. If you get an error when you run the query, go to the init file and change its processes number to XXXX (whatever number of processes you want to use). Then, run the following: alter system set processes=1000 scope=spfile;. Be sure to run show parameters processes to double check its setting. Restart the database after you make the changes. Copyright IBM Corp

16 Installation Prerequisites Lists the installation prerequisites for the master script to run properly. v Sys users password v Database Host String- tells Oracle the database to which it must connect. This is created by using the netmanager configuration assistant or netmanager assistant utilities. The database host string is also known as the Netmanager connect string, TNS alias, or local net service name. The name hoststring is used throughout this document. v Directory for log files - the master script generates log files, which you should check at the end of the installation for errors. v Directory for Oracle data files - New data files are stored in this directory and initially 100 MB of space. File Inventory Describes all of the scripts that are required to create your Oracle database - these scripts are presented to you during the installation. Oracle 11g uses the 10g scripts. v Oracle_install_ev_schema_.sql - master command file that calls all of the required files that are used during the creation of the LMS database objects. It must be run to install the LMS for Oracle database schema objects. This script is run by using the Oracle Sys account, and calls all of the other subscripts in the proper order. oracle _analyze_.sql - generates statistics on all EVS objects. oracle _recompile_.sql - recompiles all EVS objects. oracle _roles_.sql - creates two Oracle system roles. - ADMINS role - DEVELOPERS role. Note: Both of these roles are required for the LMS application. oracle _seed_data_.sql - contains SQL statements that load seed data for LMS. oracle _tablespace_.sql - used to create the following tablespaces that are required for the LMS database objects: - Content - tablespace for data that is dynamic. - ContentStatic -tablespace for data that is static. - ContentStaticNdx - tablespace for index data for the ContentStatic data. - ContentNdx - tablespace for index data for the Content data. - ContentTemp - tablespace for temporary objects. Table 6. Tablespace Sizes. The following table details the size settings for all tablespaces: TableSpace Name Size Initial Next Max Extents % Increase Content 150M * * * * ContentStatic 50M * * * * ContentStatisNdx 75M * * * * ContentNdx 75M * * * * ContentTemp 100M * * * * * These requirements are determined automatically with locally managed extents. Note: The tablespace sizes mentioned earlier are just to begin with; they need to be increased according to data use. v oracle_users.sql - creates two User accounts. 8 IBM Kenexa LMS Version 4.2.4: Installation Guide October 2015

17 DBO (database owner) - user account that owns all of the physical objects for the LMS application. Portalclient - default user that connects over the web through the application server to the database. Note: Both users are required for the LMS application. When Oracle is properly configured, proceed to Chapter 4, Installing LMS on Windows 2008 Server, on page 11. Chapter 3. Configure Oracle 10g or 11g 9

18 10 IBM Kenexa LMS Version 4.2.4: Installation Guide October 2015

19 Chapter 4. Installing LMS on Windows 2008 Server The following steps guide you through the installation of LMS About this task You might encounter an error message that reads, "Error XXX.msp was rejected by digital signature policy". You must cancel the installation and follow the instructions in Chapter 11, Defining a Local Security Policy, on page 45 before reattempting installation of the LMS. Procedure 1. Select the provided link to start the LMS installer, and run the installer. 2. Select Next to begin the installation. 3. Enter the location in which to install the LMS files. The location must be a clean directory. If a location does not exist, the installer creates one for you. 4. Select Install, and select OK at the prompt. 5. The files are installed. This process takes several minutes. 6. After the files are installed, select OK at the prompt. The Config Wizard launches. During this portion of the installation, the database is created and the LMS site is configured. 7. Application server and host settings are configured on the Web tab. Provide the following information: v Application Name: This is the portion of the site URL that is created after the hostname. For example, The application name does not have to match the name of the database or application directory. v Web Protocol: In most cases, http is the appropriate selection. However, if your server is configured for SSL, you can select https. If you select https, you must do one of the following: v Select the SSL via the tomcat radio button if you are securing the connection that uses Tomcat. Enter the name of the keystore file in the Keystore File field, and enter the key store password in the Keystore Pass field. v Select the SSL via the intermediary radio button if you are securing the connection through an intermediary server. v IP Address (optional): If your application server supports multiple IP addresses, you can specify an IP address to use for this Evolution instance. This is used for the address attribute of the Tomcat server.xml file. v External and Internal Port Number: This is the port that is used by the browser to reach the application and the port on which the application listens. These typically are the same number, unless there is a device or service between the browser and Tomcat such as an SSl accelerator. There must not be any other applications that are using this port. v External Host Name: This is the server name in the site URL, for example, If you enter a fully qualified domain name in the Domain field, then that is reflected in the site URL, for example, You can also substitute the server IP address in place of the server name. v Shutdown Port Number: If the IP Address field is empty, the shutdown port number defaults to 1 + internal port number. If the IP Address field has a value, the shutdown port number defaults to 11 + the last IP octet. The port number is verified to be unique for the server. v JVM Type: This is the type of Java Virtual Machine being used. Select either 32-bit or 64-bit, depending on the type of hardware your operating system is using. For Oracle DB's, you must have the matching client (32-bit client if you use the 32-bit jvm; 64-bit client for 64-bit jvm). 8. For SQL, select the MS Sql Server radio button and enter the following information: Copyright IBM Corp

20 v Admin User: This defaults to sa. v Admin Password: This is the SA password. v User: This is the client account name. v Password: This is the client user password. The default is K0wl3dg3N. If you already have a portalclient user, change the password. The default for previous versions of Evolution is shark. v Host Address: This is the name of the database server. If the application and database will be on the same server, enter localhost. v Host Port: This is the IP port number of the database service - the default port is To use named pipes instead of TCP/IP, set the port to zero. v Database Name/SID: This is the name of your LMS database. This name does not have to match the Application Name or installation directory name. Note: The database name cannot begin with a number. Follow the guidelines that are recommended for your version of SQL Server. v Minimum and Maximum Connections: This is the smallest and largest number of database connections that are opened at application startup. The maximum must be at least 10% larger than the Maximum Connections allowed on the Database tab. 9. For Oracle, select the Oracle radio button and enter the following information: v Admin User: This defaults to dbo. v Admin Password: This is the dbo password. v User: This is the client account name. v Password: This is the client user password. The default is K0wl3dg3N. If you already have a portalclient user, please change the password. The default for previous versions of Evolution is shark. v Database Name/SID: This becomes the name of your LMS database. This name does not have to match the Application Name or installation directory name. v Minimum and Maximum Connections: This is the smallest and largest number of database connections that are opened at application startup. The maximum must be at least 10% larger than the Maximum Connections allowed on the Database tab. v Oracle Home: This location contains the bin and JDBC directories. The wizard should auto-detect this for you. 10. Select the Services tab. Configure the following information: v Select the services that you want to install. You can specify the beginning of the name for each service in the Naming prefix field. Also, if you want your services to run on a different local admin account, select the Change services account check box and fill in the account information. The user name should either include the domain, for example, domain\username, or if running on the built-in domain, should be entered in the format.\username. Note: You can also change the account information on the Login tab of the Task Service. v Minimum and Maximum Threads: This is the smallest and largest number of Tomcat threads to allocate at startup. The maximum should be at least 10% smaller than the Maximum Connections allowed on the Database tab. v Minimum and Maximum Memory Megabytes: This is the smallest and largest amount of memory to allocation for the startup of the application. The default values (for example, 64M for minimum and 1024M for maximum) are typically acceptable. 11. Select the Integration tab. This tab helps to combine the LMS and Participate into the IBM Kenexa LMS. v KLS Secret Key - Allows Participate and LMS to communicate behind-the-scenes. The default value can be changed, and should be changed when there are multiple LMS installations. v Participate URL - The full URL for the Participate instance, for example, servername.domain.com:port/pe v Encryption Key - The key is used to encrypt and decrypt the token string that is shared between LMS and Participate 12 IBM Kenexa LMS Version 4.2.4: Installation Guide October 2015

21 12. When your settings are correct, select the Commands tab and select Automatic Configuration. If you are using SQL Server, proceed to Step For Oracle, the auto-configuration stops when the Oracle scripts are unpacked and the scripts display in their storage directory. Leave the Configuration Wizard open, as you might need later. 14. Create a blank Oracle database. 15. Start SQL*Plus by selecting Programs > Oracle > Application Development > SQL Plus from the Start menu on the database server. 16. Log in to the Oracle database as any user by typing in the User Name, Password, and Host String. The master script disconnects and reconnects as the Sys user automatically, so you can log in as any valid database user. 17. Enter the following information as you are prompted. After each entry, press the Enter key. v The installation script oracle_install_ev_schema.sql; this is done by typing symbol followed by the path\filename. The script is located in the unzipped scripts folder at \oracle\install. If any part of the path contains a space, you must enclose the entire path in double quotation marks. If you mistype anything at any point in time, press Ctrl+C to break out of the script. v Sys users password v Database Host String - The Host String name should not exceed 8 characters. v The path to the folder in which you would like to store the log files generated by Oracle. v Important: When you type the path, place a: Backward slash (\) at the end of the path for a Windows operating system Forward slash (/) at the end of the path for a Unix operating system v The path to the folder in which you would like to store the new database files that are created with this installation; be certain that you have at least 100MB of free space at this location. Follow the same path rules as with the log file. 18. The scripts are now run and the LMS schema is created. After the scripts have finished running, you see the following screen. To exit SQL*Plus, type Exit at the SQLprompt and press Enter. Installation is completed. 19. Check for errors in the database log files. OracleX_install_ev_schema.sql creates several log files (one for each subscript that is run) in the directory that is specified earlier. The name of each file is the same as the subscript name with the extension.log. After execution of oraclex_install_ev_schema.sql, search each log file for the prefix ora- - this is how oracle prefaces all its error messages, for example, ora If there are no errors, continue with Step Return to the Configuration Wizard and select Automatic Configuration on the Command tab to continue the site setup. 21. Site setup is complete when you see the message Autoconfig DONE. However, commands continue to run in the command window. Allow the command window to close on its own before you close the Config Wizard. Chapter 4. Installing LMS on Windows 2008 Server 13

22 If you installed with any incorrect settings in the Config Wizard and there are site issues, you change the settings, select File > Save to save the changes, and run Automatic Configuration again. You can also select the Advanced check box and run any of the individual tasks displayed. See Chapter 9, Start Services, on page 41 for information on starting services that are required. 14 IBM Kenexa LMS Version 4.2.4: Installation Guide October 2015

23 Chapter 5. Upgrading to LMS from Versions Prior to 2009 The following topics describe how to upgrade to LMS from Versions before Setting Up the Installation Site The following steps help you to upgrade your existing LMS site to version from any version before 2009 Procedure 1. Important: Before you upgrade, stop all services for your existing site. 2. Back up your existing LMS site directory and database. 3. Select the provided link to launch the LMS installer, and run the installer. 4. Select Next to begin the installation. The Setup Wizard opens. 5. On the Choose Install Location screen, Enter a new location in which to install the LMS files. If the directory does not yet exist, the installer creates it for you. This can be any name - in 4.2.4, your site directory, site, and database can be named differently. Your new services will be named after the site directory. Select Install. 6. Select OK at the prompt. The files are install. This process takes several minutes. 7. When the site upgrade is complete, select OK at the prompt. The Config Wizard launches. During this next portion of the installation, the database is upgraded (for SQL Server) and the site is configured. Application server and host settings are configured on the Web tab. Provide the following information: v Application Name: This is the portion of the site URL that will after the hostname, for example, This name does not have to match the name of the database or application directory. v Web Protocol: In most cases, http is the appropriate selection. However, if your server is configured for SSL, you can select https. If you select https, you must do one of the following: v Select the SSL via the Tomcat radio button if you are securing the connection that uses Tomcat. Enter the name of the keystore file in the Keystore File field, and enter the key store password in the Keystore Pass field. v Select the SSL via the intermediary radio button if you are securing the connection through an intermediary server. v IP Address (optional): If your application server supports multiple IP addresses, you can specify an IP address to use for this Evolution instance. This is used for the address attribute of the Tomcat server.xml file. v External and Internal Port Number: This is the port used by the browser to reach the application and the port on which the application listens. These typically are the same number, unless there is a device or service between the browser and Tomcat such as an SSl accelerator. There must be no other applications using this port. v External Host Name: This is the server name in the site URL, for example, If you enter a fully qualified domain name in the Domain field, then that is reflected in the site URL, for example, You can also substitute the server IP address in place of the server name. v Shutdown Port Number: If the IP Address field is empty, this defaults to 1 + internal port number. If IP Address field has a value, this defaults to 11 + the last IP octet. The port number will be verified to be unique for the server. Copyright IBM Corp

24 v JVM Type: This is the type of Java Virtual Machine being used. Select either 32-bit or 64-bit, depending on the type of hardware your operating system is using. For Oracle DB's, you must have the matching client (32 bit client if you use the 32 bit jvm; 64 bit client for 64 bit jvm). 8. Select the Database tab to configure the database settings. 9. For SQL, select the MS Sql Server radio button and enter the following information: v Admin User: This defaults to sa. v Admin Password: Enter the SA password. v User: This is the client account name. v Password: This is the client user password. Change to shark. v Host Address: This is the name of the database server. v Host Port - This is the IP port number of the database service - the default port is To use named pipes instead of TCP/IP, set the port to zero. v Database Name: This is the name of your existing LMS database. Do not change this. v Minimum and Maximum Connections: This is the smallest and largest number of database connections that are opened at application startup. The maximum should be at least 10% larger than the Maximum Connections allowed on the Database tab. 10. For Oracle, select the Oracle radio button and enter the following information: v Admin User: This defaults to dbo. v Admin Password: This is the dbo password. v User: This is the client account name. v Password: This is the client user password. The default is K0wl3dg3N. If you already have a portalclient user, change the password. The default for previous versions of Evolution is shark. v Database Name: This is the name of your LMS database. This name does not have to match the Application Name or installation directory name. v Minimum and Maximum Connections: This is the smallest and largest number of database connections that are opened at application startup. The maximum should be at least 10% larger than the Maximum Connections allowed on the Database tab. v Oracle Home: This location contains the bin and JDBC directories. The wizard should auto-detect the directories for you. 11. Select the Services tab. Configure the following information: v Select the services that you want to install. You can specify the beginning of the name for each service in the Naming prefix field. Also, if you want your services to run on a different local admin account, select the Change services account check box and complete the account information. The user name should either include the domain, for example, domain\username, or if running on the built-in domain, should be entered in the format.\username. Note: You can also change the account information on the Login tab of the Task Service. v Minimum and Maximum Threads: This is the smallest and largest number of Tomcat threads to allocate at startup. The maximum should be at least 10% smaller than the Maximum Connections allowed on the Database tab. v Minimum and Maximum Memory Megabytes: This is the smallest and largest amount of memory to allocation for the startup of the application. The default values are typically acceptable. 12. Select the Integration tab. This tab helps to combine the LMS and Participate into an IBM Kenexa LMS integration. v KLS Secret Key - Allows Participate and LMS to communicate behind-the-scenes. The default value can be changed, and should be changed when there are multiple LMS installations. v Participate URL - The full URL for the Participate instance, i.e., servername.domain.com:port/pe. This is required regardless of whether a Participate instance is being used. 16 IBM Kenexa LMS Version 4.2.4: Installation Guide October 2015

25 v Encryption Key - The key is used to encrypt and decrypt the token string that is shared between LMS and Participate 13. When all of your settings are correct, select the Commands tab and select Automatic Configuration. If you are using SQL Server, proceed to Step For Oracle, the auto-configuration stops when the Oracle scripts are unpacked, and the scripts display in their storage directory. Leave the Configuration Wizard open, as you will need it later. Start SQL*Plus by selecting Programs > Oracle > Application Development > SQL Plus from the Start menu on the database server. 15. Log in to the Oracle database as DBO. 16. You must now run the upgrade scripts in order. For each script, you must do Step 17. The scripts are: v <site dir>\appdbf\db_scripts\oracle\upgrade\ora_50_upgrade.sql v <site dir>\appdbf\db_scripts\oracle\upgrade\minor_upgrades\6_0_1\up_6_0_1.sql v <site dir>\appdbf\db_scripts\oracle\upgrade\minor_upgrades\6_0_2\up_6_0_2.sql v <site dir>\appdbf\db_scripts\oracle\upgrade\minor_upgrades\6_0_3\up_6_0_3.sql v <site dir>\appdbf\db_scripts\oracle\upgrade\minor_upgrades\6_0_4\up_6_0_4.sql v <site dir>\appdbf\db_scripts\oracle\upgrade\minor_upgrades\6_0_5\up_6_0_5.sql v <site dir>\appdbf\db_scripts\oracle\upgrade\minor_upgrades\6_0_6\up_6_0_6.sql v <site dir>\appdbf\db_scripts\oracle\upgrade\minor_upgrades\7_0_0\up_7_0_0.sql v <site dir>\appdbf\db_scripts\oracle\upgrade\minor_upgrades\8_0_0\up_8_0_0.sql v <site dir>\appdbf\db_scripts\oracle\upgrade\minor_upgrades\8_0_1\up_8_0_1.sql v <site dir>\appdbf\db_scripts\oracle\upgrade\minor_upgrades\8_0_2\up_8_0_2.sql v <site dir>\appdbf\db_scripts\oracle\upgrade\minor_upgrades\8_0_3\up_8_0_3.sql v <site dir>\appdbf\db_scripts\oracle\upgrade\minor_upgrades\9_0_0\up_9_0_0.sql v <site dir>\appdbf\db_scripts\oracle\upgrade\minor_upgrades\9_0_1\up_9_1_0.sql v <site dir>\appdbf\db_scripts\oracle\upgrade\minor_upgrades\9_0_1\up_9_2_0.sql v <site dir>\appdbf\db_scripts_lms\oracle\upgrade\ora_50_upgrade.sql v <site dir>\appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\11_0_0\up_11_0_0.sql v <site dir>\appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\11_0_1\up_11_0_1.sql v <site dir>\appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_0_0.sql v <site dir>\appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_5_0.sql v <site dir>\appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_6_0.sql v <site dir>\appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_7_0.sql v <site dir>\appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_8_0.sql v <site dir>\appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_9_0.sql v <site dir>\appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_0_0.sql v <site dir>\appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_1_0.sql v <site dir>\appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_2_0.sql v <site dir>\appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_2_1.sql v <site dir>\appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_2_2.sql v <site dir>\appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_2_3.sql v dir>\appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_2_4.sql 17. Enter the following information as you are prompted. After each entry, press the Enter key. v The upgrade script; this is done by typing symbol followed by the path\filename to the upgrade file. For 6_0_1\up_6_0_1.sql Chapter 5. Upgrading to LMS from Versions Prior to

26 If any part of the path contains a space, you must enclose the entire path in double quotation marks. If you mistype anything at any point in time, press Ctrl+C to break out of the script. v Database Host String - The Host String name should not exceed 8 characters. v Sys users password v DBO users password 18. When the upgrade is complete, SQL*Plus closes automatically. Check for errors in the upgrade log file, which is located in the root of C: 19. Return to the Configuration Wizard and select Automatic Configuration on the Command tab to continue the site setup. 20. Site setup is complete when you see the message Autoconfig DONE. However, commands continue to run in the command window. Allow the command window to close on its own before you close the Config Wiz. If you upgraded with any incorrect settings in the Config Wizard and there are site issues, you change the settings, select File > Save to save the changes, and run Automatic Configuration again. You can also select the Advanced check box and run any of the individual tasks displayed. Important: You must copy the following directories from your old site and paste them into their appropriate four locations, as shown in the following table. Select Yes to All when prompted. Table 7. Directory Relocation. The following table shows where directories must be relocated. Copy Paste <site dir>\elm\css <site dir>\elm\images <site dir>\elm\upload <site dir>\appweb \elm <site dir>\appweb \elm <site dir>\appweb \elm 21. You must also copy <site dir>\elm\resources from your old site to <site dir>\appweb\elm on your new site. However, if changes were made to the default language file on your old site, do not overwrite this file with the new version. For this directory, only the files that do not exist in the new site directory should be copied from the old site. If changes were made to the default language file, those changes must be reapplied in the new language file. 22. If you upgraded from before 2006 R3 SP1 on MS SQL, then you must run the trimming_mssql.sql script that is provided in the installation directory at appdbf\db_scripts\mssql\upgrade. 23. If you upgraded from prior to LMS 2007 R4, you must migrate your LMS data. Open the command prompt, CD to <site dir>\sysscp, and run migratedata.bat. 24. Because new services are created with 4.2.4, your old services are no longer used. To delete these services, see Chapter 12, Removing Old LMS Services, on page 47. Important: See Chapter 9, Start Services, on page 41 for information on starting the required services. Upgrading to LMS The following steps help you to upgrade your existing LMS site to version from version 2009, 2011, or 12.X. Procedure 1. Important: Before you upgrade, stop all services for your existing site. 2. Back up your existing LMS site directory and database. 18 IBM Kenexa LMS Version 4.2.4: Installation Guide October 2015

27 3. Disable any patches and plug-ins that were installed. In the plugin folder of the installation directory, create a new subfolder named disabled and move your patches and plug-ins to that folder. Then, open the ConfigWiz, select the Advanced check box on the Commands tab, and select Add/Remove Plugins. 4. Select the provided link to start the LMS installer, and run the installer. 5. Select Next to begin the installation. The Setup Wizard opens. 6. On the Choose Install Location dialog box, browse for and select the existing 2009/2011 installation directory. 7. Select OK at the prompt. The files are installed. This process takes several minutes. 8. After the files are installed, select OK at the prompt; then, select OK at the next prompt to begin the site upgrade. Do not close the Command Prompt window. Note: During this portion of the upgrade, you are notified that Tomcat is being upgraded and that server.xml is going to be overwritten. If there are customizations to server.xml in the installation directory at \tomcat\conf, back up this file before you continue, and select OK. 9. When the site upgrade is complete, select OK at the prompt. The Config Wizard launches. During this next portion of the installation, the database is upgraded (for SQL Server) and the site is configured. Application server and host settings are configured on the Web tab. Provide the following information: v Application Name: The application name is the portion of the site URL that is created after the hostname. For example, The application name does not have to match the name of the database or application directory. v Web Protocol: In most cases, http is the appropriate selection. However, if your server is configured for SSL, you can select https. If you select https, you must do one of the following: v Select the SSL via tomcat radio button if you are securing the connection by using Tomcat. Provide the name of the keystore file in the Keystore File field, and enter the key store password in the Keystore Pass field. v Select the SSL via intermediary radio button if you are securing the connection through an intermediary server. v IP Address (optional): If your application server supports multiple IP addresses, you can specify an IP address to use for this Evolution instance. This is used for the address attribute of the Tomcat server.xml file. v External and Internal Port Number: This is the port that is used by the browser to reach the application and the port on which the application listens. These typically are the same number, unless there is a device or service between the browser and Tomcat such as an SSl accelerator. There must be no other applications that are using this port. v External Host Name: This is the server name in the site URL, for example, If you enter a fully qualified domain name in the Domain field, then that is reflected in the site URL, for example, You can also substitute the server IP address in place of the server name. v Shutdown Port Number: If the IP Address field is empty, this defaults to 1 + internal port number. If IP Address field has a value, this defaults to 11 + the last IP octet. The port number will be verified to be unique for the server. v JVM Type: This is the type of Java Virtual Machine being used. Select either 32-bit or 64-bit, depending on the type of hardware your operating system is using. For Oracle DB's, you must have the matching client (32-bit client if you use the 32-bit jvm; 64-bit client for 64-bit jvm). 10. Select the Database tab to configure the database settings. 11. For SQL, select the MS Sql Server radio button and enter the following information: v Admin User: Defaults to sa. v Admin Password: The SA password. v User: The client account name. Chapter 5. Upgrading to LMS from Versions Prior to

28 v Password: The client user password. v Host Address: The name of the database server. v Host Port - The IP port number of the database service - the default port is To use named pipes instead of TCP/IP, set the port to zero. v Database Name: The name of your existing LMS database. Do not change this name. v Minimum and Maximum Connections: The smallest and largest number of database connections that are opened at application startup. The maximum must be at least 10% larger than the Maximum Connections allowed on the Database tab. 12. For Oracle, select the Oracle radio button and enter the following information: v Admin User: Defaults to dbo. v Admin Password: The dbo password. v User: The client account name. v Password: The client user password. The default is K0wl3dg3N. If you already have a portalclient user, change the password. The default for previous versions of Evolution is shark. v Database Name: The name of your LMS database. This name does not have to match the Application Name or installation directory name. v Minimum and Maximum Connections: The smallest and largest number of database connections that are opened at application startup. The maximum must be at least 10% larger than the Maximum Connections allowed on the Database tab. v Oracle Home: This location contains the bin and JDBC directories. The wizard should auto-detect this location for you. 13. Select the Services tab. Configure the following information: v Select the services that are to be installed. You can specify the beginning of the name for each service in the Naming prefix field. Also, if you want your services to run on a different local admin account, select the Change services account check box and fill in the account information. The user name should either include the domain, for example, domain\username, or if running on the built-in domain, should be entered in the format.\username. Note: You can also change the account information on the Login tab of the Task Service. Note: v Minimum and Maximum Threads: This is the smallest and largest number of Tomcat threads to allocate at startup. The maximum should be at least 10% smaller than the Maximum Connections allowed on the Database tab. v Minimum and Maximum Memory Megabytes: This is the smallest and largest amount of memory to allocation for the startup of the application. The default values are typically acceptable. 14. Select the Integration tab. This tab helps to combine LMS and Participate into a Kenexa IBM LMS. v KLS Secret Key - Allows Participate and LMS to communicate behind-the-scenes. The default value can be changed, and should be changed when there are multiple IBM Kenexa LMS installations. v Participate URL - The full URL for the Participate instance, for example, servername.domain.com:port/pe. v Encryption Key - The key is used to encrypt and decrypt the token string that is shared between LMS and Participate. 15. When all of your settings are correct, select the Commands tab and select Automatic Configuration. If you are using SQL Server, proceed to Step For Oracle, the auto-configuration stops when the Oracle scripts are unpacked, and the scripts display in their storage directory. Leave the Configuration Wizard open, as you are going to need it later. Start SQL*Plus by selecting Programs > Oracle > Application Development > SQL Plus from the Start menu on the database server. 17. Log in to the Oracle database as DBO. 20 IBM Kenexa LMS Version 4.2.4: Installation Guide October 2015

29 18. You must now run the upgrade scripts. For each script, you must do Step 19. The scripts that you run depend on the version from which you are upgrading. Use the following table to determine the scripts you need to run. Table 8. Required Minor Oracle Scripts for Each Release.. The following table displays the required minor Oracle scripts for each release. Upgrading From Necessary Scripts 2009 appdbf\db_scripts\oracle\upgrade\minor_upgrades\6_0_1\up_6_0_1.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\6_0_2\up_6_0_2.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\6_0_3\up_6_0_3.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\6_0_4\up_6_0_4.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\6_0_5\up_6_0_5.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\6_0_6\up_6_0_6.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\7_0_0\up_7_0_0.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\8_0_0\up_8_0_0.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\8_0_1\up_8_0_1.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\8_0_2\up_8_0_2.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\8_0_3\up_8_0_3.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\9_0_0\up_9_0_0.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\9_0_1\up_9_1_0.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\9_0_1\up_9_2_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\11_0_0\up_11_0_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\11_0_1\up_11_0_1.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_0_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_5_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_6_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_7_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_8_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_9_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_0_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_1_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_2_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_2_1.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_2_2.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_2_3.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_2_4.sql Chapter 5. Upgrading to LMS from Versions Prior to

30 Table 8. Required Minor Oracle Scripts for Each Release. (continued). The following table displays the required minor Oracle scripts for each release. Upgrading From Necessary Scripts 2009 SP1 appdbf\db_scripts\oracle\upgrade\minor_upgrades\6_0_2\up_6_0_2.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\6_0_3\up_6_0_3.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\6_0_4\up_6_0_4.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\6_0_5\up_6_0_5.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\6_0_6\up_6_0_6.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\7_0_0\up_7_0_0.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\8_0_0\up_8_0_0.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\8_0_1\up_8_0_1.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\8_0_2\up_8_0_2.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\8_0_3\up_8_0_3.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\9_0_0\up_9_0_0.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\9_0_1\up_9_1_0.sql appdbf\db_scripts\oracle\upgrade\minor_upgrades\9_0_1\up_9_2_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\11_0_0\up_11_0_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\11_0_1\up_11_0_1.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_0_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_5_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_6_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_7_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_8_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\12_0_0\up_12_9_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_0_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_1_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_2_0.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_2_1.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_2_2.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_2_3.sql appdbf\db_scripts_lms\oracle\upgrade\minor_upgrades\13_0_0\up_13_2_4.sql 22 IBM Kenexa LMS Version 4.2.4: Installation Guide October 2015