Project manager and lead developer: Zane U. Ji — Approximate size Age rating For all ages. This app can Access all your files, peripheral devices, apps, programs and registry Microsoft. Permissions info. Installation Get this app while signed in to your Microsoft account and install on up to ten Windows 10 devices. This product needs to be installed on your internal hard drive. Seizure warnings Photosensitive seizure warning. Report this product Report this app to Microsoft Thanks for reporting your concern.
Our team will review it and, if necessary, take action. Sign in to report this app to Microsoft. Report this app to Microsoft. Report this app to Microsoft Potential violation Offensive content Child exploitation Malware or virus Privacy concerns Misleading app Poor performance. How you found the violation and any other useful info.
Submit Cancel. System Requirements Minimum Your device must meet all minimum requirements to open this product OS Windows 10 version Recommended Your device should meet these requirements for the best experience OS Windows 10 version Open in new tab.
Modules within an application must have unique names. In addition, for enterprise beans that use container-managed persistence CMP , the. You should use a hierarchical naming scheme for module file names, EAR file names, module names as found in the module-name portion of the ejb-jar. This hierarchical naming scheme ensures that name collisions do not occur. The benefits of this naming practice apply not only to GlassFish Server, but to other Java EE application servers as well.
Starting in Java EE 6, the Java EE specification defines the portable application-name , which allows you to specify an application name in the application. For example:. The Java EE specification also defines the portable module-name element in the module standard deployment descriptors. GlassFish Server determines the application registration name according to the following order of precedence:. The name specified at deployment time in the Administration Console or in the --name option of the asadmin deploy command is used.
If no name is specified at deployment time, the portable application-name or module-name in the Java EE deployment descriptor is used. If no name is specified at deployment time or in the deployment descriptors, the archive name, minus the file type suffix, is used. Establishing a consistent naming convention can help. Application and module directory structures must follow the structure outlined in the Java EE specification.
During deployment, the application or module is expanded from the archive file to an open directory structure. If you deploy a directory instead of an EAR file, your directory structure must follow this same convention. Because there is no file name, the name of the application is taken from the application-name or module-name entry in the Java EE standard deployment descriptor.
If the application-name or module-name entry is not present, GlassFish Server creates a temporary file name and uses that name to deploy the application. If you are using the following preferred JSR 88 API, the name is derived from the application-name or module-name entry if present or the first portion of the file name without the.
Application and module versioning allows multiple versions of the same application to exist in a GlassFish Server domain, which simplifies upgrade and rollback tasks. At most one version of an application or module can be enabled on a server any given time. Versioning provides extensions to tools for deploying, viewing, and managing multiple versions of modules and applications, including the Administration Console and deployment-related asadmin subcommands. Different versions of the same module or application can have the same context root or JNDI name.
Use of versioning is optional. The version identifier is a suffix to the module or application name. It is separated from the name by a colon :. It must begin with a letter or number. The following examples show valid version identifiers for the foo application:. A module or application without a version identifier is called the untagged version. This version can coexist with other versions of the same module or application that have version identifiers. Using the asterisk by itself after the colon selects all versions of a module or application, including the untagged version.
The following table shows example version expressions and the versions they select. The following table summarizes which asadmin subcommands are identifier-aware or expression-aware. All expression-aware subcommands are also identifier-aware. The create-application-ref subcommand is expression-aware only if the --enabled option is set to false. Because the --enabled option is set to true by default, the create-application-ref subcommand is identifier-aware by default.
The list-applications and list-application-refs subcommands display information about all deployed versions of a module or application. To find out which version is enabled, use the --long option. At most one version of a module or application can be enabled on a server instance.
All other versions are disabled. Enabling one version automatically disables all others. You can disable all versions of a module or application, leaving none enabled. The --enabled option of the deploy and redeploy subcommands is set to true by default. Therefore, simply deploying or redeploying a module or application with a new version identifier enables the new version and disables all others.
To deploy a new version in a disabled state, set the --enabled option to false. Module and application versioning in GlassFish Server is subject to the following restrictions and limitations:. Use of the --name option is mandatory for modules and applications that use versioning.
There is no automatic version identifier generation. GlassFish Server does not recognize any relationship between versions such as previous or later versions. All version relationships must be tracked manually. There is no limit to the number of versions you can deploy except what is imposed by disk space limits. A module or application in a directory should not be deployed twice with a different version identifier. To redeploy a module or application from a directory with a new version, you must use the --force option of the deploy subcommand.
Database tables created or deleted as part of deployment and undeployment are global resources and cannot be qualified by an application version.
Be very careful when using global resources among versions of the same application. Web sessions are preserved during redeployment of a new version. However, preserving sessions among different versions of the same module or application is complex, because the key used for session variables is the same for the old and new versions. Therefore, you must explicitly create resources for a newer version of a module or application.
GlassFish Server ignores duplicate exported global resources and lets deployment succeed. OSGi already has its own versioning system. Therefore, when you deploy an OSGi bundle, GlassFish Server ignores any version information provided with the name but permits the deployment to succeed with warnings.
The deployment tools that are provided by GlassFish Server can be used by any user authorized as an administrator to deploy applications and modules into any GlassFish Server environment. However, effective application deployment requires planning and care. Only the developer knows exactly what is required by an application, so the developer is responsible for initial assembly and deployment. Deployment Descriptor or Annotation Creation. The developer creates the deployment descriptors or equivalent annotations using Java standards and tools.
The GlassFish Server sample applications contain deployment descriptors that can be used as templates for developing deployment descriptors. The developer assembles the archive file s using Java standards and tools, such as the jar command. For guidelines on naming, see Naming Standards. There are no GlassFish Server issues to consider. Test Deployment. The developer performs a test deployment of the archive. Archive Submission.
The developer submits the verified archive to the administrator for deployment into a production environment. The developer includes instructions for any additional deployment tasks that the administrator must perform. For an example of such additional instructions, see Access to Shared Framework Classes. The administrator applies additional deployment specifics. Sometimes the developer has indicated additional deployment needs, such as specifying the production database.
In this case, the administrator edits and reassembles the archive. Production Deployment. The administrator deploys the archive to production.
See To Deploy an Application or Module. If deployment fails, the administrator returns the archive to the developer. The developer fixes the problem and resubmits the archive to the administrator. Sometimes the administrator resolves the problem, depending on what the problem is. The GlassFish Server Administration Console is a browser-based utility that features a graphical interface that includes extensive online help for the administrative tasks. Step-by-step instructions for using the Administration Console for deployment are provided in the Administration Console online help.
You can display the help material for a page by clicking the Help button. The initial help page describes the functions and fields of the page itself. To find instructions for performing associated tasks, click a link in the See Also list.
The GlassFish Server asadmin utility is a command-line tool that invokes subcommands for identifying the operation or task that you want to perform. You can run asadmin commands either from a command prompt or from a script. Application deployment commands are listed in The asadmin Deployment Subcommands. For the most part, you can perform the same administrative tasks by using either the graphical Administration Console or the asadmin command-line utility, however, there are exceptions.
Procedures for using the command-line utilities are provided in this guide and in the command-line help pages, which are similar to man pages. You can display the help material for a command by typing help followed by the subcommand.
Common Annotations for the Java Platform 1. Java EE Connector Architecture 1. About Application Deployment Assembly, also known as packaging, is the process of combining discrete components of an application or module into a single unit that can be installed on an application server.
General Deployment Functionality Various Java EE module types, such as connector module, web module, EJB module, application client module, can be deployed in the following ways:. There are two work situations that require different safeguards and processes:. The following types of deployment descriptors are associated with GlassFish Server:. The following annotation and deployment descriptor combinations are supported:. Modules and Applications An application is a logical collection of one or more modules joined by application annotations or deployment descriptors.
Types of Modules GlassFish Server supports the following types of modules:. Module-Based Deployment You can deploy web, EJB, and application client modules separately, outside of any application. The following figure shows separately-deployed EJB, web, and application client modules.
Figure Module-Based Assembly and Deployment. Application-Based Deployment Application-based deployment is appropriate when components need to work together as one unit.
0コメント