Transcription

IBM Education Assistance for z/OS V2R2Item: IBM HTTP Server move from Domino to ApacheElement/Component: IBM HTTP ServerMaterial current as of September 2015 2015 IBM Corporation

Filename: zOS V2R2 IBM HTTP Server move from Domino to ApacheIBM Presentation Template Full VersionAgenda Trademarks Presentation Objectives Overview Usage & Invocation Interactions & Dependencies Migration & Coexistence Considerations Installation Presentation Summary AppendixPage 2 of 31 2015 IBM Corporation

Filename: zOS V2R2 IBM HTTP Server move from Domino to ApacheIBM Presentation Template Full VersionTrademarks See url http://www.ibm.com/legal/copytrade.shtml for a list of trademarks. Additional trademarks:– Apache is a trademark of Apache Software Foundation in theUnited States and/or other countries.Page 3 of 31 2015 IBM Corporation

Filename: zOS V2R2 IBM HTTP Server move from Domino to ApachePresentation Objectives In z/OS V2R2, IBM HTTP Server Powered by Apache will replace IBMHTTP Server powered by Domino. This presentation will provide a briefoverview of some of the installation and configuration tasks required tosetup an IBM HTTP Server powered by Apache. In addition, this presentation will provide examples of some of thecommon aspects of a migration from IBM HTTP Server powered byDomino to an IBM HTTP Server Powered by Apache. For brevity, IBM HTTP Server powered by Domino will be refered to asDGW, and IBM HTTP Server powered by Apache as IHS Apache.Page 4 of 31 2015 IBM Corporation

Filename: zOS V2R2 IBM HTTP Server move from Domino to ApacheIBM Presentation Template Full VersionOverview Problem Statement / Need Addressed– z/OS V2R2 will not include IBM HTTP Server powered by Domino. Solution– Migrate to the included HTTP server, IBM HTTP Server Poweredby Apache V9.0. Benefit / Value– DGW has been functionally stabilized for a long time, havingundergone no development for several years. Unlike DGW, IHSApache supports IPv6, 64-bit execution, and includes securityauthentication and authorization capabilities similar to thoseprovided in DGW. IHS Apache is based on Apache 2.4, withadditional fixes. Apache is widely used, with a large usercommunity, making modules, examples, and skills easy to find.Page 5 of 31 2015 IBM Corporation

Filename: zOS V2R2 IBM HTTP Server move from Domino to ApacheIBM Presentation Template Full VersionUsage & InvocationIHS Apache V9.0 Server Configuration, after the SMP/E install: Defining a configuration and home directory––– Create a new directory in the root. The purpose of this directory is to store configurations for new IBM HTTPServers powered by Apache. It is recommended that a new zFS is created and mounted at this directory for eachzOS image. This avoids the possibility of filling up the zFS that backs the root directory. /ihsconfigCreate a configuration subdirectory for the IHS Apache Server, IHSAE001. /ihsconfig/ihs/ihsae001Create a home subdirectory for the user ID that will run the IHS Apache Server, IHSAE001, and for the protecteduser ID that will be assigned to the started task, IHSAE002. /ihsconfig/home/ihsae001 /ihsconfig/home/ihsae002Define USER IDs using RACF–Page 6 of 31Create a user ID called IHSAE001, which will run the IHS Apache Server. Create a second protected user IDcalled IHSAE002, which will run the started task. These user IDs must have an OMVS segment and should alsohave home directories in the z/OS UNIX environment. It is recommended that these user IDs have non-zeroOMVS UIDs. See the Redbook for further details.adduser ihsae001 dfltgrp(ihsrb13) name('IHS Server 1') omvs(uid(35001)home('/ihsconfig/home/ihsae001') program('/bin/sh'))alu ihsae001 password(ihsrb13) noexpireadduser ihsae002 dfltgrp(ihsrb13) name('Apache Started Task ID')omvs(uid(35002) home('/ihsconfig/home/ihsae002') program('/bin/sh'))alu ihsae001 nopassword 2015 IBM Corporation

Filename: zOS V2R2 IBM HTTP Server move from Domino to ApacheIBM Presentation Template Full VersionUsage & Invocation Creating the IHS–/usr/lpp/ihsa zos/bin/install ihs /ihsconfig/ihs/ihsae001 8230 Run this command while logged into the ihsae001 user ID./ihsconfig/ihs/ihsae001 is the installation directory, and ihsae001 is the server name. The ownershipof this user-created directory should be set to the ihsae001 user ID.8230 is the TCP/IP port that the created IHS Apache instance will Listen on when started. Thedefault is 80.You can create multiple instances of IHS Apache by running install ihs once for each instance.However, you must specify a unique server name each time you run the installer program.The started task name and proclib member used for each IHS Apache instance will match theserver name.Output from install ihsCopying install directory and creating symlinks.Updating install paths.cmd: /usr/lpp/ihsa zos/bin/postinst -i /ihsconfig/ihs/ihsae001 -t install -vPORT 8230 -v SERVERNAME www.yourcompany.com Defining a RACF STARTED rule–Page 7 of 31Issue the following RACF commands to define the user ID for the started task that will be set up to run the serverunder. Note that we are assigning the started task to protected user ID IHSAE002.RDEFINE STARTED IHSAE001.* STDATA(USER(IHSAE002))SETROPTS RACLIST(STARTED) REFRESH 2015 IBM Corporation

