Overview #
Repository Configuration manages where DnXT stores and accesses the files that make up your regulatory submissions — documents, PDFs, XML backbone files, and supporting materials. DnXT supports multiple storage backends, from local or network file systems to cloud-based document management platforms like Veeva Vault, Egnyte, and Box.
Proper repository configuration is essential because both DnXT Publisher and DnXT Reviewer depend on accessible, well-organized file storage to function correctly. This guide covers all four repository types available in the Repository Configuration tab.
Accessing Repository Configuration #
- Log in to DnXT Administrator.
- Click Configurations in the left sidebar.
- Select the Repository Configuration tab.
- The Repository Configuration view displays sub-tabs for each supported storage type: File System, Veeva Vault, Egnyte, and Box.
File System Repository #
The File System sub-tab is the most common repository type. It connects DnXT to local or network-mounted file system folders where eCTD submission files are stored.
Folder Browser #
The File System configuration includes an interactive folder browser that displays the directory structure accessible to the DnXT server. You can navigate the folder tree to locate and select repository root folders.
Registering a File System Repository #
- Navigate to Repository Configuration > File System.
- Use the folder browser to navigate to the desired directory.
- Select the folder you want to register as a repository root.
- Click Register.
- The folder is now registered as a DnXT repository. It will appear in the registered repositories list and become available for use in Publisher and Reviewer.
Unregistering a Repository #
- In the folder browser, locate the registered repository (marked with a registration indicator).
- Select the folder.
- Click Unregister.
- Confirm the action in the dialog.
File System Best Practices #
- Use dedicated volumes — Store repository data on dedicated disk volumes or network shares separate from the DnXT application server to avoid disk space conflicts.
- Ensure server access — The DnXT application server must have read/write access to the repository path. For network shares, verify that the service account running DnXT has appropriate permissions.
- Plan folder structure — Organize repositories by purpose (e.g.,
/repos/production,/repos/archive) to make management easier. - Monitor disk space — eCTD submissions can be large. Set up monitoring alerts for disk usage on repository volumes.
Veeva Vault Integration #
The Veeva Vault sub-tab configures integration with Veeva Vault, a cloud-based content management platform widely used in the life sciences industry. When configured, DnXT can read documents from and write submissions to your Veeva Vault instance.
Veeva Vault Configuration Fields #
| Field | Description |
|---|---|
| Vault URL | The base URL of your Veeva Vault instance (e.g., https://yourcompany.veevavault.com) |
| Username | The API user account for authentication |
| Password | The API user password |
| API Version | The Vault API version to use |
| Repository Path | The root path within Vault for DnXT content |
Setting Up Veeva Vault #
- Navigate to Repository Configuration > Veeva Vault.
- Enter the Vault URL for your Veeva Vault instance.
- Enter the Username and Password for the API service account.
- Select the API Version.
- Specify the Repository Path within Vault.
- Click Save.
- Test the connection by clicking the Test Connection button (if available).
Egnyte Integration #
The Egnyte sub-tab configures integration with Egnyte, a cloud file sharing and governance platform. DnXT uses Egnyte’s API to access documents stored in your Egnyte domain.
Egnyte Configuration Fields #
| Field | Description |
|---|---|
| Domain | Your Egnyte domain name (e.g., yourcompany.egnyte.com) |
| Client ID | The OAuth client ID for the DnXT integration app |
| Client Secret | The OAuth client secret |
| Access Token | The OAuth access token for API calls |
| Root Path | The root folder path within Egnyte for DnXT content |
Setting Up Egnyte #
- Navigate to Repository Configuration > Egnyte.
- Enter your Domain.
- Enter the Client ID and Client Secret from your Egnyte developer console.
- Provide the Access Token (obtained through Egnyte’s OAuth flow).
- Specify the Root Path for DnXT content.
- Click Save.
Box Integration #
The Box sub-tab configures integration with Box, a cloud content management and collaboration platform. DnXT connects to Box using the Box API to read and write submission files.
Box Configuration Fields #
| Field | Description |
|---|---|
| Client ID | The Box app’s Client ID |
| Client Secret | The Box app’s Client Secret |
| Enterprise ID | Your Box enterprise identifier |
| Public Key ID | The public key identifier for JWT authentication |
| Private Key | The RSA private key for JWT authentication |
| Passphrase | The private key passphrase |
| Root Folder ID | The Box folder ID that serves as the root for DnXT content |
Setting Up Box #
- Navigate to Repository Configuration > Box.
- Create a Box Custom App with Server Authentication (JWT) in the Box Developer Console.
- Enter the Client ID, Client Secret, and Enterprise ID from your Box app settings.
- Generate a public/private key pair in the Box app configuration.
- Enter the Public Key ID, Private Key, and Passphrase.
- Specify the Root Folder ID (the Box folder ID for DnXT content).
- Click Save.
Choosing the Right Repository Type #
| Repository Type | Best For | Considerations |
|---|---|---|
| File System | On-premises deployments, direct file access, highest performance | Requires server-level file access; you manage backups and storage |
| Veeva Vault | Organizations already using Veeva for content management | Requires Veeva Vault license; content governance handled by Vault |
| Egnyte | Organizations using Egnyte for file sharing and governance | Requires Egnyte license; good for hybrid cloud/on-prem environments |
| Box | Organizations using Box for enterprise content management | Requires Box Enterprise license; JWT server authentication |
FAQ #
Can I use multiple repository types simultaneously? #
Yes. You can configure and use multiple repository types at the same time. For example, you might use a File System repository for active submissions and Veeva Vault for archived content. Each dossier is associated with a specific repository.
What happens to existing files if I change repository configuration? #
Changing configuration settings (like paths or credentials) does not move or modify files. If you change a path, DnXT will look for files at the new location. Ensure files are migrated to the new location before updating the configuration.
How do I migrate files between repositories? #
DnXT does not provide a built-in repository migration tool. To migrate, manually copy or move files to the new repository location, then update the repository configuration to point to the new location. Test with a single dossier before migrating everything.
Does DnXT support Amazon S3 or Azure Blob Storage? #
DnXT’s built-in repository types are File System, Veeva Vault, Egnyte, and Box. For S3 or Azure Blob, you can mount the cloud storage as a file system (using tools like s3fs or Azure Blob Fuse) and register it as a File System repository.
What permissions does the DnXT service account need on the file system? #
The service account running the DnXT application server needs read and write access to all registered repository paths. For network shares, this typically means the service account must be a member of a group with full control over the share.
