Setting up Custom Profiles

Create a directory to contain the configuration and data files for the custom profile.

The directory name must be 1 or more characters consisting of 0-9, A-Z, a-z, underscore or hyphen and no more than 80 characters long. It cannot contain spaces. It can be anywhere on your server; it does not have to be in the Rosette Server directory structure. This is the profile-data-root.
Create a subdirectory for each profile, identified by a profileId.

For each profile, create a subdirectory named profileID in the profile-data-root. The profile-path for a project is profile-data-root/profileId.
For example, let's assume our profile-data-root is rosette-users, and we have two profiles: group1 and group2. We would have the following profile-paths:
```
rosette-users/group1
rosette-users/group2
```
Edit the Rosette Server configuration files to look for the profile directories.

The configuration files are in the launcher/config/ directory. Set the profile-data-root value in these files:
- com.basistech.ws.worker.cfg
- com.basistech.ws.frontend.cfg
```
# profile data root folder that may contain profile-id/{rex,tcat} etc
profile-data-root=file:///Users/rosette-users
```
Add the customization files for each profile. They may be configuration and/or data files.

When you call the API, add "profileId" = "myProfileId" to the body of the call.

{"content": "The black bear fought the white tiger at London Zoo.",
 "profileId": "group1"
}