DOCSLIB.ORG

Lifekeeper™ for Linux Installation and Administration

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Lifekeeper™ for Linux Installation and Administration LifeKeeper® for Linux Module 3: Configuration Learning Objectives At the end of this module, you will understand: . LifeKeeper GUI server and client concepts . LifeKeeper GUI client application and applet . LifeKeeper GUI permissions . LifeKeeper Communication Paths . Miscellaneous LifeKeeper server configuration options Sep-10 Copyright © 2000-2010 by SteelEye Technology, Inc. All Rights Reserved World Wide. 2 Preparing to Run the GUI LifeKeeper GUI Overview . GUI Server Component • Must be running on each server in the cluster • Communicates with the LifeKeeper core via JNI (Java Native Interface) • Communicates with the client via RMI (Remote Method Invocation) . GUI Client Component runs… • As an application on a Linux system • As an applet invoked from a web browser (*Linux, Windows, Unix) Sep-10 Copyright © 2000-2010 by SteelEye Technology, Inc. All Rights Reserved World Wide. 3 Preparing to Run the GUI LifeKeeper GUI . QuickStart Configuration Assistant . Menu Bar . Tool Bar . Status Window . Message Display . Popup Menus via right click Sep-10 Copyright © 2000-2010 by SteelEye Technology, Inc. All Rights Reserved World Wide. 4 Preparing to Run the GUI LifeKeeper GUI Package (steeleye-lkGUI-<version>.<arch>.rpm) . Installs LifeKeeper GUI client in Java archive format . Installs LifeKeeper GUI Server . Installs LifeKeeper administration web server for use with web browsers (Java applet) . Installs a .java.policy file in /opt/LifeKeeper/htdoc containing minimum permissions to run LifeKeeper . Prepares LifeKeeper for GUI administration . To verify LifeKeeper GUI package installation rpm –qa | grep steel Sep-10 Copyright © 2000-2010 by SteelEye Technology, Inc. All Rights Reserved World Wide. 5 Preparing to Run the GUI LifeKeeper GUI Server: . Install the Java Components • Must have the Java Runtime Environment on each server in the cluster. (JRE is included on Installation Support CD). • By default, LifeKeeper expects Java to be installed in /usr/java/jre<version>/bin . Start the GUI Server process on all servers • To start the GUI server process on each server the first time: /opt/LifeKeeper/bin/lkGUIserver start • Entries for the two GUI server daemons are are automatically added to /etc/inittab. • Web server and the Java RMI server port entries are automatically added to /etc/default/LifeKeeper. Sep-10 Copyright © 2000-2010 by SteelEye Technology, Inc. All Rights Reserved World Wide. 6 Preparing to Run the GUI Configure GUI administrative users . a GUI user login is required to administer LifeKeeper from the GUI . root is automatically added during the installation as a GUI user. Password is the same as the Linux root user. GUI users should have the same password on all servers – eliminates requirement for user to enter multiple passwords during login /opt/LifeKeeper/bin/lkpasswd <user> /opt/LifeKeeper/bin/lkpasswd -d <user> Sep-10 Copyright © 2000-2010 by SteelEye Technology, Inc. All Rights Reserved World Wide. 7 Running the LifeKeeper GUI Running GUI as a Java application: . GUI client and GUI server running on same system . To invoke: • /opt/LifeKeeper/bin/lkGUIapp . lkGUIapp script sets appropriate environment variables and starts application . LifeKeeper GUI appears, Cluster Connect dialog displayed Running GUI as a Java applet: . GUI client running on same or different system as GUI server . Requires web browser and Java Runtime Environment • Java 1.5 is fully tested and supported . Default URL is http://<hostname or IP address>:81 . Java security requires that server and client must be able to resolve each other’s host names and IP addresses. Sep-10 Copyright © 2000-2010 by SteelEye Technology, Inc. All Rights Reserved World Wide. 8 Running the LifeKeeper GUI Running GUI as a Java Applet (continued): . On Linux a symlink must be created in the browser’s plugin directory to the Java plugin library. ln –s /usr/java/jre1.5.0_07/plugins/i386/ns7/libjavaplugin_oji.so \ /usr/lib/firefox/plugins/libjavaplugin_oji.so . Pre-Java 1.4 environments only: • Requires .java.policy file, so client can gain remote access to LifeKeeper servers and load Recovery Kit GUI extensions • Copy from /opt/LifeKeeper/htdoc/java.policy or http://<hostname>:81/java.policy • Set browser security parameters to low • See documentation for more information Sep-10 Copyright © 2000-2010 by SteelEye Technology, Inc. All Rights Reserved World Wide. 9 Running the LifeKeeper GUI Running the GUI Client: Open the URL: http://<hostname>:81 Example: http://node1:81 . IP addresses of browser client system and all servers must be resolvable (Java security) . Java Virtual Machine started . applet files downloaded . applet initialized . Login dialog box should appear Sep-10 Copyright © 2000-2010 by SteelEye Technology, Inc. All Rights Reserved World Wide. 10 LifeKeeper GUI Client (Review) LifeKeeper GUI Client: . Applet vs. Application • Applet allows client independence -- can run from Internet Explorer or Firefox on a Windows, Unix, or Linux client. • Applet does not require installation of any LifeKeeper packages on the client. • Applet supports security roles. • Application depends on the installation of the steeleye-lk and steeleye- lkGUI packages (requires a core product license). • Application can only be run on a Linux system. • Application has full control. • It is convenient to run the GUI as an application on an LifeKeeper server since the steeleye-lk and steeleye-lkGUI packages are already installed. Sep-10 Copyright © 2000-2010 by SteelEye Technology, Inc. All Rights Reserved World Wide. 11 GUI Applet Permissions . Guest Permission . Operator Task Guest Operator Administrato r . Administrator Connect to and disconnect from servers X X X View servers and resources X X X View server properties and logs X X X View resource properties X X X Put resources into and out of service X X Modify server properties X Create and delete comm paths X Create and delete resource hierarchies X Extend and unextend resource hierarchies X Create and delete resource dependencies X Modify resource properties X Sep-10 Copyright © 2000-2010 by SteelEye Technology, Inc. All Rights Reserved World Wide. 12 Configuring GUI Permissions . The GUI server must be invoked as root • During installation of the GUI package, an entry for the root login and password is automatically configured in the GUI password file with Administrator permission, allowing root to perform all LifeKeeper tasks on that server via the GUI application or web client. • If you plan to allow users other than root to use LifeKeeper GUI clients, then you need to configure LifeKeeper GUI users. Best practice is to always grant permissions on a cluster-wide basis • Grant permissions on a single-server basis is possible, but: – Confusing to users – Makes it impossible to perform administrative tasks Sep-10 Copyright © 2000-2010 by SteelEye Technology, Inc. All Rights Reserved World Wide. 13 Configuring GUI Permissions . User administration performed through command line interface: lkpasswd . Most commands require entering the user's password twice (validation) . Effective on next login or when GUI server is restarted . Single permission per user per server . New permissions override old ones . Commands update GUI password file on the server being administered. Repeat on all servers in the cluster. Sep-10 Copyright © 2000-2010 by SteelEye Technology, Inc. All Rights Reserved World Wide. 14 Configuring GUI Permissions . Grant Administrator permissions: /opt/LifeKeeper/bin/lkpasswd -administrator <user> . Grant Operator permissions: /opt/LifeKeeper/bin/lkpasswd -operator <user> . Grant Guest permissions: /opt/LifeKeeper/bin/lkpasswd -guest <user> . Change password (no change to access): /opt/LifeKeeper/bin/lkpasswd <user> . Remove access: /opt/LifeKeeper/bin/lkpasswd -delete <user> • (no password required) Sep-10 Copyright © 2000-2010 by SteelEye Technology, Inc. All Rights Reserved World Wide. 15 Communication Paths . Two comm paths are strongly suggested . Comm Path Functions: • Inter-node communication for obtaining status information • Heartbeat signal for verifying the systems are alive . Comm Path Types: • TCP utilizing a LAN connection (multiple TCPs allowed) • TTY utilizing a serial port connection (only 1 TTY allowed) . Comm Path Priorities • TCP - priority from 1-99 (1 is the highest) • TTY - always defaults to the lowest priority (no configurable priority) Sep-10 Copyright © 2000-2010 by SteelEye Technology, Inc. All Rights Reserved World Wide. 16 TCP Comm Path Setup: . Ethernet cards on the systems . IP addresses for each system . Two networks are suggested - one private LAN for LifeKeeper communication and one public LAN for user traffic. The user traffic LAN can be configured as a secondary comm path. Different comm paths cannot be on the same sub-net. Verify the network is functional before starting the comm path configuration. Network addresses must be resolvable, through /etc/hosts file and DNS. Sep-10 Copyright © 2000-2010 by SteelEye Technology, Inc. All Rights Reserved World Wide. 17 TCP Comm Path Configuration: . Select <Edit> <Server> <Create Comm Path> . Fields to Enter: • Local System Name • Remote System Name(s) • Type: Select TCP • Local IP Address • Remote IP address(es) • Priority . Select “Create Local” . Select “Create Remote” Sep-10 Copyright © 2000-2010 by SteelEye Technology, Inc. All Rights Reserved World Wide. 18 TTY Comm Path Setup: . Requires a null modem cable . Note: Only one TTY comm path is allowed between systems . Test the serial path using the portio command $LKROOT/bin/portio
Load more

