Title: HTTP entry points for Apache Stanbol services

The web interface of your Apache Stanbol installation provides information for the main HTTP entry points. Each resource comes with a web view that documents the matching RESTful API for applications. 

Depending on which launcher you use, you will get a different set of services. By choosing the __full launcher__, you will get everything including experimental components, if you choose the __stable launcher__ you will get the most stable components only.

*Note: all links on this page direct to [demo instances](http://dev.iks-project.eu) of Apache Stanbol. To be able to configure all services to your needs, you have run your own installation.*


## Stable Services

- [/engines](http://dev.iks-project.eu:8080/engines)

 This is a stateless interface to allow clients to submit content to be analyzed by the Enhancement Engines and get the resulting RDF enhancements at once without storing anything on the server-side.

- [/entityhub](http://dev.iks-project.eu:8080/entityhub)
 
 The Entityhub provides two main services: The entity network manages (external) referenced sites and lets one consume entity information, the Entityhub supports managing and using local entities.

- [/system/console](http://dev.iks-project.eu:8080/system/console/bundles)

 This is the OSGi administration console (for administrators and developers). The initial username / password is set to admin / admin. Use the console to add new bundles and activate, de-activate and configure components. The console can also be used to perform hot-(re)deployment of any OSGi bundles. 

 For instance to re-deploy a new version of this web interface, go to the <code>$STANBOL_HOME/enhancer/jersey</code> source folder and run the following command:

 <code>$ mvn install -o -DskipTests -PinstallBundle \
    -Dsling.url=http://localhost:8080/system/console</code>


## Services "in the Lab"

- [/sparql](http://dev.iks-project.eu:8081/sparql): This is the SPARQL endpoint for the Stanbol store. SPARQL is the standard query language the most commonly used to provide interactive access to semantic knowledge bases.


- [/contenthub](http://dev.iks-project.eu:8081/contenthub): This is a stateful interface to submit content to analyze and store the results on the server. It is then possible to browse the resulting enhanced content items. The longer-term goal of this endpoint is to implement faceted semantic search of the enhanced content items. (Note: Up to now, this endpoint is a proof of concept / experimental feature. It does not actually store the content on the disk, just in memory.)

- [/cmsadapter](http://dev.iks-project.eu:8081/cmsadapter): A component for bi-directional mapping of knowledge structures between CMIS or JCR content repositories and RDF models.


- [/ontonet](http://dev.iks-project.eu:8081/ontonet): Ontonet provides a controlled environment for managing ontologies and ontology networks and user sessions managing them.

	
- [/reasoners](http://dev.iks-project.eu:8081/reasoners): The reasoners are made for classification, consistency checking, and enrichment of an ontology. Reasoning services are provided through the built-in HermiT reasoner.


- [/rules](http://dev.iks-project.eu:8081/rules): The rules component lets you define rules to be used within the ontology networks and the reasoning services. 


- [/factstore](http://dev.iks-project.eu:8081/factstore): The FactStore implements a store for facts plus the ability to query for single facts and for combinations of facts. It implements:
	- Persistence storage for n-ary facts about entities
	- Query language to query for a single fact
	- Query language to query for combinations of facts (reasoning)