After scouting numerous articles and stack overflow for hours it seems that the IBM Database Add-Ins are not supported for Visual Studio 2019. Do correct me if I'm wrong.
Reasons for installing the Add Ins was to create entity classes in asp.net using web forms.
IBM Database Version : DB2 LUW 10.5
Reasons for the conclusions:
Installed the same fix packs for the IBM Data Server Driver Package as well as IBM Database Add-Ins for Visual Studio (Fix Pack 11) https://www.ibm.com/support/pages/node/3501195
Log Error Message : MSI (c) (98:58) [17:45:41:129]: Windows Installer installed the product. Product Name: IBM Database Add-Ins for Visual Studio, Product Version: 10.5.1100.2866, Product Language: 1041, Manufacturer: Company Name, Installation Success or Error Status: 1603
If the add in does not support Visual Studio 2019 , what would be the best replacement for Entity Framework 6.0 in order to use with IBM Db2?
If the add in does support Visual Studio 2019 is there a workaround to the following problem?
To get paid support (from IBM) for Visual-Studio 2019 in Db2, you need to have the visual studio add in that comes with Db2 v11.5.
For Db2 V10.5, it supports up to Visual Studio 2013.
It does not mean it will not work with older Db2 versions, but when you have issues (which is very likely), you won't get much help from IBM unless you have the right versions. You might be able to devise workarounds in some cases, but why bother?
If you are paying for a licence for Db2, pay for the current version and get the relevant paid support included. If you are not paying (for example, you are using a community edition) then get the latest version anyway. There seems no genuine reason for using the (out of support) Db2 v10.5 build if you are trying to use it with Microsoft software that was developed long after Db2 v10.5 was created.
Here is the link to the page that shows Db2 v11.5 supports Visual Studio 2019.
https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.swg.vs.addins.doc/html/ibmdevtsk-MigratingDB2Projects.htm
I checked to install the BizTalk SDK during my setup, and this is what I now see in the SDK folder:
I don't see the old SDK that came in some prior releases (link). I searched my entire disk for *.odx looking for SDK and didn't find any (other than the VS orchestration Template).
I did a Google search for download BizTalk 2020 SDK and nothing of interest showed up.
BizTalk 2020 Deprecated & Removed List
Samples: Removed from BizTalk Server installation.
So they just aren't available I would say.
Is there any hidden tool from MS we can use for BizTalk application migration prior to load solution into VS2015 ? I need some information about what are characteristic we may need to change specially BizTalk.btproj solution to load all project file etc., wonder to know easy approach migrating BizTalk application solution if any.
As various blogs posts and MSDN threads you needed to have an intermediate Development BizTalk environment (BizTalk 2010) and then upgrading it to the later version like BizTalk 2013/R2 and up.
You can download the developer edition here and install the SDK so you can open it in Visual Studio.
The only other way to migrate is to create new BizTalk Projects in Visual Studio 2015 / BizTalk 2016 environment, and then copying the artefacts such as Schemas, maps and re-creating any Orchestrations.
In either case you will have to do extensive retesting as there are certain changes such as the XSLT compiled transform that may cause you issues
No need for a hidden tool. Visual Studio is the tool.
When you open a downlevel Solution, Visual Studio will attempt to update any project and provide a report of what was automatically updated and what could not be updated, requiring manual intervention.
You can do this on a copy of you Solution to get a preview of any work necessary for the real upgrade.
Coming from BizTalk Server 2006, you will need an intermediate version to eventually target BizTalk Server 2016. You can download BizTalk Server 2010 from MSDN. All you need to install is the SDK. You don't need to setup/configure full BizTalk Server.
We recently changed to a new BizTalk version from 2010. We are trying to configure our first ReceivePort on it, but we are running into the error that seems to indicate that the version of the Oracle.DataAcces that is in the cache is very outdated.
I have been looking around but unfortunately, i am not an expert in how the GAC works so i haven't figured out how BizTalk selects which version to search for.
Would the solution be to Install a newer version of the Oracle Dataacces into the GAC? And is the Oracle Data adapter part of the BizTalk adapter pack? That Pack was pre installed on our server so it would be weird if it was the cause of the wrong version.
Edit: The ODAC we installed claims to be the version 4 one (in the read me and download link) but doesn't seem to be the one in the cache.
You MUST install Microsoft BizTalk Adapter for Enterprise Application. if you are using the same box that you used for BTS 2010, then Uninstall, the Old Adapter pack, and install the new one from BTS Media.
We’re thinking about downgrading our Alfresco Enterprise 3.4.1 to Alfresco Community.
I’m used to Alfresco Enterprise, but I have no experience with Community version.
We’re using EMC, Alfresco Explorer and our own development based on Web Services API and Foundation API.
I’m worried about database migration. Could I simply configure Alfresco Community 3.4.e to use our Oracle Database for Alfresco Enterprise 3.4.1? Is the schema compatible for both Community and Enterprise distributions? Which version of Alfresco Community should I use? 3.4.e? What is the downgrade path between distributions? Is there any kind of correspondence between versions of both distributions?
Any downgrade experience, guide or any related information will be welcomed.
The Alfresco Community Edition is open source, and works with a fully open source stack. Your DB options are PostGreSQL (recommended) or MySQL.
Alfresco Enterprise supports the open source databases that Community supports, PostGreSQL and MySQL, as well as a few proprietary databases too. You can look at the Database Configuration page for more information. Support for Oracle databases is only available in Enterprise.
If you want to keep paying Oracle all that money for your database licenses, then you'll need to continue to pay a tiny fraction of that cost to Alfresco for an Enterprise License. Community, being open source, only supports a fully open source stack, so you can't use Community with your uber expensive proprietary database!
If you were using an open source database like PostGreSQL or MySQL, then you might be able to do the switch as part of an upgrade. Enterprise Service Packs (eg 3.4.1) are normally newer than the equivalent community release from that series (Community gets the bug fixes on Head). Moving from a 3.4.x enterprise service pack back to a 3.4 community wouldn't be recommended, but moving from 3.4.x enterprise to a 4.x community might work. However, that's not a tested migration path, so you could well be on your own... Alfresco QA tests community -> newer community, enterprise -> newer enterprise, and community upgrading to enterprise, which are the supported paths.
This question is similar with this one about difference between Community and Enterprise version
You can not use Oracle database for Community version. It is only available for Enterprise.
There is not downgrade path for any Alfresco versions. If you are using Enterprise 3.4.2 try to use the same Community version.
I searched the web for possibilities of a downgrade from enterprise to community version, too. What I found is the answer "You may be able to downgrade, however that is never supported or tested."
When downgrading, you have to keep in mind that the community version X usually has more functionalities than the enterprise version with the same version number.
So, downgrading is experimental. I have already seen log files where the downgrade failed.
Maybe it is an option for you to export all content and import this ACP file on the new system with the community version?
Please read your contract carefully. Support and Licensing might not be the same thing in your case. If you don't want to pay anymore to Alfresco, you might be entitled to keep using your current enterprise version, but you would not longer have support. Before considering downgrading, check your contract. If in the future you want to get support and upgrade again, it might just be easier to do it with your current Alfresco Enterprise version.
But, as I said, it depends on your agreement with Alfresco.
Migration of the Alfresco repo database is no fun at all. There is no official way switching databases and in 3.x version you may have serialized objects which could be stored by hibernate db specific. This changed a little when Alfresco removed most of hibernate dependencies after 3.4. It may be an option to migrate to 4.0 EE first, migrate the db to postgres (which is closer to oracle than mysql) and finally upgrade to Alfresco Community 4.2.f (latest version with Web Services API). This may be a lot of work (even in your code) but should work.
Here in Germany it is legaly problematic to limit software usage in time if you sell a support subscription (at least for the old contracts you may have) so customers here can request support for a time unlimited EE license key before canceling the subscription contract. I recommend you go this way and update your old 3.4 to the latest 3.4.x or 4.x enterprise version available and stay on Oracle db if you don't care these costs. This step should be done anyway ;-)
I have done it before in order to create a development environment in my local machine,
First, you cannot use Oracle database so you have to use postgresql (recommended) or MySql, exporting and importing the database is not recommended, so you have to create the repository hierarchy and fix the rules, etc., then copy all custom jars (jobs, actions, workflows...) and library from the lib folder to the new one,
If you are using an external application based on alfresco uuids, make sure you updated the uuids after creating the repositories and rules