We have Artifactory Pro license version 7.27.10. As an Admin we don't see the Projects tab in the UI. Do we need the Enterprise or Enterprise+ license?
From Artifactory 7.17.4, Projects is enabled by default in the JFrog Platform for Enterprise and Enterprise+ subscriptions, as stated in the JFrog wiki page HERE
That said, from Artifactory 7.31.10, the JFrog Projects feature is supported on all JFrog Subscriptions, as follows:
All JFrog subscription types can create up to three projects in parallel to JFrog supporting extended usage of 30 projects for Enterprise subscriptions, and 300 projects for Enterprise+ subscriptions.
For further read please refer to HERE
I haven't been able to find any documentation on how to migrate Nexus 3.X.X (LATEST) OSS to PRO? Have anyone done that before?
There isn't any need to migrate, all you need to do is install your license into your current Nexus 3.x OSS instance:
https://help.sonatype.com/display/NXRM3/License+Management
I operate some Docker services. Some of them are selfmade with Dockerfiles. I now want to store them into a Sonatype Nexus private repository to publish them to another server in my network.
My research half a year ago gave me Nexus 2 OSS as best option. But now Nexus 3 got released and I'm kinda confused. What version should I use? Greatest confusion is because there is no difference between Pro and OSS version anymore on Docker Hub:
sonatype/nexus has got tags oss and pro
sonatype/nexus3 has only got tags like 3.x.x
Question is: May I use Nexus 3 for free? Or will there be any costs as in Nexus 2 Pro?
Nexus Repository Manager 2 does not support Docker as a format. Nexus Repository Manager 3 does, and Docker support is a part of our OSS solution, meaning you can use Docker completely free. There is a professional version coming with 3.1 that will start to have features such as high availability, expanded enterprise support, as well as just regular support of the product.
As for the Docker images, Nexus 3 now has the ability to operate as OSS or Pro from the same bundle so you'll likely only see tags for Releases, not OSS and Pro.
Im trying to install Tools for Apache Cordova for Visual Studio. In the first step I need to choose which third party dep. to install.
But Ive already installed most of them and already developing on this machine using cordova/node commandline-tools.
Do I need to reinstall all dependencies again? or just some (if yes, which ones?)
The installer for Tools for Apache Cordova automatically detects which software are already present on the machine. Depending whether you are installing for Visual Studio 2013 or 2015, the experience may seem a little different.
After install completes, all required tools will also be configured as expected. It is best to run the installer once to ensure that there are no incompatibilities, but rest assured, it will not re-install existing compatible software.
It is good to let Tools for Apache Cordova for Visual Studio install the 3rd party software because it will install and also configure the machine. If you want to install just the missing software manually then refer the list of dependencies here under Install dependencies manually section and accordingly install the required software and configure the machine.
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