What runnables are available?
This table lists all runnables run by ARIS server for a medium number of users installation. That's why all runnables end with _m. Installations for a small or a large number of users are typified with _s or _l. If ARIS was installed using the setup program, the default instance IDs are used as shown in the table.
Runnable | ARIS server | ARCM |
|---|---|---|
Runnables run by different server types | ||
Instance ID: zoo_m Name: Service registry Description: This runnable is a server component managing the communication, configuration and status information of all available runnables and external services. | x | x |
Instance ID: postgres_m Name: Modeling database Description: Internal standard database system storing all ARIS databases (modeling data) and the system databases (ARIS Method, filters, templates, languages, fonts, font formats and script data). This database can be replaced by an external Oracle® or Microsoft® SQL database. | x | x |
Instance ID: cloudsearch_m Name: Search index Description: Main full-text search and graph structure index for modeling data. It allows fast access to the data stored in the modeling database, Oracle® or Microsoft® SQL database. | x | x |
Instance ID: elastic_m Name: Document index (Elasticsearch) Description: Main full-text search index for documents and collaboration data. It also stores users, user groups, licenses, and privileges. | x | x |
Instance ID: adsadmin_m Name: ARIS document storage management Description: Server component managing ARIS document storage. | x | x |
Instance ID: umcadmin_m Name: ARIS Administration/User Management Description: Server component managing users, permissions, licenses, LDAP connectivity and SSO. | x | x |
Instance ID: loadbalancer_m Name: Load balancer Description: Central point of entry for all ARIS clients to the entire ARIS application, typically accessed via HTTP ports 80 or 1080, or HTTPS ports 443 or 1443. It distributes the workload across the installed components. | x | x |
Instance ID: abs_m Name: Main server component Description: Server component for modeling, publishing, and operations on modeling data including report execution. | x | x |
Instance ID: apg_m Name: Process Governance Description: Process Governance server component. Executes processes and provides managing user interfaces. | x | |
Instance ID: copernicus_m Name: Portal Description: Server component providing the published content in <connect>. | x | |
Instance ID: octopus_m Name: Analysis Description: Server component processing ad hoc analyses and queries triggered in ARIS Architect or ARIS Designer. | x | |
Instance ID: ecp_m Name: Collaboration Description: Server component of the collaboration component in ARIS. | x | |
Instance ID: simulation_m Name: Simulation Description: Server component of the simulation functionality in ARIS Architect. | x | |
Instance ID: dashboarding_m Name: Dashboards Description: Server component of the dashboarding component in ARIS. | x | |
Instance ID: arcm_m Name: ARIS Risk and Compliance server Description: Server component of ARIS Risk and Compliance. | x | |
Instance ID: hds_m (optional; not by setup) Name: Heavy-duty Server (HDS) Description: HDS is an additional component that reduces the load of ARIS reports running on you abs instance. | x | |
Instance ID: cdf_m (optional; not by setup) Name: Cloud Decoupling Framework (CDF) Description: CDF is a queue that can be used to decouple synchronous accesses to services. It is required for communication between the abs instance and the hds instance. If multiple arcm runnables are installed, a cdf runnable is mandatory. | x | |
Instance ID: ces_m (optional; not by setup) Name: Enterprise Search (CES) Description: CES is an extension that provides the powerful Enterprise Search. | x | |