Java平台标准版9部署指南

需积分: 5 35 浏览量更新于2024-06-22 收藏 947KB PDF 举报

"JDK9-JSE-Deployment Guide-164.pdf 是Oracle公司发布的Java Platform, Standard Edition (Java SE) 9的部署指南，旨在帮助开发者和管理员理解和执行Java应用程序的部署策略。该文档发布于2017年9月，涵盖了版权和使用许可协议的详细信息，并强调了对软件的使用限制。" Java SE部署指南是针对Java开发人员和系统管理员的重要参考资料，它详细阐述了在Java 9平台上部署Java应用程序的最佳实践和关键步骤。在Java 9中，有许多重要的更新和改进，包括模块系统（Project Jigsaw）、增强的JShell（REPL）以及对JVM的优化。以下是该指南可能涵盖的一些关键知识点： 1. **模块系统**：Java 9引入了模块化，这是通过Project Jigsaw实现的，旨在提高程序的可维护性、安全性和性能。了解如何定义、打包和运行模块化应用，以及如何处理模块间的依赖关系，是理解Java 9部署的关键。 2. **JShell**：这是一个交互式的Java代码运行环境，允许开发者快速测试代码片段，提高了开发效率。学习如何使用JShell进行即时代码调试和原型设计是提升开发生产力的一个重要方面。 3. **模块化JAR文件**：Java 9中的JAR文件支持模块化，这意味着可以指定模块的依赖关系和暴露的API。了解如何创建和配置模块化的JAR文件对于构建符合Java 9标准的应用至关重要。 4. **HTTP/2支持**：Java 9加强了对HTTP/2协议的支持，提供了更高效的网络通信。开发者需要知道如何利用新的HTTP客户端API来编写利用HTTP/2特性的应用程序。 5. **垃圾收集器改进**：Java 9进一步优化了垃圾收集器，如G1 GC的改进，提供了更好的内存管理性能。了解这些优化可以帮助调整应用以获得最佳性能。 6. **JEP（Java Enhancement Proposals）**：Java 9包含了多个JEP，如JEP 238（多版本JAR文件），JEP 260（增强模块读取）等，这些都影响了部署流程。理解每个JEP的目的和影响有助于更好地适应新特性。 7. **安全性**：Java 9在安全方面也有所加强，例如改进了证书管理，增强了加密算法。了解这些安全更新对于保护用户数据和应用安全非常重要。 8. **部署工具和配置**：指南还会详细介绍如何配置和使用Java Web Start、JavaFX以及Applet等部署技术，以及如何调整Java运行时选项以优化性能。 9. **兼容性和迁移**：由于Java 9引入了许多重大变化，因此了解如何从早期版本迁移到Java 9，以及如何处理兼容性问题，是部署过程中不可忽视的部分。 10. **诊断和监控**：Java 9提供了一系列诊断工具和监控功能，帮助开发者识别和解决问题。熟悉这些工具的使用可以极大地提高问题排查的效率。 Java SE 9部署指南是一份详尽的文档，涵盖了从基础到高级的Java 9部署策略，对于任何想要充分利用Java 9特性的开发者或管理员来说都是必不可少的参考资源。

Note:

Although available and supported in JDK 9, the Applet API and the Java Plug-

in are marked as deprecated in preparation for removal in a future release.

Alternatives for applets and embedded JavaFX applications include Java Web

Start and self-contained applications.

You can use an

element or JavaScript code for applications that

are embedded in a web page and use the Java Plug-In to run. Use JavaScript code to

create the link or button that calls Java Web Start to launch an application from the

browser. The Java packaging tools generate JavaScript code for both types of

execution, which you can copy into your web page.

The HTML page generated by the packaging tools is a simple test page for your

application. It includes sample JavaScript code to launch and embed your application,

which you can copy to your own web page. To avoid manual copying, consider using

HTML templates for application packaging to insert the JavaScript code into an

existing web page.

Distribute Your Application

When you have your application package and any web pages that you are using, copy

them to the appropriate location to make your application available to users.

• If your application is embedded in a web page or launched from a browser, copy

your package and the web page to the web server from which they will be loaded.

• If your application is a desktop application, copy the application to the location

from which users will download it. Self-contained applications provide installable

packages and the required JRE, which makes it easier for users to install and run

your application.

Beyond the Basics

This topic provides the minimum information needed to deploy a simple application,

which makes use of the default processing that is provided by the packaging tools.

More advanced applications could have additional requirements, for example:

• Include a custom splash screen that is shown when your application is loaded.

• Include a custom progress bar that is shown while your application is loading.

• Use JavaScript code to communicate between your application and the web page

in which it is embedded.

• Deploy Swing and SWT Applications with Embedded JavaFX Content

• Minimize the number of security dialogs and the warnings contained within the

dialogs to help ensure users that it is safe to run your application.

The Deployment trail in the Java Tutorials also provides information to help you deploy

