I85PREP
⌘ K
JFrog Artifactory Certified DevOps Engineer study materials
JFrog Artifactory Certified DevOps Engineer study resources

JFrog Artifactory Certified DevOps Engineer: Installation and Configuration

JFrog Artifactory Certified DevOps Engineer · Work through your exam, one topic at a time.

All guide sections

Installation and Configuration

Installation and Configuration

This domain tests deploying Artifactory reproducibly, wiring external dependencies, and changing configuration without corrupting data.

Core rules

  • Install options include Docker images, Helm charts, RPM/DEB packages, and archives. In containers, persist $JFROG_HOME/artifactory/var and mount configuration rather than baking it into the image.
  • In Artifactory 7, system.yaml is the central configuration file for database, router, security, and shared settings. binarystore.xml defines the binary provider: filestore, S3, Azure Blob, or GCS.
  • Database settings must point to a supported external database for production. Provide the JDBC URL, driver, user, and password, and validate connectivity before starting the full stack.
  • A reverse proxy or load balancer terminates TLS and forwards to the Router. Configure trusted proxies and the public URL so generated links, Docker tokens, and package-manager redirects are correct.
  • HA requires a shared join key so nodes form a cluster, plus identical database and binarystore configuration. The master key encrypts sensitive configuration; back it up and reuse it across nodes and restores.

Worked example

You deploy Artifactory to Kubernetes. The Helm values reference an external PostgreSQL database, an S3 bucket, and a Kubernetes Secret containing the join key and master key. A PVC is not used for binaries because S3 is the binary store; the PVC only holds var/etc and logs. The ingress points to the Router service on port 8082 and sets the external URL. A new pod joins the cluster using the same join key and reads the same S3 bucket, so uploads through any pod are visible to all.

Traps

Losing the master key makes encrypted values unrecoverable. Changing binarystore.xml after artifacts exist without a migration leaves metadata pointing at missing binaries. Pointing the reverse proxy at the Artifactory service port instead of the Router breaks UI and token flows. Using a local filestore with multiple HA nodes splits binaries across pods.