2 options
IBM HTTP server (powered by apache) : an integrated solution for IBM eServer iSeries servers / Thomas Barlen, Wilfried Blankertz.
- Format:
- Book
- Author/Creator:
- Barlen, Thomas.
- Series:
- IBM redbooks.
- Redbooks
- Language:
- English
- Subjects (All):
- Computer networks.
- Client/server computing.
- Physical Description:
- 1 online resource (458 p.)
- Place of Publication:
- San Jose, CA : IBM, International Technical Support Organization, c2005.
- Language Note:
- English
- Contents:
- Front cover
- Contents
- Notices
- Trademarks
- Foreword
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Summary of changes
- January 2005, Third Edition
- Part 1 Zen and the art of the HTTP server
- Chapter 1. 'Powered by Apache' means OS/400 integration
- 1.1 HTTP Server (powered by Apache) features
- 1.1.1 HTTP Version 1.1
- 1.1.2 GUI configuration and administration
- 1.1.3 Virtual hosts
- 1.1.4 Authentication
- 1.1.5 SSL and TLS
- 1.1.6 Proxy caching
- 1.1.7 Local memory cache
- 1.1.8 Server-side includes
- 1.1.9 CGI programming
- 1.1.10 LDAP support
- 1.1.11 Webserver Search Engine and Web Crawler
- 1.1.12 Web-based Distributed Authoring and Versioning
- 1.1.13 Access log reporting and Web usage mining
- 1.1.14 Log rollover and maintenance
- 1.1.15 Domino plug-in
- 1.1.16 WebSphere Application Server plug-in
- 1.1.17 Apache Software Foundation's Jakarta Tomcat
- 1.1.18 Apache Portable Runtime and modules
- 1.1.19 Support for the TRCTCPAPP command
- 1.1.20 Collection Services performance data
- 1.1.21 Real-time server statistics
- 1.1.22 Triggered Cache Manager
- 1.1.23 Fast Response Cache Accelerator
- 1.1.24 Compression
- 1.1.25 Highly available HTTP server
- 1.1.26 Support for IASPs
- 1.1.27 Asynchronous I/O
- 1.1.28 Denial of service
- 1.1.29 Miscellaneous
- 1.2 For more information
- Chapter 2. From zero to powered by Apache
- 2.1 Before you start
- 2.1.1 Software
- 2.1.2 User profile authorities
- 2.1.3 Web browser
- 2.2 Software installation
- 2.2.1 Installing LPPs and OS/400 options
- 2.2.2 Installing PTFs
- 2.2.3 Installing the ITSO example Web application (optional)
- 2.3 Testing the HTTP Server (powered by Apache) installation
- 2.3.1 Your first HTTP Server (powered by Apache) via a wizard.
- Chapter 3. The new GUI: IBM Web Administration for iSeries
- 3.1 Welcome page: iSeries Tasks page
- 3.2 Header images to access information for help
- 3.3 Tabbed pages for easy navigation
- 3.3.1 Setup tab: Common tasks and wizards
- 3.3.2 Manage tab
- 3.3.3 Advanced tab
- 3.3.4 Related links page
- Chapter 4. Quick guide to Apache contexts and request routing
- 4.1 In-context configuration
- 4.2 Apache server request routing
- 4.3 Request routing example
- 4.4 Configuration recommendations
- 4.5 Configuring directory listings
- Part 2 How to...
- Chapter 5. Virtual hosts
- 5.1 HTTP virtual host overview
- 5.1.1 The way TCP/IP is configured
- 5.1.2 The way the HTTP server will be configured
- 5.1.3 The way the HTTP server will handle visitor requests
- 5.2 HTTP Server (powered by Apache) virtual host overview
- 5.2.1 Additional resources
- 5.3 Virtual hosts: IP-based implementation
- 5.3.1 IP-based virtual host: Problem scenario
- 5.3.2 IP-based virtual host: Solution overview
- 5.3.3 IP-based virtual host: Step-by-step implementation
- 5.4 Virtual hosts: Name-based implementation
- 5.4.1 Name-based virtual hosts: Problem overview
- 5.4.2 Name-based virtual host: Solution overview
- 5.4.3 Name virtual host: Step-by-step implementation
- 5.5 Virtual hosts: Mass dynamic implementation
- 5.5.1 Mass dynamic virtual host: Problem scenario
- 5.5.2 Mass dynamic virtual host: Solution overview
- 5.5.3 Mass dynamic virtual host: Step-by-step implementation
- Chapter 6. Defending the IFS
- 6.1 Access control
- 6.2 Basic authentication
- 6.2.1 Authentication by OS/400 user profiles
- 6.2.2 Authentication by a validation list
- 6.2.3 Authentication by LDAP entries
- 6.3 Authenticating users via Kerberos
- 6.3.1 Getting ready for Kerberos authentication
- 6.3.2 Implementing Kerberos Web authentication.
- 6.4 Encrypting your data with SSL and TLS
- 6.4.1 Enabling SSL
- 6.4.2 TLS upgrade
- 6.4.3 Enabling SSL for the ADMIN instance
- 6.4.4 SSL handshaking
- 6.4.5 Client-side digital certificates
- 6.5 Proxy server: Protecting direct access
- 6.5.1 Forward proxy
- 6.5.2 Reverse proxy
- 6.5.3 SSL proxy
- 6.5.4 Proxy chaining
- 6.6 For more information
- Chapter 7. Serving dynamic data
- 7.1 Server-side includes
- 7.2 Everything dynamic with CGI support
- 7.3 Net.Data: A ready-made scripting tool
- 7.3.1 Implementation: Setting up the Net.Data environment
- 7.3.2 Configuring your HTTP Server (powered by Apache) for CGI
- 7.3.3 Testing your HTTP Server (powered by Apache) and Net.Data macro
- 7.4 For more information
- Part 3 Building a Web application
- Chapter 8. Migration from HTTP Server (original) to (powered by Apache)
- 8.1 A look at HTTP Server (original) and (powered by Apache)
- 8.1.1 Directives and services not supported
- 8.1.2 Equivalent directives
- 8.1.3 Functional differences
- 8.1.4 New HTTP Server (powered by Apache) directives
- 8.2 An example migration
- 8.2.1 Initial situation: HTTP Server (original) configuration
- 8.2.2 Migration steps
- 8.2.3 Result: HTTP Server (powered by Apache) configuration
- 8.3 Testing your migration
- Chapter 9. Web application serving
- 9.1 Web application servers for the iSeries server
- 9.1.1 Comparing WebSphere Application Server and ASF Jakarta Tomcat
- 9.1.2 When to use WebSphere Application Server versus ASF Jakarta Tomcat
- 9.2 Apache Software Foundation's Jakarta Tomcat on iSeries
- 9.2.1 ASF Jakarta Tomcat directory structure
- 9.2.2 ASF Jakarta Tomcat directives
- 9.2.3 ASF Jakarta Tomcat authorities
- 9.2.4 ASF Jakarta Tomcat log files
- 9.3 In-process implementation with ASF Jakarta Tomcat
- 9.3.1 Creating HTTP Server (powered by Apache).
- 9.3.2 In-process Tomcat configuration
- 9.4 Out-of-process implementation with ASF Jakarta Tomcat
- 9.4.1 Creating the ASF Tomcat server
- 9.4.2 Creating the link between the HTTP and ASF Tomcat servers
- 9.4.3 Testing the out-of-process ASF Tomcat server
- Chapter 10. Getting the best performance from HTTP Server (powered by Apache)
- 10.1 iSeries Web server performance components
- 10.2 Web server: Global performance values
- 10.2.1 Threads and asynchronous I/O
- 10.2.2 Process control: HotBackup
- 10.2.3 Logging
- 10.2.4 HostNameLookups
- 10.2.5 KeepAliveTimeout
- 10.2.6 TCP buffer size
- 10.2.7 Denial of service
- 10.2.8 CGI initialization at server startup
- 10.3 Web server: Specific performance values
- 10.3.1 HTTP Server (powered by Apache) local cache
- 10.3.2 HTTP Server (powered by Apache) proxy cache
- 10.4 Increasing throughput with compression
- 10.4.1 Compression considerations
- 10.4.2 Example configurations
- 10.4.3 Logging
- 10.4.4 Controlling the compression environment
- 10.4.5 For more information
- 10.5 Triggered Cache Manager
- 10.5.1 TCM system requirements
- 10.5.2 TCM documentation
- 10.5.3 TCM directory structure and authorization
- 10.5.4 How the TCM server works
- 10.5.5 Configuring a working TCM example
- 10.6 Fast Response Cache Accelerator
- 10.6.1 What FRCA is
- 10.6.2 How FRCA local cache works
- 10.6.3 How FRCA reverse proxy cache works
- 10.6.4 FRCA limitations
- 10.6.5 FRCA configuration examples
- 10.6.6 Miscellaneous FRCA directives beyond the online help
- 10.6.7 The FRCA challenge
- 10.6.8 For more information
- 10.7 Cryptographic coprocessors
- 10.8 Real Time Server Statistics
- 10.9 References
- Chapter 11. Getting started with Webserver Search Engine and Web Crawler
- 11.1 iSeries Webserver Search Engine
- 11.2 iSeries Webserver Search Engine Web Crawler.
- Chapter 12. Apache Portable Runtime: Extending your core functionality
- 12.1 Apache module design overview
- 12.1.1 Documentation and resources
- 12.2 Creating a module for the iSeries server
- 12.2.1 The task at hand
- 12.2.2 Source code and comments
- 12.2.3 Compiling, linking, and exporting your service program
- 12.2.4 Activating via configuration
- 12.2.5 Testing header_module
- 12.2.6 Debugging
- Chapter 13. Problem determination: When things do not go as planned
- 13.1 The art of problem determination
- 13.2 Tools of the trade
- 13.2.1 Working with configuration files
- 13.2.2 Job logs
- 13.2.3 Server logs
- 13.2.4 Net.Data logs and traces
- 13.2.5 HTTP server trace
- 13.2.6 Collection Services performance data
- 13.2.7 Other startup parameters
- 13.2.8 HTTP status codes
- 13.2.9 Communications trace
- 13.2.10 Additional resources
- Chapter 14. High availability
- 14.1 Highly available Web server cluster on the HTTP server
- 14.1.1 Primary or backup with takeover IP model
- 14.1.2 Primary or backup with a network dispatcher model
- 14.1.3 Peer model
- 14.2 A working primary or backup with takeover IP model
- 14.2.1 Problem definition
- 14.2.2 Solution definition
- 14.2.3 Assumptions
- 14.2.4 How to
- 14.3 For more information
- Chapter 15. National language considerations
- 15.1 Installing secondary languages
- 15.2 Net.Data based: iSeries Tasks page and DCM
- 15.3 Servlet based: Administration GUI
- 15.4 Other programs linked from iSeries Task page
- 15.4.1 Internet Printing Protocol server for the iSeries server
- 15.4.2 WebSphere family
- 15.4.3 4758 Cryptographic Coprocessor
- 15.5 Serving your own Web site in the world's languages
- Part 4 Appendixes
- Appendix A. Bringing PHP to your iSeries server
- Programming with PHP on the iSeries server
- What PHP is
- Why PHP
- A code example.
- PHP on the iSeries server.
- Notes:
- "January 2005."
- Includes index.
- OCLC:
- 560113404
The Penn Libraries is committed to describing library materials using current, accurate, and responsible language. If you discover outdated or inaccurate language, please fill out this feedback form to report it and suggest alternative language.