DOCSLIB.ORG

June 28 2020 Linux Documentation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
June 28 2020 Linux Documentation Linux SAFR® Documentation Linux SAFR® Documentation Documentation Version = 2.010 Publish Date = June 5, 2020 Copyright © 2020 RealNetworks, Inc. All rights reserved. SAFR® is a trademark of RealNetworks, Inc. Patents pending. 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. 1 Contents 1 What’s New 5 2 SAFR Overview 6 3 SAFR System Requirements 9 4 Licensing 15 5 Getting Started with SAFR Platform on Linux 17 6 Camera Best Practices 20 7 Manage People in the Person Directory 28 8 Importing and Registering People 29 9 Image Quality Metrics Guidance 31 10 Actions Overview 35 11 Actions Relay Event Service (ARES) 37 12 SAFRActions.config 38 13 Large Scale Deployments 49 14 Database Redundancy 53 15 Object Storage Service Redundancy (CVOS) 58 16 SSL Certificate Installation 63 17 SAFR Support Tools and Scripts 67 18 SAFR Server Backup and Restore 69 19 Video Recognition Gateway (VIRGO) 70 20 VIRGO Installation Guide 73 21 VIRGO System Requirements 75 22 VIRGO Command Line Interface 76 23 Docker 81 24 Factory Configuration 84 25 GPU Support 89 26 Service Logging 92 27 Service Monitoring 94 28 Troubleshooting 96 29 Command & Control Protocol (COP) 99 2 30 COP Introduction 100 31 COP Status Delivery 102 32 COP Status Reply 111 33 COP Image Capture 135 34 COP Tracking Result Capture 136 35 COP Logging 141 36 COP Software Updates 143 37 COP Errors 146 38 COP State Update Algorithms 152 39 COP Examples 157 40 Connect a Face Recognition Panel 162 41 Connect a Registration Kiosk 164 42 Customize a Registration Kiosk 166 43 Configure a Mobile Device into Locked Mode 168 44 Install SAFR Beam 178 45 Mobile Account Preferences 179 46 Mobile Detection Preferences 180 47 Mobile Recognition Preferences 181 48 Mobile Events Preferences 182 49 Mobile User Interface Preferences 183 50 Web Console 184 51 Status Page 185 52 People Page 191 53 Events Page 192 54 Video Feeds Pages 193 55 Reports Page 195 56 Traffic Dashboard 196 57 Queue Dashboard 199 58 Attendance Dashboard 201 59 Traversal Dashboard 203 3 60 Traffic Report 206 61 Face Detection-Person Detection Tie-In 208 62 June 2020 Release Notes 209 63 May 2020 Release Notes 210 64 April 2020 Release Notes 211 65 March 2020 Release Notes 213 66 January 2020 Release Notes 216 67 December 2019 Release Notes 218 68 November 2019 Release Notes 221 69 September 2019 Release Notes 224 70 August 2019 Release Notes 227 4 1 What’s New The following features are new in the June 2020 SAFR release: • Added new options for conflict resolution when importing facial images. 5 2 SAFR Overview SAFR is a facial recognition system that integrates cameras, door locks, and alert systems with face recognition technology to enhance access control and security. It runs on a variety of operating systems, including Windows, macOS, Linux, iOS, and Android. 2.1 SAFR Components SAFR primarily consists of the following components: • SAFR Server: Available for Windows, macOS, and Linux. The SAFR Server installation contains the recognition engine, event server, several databases, and the Web Console. The databases contain stored enrolled face images, the identity information for the stored faces, and recognition events that have been generated by the SAFR system. The SAFR Server runs as several background services that automatically start on system reboot and are kept active by the operating system. They must be running at all times for the system to be operational. All other SAFR components must connect to a SAFR Server, although if you’re doing a cloud deployment you’ll be connecting to a SAFR Server in the cloud that RealNetworks maintains. • Desktop client: Available for Windows and macOS. The Desktop client is one of the primary ways that administrators and operators can interact with the SAFR system. As such, the client can be used to enable camera connectivity, monitor video camera feeds, register users, view recognition events, and more. • Mobile client: Available for Android and iOS. The Mobile client converts a mobile device into a registration kiosk or a recognition panel. Registration kiosks allow people to self-register their face into the Identity Database so they can be approved for access or granted other privileges. Recognition panels enable the mobile device to scan the faces of people that walk by and to compare those faces against faces in the Identity Database. Mobile devices set up as recognition panels can also provide visual or audio feedback to the person viewing the mobile device based on actions that a SAFR administrator has configured. • VIRGO: Available as a standalone download for macOS and Linux. It’s also available as part of the SAFR Desktop, SAFR Edge, and SAFR Platform download packages for Windows, macOS, and Linux. The Video Recognition Gateway (VIRGO) is a daemon system which receives video feeds from one or more cameras and recognizes and tracks faces in those video streams in real time. It generates tracking events and sends those events to an event server. The VIRGO daemon can be controlled either by the command line tool or through the Video Recognition Gateway Administration (VIRGA) command & control server. • Web Console: Available on all platforms. The Web Console provides administrators and operators web-based access to the SAFR system. As such, the Web Console can be used to generate analytical reports, monitor video camera feeds, register users, view recognition events, and more. • ARES: Available as a standalone download for all platforms. Actions Relay Event Service (ARES) is a cross-platform Java application that acts as the event listener that dispatches configured actions in response to events. ARES can provide replies on any event handled by the client that originates an event and is normally installed as a service when either SAFR Platform or SAFR Edge are installed. It is constantly active and is automatically started by the operating system on power-up. • SAFR Actions: SAFR Actions is a GUI that facilitates configuring SAFRActions.config. SAFRAc- tions.config is the file that defines all the defined actions for your SAFR System, as well as a couple fields that are used to connect ARES (and SAFR Actions) to your primary SAFR Server, whether that server is local or in the cloud. See Actions for more information about actions in SAFR. 6 In addition to the SAFR components listed above, SAFR also relies on a couple additional non-SAFR components: • IP Cameras: As you might expect, Internet Protocol (IP) cameras are absolutely integral to SAFR. Both the Desktop client and VIRGO automatically detect integrated, USB, and Open Network Video Interface Forum (ONVIF) IP cameras. If an IP camera does not support ONVIF or doesn’t have ONVIF enabled, you can still manually add it to the SAFR system as described here. • Physical access control devices: Door locks, electronic gates, etc. can all be used by SAFR to grant or deny access to people, depending on whether or not they’re identified as having the proper authorization. • Notification systems: Email can be used to discretely notify specified people of various events, while general alarms can be used to alert everybody in the vicinity when unauthorized people attempt to force entry. • Additional external peripherals: Any device that can be controlled by a computer language or protocol can be incorporated into the SAFR system. 2.2 Available Download Packages The following download packages are available on the SAFR Download Portal: • SAFR Platform: Available on Windows, macOS, and Linux. The SAFR Platform installs everything you need to set up a local deployment of SAFR. This downlaod package enables a locally deployed system to be easily deployed on a single computer and afterwards expanded to additional computers as needed. See Getting Started with SAFR Platform on Linux for more information. • SAFR Desktop: Available on Windows and macOS. Installs the Desktop client and one of the VMS extensions. Windows has an additional download variant called SAFR Desktop Lite which has fewer features and lower system requirements. • SAFR Edge: Available on Windows and macOS. SAFR Edge installs the Desktop client as well as SAFR Actions, a programmable interface to create and manage responses to event triggers. For example, you can unlock a door, turn on a light, send an alert, and so on. • SAFR Mobile: Available on Android and iOS. Installs the Mobile client. When you download SAFR Mobile for Android, you’re also offered the SAFR Beam download. SAFR Beam allows you to enable the more secure Lock Task Mode on your Android device. If you don’t install SAFR Beam, then Android devices can only enable the less secure Screen Pinning Mode. See Configure Devices into Locked Mode for more information. • Actions Relay Event Service (ARES): Available on all platforms. Installs ARES. • Video Recognition Gateway (VIRGO): Available on Linux and macOS. Installs VIRGO. 2.3 Deployment Types There are two types of SAFR deployment: cloud and local. Each deployment type requires its own account type; a cloud deployment requires a SAFR Cloud Account, while a local deployment requires a SAFR Local Account. Contact your SAFR Account Manager to obtain either type of account.
Load more