Filename: zOS V2R2 IBM HTTP Server move from Domino to ApacheIBM Presentation Template Full VersionUsage & Invocation PROCLIB JCL sample: HAP.SHAPJCL(HAPCPROC)– Issue start command: S IHSAE001–– Take this member and copy it into your SYS1.PROCLIB dataset as IHSAE001. IHSAE001 is theserver name and is unique for each server instance.Unlike IBM HTTP Server powered by Domino, which only has one started task running when itstarted, you will see several started tasks running.All the spawned started tasks have the same name because the original started task had eightcharacters. If the started task name had seven characters or less, the spawned started taskswould each have a digit appended to their name. It is recommended that you use a task name ofexactly eight characters to avoid confusion.Started tasks running after starting IHSAE001SDSF DA SC55 SC55 PAG 0 CPU/L/Z 3/COMMAND INPUT NP JOBNAME StepName ProcStep JobIDIHSAE001 STEP1STC18072IHSAE001 STEP1STC18068IHSAE001 IHSAE001 *OMVSEX STC18082IHSAE001 STEP1STC18086IHSAE001 STEP1STC18094IHSAE001 STEP1STC18092Page 8 of SAE002 2015 IBM Corporation

Filename: zOS V2R2 IBM HTTP Server move from Domino to ApacheIBM Presentation Template Full VersionUsage & InvocationOperator CommandsThese commands are case sensitive, and will only work properly in the System Command Extension area. To use thesecommands, you must enter a ‘/’ at the Command Input area, then press Enter. Then, in the System Command Extension area,enter the commands below. Stop server:s IHSAE001,action 'stop‘ Graceful stop of server, waits for current processing to complete:s IHSAE001,action ‘graceful-stop‘ Restart server without waiting for current processing to complete:s IHSAE001,action 'restart‘ Graceful restart of server waits for current processing to complete:s IHSAE001,action ‘graceful‘ Modify command support–Can add this line to the httpd.confLoadModule zos cmds module modules/mod zos cmds.so–And can then use these modify commands:P IHSAE001F IHSAE001,appl 'graceful-stop'F IHSAE001,appl 'graceful'F IHSAE001,appl 'restart'Page 9 of 31 2015 IBM Corporation

Filename: zOS V2R2 IBM HTTP Server move from Domino to ApacheIBM Presentation Template Full VersionUsage & InvocationCommand line Operation Can issue commands from a telnet or OMVS session– Commands act upon the server of the directory you are in Starting a server:./apachectl -k start Stopping a server./apachectl -k stop./apachectl -k graceful-stop Restarting a server./apachectl -k restart./apachectl -k gracefulPage 10 of 31 2015 IBM Corporation

Filename: zOS V2R2 IBM HTTP Server move from Domino to ApacheIBM Presentation Template Full VersionUsage & InvocationConfiguration IHS Apache configuration is stored in httpd.conf––Located in conf sub-directoryConfiguration achieved by using: Directives that are native to the original Apache.Directives available due to additional modules and features added by IBM.Directives are configuration commands that control one or more aspects of behavior of theserver.Stanzas are enclosed blocks of directives in the configuration file, such as the VirtualHosting stanza below.Virtual Hosting VirtualHost *:80 ServerName www.yourcompany.comDocumentRoot /www/yourcompanyDirectoryIndex index.html index.htmErrorDocument 404 /www/yourcompany/error404 1.htmlErrorDocument 500 /www/yourcompany/error500 1.htmlErrorLog logs/yourcompany 80 error.logCustomLog logs/yourcompany 80 access.log commonLoglevel error /VirtualHost Page 11 of 31 2015 IBM Corporation

Filename: zOS V2R2 IBM HTTP Server move from Domino to ApacheIBM Presentation Template Full VersionInteractions & Dependencies For IBM HTTP Server powered by Apache V9.0 installation, a JavaRuntime Environment using IBM 31-bit SDK for z/OS Java TechnologyEdition V6.0 or higher (5655-R31), or IBM 64-bit SDK for z/OS JavaTechnology Edition V6.0 or higher (5655-R32) must be available on thedriving system. This requirement is for installation of the product andservice only.Page 12 of 31 2015 IBM Corporation

