Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies reply
    1
  • Answers answer
    1
  • Subscribers subscribers
    173
  • Views views
    273
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

OO Upgrade from 10.80 to 2022.05 - Content Pack Migration

ArtQ

Hello fellow OO admins!

We are planning to upgrade our existing OO 10.80 to version 2022.05, now I have this idea of creating new VMs with OO 2022.05 clean installed that will run side by side with our existing OO 10.80.

Question is, by upgrading my existing studio from 10.80 to 2022.05, will it convert my existing flows (created on studio 10.80) to version 2022.05 Content Pack so I can just import from my 2022.05 central? 

My objective is to make the upgrade as seamless and less risk as possible without compromising automation availability.

Our OO 10.80 is running on:

Central = RedHat 6.5

DB = Oracle 12c

Our planned OO 2022.05 will run on:

Central = RedHat 7.9

DB = Oracle 19c

I need your suggestions, advise, tips... etc.

THANKS IN ADVANCE Slight smile

Regards,

Don

  • Suggested Answer

    0  

    Hello, OO content is backwards compatible between OO 10.80 and OO 22.05. That being said we recommend you always stay up2date with the latest out of the box content pack dependencies found on the ITOM Marketplace 

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.