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

# Migration introduction

## Overview

Repository migration from TIBCO EBX® 5.9 to 6 is automatic on server startup. However, you must perform several technical and functional tasks prior to startup to ensure the automatic migration is successful. Some of these tasks include:

- Backing up and cleaning your existing 5.9 environment. Please note that this guide is intended for use during migration from 5.9 to 6. However, it is critical that you back up your existing repository even when upgrading from an older version of EBX® 6.

- Addressing custom modules.

- Understanding the new scalable architecture and its impact on custom Java code performance.

- Aligning with new hardware and memory requirements.

##### Note

The version numbering conventions used in this document are as follows:

- 5.9 refers to any release from 5.9.0 up to, and including, the most recent service pack for 5.9.

- 6 refers to any release from 6.0.0 up to, and including, the most recent release.

- 6.0 refers to any release from 6.0.0 up to, and including, the most recent service pack for 6.0.

- 6.x refers to any release from 6.1.0 up to, and including, the most recent release.

Likely the tasks mentioned above will be performed by different roles in your organization, in different environments (dev, pre-prod, prod, etc.), and using multiple versions of your repository. Note that some tasks must be performed multiple times; once in each environment. See the following to get started:

- Migration roadmap outlines the different phases of the migration process and provides links to the relevant documentation.

- Environment and hardware requirements outlines the impacts of migration on existing hardware.

- Changes to supported add-ons provides details on the add-ons migrated to EBX® 6, those with re-worked versions, and those that were discontinued.

### Additional documentation resources

Review the following documentation for additional information related to the migration process:

- In the All release notes sections available at docs.tibco.com, carefully review the Backwards compatibility sections for the releases leading up to the version you are migrating to. These sections contain important information that can assist your migration efforts.

- In the TIBCO EBX® Administration Guide, read the Installation and configuration section. This section contains performance tips, hardware guidelines, deployment information, and environment-specific installation instructions.

## Migration roadmap

The exact migration process depends on your organization's business requirements and implementation of TIBCO EBX®. What follows is a general guideline that addresses common requirements and provides a foundation that you can build on and adapt to address your specific needs. The links direct you to the relevant sections in the Migration Guide:

Step 1) Local environment (Developers) | This phase involves: Downloading EBX® 6 JARs Understanding new EBX® 6 architecture Refactoring custom code to leverage performance and ensure compatibility Compiling custom code with new JARs Running a test migration Generating binaries See Step 1: Adapting custom code for detailed steps.
Step 2) Pre-production environment (Dev Sec Ops) | This phase involves: Preparing a pre-production version of the repository. See Step 2: Preparing the repository for detailed steps. Understanding new environment and hardware requirements. See Environment and hardware requirements for more information. Deploying and testing in pre-production environment. See Step 3: Deploying for detailed steps.
Step 3) Production environment (Dev Sec Ops) | This phase involves: Preparing the production version of the repository. See Step 2: Preparing the repository for detailed steps. Ensuring the production environment complies with the new environment and hardware requirements. See Environment and hardware requirements for more information. Deploying and testing in the production environment. See Step 3: Deploying for detailed steps.

Documentation > Migration Guide