Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

Chapter 4. Migrate Fabric

Introduction
Copiar enlace

Migrating Fabric from JBoss Fuse 6.2 to JBoss Fuse 6.3 is a manual process.

Multiple Fabrics on a host
Copiar enlace

As part of migrating to a new JBoss Fuse release, you might want to set up multiple fabrics on the same host. This is useful when you cannot (or are not ready to) directly upgrade an existing fabric.
If you are going to have multiple fabrics on the same host then you must ensure that there are no port clashes and that the two fabrics are completely separate. To do this, specify the following options when you create a new fabric on a host where a fabric already exists: 
fabric:create --min-port startPortRange
		 --max-port endPortRange 
		 --zookeeper-server-port zookeeperServerPort
Copy to Clipboard Toggle word wrap
Ensure that the port range for the new fabric is outside the port range used by the existing fabric. You must also ensure that the port range for the new fabric does not include any default ports used by other installed applications.
After migration is complete, shut down the older fabric environment. The recommendation is to run one fabric environment on a host except when more than one is required for migration.

Migrate the Fabric configuration from JBoss Fuse 6.2 to JBoss Fuse 6.3
Copiar enlace

To migrate a Fabric configuration, extract the configuration files from the source instance, then add them to the destination instance. The profile files in both instances are held in a git repository at FUSE_HOME/data/git/local/fabric and the following rules apply:
  • Each profile version is a git branch
  • Each profile is a directory in the git working copy of particular version.
Use the git commands shown below to migrate the Fabric configuration data from JBoss Fuse 6.2 to JBoss Fuse 6.3.
  1. Ensure that both JBoss Fuse 6.2 and JBoss Fuse 6.3 are stopped.
  2. Clone both git repositories:
    • git clone FUSE62_HOME/data/git/local/fabric/.git fuse62-repo which will result in a directory called fuse62-repo
    • git clone FUSE63_HOME/data/git/local/fabric/.git fuse63-repo which will result in a directory called fuse63-repo
  3. Checkout a working branch in each repository:
    • cd fuse62-repo
    • git checkout fuse62-working-branch-name
    • cd fuse63-repo
    • git checkout fuse63-working-branch-name
  4. Compare the contents of the directory structures. You can use whatever method you choose to compare the structures and merge or copy files from the JBoss Fuse 6.2 file structure to the equivalent place in the JBoss Fuse 6.3 git repository.
  5. When the files have been added to the JBoss Fuse 6.3 git repository, check in the working branch to apply your changes.
    • cd fuse63-repo
    • git add .
    • git commit -m 'Migrating profiles from 6.2'
    • git push origin fuse63-working-branch-name.
  6. Restart JBoss Fuse 6.2 and JBoss Fuse 6.3.
Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat