When a user decides to move from an old version to a new version, there may be changes that the user might have done to the resources of the prebuilt Fiorano Components. Component Resources Migration provides the user with an automated option to move the edited components along with their resources to the new installer.
How does the utility work?
The utility checks for available edited prebuilt components in the old installers’ repository/components directory. After making a list of components to move, for each component, the utility reads the old service descriptor file and new service descriptor file from the default prebuilt Components repository. If there are changes for resources in the old service descriptor, the utility will copy the whole component directory from $NEW_FIORANO_HOME/esb/server/repository/components to $NEW_FIORANO_HOME/runtimedata/repository/components and will change the service descriptor of the new component to accommodate the changes done to the old service descriptor, and then it will copy the resource jars from the old component repository to the newly created directory in $NEW_FIORANO_HOME/runtimedata/repository/components. If anything fails, the utility reverts the changes done by deleting the new directory created by it in $NEW_FIORANO_HOME/runtimedata/repository/components.