IBM Content Manager for z/os V8.5 Fix Pack 2 Resource manager running under IBM HTTP Server powered by Apache V8.5.5 Readme

Transcription

1 IBM Content Manager for z/os V8.5 Fix Pack 2 Resource manager running under IBM HTTP Server powered by Apache V8.5.5 Readme November 2014

2 Table of Contents 1 About this README file Introduction Prerequisites IBM Content Manager for z/os V8.5 Fix Pack 2 resource manager SMP/E install Modifying the ICMRDDEF job Allocating?ICM?.AICMHFS Performing SMP/E APPLY resource manager for z/os V8.5 Fix Pack New Members Installation and Configuration Modify the 31-bit IHS Apache instance started task procedure: Change IHS Apache Proc Verify the LSDBLOCATOR field LIBPATH for the TSM Client API To start or stop the IHS Apache server New messages Changes to the IHS Server V IPv6 Support Best practice tips External Documentation...10

3 1 About this README file This readme file provides information on the IBM Content Manager for z/os V8.5 Fix Pack 2 resource manager running IBM HTTP Server powered by Apache V8.5.5 (IHS Apache). This document contains information on installation, configuration, new messages, and some best practice tips. 2 Introduction This readme is the first document you should read after you successfully install the IBM Content Manager resource manager and before you start to configure your environment. In IBM Content Manager for z/os V8.5 Fix Pack 2, the resource manager can be run on IBM HTTP Server powered by Apache V8.5.5 (IHS Apache) as an alternative to running it on IBM HTTP Server V5.3 (IHS Domino ). The section Modifying the ICMRDDEF job shows the changes in ICMRDDEF to support both IHS servers. 2.1 Prerequisites Refer to the system requirements for Content Manager for z/os that are listed in the IBM Content Manager for z/os V8.5 Fix Pack 2 release notes. This support also has two additional prerequisites. 31-bit instance of the IBM HTTP Server powered by Apache V8.5.5 NOTE: 64-bit instances are not supported. Use the UNIX shell command "apachectl -V" for the instance and look for the architecture output, which will state that it is either 32-bit or 31-bit. Versions later than V8.5.5 might be compatible. See Apache's "Module Magic Number (MMN)" ( or IBM Content Manager for z/os resource manager V8.5 Fix Pack 2 3 IBM Content Manager for z/os V8.5 Fix Pack 2 resource manager SMP/E install 3.1 Modifying the ICMRDDEF job If you plan on using a new SMP/E environment for IBM Content Manager for z/os resource manager V8.5 Fix Pack 2, you should use the attached ICMRDDEF member for the installation. If you plan on installing to an existing SMP/E environment, update your ICMRDDEF job by adding/editing the changes below, and following the instructions in the SPECIAL CUSTOMIZATION INSTRUCTIONS section found in the prologue of the attached ICMRDDEF job. 1) Job step: SMPT, add the following statements to the UCLIN. ADD DDDEF(SCEEBND2) SHR WAIT UNIT(SYSALLDA) DA(?CEE?.SCEEBND2). /* LE/370 LIB */

4 ADD DDDEF(SCEELIB) SHR WAIT UNIT(SYSALLDA) DA(?CEE?.SCEELIB). /* LE/370 LIB */ ADD DDDEF(AICMHFS2) SHR WAIT UNIT(SYSALLDA) VOLUME(?VV?) DA(?ICM?.AICMHFS2). /* RMTSMARG DLIB */ ADD DDDEF (SIMWSV8) PATH('/usr/lpp/IHSA/V8R5/.31bit/lib/'). /* apache hfs */ NOTE: A) DA(?IMW?.SIMWSDCK) was changed to DA(?DGW?.SIMWSDCK). It should not impact your environment B) If you ran ICMTDDEF, AICMHFS2 was already defined. 2) Job step: SMPD, add the following statements to the UCLIN. ADD DDDEF(AICMHFS2) SHR WAIT UNIT(SYSALLDA) VOLUME(?VV?) DA(?ICM?.AICMHFS2). /* RMHFS DLIB */ NOTE: A) If you ran ICMTDDEF, AICMHFS2 was already defined. 3) Job step: DEFPATH, add the following statements to the UCLIN. ENDZONEEDIT. ZONEEDIT DDDEF. CHANGE PATH('/usr/lpp/IHSA/V8R5/.31bit/lib'*, '?ppa?/usr/lpp/ihsa/v8r5/.31bit/lib'*). ENDZONEEDIT. 3.2 Allocating?ICM?.AICMHFS2 If you are upgrading from a resource manager with the TSM option, this data set is already allocated. Otherwise, you must allocate the data set as follows: //AICMHFS2 DD DSN=?ICM?.AICMHFS2, // DISP=(NEW,CATLG), // RECFM=VB, // LRECL=256, // BLKSIZE=0, // SPACE=(6475,(10,1,5)), // UNIT=SYSALLDA,VOL=SER=?VV?

5 3.3 Performing SMP/E APPLY resource manager for z/os V8.5 Fix Pack 2 There are no special instructions for the SMP/E APPLY step. Follow the same process to receive the fix pack, update the ICMRDDEF, and apply the fix pack. The APPLY job should complete with a return code of 0. The following members that are related to the SMP/E jobs in the?icm?.aicmins2 library are updated by the APPLY job. ICMRALLO ICMTALLO ICMRDDEF ICMTDDEF 3.4 New Members New members are introduced by Fix Pack 2 to support IHS Apache. The locations and member names are listed as follows: 1. Four new members are in the?ppr?/usr/lpp/icm/v8r5m0/bin directory icmmasct.so - for storing to OAM icmmatct.so - for storing to TSM and OAM ICMMVACT - for sticky-bit placeholder for storing to OAM in?icm?.sicmlod2 SOXPL (an alias-of ICMMVACT) 2. Two new members are in the?icm?.sicmlod2 ICMMVACT - RM module for storing to OAM SOXPL (an alias-of ICMMVACT) 3. Two new members are in the?ppr?/usr/lpp/icm/v8r5m0/sample directory ICMDSECR and ICMDSAPX - IHS Apache stubs for linkedit 4. One new member is in the?icm?.sicmobj2 ICMHTAPX - IHS Domino stub for linkedit

6 4 Installation and Configuration You can upgrade the resource manager for IBM Content Manager for z/os using the program directory for SMP/E. For installation and configuration information, refer to /dcmiz004.htm. You must also run the upgrade jobs and programs and complete the configuration steps. To run the Fix Pack 2 resource manager running IBM HTTP Server powered by Apache V8.5.5 (IHS Apache), rebind resource manager with the new bind job that is provided. Then complete the following two steps: 4.1 Modify the 31-bit IHS Apache instance started task procedure: A sample started task procedure is shipped by IHS Apache in member SHAPJCL(HAPAPROC). For more details about it see IHS Apache documentation: rtsysconz.html You can make a copy of it (usually into SYS1.PROCLIB) to add these items: a) Add these keywords to the PARM: MEMLIMIT=2G,REGION=0M,TIME=NOLIMIT For example: // PARM='SH?DIR?/bin/apachectl -k &ACTION -f &CONF -DNO_DETACH', // MEMLIMIT=2G,REGION=0M,TIME=NOLIMIT b) Add -D FOREGROUND to ensure the IBM Content Manager for z/os resource manager trace log is properly captured: For example: // CONF='?DIR?/conf/httpd.conf -D FOREGROUND ' c) Change STDOUT/STDERR to SYSOUT * instead of HFS file e.g.: //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* d) If the DB2 SDSNLOAD data set is not included in the LINKLIST, add it to the STEPLIB. For example: //STEPLIB DD DISP=SHR,DSN=?RMDSN?.SDSNLOAD (where?rmdsn? is the HLQ for your DB2 subsystem) It will resolve the following message: CSV003I REQUESTED MODULE DSNACAB NOT FOUND 4.2 Change IHS Apache Proc In the IHS Apache started task procedure above, look for the CONF keyword (e.g. CONF='? DIR?/conf/httpd.conf'), which provides the file name of the IHS Apache httpd.conf file for that instance. Edit the httpd.conf file, adding the following text (at the end), replacing the values with your IBM Content Manager for z/os resource manager values. The locations and new member names for IHS Apache are listed in section 3.3 New members of this document. LoadModule icm_rm_module?ppr?/usr/lpp/icm/v8r5m0/bin/icmmasct.so <IfModule icm_rm_module> <Location /ICMResourceManager> CharsetOptions NoTranslateRequestBodies SetHandler ICMResourceManager ICMResourceManager?RMDB2SYS??ICMMOPLN? </Location> </IfModule>

