my random Artifactory notes

gistfile1.txt

1) Linux. Artifactory start/stop
# To Start
$ARTIFACTORY_HOME/bin/artifactory.sh (concole)
$ARTIFACTORY_HOME/bin/artifactoryctl start (daemon)
$ARTIFACTORY_HOME/bin/installService.sh [USER [GROUP]]     (service)
$ARTIFACTORY_HOME/bin/artifactoryctl check | stop

2) Install script 
Creates the folder /etc/opt/jfrog/artifactory, copies the configuration files there and creates a soft link in$ARTIFACTORY_HOME/etc

To modify your JVM parameters modify JAVA_OPTIONS in /etc/opt/jfrog/artifactory/default
The $ARTIFACTORY_HOME/tomcat/logs folder is linked to $ARTIFACTORY_HOME/logs/catalina

3) service artifactory start | stop
   service artifactory check
   If Artifactory is running, you should see its pid.
   If Artifactory is not running you will see a list of environment variables used by the service.
   
   Recommeneded JVM OPTS
   -server -Xms512m -Xmx2g -Xss256k -XX:PermSize=128m -XX:MaxPermSize=256m -XX:+UseG1GC
   In JDK 8 the PermSize and MaxPermSize parameters have been deprecated.
   
4) Backup and recovery
When uninstalling an RPM distribution of Artifactory, it will save the $ARTIFACTORY_HOME folder and create a backup folder at /var/opt/jfrog/ while preserving symbolic links to remote filestores.
After installing a new instance of Artifactory, you can recover the configuration and filestore from this backup by running the script $ARTIFACTORY_BINARY/bin/recover.backup.sh.

5) Artifactory uses Apache Commons Procrun http://commons.apache.org/proper/commons-daemon/procrun.html allow Windows users to wrap (mostly) Java applications (e.g. Tomcat) as a Windows service. 

6) On windows if installed as service
sc start|stop Artifactory
sc query Artifactory

7) Artifactory list path 
http://host:port/artifactory/list/repo-path
In the Simple Browser, an item that is not cached is indicated by an icon on its right when you hover over the item. In the List Browser, an item that is not cached is indicated by an arrow.

8) The WADL file is available at the following URL: http://server:port/artifactory/api/application.wadl

9) Artifacts in a local repository can be accessed directly using the following URL: http://<host>:<port>/artifactory/<local-repository-name>/<artifact-path>

10) Artifacts in a remote repository can be accessed directly using the following URL: http://<host>:<port>/artifactory/<remote-repository-name>/<artifact-path>
 To directly access artifacts that are already stored in the cache you can use the following URL:
http://<host>:<port>/artifactory/<remote-repository-name>-cache/<artifact-path> 

11) A remote repository acts as a proxy not as a mirror. Artifacts are not pre-fetched to a remote repository cache. They are only fetched and stored on demand when requested by a client.

12) By default, Artifactory uses a global virtual repository available at: http://<host>:<port>/artifactory/repo
    This repository contains all local and remote repositories.