DOCSLIB.ORG

Analysis Server User Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Analysis Server User Guide Analysis Server User Guide This manual explains the basic principles and functionality of the Analysis Server, a software system that enables users to incorporate legacy software into reusable components that can be published on a network. This manual also discusses seven utilities for creating new software components: AnalysisLibraryWrapper, FileWrapper, ExcelWrap- per, ScriptWrapper, PerlWrapper, PXCWrapper, and Java Bean component authoring. The Analysis Server answers several questions that have plagued engineering analysis groups for years: l "How can I provide multi-platform access to our legacy software?" l "How do I make our complicated, convoluted codes a little easier for novices to use?" l "Why do I have to spend all day writing input files and parsing output files when I only want a few critical val- ues?" The Analysis Server allows the user to control complex engineering programs through a simple set of commands (e.g. get, set, and execute). This interface is consistent across all Analysis Server components, so users who understand how to manipulate one component can manipulate them all. The result is enhanced user-friendliness without rewriting the original software. Distributed access and ease of use are only the tip of the Analysis Server's capabilities. Its command set can be incor- porated into a client program, which means that other programs can directly access data from Analysis Server com- ponents. An Analysis Server client can transfer data directly from legacy software to an Excel workbook, for example. If the client program has an integration architecture, it is possible to make several previously stand-alone leg- acy programs from geographically distant, hardware distinct machines work together as though modules of a single program. This manual provides useful information for those who wish to author components and place them on a server machine or use Analysis Server components on their own machines. Topics Quick Links l The Analysis Server Overview l FAQ (online) l Installing and Configuring the Analysis Server l Build History l Analysis Server Security l FileWrapper Statements l Analysis Server Commands l aserver.conf Syntax l Adding Your Components to the Server l The AnalysisLibraryWrapper Utility l The FileWrapper Utility l The ExcelWrapper Utility l The ScriptWrapper Utility l The PerlWrapper Utility l The PXCWrapper Utility l Custom Components Using Java l Setting up a Naming Service Analysis Server Overview The Analysis Server enables users to incorporate analysis software into reusable components that can be published on a network. Once published, users can access these components from any computer on a network, regardless of their platform type, through a simple protocol. The Analysis Server protocol is similar to the HTTP protocol used to pub- lish web documents; as long as the components are properly placed on the server's computer, they can be accessed and used generically. The Analysis Server allows users to control computationally intensive software from cheaper, lightweight platforms. The Analysis Server also hides the details of data management from the user. This means that the user can concentrate on what the data means rather than how to make it fit into an arcane file format for a legacy program. This chapter explains the concept behind the Analysis Server and its benefits to engineers. Concept The Analysis Server provides generic access and control for components through a technique known as software wrapping. Since the advent of object-oriented technology, programmers have used wrapping as a means of reusing legacy software in object-oriented environments. A software wrapper is a thin software program or module that con- verts program-specific input and output operations into generic sets of commands that can apply to a wide range of programs. For example, an engineer may have a FORTRAN program that uses input and output decks. In order to publish the program on the Analysis Server, they could write a wrapper allowing them to enter all inputs and run the program using get and set operations, like these: >set program.input1 = 3 value set for <program.input1> >execute program program completed. >get program.output1 6.0 Notice that engineers do not have to write the actual input decks for the program; in fact, they do not need to know that the program requires input decks at all. Once the component author invests the one-time effort required to write the wrapper, the wrapper automatically performs the tedious task of writing the input and output file. This leaves the engineer free to focus on results. Most input and output files can be wrapped quickly and easily using the FileWrap- per utility. Even files with hundreds of inputs and outputs can be wrapped using the FileWrapper utility in a minimal amount of time. If more flexibility and control is desired, the author can write a wrapper in Java. A user is not limited to accessing components through an interactive session. Developers can write Analysis Server cli- ents that can access components automatically. For example, it is possible to write Excel spreadsheet routines that call an Analysis Server component repeatedly to perform a parametric study. Programmers can write Analysis Server cli- ents in a variety of languages, such as Perl, Java, and C++. The Analysis Server can also be reused as an OLE auto- mation component. Because it is possible to connect to the Analysis Server from multiple locations simultaneously, several users can access the same code from different workstations. Benefits As mentioned, one benefit is saving time otherwise spent building and troubleshooting complex files. When software is used extensively as an R&D or production tool, users may spend a large portion of their time on this tedious, error- prone task. Smart users write scripts that partially automate some of the repetitiveness of these tasks, but these scripts often require program-specific knowledge to use. The Analysis Server's simple get and set methods allow users to operate the code without worrying about these details. The flexibility of software wrapping also allows the Analysis Server to present legacy software as a set of several simple-to-use components rather than as a complex, monolithic program. Expert users understand all of a program's high-level features and can interpret its data accurately and confidently. Basic users operate the program occasionally for a limited number of tasks and may lack the overall conceptual understanding. These basic users may present a dilemma since they cannot reliably use the program in all situations, but may not have an expert available for con- sultation. The Analysis Server solves this dilemma by allowing developers to create one wrapper that exposes the entire program for the expert user and one wrapper that exposes only one or two well understood features to the novice. Writing Analysis Server client programs provides another benefit. Developers can integrate several analysis com- ponents into a single program where they can share data dynamically. These programs can be written with drivers, such as optimizers and graphing tools, that can treat these components as a unified whole. For example, a user can cre- ate a client that links a UNIX-based FORTRAN analysis to a PC based business application. With the client, the user can enter a range of analysis inputs and then graph these inputs against the outputs of the business application. If a bet- ter analysis becomes available, the user can swap the new program for the old one without affecting the client, provided that the new program's wrapper has the same interface functions as the old one. Phoenix Integration has created an Analysis Server client called ModelCenter that enables users to access all the Ana- lysis Servers available on a given network, retrieve their components, and compose them visually into a model con- taining several components and their data sharing relationships. These relationships, called links, enable users to graphically assign the outputs of one analysis to the inputs of another, creating a chain of linked analysis programs that can operate as a single unit. Users can then employ a collection of tools to perform operations such as graphing, parametric sweeps, and optimization on the integrated model. Analysis Server Terminology A public_aserver directory is a base user directory that holds all of the categories and components that a user has published. When the user establishes a connection to the Analysis Server, the Analysis Server searches for all the pub- lic_aserver directories that it can find in a specified path. The Analysis Server's configuration file specifies that path. Each public_aserver is listed as a category when the user performs a listCategories command. The public_aserver directory is similar to a public_html directory; all items inside this directory are accessible to the public, but no items outside of these directories are accessible. Typically, each user in a multi-user system can own a public_aserver directory in their home directory, just as they can own a public_html directory. The analyses directory provides the base repository for Analysis Server components. When publishing a widely used component on the Analysis Server, it can be placed inside of the analyses directory. The analyses directory is a master directory for components; components in this directory and its subdirectories belong to the Analysis Server itself rather than to individual users with accounts on that server. When users want to publish their own components, the components can also be placed in their public_aserver directories. A category is a grouping of components inside an Analysis Server directory. A category hierarchy is analogous to a conventional directory structure inside the computer's directory hierarchy. It is actually implemented by creating sub- directories inside the analyses directory or any public_aserver directory on a server machine. The user can create a hierarchical organization of categories by placing subdirectories inside higher-level category directories.
Load more

