Step 1. Launch Aspire and open the Content Source Management Page

Launch Aspire (if it's not already running). See:

• Launch Control

• Browse to: http://localhost:50505. For details on using the Aspire Content Source Management page, please refer to Admin UI

Step 2. Add a new Content Source

• For this step please follow the step from the Configuration Tutorial of the connector of you choice, please refer to Connector list

Step 3. Add a new Publish to File to the Workflow

To add a Publish to File drag from the Publish to File rule from the Workflow Library and drop to the Workflow Tree where you want to add it. This will automatically open the Publish to File window for the configuration of the publisher.

Step 3a. Specify Publisher Information

 In the Publish to File window, specify the connection information to publish to the log file.

1. Name: Enter the name of the publisher. (This name must be unique).

2. Number of logged jobs: Indicates the number of jobs to retain at the logger (default is 5).
3. Log file type: Choose between the two options to log files
   1. File name: Is the path to the file where the jobs are going to be written, the default is ${app.name}/publishToFile.jobs. This option will manage one file
   2. Log file directory: Is the path to the file where the jobs are going to be written, the default is ${app.name}/publishToFileLogs. This option will create one log file for each batch it receives.
4. Debug:  Check if you want to run the publisher in debug mode.
5. Click on the Add button.

Once you've clicked on the Add button, it will take a moment for Aspire to download all of the necessary components (the Jar files) from the Maven repository and load them into Aspire. Once that's done, the publisher will appear in the Workflow Tree.