Migrate plug-ins with branching

You can migrate your project and save any workflows that you modify in an up-to-date format. You also begin to use the latest version of the plug-in SDK. If you want to have support for 7.x, you can branch your project.

Prerequisites

  • Verify that you are running Automation Orchestrator 8.12.
  • If your project does not depend on internal Automation Orchestrator Maven libraries which are not distributed with the SDK, you can install the new SDK and delete the repositories and pluginRepositories sections from the pom.xml file.

    You must also move to the usage of an isolated ClassLoader for your plug-in. For more information, see ClassLoaders. If you do depend on libraries not distributed with the plug-in SDK, it is recommended that you find an alternative to those libraries. Otherwise, you can still use the Maven repository by changing the repository URLs to point to your new Automation Orchestrator installation. Use the DNS names, everything else must remain unchanged.

Procedure

  1. Open the pom.xml file in the root folder of your project.
    1. Change the vco.version to 8.4.0.
    2. Change <artifactId>maven-o11n-package-plugin</artifactId> entry to <artifactId>o11n-package-maven-plugin</artifactId>.
  2. Open the pom.xml file in the project-name folder (the folder on the same level as the <project-name>-package folder) and change <artifactId>maven-o11n-dar-plugin</artifactId> to <artifactId>o11n-dar-maven-plugin</artifactId>.
  3. To build your plug-in, run the following Maven command. 
    mvn clean install -Dinstallation.mode=always -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true
  4. Log in to the Automation Orchestrator Control Center as root and navigate to the Manage Plug-ins page.
  5. Install your new plug-in. See Install or Update a vRealize Orchestrator Plug-In.
  6. Edit and save the workflows that you want to change.

    Editing the workflows breaks their backward compatibility because they no longer use the presentation format prior to vRealize Orchestrator 8.x.

    If you cannot edit your workflows, make sure that you have set the allowedMasks property value to vef in the configuration for the o11n-package-maven-plugin in the pom.xml of the your-project-name-package folder. Example:
    xml
<plugin>
	<groupId>com.vmware.o11n.mojo.pkg</groupId>
	<artifactId>o11n-package-maven-plugin</artifactId>
	<version>${vco.version}</version>
	<configuration>
		<allowedMask>vef</allowedMask>
	</configuration>
</plugin>
  7. Go to your your-project-name-package folder and run the following command. 
    mvn o11n-package:import-package \
	-DserverUrl=<your_vro_hostname>:443 \
	-Dusername=<vro_user> \
	-Dpassword=<vro_password> \
	-Dmaven.wagon.http.ssl.insecure=true \
	-Dmaven.wagon.http.ssl.allowall=true
    The changes that you made to the workflows in step 6 in this procedure are downloaded.