...
| Code Block | ||
|---|---|---|
| ||
cd /opt/opendsopendj.0 ./setup --cli Please set OPENDS_JAVA_HOME to the root of a Java 6 update 10 (or higher) installation or edit the java.properties file and then run the dsjavaproperties script to specify the Java version to be used. |
...
| Code Block |
|---|
sudo mv /home/serveradmin/OpenDJ-2.4.5/ /opt/opendj/
sudo chown -R serveradmin:staff ./opendj/
sudo chmod -R 750 ./opendj/
sudo mv ./opendj/ ./opendj.0/ # Marking this as the first instance |
Start the Setup
Run the command line setup,
| Code Block | ||
|---|---|---|
| ||
cd /opt/opendsopendj.0 ./setup --cli |
The initial root user for the DN, the default is cn=Directory Manager, a well known account.
If you use the default, make Unless otherwise indicated select the default option,
| Code Block |
|---|
What would you like to use as the initial root user DN for the Directory
Server? [cn=Directory Manager]:
Please provide the password to use for the initial root user:
Please re-enter the password for confirmation: |
Make sure to use a complex password for the initial root user. We'll use the standard T&R password on "Directory Manager".
| Code Block |
|---|
On which port would you like the Directory Server to accept connections from
LDAP clients? [1389]:
On which port would you like the Administration Connector to accept
connections? [4444]: |
For LDAP client port, unless you are running with root priviledges you cannot use ports 1 through 1024. So rather than use 389, use 1389.
Use the default 4444 port for Administration Connector.
| Code Block |
|---|
Do you want to create base DNs in the server |
...
? (yes / no) [yes]: Provide the base DN for the directory data: [dc=example,dc=com]: |
...
cd=krypton,dc=com |
...
Options for populating the database: 1) Only create the base |
...
Do you want to enable SSL? (yes / no) [no]:
Do you want to enable Start TLS? (yes / no) [no]:
Say no to starting the server. We will verify the environment first before starting.
What would you like to do? 1) Set up the server with the parameters above
| Code Block | ||
|---|---|---|
| ||
entry
2) Leave the database empty
3) Import data from an LDIF file
4) Load automatically-generated sample data
Enter choice [1]:
Do you want to enable SSL? (yes / no) [no]:
Do you want to enable Start TLS? (yes / no) [no]:
Do you want to start the server when the configuration is completed? (yes /
no) [yes]: no |
Do you want to create base DNs in the server, select yes if you have a real DNS or use host entries on the server and client.
I select no to start the server because I like to we can run the status command even if the server is off and verify the configuration.
| Code Block | ||
|---|---|---|
| ||
Setup Summary ============= LDAP Listener Port: 1389 Administration Connector Port: 4444 LDAP Secure Access: disabled Root User DN: cn=Directory Manager Directory Data: Create New Base DN cd=krypton,dc=com. Base DN Data: Only Create Base Entry (cd=krypton,dc=com) Do not start Server when the configuration is completed What would you like to do? 1) Set up the server with the parameters above 2) Provide the setup parameters again 3) Print equivalent non-interactive command-line 4) Cancel and exit Enter choice [1]: See /tmp/opends-setup-774306341481213092998122271824097562.log for a detailed log of this operation. Configuring Directory Server ..... Done. Creating Base Entry dccd=tin-phamkrypton,dc=com ..... Done. To see basic server configuration status and configuration you can launch /opt/opendj.0/bin/status |
You can run the status command even if the server is off and verify the configuration.
Start and Stop
As a reference,
...
| Code Block | ||
|---|---|---|
| ||
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,
- Configuration
- 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,
- openam
- opensso
Reference for the command.
| Code Block | ||
|---|---|---|
| ||
./OpenDJ/bin/dsconfig create-backend --backend-name myOrgRoot --set base-dn:o=myOrg --set enabled:true |
..
| Note |
|---|
| K this is getting ridiculous... for now let's just use the internal data store for the configurations. |
...
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
cd /opt/opends.0./dsconfig -h opendj.tin-pham.com -p 4444 -D "cn=Directory Manager" -w ****** set-global-configuration-prop --set single-structural-objectclass-behavior:warn -X -n |
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.
References
Not bad but not good manual setup - http://opendj.forgerock.org/doc/install-guide/OpenDJ-Install-Guidedocs.html
https://bugster.forgerock.org/jira/browse/OPENDJ-330