I currently use Siebel version 8.1.1.11, I would like to upgrade version 21.2 or 21.4 version. Have you ever been partake of something this experience. If so that, is there any tools to this upgrade? Can you share your experience?
Thanks for help
Based on my experience, this operation is complicated if there are many customizations are made in the version 8.1.1.11 in order to meet the requirements of version 21.2 or 21.4 and mostly needs long-term project to implement the upgrade and minimize the number of possible issues. However, if the current version has little customizations. Then, there might be a chance to upgrade, but still the gap is big between the two versions.
Related
I am going to upgrade my OBIEE app which has 11.1.1.6 version to 12C version(12.2.1.3 or 12.2.14).
By searching on the internet, I have found some valuable documents or articles with regard to upgrade from 11.1.1.7 to 12C(not 11.1.1.6). As there are mostly tangible and fundamental changes from one version rather than higher one (when new version is released by Oracle co.), especially in terms of architecture, my concern is that it is possible to upgrade from 11.1.1.6 to 12C ?
Thanks in advance.
No, an upgrade directly from 11.1.1.6 to 12.2.1.4 is NOT supported. You shouldn't even try to use 12.2.1.3 anymore as it is an old 12c version.
You must do 11.1.1.6 to 11.1.1.7 or 11.1.1.9 (better 11.1.1.9) and then upgrade to 12.2.1.4.
I am currently working on USD 1.0 which is of-course a very old version of USD.
We are trying to move to the newest version of USD in my organization, which i believe is USD 4.0
I have tried searching the web but other than the MSDN article i have been able to gather much detail on this version.
I am trying to figure out my possibilities in trying to adapt to this newer version. In light of it, i have a few questions listed below,
Has Microsoft released only the preview/trial version of USD 4.0 yet? Or is it made available for general public which means we can access and start developing in our production environment?
Is the new version of USD, a web based version? I have heard that
this version is not the desktop application like it was before.
Will it be safe to migrate from USD 1.0 to USD 4.0?
Microsoft has also introduced Unified Client Interface, what is it?
Is it available only with USD 4.0?
Features comparison with USD 1.0?
If Microsoft have released the preview version only, then when will
they release the stable version? (any tentative date)?
Also, if they have released the preview version just then obviously they might change it in future. Therefore, it will not be wise enough to migrate to it if it is just a preview version.
Looking forward to your answers. Any sort of videos, articles, documentations, press releases, your personal opinions are welcome.
Thanks
Most 'manual' based MSDN information has been moved to Microsoft Docs: https://learn.microsoft.com
USD 4.x is still a desktop application that loads MSD components. You can upgrade to a more recent version 3.2 quite easily:
You can upgrade a Unified Service Desk 1.x or Unified Service Desk 2.0 sample application package to Unified Service Desk 3.2 by importing the Upgrade sample application package. The upgrade will not affect the configuration data associated with the existing solution.
Follow the steps here:
https://learn.microsoft.com/en-us/dynamics365/customer-engagement/unified-service-desk/admin/upgrade-unified-service-desk-solution?view=dynamics-usd-3
From there on forward it is much more easy to compare 3.x with 4.x and answer all your remaining questions.
Neil Parkhurst also has a ton of information.
https://neilparkhurst.com/2016/06/20/usd-the-book/
It is important to me to know whcih version of software should I use?
Last or Stable?
For example:
Laravel 5.5 (Stable) or Laravel 5.6 (Last)
cPanel 68.0.19 (Stable) or cPanel 68.1.1 (Last)
There are two options with Laravel:
Long Term Support
For those not familiar with long-term support, these are special versions that are feature locked at the date of release. They do not get any new features but keep getting bug fixes and security updates throughout the maintenance window.
For LTS releases, such as Laravel 5.5, bug fixes are provided for 2 years and security fixes are provided for 3 years. These releases provide the longest window of support and maintenance. For general releases, bug fixes are provided for 6 months and security fixes are provided for 1 year.
Version 5.1 was Laravel’s first LTS release.
LTS versions are popular with companies looking to reduce the risk, expense, and disruption of software deployment, while promoting the dependability of the software. It does not imply technical support.
Framework Releases
Major framework releases are released every six months (February and August), while minor releases may be released as often as every week. Minor releases should never contain breaking changes.
Using the latest release of the framework provides access to not only the latest security updates, but also new features. Updating your application to the latest release of the framework allows you to take advantage of new features and keeping migrations between subsequent versions relatively straightforward. It’s also an opportunity to refactor code to utilise the functionality of the framework. The work associated with upgrading is incremental, rather than the big jump between LTS versions.
If you follow the installation instructions (https://laravel.com/docs/5.5), you will be downloading the latest release of the framework.
As the question states, I am preparing to deploy my first couple modules on the Magento Connect store and want to make sure I am targeting the best versions. Testing on 1.3 is proving to be a bit of a pain, and if only a few people use that version I would rather spend the time making the modules better!
Google hasn't helped as yet, though I think the keywords I use are getting picked up as other more specific technical questions (Google Base, for example).
Does this information exist? What about your personal experience? For me, I have only encountered installations below 1.5 Community (1.10 Enterprise) for upgrade projects. I haven't personally encountered a client that is on 1.4 and plans to stay on 1.4.
Thanks!
Tim
There are a signification amount of people who have older versions and wont upgrade because of the complexity and the amount of modification they have done to their stores.
Most people right now who are on community version seem to be on 1.5 or 1.6, but if you want to test older versions just download from the archive install locally and see if it works for the older versions.
Here is a link to the downloadable versions of magento, in case you decide to test on those older versions:
http://www.magentocommerce.com/download - click released archived tab at the top
I was wondering, how often does DHTMLX offer a new version and how hard do you find it to upgrade your applications to the new version. This is namely a critical part in my research, but I cant seem to find any problems with updates. This question is just to make sure that my findings are correct.
Please suffice with: version number, DHTMLX component.
I work for DHTMLX. During the past 3 years we released one major update per year. Currently we're preparing the next version which we hope will be available in beta till the end of April 2012. We try to make the new releases backwards compatible and provide the upgrade path to the latest release (like here).
I've used many controls from the dhtmlxsuite in our app for the past 5 yrs. They are pretty good at making things backwards compatible, but not always. When going from v3 to v4 just a few months ago, there was quite a lot I had to do get my code back up and running. Also there dropped a few features that were supported in v3, this is not so good in my opinion. But overall, I really like the dhtmlx controls, they are an integral part of our product which now is used all over the world by thousands of users (http://www.ecosys.net/ecosys-epc/).