• Product manuals

Browse the manual

• Introduction
  • Installation
• Basic usage
  • Handling passwords
  • Managing SSL certificates
  • Data objects, data files and the CLC URL
    • The CLC URL - name forms
    • The CLC URL - the ID form
    • Indicating local system files or folders
  • Result files and connecting analyses in pipelines
  • Executing workflows
  • Emptying the recycling bin for a CLC Server File Location

The CLC URL - name forms

The name forms of CLC URLs are listed below, along with the types of locations the refer to and an example.

• clc://server or clc://host:port Used to refer to data elements or directories in a CLC Server persistence model. The first entry after the URL is the name of the persistence, followed by the path to the data element within the persistence. For example, with a persistence called CLC_Server_Project, the CLC URL to a data element called myAlignment within a folder called alignments would be clc://server/CLC_Server_Project/alignments/myAlignment or clc://hostname:7777/CLC_Server_Project/alignments/myAlignment.

  Note that for CLC data in a persistence model, you need the name of the data element, as seen via the Navigation Area of a Workbench, not the name of the file itself, at the filesystem level.

• clc://local Used to refer to files on the local filesystem. To use this form, direct transfer from client systems must be allowed by the CLC Server. The full path to the file should be given after the URL. E.g. clc://local/home/myusername/project1/s_1_1.sequence.txt

• clc://serverfile Used to refer to files in an Import/Export area for the CLC Server. The full path to the file should be given after the URL. E.g. clc://serverfile/mnt/data/project1/s_1_1.sequence.txt

• clc://cloudfile Used to refer to files in an AWS S3 bucket. The full S3 address for the file should be given after the CLC URL, e.g. clc://cloudfile/s3://mys3location/subfoldername/mysequence.fastq

---