1 Randy Vaudt & Craig Kato 17 October 2000 Apache at Inovant TPFUG Fall 2000

2 Apache at Inovant Agenda s Installation experiences s Security plans s Planned use at Inovant s TOC demo s Development environment s Future changes s Questions

3 Apache at Inovant Installation Experiences s Downloading and unpacking the Apache source s Source configuration for TPF s Compiling Apache source s Installing Apache on TPF s Apache configuration s Activating Apache

4 Installation Experiences Downloading and unpacking the Apache source s Version downloaded from the Apache Software Foundation’s web site: s Installation instructions at:  apache_ tar.gz s FTP tarball file to USS s Uncompress and extract on USS using gunzip and pax  “src” subdirectory only s Uncompress on workstation using WinZip  Documentation, configuration files, etc.

5 Installation Experiences Source Configuration for TPF s Daemon Model  “include/ap_config.h” – Add #define USE_TPF_DAEMON  Problems – Looping dlayc() in CLTZ s Nolisten Model  “include/ap_config.h” – Remove #define USE_TPF_DAEMON  Problems – Loadset activation

6 Installation Experiences Source Configuration for TPF (cont.) s Use shared memory for performance  “include/ap_config.h” – Add #define USE_SHMGET_SCOREBOARD – Remove #define USE_TPF_SCOREBOARD

7 Installation Experiences Compiling Apache source s No compilation problems s Compilation instructions at: s Inovant at PUT level 12 s Headers copied to LRECL 72 PDS to remove sequence numbers s Warning expected from “src/main/util_uri.c”  WARNING CBC3280 Function assignment between types “char *” and “const char *” is not allowed.

8 Installation Experiences Installing Apache on TPF s Installation instructions at: s DLM linked using compiled object on USS  Name: CHTA  Pre-allocated by IBM with correct PAT options s Loadset created using sample JCL in “/src/os/tpf/samples” s Internet Daemon Control File (IDCF) entry created  ZINET ADD S-APACHE …

9 Installation Experiences Apache configuration s Posix directory tree created using ZFILE  “/usr/local/apache/…”  conf - Configuration files  logs - Log files  htdocs - HTML documents

10 Installation Experiences Apache configuration (cont.) s Configuration directives  “conf/httpd.conf” – Download to workstation via FTP – Update file – Upload to TPF via FTP – Restart Apache s No “conf/srm.conf” or “conf/access.conf”  “conf/httpd.conf” – ResourceConfig /dev/null – AccessConfig /dev/null

11 Installation Experiences Apache configuration (cont.) s Time and research required s Documentation available  “htdocs/manual” subdirectory  O’Reilly’s Apache: The Definitive Guide

12 Installation Experiences Activating Apache s Starting the server  ZINET START S-APACHE s Stopping the server  ZINET STOP S-APACHE s Stop/start required when  “httpd.conf” modified  Loadset(s) activated (due to Nolisten problem)

13 Apache at Inovant Security plans s Inovant will be developing a custom security module to be linked into Apache DLM  Will interface with revised version of Inovant’s existing SNA/IP remote terminal security package  Will provide security services not part of standard Apache authentication module – Password history, session time-out, logging, audit trail, etc.

14 Apache at Inovant Security plans (cont.) s Web server and its internal files will be protected from outside access using standard Apache directory and file directives s Separate directory structures will be provided outside the web server for application scripts and data s We will be developing utilities to monitor and archive the error_log and access_log files created by Apache in the “log” directory

15 Apache at Inovant Security plans (cont.) s References  O’Reilly’s Writing Apache Modules with Perl and C  Security Tips for Server Configuration –

16 Apache at Inovant Planned use at Inovant s Web-based data security administration s Existing TPF functional messages s MQ administrative functions s Remote console access

17 Planned use at Inovant Web-based data security administration s Convert existing remote terminal security administration functions to web-based interfaces s Add new security administration functions to support the external Apache security module

18 Planned use at Inovant Existing TPF functional messages s Replace user interfaces of application and middleware functional messages  C++ and Perl CGI  Java applets s Only functions not required below CRAS state s User-friendly graphical interfaces  Not direct one-for-one replacements of green screens  Field-level help  Language support (French, Spanish, etc.) s No “screen scraping”

19 Planned use at Inovant MQ administrative functions  GUI interfaces for all ZMQSC entries  List all defined queues and queue depths  Browse items on queue  Delete an item  Transfer an item  Clear a queue  Put a test message

20 Planned use at Inovant Remote console access s Web-based replacement for 3270 SNA remote “green screen” console access s 3270 emulator no longer required s Utilize existing remote terminal security package s Links to web-based documentation and help for TPF functional messages s Prototype Java applet has been developed to interface with a TCP/IP socket server application

21 TOC Demo Prototype based on existing functional messages Standard web technologies s HTML, forms, CSS s C++ CGI s Java, JavaBeans User-friendly interface s Non-cryptic display s Mouse-over help s Multiple language support No “screen scraping”

22 TOC Demo “Green screen” interface ZBDCH 4xxxxxxxxxxxx219 NAA40001I xxxxxxxxxxxx219 FMT=00 4C DF HASH= IID= xxxxxx NAA40002I EXC PRD= FB=40 CD=01 REG REGA REGB REGC REGD REGE REGF EFF TIME= MRB UPD TIME= MRB VIC=A SOURCE HISTORY: MRB EAR RESPONSE CODE: NAA40043I NO ACTIVITY NAA40044I NO PVV DATA NAA40047I NO RISK LEVEL DATA NAA40048I NO FULL AUTH DATA NAA40049I NO NEW AVS DATA NAA40046I NO TELECODE DATA

23 TOC Demo Browser interface

24 TOC Demo Browser interface (cont.)

25 TOC Demo Browser interface (cont.)

26 Apache at Inovant Development environment s CGI programs  Standard C++ development environment  VisualAge/TPF  Same as developing any other DLM on TPF s CGI Infrastructure  C++ classes developed for request & response handling s Java  JDK  VisualAge for Java

27 Apache at Inovant Future changes s Perl  CGI scripting  ZFILE enhancement (APAR PJ27277) required

28 Apache at Inovant Questions?