New Approaches in Automation

Total Page:16

File Type:pdf, Size:1020Kb

New Approaches in Automation Automation Boost your productivity a thousand times Allen Lam, IT Manager HKU Libraries [email protected] 1 Automation Automate Innopac by Expect Automate Millennium by AutoIt New ways to program Expect New ways to program AutoIt Sierra automation 2 Usage of automation 1 Create review list (of bib, item, patron, etc) 2 Updating records (when global/rapid updates cannot help) 3 Loading/Exporting records 4 Generating statistics files, reports, etc 5 FTP upload/download 6 *Any* repeating tasks 3 Tools Automate Innopac by Expect Automate Millennium by AutoIt Expect is a Unix automation and testing tool, an extension to the Tcl scripting language, for interactive applications such as telnet, ftp, ssh… 4 Tcl & Expect Tool For controlling command and extending language applications Expect is an extension of Tcl 5 expect – automates “talks” to servers expect script send command wait for response 6 Bibles of Tcl and Expect 7 Ways to write Expect-style programs expect • reliable, in a less popular language (Tcl) • http://www.nist.gov/el/msid/expect.cfm expect4j • Excellent • http://code.google.com/p/expect4j/ (Java) expectj • works for light duty tasks only • http://expectj.sourceforge.net/ (Java) 8 Ways to write Expect-style programs enchanter • Excellent (Python, Ruby, • http://code.google.com/p/enchanter/ BeanShell) expect in • http://php.net/manual/en/ php (PECL book.expect.php extension) Expect.pm • http://search.cpan.org/~rgiersig/ Expect-1.15/Expect.pod (perl expect module) 9 Expect programmers, don’t limit yourself to Tcl Tcl . Java Delphi php Expect .NET Perl C# Ruby c/c++ Python 10 Java JVM > Tcl interpreter Multi-Threads Light weight Excellent IDE OO No compile Rich Lib Multi-platforms Pre-installed Garbage collection Community support Tcl/Expect Cannot spawn in DOS Cannot run in Windows Can run everywhere 11 Weakness in Mill Create Review File ONLY by Boolean search 12 Missing feature in Mill Create Review File by a given list of numbers ISSN/ISBN Bib rec# Call numbers Item rec# Barcodes Patron rec# Card numbers Order rec# Invoice numbers …… Course codes ….. 13 Demo For creating review files from rec#, ISN, BC A Java program with GUI Using expect4j to control Innopac Wrapped in exe Runs directly in Windows 14 Howto 1: Search by rec# SSH connection Innopac login Search by rec# Expect dialogue - Expect () Append to review list - Send () - … disconnect end﹜ 15 Gen Review File using Rec# 16 Gen Review File using Rec# 17 Gen Review File using Rec# Loop 18 Indexed fields other than Rec# 19 OPAC search to build review file 20 Howto 2: OPAC search SSH connection Innopac login OPAC Search Capture rec# Expect dialogue - Expect () Search by rec# - Send () - … Append to review list ﹜ disconnect end 21 Tools Automate Innopac by Expect Automate Millennium by AutoIt AutoIt is a freeware scripting language designed for automating the Windows GUI. It uses a combination of simulated keystrokes, mouse movement and window/control manipulation… 22 automate Millennium by AutoIt (Windows Only) But q Slow automating q Unpredictable response time linear sequential tasks is good q Bad for long sequence of iterative actions 23 Automation in the Sierra era web services/ API Custom Programs Create Access right= Read Update Delete 24 Automation in the Sierra era web services RW access to DB layer? Patron WS Item WS Bib WS Comprehensive enough? ReviewFile WS Price? Admin WS etc ?? 25 Char-based UI (Innopac) replaced by Command line UI? We wish… Every single command can be accomplished equally by different interfaces Command line UI GUI WS/API 26 Make Sierra an Open Platform Let community programmers contribute to Sierra 27 Summary 1 Automate Innopac by Expect Automate Millennium by AutoIt Expect can be written in many languages AutoIt has limitations AutoIt works well with Java AutoIt works best with non-iterative solutions 28 Summary 2 Methods to create review files from list Demo programs Sierra’s WS allows another form of automation • Can Sierra also give us a command-line interface? • Open platform is the trend 29 30 .
Recommended publications
  • Pexpect Documentation Release 4.8
    Pexpect Documentation Release 4.8 Noah Spurrier and contributors Apr 17, 2021 Contents 1 Installation 3 1.1 Requirements...............................................3 2 API Overview 5 2.1 Special EOF and TIMEOUT patterns..................................6 2.2 Find the end of line – CR/LF conventions................................6 2.3 Beware of + and * at the end of patterns.................................7 2.4 Debugging................................................8 2.5 Exceptions................................................8 2.6 Pexpect on Windows...........................................9 3 API documentation 11 3.1 Core pexpect components........................................ 11 3.2 fdpexpect - use pexpect with a file descriptor.............................. 23 3.3 popen_spawn - use pexpect with a piped subprocess.......................... 23 3.4 replwrap - Control read-eval-print-loops................................. 24 3.5 pxssh - control an SSH session...................................... 25 4 Examples 33 5 FAQ 35 6 Common problems 39 6.1 Threads.................................................. 39 6.2 Timing issue with send() and sendline()................................. 39 6.3 Truncated output just before child exits................................. 40 6.4 Controlling SSH on Solaris....................................... 40 6.5 child does not receive full input, emits BEL............................... 40 7 History 41 7.1 Releases................................................. 41 7.2 Moves and forks............................................
    [Show full text]
  • Ajuba Solutions Version 1.4 COPYRIGHT Copyright © 1998-2000 Ajuba Solutions Inc
    • • • • • • Ajuba Solutions Version 1.4 COPYRIGHT Copyright © 1998-2000 Ajuba Solutions Inc. All rights reserved. Information in this document is subject to change without notice. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means electronic or mechanical, including but not limited to photocopying or recording, for any purpose other than the purchaser’s personal use, without the express written permission of Ajuba Solutions Inc. Ajuba Solutions Inc. 2593 Coast Avenue Mountain View, CA 94043 U.S.A http://www.ajubasolutions.com TRADEMARKS TclPro and Ajuba Solutions are trademarks of Ajuba Solutions Inc. Other products and company names not owned by Ajuba Solutions Inc. that appear in this manual may be trademarks of their respective owners. ACKNOWLEDGEMENTS Michael McLennan is the primary developer of [incr Tcl] and [incr Tk]. Jim Ingham and Lee Bernhard handled the Macintosh and Windows ports of [incr Tcl] and [incr Tk]. Mark Ulferts is the primary developer of [incr Widgets], with other contributions from Sue Yockey, John Sigler, Bill Scott, Alfredo Jahn, Bret Schuhmacher, Tako Schotanus, and Kris Raney. Mark Diekhans and Karl Lehenbauer are the primary developers of Extended Tcl (TclX). Don Libes is the primary developer of Expect. TclPro Wrapper incorporates compression code from the Info-ZIP group. There are no extra charges or costs in TclPro due to the use of this code, and the original compression sources are freely available from http://www.cdrom.com/pub/infozip or ftp://ftp.cdrom.com/pub/infozip. NOTE: TclPro is packaged on this CD using Info-ZIP’s compression utility.
    [Show full text]
  • A Multiplatform Pseudo Terminal
    A Multi-Platform Pseudo Terminal API Project Report Submitted in Partial Fulfillment for the Masters' Degree in Computer Science By Qutaiba Mahmoud Supervised By Dr. Clinton Jeffery ABSTRACT This project is the construction of a pseudo-terminal API, which will provide a pseudo-terminal interface access to interactive programs. The API is aimed at developing an extension to the Unicon language to allow Unicon programs to easily utilize applications that require user interaction via a terminal. A pseudo-terminal is a pair of virtual devices that provide a bidirectional communication channel. This project was constructed to enable an enhancement to a collaborative virtual environment, because it will allow external tools such to be utilized within the same environment. In general the purpose of this API is to allow the UNICON runtime system to act as the user via the terminal which is provided by the API, the terminal is in turn connected to a client process such as a compiler, debugger, or an editor. It can also be viewed as a way for the UNICON environment to control and customize the input and output of external programs. Table of Contents: 1. Introduction 1.1 Pseudo Terminals 1.2 Other Terminals 1.3 Relation To Other Pseudo Terminal Applications. 2. Methodology 2.1 Pseudo Terminal API Function Description 3. Results 3.1 UNIX Implementation 3.2 Windows Implementation 4. Conclusion 5. Recommendations 6. References Acknowledgments I would like to thank my advisor, Dr. Clinton Jeffery, for his support, patience and understanding. Dr. Jeffery has always been prompt in delivering and sharing his knowledge and in providing his assistance.
    [Show full text]
  • Networking Telnet
    IBM i Version 7.2 Networking Telnet IBM Note Before using this information and the product it supports, read the information in “Notices” on page 99. This edition applies to IBM i 7.2 (product number 5770-SS1) and to all subsequent releases and modifications until otherwise indicated in new editions. This version does not run on all reduced instruction set computer (RISC) models nor does it run on CISC models. This document may contain references to Licensed Internal Code. Licensed Internal Code is Machine Code and is licensed to you under the terms of the IBM License Agreement for Machine Code. © Copyright International Business Machines Corporation 1998, 2013. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Telnet................................................................................................................... 1 What's new for IBM i 7.2..............................................................................................................................1 PDF file for Telnet........................................................................................................................................ 1 Telnet scenarios...........................................................................................................................................2 Telnet scenario: Telnet server configuration.........................................................................................2 Telnet scenario: Cascaded Telnet
    [Show full text]
  • An Empirical Investigation Into Programming Language Syntax
    i i i i An Empirical Investigation into Programming Language Syntax ANDREAS STEFIK, University of Nevada, Las Vegas SUSANNA SIEBERT, The Genome Institute, Washington University School of Medicine Recent studies in the literature have shown that syntax remains a significant barrier to novice computer science students in the field. While this syntax barrier is known to exist, whether and how it varies across programming languages has not been carefully investigated. For this article, we conducted four empirical studies on programming language syntax as part of a larger analysis into the, so called, programming language wars. We first present two surveys conducted with students on the intuitiveness of syntax, which we used to garner formative clues on what words and symbols might be easy for novices to understand. We followed up with two studies on the accuracy rates of novices using a total of six programming languages: Ruby, Java, Perl, Python, Randomo, and Quorum. Randomo was designed by randomly choosing some keywords from the ASCII table (a metaphorical placebo). To our surprise, we found that languages using a more traditional C-style syntax (both Perl and Java) did not afford accuracy rates significantly higher than a language with randomly generated keywords, but that languages which deviate (Quorum, Python, and Ruby) did. These results, including the specifics of syntax that are particularly problematic for novices, may help teachers of introductory programming courses in choosing appropriate first languages and in helping students to overcome the challenges they face with syntax. Categories and Subject Descriptors: D.3 [Programming Languages]; H.1.2 [Information Systems]: User/Machine Systems—Software psychology General Terms: Design, Experimentation, Human Factors, Standardization Additional Key Words and Phrases: Programming Languages, Novice Programmers, Syntax ACM Reference Format: Stefik, A.
    [Show full text]
  • NSWI 0138: Advanced Unix Programming
    NSWI 0138: Advanced Unix programming (c) 2011-2016 Vladim´ırKotal (c) 2009-2010 Jan Pechanec, Vladim´ırKotal SISAL MFF UK, Malostransk´en´am.25, 118 00 Praha 1 Charles University Czech Republic Vladim´ırKotal [email protected] March 10, 2016 1 Vladim´ırKotal NSWI 0138 (Advanced Unix programming) Contents 1 Overview 5 1.1 What is this lecture about? . .5 1.2 The lecture will cover... .5 1.3 A few notes on source code files . .6 2 Testing 6 2.1 Why?...........................................6 2.2 When ? . .6 2.3 Types of testing . .7 3 Debugging 8 3.1 Debuging in general . .8 3.2 Observing . .9 3.3 Helper tools . .9 3.3.1 ctags . .9 3.3.2 cscope . 10 3.3.3 OpenGrok . 11 3.3.4 Other tools . 11 3.4 Debugging data . 11 3.4.1 stabs . 11 3.4.2 DWARF . 12 3.4.3 CTF (Compact C Type Format) . 12 3.5 Resource leaks . 13 3.6 libumem . 13 3.6.1 How does libumem work . 14 3.6.2 Using libumem+mdb to find memory leaks . 14 3.6.3 How does ::findleaks work . 16 3.7 watchmalloc . 17 3.8 Call tracing . 18 3.9 Using /proc . 19 3.10 Debugging dynamic libraries . 20 3.11 Debuggers . 20 3.12 Symbol search and interposition . 20 3.13 dtrace . 21 4 Terminals 21 4.1 Terminal I/O Overview . 21 4.2 Terminal I/O Overview (cont.) . 22 4.3 Physical (Hardware) Terminal . 24 4.4 stty(1) command . 24 4.5 TTY Driver Connected To a Phy Terminal .
    [Show full text]
  • Specialising Dynamic Techniques for Implementing the Ruby Programming Language
    SPECIALISING DYNAMIC TECHNIQUES FOR IMPLEMENTING THE RUBY PROGRAMMING LANGUAGE A thesis submitted to the University of Manchester for the degree of Doctor of Philosophy in the Faculty of Engineering and Physical Sciences 2015 By Chris Seaton School of Computer Science This published copy of the thesis contains a couple of minor typographical corrections from the version deposited in the University of Manchester Library. [email protected] chrisseaton.com/phd 2 Contents List of Listings7 List of Tables9 List of Figures 11 Abstract 15 Declaration 17 Copyright 19 Acknowledgements 21 1 Introduction 23 1.1 Dynamic Programming Languages.................. 23 1.2 Idiomatic Ruby............................ 25 1.3 Research Questions.......................... 27 1.4 Implementation Work......................... 27 1.5 Contributions............................. 28 1.6 Publications.............................. 29 1.7 Thesis Structure............................ 31 2 Characteristics of Dynamic Languages 35 2.1 Ruby.................................. 35 2.2 Ruby on Rails............................. 36 2.3 Case Study: Idiomatic Ruby..................... 37 2.4 Summary............................... 49 3 3 Implementation of Dynamic Languages 51 3.1 Foundational Techniques....................... 51 3.2 Applied Techniques.......................... 59 3.3 Implementations of Ruby....................... 65 3.4 Parallelism and Concurrency..................... 72 3.5 Summary............................... 73 4 Evaluation Methodology 75 4.1 Evaluation Philosophy
    [Show full text]
  • Amira” for the Geosciences
    Web-Based Service of a Visualization Package “Amira” for the Geosciences Yunsong Wang1, Gordon Erlebacher1, Zachary A. Garbow2, David A. Yuen2 1School of Computational Science & Information Technology, Florida State University, Tallahassee, FL 32306-4120, U.S.A Emails: [email protected], [email protected] 2Department of Geology and Geophysics, University of Minnesota Supercomputing Institute, University of Minnesota, Minneapolis, MN 55455-0219, U.S.A Emails: [email protected], [email protected] Abstract. Amira is a powerful 3-D visualization package and has been employed recently by the science and engineering communities to gain insight into their data. We discuss a new paradigm for the use of Amira in the Earth sciences, which relies on the client-server paradigm. We have developed a module called WEB-IS2, which provides web-based access to Amira. This tool allows Earth scientists to manipulate Amira controls remotely and to analyze, render and view large datasets through the Internet, without regard for time or location. This could have important ramifications for GRID computing. 1. Introduction There is an ongoing explosion of data in the geosciences: datasets are growing in size at what seems to be exponential rates because of the acquisition of satellite interferometry and multispectral data, geodetic data collection campaigns and ever more detailed seismic surveys. Large scale, three-dimensional, unsteady simulations of geophysical phenomena over a wide range of spatial and temporal scales contribute significantly to this growth. Aside from the sheer size of the data sets, large scale multi-institution, multi-regional collaborations result in the distribution of this data across the globe.
    [Show full text]
  • Rubywrite: a Ruby-Embedded Domain-Specific Language for High-Level Transformations
    RubyWrite: A Ruby-Embedded Domain-Specific Language for High-Level Transformations Andrew Keep, Arun Chauhan, Chun-Yu Shei, and Pushkar Ratnalikar Indiana University, Bloomington, IN 47405, USA fakeep,achauhan,cshei,[email protected] Abstract. We introduce a Domain Specific Language (DSL), called RubyWrite, embedded within Ruby, with the goal of providing an ex- tensible, effective, portable, and easy to use framework for encoding source-level transformations. Embedding within Ruby provides access to the powerful features of Ruby, including its purely object-oriented design and meta-programming capabilities. The syntactic flexibility and advanced language features of Ruby drove our choice of it as the host lan- guage. Easy integration of external C interfaces seamlessly within Ruby lets us move performance critical operations to C, or link with external libraries. RubyWrite was developed to aid our compiler research where it provides the core of three compiler infrastructure development projects, and is used as a teaching aid in a graduate-level compilers course. We expect RubyWrite to be widely applicable and a proof of concept in leveraging an existing modern language to write a portable compiler in- frastructure core. 1 Introduction We describe a Domain Specific Language (DSL), embedded within Ruby, aimed at simplifying the task of source-level transformations through term-rewriting. The DSL, called RubyWrite, is motivated by the need for a compiler development environment that allows easy integration of source-level transformations with program analysis. After spending frustrating months trying to develop a compiler for matlab in C++ a few years ago, we made the decision to move to a domain-specific lan- guage for compiler development.
    [Show full text]
  • LFS-BOOK.Pdf
    Linux From Scratch Версия 7.3 Автор Gerard Beekmans Редакторы Matthew Burgess и Bruce Dubbs Перевод Иван Лабутин Linux From Scratch: Версия 7.3 by Автор Gerard Beekmans, Редакторы Matthew Burgess и Bruce Dubbs, Перевод Иван Лабутин Copyright © 1999-2013 Gerard Beekmans Copyright © 1999-2013, Gerard Beekmans Все права защищены. Эта книга выпущена под лицензией Creative Commons License. Команды для компьютера могут быть извлечены из книги под лицензией MIT License. Linux® зарегистрированная торговая марка Linus Torvalds. Linux From Scratch - Версия 7.3 Содержание Пролог ......................................................................................................................... viii i. Предисловие ........................................................................................................ viii ii. Кому адресована эта книга? ............................................................................... ix iii. Целевые архитектуры LFS .................................................................................. x iv. LFS и стандарты .................................................................................................. x v. Пояснения к выбранным пакетам ..................................................................... xii vi. Необходимые знания ....................................................................................... xvii vii. Требования к хост-системе ........................................................................... xviii viii. Соглашения, используемые в книге .............................................................
    [Show full text]
  • Ruby Programming
    Ruby Programming Wikibooks.org December 1, 2012 On the 28th of April 2012 the contents of the English as well as German Wikibooks and Wikipedia projects were licensed under Creative Commons Attribution-ShareAlike 3.0 Unported license. An URI to this license is given in the list of figures on page 249. If this document is a derived work from the contents of one of these projects and the content was still licensed by the project under this license at the time of derivation this document has to be licensed under the same, a similar or a compatible license, as stated in section 4b of the license. The list of contributors is included in chapter Contributors on page 243. The licenses GPL, LGPL and GFDL are included in chapter Licenses on page 253, since this book and/or parts of it may or may not be licensed under one or more of these licenses, and thus require inclusion of these licenses. The licenses of the figures are given in the list of figures on page 249. This PDF was generated by the LATEX typesetting software. The LATEX source code is included as an attachment (source.7z.txt) in this PDF file. To extract the source from the PDF file, we recommend the use of http://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/ utility or clicking the paper clip attachment symbol on the lower left of your PDF Viewer, selecting Save Attachment. After extracting it from the PDF file you have to rename it to source.7z. To uncompress the resulting archive we recommend the use of http://www.7-zip.org/.
    [Show full text]
  • Name Description Files
    PTY(7) Linux Programmer’sManual PTY(7) NAME pty − pseudoterminal interfaces DESCRIPTION Apseudoterminal (sometimes abbreviated "pty") is a pair of virtual character devices that provide a bidirec- tional communication channel. One end of the channel is called the master;the other end is called the slave.The slave end of the pseudoterminal provides an interface that behavesexactly likeaclassical termi- nal. A process that expects to be connected to a terminal, can open the slave end of a pseudoterminal and then be drivenbyaprogram that has opened the master end. Anything that is written on the master end is provided to the process on the slave end as though it was input typed on a terminal. Forexample, writing the interrupt character (usually control-C) to the master device would cause an interrupt signal (SIGINT)to be generated for the foreground process group that is connected to the slave.Conversely,anything that is written to the slave end of the pseudoterminal can be read by the process that is connected to the master end. Pseudoterminals are used by applications such as network login services (ssh(1), rlogin(1), telnet(1)), terminal emulators such as xterm(1), script(1), screen(1), tmux(1), unbuffer(1), and expect(1). Data flowbetween master and slave ishandled asynchronously,much likedata flowwith a physical termi- nal. Data written to the slave will be available at the master promptly,but may not be available immedi- ately.Similarly,there may be a small processing delay between a write to the master,and the effect being visible at the slave. Historically,two pseudoterminal APIs have evolved: BSD and System V.SUSv1 standardized a pseudoter- minal API based on the System V API, and this API should be employed in all newprograms that use pseu- doterminals.
    [Show full text]