The content below is for Apache Syncope <= 1.2 - for later versions the Getting Started guide is available. |
Once you have created your project, you already have a set of tools for evaluating Syncope in a quite rich scenario, without the need of setting up additional components like JEE container, database, LDAP server and so on.
From the top-level directory of your project, execute:
mvn clean package |
then, from the console subdirectory execute:
mvn -P embedded |
Log files are available under
core/target/log console/target/log |
Syncope core is the main web application, exposing a set of RESTful services.
Syncope console is the administration interface for dealing with Syncope core.
Syncope core's persistence is based on JPA: this allows deployment on a wide range of DBMS; when running in embedded mode, H2 (in-memory) is used for internal storage.
A SQL web interface is available at http://localhost:9080/syncope/db.jsp:
Insert
jdbc:h2:mem:syncopedb |
as JDBC URL
(Do you want to understand what an external resource is? Check Connectors and resources).
An H2 TCP database is available for propagation.
A SQL web interface is available at http://localhost:9082/:
Insert
jdbc:h2:tcp://localhost:9092/mem:testdb |
as JDBC URL
(Do you want to understand what an external resource is? Check Connectors and resources).
An Apache DS instance is available for propagation.
You can configure any LDAP client (as JXplorer, for example) with the following information:
base DN:
o=isp |
bind DN:
uid=admin,ou=system |
(Do you want to understand what an external resource is? Check Connectors and resources).
An example SOAP server is available at http://localhost:9080/wssample/services.
You can check its internal storage by visiting http://localhost:9080/wssample/exploredb.jsp.