Subscription Information
This feature is supported with the Enterprise+ license.
JFrog Artifactory Edge (an "Edge node") is an edition of JFrog Artifactory whose available features have been customized to serve the primary purpose of distributing software to a runtime such as a data center, a point-of-sale or even a mobile device. All packages hosted in an Edge node are part of a Release Bundle which is a secure and immutable collection of software packages that make up a release to be provisioned or can be uploaded using direct file upload through the UI or REST API.
Note
Distributing Release Bundles REST API can be found here.
Before you get started - Establish a circle of trust
An Edge node can only receive Release Bundles from an Artifactory service if they are both within the same circle of trust. Once you have completed the installation of the Edge node, make sure to add it to the circle of trust for any Artifactory service from which it should receive Release Bundles. To learn how to establish a circle of trust, see Establishing the Circle of Trust.
Edge Installation Options
The process of installing an Edge node is identical to installing any other Artifactory instance. The following section details the process of installing Artifactory using Linux Archive a popular installation option. For other Artifactory installation options, see Installing Artifactory.
Install Artifactory single node with Linux Archive
Before you proceed with the installation, review the system requirements.
Artifactory Linux Archive Installation Steps
Complete the following steps to install the product.
Create a JFrog Home directory and move the downloaded installer archive into that directory.
For example:
mkdir jfrog mv jfrog-artifactory-<pro|oss|cpp-ce>-<version>-linux.tar.gz jfrog cd jfrog
Set the JFrog Home environment variable.
export JFROG_HOME=<full path of the jfrog directory>
To learn more about the system variable JFROG_HOME, see JFrog Home.
Extract the contents of the compressed archive and move it into the
artifactory
directory.tar -xvf jfrog-artifactory-<pro|oss|cpp-ce>-<version>-linux.tar.gz mv artifactory-<pro|oss|cpp-ce>-<version> artifactory
Customize the production configuration (optional) including database, Java Opts, and filestore.
Run Artifactory as a foreground or daemon process, or as a service.
Access Artifactory from your browser at:
http://SERVER_HOSTNAME:8082/ui/
. For example, on your local machine:http://localhost:8082/ui/
.Check Artifactory Log.
Configure log rotation of the console log
The
console.log
file can grow quickly since all services write to it. For more information, see configure the log rotation.
Artifactory Post-Installation Steps
Once the installation is complete, complete the following tasks.
Change the default admin password. The default user will have the following credentials predefined in the system:
User: admin, Password: password
Make sure you have applied your licenses
Continue to configure the system using the Artifactory Product Configuration
Configure a reverse proxy (optional for Docker Registry)
You can run Artifactory with one of the supported HTTP serversset up as a front end of each node.
Artifactory Linux Archive Install Script Commands
The following are the sequence of commands performed by the Linux Archive install script.
User creation |
To change the default user, edit the shared When running the service with a different user, make sure to update the shared.user and the shared |
artifactory default |
To modify your JVM parameters, modify the |
systemd or init |
|
Tomcat Preparation |
|
chkconfig calls |
|
Set ownership |
|
Run Artifactory as a process
You can run Artifactory as a foreground or as daemon process. When running as a foreground process, the console is locked and you can stop the process at any time.
To run as a foreground process $JFROG_HOME/artifactory/app/bin/artifactoryctl To run as a daemon process $JFROG_HOME/artifactory/app/bin/artifactoryctl start To manage the process $JFROG_HOME/artifactory/app/bin/artifactoryctl check|stop
Run Artifactory as a service
Artifactory is packaged as an archive file with a bundled Tomcat, and a complete install script that you can use to install it as a service running under a custom user. This is currently supported on Linux and Solaris systems.
When running Artifactory as a service, the installation script creates a user called artifactory
, which must have run and execute permissions on the installation directory. We recommended that you extract the Artifactory download file into a directory that gives run and execute permissions to all users such as /opt
.
To install Artifactory as a service, browse to the $JFROG_HOME/artifactory /app/bin
directory and execute the following command as root.
# USER (optional) - the user you want application to run as (default = artifactory) # GROUP (optional) - the group with which the application will run as. (default = artifactory) $JFROG_HOME/artifactory/app/bin/installService.sh [USER [GROUP]]
Manage the service
Use systemd
or init.d
commands depending on your system.
Using systemd systemctl <start|stop|status> artifactory.service Using init.d service artifactory <start|stop|check>
Add an Edge Node
After you install Artifactory, use the following steps to add the Artifactory Edge node.
Step 1: Optional: Enable the Replicator on Both Instances
The Replicator is a process that optimizes replication when distributing software with JFrog Distribution. You can enable a Replicator on both Artifactory instances. See Replicator Installation and Activation for more information.
Step 2: Establish a Circle of Trust
An Edge node can only receive Release Bundles from an Artifactory service if they are both within the same circle of trust. Establish a circle of trust by copying the root crt
from the source Artifactory to the trusted keys folder of the edge instance. For more information, see Establishing a Circle of Trust.
Step 3: Add the Edge Node to JFrog Mission Control
Using Platform Deployments, add the Artifactory Edge node to Mission Control. For more information, see Managing Platform Deployments.
Step 4: Add the Edge Node as a Target for Source Instance in Access Federation
Access Federation gives you control over access to all, or any subset of your services from one location by synchronizing all security entities (users, groups, permissions and access tokens) between the federated services. Once access federation has been set up, you can manage all security entities in the federated services from one place. For more information, see Access Federation.
Step 5: Add Signing Keys to JFrog Distribution
The JFrog Platform supports signing keys to establish trust with your clients for downloading your packages from Artifactory. Signing keys consist of a public and a private key pair, which are used for signing and verifying release bundles. When installing a new Edge, you will need to propagate the public keys to the new Edge. To learn about how to add and propagate keys, see GPG Signing.
Next step: Configuring Distribution