7 The tokens?rmdb2sys? and?icmmopln? which are parameters to the ICMResourceManager directive must be replaced by the values used in the resource manager bind job (in?icm?.sicmins2). To store objects into TSM as well as OAM, use the following LoadModule directive instead of the one above for the TSM option: LoadModule icm_rm_module?ppr?/usr/lpp/icm/v8r5m0/bin/icmmatct.so IHS Apache can load the resource manager module from a PDS library using the same implementation as for IHS Domino. To use the ICMVACT in the?icm?.sicmlod2 instead of using the load module in the HFS, change icmmasct.so to ICMMVACT. LoadModule icm_rm_module?ppr?/usr/lpp/icm/v8r5m0/bin/icmmvact - ICMMVACT in the HFS should have been set as program controlled and with the sticky bit by the installation program. If not, you can use the following shell commands: - 'chmod +t ICMMVACT' to set the sticky bit, - 'extattr +p ICMMVACT' to set the program controlled bit. - The actual module ICMMVACT can be available to the started task either in the IHS Apache STEPLIB concatenation, or LNKLST, or in dynamic LPA. 4.3 Verify the LSDBLOCATOR field Ensure the LSDBLOCATOR field in the ICMRMCONTROL table has the DB2 location name: SELECT LSDBLOCATOR FROM?RMCREATOR?.ICMRMCONTROL WHERE RM390ID = 1; If the query above does not show the name of the DB2 location where the LS resides, please update it. This will prevent an SQL -950 error. 4.4 LIBPATH for the TSM Client API For TSM support: Make sure that the path to find the TSM Client API library file libapids.a at runtime is included in the LIBPATH. One way to do this is to modify the bin/envvars file in the IHS Apache instance directory to add the path to libapids.a to the LIBPATH. For example, if your IHS Apache instance is located in /websrv2, and your TSM Client API install path is /usr/lpp/tivoli/tsm/client/api/bin, then you would edit the /websrv2/bin/envvars file, find the last change to LIBPATH: LIBPATH=/websrv2/modules:$LIBPATH and add your path to it: LIBPATH=/websrv2/modules:/usr/lpp/Tivoli/tsm/client/api/bin:$LIBPATH

8 5 To start or stop the IHS Apache server If the started task procedure you use is named "WEBSRV2", then you can use the following commands to start and stop the Apache instance (stop ends the task and the SYSOUT output stays in its print queue, while start begins a new task with fresh logs). S WEBSRV2,ACTION='start' S WEBSRV2,ACTION='stop' NOTE : Problems with the resource manager module (e.g. abends, permissions, etc) may prevent the stop command from completing. If this happens, comment out the resource manager directives added in the conf file, stop Apache, and then add them back into the conf file before starting Apache again. 'start' and 'stop' are in lower case in the command above. To make sure that 'start' and 'stop' are in lower case, do not issue these commands under SDSF as COMMAND INPUT. Instead, issue the commands under the System Command Extension by entering a forward slash '/' under SDSF COMMAND INPUT and then pressing ENTER. 6 New messages New messages have been added in support of IHS Apache by IBM Content Manager for z/os. These messages will be available in the full release of Fix Pack 2 at 1/icm_rm_zos_over.htm Message ID: ICM237E Message text: The IBM HTTP Server level is not supported. Explanation: The IBM HTTP Server version is not supported by z/os. For example, the IBM HTTP Server V5.3 will no longer be supported after z/os Version 2.1. User response: Find the supported versions of IBM HTTP Server in the software prerequisites for Content Manager for z/os, and make sure that the version is also supported by z/os itself. In addition, check that the resource manager is indeed being loaded by the intended version of the IBM HTTP Server. Message ID: ICM238E Message text: The object length in the HTTP header does not match the actual transfer length. Explanation: The data in the HTTP header that the resource manager received indicated a certain object length; however, during the actual transfer, the object seems to have a different length. User response: A network or client error can cause the lengths to appear different. If the problem persists, find the offending clients, and analyze why the data in the HTTP header does not match the actual object length. Message ID: ICM239E Message text: HTTP Write error. Explanation: The resource manager failed to send data to the requesting client or API. There may be a network error, or a client closed its connection prematurely. User response: A network or client error may have occurred. If the problem persists, a client may be programmatically closing its connection prematurely. For example, a client opens a connection, requests data, and closes the connection prematurely. Such clients can be modified to either read the entire object, or to request the necessary portion only.

