The BMC Helix Innovation Suite product is now renamed to BMC Helix Platform. To view the latest documentation, see BMC Helix Platform.

If you have bookmarked these pages, you should update them with the new links.

Upgrading BMC Helix Innovation Suite SDK to 18.11.01: Patch 01

If you are using the BMC Helix Innovation Suite SDK to build and deploy applications and/or libraries, after you receive the notification, you must upgrade BMC Helix Innovation Suite SDK and any application projects that you created using an earlier version of BMC Helix Innovation Suite SDK. Note that these steps are not required for pure codeless development using BMC Helix Innovation Studio.

Tip

For more information about issues corrected in this patch, see Known and corrected issues.

Before you begin

To avoid errors after upgrading to BMC Helix Innovation Suite SDK to 18.11.1, ensure that you have performed the workarounds mentioned in upgrade considerations

To upgrade BMC Helix Innovation Suite SDK to 18.11 Patch 01

  1. After you receive notification that your BMC Helix Innovation Suite has been updated, download the BMC Helix Innovation Suite SDK ZIP file (com.bmc.arsys.rx.sdk-18.11.1.zip).

  2. Make sure that you have Node.js version 10.7.0 and Yarn version v1.9.4 installed. If not, see To install Node.js.
  3. Rename your current SDK folder to create a backup.
    For example, rename it to com.bmc.arsys.rx.sdk-18.08.1.BACKUP.
  4. At the location where you want to install the SDK, create a new SDK folder and extract the BMC Helix Innovation Suite SDK ZIP file (com.bmc.arsys.rx.sdk-18.11.1.zip).

  5. Add an environment variable, RX_SDK_HOME, that points to the sdk folder location.

  6. Find the .m2 folder (usually located in your user directory, such as %HOMEPATH%\.m2 on windows). Delete the arsys and rx folders located there.
  7. Install BMC Helix Innovation Suite SDK in your Maven repository by using the following commands:

    \com.bmc.arsys.rx.sdk-18.11.1> cd lib
    \com.bmc.arsys.rx.sdk-18.11.1\lib> mvn clean install
  8. Update the archetype-catalog.xml file to delete the earlier archetype versions (for example, 17.5.0) and ensure the archetype-catalog.xml has the archetype version as 18.11.1-SNAPSHOT.

    The archetype-catalog.xml file might be located at following locations:

    • .m2
    • .m2/repository

    For example:

    <archetype>
     <groupId>com.bmc.arsys</groupId>
     <artifactId>rx-sdk-archetype-lib</artifactId>
     <version>18.11.1-SNAPSHOT</version>
     <description>Generate a Rx base library.</description>
     </archetype>
     <archetype>
     <groupId>com.bmc.arsys</groupId>
     <artifactId>rx-sdk-archetype-simple</artifactId>
     <version>18.11.1-SNAPSHOT</version>
     <description>Generate a Rx application that has login page, landing page, a few view definitions, and some record definitions.</description>
     </archetype>
     </archetypes>

To upgrade your application or library

For each new SDK, you need to update the SDK version in the pom.xml file as in <rx-sdk.version>18.11.1-SNAPSHOT</rx-sdk.version>.

If your application, or library, was created for release 18.8.0 or earlier, and you have not already upgraded it to 18.08.1 yet, perform the following one-time steps after the latest SDK (18.11.1) is installed.

  1. Make sure that your tools are updated to the correct versions, including the SDK (18.11.1).

  2. Create a new dummy application or library using the maven archetype rx-sdk-archetype-simple. For more information, see Creating a Project using Maven and the Archetype.
    You are not required to build the application or library. The use of this application is only for temporary use and hence for this upgrade name the temporary application as TempApp and refer the original application as MyApp.

    Important

    If you have any customizations to the build scripts created from an archetype, create a backup of MyApp\bundle folder.

  3. Delete the MyApp\bundle\node_modules folder.
  4. Delete the MyApp\bundle\yarn.lock file.
  5. Delete the MyApp\bundle\grunt\watch.js file.
  6. Copy the following files from the TempApp folder to replace the files in MyApp folder.

    Copy fromTo replace
    TempApp\bundle\Gruntfile.jsMyApp\bundle\Gruntfile.js
    TempApp\bundle\karma.conf.jsMyApp\bundle\karma.conf.js
    TempApp\bundle\grunt\saas.jsMyApp\bundle\grunt\saas.js
  7. Copy TempApp\bundle\grunt\chokidar.js file to MyApp\bundle\grunt folder.
  8. Edit the MyApp\bundle\package.json file to update the list within the devDependencies object to match the same list defined in TempApp\bundle\package.json.
  9. Rebuild your application using the 18.11.1 SDK.

To upgrade the UI automation project

If you are upgrading from 18.11.0 or earlier, add the following property to the properties.config file.

# If you want to use drivers of your own choice, download them in the folder called drivers and provide define the driver location. 
# If you do not want to use the drivers of your own choice, leave the driversLocation attribute as blank. 
# For example, driversLocation=drivers -> this will pick up drivers.exe from drivers folder under the ui-automation. 
# driversLocation= -> By default this is set to blank. It then picks up drivers bundled in the ui framework jars. These drivers are tested.
driversLocation=


Related topic

Known and corrected issues

Was this page helpful? Yes No Submitting... Thank you

Comments