DOCSLIB.ORG

Runtime Configuration Guidelines

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Runtime Configuration Guidelines 2006-09-05 Java and all Java-based trademarks are Apple Computer, Inc. trademarks or registered trademarks of Sun © 2003, 2006 Apple Computer, Inc. Microsystems, Inc. in the U.S. and other All rights reserved. countries. Simultaneously published in the United No part of this publication may be States and Canada. reproduced, stored in a retrieval system, or Even though Apple has reviewed this document, transmitted, in any form or by any means, APPLE MAKES NO WARRANTY OR mechanical, electronic, photocopying, REPRESENTATION, EITHER EXPRESS OR IMPLIED, WITH RESPECT TO THIS recording, or otherwise, without prior DOCUMENT, ITS QUALITY, ACCURACY, written permission of Apple Computer, Inc., MERCHANTABILITY, OR FITNESS FOR A with the following exceptions: Any person PARTICULAR PURPOSE. AS A RESULT, THIS DOCUMENT IS PROVIDED “AS IS,” AND is hereby authorized to store documentation YOU, THE READER, ARE ASSUMING THE on a single computer for personal use only ENTIRE RISK AS TO ITS QUALITY AND ACCURACY. and to print copies of documentation for IN NO EVENT WILL APPLE BE LIABLE FOR personal use provided that the DIRECT, INDIRECT, SPECIAL, INCIDENTAL, documentation contains Apple’s copyright OR CONSEQUENTIAL DAMAGES notice. RESULTING FROM ANY DEFECT OR INACCURACY IN THIS DOCUMENT, even if The Apple logo is a trademark of Apple advised of the possibility of such damages. Computer, Inc. THE WARRANTY AND REMEDIES SET FORTH ABOVE ARE EXCLUSIVE AND IN Use of the “keyboard” Apple logo LIEU OF ALL OTHERS, ORAL OR WRITTEN, EXPRESS OR IMPLIED. No Apple dealer, agent, (Option-Shift-K) for commercial purposes or employee is authorized to make any without the prior written consent of Apple modification, extension, or addition to this may constitute trademark infringement and warranty. unfair competition in violation of federal Some states do not allow the exclusion or limitation of implied warranties or liability for and state laws. incidental or consequential damages, so the above limitation or exclusion may not apply to No licenses, express or implied, are granted you. This warranty gives you specific legal with respect to any of the technology rights, and you may also have other rights which vary from state to state. described in this document. Apple retains all intellectual property rights associated with the technology described in this document. This document is intended to assist application developers to develop applications only for Apple-labeled or Apple-licensed computers. Every effort has been made to ensure that the information in this document is accurate. Apple is not responsible for typographical errors. Apple Computer, Inc. 1 Infinite Loop Cupertino, CA 95014 408-996-1010 Apple, the Apple logo, AppleScript, Carbon, Cocoa, Mac, Mac OS, Quartz, Sherlock, and Xcode are trademarks of Apple Computer, Inc., registered in the United States and other countries. Finder and Safari are trademarks of Apple Computer, Inc. Objective-C is a registered trademark of NeXT Software, Inc. Contents Introduction to Runtime Configuration Guidelines 9 Organization of This Document 9 Information Property List Files 11 Standard Information Property List Files 11 Localizing Property List Values 12 Creating and Editing Property Lists 12 An Example of an Information Property List File 13 Putting Info.plist Files in a Flat Executable 14 Property List Key Reference 15 Key Summary 15 Key Descriptions 20 APInstallerURL 20 APFiles 20 CFAppleHelpAnchor 20 CFBundleAllowMixedLocalizations 21 CFBundleDevelopmentRegion 21 CFBundleDisplayName 21 CFBundleDocumentTypes 21 CFBundleExecutable 23 CFBundleHelpBookFolder 23 CFBundleHelpBookName 23 CFBundleIconFile 23 CFBundleIdentifier 23 CFBundleInfoDictionaryVersion 24 CFBundleLocalizations 24 CFBundleName 24 CFBundlePackageType 24 CFBundleShortVersionString 24 CFBundleSignature 25 CFBundleURLTypes 25 CFBundleVersion 25 CFPlugInDynamicRegistration 25 CFPlugInDynamicRegisterFunction 26 3 2006-09-05 | © 2003, 2006 Apple Computer, Inc. All Rights Reserved. CFPlugInFactories 26 CFPlugInTypes 26 CFPlugInUnloadFunction 26 CSResourcesFileMapped 26 LSBackgroundOnly 27 LSEnvironment 27 LSGetAppDiedEvents 27 LSHasLocalizedDisplayName 27 LSMinimumSystemVersion 27 LSMultipleInstancesProhibited 28 LSPrefersCarbon 28 LSPrefersClassic 28 LSRequiresCarbon 28 LSRequiresClassic 28 LSUIElement 29 LSUIPresentationMode 29 LSVisibleInClassic 30 NSAppleScriptEnabled 30 NSHumanReadableCopyright 30 NSJavaNeeded 30 NSJavaPath 30 NSJavaRoot 30 NSMainNibFile 30 NSPersistentStoreTypeKey 31 NSPrefPaneIconFile 31 NSPrefPaneIconLabel 31 NSPrincipalClass 31 NSServices 31 The Preferences System 33 How Preferences Are Stored 34 Preference Domains 34 The defaults Utility 35 Environment Variables 37 Environment Variable Scope 37 User Session Environment Variables 37 Application-Specific Environment Variables 38 Guidelines for Configuring Applications 39 Information Property List Files 39 Required Properties 39 Recommended Properties 40 4 2006-09-05 | © 2003, 2006 Apple Computer, Inc. All Rights Reserved. Localized Properties 40 Document Configuration 41 The PkgInfo File 41 Using a ‘plst’ Resource 42 Using Launch Arguments 42 Document Revision History 43 5 2006-09-05 | © 2003, 2006 Apple Computer, Inc. All Rights Reserved. 6 2006-09-05 | © 2003, 2006 Apple Computer, Inc. All Rights Reserved. Tables and Listings Information Property List Files 11 Listing 1 The Info.plist file for the Sketch demo application 13 Property List Key Reference 15 Table 1 Summary of standard keys 15 Table 2 Keys for APFiles dictionary 20 Table 3 Keys for type-definition dictionaries 21 Table 4 Keys for CFBundleURLTypes dictionaries 25 Table 5 Keys for NSServices dictionaries 31 The Preferences System 33 Table 1 Preference domains in search order 35 Guidelines for Configuring Applications 39 Table 1 Command-line arguments for Cocoa applications 42 7 2006-09-05 | © 2003, 2006 Apple Computer, Inc. All Rights Reserved. 8 2006-09-05 | © 2003, 2006 Apple Computer, Inc. All Rights Reserved. Introduction to Runtime Configuration Guidelines Dynamic configuration is a convenient way to adjust the properties of your executable without recompiling your code. Rather than relying on hardcoded information, your application implements slightly different behaviors based on external settings. There are several ways to record these settings, ranging from user preferences to property lists stored with your bundle. Bundles use property lists extensively to store information about the bundle and its contents. The information in these property lists is used by system entities, such as the Finder and Launch Services, to determine what to do with the bundle. For example, Launch Services uses data in an application’s information property list to bind one or more document types to the application. Organization of This Document This document contains the following articles: ■ “Information Property List Files” (page 11) discusses information property list files and how you use them to configure your bundled application. ■ “Property List Key Reference” (page 15) provides a reference for the keys that can go into an information property list file. ■ “The Preferences System” (page 33) discusses the role and scope of user preferences and describes the use of the defaults tool for accessing preferences. ■ “Environment Variables” (page 37) discusses the role of environment variables in configuring applications. This section also covers some of the ways you can establish environment variables for a given user session or process. ■ “Guidelines for Configuring Applications” (page 39) lists the required and recommended configuration options for applications. This article also describes additional ways to configure both bundled and non-bundled applications. Organization of This Document 9 2006-09-05 | © 2003, 2006 Apple Computer, Inc. All Rights Reserved. Introduction to Runtime Configuration Guidelines 10 Organization of This Document 2006-09-05 | © 2003, 2006 Apple Computer, Inc. All Rights Reserved. Information Property List Files Information property list files contain essential configuration information for a bundled executable. Most bundles have at least one file of this type (usually named Info.plist) containing most of the bundle’s configuration information. Other files may also be present depending on the bundle’s contents. All property list files contain text data encoded using Unicode UTF-8 and organized using Extensible Markup Language (XML) code. The XML structure is a great programmatic convenience as it permits the information in the file to be organized hierarchically. Elements of XML correspond to entities such as arrays, dictionaries, strings, and other simple types. Individual properties can represent simple types or containers for other properties. Important: In the sections that follow, pay attention to the capitalization of files and directories that reside inside a bundle. CFBundle and NSBundle consider case when searching for resources inside a bundle directory. Case mismatches could prevent you from finding your resources at runtime. Standard Information Property List Files By convention, a bundle’s information property list file has the name Info.plist. This file resides in the bundle’s Contents directory and contains configuration information for all supported platforms. However, if you want to configure your application differently on different platforms, you can include platform-specific versions of your information property list file. These files reside in your Contents
Recommended publications
  • Tinkertool System 7 Reference Manual Ii

    Tinkertool System 7 Reference Manual Ii

    Documentation 0642-1075/2 TinkerTool System 7 Reference Manual ii Version 7.5, August 24, 2021. US-English edition. MBS Documentation 0642-1075/2 © Copyright 2003 – 2021 by Marcel Bresink Software-Systeme Marcel Bresink Software-Systeme Ringstr. 21 56630 Kretz Germany All rights reserved. No part of this publication may be redistributed, translated in other languages, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of the publisher. This publication may contain examples of data used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. The publisher may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Make sure that you are using the correct edition of the publication for the level of the product. The version number can be found at the top of this page. Apple, macOS, iCloud, and FireWire are registered trademarks of Apple Inc. Intel is a registered trademark of Intel Corporation. UNIX is a registered trademark of The Open Group. Broadcom is a registered trademark of Broadcom, Inc. Amazon Web Services is a registered trademark of Amazon.com, Inc.
  • Designing PCI Cards and Drivers for Power Macintosh Computers

    Designing PCI Cards and Drivers for Power Macintosh Computers

    Designing PCI Cards and Drivers for Power Macintosh Computers Revised Edition Revised 3/26/99 Technical Publications © Apple Computer, Inc. 1999 Apple Computer, Inc. Adobe, Acrobat, and PostScript are Even though Apple has reviewed this © 1995, 1996 , 1999 Apple Computer, trademarks of Adobe Systems manual, APPLE MAKES NO Inc. All rights reserved. Incorporated or its subsidiaries and WARRANTY OR REPRESENTATION, EITHER EXPRESS OR IMPLIED, WITH No part of this publication may be may be registered in certain RESPECT TO THIS MANUAL, ITS reproduced, stored in a retrieval jurisdictions. QUALITY, ACCURACY, system, or transmitted, in any form America Online is a service mark of MERCHANTABILITY, OR FITNESS or by any means, mechanical, Quantum Computer Services, Inc. FOR A PARTICULAR PURPOSE. AS A electronic, photocopying, recording, Code Warrior is a trademark of RESULT, THIS MANUAL IS SOLD “AS or otherwise, without prior written Metrowerks. IS,” AND YOU, THE PURCHASER, ARE permission of Apple Computer, Inc., CompuServe is a registered ASSUMING THE ENTIRE RISK AS TO except to make a backup copy of any trademark of CompuServe, Inc. ITS QUALITY AND ACCURACY. documentation provided on Ethernet is a registered trademark of CD-ROM. IN NO EVENT WILL APPLE BE LIABLE Xerox Corporation. The Apple logo is a trademark of FOR DIRECT, INDIRECT, SPECIAL, FrameMaker is a registered Apple Computer, Inc. INCIDENTAL, OR CONSEQUENTIAL trademark of Frame Technology Use of the “keyboard” Apple logo DAMAGES RESULTING FROM ANY Corporation. (Option-Shift-K) for commercial DEFECT OR INACCURACY IN THIS purposes without the prior written Helvetica and Palatino are registered MANUAL, even if advised of the consent of Apple may constitute trademarks of Linotype-Hell AG possibility of such damages.
  • Chapter 1. Origins of Mac OS X

    Chapter 1. Origins of Mac OS X

    1 Chapter 1. Origins of Mac OS X "Most ideas come from previous ideas." Alan Curtis Kay The Mac OS X operating system represents a rather successful coming together of paradigms, ideologies, and technologies that have often resisted each other in the past. A good example is the cordial relationship that exists between the command-line and graphical interfaces in Mac OS X. The system is a result of the trials and tribulations of Apple and NeXT, as well as their user and developer communities. Mac OS X exemplifies how a capable system can result from the direct or indirect efforts of corporations, academic and research communities, the Open Source and Free Software movements, and, of course, individuals. Apple has been around since 1976, and many accounts of its history have been told. If the story of Apple as a company is fascinating, so is the technical history of Apple's operating systems. In this chapter,[1] we will trace the history of Mac OS X, discussing several technologies whose confluence eventually led to the modern-day Apple operating system. [1] This book's accompanying web site (www.osxbook.com) provides a more detailed technical history of all of Apple's operating systems. 1 2 2 1 1.1. Apple's Quest for the[2] Operating System [2] Whereas the word "the" is used here to designate prominence and desirability, it is an interesting coincidence that "THE" was the name of a multiprogramming system described by Edsger W. Dijkstra in a 1968 paper. It was March 1988. The Macintosh had been around for four years.
  • The Open Scripting Architecture: Automating, Integrating, and Customizing Applications

    The Open Scripting Architecture: Automating, Integrating, and Customizing Applications

    The Open Scripting Architecture: Automating, Integrating, and Customizing Applications Unpublished manuscript, 1993 William R. Cook Warren H. Harris Apple Computer Apple Computer Research Topic areas: Language design and implementation, tools and environments, components and frameworks, concurrent and distributed systems, databases and persistence. Abstract The Open Scripting Architecture combines aspects of object-oriented programming, distributed computation, database queries, and dynamic languages into a powerful and practical system for automation, integration, and customization of applications and system services. Applications are integrated together with distributed messaging. The messages operate upon user-level application objects, like windows and spreadsheet cells that are identified by queries over properties and document containment structure. A general-purpose scripting language automates message sending and handling, and supports persistence and mobile objects. Applications call on scripting services to customize the behavior of their objects through a generic script management API. 1 Introduction The Open Scripting Architecture (OSA) is a comprehensive infrastructure for automating complex or repetitive tasks, integrating distributed applications and system services, and customizing application behavior. These end-user benefits are supported by a synergistic combination of technologies: distributed messaging and referencing of application objects, object-oriented scripting languages, and script development and management tools. Object-oriented concepts are used throughout the architecture, in the scripting language, the system, and the applications. The OSA is unique in several respects. First, it decouples the clients of scripting services (applications) from the providers of those services (language processors like AppleScript™). This decoupling allows for uniform scriptability across all applications in the same way a graphics toolbox provides a uniform GUI.
  • Darwin: Mac OS X's Core OS

    Darwin: Mac OS X's Core OS

    ADC April 2001 3/8/01 1:57 PM Page 1 Apple Developer Connection Direct Darwin: Mac OS X’s Core OS eneath Mac OS X’s user-friendly and attractive user interface, Most of the reference documents can be Aqua, and the application frameworks (Classic, Carbon and found in the /Developer/Documentation/ BCocoa) is Darwin: Mac OS X’s core OS. Unseen by users, Kernel directory on any Mac OS X system Darwin provides a strong yet flexible foundation with features like with the Mac OS X Developer Tools package preemptive multitasking, protected memory and real-time support installed. that make Mac OS X a truly modern operating system. The focus of this article is to provide a brief overview of Components of Darwin Darwin and its components as well as give an introduction to Just like in the old Reese’s Peanut Butter developing kernel extensions—modules that extend Darwin’s Cups commercials (“You’ve got chocolate in functionality. For more in-depth information, you should read my peanut butter… No, you’ve got peanut butter on my choco- Inside Mac OS X: Kernel Environment which is available, along late!”), Darwin blends a mixture of mature industry standard com- with other documents referred to in this article, on the Apple ponents such as Mach and BSD with Apple-engineered components Developer Connection (ADC) web site in the Mac OS X to provide Mac OS X with a stable, reliable and extensible founda- Documentation section: tion. Darwin consists of five main components: Mach, I/O Kit, File http://developer.apple.com/techpubs/macosx/macosx.html System, Networking and BSD.
  • Managing OS X with Configuration Profiles

    Managing OS X with Configuration Profiles

    Apple Technical White Paper Managing OS X with Configuration Profiles Apple Technical White Paper Managing OS X with Configuration Profiles OS X Lion v 10.7.3 1 Apple Technical White Paper Managing OS X with Configuration Profiles Table of Contents About Configuration Profiles .......................................................................................3 Creating Configuration Profiles ..................................................................................8 Deploying Configuration Profiles ...............................................................................13 Appendix A: Profile Reference .....................................................................................25 Appendix B: Service Port Reference ..........................................................................28 Appendix C: Example Profiles ......................................................................................29 2 Apple Technical White Paper Managing OS X with Configuration Profiles About Configuration Profiles Introduction On iOS devices, preferences and preconfigured settings are managed with Mobile Device Management (MDM) technologies and configuration profiles. Beginning with OS X Lion, Apple has brought the configuration profile and MDM technologies from iOS to OS X. Configuration profiles not only allow for the same preference policies to be deployed as the Managed Preferences system, but they also bring powerful new configuration options such as directory service binding, 802.1X configuration, and certificate
  • Lecture 7 Mac OS X and Ios Operating Systems Saving Data In

    Lecture 7 Mac OS X and Ios Operating Systems Saving Data In

    Mac OS X and iOS operating systems Lecture 7 Saving data in iOS Tomasz Idzi Agenda NSString and NSData NSFileManager Property List JSON Core Data Mac OS X and iOS operating systems Tomasz Idzi iOS Directories App Documents Inbox Library Caches temp Mac OS X and iOS operating systems Tomasz Idzi iOS Directories Directory Description Backed up by iTunes AppName.app This directory contains the app and all of its resources. NO Documents/ Use this directory to store user-generated content. YES Use this directory to access files that your app was asked to open Documents/Inbox YES by outside entities. Such as mail’s attachments. This is the top-level directory for any files that are not user data Library YES files. Library/Caches Subfolder of Library for any caching files. NO Use this directory to write temporary files that don’t need to persist Tmp/ NO between launches of your app. Mac OS X and iOS operating systems Tomasz Idzi Accessing File Paths NSArray *paths = NSSearchPathForDirectoriesInDomains (NSDocumentDirectory, NSUserDomainMask, YES); NSString *docPath = [paths firstObject]; NSString *path = [docPath stringByAppendingComponent:@”myFile.txt”]; Mac OS X and iOS operating systems Tomasz Idzi Writing NSData BOOL success = [data writeToFile:path options:NSDataWritingAtomic error:&error]; NSDataWritingAtomic - create temp file first NSDataWritingWithoutOverwriting - prevent overwriting an existing file Mac OS X and iOS operating systems Tomasz Idzi Reading NSData [NSData alloc] initWithContentsOfFile: path options:NSDataReadingMappedIfSafe error:&error]; NSDataReadingMappedIfSafe - file should be mapped into virtual memory, if possible and safe NSDataReadingUncached - file should not be stored in the file-system caches NSDataReadingMappedAlways - map the file, if possible.
  • Dell Encryption Enterprise for Mac Administrator Guide V10.9

    Dell Encryption Enterprise for Mac Administrator Guide V10.9

    Dell Encryption Enterprise for Mac Administrator Guide v10.9 March 2021 Rev. A02 Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2012-2021 Dell Inc. All rights reserved. Registered trademarks and trademarks used in the Dell Encryption and Endpoint Security Suite Enterprise suite of documents: Dell™ and the Dell logo, Dell Precision™, OptiPlex™, ControlVault™, Latitude™, XPS®, and KACE™ are trademarks of Dell Inc. Cylance®, CylancePROTECT, and the Cylance logo are registered trademarks of Cylance, Inc. in the U.S. and other countries. McAfee® and the McAfee logo are trademarks or registered trademarks of McAfee, Inc. in the US and other countries. Intel®, Pentium®, Intel Core Inside Duo®, Itanium®, and Xeon® are registered trademarks of Intel Corporation in the U.S. and other countries. Adobe®, Acrobat®, and Flash® are registered trademarks of Adobe Systems Incorporated. Authen tec® and Eikon® are registered trademarks of Authen tec. AMD® is a registered trademark of Advanced Micro Devices, Inc. Microsoft®, Windows®, and Windows Server®, Windows Vista®, Windows 7®, Windows 10®, Active Directory®, Access®, BitLocker®, BitLocker To Go®, Excel®, Hyper-V®, Outlook®, PowerPoint®, Word®, OneDrive®, SQL Server®, and Visual C++® are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. VMware® is a registered trademark or trademark of VMware, Inc. in the United States or other countries.
  • Opencore Reference Manual (0.5.9::::::::: 0.6.0) [2020.07.05]

    Opencore Reference Manual (0.5.9::::::::: 0.6.0) [2020.07.05]

    OpenCore Reference Manual (0.5.90.6.0::::::::: ) [2020.07.05] Copyright ©2018-2020 vit9696 1 Introduction This document provides information on OpenCore user configuration file format used to setup the correct functioning of macOS operating system. It is to be read as the official clarification of expected OpenCore behaviour. All deviations, if found in published OpenCore releases, shall be considered documentation or implementation bugs, and are requested to be reported through Acidanthera Bugtracker. ::::::Errata :::::sheet::is::::::::available:::in OpenCorePkg repository.: This document is structured as a specification, and is not meant to provide a step by step algorithm for configuring end-user board support package (BSP). The intended audience of the document are programmers and engineers with basic understanding of macOS internals and UEFI functioning. For these reasons this document is available exclusively in English, and all other sources or translations of this document are unofficial and may contain errors. Third-party articles, utilities, books, and alike may be more useful for a wider audience as they could provide guide-like material. However, they are prone to their authors’ preferences, tastes, this document misinterpretation, and essential obsolescence. In case you use these sources, for example, Dortania’s OpenCore Desktop Guide and related material, please ensure to follow this document for every made decision and judge its consequences. Be warned that regardless of the sources used you are required to fully understand every dedicated OpenCore configuration option and concept prior to reporting any issues in Acidanthera Bugtracker. 1.1 Generic Terms • plist — Subset of ASCII Property List format written in XML, also know as XML plist format version 1.
  • Macintosh Library Modules Release 2.4.1

    Macintosh Library Modules Release 2.4.1

    Macintosh Library Modules Release 2.4.1 Guido van Rossum Fred L. Drake, Jr., editor 30 March 2005 Python Software Foundation Email: [email protected] Copyright c 2001-2004 Python Software Foundation. All rights reserved. Copyright c 2000 BeOpen.com. All rights reserved. Copyright c 1995-2000 Corporation for National Research Initiatives. All rights reserved. Copyright c 1991-1995 Stichting Mathematisch Centrum. All rights reserved. See the end of this document for complete license and permissions information. Abstract This library reference manual documents Python’s extensions for the Macintosh. It should be used in conjunction with the Python Library Reference, which documents the standard library and built-in types. This manual assumes basic knowledge about the Python language. For an informal introduction to Python, see the Python Tutorial; the Python Reference Manual remains the highest authority on syntactic and semantic questions. Finally, the manual entitled Extending and Embedding the Python Interpreter describes how to add new extensions to Python and how to embed it in other applications. CONTENTS 1 Using Python on a Macintosh 1 1.1 Getting and Installing MacPython .................................. 1 1.2 The IDE ............................................... 2 1.3 The Package Manager ........................................ 3 2 MacPython Modules 5 2.1 macpath — MacOS path manipulation functions ......................... 5 2.2 macfs — Various file system services ............................... 5 2.3 ic — Access to Internet Config ................................... 8 2.4 MacOS — Access to Mac OS interpreter features .......................... 9 2.5 macostools — Convenience routines for file manipulation ................... 10 2.6 findertools — The finder’s Apple Events interface ...................... 10 2.7 EasyDialogs — Basic Macintosh dialogs ............................ 11 2.8 FrameWork — Interactive application framework ........................
  • Clustering and Backing up Hyper-V 2012 R2 on Oracle Zfs Storage Appliance

    Clustering and Backing up Hyper-V 2012 R2 on Oracle Zfs Storage Appliance

    Clustering and Backing Up Hyper-V 2012 R2 with the Oracle ZFS Storage Appliance ORACLE WHITE PAPER | APRIL 2016 Table of Contents Introduction 3 Target Audience 3 Solution Overview 4 Oracle ZFS Storage Appliance Storage Tiering Overview 5 Prerequisites 6 Provisioning iSCSI LUN(s) on Oracle ZFS Storage Appliance 7 Creating a Pool 7 Enabling iSCSI Service 11 Configuring the iSCSI Network 11 Creating an iSCSI Target 12 Registering iSCSI Initiators 15 Creating a Project 19 Creating iSCSI LUNs 20 Connecting Hyper-V Hosts to Oracle ZFS Storage Appliance iSCSI LUN(s) 21 Configuring the iSCSI Network Interface 22 Installing Hyper-V Role, Failover Cluster, and MPIO Features 25 Connecting Hyper-V Hosts to the Oracle ZFS Storage iSCSI Target 30 Configure MPIO for iSCSI Devices Support 36 Creating the Hyper-V Cluster 37 Creating and Validating the Cluster 37 Creating Cluster Shared Volumes (CSV) for Highly Available Virtual Machines 41 Creating a Test Virtual Machine 42 Testing Failover and Failback 47 Monitoring the Oracle ZFS Storage Appliance with DTrace Analytics 50 1 CLUSTERING AND BACKING UP HYPER-V 2012 R2 ON ORACLE ZFS STORAGE APPLIANCE Backing Up Hyper-V VMs Using Commvault Simpana and Intellisnap Plug- for Oracle ZFS Storage Appliance 53 Setting Up the Array Information 53 Installing Agent Software on the Hyper-V Clustered Hosts 53 Configuring the Hyper-V Clients in CommCell Console 53 Creating a Storage Library for the Snapshots 54 Creating a Storage Policy 54 Creating the Snapshot 54 Performing a Backup 55 Restoration 55 Conclusion 55 Appendix A: Reference Architecture for Example Configuration 56 Appendix B: Benchmark Results 58 SPC-2 Results 58 Oracle Quality Awards for NAS 58 Appendix C: Additional References 59 2 CLUSTERING AND BACKING UP HYPER-V 2012 R2 ON ORACLE ZFS STORAGE APPLIANCE Introduction The costs of traditional servers – their deployment, maintenance and recovery time, data center space usage, power and cooling – are key reasons that have led to high adoption rates for virtualization solutions.
  • Programming Mac OS X: a GUIDE for UNIX DEVELOPERS

    Programming Mac OS X: a GUIDE for UNIX DEVELOPERS

    Programming Mac OS X: A GUIDE FOR UNIX DEVELOPERS KEVIN O’MALLEY MANNING Programming Mac OS X Programming Mac OS X A GUIDE FOR UNIX DEVELOPERS KEVIN O’MALLEY MANNING Greenwich (74° w. long.) For electronic information and ordering of this and other Manning books, go to www.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact: Special Sales Department Manning Publications Co. 209 Bruce Park Avenue Fax: (203) 661-9018 Greenwich, CT 06830 email: [email protected] ©2003 by Manning Publications Co. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps. Recognizing the importance of preserving what has been written, it is Manning’s policy to have the books they publish printed on acid-free paper, and we exert our best efforts to that end. Manning Publications Co. Copyeditor: Tiffany Taylor 209 Bruce Park Avenue Typesetter: Denis Dalinnik Greenwich, CT 06830 Cover designer: Leslie Haimes ISBN 1-930110-85-5 Printed in the United States of America 12345678910–VHG–05 040302 brief contents PART 1OVERVIEW ............................................................................. 1 1 ■ Welcome to Mac OS X 3 2 ■ Navigating and using Mac OS X 27 PART 2TOOLS ..................................................................................