Configuration

The XDI2 configuration of xdi2-selfhosted defines a single "self-hosted" graph and messaging target.

Configuring the self-hosted graph

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

cloudname   =  =alice
cloudnumber =  [=]!:uuid:1111
secrettokenglobalsalt = 00000000-0000-0000-0000-000000000000
secrettokendigest =  xdi2-digest:ec136367-5969-4e69-9c8a-483e330c317f:8a447e411aad21477b67b8793e5be16749416b996c61a40476c17231be4d9390a8e703b87cf8750b66fb541f2088799d3b564ee6ed33cae8f9f84ce39c1527e62e
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.