CS5233 Components – Models and Engineering - Komponententechnologien - Master of Science (Informatik)

Total Page:16

File Type:pdf, Size:1020Kb

CS5233 Components – Models and Engineering - Komponententechnologien - Master of Science (Informatik) Prof. Dr. Th. Letschert CS5233 Components – Models and Engineering - Komponententechnologien - Master of Science (Informatik) Working with Jars (and other files using NIO) Seite 1 © Th Letschert Jars http://download.oracle.com/javase/tutorial/deployment/jar/index.html Jar Files Jar files : most important de-facto components in the Java biotope Jar file : archive file in zip format Zip file : format for (compressed) archive file with (compressed) content files Jar Tool command line tool <jdk>/bin/jar create / manipulate / extract from jar files Seite 2 Th Letschert Jars / Jar Tool Jar Tool / common operations Create jar c[v0M]f jarfile inputfiles Options: jar c[v0]mf manifest jarfile inputfiles c create v verbose output 0 no compression Update M no manifest file jar u[v0M]f jarfile inputfiles f specify name of jar file jar u[v0]mf manifest jarfile inputfiles m specify name of manifest file u update Extract files x extract t display table of contents jar x[v]f jarfile [inputfiles] List contents jar t[v]f jarfile [inputfiles] Seite 3 Th Letschert Jars / Meta Information Meta-Information a jar file may contain a directory META-INF containing “meta information” META-INF the directory for meta information contains information relevant for configuration purposes files / directories that are recognized by standard Java tools: – META-INF/MANIFEST.MF – META-INF/INDEX.LIST – META-INF/x.SF – META-INF/x.DSA – META-INF/services/ Seite 4 Th Letschert Jars / Meta Information Manifest-Version: 1.0 Created-By: 1.7.0-ea (Oracle Corporation) Manifest file MANIFEST.MF Example: Default manifest created by <jdk-7>/bin/jar Text file (UTF-8) structured into name – value pairs. Has to start with the main attribute – Manifest-Version version number of the manifest specification Additional main-attributes may follow – Created-By vendor of the java implementation – Signature-Version the signature version – Class-Path space separated list of relative urls that extend the class path – Main-Class main class in case the jar file defines a standalone application – Extension-Name the name of the extension (the jar file contains an extension) – … etc. …. Per entry attributes may follow after an empty line These are attributes that refer to a single entry of the jar file Example: Content-type of a file Seite 5 Th Letschert Jars / Working with Jars Package java.util.jar Provides classes for reading and writing jar files. Class java.util.jar.JarFile read the contents of a jar file Class java.util.jar.JarInputStream read the contents of a jar file from an input stream Class java.util.jar.JarOutputStream write the contents of a jar file to an output stream Package java.net Class java.net.JarURLConnection subclass of URLConnection read data identified by a jar-url Seite 6 Th Letschert Jars / Working with Jars JarFile Example: read and display content of a jar file import java.io.IOException; import java.util.Enumeration; import java.util.Scanner; import java.util.jar.*; public class ReadJar { public static void main(String[] args) throws IOException { Scanner scan = new Scanner(System.in); // get jar file's name String jarName = scan.next(); // display content JarFile jarFile = new JarFile(jarName); Enumeration<JarEntry> entries = jarFile.entries(); while (entries.hasMoreElements()) { JarEntry jarEntry = entries.nextElement(); System.out.println(jarEntry.getName()); } // display manifest Manifest manifest = jarFile.getManifest(); for (Object mainAttr: manifest.getMainAttributes().keySet()) { System.out.println( mainAttr + " -> " + manifest.getMainAttributes().getValue((Attributes.Name) mainAttr)); } } } Seite 7 Th Letschert Jars / Working with Jars JarFile Example: read and display content of a jar Manifest (1) import java.io.IOException; import java.io.InputStream; import java.nio.file.FileSystems; import java.nio.file.Files; import java.nio.file.Path; file handling relies on nio-2 import java.util.Map; features of Java 7 import java.util.jar.Attributes; import java.util.jar.JarInputStream; import java.util.jar.Manifest; public class Test { public static void main(String[] args) throws IOException { Path path = FileSystems.getDefault().getPath("/tmp/ajar.jar"); InputStream fis = Files.newInputStream(path); JarInputStream jis = new JarInputStream(fis); Manifest manifest = jis.getManifest(); ... next Slide ... } } Seite 8 Th Letschert Jars / Working with Jars JarFile Example: read and display content of a jar Manifest (2) System.out.println("Main Entries:"); for (Object mainAttr: manifest.getMainAttributes().keySet()) { System.out.println( mainAttr + " -> " + manifest.getMainAttributes().getValue((Attributes.Name) mainAttr)); } System.out.println(); System.out.println("Entries:"); Map<String,Attributes> manifestEntries = manifest.getEntries(); for(String key : manifestEntries.keySet() ) { System.out.println("entry key: " + key); System.out.println("entry values: "); Attributes attrs = manifestEntries.get(key); for (Object o : attrs.keySet()) { System.out.println(" " + o + " => " + attrs.getValue((Attributes.Name)o)); } } Main Entries: Manifest-Version: 1.0 Manifest-Version -> 1.0 Blubber-bla: wusch schlabber -> Schlapp schlabber: Schlapp Blubber-bla -> wusch Entries: Name: /p_269/CoreBuilder.class entry key: /p_269/CoreBuilder.class Bu-Bu: true entry values: Sealed: false Manifest file Sealed => false Bu-Bu => true Output Seite 9 Th Letschert Jars / Working with Jars JarFile Example: unzip jar file (1) import java.io.File; import java.io.IOException; import java.nio.file.DirectoryStream; import java.nio.file.FileSystems; import java.nio.file.Files; import java.nio.file.Path; import java.nio.file.PathMatcher; import java.nio.file.attribute.PosixFilePermission; import java.nio.file.attribute.PosixFilePermissions; import java.util.Enumeration; import java.util.Set; import java.util.jar.JarEntry; import java.util.jar.JarFile; public class ExtractJar { public static void main(String[] args) throws IOException { Path jarPath = FileSystems.getDefault().getPath("/tmp/Scratch/ajar.jar"); // check jar if (! Files.exists(jarPath) || ! Files.isReadable(jarPath) || Files.isDirectory(jarPath) ) { throw new IOException("not a readable file"); } PathMatcher matcher = FileSystems.getDefault().getPathMatcher("glob:" + "*.jar"); Path filePath = jarPath.getFileName(); if (filePath == null || ! matcher.matches(filePath)) { throw new IOException(" file does not exist or is not a jar file"); } if ( ! Files.probeContentType(jarPath).equals("application/x-java-archive") ) { throw new IOException("no jar content " + Files.probeContentType(jarPath)); } } ... next Slide ... } Seite 10 Th Letschert Jars / Working with Jars JarFile Example: unzip jar file (2) // determine directory to inflate into Path dirPath = jarPath.getParent(); String fileNameWithoutExt = ((filePath.toString()).split("\\."))[0]; Path inflatePath = dirPath.resolve(fileNameWithoutExt); System.out.println("inflate in directory " + inflatePath); // create inflate dir, previously delete it recursively if it already exists deleteRecursive(inflatePath); Set<PosixFilePermission> perms = PosixFilePermissions.fromString("rwxr-x---"); Files.createDirectory(inflatePath, PosixFilePermissions.asFileAttribute(perms)); //inflate jar content to dir JarFile jarFile = new JarFile(new File(jarPath.toString())); Enumeration<JarEntry> entries = jarFile.entries(); while (entries.hasMoreElements()) { JarEntry jarEntry = entries.nextElement(); Path destPath = inflatePath.resolve( FileSystems.getDefault().getPath(jarEntry.getName())); if (jarEntry.getName().endsWith("/")) { // directory Files.createDirectories(destPath); continue; } Files.createDirectories(destPath.getParent()); Files.copy(jarFile.getInputStream(jarEntry), destPath); } Seite 11 Th Letschert Jars / Working with Jars JarFile Example: unzip jar file (3) /** * Delete a file or recursively a directory * @param path the file or directory * @throws IOException if something went wrong */ private static void deleteRecursive(Path path) throws IOException { if (Files.isDirectory(path)) { DirectoryStream<Path> stream = Files.newDirectoryStream(path); for (Path entry: stream) { deleteRecursive(entry); } Files.deleteIfExists(path); } } helper function for deletion Seite 12 Th Letschert Jars / Jar URL Jar URL identifies resources within a jar file defined by Java API specification Syntax : jar:<url>!/[<entry>] where <url> is a non-jar url (e.g. a file url: file://[host]/path a http url, or ftp url) Examples (from Java API doc.): A Jar entry jar:http://www.foo.com/bar/baz.jar!/COM/foo/Quux.class A Jar file jar:http://www.foo.com/bar/baz.jar!/ A Jar directory jar:http://www.foo.com/bar/baz.jar!/COM/foo/ Seite 13 Th Letschert Jars / Working with Jars Example: load and execute runnable jar file (1) import java.io.IOException; import java.lang.reflect.InvocationTargetException; import java.lang.reflect.Method; import java.lang.reflect.Modifier; import java.net.JarURLConnection; import java.net.URL; import java.net.URLClassLoader; import java.util.Scanner; import java.util.jar.Attributes; public class JarExecuter { public static void main(String[] args) throws IOException, ClassNotFoundException, SecurityException, NoSuchMethodException, IllegalArgumentException, InvocationTargetException { Scanner scan = new Scanner(System.in); // get jar file's name // something like // /some/directory/HelloWorld.jar String jarName = scan.next(); ... next slide ... } } Seite 14 Th Letschert Jars / Working with Jars Example: load and execute runnable jar file (2) //The syntax of a JAR URL is:jar:<url>!/{entry} //
Recommended publications
  • The Ark Handbook
    The Ark Handbook Matt Johnston Henrique Pinto Ragnar Thomsen The Ark Handbook 2 Contents 1 Introduction 5 2 Using Ark 6 2.1 Opening Archives . .6 2.1.1 Archive Operations . .6 2.1.2 Archive Comments . .6 2.2 Working with Files . .7 2.2.1 Editing Files . .7 2.3 Extracting Files . .7 2.3.1 The Extract dialog . .8 2.4 Creating Archives and Adding Files . .8 2.4.1 Compression . .9 2.4.2 Password Protection . .9 2.4.3 Multi-volume Archive . 10 3 Using Ark in the Filemanager 11 4 Advanced Batch Mode 12 5 Credits and License 13 Abstract Ark is an archive manager by KDE. The Ark Handbook Chapter 1 Introduction Ark is a program for viewing, extracting, creating and modifying archives. Ark can handle vari- ous archive formats such as tar, gzip, bzip2, zip, rar, 7zip, xz, rpm, cab, deb, xar and AppImage (support for certain archive formats depends on the appropriate command-line programs being installed). In order to successfully use Ark, you need KDE Frameworks 5. The library libarchive version 3.1 or above is needed to handle most archive types, including tar, compressed tar, rpm, deb and cab archives. To handle other file formats, you need the appropriate command line programs, such as zipinfo, zip, unzip, rar, unrar, 7z, lsar, unar and lrzip. 5 The Ark Handbook Chapter 2 Using Ark 2.1 Opening Archives To open an archive in Ark, choose Open... (Ctrl+O) from the Archive menu. You can also open archive files by dragging and dropping from Dolphin.
    [Show full text]
  • Installing and Customizing Entirex Process Extractor Installing and Customizing Entirex Process Extractor
    Installing and Customizing EntireX Process Extractor Installing and Customizing EntireX Process Extractor Installing and Customizing EntireX Process Extractor This chapter covers the following topics: Delivery Scope Supported Platforms Prerequisites for using EntireX Process Extractor Installation Steps Customizing your EntireX Process Extractor Environment Delivery Scope The installation medium of the EntireX Process Extractor contains the following: 1 Installing and Customizing EntireX Process Extractor Delivery Scope File/Folder Description 3rdparty Source of open source components used for this product. Doc Documentation as PDF documents. UNIX For UNIX platforms. UNIX\EntireXProcessExtractor.tar The runtime part, which is unpacked to a folder for the runtime installation. Windows\ For Windows platforms. Windows\install\ Folder with two installable units: Design-time Part com.softwareag.entirex.processextractor.ide-82.zip This is installed into a Software AG Designer with EntireX Workbench 8.2 SP2. Runtime Part EntireXProcessExtractor.zip This is extracted to the folder for the runtime installation. Windows\lib\ Folder with Ant JARs and related JARs. Windows\scripts\ Folder with Ant script for installation, used by install.bat. Windows\install.bat Installation script for Windows. Windows\install.txt Description of the installation process for Windows. zOS For z/OS (USS) platforms. zOS\EntireXProcessExtractor.tar The runtime part, which is unpacked to a folder for the runtime installation. 3rdpartylicenses.pdf Document containing the license texts for all third party components. install.txt How to install the product on the different platforms. license.txt The Software AG license text. readme.txt Brief description of the product. The runtime part of the EntireX Process Extractor is provided as file EntirexProcessExtractor.zip in folder Windows\install, which contains the following files: 2 Delivery Scope Installing and Customizing EntireX Process Extractor File Description entirex.processextractor.jar The main JAR file for the EntireX Process Extractor.
    [Show full text]
  • Running Apache FOP
    Running Apache FOP $Revision: 533992 $ Table of contents 1 System Requirements...............................................................................................................2 2 Installation................................................................................................................................2 2.1 Instructions.......................................................................................................................... 2 2.2 Problems..............................................................................................................................2 3 Starting FOP as a Standalone Application...............................................................................3 3.1 Using the fop script or batch file......................................................................................... 3 3.2 Writing your own script.......................................................................................................5 3.3 Running with java's -jar option............................................................................................5 3.4 FOP's dynamical classpath construction............................................................................. 5 4 Using Xalan to Check XSL-FO Input......................................................................................5 5 Memory Usage.........................................................................................................................6 6 Problems.................................................................................................................................
    [Show full text]
  • Rule Base with Frequent Bit Pattern and Enhanced K-Medoid Algorithm for the Evaluation of Lossless Data Compression
    Volume 3, No. 1, Jan-Feb 2012 ISSN No. 0976-5697 International Journal of Advanced Research in Computer Science RESEARCH PAPER Available Online at www.ijarcs.info Rule Base with Frequent Bit Pattern and Enhanced k-Medoid Algorithm for the Evaluation of Lossless Data Compression. Nishad P.M.* Dr. N. Nalayini Ph.D Scholar, Department Of Computer Science Associate professor, Department of computer science NGM NGM College, Pollachi, India College Pollachi, Coimbatore, India [email protected] [email protected] Abstract: This paper presents a study of various lossless compression algorithms; to test the performance and the ability of compression of each algorithm based on ten different parameters. For evaluation the compression ratios of each algorithm on different parameters are processed. To classify the algorithms based on the compression ratio, rule base is constructed to mine with frequent bit pattern to analyze the variations in various compression algorithms. Also, enhanced K- Medoid clustering is used to cluster the various data compression algorithms based on various parameters. The cluster falls dissentingly high to low after the enhancement. The framed rule base consists of 1,048,576 rules, which is used to evaluate the compression algorithm. Two hundred and eleven Compression algorithms are used for this study. The experimental result shows only few algorithm satisfies the range “High” for more number of parameters. Keywords: Lossless compression, parameters, compression ratio, rule mining, frequent bit pattern, K–Medoid, clustering. I. INTRODUCTION the maximum shows the peek compression ratio of algorithms on various parameters, for example 19.43 is the Data compression is a method of encoding rules that minimum compression ratio and the 76.84 is the maximum allows substantial reduction in the total number of bits to compression ratio for the parameter EXE shown in table-1 store or transmit a file.
    [Show full text]
  • Software Development Kits Comparison Matrix
    Software Development Kits > Comparison Matrix Software Development Kits Comparison Matrix DATA COMPRESSION TOOLKIT FOR TOOLKIT FOR TOOLKIT FOR LIBRARY (DCL) WINDOWS WINDOWS JAVA Compression Method DEFLATE DEFLATE64 DCL Implode BZIP2 LZMA PPMd Extraction Method DEFLATE DEFLATE64 DCL Implode BZIP2 LZMA PPMd Wavpack Creation Formats Supported ZIP BZIP2 GZIP TAR UUENCODE, XXENCODE Large Archive Creation Support (ZIP64) Archive Extraction Formats Supported ZIP BZIP2 GZIP, TAR, AND .Z (UNIX COMPRESS) UUENCODE, XXENCODE CAB, BinHex, ARJ, LZH, RAR, 7z, and ISO/DVD Integration Format Static Dynamic Link Libraries (DLL) Pure Java Class Library (JAR) Programming Interface C C/C++ Objects C#, .NET interface Java Support for X.509-Compliant Digital Certificates Apply digital signatures Verify digital signatures Encrypt archives www.pkware.com Software Development Kits > Comparison Matrix DATA COMPRESSION TOOLKIT FOR TOOLKIT FOR TOOLKIT FOR LIBRARY (DCL) WINDOWS WINDOWS JAVA Signing Methods SHA-1 MD5 SHA-256, SHA-384 and SHA-512 Message Digest Timestamp .ZIP file signatures ENTERPRISE ONLY Encryption Formats ZIP OpenPGP ENTERPRISE ONLY Encryption Methods AES (256, 192, 128-bit) 3DES (168, 112-bit) 168 ONLY DES (56-bit) RC4 (128, 64, 40-bit), RC2 (128, 64, 40-bit) CAST5 and IDEA Decryption Methods AES (256, 192, 128-bit) 3DES (168, 112-bit) 168 ONLY DES (56-bit) RC4 (128, 64, 40-bit), RC2 (128, 64, 40-bit) CAST5 and IDEA Additional Features Supports file, memory and streaming operations Immediate archive operation Deferred archive operation Multi-Thread
    [Show full text]
  • CA Cross-Enterprise Application Performance Management Installation Guide
    CA Cross-Enterprise Application Performance Management Installation Guide Release 9.6 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.
    [Show full text]
  • Jar Cvf Command Example
    Jar Cvf Command Example Exosporal and elephantine Flemming always garottings puissantly and extruding his urinalysis. Tarzan still rabbet unsensibly while undevout Calhoun elapsed that motorcycles. Bela purchase her coccyx Whiggishly, unbecoming and pluvial. Thanks for newspaper article. Jar file to be created, logical volumes, supports portability. You might want but avoid compression, and archive unpacking. An unexpected error has occurred. Zip and the ZLIB compression format. It get be retained here demand a limited time recognize the convenience of our customers but it be removed in whole in paper at mine time. Create missing number of columns for our datatypes. Having your source files separate from your class files is pay for maintaining the source code in dummy source code control especially without cease to explicitly filter out the generated class files. Best practice thus not to censorship the default package for any production code. Java installation and directs the Jar files to something within the Java Runtime framework. Hide extensions for known file types. How trim I rectify this problem? Java releases become available. Have a glow or suggestion? On the command line, dress can snap a Java application directly from your JAR file. Canvas submission link extract the assignment. To prevent package name collisions, this option temporarily changes the pillar while processing files specified by the file operands. Next, but people a API defined by man else. The immediately two types of authentication is normally not allowed as much are less secure. Create EAR file from the command line. Path attribute bridge the main. Please respond your suggestions in total below comment section.
    [Show full text]
  • Reducing Delay with Dynamic Selection of Compression Formats
    In Proceedings of the International Symposium on High Performance Distributed Computing (HPDC), August 2001. Reducing Delay With Dynamic Selection of Compression Formats Chandra Krintz Brad Calder Department of Computer Science and Engineering University of California, San Diego g fckrintz,calder @cs.ucsd.edu Abstract aggressive compression ratios (resulting in longer transfer times). Internet computing is facilitated by the remote execution Compression is commonly used to improve the perfor- methodology in which programs transfer to a destination mance of applications that transfer over the Internet for re- for execution. Since transfer time can substantially degrade mote execution, i.e., mobile programs. The overhead im- performance of remotely executed (mobile) programs, file posed by compression-based remote execution includes the compression is used to reduce the amount that transfers. time for mobile code requests (program invocation and dy- Compression techniques however, must trade off compres- namic loading) and transfer. In addition, decompression sion ratio for decompression time due to the algorithmic time must also be included in this metric, since it occurs complexity of the former since the latter is performed at on-line while the program is executing. We refer to the runtime in this environment. combined overhead due to program request, transfer, and With this work, we define Total Delay as the time for decompression as Total Delay. both transfer and decompression of a compressed file. To Due to the inherent space-time trade-off made by com- minimize total delay, a mobile program should be com- pression algorithms, total delay is minimized only when se- pressed in a format that minimizes total delay.
    [Show full text]
  • Software Requirements Specification
    Software Requirements Specification for PeaZip Requirements for version 2.7.1 Prepared by Liles Athanasios-Alexandros Software Engineering , AUTH 12/19/2009 Software Requirements Specification for PeaZip Page ii Table of Contents Table of Contents.......................................................................................................... ii 1. Introduction.............................................................................................................. 1 1.1 Purpose ........................................................................................................................1 1.2 Document Conventions.................................................................................................1 1.3 Intended Audience and Reading Suggestions...............................................................1 1.4 Project Scope ...............................................................................................................1 1.5 References ...................................................................................................................2 2. Overall Description .................................................................................................. 3 2.1 Product Perspective......................................................................................................3 2.2 Product Features ..........................................................................................................4 2.3 User Classes and Characteristics .................................................................................5
    [Show full text]
  • Freebsd General Commands Manual BSDCPIO (1)
    BSDCPIO (1) FreeBSD General Commands Manual BSDCPIO (1) NAME cpio —copyfiles to and from archives SYNOPSIS cpio { −i}[options][pattern . ..][<archive] cpio { −o}[options] <name-list [>archive] cpio { −p}[options] dest-dir < name-list DESCRIPTION cpio copies files between archivesand directories. This implementation can extract from tar,pax, cpio, zip, jar,ar, and ISO 9660 cdrom images and can create tar,pax, cpio, ar,and shar archives. The first option to cpio is a mode indicator from the following list: −i Input. Read an archive from standard input (unless overriden) and extract the contents to disk or (if the −t option is specified) list the contents to standard output. If one or more file patterns are specified, only files matching one of the patterns will be extracted. −o Output. Read alist of filenames from standard input and produce a newarchive onstandard output (unless overriden) containing the specified items. −p Pass-through. Read alist of filenames from standard input and copythe files to the specified direc- tory. OPTIONS Unless specifically stated otherwise, options are applicable in all operating modes. −0 Read filenames separated by NUL characters instead of newlines. This is necessary if anyofthe filenames being read might contain newlines. −A (o mode only) Append to the specified archive.(Not yet implemented.) −a (o and p modes) Reset access times on files after theyare read. −B (o mode only) Block output to records of 5120 bytes. −C size (o mode only) Block output to records of size bytes. −c (o mode only) Use the old POSIX portable character format. Equivalent to −-format odc.
    [Show full text]
  • DROID: User Guide
    DROID: User Guide © Crown copyright 2020 You may re-use this information (excluding logos) free of charge in any format or medium, under the terms of the Open Government Licence. To view this licence, visit: nationalarchives.gov.uk/doc/open- government-licence or email [email protected] Where we have identified any third-party copyright information, you will need to obtain permission from the copyright holders concerned. This publication is available for download at nationalarchives.gov.uk. DROID: User Guide Contents 1 Introduction .................................................................................................................................................. 3 1.1 What is DROID? .......................................................................................................................................... 3 1.2 What is the purpose of this guidance? ................................................................................................... 3 1.3 Who is this guidance for? ......................................................................................................................... 3 2 Running DROID ............................................................................................................................................ 4 2.1 Installing and using DROID ...................................................................................................................... 4 2.2 Creating a profile ......................................................................................................................................
    [Show full text]
  • Large-Scale Client Deployment Using Java Web Start Software, TS-3212
    Large-Scale Deployment Using Java™ Web Start Software Matthias Schorer Technical Chief Architect FIDUCIA IT AG http://www.fiducia.de TS-3212 2006 JavaOneSM Conference | Session TS-3212 | Goal of the Talk Learn about the benefits of Java™ Web Start software and how it can be used to deploy complex software in a large environment 2006 JavaOneSM Conference | Session TS-3212 | 2 Agenda Who is FIDUCIA IT AG Java Web Start software in a nutshell Challenges for Java Web Start software How we made Java Web Start software work for us The Java Network Launching Protocol and API (JNLP) Runner How to use Pack200 to improve downloads How to enable your software for Java Web Start Common pitfalls 2006 JavaOneSM Conference | Session TS-3212 | 3 Agenda Who is FIDUCIA IT AG Java Web Start software in a nutshell Challenges for Java Web Start software How we made Java Web Start software work for us The Java Network Launching Protocol and API (JNLP) Runner How to use Pack200 to improve downloads How to enable your software for Java Web Start Common pitfalls 2006 JavaOneSM Conference | Session TS-3212 | 4 Who Is FIDUCIA The Company • FIDUCIA is the largest IT-Full service provider for the German cooperative banks • 3,480 employees • 728M € turnover • 920 individual banks rely on our service 2006 JavaOneSM Conference | Session TS-3212 | 5 Who Is FIDUCIA The Big Irons • z/Series mainframe with 110 CPUs 35,000 MIPS • 2,068 Sun Servers • SAN Storage 207 TB • Tape Storage 2,800 TB, 18,000 cassettes 2006 JavaOneSM Conference | Session TS-3212 | 6 Who Is FIDUCIA Data and Traffic • 53M customer accounts • 3B Transactions/year almost 100% created through Java technology! • 105,000 PC workstations • 11,100 ATMs • 12,050 statement printers 2006 JavaOneSM Conference | Session TS-3212 | 7 Who Is FIDUCIA Our Java History • 1996: Fiducia wrote the first home banking Java- based applet • 1998: Fiducia started development of the Java-based Banking Framework JBF • 1999: Fiducia decided to rewrite the whole Software Stack using JBF, including brokerage, ATM, self service, etc.
    [Show full text]