Recommended publications
  • WEKA Manual for Version 3-7-8
    WEKA Manual for Version 3-7-8 Remco R. Bouckaert Eibe Frank Mark Hall Richard Kirkby Peter Reutemann Alex Seewald David Scuse January 21, 2013 ⃝c 2002-2013 University of Waikato, Hamilton, New Zealand Alex Seewald (original Commnd-line primer) David Scuse (original Experimenter tutorial) This manual is licensed under the GNU General Public License version 3. More information about this license can be found at http://www.gnu.org/licenses/gpl-3.0-standalone.html Contents ITheCommand-line 11 1Acommand-lineprimer 13 1.1 Introduction . 13 1.2 Basic concepts . 14 1.2.1 Dataset . 14 1.2.2 Classifier . 16 1.2.3 weka.filters . 17 1.2.4 weka.classifiers . 19 1.3 Examples . 23 1.4 Additional packages and the package manager . .24 1.4.1 Package management . 25 1.4.2 Running installed learning algorithms . 26 II The Graphical User Interface 29 2LaunchingWEKA 31 3PackageManager 35 3.1 Mainwindow ............................. 35 3.2 Installing and removing packages . 36 3.2.1 Unofficalpackages ...................... 37 3.3 Usingahttpproxy.......................... 37 3.4 Using an alternative central package meta data repository . 37 3.5 Package manager property file . 38 4SimpleCLI 39 4.1 Commands . 39 4.2 Invocation . 40 4.3 Command redirection . 40 4.4 Command completion . 41 5Explorer 43 5.1 The user interface . 43 5.1.1 Section Tabs . 43 5.1.2 Status Box . 43 5.1.3 Log Button . 44 5.1.4 WEKA Status Icon . 44 3 4 CONTENTS 5.1.5 Graphical output . 44 5.2 Preprocessing . 45 5.2.1 Loading Data .
    [Show full text]
  • 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.
    [Show full text]
  • User Interface Specification for Interactive Software Systems
    User Interface Specification for Interactive Software Systems Process-, Method- and Tool-Support for Interdisciplinary and Collaborative Requirements Modelling and Prototyping-Driven User Interface Specification Dissertation zur Erlangung des akademischen Grades des Doktor der Naturwissenschaften (Dr. rer. nat.) Universität Konstanz Mathematisch-Naturwissenschaftliche Sektion Fachbereich Informatik und Informationswissenschaft Vorgelegt von Thomas Memmel Betreuer der Dissertation: Prof. Dr. Harald Reiterer Tag der mündlichen Prüfung: 29. April 2009 1. Referent: Prof. Dr. Harald Reiterer 2. Referent: Prof. Dr. Rainer Kuhlen Prof. Dr. Rainer Kuhlen For Cathrin Acknowledgements I thank my advisor, Prof. Dr. Harald Reiterer, for more than 6 years of great Prof. Dr. Harald Reiterer teamwork. Since I joined his work group as a student researcher, his guidance and friendship have helped me to reach high goals and achieve scientific recognition. I thank Harald for his creative contributions and his unfailing support, which made him the best supervisor I could imagine. Every time I read the Dr. in front of my name, I will think about the person who made it possible. It was Harald! Moreover, I thank him for teaching me many skills, of which especially purposefulness and per- suasive power opened up a world of possibilities. Among the other researchers in the human-computer interaction work group, spe- My colleague and friend Fredrik cial thanks are due to my colleague Fredrik Gundelsweiler. Fredrik and I started working for Harald at the same time, and since then we have shared many experi- ences. I worked with Fredrik at Siemens AG in Munich, and we both gained interna- tional work experience during our stay at DaimlerChrysler AG in Singapore.
    [Show full text]
  • Vtpin: Practical Vtable Hijacking Protection for Binaries
    VTPin: Practical VTable Hijacking Protection for Binaries Pawel Sarbinowski Vasileios P. Kemerlis Cristiano Giuffrida Vrije Universiteit Amsterdam Brown University Vrije Universiteit Amsterdam [email protected] [email protected] [email protected] Elias Athanasopoulos Vrije Universiteit Amsterdam [email protected] ABSTRACT 1. INTRODUCTION VTable hijacking has lately been promoted to the de facto technique The recent advances in software hardening have undoubtedly for exploiting C++ applications, and in particular web browsers. made exploitation a challenging craft [45]. Yet, despite the plethora VTables, however, can be manipulated without necessarily corrupt- of defenses in place [37], attackers still find ways to compromise ing memory, simply by leveraging use-after-free bugs. In fact, in essential commodity software, like web browsers [5,6]. Modern the recent Pwn2Own competitions all major web browsers were exploits are highly sophisticated and typically leverage a variety of compromised with exploits that employed (among others) use-after- different vulnerabilities to bypass established protections, such as free vulnerabilities and VTable hijacking. address space layout randomization (ASLR) [42], non-executable In this paper, we propose VTPin: a system to protect against memory [12], and sandboxing [18]. To this end, temporal safety VTable hijacking, via use-after-free vulnerabilities, in large C++ errors, and particularly use-after-free vulnerabilities, are becoming binaries that cannot be re-compiled or re-written. The main idea be- a key component of the attackers’ arsenal [1,2,7,8]. Interestingly, hind VTPin is to pin all the freed VTable pointers on a safe VTable exploiting use-after-free bugs does not require corrupting memory; under VTPin’s control.
    [Show full text]
  • United States Patent (19) 11 Patent Number: 6,061,061 Conrad Et Al
    US006061061A United States Patent (19) 11 Patent Number: 6,061,061 Conrad et al. (45) Date of Patent: *May 9, 2000 54) COMPUTER SYSTEM WITH GRAPHICAL 2693810 6/1991 France. USER INTERFACE INCLUDING SPRING LOADED ENCLOSURES OTHER PUBLICATIONS 75 Inventors: Thomas J. Conrad, San Jose; Yin Yin tiMy“M ft WindowSTM 7 User’sSer's Guide.Oude, MiMicroSOIL ft UorporaC Wong, Menlo Park, both of Calif. “Screen Dumps from Microsoft WindowsTM v3.1.” 73 ASSignee: Apple Computer, Inc., Cupertino, Microsoft Corporation, 1985-1992, pp. 1-10. Calif. Jeff Johnson, et al., “The Xerox Star: A Retrospective,” Computer, Sep. 1989, pp. 11-27. * Notice: This patent is subject to a terminal dis- Brad W. Myers, “Window Interfaces, A Taxonomy of Win claimer. dow Manager User Interfaces.” IEEE Computer Graphics and Applications, Sep. 1988, pp. 65-83. 21 Appl. No.: 08/889,719 “Automatic Window Management Mode.” IBM Technical 9 Disclosure Bulletin, vol. 35, No. 4B, Sep. 1992. 22 Filed: Jul. 8, 1997 (List continued on next page.) Related U.S. Application Data Primary Examiner-Crescelle N. dela Torre 63 Continuation of application No. 08/482,186, Jun. 7, 1995, Attorney, Agent, or Firm Blakely, Sokoloff Taylor & Pat. No. 5,680,562, which is a continuation of application Zafman No. 08/076.253, Jun. 11, 1993, Pat. No. 5,583,984. (51) Int. Cl. ................................................ G06F 15/00 57 ABSTRACT 52 U.S. Cl. ............................................. 345/340; 345/348 A new behavior in a graphical user interface allows the user 58 Field of Search ..................................... 345/340, 326, to open and close enclosures, while dragging an object.
    [Show full text]
  • Testing and Maintenance of Graphical User Interfaces Valeria Lelli Leitao
    Testing and maintenance of graphical user interfaces Valeria Lelli Leitao To cite this version: Valeria Lelli Leitao. Testing and maintenance of graphical user interfaces. Human-Computer Inter- action [cs.HC]. INSA de Rennes, 2015. English. NNT : 2015ISAR0022. tel-01232388v2 HAL Id: tel-01232388 https://tel.archives-ouvertes.fr/tel-01232388v2 Submitted on 11 Apr 2016 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. THÈSE INSA Rennes présentée par sous le sceau de l’Université Européenne de Bretagne Valéria Lelli Leitão Dan- pour obtenir le grade de tas DOCTEUR DE L’INSA DE RENNES ÉCOLE DOCTORALE : MATISSE Spécialité : Informatique LABORATOIRE : IRISA/INRIA Thèse soutenue le 19 Novembre 2015 devant le jury composé de : Testing and Pascale Sébillot Professeur, Universités IRISA/INSA de Rennes / Présidente maintenance of Lydie du Bousquet Professeur d’informatique, Université Joseph Fourier / Rapporteuse Philippe Palanque graphical user Professeur d’informatique, Université Toulouse III / Rapporteur Francois-Xavier Dormoy interfaces Chef de produit senior, Esterel Technologies / Examinateur Benoit Baudry HDR, Chargé de recherche, INRIA Rennes - Bretagne Atlantique / Directeur de thèse Arnaud Blouin Maître de Conférences, INSA Rennes / Co-encadrant de thèse Testing and Maintenance of Graphical User Interfaces Valéria Lelli Leitão Dantas Document protégé par les droits d’auteur Contents Acknowledgements 5 Abstract 7 Résumé en Français 9 1Introduction 19 1.1 Context ...................................
    [Show full text]
  • GUI Ripping: Reverse Engineering of Graphical User Interfaces for Testing
    GUI Ripping: Reverse Engineering of Graphical User Interfaces for Testing Atif Memon Ishan Banerjee, Adithya Nagarajan Department of Computer Science Department of Computer Science and Fraunhofer Center for University of Maryland Experimental Software Engineering College Park, Maryland, USA University of Maryland {ishan, sadithya}@cs.umd.edu College Park, Maryland, USA [email protected] Abstract trols that represent everyday objects such as menus, but- tons, lists, and windows. Recognizing the importance of Graphical user interfaces (GUIs) are important parts of GUIs, software developers are dedicating large parts of the today’s software and their correct execution is required to code to implementing GUIs [12]. The correctness of this ensure the correctness of the overall software. A popular code is essential to the correct execution of the overall soft- technique to detect defects in GUIs is to test them by exe- ware. A popular technique to detect defects in software is cuting test cases and checking the execution results. Test testing [3, 2, 23]. During testing, test cases are created and cases may either be created manually or generated auto- executed on the software. Test cases may either be created matically from a model of the GUI. While manual testing manually by a tester [10, 27, 8] or automatically by using a is unacceptably slow for many applications, our experience model of the software derived from its specifications [20]. with GUI testing has shown that creating a model that can In all our work to date [20, 17, 21, 16, 18, 19, 15, 12, 14], be used for automated test case generation is difficult.
    [Show full text]
  • Using-Designer.Pdf
    Using Designer AEM 6.3 Forms Legal notices For legal notices, see http://help.adobe.com/en_US/legalnotices/index.html. Last updated 4/26/17 Contents Welcome to Designer . 1 About Designer . 1 Using Designer in the SAP environment . 1 Using Designer in different spaces . 2 New features in Designer . 2 Render XFA forms as HTML5 forms . 2 Support for Turkish Lira locale . 2 Support for Japanese Postal barcode . 3 Accessibility Checker . 3 Add document title to the PDF title bar . 3 Support for Hindi language . 3 New features in Designer . 3 Preview your XDP forms in HTML in Designer . 3 Preview your XDP forms in HTML in forms manager . 4 Accessibility Checker . 4 Add document title to the PDF title bar . 4 Where to find documentation, samples, and tutorials . 4 Get started with samples and tutorials . 5 Add calculations to forms . 5 Enhance forms by using scripts . 5 Getting Started . 7 About forms . 7 Interactive forms . 7 Non-interactive forms . 8 Print and fill forms . 8 About form designs . 8 Form design layouts . 9 i Fixed layout . 9 Flowable layout . 9 Parts of a form design . 10 Master pages . 10 Pages . 11 Content areas . 11 Subforms . 11 Tables . 12 Field objects . 12 Boilerplate or static objects . 13 Installing and configuring Designer . 13 Configuring JVM settings . 13 Looking at the workspace . 14 About editors . 14 About palettes . 17 Customizing the workspace . .23 Managing library palettes . 28 Steps to creating a form design . 33 Basic steps to creating a form design . 33 Plan the form design . 33 Create the form design .
    [Show full text]
  • Mapping Guis to Auditory Interfaces
    Mapping GUIs to Auditory Interfaces Elizabeth D. Mynatt and W. Keith Edwards Graphics, Visualization, and Usability Center College of Computing Georgia Institute of Technology Atlanta, GA 3032-0280 [email protected], [email protected] ABSTRACT little trouble accessing standard ASCII terminals. The line- This paper describes work to provide mappings between X- oriented textual output displayed on the screen was stored in based graphical interfaces and auditory interfaces. In our the computer’s framebuffer. An access program could sim- system, dubbed Mercator, this mapping is transparent to ply copy the contents of the framebuffer to a speech synthe- applications. The primary motivation for this work is to sizer, a Braille terminal or a Braille printer. Conversely, the provide accessibility to graphical applications for users who contents of the framebuffer for a graphical interface are sim- are blind or visually impaired. We describe the design of an ple pixel values. To provide access to GUIs, it is necessary to auditory interface which simulates many of the features of intercept application output before it reaches the screen. This graphical interfaces. We then describe the architecture we intercepted application output becomes the basis for an off- have built to model and transform graphical interfaces. screen model of the application interface.The information in Finally, we conclude with some indications of future the off-screen model is then used to create alternative, acces- research for improving our translation mechanisms and for sible interfaces. creating an auditory “desktop” environment. The goal of this work, called the Mercator1 Project, is to pro- KEYWORDS: Auditory interfaces, GUIs, X, visual impair- vide transparent access to X Windows applications for com- ment, multimodal interfaces.
    [Show full text]
  • Automatically Generating High-Quality User Interfaces for Appliances
    Automatically Generating High-Quality User Interfaces for Appliances Jeffrey Nichols December 2006 CMU-HCII-06-109 Human Computer Interaction Institute School of Computer Science Carnegie Mellon University Pittsburgh, Pennsylvania 15213 Thesis Committee: Brad A. Myers, Chair Scott E. Hudson John Zimmerman Dan R. Olsen, Jr., Brigham Young University Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy Copyright © 2006 Jeffrey Nichols. All rights reserved. This research was supported in part by the National Science Foundation (through the author’s Graduate Re- search Fellowship and grants IIS-0117658 and IIS-0534349), Microsoft, General Motors, the Pittsburgh Digital Greenhouse, and Intel. Equipment supporting this research was generously donated by Mitsubishi Elec- tric Research Laboratories, VividLogic, Lantronix, Lutron, IBM Canada, Symbol Technologies, Hewlett- Packard, and Lucent. The views and conclusions contained herein are those of the author and should not be interpreted as necessarily representing the official policies or endorsements, either expressed or implied, of any sponsoring party or the U.S. Government. Keywords: Automatic interface generation, aggregate user interfaces, handheld computers, personal digital assistants, mobile phones, home theater, appliances, personal universal con- troller (PUC), user interface description languages (UIDLs), remote controls, multi-modal interfaces, speech recognition, Smart Templates, user interface consistency, personal consis- tency, familiarity ii Automatically Generating High-Quality User Interfaces for Appliances Jeffrey Nichols iii iv Abstract0B In this dissertation, I show that many appliance usability problems can be addressed by mov- ing the user interface from the appliance to a handheld device that the user is already carrying, such as a Personal Digital Assistant (PDA) or mobile phone.
    [Show full text]
  • Day One: Beginner's Guide to Learning Junos
    DAY ONE: BEGINNER’S GUIDE TO LEARNING JUNOS® The Juniper AmbAssADors Are A Diverse set of inDepenDent network engineers, ConsultAnts, AnD ArChiteCts who work in the fielD with Juniper technologies on A DAily bAsis. Their mission is to spreaD the worD About the power AnD sCAlAbility of Juniper’s network offerings. InDeeD, they Are responsible for over A Dozen ONE: DAY Day One books AnD Countless soCiAl meDiA AppeArAnCes, viDeos, AnD trAining sessions. But they hAve Al- DAY ONE: BEGINNER’S GUIDE TO ways wanteD to fill A mAjor gAp in the networking CAnnon AnD Create A true beginner’s guiDe to the most powerful networking OS in the worlD. AnD now they hAve Done it, the AmbAssADor wAy: hAnDs on, to the ® point, anD complete. It’s all here in the Beginner’s Guide to Learning Junos. LEARNING JUNOS BEGINNER’S GUIDE TO LEARING JUNOS LEARING TO GUIDE BEGINNER’S “Whether you are new to Juniper or not, there isn’t a more complete introduction to Junos available. I wish Nine this book was around when I started my network journey years ago. The Ambassador authors bring together so much knowledge and expert field experience that this book is a one-stop-shop to take you from beginner to Junos expert.” Melchior Aelmans, Lead Engineer Cloud Providers, Juniper Networks The Juniper Ambassadors “Nowadays there are many vendors offering similar services and its difficult to learn them all. What network show you how to stand up engineers need is a clear and easy-to-follow guide to assist them in their learning journey.
    [Show full text]
  • Enterprise Governance, Risk and Compliance Security Implementation Guide Release 8.6.6.1000 Part No
    Oracle® Enterprise Governance, Risk and Compliance Security Implementation Guide Release 8.6.6.1000 Part No. E69143-01 February 2016 Oracle Enterprise Governance, Risk and Compliance Security Implementation Guide Part No. E69143-01 Copyright © 2016 Oracle Corporation and/or its affiliates. All rights reserved. Primary Author: David Christie Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. The 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 software or related documentation 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]