Bootstrap

The Bootstrap Repository Connector is used for quickly generating dummy files and metadata to test things such as mappings and tasks.

The basic setup gives a number of ranges for specific metadata fields for each file.

Metadata

Files generated by this connector will have the following metadata:

  • Document Length

  • Document Mimetype (Content Type)

  • A Parent folder path

  • A Last Modified Date

  • A Created Date

  • If Include Binaries is checked under Advanced Settings, a fake binary within the configured size range will be attached to the metadata.

  • Files will have a randomised name of letters and numbers and will be of a randomized mimetype from the following list of extensions:

    eml

    png

    csv

    mp3

    mp4

    eml

    mpeg

    zip

    txt

    css

    html

    mp3

    doc

    xls

    ppt

    xml

    pdf

Integration Connection

Every job requires an integration connection for both the source repository connection and the output connection. Also known as input an output connections. Their job is to query or crawl remote systems for files, folders, metadata, versions, and renditions. . In repo mode, it will retrieve list items and all of their relevant metadata from a list or library on the specified site. In output mode, the connection will write content and assign the mapped content type (from type mappings), or simply leave the new list item as a Document. Click here for more information on setting up an integration connection.

  1. Select integration and click on the new connection button.

  2. Enter the name and description of your connection.

  3. Select the connection type from the drop down list.

  4. Click Save on the Create Connection form.

  5. Click Save on the Edit Connection page.

There are no fields to configure in an integration connection.

Guide toIntegration connections

Job Configuration

A 3Sixty Job is the process of moving or syncing content (including versions, ACL's, metadata) from one CMS (content management system) to another. Add tasks to your job to have better control over how your data gets migrated. Click here for details on how to set up an integration job.

Guide to Integration jobs

  1. Select List Jobs under integration on the navigation menu or the dashboard

  2. Click the create job button

  3. In the New Job form

    1. Name the job

    2. Select Simple Migration from the job type drop down

    3. Select the Repository Connection

    4. Select the Output connection

    5. Select your Content Service Connection

      (Only required if you will be using Federation)

    6. Click Save to open the Edit Job page

    7. Fill in the configurations for the Repo and Output Configuration tabs

  4. Click save to save your new integration job

  1. Select Run and Monitor Jobs under Integration in the navigation menu

  2. Click the play button next to the job you want to run

  3. Click the refresh button to view your completed job status

    (Larger jobs will take longer to run)

When the Bootstrap connector has been selected as the repository connector of a given job, additional configurations will need to be provided within the Job.

Basic Configuration

Use this when you need to quickly generate files

Note:  FILE CONTENT
If Include Binaries in the Details tab is checked, the dummy files will include a file which matches the size on the metadata. The content of the file will not be particularly useful.

  • Number of files to generate: This is a count of individual files, not batches of files.

  • Parent path base: Sets the parent path metadata for the files being generated.

  • Creation Date Range Start : The first possible date for the Created Date metadata

  • Creation Date Range End : The last possible date for the Created Date metadata

  • Last Modified Date Range Start : The first possible date for the Last Modified Date metadata

  • Last Modified Date Range End : The last possible date for the Last Modified Date metadata

  • Size Range Start (Bytes): The minimum size of the document

  • Size Range End (Bytes): The maximum size of the document

  • Allow for non standard mimetypes: Expands the list of mimetypes (200+)

Advanced Configuration

  • Config File Location: This is the location where the config/properties file resides

  • File Generator: Type of file generator (Random or Linear)

Advanced Configuration Properties

  • outputRootDir (string): The root output folder for each document's parent

  • path.templateDir (string): folder which contains template files to use as content

  • numberOfFiles (int): number of files to create per repository thread

  • maxFilesInTree (int): Limits number of files per folder tree

  • folderPattern (string): A pattern using date parts that will create a parent based on the current date and pattern. Default pattern is /yyyy/M/dd/kk/mm/ss/(kk is hours)

  • File Names (String): File names will take the format[name.first][name.middle][name.last].

Each of the following properties should be a path to a text file with a list of options for file names.

  • name.first.file

  • name.middle.file

  • name.last.file

API Keys

Bootstrap Connector: Read=true: Write=false: MIP=false

Repo (Read) Specs

Key

Description

Data Type
bootInfo Basic configuration will only create basic metadata. If Include Binaries is checked, a file of random bytes equal to the size property will be created.  

numFiles

Number of files to generate

Integer

parentPath

Parent path base

String

createRangeStart

Creation Date Range Start

String

createRangeEnd

Creation Date Range End

String

modifiedRangeStart

Last Modified Date Range Start

String

modifiedRangeEnd

Last Modified Date Range End

String

sizeRangeStart

Size Range Start (Bytes)

Integer

sizeRangeEnd

Size Range End (Bytes)

Integer

useAllMime

Allow for nonstandard mimetypes (200+ types)

Boolean

bootInfoAdv

Populating the config file field will override all basic configuration.

 

configfile

Config File Location

String

generator

File Generator

String

Need help using the Bootstrap Connector? We can help.