Administer > Deploy > Deploying customized assets > Customized WebSphere Commerce Enterprise Application (EAR) assets > Deploying custom Java EE assets

Deploy J2EE assets for a partial application

The partial application option provides the ability to deploy several files into the J2EE application at the same time. You must also use this option to delete any number of files that are in the J2EE application.

Do not use this option if the single file is a J2EE module. J2EE modules must be deployed as an entire module.

Use this option to deploy any combination of assets such as:

• Logic jars
• JSP files
• Configuration XML files

Consider the following scenario: A problem has been found in a JSP file and a controller command. The developer has made and tested the changes in the development environment. The functional tester has also validated the change in the quality assurance environment.

It is now time to deploy the changed assets to the production site.

In the packaging phase, you build a single ZIP file that contains:

• The entire logic jar file that includes all existing code that is part of that JAR file, including the changed controller command .class file
• The JSP file

The structure of the ZIP file is like the following example:

• WebSphereCommerceServerExtensionsLogic.jar
• Stores.war/myStore/myPage.jsp

Before you begin

Build a ZIP file that contains the assets that to deploy. This ZIP file is used as the input to this process.

Always back up the J2EE assets before you deploy.

Use either the WebSphere administrative console to add or update assets. However, deleting application files in a partial application update deployment scenario is accomplished by supplying a special metadata file called...

META-INF/ibm-partialapp-delete.props

...in the partial application ZIP. This file can exist at the application scope or at any embedded archive scope including modules.

Procedure

1. Deploy using the WebSphere administrative console

   1. Backup the J2EE assets.

   2. Place the ZIP file containing the changed files either on the machine running WebSphere administrative console or the machine running the Web browser you are using to access the WebSphere administration console.

   3. Start the WebSphere Application Server administration server.
      

   4. Launch the WebSphere administrative console.
      

   5. In the WebSphere administration console, expand...

      Applications | Application Types | WebSphere enterprise applications

   6. From the Enterprise Applications list, select the check box next to the J2EE application for the instance, WC_instance (for example, WC_demo). Click Update.

   7. On the Preparing for Application Installation page, under the Application update options section:

      1. Select Replace, add, or delete multiple files

      2. If the changed files are on the same machine as the Web browser used to connect to the WebSphere administrative console:

         If you are typing the directory paths, always use forward slashes no matter which platform you are using. Do not prefix with a leading slash.

      3. In the Specify the path to the compressed file section, select Local file system. Specify the full path and file name to the ZIP file containing all of the changed files. Click Next.

         If the changed file is on the server that the Web browser is connected to use the WebSphere administrative console.

         If you are typing in the directory paths, always use forward slashes no matter which platform you are using. Do not prefix with a leading slash.

      4. In the Upload the archive file with the new or replacement files section, select Remote file system.

         Specify the full path and file name to the ZIP file containing all of the changed files; then click Next.

      5. The Updating Application page is displayed with a confirmation message. Click OK.

      6. WebSphere Application Server saves the updates and deploys the file. On the Updating page, click Save to Master Configuration to save the changes.

2. Deploy using the wsadmin tool

   1. Back up the changed assets before deploying.

   2. Place the ZIP file containing the changed files on the file system of the machine running the wsadmin tool.

   3. Start the wsadmin tool.
      

   4. Run the following commands depending on the language you have chosen:

      • JACL

        $AdminApp update WC_ instance partialapp {-contents path to partial zip}

        $AdminConfig save

        For example: $AdminApp update WC_prod partialapp {-contents /deployments/2007-01-01a/partialApp.zip}

        $AdminConfig save

      • Jython AdminApp.update('WC_ instance', 'partialapp', '[-contents path to partial zip]')

        AdminApp.save()

        For example: AdminApp.update('WC_prod', 'partialapp', '[-contents /deployments/2007-01-01a/partialApp.zip]')

        AdminApp.save()

Related tasks

Deploy custom J2EE assets

Validate changes have been deployed for a custom Enterprise Application (EAR) file

Compiling JavaServer Page files

Related reference

Troubleshoot: Deployment

+

Search Tips   |   Advanced Search