DOCSLIB.ORG

Administering Evergreen Through the Command Line Documentation Interest Group Administering Evergreen Through the Command Line Documentation Interest Group

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Administering Evergreen Through the Command Line Documentation Interest Group Administering Evergreen Through the Command Line Documentation Interest Group Administering Evergreen through the Command Line Documentation Interest Group Administering Evergreen through the Command Line Documentation Interest Group Report errors in this documentation using Launchpad. Table of Contents I. Introduction ............................................................................................................................................................. 7 1. About This Documentation ............................................................................................................................... 9 2. About Evergreen ............................................................................................................................................ 10 II. Installing Evergreen ............................................................................................................................................... 11 3. System Requirements ..................................................................................................................................... 14 Server Minimum Requirements .................................................................................................................... 14 Web Client Requirements ........................................................................................................................... 14 Staff Client Requirements ........................................................................................................................... 14 4. Installing the Evergreen server ......................................................................................................................... 15 Preamble: referenced user accounts .............................................................................................................. 15 Preamble: developer instructions .................................................................................................................. 15 Installing prerequisites ................................................................................................................................ 16 Extra steps for web staff client .................................................................................................................... 17 Configuration and compilation instructions .................................................................................................... 18 Installation instructions ............................................................................................................................... 18 Change ownership of the Evergreen files ....................................................................................................... 18 Run ldconfig ............................................................................................................................................. 18 Additional Instructions for Developers .......................................................................................................... 18 Configure the Apache Web server ................................................................................................................ 19 Configure OpenSRF for the Evergreen application .......................................................................................... 21 Configure action triggers for the Evergreen application .................................................................................... 21 Creating the Evergreen database .................................................................................................................. 21 Starting Evergreen ..................................................................................................................................... 23 Testing connections to Evergreen ................................................................................................................. 24 Getting help .............................................................................................................................................. 24 License .................................................................................................................................................... 25 5. Upgrading the Evergreen Server ....................................................................................................................... 26 Software Prerequisites ................................................................................................................................ 26 Upgrade the Evergreen code ........................................................................................................................ 26 Upgrade the Evergreen database schema ....................................................................................................... 28 Restart Evergreen and Test ......................................................................................................................... 31 Review Release Notes ................................................................................................................................ 31 6. Setting Up EDI Acquisitions ........................................................................................................................... 32 Introduction .............................................................................................................................................. 32 Installation ................................................................................................................................................ 32 Configuration ............................................................................................................................................ 33 Troubleshooting ........................................................................................................................................ 34 7. Migrating from a legacy system ....................................................................................................................... 36 Introduction .............................................................................................................................................. 36 Making electronic resources visible in the catalog ........................................................................................... 36 Migrating your bibliographic records ............................................................................................................ 37 Migrating your call numbers, copies, and parts ............................................................................................... 38 Migrating Patron Data ................................................................................................................................ 41 III. Individual Evergreen Components ........................................................................................................................... 45 8. Easing gently into OpenSRF ............................................................................................................................ 47 Abstract ................................................................................................................................................... 47 Introducing OpenSRF ................................................................................................................................. 47 Enough jibber-jabber: writing an OpenSRF service ......................................................................................... 52 Getting under the covers with OpenSRF ........................................................................................................ 64 Evergreen-specific OpenSRF services ........................................................................................................... 67 Evergreen after one year: reflections on OpenSRF .......................................................................................... 68 Administering Evergreen through the Command Line 3 Summary .................................................................................................................................................. 70 Appendix: Python client ............................................................................................................................. 70 9. Support Scripts .............................................................................................................................................. 72 marc_export: Exporting Bibliographic Records into MARC files ....................................................................... 73 Importing Authority Records from Command Line ......................................................................................... 74 Juvenile-to-adult batch script ....................................................................................................................... 75 MARC Stream Importer ............................................................................................................................. 75 Processing Action Triggers ......................................................................................................................... 75 10. Daemons and services ................................................................................................................................... 77 Starting and Stopping the Reporter Daemon ..................................................................................................
Load more

