Page tree
Skip to end of metadata
Go to start of metadata


A service is a component that is not in a workflow. You can send messages and receive responses, but the messages are not passed on to a next stage. Also, you must talk directly to the service rather than going through an Ingest Service or QueryReceiver. 


Expert Users Only!

To implement a custom service is an advanced task that typically requires a consultation with Attivio's Professional Services team.

View incoming links.


AIE Services

To see the list of active services in an AIE installation, use the AIE Administrator to view the System Management node, and the Services page. There you will see the current status of many AIE components that run as services.

Custom Service Configuration

To define services, define the component and then add it to <project-dir>\conf\services.xml.  For example:

<?xml version="1.0" encoding="UTF-8"?>

<component xmlns="" xmlns:xsi="" 
xsi:schemaLocation=" "/>

<?xml version="1.0" encoding="UTF-8"?>

<services xmlns="" 
xsi:schemaLocation=" ">
  <service name="scheduler"/>
  <service name="languageModelService"/>
  <service name="myCustomService"/>

Nodeset Configuration

If your project is a multi-node configuration, you might want to specify where your custom service runs. To do this, you typically edit the project's topology-layout.xml file, under the <topology> element. For example, if your configuration includes the following definition:

<?xml version="1.0" encoding="UTF-8"?>

<attivio xmlns="" 
xsi:schemaLocation=" ">
    <layout default-service-nodeset="*" default-ingest-nodeset="indexers" default-query-nodeset="searchers" default-connector-nodeset="connectors">
      <service-location name="scheduler" nodeset="admin"/>
      <service-location name="myCustomService" nodeset="customService"/>

In this example, a custom service would start on the nodes belonging to the customService nodeset.

  • No labels