Version 1

    The 2020.1 releases of Aurea Process and Aurea Monitor are here!

    To celebrate, we hosted a webinar, Aurea Integration Solutions Urgent Upgrade, and showcased the exciting new features included in this release.  Here are the published answers from the questions customers asked during the Q&A at the conclusion of the webinar. 

    If you missed the live webinar, be sure to watch the recording: Aurea Integration Solutions Urgent Upgrade

     

    Q.  What Upgrade packages are available to help us upgrade to the latest release?

     

    Aurea Professional Services has developed packages that will help you to upgrade faster with less impact on your internal resources. 

     

    Process Upgrade Version 8 & ⇧

    • Includes all Process software assets, up to 10 applications
    • Performed on a specified non-production environment
    • Includes 30-day post support


    Monitor Upgrade Package  Version 2013 & ⇧

    • Includes Management Server and 20 Monitor Agents
    • Performed on a specified non-production environment
    • Includes 30-day post support

     

    Contact your Aurea Account Executive to learn more about services available to help you with your upgrade.

     

    Q. Will the new 2020.1 and 2020.2 Aurea Monitor architecture be backwards compatible with existing stats in the monitor database or will the database need to clean start?

     

    Jiri De Jagere: That's a very good question. So the main difference in the architecture itself is in how the agents and intermediaries are deployed and managed.  In the past, they were standalone installations, today the architecture uses something we call a launcher.  Launcher is a very small, lightweight process you install on the server. And when it comes online it'll dial into the management server to pull in its configuration.  So that means that the data side of the solution hasn't been touched and existing stats and metrics can be migrated across.  The same applies to things like policies that have been configured as and so we have the means of migrating them from one environment to the other. Obviously, the easiest is to do a greenfield installation and start from scratch. But we have the means to migrate all of your configuration over if required.



    Q. Will removing the flash components affect earlier versions of Aurea Process (Savvion)  and will the upgrade require major code changes?

     

    Jiri De Jagere:  We have removed Adobe Flash from the Aurea Process as of version 2020.1. Specifically, so that means that all the older versions will still depend on flash, which means that there are parts of the user interface that use flash and that will potentially stop working.  In particular, the parts of the user interface that build on Adobe Flash or the dashboards with your process and the process instance, so our recommendation is to upgrade to 2020.1 or later to make sure that the version that you are on has no dependency on Adobe Flash.

     

    The only parts that rely on Adobe Flash are in the user interface. It is just some aspects of the user interface, but they are pretty important aspects that I'm sure most of you, if not everybody uses. So getting rid of flash is very important.

     

    The second part of the question was, does it require major code changes and no that is not the case. We consider the Aurea Process upgrade to be a standard drop in replacement of the previous platform. So obviously, when you migrate to 2020.1 dot one you want to do some regression testing, etc. To make sure that your application continues to work as expected.

     

    There are no major issues. We haven't done any breaking API changes. So all should continue to work, that is if you've been keeping up to date.

     

    Mark Hall: Yeah, that that would be the one point I would emphasize as well in terms of the major code changes, it really depends on what version of the Aurea Process or Savvion you're using, I know some customers are still running some quite old versions and the upgrade will require a little bit more work. So I would urge you, as a next step, please get in touch with your account executive to understand if you are running an older version and what some of these changes may mean to your specific situation.



    Q. Is there any impact to the Sonic Management Console, we're only using Aurea Messenger?

     

    Mark Hall:  I believe the answer is no. The management console doesn't use flash and so the expiration of flash won't affect you. However, as part of the upgrade the release of messenger, as well as the enterprise features that you went through earlier. So we would always recommend customers take a look at the latest version of the messenger release as well.



    Q.  Is Bootstrap applied to only the chart files or applied to the UI from the applications.

     

    Jiri De Jagere: So we use Bootstrap as the styling framework across all web applications. So the whole web application itself is styled using bootstrap. So if you are on version 2013 or 2015 the standard out of the box UI will actually look different because we've applied these new style sheets.  But obviously if you're familiar with CSS. There are options to customize that



    Q. For Monitor will the upgrade to 2020.2 be required if we don't use the flash based portions of the UI?

     

    Jiri De Jagere: The Adobe Flash components only impact the parts of the UI that use Flash because it's a UI technology.  If you do not rely on a management server, its flow mapping, alert maps, dashboard widgets, etc.  then no, but obviously those are core functionalities of the application,  so it's highly likely that you use them.



    Q. What is the impact to those customers who are using the intermediary part of Aurea Monitor, can you talk a little bit about how the removal of flash will affect those customers, please?

     

    Jiri De Jagere: Sure. So intermediary itself has no direct dependency upon Adobe Flash, there are no UI components as part of intermediary that actually use Adobe Flash, but obviously intermediary is managed and installed via the management server and all the monitoring capabilities that are part of the management server do rely on Adobe Flash for a lot of their advanced visualizations. So if you use the monitoring capabilities, besides the API management capabilities of intermediary, then you do have a dependency on Adobe Flash.  If you do not use the monitoring capabilities at all, then those would obviously stop working, you would have a broken UI, but they don't impact the operation of intermediary itself.



    Q. For the 2020.1 version of monitor, can we get them as a docker image or as a regular installation?

     

    Jiri De Jagere:  Well, we obviously ship installers as we've traditionally been doing. And we also have Docker images available as tar balls for you to use in your own repository. So you can import them and use them for your own development test and production environments.

     

    Q.  For the 2020.1 feature changes and removal of flash, are they available on both standard enterprise versions?

     

    Jiri De Jagere: The removal of Adobe Flash components  are across both standard and enterprise versions of the product.  We do think there are benefits for customers upgrading to enterprise because of the new features within the products as well as the removal of Flash components.



    Q. We are using very old version of Messenger (Sonic 8.5.1). Will we still get support and fixes for this going forward? '+ will Aurea support OpenJDK for Sonci 8.5?

     

    Jiri De Jagere:  Sonic 8.5 is End of Life and no fixes will be shipped. The OpenJDK will not be supported for Sonic 8.5 either, as it is end of life.

     

    Q. Are you planning to release the documentation with process examples to upgrade from 2015/2019 to 2020 R1? - For Process

     

    Jiri De Jagere:  Yes

     

    Q. Does the new version of Monitor include Kafka, Spark etc.? Does it requre a message broker for the agent-server communication?

     

    Jiri De Jagere:  No, the new version of Monitor does not use Kafka or Spark. The communication between the Agents / Intermediaries and the Management Server has been standardized on JMS now, so a message broker is required.