Recommended publications
  • Diseño E Implementación De Actualizaciones Over the Air (OTA) Para Redes De Sensores Inalámbricas
    Diseño e implementación de actualizaciones Over The Air (OTA) para redes de sensores inalámbricas David García Fernández GRADO EN INGENIERÍA INFORMÁTICA FACULTAD DE INFORMÁTICA UNIVERSIDAD COMPLUTENSE DE MADRID Trabajo Fin de Grado en Ingeniería Informática Curso 2018-2019 Director: Joaquín Recas Resumen en castellano El objeto de este trabajo es el estudio de la viabilidad de las actualizaciones de firmware Over The Air (OTA) utilizando una red LPWAN, en concreto LoRaWAN. Dar soporte para actualizaciones de firmware OTA a día de hoy resulta fundamental y más todavía cuando estos nodos se encuentran en lugares remotos o sitios donde el acceso es muy limitado o peligroso. Tener implementada la funcionalidad para actualizaciones vía OTA permite corregir errores o añadir nuevas funcionalidades a distancia. Uno de los objetivos prioritarios consiste en que la misma actualización pueda llegar a un conjunto de nodos a la vez evitando tener que actualizar los nodos uno por uno, ya que esto supondría el envío de gran cantidad de información duplicada. Para llevar a cabo esta tarea, se ha realizado un estudio en profundidad sobre las características y el funcionamiento de la red LoRaWAN teniendo en cuenta que las redes LPWAN en general dificultan llevar a cabo este tipo de actualizaciones debido a sus conocidas limitaciones en cuanto a tamaño de payload y elevada latencia. Finalmente, este trabajo demuestra la viabilidad de las OTA mediante la aplicación de parches de actualización de firmware a conjuntos de nodos. Palabras clave OTA Over The Air Pycom Lopy STM32L475 LoRa LoRaWAN Bajo consumo Firmware OTA LoRa Server Red de sensores Abstract The aim of this work is the study of the feasibility of firmware updates Over The Air (OTA) using an LPWAN network, specifically LoRaWAN.
    [Show full text]
  • July 20 2020 Linux Documentation
    Linux SAFR® Documentation Linux SAFR® Documentation Documentation Version = 2.016 Publish Date = July 20, 2020 Copyright © 2020 RealNetworks, Inc. All rights reserved. SAFR® is a trademark of RealNetworks, Inc. Patents pending. 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. 1 Contents 1 What’s New 5 2 SAFR Overview 6 3 SAFR System Requirements 9 4 Licensing 15 5 Getting Started with SAFR Platform on Linux 17 6 Camera Best Practices 20 7 Manage People in the Person Directory 28 8 Importing and Registering People 29 9 Image Quality Metrics Guidance 31 10 Actions Overview 35 11 Actions Relay Event Service (ARES) 37 12 SAFRActions.config 38 13 Large Scale Deployments 49 14 Database Redundancy 53 15 Object Storage Service Redundancy (CVOS) 58 16 SSL Certificate Installation 63 17 SAFR Support Tools and Scripts 67 18 SAFR Server Backup and Restore 69 19 SAFR Platform Command Line Install
    [Show full text]
  • Cybersecurity of Firmware Updates DISCLAIMER
    DOT HS 812 807 October 2020 Cybersecurity of Firmware Updates DISCLAIMER This publication is distributed by the U.S. Department of Transportation, National Highway Traffic Safety Administration, in the interest of information exchange. The opinions, findings, and conclusions expressed in this publication are those of the authors and not necessarily those of the Department of Transportation or the National Highway Traffic Safety Administration. The United States Government assumes no liability for its contents or use thereof. If trade or manufacturers’ names are mentioned, it is only because they are considered essential to the object of the publication and should not be construed as an endorsement. The United States Government does not endorse products or manufacturers. Suggested APA Format Citation: Bielawski, R., Gaynier, R., Ma, D., Lauzon, S., & Weimerskirch, A. (2020, October). Cybersecurity of Firmware Updates (Report No. DOT HS 812 807). National Highway Traffic Safety Administration. Technical Report Documentation Page 1. Report No. 2. Government Accession No. 3. Recipient's Catalog No. DOT HS 812 807 4. Title and Subtitle 5. Report Date Cybersecurity of Firmware Updates October 2020 6. Performing Organization Code 7. Authors 8. Performing Organization Report No. Russ Bielawski, Ron Gaynier, Dr. Di Ma, Sam Lauzon, and Dr. André Weimerskirch 9. Performing Organization Name and Address 10. Work Unit No. (TRAIS) Transportation Research Institute 11. Contract or Grant No. University of Michigan (Ann Arbor, MI) DTNH22-15-R-00104 Vehicle University of Michigan-Dearborn Electronics Systems Safety IDIQ Volkswagen Group of America (Herndon, VA) 12. Sponsoring Agency Name and Address 13. Type of Report and Period Covered National Highway Traffic Safety Administration Final Report 1200 New Jersey Avenue, SE 14.
    [Show full text]
  • MBS Macextras Plugin.Pdf
    MBS MacExtras Plugin Documentation Christian Schmitz September 6, 2021 2 0.1 Introduction This is the PDF version of the documentation for the Xojo Plug-in from Monkeybread Software Germany. Plugin part: MBS MacExtras Plugin 0.2 Content • 1 List of all topics 3 • 2 List of all classes 29 • 3 List of all controls 31 • 4 List of all modules 33 • 5 List of all global methods 35 • 6 All items in this plugin 37 • 18 List of Questions in the FAQ 231 • 19 The FAQ 241 Chapter 1 List of Topics • 7 Apple Remote 39 – 7.1.1 class AppleRemoteMBS 39 ∗ 7.1.7 startListening 40 ∗ 7.1.8 stopListening 40 ∗ 7.1.10 ClickCountEnabledButtons as Integer 40 ∗ 7.1.11 ClickCountingEnabled as Boolean 40 ∗ 7.1.12 Handle as Integer 41 ∗ 7.1.13 ListeningOnAppActivate as Boolean 41 ∗ 7.1.14 ListeningToRemote as boolean 41 ∗ 7.1.15 MaximumClickCountTimeDifference as Double 41 ∗ 7.1.16 OpenInExclusiveMode as boolean 42 ∗ 7.1.17 ProcessesBacklog as Boolean 42 ∗ 7.1.18 RemoteAvailable as boolean 42 ∗ 7.1.19 remoteId as Integer 42 ∗ 7.1.20 SimulatesPlusMinusHold as Boolean 42 ∗ 7.1.22 ButtonPressed(ButtonID as Integer, PressedDown as boolean, clickCount as Integer) 43 ∗ 7.1.24 kRemoteButtonFullscreen2009 = 32768 43 ∗ 7.1.25 kRemoteButtonLeft = 64 43 ∗ 7.1.26 kRemoteButtonLeftHold = 256 43 ∗ 7.1.27 kRemoteButtonMenu = 8 44 ∗ 7.1.28 kRemoteButtonMenuHold = 512 44 ∗ 7.1.29 kRemoteButtonPlay = 16 44 ∗ 7.1.30 kRemoteButtonPlay2009 = 16384 44 ∗ 7.1.31 kRemoteButtonPlaySleep = 1024 44 ∗ 7.1.32 kRemoteButtonRight = 32 44 ∗ 7.1.33 kRemoteButtonRightHold = 128 45 3 4 CHAPTER 1.
    [Show full text]
  • MBS Cocoaextras Plugin Documentation
    MBS CocoaExtras Plugin Documentation Christian Schmitz July 16, 2017 2 0.1 Introduction This is the PDF version of the documentation for the Xojo (Real Studio) Plug-in from Monkeybread Software Germany. Plugin part: MBS CocoaExtras Plugin 0.2 Content • 1 List of all topics 3 • 2 List of all classes 31 • 3 List of all controls 33 • 4 List of all modules 35 • 5 List of all global methods 37 • 6 All items in this plugin 39 • 20 List of Questions in the FAQ 223 • 21 The FAQ 233 Chapter 1 List of Topics • 6 Apple Remote 39 { 6.1.1 class AppleRemoteMBS 39 ∗ 6.1.3 startListening 39 ∗ 6.1.4 stopListening 39 ∗ 6.1.6 ClickCountEnabledButtons as Integer 40 ∗ 6.1.7 ClickCountingEnabled as Boolean 40 ∗ 6.1.8 Handle as Integer 40 ∗ 6.1.9 ListeningOnAppActivate as Boolean 40 ∗ 6.1.10 ListeningToRemote as boolean 41 ∗ 6.1.11 MaximumClickCountTimeDifference as Double 41 ∗ 6.1.12 OpenInExclusiveMode as boolean 41 ∗ 6.1.13 ProcessesBacklog as Boolean 41 ∗ 6.1.14 RemoteAvailable as boolean 41 ∗ 6.1.15 remoteId as Integer 42 ∗ 6.1.16 SimulatesPlusMinusHold as Boolean 42 ∗ 6.1.18 ButtonPressed(ButtonID as Integer, PressedDown as boolean, clickCount as Integer) 42 ∗ 6.1.20 kRemoteButtonFullscreen2009 = 32768 42 ∗ 6.1.21 kRemoteButtonLeft = 64 43 ∗ 6.1.22 kRemoteButtonLeftHold = 256 43 ∗ 6.1.23 kRemoteButtonMenu = 8 43 ∗ 6.1.24 kRemoteButtonMenuHold = 512 43 ∗ 6.1.25 kRemoteButtonPlay = 16 43 ∗ 6.1.26 kRemoteButtonPlay2009 = 16384 43 ∗ 6.1.27 kRemoteButtonPlaySleep = 1024 43 ∗ 6.1.28 kRemoteButtonRight = 32 43 ∗ 6.1.29 kRemoteButtonRightHold = 128 44 3 4 CHAPTER 1.
    [Show full text]
  • Cybersecurity of Firmware Updates DISCLAIMER
    DOT HS 812 807 October 2020 Cybersecurity of Firmware Updates DISCLAIMER This publication is distributed by the U.S. Department of Transportation, National Highway Traffic Safety Administration, in the interest of information exchange. The opinions, findings, and conclusions expressed in this publication are those of the authors and not necessarily those of the Department of Transportation or the National Highway Traffic Safety Administration. The United States Government assumes no liability for its contents or use thereof. If trade or manufacturers’ names are mentioned, it is only because they are considered essential to the object of the publication and should not be construed as an endorsement. The United States Government does not endorse products or manufacturers. Suggested APA Format Citation: Bielawski, R., Gaynier, R., Ma, D., Lauzon, S., & Weimerskirch, A. (2020, October). Cybersecurity of Firmware Updates (Report No. DOT HS 812 807). National Highway Traffic Safety Administration. Technical Report Documentation Page 1. Report No. 2. Government Accession No. 3. Recipient's Catalog No. DOT HS 812 807 4. Title and Subtitle 5. Report Date Cybersecurity of Firmware Updates October 2020 6. Performing Organization Code 7. Authors 8. Performing Organization Report No. Russ Bielawski, Ron Gaynier, Dr. Di Ma, Sam Lauzon, and Dr. André Weimerskirch 9. Performing Organization Name and Address 10. Work Unit No. (TRAIS) Transportation Research Institute 11. Contract or Grant No. University of Michigan (Ann Arbor, MI) DTNH22-15-R-00104 Vehicle University of Michigan-Dearborn Electronics Systems Safety IDIQ Volkswagen Group of America (Herndon, VA) 12. Sponsoring Agency Name and Address 13. Type of Report and Period Covered National Highway Traffic Safety Administration Final Report 1200 New Jersey Avenue, SE 14.
    [Show full text]
  • May 12 2020 Linux Documentation
    Linux SAFR® Documentation Linux SAFR® Documentation Documentation Version = 2.007 Publish Date = April 12, 2020 Copyright © 2020 RealNetworks, Inc. All rights reserved. SAFR® is a trademark of RealNetworks, Inc. Patents pending. 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. 1 Contents 1 What’s New 5 2 SAFR Overview 6 3 SAFR System Requirements 9 4 Licensing 15 5 Getting Started with SAFR Platform on Linux 17 6 Manage People in the Person Directory 20 7 Importing and Registering People 21 8 Image Quality Metrics Guidance 23 9 Actions Overview 27 10 Actions Relay Event Service (ARES) 29 11 SAFRActions.config 30 12 Large Scale Deployments 41 13 Database Redundancy 45 14 Object Storage Service Redundancy (CVOS) 50 15 SSL Certificate Installation 55 16 SAFR Support Tools and Scripts 59 17 SAFR Server Backup and Restore 61 18 Video Recognition Gateway (VIRGO) 62 19 VIRGO Installation
    [Show full text]
  • Securing Software Updates for Automobiles∗
    Uptane: Securing Software Updates for Automobiles∗ Trishank Karthik Akan Brown Sebastien Awwad Kuppusamy NYU Tandon School of NYU Tandon School of NYU Tandon School of Engineering Engineering Engineering [email protected] [email protected] [email protected] Damon McCoy Russ Bielawski Cameron Mott NYU Tandon School of University of Michigan Southwest Research Institute Engineering [email protected] [email protected] [email protected] Sam Lauzon André Weimerskirchy Justin Cappos University of Michigan University of Michigan, NYU Tandon School of [email protected] Lear Corporation Engineering [email protected] [email protected] ABSTRACT 26,27,29–31,33–37,39]. In one such case, a compromised Source- Forge mirror distributed a malicious version of phpMyAdmin, a Software update systems for automobiles can deliver significant popular database administration software [33]. The modified ver- benefits, but, if not implemented carefully, they could potentially sion allowed attackers to gain system access and remotely execute incur serious security vulnerabilities. Previous solutions for secur- PHP code on servers that installed the software. ing software updates consider standard attacks and deploy widely understood security mechanisms, such as digital signatures for the Automobiles introduced software updates more than a decade software updates, and hardware security modules (HSM) to sign ago, and today many electronic components in a vehicle can be up- software updates. However, no existing solution considers more dated by an automotive technician with a proper tool. However, advanced security objectives, such as resilience against a reposi- available update mechanisms played a crucial role in a variety of tory compromise, or freeze attacks to the vehicle’s update mech- published automotive related hacks, such as the recent study by anism, or a compromise at a supplier’s site.
    [Show full text]
  • Diffusion 6.6 User Guide Contents
    Diffusion 6.6 User Guide Contents List of Figures..............................................................................................10 List of Tables............................................................................................... 12 Part I: Welcome.......................................................................... 15 Introducing Diffusion................................................................................................. 16 Introducing topics and data................................................................................................ 16 Introducing sessions.............................................................................................................20 What's new in Diffusion 6.6?...................................................................................... 23 Part II: Quick Start Guide............................................................ 26 Part III: Design Guide.................................................................. 27 Support.....................................................................................................................28 System requirements for the Diffusion server....................................................................28 Platform support for the Diffusion API libraries.................................................................31 Feature support in the Diffusion API...................................................................................33 License types.........................................................................................................................38
    [Show full text]
  • Common Installation Guide CARAB 2.0 SPS1 Content
    Installation Guide CUSTOMER SAP Customer Activity Repository retail applications bundle Document Version: 1.0.0 – 2017-02-27 Common Installation Guide CARAB 2.0 SPS1 Content 1 Introduction.................................................................. 5 1.1 About this Document.............................................................5 1.2 Integration with SAP Fashion Management.............................................6 1.3 SAP Notes for the Installation.......................................................7 1.4 Information Available on SAP Help Portal..............................................13 1.5 Naming Conventions............................................................15 2 Planning.................................................................... 18 2.1 Overall System Planning..........................................................18 2.2 System Landscape Variants.......................................................21 SAP Allocation Management for Retail............................................. 21 SAP Assortment Planning for Retail...............................................22 SAP Customer Activity Repository................................................26 SAP Merchandise Planning for Retail..............................................30 3 Prerequisites.................................................................33 4 Preparation..................................................................41 4.1 SAP Assortment Planning for Retail..................................................41 Verify SAP
    [Show full text]
  • Apache Solr Reference Guide Covering Apache Solr
    TM Apache Solr Reference Guide Covering Apache Solr 5.5 Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Apache and the Apache feather logo are trademarks of The Apache Software Foundation. Apache Lucene, Apache Solr and their respective logos are trademarks of the Apache Software Foundation. Please see the Apache Trademark Policy for more information. Fonts used in the Apache Solr Reference Guide include Raleway, licensed under the SIL Open Font License, 1.1. Apache Solr Reference Guide This reference guide describes Apache Solr, the open source solution for search. You can download Apache Solr from the Solr website at http://lucene.apache.org/solr/. This Guide contains the following sections: Getting Started: This section guides you through the installation and setup of Solr. Using the Solr Administration User Interface: This section introduces the Solr Web-based user interface. From your browser you can view configuration files, submit queries, view logfile settings and Java environment settings, and monitor and control distributed configurations.
    [Show full text]
  • Application Hosting Configuration Guide for Cisco ASR 9000 Series Routers
    Application Hosting Configuration Guide for Cisco ASR 9000 Series Routers First Published: 2016-11-01 Last Modified: 2021-07-30 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]