DOCSLIB.ORG

Chapter 4. Administering and Configuring the Administration Server

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Chapter 4. Administering and Configuring the Administration Server IBM IBM HTTP Server - Powered by Apache Version 9 SC27-8417-01 IBM IBM HTTP Server - Powered by Apache Version 9 SC27-8417-01 ii z/OS V2R2 HTTP Server User's Guide Contents Tables ............... v Chapter 3. Administering and configuring IBM HTTP Server ..... 69 Note ................ vii Performing required z/OS system configurations .. 69 ix Starting and stopping IBM HTTP Server..... 73 Using the administrative console to start IBM How to send your comments to IBM .. xi HTTP Server ............. 74 Using apachectl commands to start IBM HTTP If you have a technical problem........ xi Server ............... 75 Using Windows services to start IBM HTTP Summary of changes ........ xiii Server ............... 76 Using JCL procedures to start IBM HTTP Server Summary of changes for IBM HTTP on z/OS .............. 78 Server Version 9, z/OS Version 2 Configuring IBM HTTP Server ........ 81 Release 2 (V2R2), as updated Apache modules (containing directives) September 2016 ........... xv supported by IBM HTTP Server ...... 82 Apache programs supported by IBM HTTP Server ............... 89 Chapter 1. Product overview and quick Apache APR and APR-util libraries supported by start ................ 1 IBM HTTP Server ........... 90 What is new in this release ......... 1 Apache MPM and addressing modes supported Key differences from the Apache HTTP Server ... 2 by IBM HTTP Server .......... 91 IPv4 and IPv6 configuration for Windows Chapter 2. Migrating and installing IBM operating systems ........... 91 HTTP Server ............. 5 Enabling IBM HTTP Server for FastCGI applications 92 Learn about FastCGI .......... 93 Migrating from previous versions of IBM HTTP FastCGI directives ........... 93 Server ................ 5 Managing IBM HTTP Server remotely with the Migrating from IBM HTTP Server V5.3 for z/OS . 7 WebSphere Application Server administrative Migrating to IBM HTTP Server 9.0 ..... 22 console ............... 104 Installing IBM HTTP Server on distributed systems 23 Extending IBM HTTP Server functionality with Mounting CD-ROMS on AIX, HP-UX, Linux and third-party plug-in modules ........ 105 Solaris systems ............ 26 Viable compilers for Apache and third-party Installing IBM HTTP Server using the GUI ... 28 plug-in modules ........... 106 Installing IBM HTTP Server silently ..... 32 Build method options for dynamic modules .. 107 Creating multiple instances of IBM HTTP Server Considerations for building dynamic modules on Windows operating systems....... 43 on Windows platforms ......... 107 Running multiple instances of IBM HTTP Server Considerations for building dynamic modules from a single install .......... 44 on Unix platforms ........... 108 Installing fix packs on IBM HTTP Server using Configuring IBM HTTP Server for SMF recording 108 the Installation Manager GUI ....... 46 Classifying HTTP requests for WLM (z/OS Uninstalling IBM HTTP Server using the GUI .. 47 operating systems) ........... 109 Uninstalling IBM HTTP Server silently .... 48 WLM directives for IBM HTTP Server .... 111 Uninstalling fix packs from IBM HTTP Server using the Installation Manager GUI ..... 53 Migrating and installing IBM HTTP Server on z/OS Chapter 4. Administering and systems................ 54 configuring the administration server . 113 Installing and configuring IBM HTTP Server on Starting and stopping the IBM HTTP Server the z/OS V2R2 system ......... 54 administration server ........... 113 Installing IBM HTTP Server for WebSphere Protecting access to the IBM HTTP Server Application Server for z/OS V2R1 and earlier .. 58 administration server ........... 114 Configuring an instance of IBM HTTP Server on Enabling access to the administration server z/OS V2R1 ............. 64 using the htpasswd utility ........ 114 Uninstalling IBM HTTP Server for z/OS.... 66 Running the setupadm command for the administration server .......... 115 Setting permissions manually for the administration server .......... 117 © Copyright IBM Corp. 2016 iii Chapter 5. Securing IBM HTTP Server 119 Storing a certificate authority certificate ... 199 Securing IBM HTTP Server ......... 119 Storing the encrypted database password in a Configure SSL between the IBM HTTP Server stash file .............. 199 Administration Server and the deployment Managing keys with the native key database manager ............... 120 gskkyman (z/OS systems) ......... 200 Securing with SSL communications ...... 122 Getting started with the cryptographic hardware Secure Sockets Layer (SSL) protocol ..... 125 for SSL (Distributed systems) ........ 200 SSL directive considerations ....... 131 Cryptographic hardware for Secure Sockets Authentication ............ 132 Layer ............... 200 Encryption ............. 133 Using IKEYMAN to store keys on a PKCS11 Secure Sockets Layer environment variables .. 134 device ............... 202 SSL directives ............ 138 Configuring IBM HTTP Server to use nCipher Setting advanced SSL options ........ 165 and Rainbow accelerator devices and PKCS11 Choosing the level of client authentication... 165 devices .............. 204 Server Name Indication ......... 166 Authenticating with LDAP on IBM HTTP Server Viewing cipher specifications ....... 167 using mod_ldap ............. 205 SSL cipher specifications......... 168 Converting your directives from mod_ibm_ldap Choosing the type of client authentication to mod_ldap............. 207 protection ............. 170 Authenticating with SAF on IBM HTTP Server Defining SSL for multiple-IP virtual hosts ... 171 (z/OS systems) ............. 218 Setting up a reverse proxy configuration with SAF directives ............ 219 SSL................ 171 Setting up HTTP Strict Transport Security (HSTS) 227 IBM HTTP Server certificate management .... 172 Managing keys with the IKEYMAN graphical Chapter 6. Troubleshooting and interface (Distributed systems)........ 175 support: IBM HTTP Server ...... 229 Starting the Key Management utility user Troubleshooting IBM HTTP Server ...... 229 interface .............. 176 Known problems on Windows platforms ... 229 Working with key databases ....... 176 Known problems on z/OS platforms .... 231 Changing the database password ...... 177 Known problems with hardware cryptographic Creating a new key pair and certificate request 178 support on AIX............ 231 Importing and exporting keys ....... 179 Symptoms of poor server response time ... 232 Listing certificate authorities ....... 181 Hints and tips for managing IBM HTTP Server Certificate expiration dates ........ 182 using the administrative console ...... 232 Creating a self-signed certificate ...... 182 Could not connect to IBM HTTP Server Receiving a signed certificate from a certificate administration server error ........ 234 authority .............. 183 Experiencing an IBM HTTP Server Service logon Displaying default keys and certificate failure on Windows operating systems .... 234 authorities ............. 184 Viewing error messages for a target server that Storing a certificate authority certificate ... 185 fails to start .............. 235 Storing the encrypted database password in a Cache messages ........... 236 stash file .............. 185 Configuration messages ......... 236 Managing keys from the command line Handshake messages .......... 238 (Distributed systems) ........... 186 SSL initialization messages ........ 246 Using the gskcapicmd command ...... 187 I/O error messages .......... 254 Key Management Utility command-line SSL stash utility messages ........ 255 interface (gskcmd) syntax ........ 188 Creating a new key database using the Appendix. Accessibility ....... 263 command-line interface ......... 191 Accessibility features ........... 263 Managing the database password using the Consult assistive technologies ........ 263 command line ............ 192 Keyboard navigation of the user interface .... 263 Creating a new key pair and certificate request 193 Dotted decimal syntax diagrams ....... 263 Importing and exporting keys using the command line ............ 194 Creating a self-signed certificate ...... 195 Notices .............. 267 Receiving a signed certificate from a certificate authority .............. 197 Index ............... 269 Displaying default keys and certificate authorities ............. 198 iv z/OS V2R2 HTTP Server User's Guide Tables 1. Default locations for Installation Manager files 60 9. Variables for HTTPS_CIPHER in Secure 2. Apache modules ........... 83 Sockets Layer V2. .......... 136 3. MPM and addressing modes ....... 91 10. Attribute values for the SSLClientAuthGroup 4. Bytes ranges and their descriptions for SMF directive ............. 150 records.............. 109 11. Attribute values for the 5. Signer Certificate information ...... 122 SSLClientAuthRequire directive ..... 151 6. Types of access and mechanisms for SSL 12. Client authentication level ....... 165 environment variables ........ 134 13. Medium and high strength TLS ciphers 169 7. SSL handshake environment variables 135 14. Other TLS ciphers .......... 170 8. Variables for HTTPS_KEYSIZE and 15. Actions for gskcmd command objects 188 HTTPS_SECRETKEYSIZE in Secure Sockets 16. LDAP configuration directives conversion 208 Layer V3 and Transport Layer Security V1 .. 135 © Copyright IBM Corp. 2016 v vi z/OS V2R2 HTTP Server User's Guide Note Before using this information and the product it supports, read the information in Notices. © Copyright IBM Corp. 2016 vii viii z/OS V2R2 HTTP Server User's Guide © Copyright IBM Corp. 2016 ix x z/OS V2R2 HTTP Server User's Guide How to send your comments to IBM
Load more

