Show TOC

 Updating a Single FileLocate this document in the navigation structure

Use

The purpose of this procedure is to update a file that is a part of an already deployed application without restarting the application. It is time-reducing and especially useful for large-scale applications.

Caution

Updating a single file within an application is not advisable in real-life systems. It can lead to unexpected behavior of the application, since no tests have been done on the overall performance of the new application functionality. You should use single file update only in development systems.

If you have manually changed the application source or properties without the update or single file update procedures, these changes will be lost during the update or single file update procedures. We strongly advise you to make changes only using the update or single file update procedures. Otherwise you will have to restore these custom changes manually on every instance where they are installed.

Caution

This procedure cannot update:

  • for enterprise beans and EJB JARs
    • the enterprise bean interfaces and the deployment descriptor files.
    • the bean class file of an EJB bean, version 1.1 with CMP.
  • for the WAR files:
    • the auth_type, login modules, security role and login-config properties.
    • the security constraint property if you do not already have a login config property set.
    • from the web-j2ee.xml file you cannot change the security-role, security-role-map and the login-module-configuration properties.
Prerequisites

You must be logged on to J2EE Engine. For more information, see Logging on to SAP J2EE Engine in the Administration Manual.

The application must be already deployed.

Procedure
  1. Open the Single File Update dialog box.
    If You Want To Then

    Open it in the Deploy Tool

    For the project you are working on, choose Deploy → Deployment → Single File Deploy.

    Open it in the Visual Administrator

    Choose the Single File Update button.
  2. Specify the application name to which the file you want to update belongs. Application Name displays a list of all deployed applications on J2EE Engine.
  3. Specify the Module. It is the name of the archive to which the file you want to update belongs to. For example, a JAR file. The name must be the same as the name of the archive in the EAR file including the file extension.
  4. Specify the File Name of the new file in the file system. This file will be used to update the old file in the selected module.
    Note

    You can use a different file name.

  5. Specify the Mapping name of the updated file within the archive. You can use the name of the file.
    Caution

    You must use the exact mapping name of the file as it is in the selected module.

    You can also use the button that is next to the Mapping field. As a result, the Mapping field will list all mappings for the selected module.

    Caution

    The button is not active in the Deploy Tool.

  6. Specify the Container to serve the new file. Choose one of the containers started on the J2EE Engine.
  7. Choose Add and then OK.
    Note

    The Deploy Tool can update simultaneously more than one files, provided that they belong to one and the same application.