9 Message ID: ICM240E Message text: The IBM HTTP Server is not initialized for this resource manager. Explanation: The resource manager received its first request via HTTP before its local initialization routine was run by the IBM HTTP Server. User response: Modify the IBM HTTP Server configuration file (for example, httpd.conf) to call the resource manager initialization routine when the server starts: If you are using IBM HTTP Server V8.5.5 or above, call the initialization routine ICMResourceManager?RMDB2SYS??ICMMOPLN? where?rmdb2sys? is the DB2 Subsystem to which the resource manager should connect, and? ICMMOPLN? is the DB2 plan name created in the bind job that the resource manager is opening. The tokens must be replaced by the same values as the tokens used in the Bind job. If you are using IBM HTTP Server V5.3, use the ServerInit directive to call the resource manager initialization routine: ServerInit <path>/icmmosct.so:syncrmdatawithls 7 Changes to the IHS Server V5.3 A ServerInit directive has been added to call the resource manager initialization routine. The rm_module_name can be either icmmosct for OAM or icmmotct for TSM and OAM ServerInit <path>/rm_module_name.so:syncrmdatawithls Example: ServerInit?ppr?/usr/lpp/icm/V8R5M0/bin/icmmosct.so:SyncRMDataWithLS Service /ICMResourceManager*?ppr?/usr/lpp/icm/V8R5M0/bin/icmmosct.so:myservice 8 IPv6 Support Prior to Content Manager Version 8.5 Fix Pack 2, IHS Apache is used as a proxy server to implement IPv6 in a Content Manager for z/os environment. With the availability of Content Manager 8.5 Fix Pack 2, resource manager can run under IHS Apache and if so, the proxy server is no longer needed. There no specific customization needed in the IHS Apache configuration file or in the CM, IHS Apache with resource manager plugin can process IPv6 Communication automatically. 9 Best practice tips 1) Language Environment (LE) tuning options: HEAP and STACK storage are used by the LE routines to define work areas in memory. Performance could be improved when the initial allocation of memory for HEAP and STACK are adjusted so that the LE manager of storage is continually freeing storage to maintain the specified threshold. You can adjust the STACK for the best performance in IHS Apache envvars under the bin directory of the IHS Apache install path. For example: set _CEE_RUNOPTS="STACK(1M,128K,ANY,KEEP,1M,128K)" 2) Set up the same started task name: When you issue the command S WEBSRV2,ACTION='start' to start the started task, you will see several started tasks with different names. If the started task procedure name has seven characters or less, then the spawned started tasks will each have a digit appended to their name. You can set them all to the same started task name, (for example: _BPX_JOBNAME=WEBSRV2X) by using the environment variable in the IHS Apache envvars file.

10 3) Service class for the IHS Apache started task: define a service class with a high response time goal (for example: Execution velocity of 25). For more information on to setting up for WLM (workload management) for IHS Apache, refer to the WLM topic in the redpaper IBM HTTP Server on z/os Migrating from Domino-powered to Apache-powered (see url in #2 in the External Documentation below). 10 External Documentation 1) IHS 8.0 documentation on Knowledge Center (this has all platforms): /ihs/welcome_ihs.html 2) Redpaper specific for IHS Domino to Apache migration: 3) Techdoc provides a sample custom module for use with the IBM HTTP Server for z/os powered by Apache: 4) Apache 2.2 general documentation hosted in an IBM website: 5) IBM Content Manager V8.5 for z/os resource manager planning: htm