Cloud Software Group, Inc. EBX®
Documentation > Migration Guide
Navigation mode Documentation > Migration Guide

# Step 3: Deploying

## Overview

What follows are the high-level steps to deploy. If you have questions, refer to the TIBCO EBX® Installation Guide as it contains more detailed information and includes platform specific notes.

##### Attention

If you are deploying add-ons, it is a prerequisite to launch the repackaging `ant` task included in the Add-ons Bundle. Its location is as follows (see the TIBCO EBX® Add-ons Versioning and Packaging Guide for additional details): `<Add-ons Bundle location>\script\ebxRepackageWithLGPL.xml`.

To deploy:

1. Stop your application server.

2. Deploy libraries:

   1. For the EBX® core product, the following are located in `<EBX® 6 bundle location>\ebx.software\lib`:

      - When migrating to EBX® 6.0.x:

        - For EBX®: `ebx.jar`

        - To support the new compression algorithm: `ebx-lz4.jar`

        - For email support: `jakarta.mail-2.0.1.jar`

      - When migrating to EBX® 6.x.x:

        - For EBX®: `ebx.jar`

        - To support the new compression algorithm: `ebx-lz4.jar`

        - For third-party Java APIs: `ebx-resources-api.jar`

        - For email support: `jakarta.mail-2.0.1.jar`

   2. For EBX® Add-ons: `<EBX® Add-ons Bundle location>\lib\ebx-addons.jar`.

   3. Any custom libraries compiled using EBX® 6.

3. Deploy web applications:

   1. For the EBX® core product (located in `<EBX® 6 bundle location>\ebx.software\webapps\wars-packaging`):

      - `ebx-dataservices.war`

      - `ebx-dma.war`

      - `ebx-manager.war`

      - `ebx-root-1.0.war`

      - `ebx-ui.war`

      - `ebx.war`

      - `ebx-authenticator.war` (for version 6.1.3 and newer only)

      - `ebx-ide.war` (for version 6.2.0 and newer only)

      - `ebx-hub.war` (for version 6.2.0 and newer only)

   2. For EBX® Add-ons (located in `<EBX® Add-ons bundle location>\wars`):

      - `ebx-addon-common.war` (mandatory)

      - `ebx-addon-adix.war`

      - `ebx-addon-dama.war`

      - `ebx-addon-dint.war`

      - `ebx-addon-dmdv.war`

      - `ebx-addon-dpra.war`

      - `ebx-addon-dqid.war`

      - `ebx-addon-mame.war`

      - `ebx-addon-moda.war`

      - `ebx-addon-tese.war`

   3. All of your project-specific WAR files complied using EBX® 6.

4. Start your application server. The amount of time that the automatic migration process takes depends on the volume of migrated data.

   Successful migration is indicated by the following message in the `kernel.log` file: `******** EBX® started and initialized ********`.

   If a data model is still in error, migration will stop. Use the `kernel.log` file to find the root cause and follow the instructions in Data model cleanup.

Documentation > Migration Guide