Filename: zOS V2R2 IBM HTTP Server move from Domino to ApacheIBM Presentation Template Full VersionMigration & Coexistence ConsiderationsIn April 2013, IBM recommended that customers migrating to z/OS V2R1use IHS Apache V8.5.5, available in z/OS Ported Tools, as a replacementfor DGW, in anticipation of the removal of support for DGW in z/OS V2R2.While it is possible to migrate from DGW to IHS Apache V9.0 directly withz/OS V2R2, performing such a complex migration this way could potentiallydelay your entire z/OS V2R2 migration.By migrating from DGW to IHS Apache V8.5.5 now, you will have thebenefit of a running reference DGW server available on your z/OS system,additional time to test and verify that the functionality of your new IHSApache V8.5.5 server is comparable to your DGW server, and that the typeof IHS in use is transparent to the enduser. The subsequent migration fromIHS Apache V8.5.5 to IHS Apache V9.0 will be simple in comparison.Page 13 of 31 2015 IBM Corporation

Filename: zOS V2R2 IBM HTTP Server move from Domino to ApacheIBM Presentation Template Full VersionMigration & Coexistence ConsiderationsA strongly suggested migration path if you are using IBM HTTP Server powered by Domino.1. Are you affected? Use the “as is” health check ation/HTTP Health Checker.htmlThis check will simply tell you if you are using IBM HTTP Server powered by Domino.2. While on z/OS V1.13 or z/OS V2.1: Install IBM Ported Tools V1.3 HTTP Server (level 8.5.5, Apache level 2.2). Migrate from IBM HTTP Server powered by Domino to the HTTP Server 8.5.5. Use Redbook: IBM HTTP Server on z/OS: Migrating from Domino-powered to Apachepowered (REDP-4987) Use z/OS UNIX Tools and Toys ihsCMT ix/bpxa1ty2.html). This tool generates an approximationof an equivalent httpd configuration file for IHSA. You can run the Domino and Apache servers side by side on z/OS V1.13 or V2.1. Page 14 of 31z/OS Infoprint Server still needs the Domino server prior to z/OS V2.2! 2015 IBM Corporation

Filename: zOS V2R2 IBM HTTP Server move from Domino to ApacheIBM Presentation Template Full VersionMigration & Coexistence ConsiderationsA strongly suggested migration path if you are using IBM HTTP Server powered by Domino,continued:3. When installing z/OS V2.2: Migrate to IBM HTTP Server 9.0 (in the z/OS V2.2 base, Apache level 2.4). Use “Upgrading to 2.4 from l24/upgrading.html . Refer to J 8.5.5/com.ibm.websphere.ihs.doc/ihs/cihs upgrading2.html for the general process on how to move from 8.5.5 to 9.0 (although thedocumentation does not yet discuss z/OS or 9.0). Configure z/OS Infoprint Server (Infoprint Central), PKI, and Library Server to use the newz/OS V2.2 HTTP Server. Take advantage of the migration accommodation for “dual” IHSA (8.5.5 and 9.0), ifnecessary.Page 15 of 31 2015 IBM Corporation

Filename: zOS V2R2 IBM HTTP Server move from Domino to ApacheIBM Presentation Template Full VersionMigration & Coexistence ConsiderationsThe migration accommodation for “dual” IHSA (8.5.5 and 9.0) onz/OS V2.2IBM Ported Tools V1.2 and V1.3 HTTP Server feature are at level 8.5.5, andwill run on z/OS V1.12, V1.13, and V2.1.and now with a migrationaccommodation: z/OS V2.2.It is recommended to use this migration accommodation if you need bothIHSA 8.5.5 and 9.0 on z/OS V2.2.If you use this migration accommodation, it is expected that you will movefrom IHSA 8.5.5 to 9.0 (and therefore only be using IHSA 9.0) on z/OS V2.2before the End of Service for z/OS V2.1 (planned to be September 2018).Thus, you will have approx. 3 years of “dual” IHSA 8.5.5 and 9.0 support onz/OS V2.2.Page 16 of 31 2015 IBM Corporation

Filename: zOS V2R2 IBM HTTP Server move from Domino to ApacheIBM Presentation Template Full VersionMigration & Coexistence ConsiderationsMigration Health Check IBM has developed a Migration Health Check to determine if any startedtasks are IHS Servers powered by Domino. The suggested check name isZOSMIG HTTP SERVER DOMINO.– Available at the z/OS V2R1 migration and installation support webpage. If any instances of DGW are found, the Health Check will write thefollowing message to syslog, followed by a list of the instance names:“One or more IBM HTTP Server(s) Powered by Domino were found.”Page 17 of 31 2015 IBM Corporation

Filename: zOS V2R2 IBM HTTP Server move from Domino to ApacheIBM Presentation Template Full VersionMigration & Coexistence Considerations Note that the IHS A