Configuration

The XDI2 configuration files of xdi2-csp define three main components:

• A "registry" graph and messaging target
• A "prototype" graph and messaging target
• A "registry" messaging target factory

Configuring the "registry" graph

Create a file in /etc/xdi2/xdi2-csp.properties on your local filesystem:

cloudname   =  +testcsp
cloudnumber =  [+]!:uuid:9999
secrettokenglobalsalt = 00000000-0000-0000-0000-000000000000
secrettokendigest =  xdi2-digest:00000000-0000-0000-0000-000000000000:a7292f2347aef29a9e4c05d35764019106143a339b6e9bb39faee53103e1d6f55e49213d77d16a326a91bab0fc6885779d04e2e4470125720860cf54f872b3bb
discoveryservice = https://xdidiscoveryserviceote.xdi.net/

Set cloudname and cloudnumber appropriately.

Set secrettokenglobalsalt and secrettokendigest according to these instructions, or use the xdi2-tools utility to create these values.

Set discoveryservice to an XDI discovery service such as Neustar PROD, OTE, or others.

Storage

By default, the in-memory backend storage of XDI2 is used. To change this, edit the applicationContext.xml file and see here for options.