Recommended publications
  • Cross-Platform System of Medical Documents Protection Through Digital Signatures
    CROSS-PLATFORM SYSTEM OF MEDICAL DOCUMENTS PROTECTION THROUGH DIGITAL SIGNATURES Fernando Guilherme Ferreira Sousa Project/Dissertation developed under supervising of José Magalhães Cruz (PhD) in Glintt - Healthcare Solutions, S.A. 1. Motivation documents, which are then sent to the server and, consequently, validated and stored in the database. Due to the extreme information sensibility in the Subsequent to this process, each time a document is health area, it is really necessary to be absolutely sure opened to be viewed, for example, a check is made of about who performs certain medical transactions. It a possible change to the same document, in order to must have permission and authority to do so, i.e. be ensure that recurrently its integrity. Through really the right person to do this transaction. In areas cryptography-based security methods of public keys, involving health treatments, marking of exams or it is verified if someone tampered the document or even surgeries and new prescriptions, there must be made it invalid in some way. an extremely effective control to verify effectively that all transactions must be properly carried out, Each platform that the doctor use should read his without any type of deception or illegality. digital certificate, which is contained in a Smart Card and is installed on the machine, once inserted in a One of the biggest motivations is that the patient, in suitable card reader. Then, the digital signature is the future, might be aware that there is a control in performed with the certificate’s associated private the preparation of their medical documents. All key, which certificates the medical document.
    [Show full text]
  • Applets, Servlets and JSP
    Java Programming : applets, servlets and JSP. SR03 Dritan Nace A summary of Java Java is a language developed by Sun, which is designed to be object oriented and Simple, robust and secure, independent of hardware architectures and Multitasking. Object oriented and simple : Simpler than C++, transparent memory managment… Robust et secure : Data typing is extremely strict. For applets, it is in principle impossible to access the resources of the host machine. Independant of hardware architectures : The compiler generates a universal code : the « byte-code ». An interpreter which is specific to the host machine, « virtual machine », executes the programs. Multitasking : Java seemingly allows execution of several processes. In reality, a time slot is given to each process on the processor (Multithreaded). J2SE versus J2EE J2SE (standard edition) contains the basic usable components from both the client and server side, – GUI, AWT/Swing for applications (client) or applets. Currently J2SE v1.6 (ou V6) J2EE (enterprise edition), is in a certain sense an extension of SE, designed for server side programming – Servlets, JSP, EJB, etc. • Currently J2EE v1.4 Java and object oriented programming • Classes, and objects – The objects include data and processing for the data. Communication is done via messages (methods). – A class corresponds to an abstract model for object construction. A class is made up of: • attributes (static part) • Methods (dynamic part), which define the behaviour. – Inheritance : the « is a » relationship : a car is a vehicule, – Polymorphism : the same message can be recognised by several objects and entail different behaviour. Portability: JVM The compiler compiles the java source in byte code : javac car.java => car.class Then, java is the name of the program which will interpret the generated byte code.
    [Show full text]
  • Abstract Window Toolkit Overview
    In this chapter: • Components • Peers 1 • Layouts • Containers • And the Rest • Summary Abstract Window Toolkit Overview For years, programmers have had to go through the hassles of porting software from BSD-based UNIX to System V Release 4–based UNIX, from OpenWindows to Motif, from PC to UNIX to Macintosh (or some combination thereof), and between various other alternatives, too numerous to mention. Getting an applica- tion to work was only part of the problem; you also had to port it to all the plat- forms you supported, which often took more time than the development effort itself. In the UNIX world, standards like POSIX and X made it easier to move appli- cations between different UNIX platforms. But they only solved part of the prob- lem and didn’t provide any help with the PC world. Portability became even more important as the Internet grew. The goal was clear: wouldn’t it be great if you could just move applications between different operating environments without worr yingabout the software breaking because of a different operating system, win- dowing environment, or internal data representation? In the spring of 1995, Sun Microsystems announced Java, which claimed to solve this dilemma. What started out as a dancing penguin (or Star Trek communicator) named Duke on remote controls for interactive television has become a new paradigm for programming on the Internet. With Java, you can create a program on one platform and deliver the compilation output (byte-codes/class files) to ever yother supported environment without recompiling or worrying about the local windowing environment, word size, or byte order.
    [Show full text]
  • Apache Harmony Project Tim Ellison Geir Magnusson Jr
    The Apache Harmony Project Tim Ellison Geir Magnusson Jr. Apache Harmony Project http://harmony.apache.org TS-7820 2007 JavaOneSM Conference | Session TS-7820 | Goal of This Talk In the next 45 minutes you will... Learn about the motivations, current status, and future plans of the Apache Harmony project 2007 JavaOneSM Conference | Session TS-7820 | 2 Agenda Project History Development Model Modularity VM Interface How Are We Doing? Relevance in the Age of OpenJDK Summary 2007 JavaOneSM Conference | Session TS-7820 | 3 Agenda Project History Development Model Modularity VM Interface How Are We Doing? Relevance in the Age of OpenJDK Summary 2007 JavaOneSM Conference | Session TS-7820 | 4 Apache Harmony In the Beginning May 2005—founded in the Apache Incubator Primary Goals 1. Compatible, independent implementation of Java™ Platform, Standard Edition (Java SE platform) under the Apache License 2. Community-developed, modular architecture allowing sharing and independent innovation 3. Protect IP rights of ecosystem 2007 JavaOneSM Conference | Session TS-7820 | 5 Apache Harmony Early history: 2005 Broad community discussion • Technical issues • Legal and IP issues • Project governance issues Goal: Consolidation and Consensus 2007 JavaOneSM Conference | Session TS-7820 | 6 Early History Early history: 2005/2006 Initial Code Contributions • Three Virtual machines ● JCHEVM, BootVM, DRLVM • Class Libraries ● Core classes, VM interface, test cases ● Security, beans, regex, Swing, AWT ● RMI and math 2007 JavaOneSM Conference | Session TS-7820 |
    [Show full text]
  • Migrating from Java Applets to Plugin-Free Java Technologies
    Migrating from Java Applets to plugin-free Java technologies An Oracle White Paper January, 2016 Migrating from Java Applets to plugin-free Java technologies Migrating from Java Applets to plugin-free Java technologies Disclaimer The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. Migrating from Java Applets to plugin-free Java technologies Executive Overview ........................................................................... 4 Browser Plugin Perspectives ............................................................. 4 Java Web Start .................................................................................. 5 Alternatives ....................................................................................... 6 Native Windows/OS X/Linux Installers ........................................... 6 Inverted Browser Control ............................................................... 7 Detecting Applets .............................................................................. 7 Migrating from Java Applets to plugin-free Java technologies Executive Overview With modern browser vendors working to restrict or reduce the support of plugins like
    [Show full text]
  • Installing Open Java Development Kit – Ojdkbuild for Windows
    Installing Open Java Development Kit – ojdkbuild for Windows © IZUM, 2019 IZUM, COBISS, COMARC, COBIB, COLIB, CONOR, SICRIS, E-CRIS are registered trademarks owned by IZUM. CONTENTS 1 Introduction ......................................................................................................... 1 2 OpenJDK distribution .......................................................................................... 1 3 Removing Oracle Java ......................................................................................... 2 4 Installing OJDK – 32bit or 64bit, IcedTea Java .................................................. 3 5 Installing the COBISS3 interface ........................................................................ 7 6 Launching the COBISS3 interface .................................................................... 11 7 COBISS3 interface as a trusted source in IcedTea ojdkbuild ........................... 11 © IZUM, 16. 7. 2019, VOS-NA-EN-380, V1.0 i VOS Installing Open Java Development Kit – ojdkbuild for Windows 1 Introduction At the end of 2018 Oracle announced a new business policy for Java SE which entered into force in April 2019. That is why when you install Java a notification and warning window appears. All versions of Java from 8 u201 onwards not intended for personal use are payable. For this reason, we suggest you do not update Java 8 to a newer version for work purposes. If you want a newer version of Java 8, install OpenJDK 8 and IcedTea. Also, do not install Java 8 on new computers (clients), but install OpenJDK 8 with IcedTea support. 2 OpenJDK distribution OpenJDK 1.8. build for Windows and Linux is available at the link https://github.com/ojdkbuild/ojdkbuild. There you will find versions for the installation. The newest version is always at the top, example from 7 May 2019: © IZUM, 16. 7. 2019, VOS-NA-EN-380, V1.0 1/11 Installing Open Java Development Kit – ojdkbuild for Windows VOS 3 Removing Oracle Java First remove the Oracle Java 1.8 software in Control Panel, Programs and Features.
    [Show full text]
  • Home Java Plugin Detector Java (Using <Applet> And/Or <Object> Tag
    22/05/12 Java plugin detection with PluginDetect Home Java Plugin Detector Java (using <applet> and/or <object> tag) installed & enabled: true Highest Installed Java Version: 1,6,0,31 Java 1,6,0,10 or higher (using <applet> and/or <object> tag) is installed & enabled. Java detection: completed ON THE FLY (OTF) Deployment Toolkit browser plugin installed & enabled: false Next-Generation Java Plugin2 installed & enabled: true Java vendor: Sun Microsystems Inc. Java plugin name: Java(TM) Platform SE 6 U31 Java plugin description: Next Generation Java Plug-in 1.6.0_31 for Mozilla browsers navigator.javaEnabled(): true [This detector is capable of OTF & NOTF Java detection. Detection occurs before window.onload event has fired.] [window.onload event has fired successfully.] [ The plugin detector(s) in this web page use the following: PluginDetect_Java.js, detectJava_OTF_NOTF.js, getJavaInfo.jar ] Download PluginDetect and the jarfile here... In order to do Java detection, you will need 2 things: 1) download the getJavaInfo.jar applet along with a few Java detection examples. The jarfile (Java ARchive file) is used by PluginDetect in order to accomplish Java detection. 2) download the PluginDetect script itself. The PluginDetect script generator will allow you to customize the PluginDetect script to include whatever features you desire. That being said, I would still recommend that you read thru most of this page before creating your own Java detection code. A brief introduction to Java detection PluginDetect uses a number of different methods when trying to detect Java in your browser. These Java detection methods can be divided into 2 groups: a) the non-applet methods and b) the applet methods.
    [Show full text]
  • (Microsoft Powerpoint
    Entwicklung mit JavaFX Die Java UI-Technologie im JDK 8 Wolfgang Weigend Sen. Leitender Systemberater Java Technologie und Architektur 1 Copyright © 2016 Oracle and/or its affiliates. All rights reserved. The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. 2 Copyright © 2016 Oracle and/or its affiliates. All rights reserved. Agenda • Aktueller Status von JavaFX • Entwicklungsressourcen beim Engineering und in der Java Community • Linux on ARM Port • JavaFX-Aufbau und Architekturkonzept • Migration von Swing Komponenten • Barrierefreiheit • Vorteile bei der Entwicklung von JavaFX Anwendungen • SceneBuilder GUI Editor • Automatisiertes Testen von JavaFX GUI Komponenten • Open Source Projekt OpenJFX • Kundenbeispiele, Projekte und relevante Partnerlösungen • Zusammenfassung 3 Copyright © 2016 Oracle and/or its affiliates. All rights reserved. Aktueller Status von JavaFX • JavaFX 8 ist fester Bestandteil der Java SE 8 – General Availability for Windows, Linux, Mac OS – Java SE 8 Roadmap until 2025 and expected JDK 9 until 2028 – Java SE Development Kit 8 Update 6 for ARM • Starting with JDK 8u33, JavaFX Embedded is removed from the ARM bundle and is not supported – http://www.oracle.com/technetwork/java/javase/jdk-8u33-arm-relnotes-2406696.html – http://mail.openjdk.java.net/pipermail/openjfx-dev/2015-January/016570.html • Development Tools – NetBeans 8.2 – JavaFX Scene Builder 2.0 und Version 8.2.0 – e(fx)clipse • major release cycle alignment with eclipse roadmap • minor release cycle with JavaFX roadmap 4 Copyright © 2016 Oracle and/or its affiliates.
    [Show full text]
  • (F/K/A LCCP) Open Source Disclosure
    Below are the licenses for open source software used in the LCCP product and platform. You may download certain source code (as required by applicable licenses below) from verizon.com/opensource. 1. Xerces 3.1.1 2. Libtins 3. G3log v1.1 4. Winpcap v4.1.0.902 5. jersey-container-servlet-core 2.23.1 6. jersey-media-moxy 2.23.1 7. jersey-container-servlet 2.7 8. jersey-media-multipart 2.23.2 9. jersey-media-json-jackson 2.23.2 10. derby 10.12.1.1 11. Log4j 1.2.17 12. quartz 2.2.1 13. jetty-server/jetty-servlet/jetty-webapp 9.2.3.v20140905 14. commons-dbcp 1.4 15. json 20160810 16. gson 2.7 17. mimepull 1.9.3 18. poi 3.15 19. poi-ooxml 3.15 20. ibatis-sqlmap 2.3.0 21. commons-net 3.4 22. commons-lang 3 23. Angular JS/Angular Cookies/Angular Routes/Angular Sanitize 1.5.7 24. Angular ToolTips 1.1.7 25. Google Material Design 26. jQuery v3.0 27. ngDraggable 28. Simple Pagination 29. Animation 3.5.1 30. Freemarker library 2.3.25 31. jetty-runner 9 32. jersey-client 1.8 33. jersey-core 1.8 34. jackson-core-asl-1.7.1 35. jackson-mapper-asl-1.7.1 36. device-api 0.3.2 37. ddmlib 24.5.0 38. ADB 39. AdbWinAPI.dll 40. NVD 3 1.8.1 41. JSCH – 0.1.55 42. Libssh2 – 0.74 43. COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.1 44.
    [Show full text]
  • Introduction to Java Applets
    1 2020 Introduction to Java Applets 2005 Pearson Education, Inc. All rights reserved. 2 Observe due measure, for right timing is in all things the most important factor. — Georg Wilhelm Friedrich Hegel Painting is only a bridge linking the painter’s mind with that of the viewer. — Eugene Delacroix The direction in which education starts a man will determine his future in life. — Plato 2005 Pearson Education Inc. All rights reserved. 3 OBJECTIVES In this chapter you will learn: To differentiate between applets and applications. To observe some of Java's exciting capabilities through the JDK's demonstration applets. To write simple applets. To write a simple HyperText Markup Language (HTML) document to load an applet into an applet container and execute the applet. Five methods that are called automatically by an applet container during an applet's life cycle. 2005 Pearson Education, Inc. All rights reserved. 4 20.1 Introduction 20.2 Sample Applets Provided with the JDK 20.3 Simple Java Applet: Drawing a String 20.3.1 Executing an Applet in the appletviewer 20.3.2 Executing an Applet in a Web Browser 20.4 Applet Life-Cycle Methods 20.5 Initializing an Instance Variable with Method init 20.6 Sandbox Security Model 20.7 Internet and Web Resources 20.8 Wrap-Up 2005 Pearson Education, Inc. All rights reserved. 5 20.1 Introduction • Applets – Java programs that can be embedded in HyperText Markup Language (HTML) documents – The browser that executes an applet is generically known as the applet container 2005 Pearson Education, Inc. All rights reserved.
    [Show full text]
  • Applets Programming Introduction Building Applet Code
    Introduction Applets are small Java programs that are embedded in Web pages. Applets Programming They can be transported over the Internet from one computer (web server) Enabling Application Delivery Via to another (client computers). the Web They transform web into rich media and support the delivery of applications via the Internet. 1 2 Applet: Making Web Interactive and How Applets Differ from Applications Application Delivery Media ¡ 1 2 3 4 5 Although both the Applets and stand-alone applications are Java programs, there are certain restrictions are APPLET hello.class Create Accessing The browser Development AT SUN’S Applet from creates imposed on Applets due to security concerns: “hello.java” WEB tag in Your Organisation a new ¢ Applets don’t use the main() method, but when they are load, AT SERVER HTML window and automatically call certain methods (init, start, paint, stop, SUN.COM document a new thread destroy). and ¢ They are embedded inside a web page and executed in then runs the browsers. code ¢ They cannot read from or write to the files on local computer. Hello Java ¢ They cannot communicate with other servers on the network. <app= “Hello”> The Internet ¢ They cannot run any programs from the local computer. Hello ¢ They are restricted from using libraries from other languages. ¡ The above restrictions ensures that an Applet cannot do any damage to the local system. 3 4 Building Applet Code: An Example Embedding Applet in Web Page //HelloWorldApplet.java < HTML> import java.applet.Applet; < HEAD> import java.awt.* ; < TITLE> Hello World Applet < /TITLE> public class HelloWorldApplet extends Applet { < /HEAD> public void paint(Graphics g) { g.drawString ("Hello World of Java!",25, 25); < body> < h1> Hi, This is My First Java Applet on the Web!< /h1> } < APPLET CODE= "HelloWorldApplet.class" width= 500 height= 400> } < /APPLET> < /body> < /HTML> 5 6 Accessing Web page (runs Applet) Applet Life Cycle £ Every applet inherits a set of default behaviours from the Applet class.
    [Show full text]
  • Security Target Lite Rev
    NXP JCOP on SN100.C25 Secure Element Security Target Lite Rev. 3.1 – 2020-08-25 Evaluation documentation Release Company Public NSCIB-CC-195714_3 Document Information Info Content Keywords ASE, JCOP, Common Criteria, EAL5 augmented Abstract This document contains information to fulfill the requirements of the Common Criteria component ASE (Security Target) for the Evaluation of the NXP JCOP products deployed on NXP SN100 Secure Element, developed and provided by NXP Semiconductors, Business Unit Security & Connectivity, according to the Common Criteria for Information Technology Security Evaluation Version 3.1 at EAL5 augmented. NXP Semiconductors JCOP on SN100.C25 Security Target Lite Company Public Rev Date Description 2.0 2019-10-10 Product Maintenance for JCOP 5.0 on SN100 3.0 2020-08-24 Re-certification for JCOP 6.1 on SN100 3.1 2020-08-25 Corrected a typo in the references Release ©NXP B.V. 2019. All rights reserved. Evaluation documentation Rev. 3.1 – 2020-08-25 1 of 186 NXP Semiconductors JCOP on SN100.C25 Security Target Lite Company Public 1 ST Introduction (ASE_INT) The TOE consists of a software stack (JCOP), which is stored and executed on a certified embedded Secure Element (eSE), including an associated Crypto Library and Security Software. The Secure Element (eSE) is embedded in a micro-controller which also includes an Integrated NFC controller and a System Mailbox. 1.1 ST Reference and TOE Reference Title NXP JCOP on SN100.C25 Secure Element Security Target Lite ST Version Revision 3.1 Date Product 2020-08-25 Type TOE Java Card Name NXP JCOP on SN100.C25 Secure Element Certification ID NSCIB-CC-195714_3 CC version Common Criteria for Information Technology Security Evaluation Version 3.1, Revision 5, April 2017 (Part 1 [8], Part 2 [9] and Part 3 [10]) Tab.
    [Show full text]