############################################################################### # IBM Content Manager OnDemand for Multiplatforms # # Server for # # AIX, Linux, Linux on System z, and Windows # # README # # Release 10.1.0.0 # # Apr. 7, 2017 # # # # 5724-J33 (C) COPYRIGHT IBM CORPORATION 2017 # # All Rights Reserved # # Licensed Materials - Property of IBM # # US Government Users Restricted Rights - Use, duplication or # # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # ############################################################################### Welcome to the Installation Notes for IBM Content Manager OnDemand Server. For the latest information about IBM Content Manager OnDemand visit the product web site at: http://www.software.ibm.com/data/ondemand Contents ------------------------------------------------------------------------------- 1) Installation Notes 1.1) Upgrade Notes 1.2) Upgrade Steps 1.3) ARS_ORIGINAL_CODEPAGE 1.4) Update the System Log and System Load definitions to support the new date formats 1.5) Update the IBM Content Manager OnDemand System tables indexes 2) Server History 2.1) Server Notes 2.1.1) Enhancements 2.1.2) Platform Changes 2.1.3) Separately Priced Feature Enablement 2.2) AIX Server 2.2.10.1.0.0) Release (10.1.0.0) 2.3) Windows Server 2.3.10.1.0.0) Release (10.1.0.0) 2.4) Linux Server 2.4.10.1.0.0) Release (10.1.0.0) 2.5) Linux on System z Server 2.5.10.1.0.0) Release (10.1.0.0) 3) Web Enablement Kit History 3.1) Web Enablement Kit Notes 3.1.10.1.0.0) Release (10.1.0.0) 3.2) Contents of the Installation Package 3.3) AFP Web Viewer (ActiveX) 3.3.10.1.0.0) Release (10.1.0.0) 3.4) Java Line Data Applet 3.4.10.1.0.0) Release (10.1.0.0) 3.5) Java APIs 3.5.10.1.0.0) Release (10.1.0.0) 3.6) CFSOD Export Utility 3.6.10.1.0.0) Release (10.1.0.0) 5) IBM Global Security Kit Installation 5.1) AIX GSKit Install 5.2) Linux GSKit Install 5.3) Linux for System z GSKit Install 5.4) Windows GSKit Install 6) Testing Environment 6.1) IBM Content Manager OnDemand Currency Testing 6.2) IBM Content Manager OnDemand Testing Environment 7) Reference -----------------end of Contents----------------------------------------------- 1) Installation Notes 1.1) Upgrade Notes Before upgrading to IBM Content Manager OnDemand V10.1, you should backup your database and make sure you have a copy of the currently installed version of IBM Content Manager OnDemand. You should backup your configuration files too. The IBM Content Manager OnDemand for Multiplatforms V10.1 installation uses InstallAnywhere. The default install directory path names have changed for IBM Content Manager OnDemand for Multiplatforms Server. The default install path is now /opt/IBM/ondemand/V10.1 for AIX and /opt/ibm/ondemand/V10.1 for Linux and Linux on System z. The Windows install path is now C:\Program Files\IBM\OnDemand\V10.1. Customers can now install to the default path or specify an alternative one. If you choose to install in a different directory other than the default, you will have to add the new install lib64 path to the library search path using the environment variables LIBPATH for AIX or LD_LIBRARY_PATH for the other UNIX platforms. IBM Content Manager OnDemand for Multiplatforms Server requires the installation of the 64bit IBM Global Security Kit Version 8. Please see the section below for each platform for more information about how to install this component. Any ACIF exits that use ICU will need to be recompiled with version 58.2. The exits will also need to properly locate the ICU Dat file in the IBM Content Manager OnDemand server installation directory. For more information please read the WBTS Technote, 1686051 "Upgrade Guide for IBM Content Manager OnDemand Server V10.1.0" available by going to http://support.ibm.com and searching on the Technote number. 1.2) Upgrade Steps These steps are only required if you are upgrading from a previous version of IBM Content Manager OnDemand for Multiplatforms Server. Before upgrading to IBM Content Manager OnDemand V10.1, you should backup your database, configuration files, and make sure you have a copy of the currently installed version of IBM Content Manager OnDemand. Upgrade your Content Manager OnDemand instance. By default, V10.1 will be installed to a different directory than V9.5 or V9.0. On Unix: Restore your Content Manager OnDemand server configuration files (ars.ini, ars.cfg, ars.cache, ars.dbfs, arsload.cfg) and re-compiled custom user exits to your Content Manager OnDemand V10.1 directories. On Windows: Run the V10.1 OnDemand Configurator to upgrade the instance. To upgrade the IBM Content Manager OnDemand Database for use with IBM Content Manager OnDemand V10.1, log in as the IBM Content Manager OnDemand instance owner and run the following commands after installing V10.1 and any fix packs. This is mandatory. Stop the IBM Content Manager OnDemand server arssockd [-I ] -T Install the base IBM Content Manager OnDemand V10.1.0.0 See the section on your specific platform Apply the current fix pack See the section on your specific platform For SQL Server: Drop the current indexes arsdb [-I ] -efv Update the database arsdb [-I ] -uv For SQL Server: Create the current indexes arsdb [-I ]-rfv Then perform database maintenance arsdb [-I ] -mv for Oracle arsdb [-I ] -sv Start the IBM Content Manager OnDemand Server arssockd [-I ] -S where OD_INSTANCE is the IBM Content Manager OnDemand instance name. If this is not specified, the default is ARCHIVE. 1.3) ARS_ORIGINAL_CODEPAGE - Configuration changes needed for localized database codepage support - A new ARS.CFG parameter, ARS_ORIGINAL_CODEPAGE, is now required. When upgrading IBM Content Manager OnDemand for MP V10.1 from a pre-V8.5 IBM Content Manager OnDemand for MP instance, this MUST be set to the codepage the pre-V8.5 IBM Content Manager OnDemand server was running in. Failure to set it will prevent the IBM Content Manager OnDemand server from starting. SETTING IT INCORRECTLY WILL RESULT IN DATA CORRUPTION. Example failure to start message which will be sent to the console: DB Error: STARTUP -- SQLSTATE=1. ARS_ORIGINAL_CODEPAGE is not defined in ars.cfg. Run arsdb -u -I to determine setting of ARS_ORIGINAL_CODEPAGE, SQLCODE=0, File=arssrvr.c, Line=7892 - Steps to set the value of ARS_ORIGINAL_CODEPAGE - UNIX Servers Run arsdb -u without ARS_ORIGINAL_CODEPAGE in the ARS.CFG for information on the proper setting for ARS_ORIGINAL_CODEPAGE. An example of running the arsdb -u -I command without ARS_ORIGINAL_CODEPAGE in the ARS.CFG is: arsdb: Unable to initialize environment. The return code is -1. If this is a new (created in 8.5 or later) instance, then define ARS_ORIGINAL_CODEPAGE=1208 in ars.cfg. Otherwise, if this is an existing instance (created prior to 8.5), then define ARS_ORIGINAL_CODEPAGE=923 in ars.cfg. Once set, ARS_ORIGINAL_CODEPAGE must never change. Edit the ARS.CFG file and add the ARS_ORIGINAL_CODEPAGE parameter set to the appropriate value determined by the arsdb command. - Windows Server Run arsdb.exe -u -I for information on the proper setting for ARS_ORIGINAL_CODEPAGE. An example of running the arsdb.exe -I -u command, where OD_INSTANCE is the IBM Content Manager OnDemand instance name, without ARS_ORIGINAL_CODEPAGE set is: arsdb: Unable to initialize environment. The return code is -1. If this is a new (created in 8.5 or later) instance, then define ARS_ORIGINAL_CODEPAGE with a value of 1208 in the registry. Otherwise, if this is an existing instance (created prior to 8.5), then define ARS_ORIGINAL_CODEPAGE with a value of 5348 in the registry. The registry setting should be placed in the following section HKEY_LOCAL_MACHINE\SOFTWARE\ IBM\OnDemand for Windows\@SRV@_)\CFG. Once set, ARS_ORIGINAL_CODEPAGE must never change. IMPORTANT: This README contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, read the following article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry (http://support.microsoft.com/kb/256986/EN-US/ ) Use the regedit.exe command to update the Windows Registry Key specified in the output of the arsdb command and add the ARS_ORIGINAL_CODEPAGE string value set to the appropriate value determined by the arsdb command. 1.4) Update the System Log and System Load definitions to support the new date formats. - This is optional. The old date formats are still supported. If you have not already updated the System Log and System Load to take advantage of the new date support, you can run the following commands. To update the System Log Application Group and Folder arssyscr [-I ] -l -u To update the System Load Application Group and Folder arssyscr [-I ] -a -u To display the new date, date/time formats, you must use one of the V9 or later clients. This includes, but is not limited to, the Windows Client, ODWEK Java APIs, CICS, etc. Once this is done, older V8.5 Clients will not be able to display the newer date format. For more information please read the WBTS Technote 7036188 - "Content Manager OnDemand V9.0 new date types for Date, Date/Time and Date/Time(TZ)" available by going to http://support.ibm.com and searching on the Technote number. 1.5) Update the IBM Content Manager OnDemand System tables indexes - Customers should run the arsdb commands to drop and recreate the indexes if updating from older versions. Drop the indexes: arsdb [-I ] -efv Create the indexes: arsdb [-I ] -rfv Then you will need to update the statistics on all the IBM Content Manager OnDemand System tables arsdb [-I ] -mv Or, for Oracle arsdb [-I ] -sv -------------end of Installation Notes----------------------------------------- 2) Server History 2.1) Notes 2.1.1) Enhancements For information about the new enhancements to IBM Content Manager for Multiplatforms V10.1. please read the WBTS Technote 7021523 - "What's new in Content Manager OnDemand" available by going to http://support.ibm.com and searching on the Technote number. 2.1.2) Platform changes 2.1.2.1) The HPUX platform is no longer supported 2.1.2.2) The Oracle Solaris platform is no longer supported 2.1.3) Separately Priced Feature Enablement In order to use any IBM Content Manager OnDemand Separately Priced Feature, you must now install the appropriate feature. The install images for Enhanced Retention Management, PDF Indexer, OnDemand Distribution Facility, and Full Text Search are available through Passport Advantage. -------------end of Notes------------------------------------------------------ 2.2) AIX Server 2.2.10.1.0.0) Release (10.1.0.0) - Pre-reqs - AIX 7.1 TL4 or later - IBM XL C/C++ Runtime for AIX, V13.1.3.1 or later - Database - DB2 V10.5 or later - Oracle 12c Release 1 or later - IBM Spectrum Protect(TSM) V7.1.4 or later - IBM Global Security Kit Version 8 - Included in the installation packaging - Installation - Unix installs are packaged with InstallAnywhere. The native installs using SMIT, swinstall, pkgadd, or RPM are no longer supported - Pre-reqs - 700MB of free space in /tmp and 1.2GB in /opt. - To install from the command line - odaix.bin -i console - To uninstall from the command line - /opt/IBM/ondemand/V10.1/_uninst1010/uninstallod -i console - Please read the Installation Documentation online at: http://www.ibm.com/support/knowledgecenter/SSEPCD_10.1.0 for further information - Installing the IBM Global Security Kit Version 8 - See section 5) IBM Global Security Kit Installation -------------end of AIX Server------------------------------------------------- 2.3) Windows Server 2.3.10.1.0.0) Release (10.1.0.0) - Pre-reqs - Windows Server 2012 R2 64bit or later - Database - DB2 V10.5 or later - Oracle 12c Release 1 or later - Microsoft SQL Server 2014 or later - Microsoft .NET Framework 4.6.1 or later - IBM Spectrum Protect(TSM) V7.1.4 or later - IBM Global Security Kit Version 8 - Included in the installation packaging - Installation - Pre-reqs - 2GB of free space on C:\ - To install from the command line - odwin.exe - To uninstall use Programs and Features from the Control Panel - Please read the Installation Documentation online at: http://www.ibm.com/support/knowledgecenter/SSEPCD_10.1.0 for further information - Installing the IBM Global Security Kit Version 8 The GSKit Crypt and SSL components are installed automatically. -------------end of Windows Server--------------------------------------------- 2.4) Linux 2.4.10.1.0.0) Release (10.1.0.0) - Pre-reqs - Red Hat Enterprise Linux Server release 7.2 for x86_64 or later - glibc.i686, libgcc.i686, and libstdc++.i686 for 32bit support. - SuSE Linux Enterprise Server (SLES) 12 SP1 for AMD64/Intel64 or later - Database - DB2 V10.5 or later - Oracle 12c Release 1 or later - IBM Spectrum Protect(TSM) V7.1.4 or later - IBM Global Security Kit Version 8 - Included in the installation packaging - Installation - Unix installs are packaged with InstallAnywhere. The native installs using SMIT, swinstall, pkgadd, or RPM are no longer supported - Pre-reqs - 620MB of free space in /tmp and 1.1GB in /opt - To install from the command line - odlinux.bin -i console - To uninstall from the command line - /opt/ibm/ondemand/V10.1/_uninst1010/uninstallod -i console - Please read the Installation Documentation online at: http://www.ibm.com/support/knowledgecenter/SSEPCD_10.1.0 for further information - Installing the IBM Global Security Kit Version 8 - See section 5) IBM Global Security Kit Installation -------------end of Linux Server----------------------------------------------- 2.5) Linux on System z Server 2.5.10.1.0.0) Release (10.1.0.0) - Pre-reqs - Red Hat Enterpise Linux(RHEL) 7.2 for IBM System z or later - SUSE Linux Enterprise Server(SLES) for System z 12 SP1 or later - Database - DB2 V10.1 or later - IBM Spectrum Protect(TSM) V7.1.4 or later - IBM Global Security Kit Version 8 - Included in the installation packaging - Installation - Unix installs are packaged with InstallAnywhere. The native installs using SMIT, swinstall, pkgadd, or RPM are no longer supported - Pre-reqs - 620MB of free space in /tmp and 1.1GB in /opt - To install from the command line - odlinux390.bin -i console - To uninstall from the command line - /opt/ibm/ondemand/V10.1/_uninst900/uninstallod -i console - Please read the Installation Documentation online at: http://www.ibm.com/support/knowledgecenter/SSEPCD_10.1.0 for further information - Installing the IBM Global Security Kit Version 8 - See section 5) IBM Global Security Kit Installation -------------end of Linux on System z Server----------------------------------- -----------------end of Server History----------------------------------------- 3) Web Enablement Kit History 3.1) Web Enablement Kit Notes 3.1.10.1.0.0) Release (10.1.0.0) - The ODWEK executables, libraries, jars, applets, and plugins are now packaged with OnDemand Server installations. - The IBM Content Manager OnDemand Web Enablement Kit is now installed to a new default directory. It is installed to /opt/IBM/ondemand/V10.1/www for AIX. It is installed to /opt/ibm/ondemand/V10.1/www for Linux and Linux on System z. It is installed to C:\Program Files\IBM\OnDemand\V10.1\www for Windows. - Before using the latest version of the Web Enablement Kit, you must delete all of the files from the Web Enablement Kit temp directory. - The Java API shared libraries are both 32bit and 64bit on AIX, Linux, and Windows. The Java API shared library on Linux for System z is 64-bit only. - The ODWEK 32bit CGI and Servlet are no longer supported. - The Image Web Viewer(ActiveX) is no longer supported. - Pre-reqs - IBM Global Security Kit Version 8 - 64bit and 32bit - Included in the installation packaging -------------end of Web Enablement Kit Notes----------------------------------- 3.2) Contents of the Web Enablement Kit Package. locale/icudt58l.dat (Windows, Linux) locale/icudt58b.dat (AIX, Linux for System z) - This file should be left in the installation Locale directory. bin32/icudt58.dll (Windows 32bit) bin32/icuin58.dll (Windows 32bit) bin32/icuio58.dll (Windows 32bit) bin32/icuuc58.dll (Windows 32bit) - These libraries are used for 32bit ICU support on Windows. These files must be placed in the same directory as the JAVA API shared library or a directory that is in the command search path defined by the Path environment variable. bin/icudt58.dll (Windows 64bit) bin/icuin58.dll (Windows 64bit) bin/icuio58.dll (Windows 64bit) bin/icuuc58.dll (Windows 64bit) - These libraries are used for 64bit ICU support on Windows. These files must be placed in the same directory as the JAVA API shared library or a directory that is in the command search path defined by the Path environment variable. bin32/arsgsk32.dll (Windows 32bit) bin/arsgsk64.dll (Windows 64bit) -These libraries are used for GSKit SSL support on Windows. These files must be placed in the same directory as the JAVA API shared library or a directory that is in the command search path defined by the Path environment variable. ODApi.jar ars3wapi32.dll (Windows) ars3wapi64.dll (Windows) libars3wapi32.a (AIX) libars3wapi64.a (AIX) libars3wapi32.so (Linux) libars3wapi64.so (Linux, Linux for System z) - Java API and support files. See the documentation and api/ODApiDoc.zip for more information on using the APIs. api/ODApi.jar - This is the IBM Content Manager OnDemand Web Enablement Kit Java API jar file api/ODApiDoc.zip - This is the IBM Content Manager OnDemand Web Enablement Kit Java API Documentation locale/arscpcs.cfg - This file contains the code page to code set mappings. This file should stay in the installation directory. applets/ODLineDataViewer2.jar - IBM Content Manager OnDemand Line Data Viewer applet applets/IEFix.js - JavaScript file to assist applet launch plugins/afpplgin.exe - IBM Content Manager OnDemand AFP Web Viewer (ActiveX) - All languages including DBCS support - This is an InstallShield self extracting install file. This file should be downloaded to the user's Windows 7, Windows 8, or Window 10 system and run to install the OnDemand AFP Web Viewer. If the user is running a browser while the installation is in progress, then the user must stop and restart the browser before the Web Viewer can be used. plugins/afpplgin.zip - IBM Content Manager OnDemand AFP Web Viewer (ActiveX) - Zip format for all languages include DBCS support exporter/CFSODExporter.jar - Only for use with CFS-CMOD -------------end of Contents of the Web Enablement Kit Package----------------- 3.3) AFP Web Viewer (32bit ActiveX) 3.3.10.1.0.0) Release (10.1.0.0) - Pre-reqs - Windows 7 SP1 (32bit or 64bit) - Upgraded the AFP Web Viewer to Version 3.7.0.0 -------------end of AFP Plugin------------------------------------------------- 3.4) Java Line Data Applet 3.4.10.1.0.0) Release (10.1.0.0) - Pre-reqs - Java 1.7 or later -------------end of Java Line Data Applet-------------------------------------- 3.5) Java API 3.5.10.1.0.0) Release (10.1.0.0) - Pre-reqs - Java 1.7 or later - AIX 7.1 TL4 or later - Red Hat Enterprise Linux (RHEL) 7.2 or later - SUSE Linux Enterprise Server (SLES) 12.1 or later - Red Hat Enterprise Linux (RHEL) on System z RedHat 7.2 or later - SUSE Linux Enterprise Server (SLES) on IBM System z 12.1 or later - Windows Server 2012 R2 or later (64bit only) - If the IBM Content Manager OnDemand Web Enablement Kit is installed to a different path than the default, the path to the new installation directory must be specified in the ODConfig object. - Starting at version 10.1, regardless of the value specified for the TraceLevel, the Java APIs will create a arswww.trace file in the directory specified by TraceDir. The TraceLevel and TraceDir are specified in the ODConfig object. -------------end of Java API--------------------------------------------------- 3.6) CFSOD Export Utility 3.6.10.1.0.0) Release (10.1.0.0) - Pre-reqs - Java 1.7 or later - Database with JDBC Type 4 driver - DB2 V10.5 or later - Oracle 12c Release 1 or later - Microsoft SQL Server 2014 or later - IBM FileNet P8 Version 5.1+ or later -------------end of CFSOD Export Utility--------------------------------------- ----------------end of Web Enablement Kit History------------------------------ 4) IBM Global Security Kit Installation 4.1) AIX GSKit Install The GSKit install media must be accessible to the installation programs. Although the SMIT program can access the install media via a read-only device (such as a CD-ROM), the recommended method is to copy the GSKit media to the local file system first. A good place for this is /var/spool/pkg or alternatively /tmp/gsk8. The AIX packages are distributed in a compressed tar file. To gain access to the software packages that will be recognized by native install tools you first need to uncompress them. This can be achieved as follows: zcat gskcrypt64-8.0.50.75.aix.ppc.tar.Z | tar -xvf - zcat gskssl64-8.0.50.75.aix.ppc.tar.Z | tar -xvf - zcat gskcrypt32-8.0.50.75.aix.ppc.tar.Z | tar -xvf - zcat gskssl32-8.0.50.75.aix.ppc.tar.Z | tar -xvf - This will decompress the RTE install packages for AIX. The following installation instructions assume that you have decompressed the installation packages and are working with them directly. Installing with SMIT GUI tool Do the following: 1. From the command line, run inutoc in the directory containing the GSKit packages. This creates a table of contents needed by SMIT. /usr/sbin/inutoc /tmp/gsk8 2. Invoke the SMIT application by entering smit on the command line. 3. Choose "Software Installation & Maintenance". 4. Then choose "Install Software". 5. Select "Install and Update Software by Package Name". 6. On the device/directory window specify the directory that contains the installable software. 7. Select packages GSKit8.gskcrypt64.ppc.rte, GSKit8.gskssl64.ppc.rte, GSKit8.gskcrypt32.ppc.rte, and GSKit8.gskssl32.ppc.rte from the Multi-select List. 8. Select the file sets of the software package to install. 9. Mark the options appropriate to your installation requirements from the options window. Note: Set the "install all prereqs" options to "yes" 10. Confirm to complete the installation. Installing with installp command line tool To install GSKit 8 for PPC64 systems using the installp command the following chain of commands would need to be executed: 1. /usr/bin/inutoc /tmp/gsk8 2. installp -acgqw -d /tmp/gsk8 GSKit8.gskcrypt64.ppc.rte \ GSKit8.gskssl64.ppc.rte \ GSKit8.gskcrypt32.ppc.rte \ GSKit8.gskssl32.ppc.rte See the installp man page for more information about the command line switches. Removing Packages with SMIT GUI tool Do the following: 1. Invoke SMIT, by entering smit on the command line. 2. From the menu, choose the "Software Installation and Maintenance". 3. Then select "Software Maintenance and Utilities". 4. From the Maintenance window select "Remove Installed Software" to open the "Remove Software Product" dialogue window. 5. Enter the name of the installed GSKit SSL software package (e.g. GSKit8.gskssl64.ppc.rte). 6. Turn the flag for "REMOVE dependent software?" to "YES" to instruct the system to automatically remove the GSKit Crypt software package. 7. Confirm the procedure to complete the removal of the software package. Removing Packages with installp command line tool Use installp to remove all of the GSKit packages. To remove GSKit 8 for PPC64 with the installp command: installp -u -g -V2 GSKit8.gskssl64.ppc.rte \ GSKit8.gskcrypt64.ppc.rte \ GSKit8.gskssl632.ppc.rte \ GSKit8.gskcrypt32.ppc.rte -------------end of AIX GSKit Install------------------------------------------ 4.2) Linux GSKit Install The installation must be performed as the user root. The -nodeps flag should not be used unless specifically called out in the instructions below. Installing with RPM command line tool Do the following: 1. Use the rpm command to perform the installation as follows: To install in the default location: /usr/local rpm -Uv gskcrypt64-8.0.50.75.linux.x86_64.rpm rpm -Uv gskssl64-8.0.50.75.linux.x86_64.rpm rpm -Uv gskcrypt32-8.0.50.75.linux.x86_64.rpm rpm -Uv gskssl32-8.0.50.75.linux.x86_64.rpm Removal using the Command Line Interface Note that the rpm command run with the -qa option will provide a list of installed packages. This may be used to determine the exact names of the currently installed GSKit packages. For example, rpm -qa | grep gsk Do the following: 1. Run the rpm command to remove the GSKit SSL package followed by the GSKit Crypt package. rpm -ev gskssl64-8.0.50.75 gskcrypt64-8.0.50.75 \ gskssl32-8.0.50.75 gskcrypt32-8.0.50.75 -------------end of Linux GSKit Install---------------------------------------- 4.3) Linux for System z GSKit Install The installation must be performed as the user root. The -nodeps flag should not be used unless specifically called out in the instructions below. Installing with RPM command line tool Do the following: 1. Use the rpm command to perform the installation as follows: To install in the default location: /usr/local rpm -Uv gskcrypt64-8.0.50.75.linux.s390x.rpm rpm -Uv gskssl64-8.0.50.75.linux.s390x.rpm rpm -Uv gskcrypt31-8.0.50.75.linux.s390.rpm rpm -Uv gskssl31-8.0.50.75.linux.s390.rpm Removal using the Command Line Interface Note that the rpm command run with the -qa option will provide a list of installed packages. This may be used to determine the exact names of the currently installed GSKit packages. For example, rpm -qa | grep gsk Do the following: 1. Run the rpm command to remove the GSKit SSL package followed by the GSKit Crypt package. rpm -ev gskssl64-8.0.50.75 gskcrypt64-8.0.50.75 \ gskssl31-8.0.50.75 gskcrypt31-8.0.50.75 -------------end of Linux for System z GSKit Install--------------------------- 4.4) Windows GSKit Install The GSKit Crypt and SSL components are installed automatically. -------------end of Windows GSKit Install-------------------------------------- -----------------end of IBM Global Security Kit Installation------------------- 5) IBM Content Manager OnDemand Testing 5.1) Concurrency Testing IBM Content Manager OnDemand has been currency tested with: AIX 7.1 TL4 Windows Server 2012 R2 DB2 V10.5 SQL Server 2014 Oracle 12c Release 1 IBM Spectrum Protect(TSM) 7.1.4 KVM Hypervisor DB2 pureScale AdoptOpenJDK 8 IBM Content Manager OnDemand Web Enablement Kit has been currency tested with: 5.2) Testing Environments IBM Content Manager OnDemand for Multiplatforms is tested in 15 configurations on 7 different platforms. The following is a list of the environments in which IBM tested the latest fix pack. AIX: AIX - 7.1 TL4 DB2 - 10.5 Oracle - 12c R1 IBM Spectrum Protect(TSM) - 7.13 Windows: Windows - Server 2012 R2 64bit DB2 - 10.5 Oracle - 12c R1 SQL Server - 2014 IBM Spectrum Protect(TSM) - 7.1.4 Linux on x86_64: RedHat - RHEL release 7.2 SuSE - SLES 12.1 DB2 - 10.5 Oracle - 12c R1 IBM Spectrum Protect(TSM) - 7.1.4 Linux on System z: RedHat - RHEL release 7.2 SuSE - SLES 12.1 DB2 - 10.5 IBM Spectrum Protect(TSM) - 7.1.4 -----------------end of IBM Content Manager OnDemand Testing------------------- 6) Reference ------------------------------------------------------------------------------- You can find information updates by searching the Web Based Technical Support web site at: http://www.ibm.com/software/data/ondemand/mp/support.html You can find the following additional documents by entering the document # or title in the search field: Document# Document title 1686051 Upgrade Guide for IBM Content Manager OnDemand Server V10.1.0 7021523 What's new in Content Manager OnDemand -----------------end of Reference----------------------------------------------