Page History

...

export OPENDS_JAVA_HOME=/opt/opendj-java-runtime
svradm@tinh0v01app:cd /opt/opendj.0/bin$bin
./dsjavaproperties
The operation was successful.  The server commands will use the java arguments and java home specified in the properties file located in /opt/opendj.0/config/java.properties

...

You can run the status command even if the server is off and verify the configuration.

Start and Stop

As a reference,

cd /opt/opendj.0/bin
./start-ds

cd /opt/opendj.0/bin
bin/stop-ds

# I think this is verbose mode but not finding docs on it
./start-ds -s

Start the server,

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

OpenAM uses two data stores,

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 

Relax the Restriction on Objects

Another bug in a sense. Carefully reading the manual,

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

References

Not bad but not good manual setup - http://opendj.forgerock.org/doc/install-guide/OpenDJ-Install-Guide.html

...