Recommended publications
  • Creating Dynamic Web-Based Reporting Dana Rafiee, Destiny Corporation, Wethersfield, CT
    Creating Dynamic Web-based Reporting Dana Rafiee, Destiny Corporation, Wethersfield, CT ABSTRACT OVERVIEW OF SAS/INTRNET SOFTWARE In this hands on workshop, we'll demonstrate and discuss how to take a standard or adhoc report and turn it into a web based First, it is important to understand SAS/INTRNET software and its report that is available on demand in your organization. In the use. workshop, attendees will modify an existing report and display the results in various web based formats, including HTML, PDF Three components are required for the SAS/INTRNET software and RTF. to work. INTRODUCTION 1) Web Server Software – such as Microsoft’s Personal To do this, we’ll use Dreamweaver software as a GUI tool to Web Server/Internet Information Services, or the create HTML web pages. We’ll use SAS/Intrnet software as a Apache Web Server. back end tool to execute SAS programs with parameters selected on the HTML screen presented to the user. 2) Web Browser – Such as Microsoft’s Internet Explorer or Netscape’s Navigator. Our goal is to create the following screen for user input. 3) SAS/INTRNET Software – Called the Application Dispatcher. It is composed of 2 pieces. o SAS Application Server – A SAS program on a Server licensed with the SAS/INTRNET Module. o Application Broker – A Common Gateway Interface (CGI) program that resides on the web server and communicates between the Browser and the Application Server. These components can all reside on the same system, or on different systems. Types of Services 1) Socket Service: is constantly running, waiting for incoming Transactions.
    [Show full text]
  • An Execution Model for Serverless Functions at the Edge
    An Execution Model for Serverless Functions at the Edge Adam Hall Umakishore Ramachandran Georgia Institute of Technology Georgia Institute of Technology Atlanta, Georgia Atlanta, Georgia ach@gatech:edu rama@gatech:edu ABSTRACT 1 INTRODUCTION Serverless computing platforms allow developers to host single- Enabling next generation technologies such as self-driving cars or purpose applications that automatically scale with demand. In con- smart cities via edge computing requires us to reconsider the way trast to traditional long-running applications on dedicated, virtu- we characterize and deploy the services supporting those technolo- alized, or container-based platforms, serverless applications are gies. Edge/fog environments consist of many micro data centers intended to be instantiated when called, execute a single function, spread throughout the edge of the network. This is in stark contrast and shut down when finished. State-of-the-art serverless platforms to the cloud, where we assume the notion of unlimited resources achieve these goals by creating a new container instance to host available in a few centralized data centers. These micro data center a function when it is called and destroying the container when it environments must support large numbers of Internet of Things completes. This design allows for cost and resource savings when (IoT) devices on limited hardware resources, processing the mas- hosting simple applications, such as those supporting IoT devices sive amounts of data those devices generate while providing quick at the edge of the network. However, the use of containers intro- decisions to inform their actions [44]. One solution to supporting duces some overhead which may be unsuitable for applications emerging technologies at the edge lies in serverless computing.
    [Show full text]
  • The Uch Enmek Example(Altai Republic,Siberia)
    Faculty of Environmental Sciences Institute for Cartography Master Thesis Concept and Implementation of a Contextualized Navigable 3D Landscape Model: The Uch Enmek Example(Altai Republic,Siberia). Mussab Mohamed Abuelhassan Abdalla Born on: 7th December 1983 in Khartoum Matriculation number: 4118733 Matriculation year: 2014 to achieve the academic degree Master of Science (M.Sc.) Supervisors Dr.Nikolas Prechtel Dr.Sander Münster Submitted on: 18th September 2017 Faculty of Environmental Sciences Institute for Cartography Task for the preparation of a Master Thesis Name: Mussab Mohamed Abuelhassan Abdalla Matriculation number: 4118733 Matriculation year: 2014 Title: Concept and Implementation of a Contextualized Navigable 3D Landscape Model: The Uch Enmek Example(Altai Republic,Siberia). Objectives of work Scope/Previous Results:Virtual Globes can attract and inform websites visitors on natural and cultural objects and sceneries.Geo-centered information transfer is suitable for majority of sites and artifacts. Virtual Globes have been tested with an involvement of TUD institutes: e.g. the GEPAM project (Weller,2013), and an archaeological excavation site in the Altai Mountains ("Uch enmek", c.f. Schmid 2012, Schubert 2014).Virtual Globes technology should be flexible in terms of the desired geo-data configuration. Research data should be controlled by the authors. Modes of linking geo-objects to different types of meta-information seems evenly important for a successful deployment. Motivation: For an archaeological conservation site ("Uch Enmek") effort has already been directed into data collection, model development and an initial web-based presentation.The present "Open Web Globe" technology is not developed any further, what calls for a migra- tion into a different web environment.
    [Show full text]
  • Modern Web Application Frameworks
    MASARYKOVA UNIVERZITA FAKULTA INFORMATIKY Û¡¢£¤¥¦§¨ª«¬­Æ°±²³´µ·¸¹º»¼½¾¿Ý Modern Web Application Frameworks MASTER’S THESIS Bc. Jan Pater Brno, autumn 2015 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or ex- cerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Bc. Jan Pater Advisor: doc. RNDr. Petr Sojka, Ph.D. i Abstract The aim of this paper was the analysis of major web application frameworks and the design and implementation of applications for website content ma- nagement of Laboratory of Multimedia Electronic Applications and Film festival organized by Faculty of Informatics. The paper introduces readers into web application development problematic and focuses on characte- ristics and specifics of ten selected modern web application frameworks, which were described and compared on the basis of relevant criteria. Practi- cal part of the paper includes the selection of a suitable framework for im- plementation of both applications and describes their design, development process and deployment within the laboratory. ii Keywords Web application, Framework, PHP,Java, Ruby, Python, Laravel, Nette, Phal- con, Rails, Padrino, Django, Flask, Grails, Vaadin, Play, LEMMA, Film fes- tival iii Acknowledgement I would like to show my gratitude to my supervisor doc. RNDr. Petr So- jka, Ph.D. for his advice and comments on this thesis as well as to RNDr. Lukáš Hejtmánek, Ph.D. for his assistance with application deployment and server setup. Many thanks also go to OndˇrejTom for his valuable help and advice during application development.
    [Show full text]
  • Attacking AJAX Web Applications Vulns 2.0 for Web 2.0
    Attacking AJAX Web Applications Vulns 2.0 for Web 2.0 Alex Stamos Zane Lackey [email protected] [email protected] Blackhat Japan October 5, 2006 Information Security Partners, LLC iSECPartners.com Information Security Partners, LLC www.isecpartners.com Agenda • Introduction – Who are we? – Why care about AJAX? • How does AJAX change Web Attacks? • AJAX Background and Technologies • Attacks Against AJAX – Discovery and Method Manipulation – XSS – Cross-Site Request Forgery • Security of Popular Frameworks – Microsoft ATLAS – Google GWT –Java DWR • Q&A 2 Information Security Partners, LLC www.isecpartners.com Introduction • Who are we? – Consultants for iSEC Partners – Application security consultants and researchers – Based in San Francisco • Why listen to this talk? – New technologies are making web app security much more complicated • This is obvious to anybody who reads the paper – MySpace – Yahoo – Worming of XSS – Our Goals for what you should walk away with: • Basic understanding of AJAX and different AJAX technologies • Knowledge of how AJAX changes web attacks • In-depth knowledge on XSS and XSRF in AJAX • An opinion on whether you can trust your AJAX framework to “take care of security” 3 Information Security Partners, LLC www.isecpartners.com Shameless Plug Slide • Special Thanks to: – Scott Stender, Jesse Burns, and Brad Hill of iSEC Partners – Amit Klein and Jeremiah Grossman for doing great work in this area – Rich Cannings at Google • Books by iSECer Himanshu Dwivedi – Securing Storage – Hackers’ Challenge 3 • We are
    [Show full text]
  • Performance Comparison of XHR Polling, Long Polling, Server Sent Events and Websockets
    Thesis no: urn:nbn:se:bth-14497 Performance comparison of XHR polling, Long polling, Server sent events and Websockets Rasmus Appelqvist Oliver Örnmyr Faculty of Computing Blekinge Institute of Technology SE-371 79 Karlskrona Sweden This thesis is submitted to the Faculty of Computing at Blekinge Institute of Technology in partial fulfillment of the requirements for the degree of Bachelor in Software Engineering. Contact Information: Author(s): Rasmus Appelqvist E-mail: [email protected] Oliver Örnmyr E-mail: [email protected] University advisor: Javier Gonzales Huerta PhD Department of Software Engineering Faculty of Computing Internet : www.bth.se Blekinge Institute of Technology Phone : +46 455 38 50 00 SE-371 79 Karlskrona, Sweden Fax : +46 455 38 50 57 i ABSTRACT Context. Many simultaneous clients that connects to a website where the client receives frequent updates from the server will put stress on the server. Selecting a performance efficient technology for sending updates to the client when building the web sites can allow for lesser server hardware requirements which can result in reduced server hardware costs. Knowledge about the difference between the technologies that can solve the problem of updating a client with information from the server is necessary to decide which technology to use to gain performance. Objectives. This study considers what performance factors that affect XHR polling, Long polling, Server sent events and Websockets to allow web application developers to decide on when to use which technology. This study will also try to find out if the performance difference between the compared technologies are noticeable and which one is the best from a performance perspective.
    [Show full text]
  • Interfacing Apache HTTP Server 2.4 with External Applications
    Interfacing Apache HTTP Server 2.4 with External Applications Jeff Trawick Interfacing Apache HTTP Server 2.4 with External Applications Jeff Trawick November 6, 2012 Who am I? Interfacing Apache HTTP Server 2.4 with External Applications Met Unix (in the form of Xenix) in 1985 Jeff Trawick Joined IBM in 1990 to work on network software for mainframes Moved to a different organization in 2000 to work on Apache httpd Later spent about 4 years at Sun/Oracle Got tired of being tired of being an employee of too-huge corporation so formed my own too-small company Currently working part-time, coding on other projects, and taking classes Overview Interfacing Apache HTTP Server 2.4 with External Applications Jeff Trawick Huge problem space, so simplify Perspective: \General purpose" web servers, not minimal application containers which implement HTTP \Applications:" Code that runs dynamically on the server during request processing to process input and generate output Possible web server interactions Interfacing Apache HTTP Server 2.4 with External Applications Jeff Trawick Native code plugin modules (uhh, assuming server is native code) Non-native code + language interpreter inside server (Lua, Perl, etc.) Arbitrary processes on the other side of a standard wire protocol like HTTP (proxy), CGI, FastCGI, etc. (Java and \all of the above") or private protocol Some hybrid such as mod fcgid mod fcgid as example hybrid Interfacing Apache HTTP Server 2.4 with External Applications Jeff Trawick Supports applications which implement a standard wire protocol, no restriction on implementation mechanism Has extensive support for managing the application[+interpreter] processes so that the management of the application processes is well-integrated with the web server Contrast with mod proxy fcgi (pure FastCGI, no process management) or mod php (no processes/threads other than those of web server).
    [Show full text]
  • XAMPP Web Development Stack
    XAMPP Web Development Stack Overview @author R.L. Martinez, Ph.D. The steps below outline the processes for installing the XAMPP stack on a local machine. The XAMPP (pronounced Zamp) stack includes the following: Apache HTTP Server, MariaDB (essentially MySQL), Database Server, Perl, and the PHP Interpreter. The “X” in XAMPP is used to signify the cross-platform compatibility of the stack. The Apache HTTP Server and PHP are required to run phpMyAdmin which is a PHP application that is used for database administration tasks such as creating databases and tables, adding users, etc. Alternative to XAMPP If you have experience with MySQL Workbench, you may prefer to install MySQL Server and MySQL Workbench via the MySQL Installer. MySQL Workbench performs the same functions as phpMyAdmin. However, unlike phpMyAdmin which is a web-based application, MySQL Workbench is a locally installed application and therefore does not require an HTTP Server (e.g. Apache) to run. Installing XAMPP Many of the steps listed have several alternatives (such as changing MySQL passwords via a command line) and students are welcomed and encouraged to explore alternatives. 1. Download XAMPP from the URL below and place the installer (.exe) in the location where you want to install XAMPP. Placing the installer (.exe) in the same location as the intended installation is not required but preferred. http://www.apachefriends.org/download.html Page 1 of 17 XAMPP Web Development Stack 2. See the warning which recommends not installing to C:\Program Files (x86) which can be restricted by UAC (User Account Control). In the steps below XAMPP is installed to a USB flash drive for portability.
    [Show full text]
  • About Mod Perl Table of Contents
    About mod_perl Table of Contents: About mod_perl General information regarding mod_perl of historical inter- est. Last modified Sun Feb 16 01:38:23 2014 GMT 15 Feb 2014 1 Table of Contents: Part I: Development - 1. The mod_perl Project Management Committee the mod_perl Project Management Committee (PMC) is a group of mod_perl committers who take responsibility for the long-term direction of the project. - 2. mod_perl Contributors A list of people having helped mod_perl along the way, and information about them - 3. Companies sponsoring and supporting mod_perl developers Several companies have contributed to mod_perl by sponsoring mod_perl developers and/or allowing their employees to work on mod_perl as a part of their day job. - 4. Other contributors to mod_perl The other contributions made to mod_perl, that we don’t have enough information on. - 5. History Since mod_perl’s inception in 1996, many things have changed, and it’s interesting to look at mod_perl’s evolution and related events during the time from then to now. Part II: Link to This Site - 6. Link to us A number of banners and buttons that can be used to link to the mod_perl site Part III: mod_perl General Information - 7. How to pronounce mod_perl Do you think that "mod_perl" is a strange name and wondering about how to pronounce it? - 8. License mod_perl is an Apache Software Foundation (http://www.apache.org/) project, licensed under The Apache Software License, an Open Source license. 2 15 Feb 2014 The mod_perl Project Management Committee 1 The mod_perl Project Management Committee 1 The mod_perl Project Management Committee 15 Feb 2014 3 1.1 Description 1.1 Description the mod_perl Project Management Committee (PMC) is a group of mod_perl committers who take respon- sibility for the long-term direction of the project.
    [Show full text]
  • Security Guide Release 21.0.2 F10645-01
    1[Oracle®] AutoVue Client/Server Deployment Security Guide Release 21.0.2 F10645-01 October 2018 Oracle® AutoVue Client/Server Deployment Security Guide Release 21.0.2 F10645-01 Copyright © 1999, 2018, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • CA SOA Security Manager Agent Configuration Guide
    CA™ SOA Security Manager Agent Configuration Guide r12.1 Second Edition This documentation and any related computer software help programs (hereinafter referred to as the "Documentation") are for your informational purposes only and are subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be used or disclosed by you except as may be permitted in a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.
    [Show full text]
  • Release Information Manual Version 8.3.0
    Release Information Manual Version 8.3.0 Table of Contents Preface ...................................................................................................................... 1 About the TerraLens® Platform ...................................................................................... 1 In This Manual ........................................................................................................... 2 Intended Audience ..................................................................................................... 2 1 Product Components ................................................................................................ 3 2 Supported Platforms ................................................................................................ 4 Operating Systems, Compilers, and Programming Languages .................................................. 4 Graphics Hardware and Drivers ...................................................................................... 6 3 New Features ......................................................................................................... 7 TerraLens 8.3.0 ......................................................................................................... 7 DEM GeoTIFFs ......................................................................................................... 7 WMTS MapServer ..................................................................................................... 7 WMTS MapSource....................................................................................................
    [Show full text]