Page History

...

cd /opt/opendj.0/bin 
./start-ds
See /tmp/opends-setup-7855637320320628455.log for a detailed log of this operation.
Configuring Directory Server ..... Done.
Creating Base Entry dc=tin-pham,dc=com ..... Done.
Starting Directory Server .......... Done.
To see basic server configuration status and configuration you can launch /opt/opendj.0/bin/status

Create Data Stores

During the OpenAM uses installation, two data stores will be are created,

1. Configuration
2. User

Be default we already have a branch for Users under dc=tin-pham,dc=com. So we'll create a new data store for open am itself called,

1. openam
2. opensso

Reference for the command.

./OpenDJ/bin/dsconfig create-backend --backend-name myOrgRoot --set base-dn:o=myOrg --set enabled:true 

..

...

It is recommended by ForgeRock that the configuration use the OpenAM embedded data store for up to 4 OpenAM replicas. ForgeRock further recommends that no more then 4 OpenAM replicas exist for a given installation.

In our own experience, we were not successful when we tried to use OpenDJ for the configuration data store even though we followed the steps to Relax the Restriction on Objects.

Relax the Restriction on Objects

Another bug in a sense. Carefully reading the manual, If "if you decide to use an existing installation of OpenDJ for configuration data, then you must first relax the restriction on objects with multiple structural object classes, by using the OpenDJ *dsconfig* command before completing OpenAM configuration".

Enter this into the command line

...