applications embedded in a web page or launched from a browser.

Chapter 1

Distribute Your Application

1-6

Self-Contained Application Packaging

This topic describes how to generate the package for a self-contained application. A

self-contained application contains your Java or JavaFX application and the JRE

needed to run the application. Self-contained packages can be created for distribution

to systems running Linux, macOS, and Windows.

This topic includes the following sections:

• Introduction

• Benefits and Drawbacks of Self-Contained Application Packages

• Basics

• Installable Packages

• Working Through a Deployment Scenario

Introduction

The Java packaging tools provide built-in support for several formats of self-contained

application packages. The basic package is a single folder on your hard drive that

includes all application resources and the JRE. The package can be redistributed as

is, or you can build an installable package (for example, EXE or DMG format.)

From the standpoint of process, producing a self-contained application package is

similar to producing a basic application package, with the following differences:

• Self-contained application packages must be explicitly requested by passing the

native

argument to the

<fx:deploy>

Ant task or

javapackager -deploy

command.

• Self-contained application packages must be built on the operating system on

which it is intended to run. Prerequisite tools must be available to build a package

in a specific format.

• Self-contained application packages can only be built using JDK 7 Update 6 or

later. The Java Packager for JDK 9 packages applications with a JDK 9 runtime

image. To package a JDK 8 or JDK 7 JRE with your application, use the JDK 8

Java Packager.

While it is easy to create a basic self-contained application package, tailoring it to

achieve the best user experience for a particular distribution method usually requires

some effort and a deeper understanding of the topic.

Benefits and Drawbacks of Self-Contained Application

Packages

Deciding whether the use of self-contained application packages is the best way to

deploy your application depends on your requirements.

Self-contained application packages provide the following benefits:

2-1

• Users install the application with an installer that is familiar to them and launch it in

the usual way.

• You control the version of the JRE used by the application.

• Applications can be deployed on fresh systems with no requirement for the JRE to

be installed.

• Deployment occurs with no need for admin permissions when using ZIP or user-

level installers.

• File associations can be registered for the application.

• Support for secondary launchers enables a suite of applications to be bundled in a

single self-contained application package.

Self-contained application packages have the following drawbacks:

• "Download and run" user experience

Unlike web deployment, the user experience is not about "launch the application

from the web." It is more one of "download, install, and run" process, in which the

user might need to go through additional steps to get the application launched. For

example, the user might have to accept a browser or operating system security

dialog, or find and launch the application installer from the download folder.

• Larger download size

In general, the size of self-contained application packages is larger than the size of

a standalone application, because a private copy of the JRE is included.

• Package per target platform

Self-contained application packages are platform-specific and can only be

produced for the same system on which you build. To deliver self-contained

application packages on Windows, Linux, and macOS, you must build your project

on all three platforms.

• Application updates are the responsibility of developer

Web-deployed Java applications automatically download application updates from

the web as soon as they are available. The Java Autoupdate mechanism takes

care of updating the JRE to the latest secure version several times every year.

Self-contained applications do not have built-in support for automatic updates.

Basics

Each self-contained application package includes the following items:

• Application code in a set of JAR files, plus any other application resources (data

files, native libraries)

• Copy of the JRE, to be used by this application only

• Native launcher for the application, multiple launchers for a single package are

supported

• Metadata, such as icons

Multiple package formats are possible. Built-in support is provided for several types of

packages. You can also assemble your own packages by post-processing a self-

contained application packaged as a folder, for example, if you want to distribute your

application as a ZIP file.

Chapter 2

Basics

2-2

剩余163页未读，继续阅读

weixin_40191861_zj

粉丝: 84
资源: 1万+

Java平台标准版9部署指南

JDK10-JSE ,Installation Guide-57.pdf

JDK9-JSE-Monitoring and Management Guide-67.pdf

JDK9-JSE-Nashorn User's Guide-32.pdf

bcprov-jdk14-145.jar

jdk-8.0.302.8-hotspot和jdk1.8区别

bcprov-jdk16-1.46.jar has unsigned entries - org/bouncycastle/LICENSE.class

3、安装和配置JDK rpm -qa|grep openjdk packages中jdk-8u211-linux-x64.tar.gz cd /opt/packages tar -zxvf jdk-8u211-linux-x64.tar.gz -C /opt/programs vi /etc/profile export JAVA_HOME=/opt/programs/jdk1.8.0_211 export PATH=$PATH:$JAVA_HOME/bin source /etc/profile java -version写注释

aspose-words-21.6.0-jdk17.jar下载

lrwxrwxrwx. 1 root root 26 6月 8 01:35 jdk-11.0.19 -> /export/server/jdk-11.0.19 lrwxrwxrwx. 1 root root 47 6月 8 01:06 jdk-11.0.19_linux-x64_bin.tar.gz -> /export/server/jdk-11.0.19_linux-x64_bin.tar.gz

最新资源