Using the latest version?
JFrog Platform User Guide
JFrog Artifactory 6.x Documentation
To get the latest version, go to the JFrog Unified Platform
Getting Started with Artifactory Enterprise Plus
JFrog Mission Control is required
To fully benefit from the capabilities of JFrog Enterprise+, your Artifactory Enterprise+ installation must be added as a service in JFrog Mission Control. Before you install your Artifactory Enterprise+ instance, make sure you have JFrog Mission Control running and ready to include the Artifactory Enterprise+ instance you are about to install.
To start using Artifactory Enterprise+, you need to take the following steps:
- Install Artifactory
- Add Artifactory as a service in JFrog Mission Control
- Modify your NGINX configuration
- Activate Artifactory with an Enterprise+ license
Installing Artifactory Enterprise Plus
To install Artifactory Enterprise+, install Artifactory as an HA cluster or as an individual instance using the usual process and activate it with an Enterprise+ license.
To install Artifactory Enterprise+ as an HA cluster, please refer to HA Installation and Setup
To install an individual Artifactory Enterprise+ instance, please refer to Installing Artifactory
Adding Artifactory Enterprise Plus as a Service in Mission Control
Activation of Enterprise+ services is managed through JFrog Mission Control.
Therefore, to activate your newly installed Artifactory Enterprise+ cluster (or instance), you first need to add it as a service to JFrog Mission Control as described in Managing Services in the JFrog Mission Control User Guide.
Modify NGINX Configuration
As part of the distribution flow, Artifactory needs to interact with JFrog Distribution which relies on HTTP/1.1 protocol functionalities, such as chunked transfer encoding. To support these functionalities, you need to add the following settings to your NGINX configuration:
For the following api: api/replication/replicate/file/streaming, you will have to disable response buffering. One way to do it is to configure a sublocation under the artifactory location as following:
Artifactory Enterprise+ licenses are managed with license buckets through JFrog Mission Control
Once your Artifactory Enterprise+ cluster (or instance) has been added as a service in Mission Control, you can assign it with an Enterprise+ license as described in Attaching and Detaching Licenses in the JFrog Mission Control User Guide.
Enterprise Plus Licensing for Artifactory HA
All nodes must have an Enterprise+ license
To provide the full functionality available with JFrog Enterprise+, each node of Artifactory HA cluster must be activated with an Enterprise+ license.
What if any of the nodes only has an Enterprise (not +) license?
If any of the nodes is activated with an Enterprise license (i.e.not Enterprise+), then the whole cluster will only provide functionality available with Artifactory Enterprise (such as S3 storage, filestore sharding, multi-push replication etc.)
What if any of the nodes has no license, or an invalid or expired license?
If any of the nodes is missing alicense,or has an invalid or expired license, the functionality available from the cluster will be very limited and uploading or download a package, or use of the REST API will be blocked (this is the normal behavior of an HA cluster with a missing or invalid license).
How are licensing managed when i add a new node of replace a node in Artifactory HA?
During E+ setup, licenses are added through Mission Control. While adding a service, the license is extracted from the license bucket. Everytime, users have to manually configure the services for licenses, when a new node is added or swapped while HA setup.