Before diving into the migration process, it's essential to understand the foundational components that make up a JFrog Artifactory instance.
Artifactory consists of three core components:
Application Server (Artifactory Application)
This refers to the Artifactory application itself. It handles all Artifactory activities, including REST API requests, maintenance tasks, and replication. It requires a connection to a Database and filestore to operate.
Two key configuration files are saved on the server. The first is system.yaml, which defines the database connection (among other things). The second is the master.key, which is used to encrypt sensitive data in the database.
Database
Stores all Artifactory-related data, such as user details, groups, permissions, repository configurations, and metadata for each artifact, including names and full paths. It also stores all the configuration information relating to application settings.
Filestore (Binary Store)
Stores the actual binaries, organized by their SHA-1 checksum. Only the file itself is saved here; details like artifact name, path, and creation date are stored exclusively in the database.