XNAT Plugin Model
A plugin is a compiled, self-contained package separate from your XNAT server but installed into the XNAT plugins folder. Once installed, the plugin runs in the same process space with XNAT as a fully integrated extension to the core XNAT server.
Plugins are written and contributed by the core XNAT team, the PIXI development team and by individual sites with specific needs that are not found in core XNAT.
Select & Download Plugins
Plugins are Java jar files that are added to the operating environment during the installation process. You can select and download the jar files as part of preparation for installation.
The PIXI plugin contains the essential software that extends XNAT for preclinical imaging. Please include that plugin as part of the installation process. The table below lists other plugins commonly used in the PIXI environment. These are available on the XNAT Downloads Page.
Extends Container Service
XNAT/Python Integrated Environment
Note that Container Service is required for using PIXI’s hotel image splitting feature.
XNAT can be deployed to support different environments ranging from a single user running on a laptop to a larger, enterprise-level system. This section provides overviews of the small and large environments.
The Dockerized version of XNAT can run on both Docker Desktop and the professional versions of Docker. XNAT provides a Docker Compose file that defines the environment for running the application. This is an appropriate environment for individuals to run on their laptop or desktop for evaluation and can also serve as the basis for a larger deployment. Instructions for this environment are provided in the next section.
Users with IT support who want a system that is available to a larger audience will want to understand the XNAT Administration documentation. This describes an environment where the XNAT software is running as a system service in a Linux environment and is available 24x7. Instructions are included for managing user authentication using an LDAP server (Windows Active Directory) and/or running XNAT behind a firewall with HTTPS-protected connections. For the steps listed on the XNAT Installation Guide page.
We recommend starting with the Dockerized version. You will have a functioning PIXI system within a few minutes and can learn the administrative functions and the application itself before investing more time with a production installation.
Run XNAT with Docker Compose
Use the following steps to quickly deploy an XNAT with the PIXI plugin using Docker Compose on your local system. You will need to have git and Docker installed as well as Docker Compose, which is typically included when you install Docker.
Clone the xnat-docker-compose repository:
git clone https://github.com/NrgXnat/xnat-docker-compose cd xnat-docker-compose
Put any XNAT plugin jars you want to use in the
xnat/pluginsfolder. Note you do not need to download the XNAT war file. It will be included as part of the Docker container.
PIXI can be dowloaded with the following command:
wget -q -P ./xnat/plugins/ https://github.com/preclinical-imaging/pixi-plugin/releases/download/v1.0.0/pixi-plugin-1.0.0.jar
Other helpful plugins can be downloaded with the following commands:wget -q -P ./xnat/plugins/ https://api.bitbucket.org/2.0/repositories/icrimaginginformatics/ohif-viewer-xnat-plugin/downloads/ohif-viewer-3.6.0.jar wget -q -P ./xnat/plugins/ https://api.bitbucket.org/2.0/repositories/xnatdev/container-service/downloads/container-service-3.4.1-fat.jar wget -q -P ./xnat/plugins/ https://api.bitbucket.org/2.0/repositories/xnatx/xnatx-batch-launch-plugin/downloads/batch-launch-0.6.0.jar
Initialize the XNAT docker compose environment variables. Review the .env file and make changes as appropriate.
cp default.env .env
Start XNAT with Docker Compose in detached mode:
docker compose up -d