Recommended publications
  • Fully Eliminated the Language Barrier and Enable Ease of Communication Through This Application
    IOSR Journal of Computer Engineering (IOSR-JCE) e-ISSN: 2278-0661, p- ISSN: 2278-8727Volume 16, Issue 2, Ver. XI (Mar-Apr. 2014), PP 113-119 www.iosrjournals.org Alltalk™- A Windows Phone Messenger with Cross Language Communication Shruti Shetye1, Akhil Abraham2, Royston Pinto3, Sonali Vaidya4 1(BE-IT Student, Information Technology, St. FrancisInstitute of Technology, India) 2(BE-IT Student, Information Technology, St. Francis Institute of Technology, India) 3(BE-IT Student, Information Technology, St. Francis Institute of Technology, India 4(Lecturer, Information Technology, St. Francis Institute of Technology, India) __________________________________________________________________________________ Abstract:In day to day life, messengers or chatting applications provide facility for instant messaging over the internet. Exchange of messages takes place in universally used languages like English, French, etc. where both the users know how to communicate in a common language. Thus chatting on mobile phones is a luxury when both the parties involved know a common language. Hence we have implemented ALLTALK™ which is a Windows 8 phone based chatting application which makes cross language communication possible using mobile programming and networking technology.This application will enable the communication between two persons irrespective of the language each user wishes to use individually. The various modes of communication available in this messenger are through text and voice. Due to the best processing power provided among the available smartphones and high battery life we choose to work on windows 8 platform. Thus we have successfully eliminated the language barrier and enable ease of communication through this application. Keywords: Cross Language communication, instant messenger, socket connection, translator,Windows phone app.
    [Show full text]
  • TLS in the Wild: an Internet-Wide Analysis of TLS-Based Protocols for Electronic Communication
    TLS in the wild: An Internet-wide analysis of TLS-based protocols for electronic communication Ralph Holz∗, Johanna Amannz, Olivier Mehaniy, Matthias Wachsx, Mohamed Ali Kaafary ∗University of Sydney, Australia, Email: [email protected] yData61/CSIRO, Sydney, Australia, Email: [email protected] zICSI, Berkeley, USA, Email: [email protected] xTechnical University of Munich, Germany, Email: [email protected] This is a preprint of the camera-ready version to appear at NDSS 2016. Last update: 19 Dec 2015. Abstract—Email and chat still constitute the majority of in 2018 [11]. As for chat, the most widely used standard- electronic communication on the Internet. The standardisation based networks are IRC group chats and the XMPP instant and acceptance of protocols such as SMTP, IMAP, POP3, XMPP, messaging and multi-user conferencing network. and IRC has allowed to deploy servers for email and chat in a decentralised and interoperable fashion. These protocols can be In their early days, email protocols such as SMTP, POP3, secured by providing encryption with TLS—directly or via the and IMAP were designed with no special focus on security. STARTTLS extension. X.509 PKIs and ad hoc methods can be In particular, authentication in SMTP was introduced a while leveraged to authenticate communication peers. However, secure after the protocol’s standardisation, initially as a way to configuration is not straight-forward and many combinations fight spam. User agents started to move towards encryption of encryption and authentication mechanisms lead to insecure deployments and potentially compromise of data in transit. In and authenticated connections gradually, using the then-new this paper, we present the largest study to date that investigates SSL 3 and later the TLS protocols to protect the transport the security of our email and chat infrastructures.
    [Show full text]
  • The Use and Application of Open Source Integrated Library System in Academic Libraries in Nigeria: Koha Example
    University of Nebraska - Lincoln DigitalCommons@University of Nebraska - Lincoln Library Philosophy and Practice (e-journal) Libraries at University of Nebraska-Lincoln 2015 The seU and Application of Open Source Integrated Library System in Academic Libraries in Nigeria: Koha Example Emeka C. Uzomba Mr. Federal University,Oye-Ekiti, Ekiti State, [email protected] OLUWATOFUNMI JESUDUNNI OYEBOLA Mrs. Federal University Oye-Ekiti, Nigeria, [email protected] ANTHONY CHUKWUMA IZUCHUKWU Mr. University of Nigeria, Nsukka, [email protected] Follow this and additional works at: http://digitalcommons.unl.edu/libphilprac Part of the Educational Assessment, Evaluation, and Research Commons, and the Library and Information Science Commons Uzomba, Emeka C. Mr.; OYEBOLA, OLUWATOFUNMI JESUDUNNI Mrs.; and IZUCHUKWU, ANTHONY CHUKWUMA Mr., "The sU e and Application of Open Source Integrated Library System in Academic Libraries in Nigeria: Koha Example" (2015). Library Philosophy and Practice (e-journal). 1250. http://digitalcommons.unl.edu/libphilprac/1250 THE USE AND APPLICATION OF OPEN SOURCE INTEGRATED LIBRARY SYSTEM IN ACADEMIC LIBRARIES IN NIGERIA: KOHA EXAMPLE BY EMEKA CHRISTIAN UZOMBA Federal University Oye-Ekiti (Corresponding Author) Phone: +2348036996747 P.M.B.2273 Oye-Ekiti, Ekiti State, Nigeria. [email protected] , [email protected] , OLUWATOFUNMI JESUDUNNI OYEBOLA Federal University Oye-Ekiti (Co-Author) Phone: +2348030617819 P.M.B.2273 Oye-Ekiti, Ekiti State, Nigeria. [email protected] , [email protected] ANTHONY CHUKWUMA IZUCHUKWU Department of Library and Information Science, University of Nigeria, Nsukka (Co-Author) Phone: +2348067699821 [email protected] ABSTRACT This study examined the use of open source integrated library system in academic libraries in Nigeria, with the aim of highlighting the capabilities and potentials of open source software (Koha) and its practical importance to academic libraries across the globe.
    [Show full text]
  • Open Source Library Management System Software: a Review
    World Academy of Science, Engineering and Technology International Journal of Computer and Systems Engineering Vol:5, No:5, 2011 Open Source Library Management System Software: A Review Sangsuree Vasupongayya, Kittisak Keawneam, Kittipong Sengloilaun, Patt Emmawat materials), cataloging (i.e., classifying and indexing of Abstract—Library management systems are commonly used in materials), circulation (i.e., lending and receiving of materials) all educational related institutes. Many commercial products are and serials management (i.e., managing magazine and available. However, many institutions may not be able to afford the newspaper information. The second component is an cost of using commercial products. Therefore, an alternative solution interlibrary load management system. Because a library may in such situations would be open source software. This paper is focusing on reviewing open source library management system not have a hold of all materials required, an interlibrary loan is packages currently available. The review will focus on the abilities to a way for its patron to request such materials from other perform four basic components which are traditional services, libraries. The last component is a system to manage electronic interlibrary load management, managing electronic materials and materials and digital media. basic common management system such as security, alert system and In addition to the above three main components, a library statistical reports. In addition, environment, basic requirement and management system software package must contain a supporting aspects of each open source package are also mentioned. commonly shared components such as a user account management feature, a security component, an alert system Keywords— open source, library management, review.
    [Show full text]
  • Software Evolution Objectives
    Software evolution Objectives To explain why change is inevitable if software systems are to remain useful To discuss software maintenance and maintenance cost factors To describe the processes involved in software evolution To discuss an approach to assessing evolution strategies for legacy systems Topics covered Program evolution dynamics Software maintenance Evolution processes Legacy system evolution Software change Software change is inevitable New requirements emerge when the software is used The business environment changes Errors must be repaired New computers and equipment is added to the system The performance or reliability of the system may have to be improved A key problem for organisations is implementing and managing change to their existing software systems Importance of evolution Organisations have huge investments in their software systems - they are critical business assets To maintain the value of these assets to the business, they must be changed and updated The majority of the software budget in large companies is devoted to evolving existing software rather than developing new software Spiral model of evolution Program evolution dynamics Program evolution dynamics is the study of the processes of system change After major empirical studies, Lehman and Belady proposed that there were a number of ‘laws’ which applied to all systems as they evolved There are sensible observations rather than laws. They are applicable to large systems developed by large organisations. Perhaps less applicable in other cases Lehman’s laws Law Description Continuing change A program that is used in a real-world environment necessarily must change or become progressively less useful in that environment. Increasing complexity As an evolving program changes, its structure tends to become more complex.
    [Show full text]
  • Software Evolution of Legacy Systems a Case Study of Soft-Migration
    Software Evolution of Legacy Systems A Case Study of Soft-migration Andreas Furnweger,¨ Martin Auer and Stefan Biffl Vienna University of Technology, Inst. of Software Technology and Interactive Systems, Vienna, Austria Keywords: Software Evolution, Migration, Legacy Systems. Abstract: Software ages. It does so in relation to surrounding software components: as those are updated and modern- ized, static software becomes evermore outdated relative to them. Such legacy systems are either tried to be kept alive, or they are updated themselves, e.g., by re-factoring or porting—they evolve. Both approaches carry risks as well as maintenance cost profiles. In this paper, we give an overview of software evolution types and drivers; we outline costs and benefits of various evolution approaches; and we present tools and frameworks to facilitate so-called “soft” migration approaches. Finally, we describe a case study of an actual platform migration, along with pitfalls and lessons learned. This paper thus aims to give software practitioners—both resource-allocating managers and choice-weighing engineers—a general framework with which to tackle soft- ware evolution and a specific evolution case study in a frequently-encountered Java-based setup. 1 INTRODUCTION tainability. We look into different aspects of software maintenance and show that the classic meaning of Software development is still a fast-changing environ- maintenance as some final development phase after ment, driven by new and evolving hardware, oper- software delivery is outdated—instead, it is best seen ating systems, frameworks, programming languages, as an ongoing effort. We also discuss program porta- and user interfaces. While this seemingly constant bility with a specific focus on porting source code.
    [Show full text]
  • A User Study of Off-The-Record Messaging
    A User Study of Off-the-Record Messaging Ryan Stedman Kayo Yoshida Ian Goldberg University of Waterloo 200 University Avenue West Waterloo, Ontario, Canada N2L 3G1 {rstedman@cs, k2yoshid@math, iang@cs}.uwaterloo.ca ABSTRACT Keywords Instant messaging is a prevalent form of communication ac- OTR, Usable Security, Instant Messaging, Think Aloud ross the Internet, yet most instant messaging services pro- vide little security against eavesdroppers or impersonators. 1. INTRODUCTION There are a variety of existing systems that aim to solve There has been much research into creating privacy-en- this problem, but the one that provides the highest level hancing technologies, especially since the Internet has started of privacy is Off-the-Record Messaging (OTR), which aims to play an essential role in everyday life. However, not many to give instant messaging conversations the level of privacy of these technologies have seen widespread adoption. One available in a face-to-face conversation. In the most recent of the reasons for this is that many of these technologies redesign of OTR, as well as increasing the security of the provide insufficient usability [8]. protocol, one of the goals of the designers was to make OTR The process of evaluating and enhancing usability is im- easier to use, without users needing to understand details of portant in order for a privacy-enhancing technology to pro- computer security such as keys or fingerprints. vide benefits to ordinary users. Since privacy is not just To determine if this design goal has been met, we con- intended for computer scientists or cryptographers, but for ducted a user study of the OTR plugin for the Pidgin in- everyone, these technologies should be accessible to the gen- stant messaging client using the think aloud method.
    [Show full text]
  • A Technique for Legacy System Re-Engineering
    International Journal of Management and Applied Science, ISSN: 2394-7926 Volume-2, Issue-12, Special Issue-1, Dec.-2016 INFORMATION SYSTEM INTEGRATION: A TECHNIQUE FOR LEGACY SYSTEM RE-ENGINEERING EMOKPAE OSATOHANMWEN Dept of Computer Engineering, Institute of Opencast Mining and Technology. Agbor Road Benin City, Nigeria. E-mail:[email protected] Abstract - Many organizations are still faced with the problems of converting applications written in legacy compilers such as COBOL, PASCAL ANS FORTRAN etc. into internet compliant applications. This has become necessary because most internet-based applications are written in C++, Java and Ms.Net. The objective of this paper is to show how information system integration can aid in the forward engineering of legacy system. Software re-engineering covers the examination and alteration of legacy system in order to rebuild it according to modem software engineering methods and technologies in a forward engineering process. Information system integration provides a means for both understanding and capturing about the application and its domain and re-developing the system based on change requirement. Information system integration helps to rebuild any legacy by adopting modern software engineering principles, methods and technologies, which allows systems to architecture engineers over the years have devises many modernization techniques. This paper evaluates the use of information system integration as a veritable technique for transformation of legacy system. Keywords - COBOL, PASCAL, FORTRANS, C++,Java Ms.Net etc I. INTRODUCTION streamlining business processes to the software used. There are five levels of integrating information Many organizations are still faced with the problem system, which include data, data management, of converting applications written in Legacy middleware, application and user interface (Bizer, compilers such as COBOL, Pascal and FORTRAN 2003).
    [Show full text]
  • The 2020 Guide to Legacy System Innovation
    The 2020 Guide to Legacy System Innovation Legacy Systems The Keys A New Freedom for 2 APIs 4 6 8 Meet the to Freedom Approach to the Future 21st Century Modernization. The 2020 Guide to Legacy System Innovation Legacy Systems Meet the 21st Century egacy systems running on mainframe computers are at the heart of our economy – and our society. L They are an essential part of our tax systems, our social services, and our public safety. They also run the stock market, our financial institutions, ATMs, transportation systems and utility grids. In fact, we use them all the time and likely don’t even know it. For state and local governments, these legacy systems are a mixed blessing. On the one hand, they have provided extraordinary reliability. They’ve proved themselves with successful track records of 20, 30, or APIs even 40 years. On the other hand, they are rigid, and some would even say fragile, closed and expensive to maintain. Making changes to a legacy system is costly, risky, and prone to failure. Also, legacy systems are by nature siloed systems that keep their data locked inside where it’s safe, but inaccessible. As one senior public sector IT executive put it, “I feel like my data is in jail.” For decades, agencies have been looking for freedom include day-to-day operations, staffing, responding to from legacy systems—a way off of their existing systems. pressure for innovation from elected officials, application Software AG offers a better, stronger alternative: the users and citizens themselves, and complying with Freedom for Legacy solution.
    [Show full text]
  • Offline OTR Messaging System Under Network Disruption
    computers & security 82 (2019) 227–240 Available online at www.sciencedirect.com j o u r n a l h o m e p a g e : w w w . e l s e v i e r . c o m / l o c a t e / c o s e 2 O TR: Offline OTR messaging system under R network disruption Mahdi Daghmehchi Firoozjaei a,b, MinChang Kim a, JaeSeung Song b, ∗ Hyoungshick Kim a,1, a Department of Electrical and Computer Engineering, College of Information and Communication Engineering, Sungkyunkwan University, Suwon, Republic of Korea b Department of Computer and Information Security, College of Software & Convergence technology, Sejong University, Seoul, Republic of Korea a r t i c l e i n f o a b s t r a c t Article history: Providing a secure and efficient communication system under network disruption without Received 14 August 2018 a trusted third party remains a challenging issue. To develop a secure and efficient system Accepted 26 December 2018 in such situations, we extend the conventional Off-The-Record (OTR) protocol into a new Available online 29 December 2018 protocol named offline OTR (O 2TR). O 2TR provides end-to-end security between users with- out requiring the assumption that they are persistently connected to each other. To show Keywords: the feasibility of the proposed protocol, we implemented a prototype to support O 2TR based Key management on the Gajim XMMP instant messaging platform. Our experiments showed that O 2TR can Reliability be used reliably even when the corresponding network party is temporarily broken down.
    [Show full text]
  • Designing a Modern XMPP Service with Ejabberd
    ejabberd architecture and challenges in designing a modern messaging service 17th November 2015 Mickaël Rémond <[email protected]> Introduction ejabberd is scalable and versatile enough to adapt to most of the realtime messaging jobs you will want to handle. For many tasks, like corporate messaging, you can consider ejabberd as a standard package. However, to reach high level of scalability and flexibility, you need to consider ejabberd as an XMPP framework. As such, to build your modern messaging system, you need to: Be familiar with XMPP - Prerequisite. Learn ejabberd architecture Learn ejabberd API Work on solution design. Take control of your messaging platform and design it ! ejabberd: Routing messages in a statefull world ejabberd is a message router. Its role is to support real time messaging feature by moving messages from clients to other clients. In that sense it is stateless. However, to integrate in a statefull world, ejabberd has to support statefull features: Stateless: ejabberd is an XMPP server: Its goal is to route XMPP packets between JID. Statefull: In most case ejabberd depends on data (user base, contact list, …) or produce data (message archive, ...) Goal: deploy an ejabberd that is as stateless as possible, by leveraging backends. What are ejabberd backends ? Backends are pluggable modules you can configure to define where you would like to store part or all of your data. Backends provide the data to the feature modules of ejabberd. They can be read-write or read-only if you do not need some of the ejabberd associated features: For example, if you handle user management elsewhere in your infrastructure, you can use a user back-end that can only authenticate users but not create them.
    [Show full text]
  • Debian's Role in Establishing an Alternative to Skype
    Debian’s role in establishing an alternative to Skype Motivation, Challenges and Tactics Daniel Pocock [email protected] http://www.OpenTelecoms.org mini-DebConf, Paris, November 2012 Daniel Pocock [email protected] Debian’s role in establishing an alternative to Skype Introduction Motivation – why do we need to do something? What happens if we do nothing? Challenges – why hasn’t it been done already? Tactics – what can we do over the next 12 months? Daniel Pocock [email protected] Debian’s role in establishing an alternative to Skype Motivation Some background Yes, you’ve seen me before – in Managua. Slides and video are available and highly recommended. Is there something new? – yes. Daniel Pocock [email protected] Debian’s role in establishing an alternative to Skype Motivation Why mention Skype? Widely deployed – hundreds of millions of users Interdependency – unlike other types of software, interoperability is a critical factor in the success of real-time communications software Viber – another proprietary solution that has quickly gained traction thanks to ease of use. The free software community missed the boat in the desktop VoIP arena, now the same may be happening for mobile. Daniel Pocock [email protected] Debian’s role in establishing an alternative to Skype Motivation How bad is it? Marketing – Skype allows Microsoft to study your thoughts and emotions in real time. Feedback to advertisers. Privacy – Microsoft has patented a technique for monitoring Skype. Call records, friend lists, etc. Statistical techniques for identifying who is pregnant, who is a homosexual, have all been exposed recently.
    [Show full text]