Getting started

Using UNICORE

If you are an end-user or application developer who wishes to use an existing UNICORE installation, have a look at the user documentation for the UNICORE Commandline Client, the PyUNICORE client library or the REST API documentation.

Evaluating UNICORE

If you wish to experiment with a UNICORE server installation or wish to quickly evaluate UNICORE’s features, you can try our UNICORE Docker image.

Also, you can download the Core Server Bundle which can be installed very quickly on a single test machine or even your laptop.

Deploying UNICORE

Full production deployments of UNICORE range from minimalistic to rather complex, depending on your requirements, use cases and existing infrastructure.

A few starting points:

for each target resource (e.g. a compute cluster) you need a TSI and a UNICORE/X The TSI is deployed on the cluster login node(s), while UNICORE/X requires a VM or server, UNICORE/X should NOT be run on a machine where users can log in.
we strongly recommend running a Gateway, one for all of an institution/company’s UNICORE services is enough. This will shield the services from direct external access for added security.
For the services (except TSI where this is optional), you will need server certificate(s) from a CA (similar to a web server)
for multi-site workflows, you will need a Registry and a Workflow service

You can always contact us for advice in your specific situation.