> For the complete documentation index, see [llms.txt](https://indigo-dc.gitbook.io/indigo-paas-orchestrator/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://indigo-dc.gitbook.io/indigo-paas-orchestrator/service_reference_card.md).

# Service Reference Card

* Daemons running
  * `/usr/lib/jvm/java/bin/java` (inside the docker container)
* Init scripts and options
  * Started as a docker container (`docker run`)
* Configuration files location with example or template
  * The configuration parameters are provided through environment variables of the docker run command
* Logfile locations (and management) and other useful audit information
  * logs can be retrieved with the `docker logs` command
* Open ports
  * `8080` HTTP port
* Possible unit test of the service
  * Continuous unit tests are conducted during development via [Jenkins](https://jenkins.indigo-datacloud.eu/blue/organizations/jenkins/Pipeline-as-code%2Forchestrator/activity).
* Where is service state held (and can it be rebuilt)
  * The service state is held in two attached DBs; it can be rebuilt from SQL dumps
* Cron jobs
  * **NONE**
* Security information
  * Access control Mechanism description (authentication & authorization)
    * IAM OAuth2 bearer token (`RFC 6750`)
  * Firewall configuration
    * Outbound traffic must be allowed to every port and addresses
    * Inbound traffic must be allowed to HTTP port from any addresses
  * Security recommendations
    * It's advised to put the orchestrator behind a reverse proxy with HTTPS enabled


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://indigo-dc.gitbook.io/indigo-paas-orchestrator/service_reference_card.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.