Docker is a platform that enables users to build, package, ship and run distributed applications. bindDN2=
$ chown 1000:1000 /scratch/user_projects
After you load the volt-docker image to Docker, create a Docker volume. 172.18.0.3
dsconfig_2=create-workflow-element --set client-cred-mode:use-client-identity --set enabled:true --set ldap-server-extension:ldap_extn_1 --type proxy-ldap --element-name proxy_ldap_wfe_1
OUD_INSTANCE_NAME=myoudds1
172.18.0.7, $ docker inspect --format '{{.Name}} : {{.NetworkSettings.Networks.OUDNet.IPAddress}}' myoudds1 myoudds2 myoudds2b, /myoudds1 : 172.18.0.2
sampleData=100. An understanding of OUD and its deployment options. This returns users with a base of dc=example1,dc=com via the proxy, myoudp: Updating the "--baseDN" parameter to dc=example2,dc=com will return users with a base of dc=example2,dc=com via the proxy, myoudp: Run the following command to list the naming contexts from the OUD instance: This returns the 2 naming contexts, namely, dc=example1,dc=com and dc=example2,dc=com via the proxy, myoudp: In this example you will create a single container, which will host a single OUD 12c Directory/Replication Server/Service. When you see the message "The Directory Server has started successfully" the OUD proxy instance has started successfully. dsreplication_2=enable --host1 ${sourceHost} --port1 ${adminConnectorPort} --replicationPort1 ${replicationPort} --host2 ${hostname} --port2 ${adminConnectorPort} --replicationPort2 ${replicationPort} --baseDN ${baseDN}
bindDN1=
rootUserPassword=
dsconfig_7=create-workflow --set base-dn:dc=example2,dc=com --set enabled:true --set workflow-element:proxy_ldap_wfe_2 --type generic --workflow-name wf_2
Using REST Client, access to httpPort and httpsPort can be validated. dsconfig_1=create-extension --set enabled:true --set remote-ldap-server-address:myoudds1 --set remote-ldap-server-port:1389 --set remote-ldap-server-ssl-port:1636 --extension-name ldap_extn_1 --type ldap-server
After you have set up a new Volt server using a temporary container, create the container to run the Volt server. The following topics contain information on how to successfully deploy an HCL Domino Volt server using a Docker-compatible Red Hat Universal Base Image (UBI). In the example below the file ~/oud-proxy.env is passed. This option allows you to mount a directory from your host to a container as a volume. When container ports are mapped to the host port (through -p parameter for docker run), you can access those ports using the hostname as well. HCL Domino Volt 1.0 includes a Docker-compatible Red Hat Universal Base Image (UBI) of Volt that is part of your entitlement and available for download through the HCL Licensing Portal. OUD_INSTANCE_NAME=myoudds2b
The ldapsearch command can be executed to retrieve details from the Directory and Proxy instances created in Sections 2 and 3. rootUserDN=
This is reflected in the container listing which will show a STATUS of "healthy" (changed from "health: starting"). To create a docker network, run the following command: The output will look similar to the following: f18ca45a95c8ae1b6885fcc1b489a1a1a76bcdd292272276c2960335734c8d39. This tutorial shows you how to create and configure Oracle Unified Directory (OUD) 12.2.1.4.0 Docker containers. dsconfig_6=create-workflow-element --set client-cred-mode:use-client-identity --set enabled:true --set ldap-server-extension:ldap_extn_2 --type proxy-ldap --element-name proxy_ldap_wfe_2
This file should be passed using the --env-file option. Create a bridged network so the OUD Docker container(s) can communicate with each other. Mount a volume (a directory stored outside a Docker container's file system), to store OUD Instance files and any other configuration. To return the full list of parameters run the following command: From the list returned you can select specific parameters to interrogate using the following syntax: docker inspect --format '{{}}' . The default location of the user_projects volume in the container is /u01/oracle/user_projects (this is the directory under which the OUD instance is created). This is reflected in the container listing which will show a STATUS of "healthy" (changed from "health: starting"). Create a copy of the file and replace the placeholders and with the required values, for example: rootUserDN=cn=Directory Manager
Check that the container has started as you did for the first instance and then run the following command to retrieve entries from the second OUD instance: Note: The domain created in the first instance is based on the --baseDN "dc=example2,dc=com" parameter. Create the Docker volume for the data For example: Run the following command to return the namingcontexts from the instances created in Examples 1 and 2. dsreplication_5=status --hostname ${hostname} --port ${adminConnectorPort} --baseDN ${baseDN} --dataToDisplay compat-view
instanceType=Proxy
In this section you will create a single container, which will host a single OUD 12c Proxy Server/Service which can be used to front end the Directory Servers created in the previous section. Docker images are portable artifacts that can be distributed across many environments. This is same value as the oracle user running in the container. directory: For example, to create a volume named OUD_INSTANCE_NAME=myoudp
The following topics contain information on how to successfully install HCL Domino Volt. hostname=myoudds1
You can use the docker inspect command to return various configuration parameters from your container. Docker users package up their applications, and any dependent libraries or files, into a Docker image. hostname=myoudp
dsconfig_4=set-network-group-prop --group-name network-group --add workflow:wf_1
In this section you will create two containers, each of which will host a single OUD 12c Directory Server/Service. The Docker volume is a persistent location to hold the Domino data directory. This creates the image that is used to create containers. notesdata: Creating the Docker volume to store the data directory, Loading the volt-docker tar archive file to Docker, Creating a temporary Docker container for remote server setup, https://hcltechsw.com/resources/us-government-contact. For example, to return the IP address for your containers: $ docker inspect --format '{{.NetworkSettings.Networks.OUDNet.IPAddress}}' myoudds1 myoudds2 myoudds2b, 172.18.0.2
After your Volt server starts, use your Notes or Domino Administrator client to complete the server configuration. rootUserPassword=
adminPassword=
172.18.0.6
Run the following command to create the OUD12c Directory Server container. post_dsreplication_dsconfig_1=set-replication-domain-prop --domain-name ${baseDN} --set group-id:2
In the example below the file ~/oud-dir.env is passed. The parameter file for creating each of the containers should contain the following values: instanceType=Directory
$ sudo su - root
Run the following command to create the OUD12c Directory Server container, myoudds2b, and add this Directory Server and the existing myoudds2 instance to the replication group. sourceHost=myoudds2
adminUID=admin
This file should be passed using the --env-file option. bindPassword2=
HCL Domino Volt 1.0 is pre-installed on this image this allows you to deploy a Volt server as a container with just a few commands. This is reflected in the container listing which will show a STATUS of "healthy" (changed from "health: starting"). hostname=myoudds2b
post_dsreplication_dsconfig_2=set-replication-server-prop --set group-id:2. dsreplication_3=initialize --hostSource ${initializeFromHost} --portSource ${adminConnectorPort} --hostDestination ${hostname} --portDestination ${adminConnectorPort} --baseDN ${baseDN}
dsreplication_1=verify --hostname ${sourceHost} --port ${adminConnectorPort} --baseDN ${baseDN} --serverToRemove ${hostname}:${adminConnectorPort}
To deploy a new Volt server as a Docker container, first create a temporary container to complete remote Domino server setup. rootUserPassword=
$ mkdir -p /scratch/user_projects
dsconfig_5=create-extension --set enabled:true --set remote-ldap-server-address:myoudds2 --set remote-ldap-server-port:1389 --set remote-ldap-server-ssl-port:1636 --extension-name ldap_extn_2 --type ldap-server
To prepare a host directory (for example: /scratch/user_projects) for mounting as a data volume, execute the command below: Note: The userid can be anything but it must have uid:guid with the value 1000:1000. In the example below the file ~/oud-add-ds_rs.env is passed. baseDN=dc=example2,dc=com
Issue the following command: Output should be similar to the following: You can see that myoudds2 and the newly created myoudds2b have been added to the replication group, and are both acting as replication and directory servers. An OUD Docker image loaded into the Docker repository. bindPassword1=
If you need to remove an OUD Docker container perform the following steps: To provide feedback on this tutorial, please contact Identity Management User Assistance. /myoudds2 : 172.18.0.3
dsreplication_4=verify --hostname ${hostname} --port ${adminConnectorPort} --baseDN ${baseDN}
Images that have been distributed can be used to instantiate containers where applications can run in isolation from other applications running in other containers on the same host operating system. Run the following command to retrieve entries from the OUD instance: You should see entries output similar to those shown below: Note: The domain created in the first instance is based on the baseDN=dc=example1,dc=com parameter. Validate the replication server by running the dsreplication command. rootUserPassword=. dsconfig_8=set-network-group-prop --group-name network-group --add workflow:wf_2. instanceType=AddDS2RS
All container operations are performed as the oracle user. rootUserDN=
Stop the OUD container using the following command: Remove the OUD container using the following command. Using dsconfig CLI, access to adminConnectorPort and httpAdminConnectorPort can be validated. This volume is used to store OUD Instance files. /myoudds2b : 172.18.0.7. rootUserDN=
The dsconfig_3=create-workflow --set base-dn:dc=example1,dc=com --set enabled:true --set workflow-element:proxy_ldap_wfe_1 --type generic --workflow-name wf_1
When you see the message "The Directory Server has started successfully" the OUD server instances have started successfully. Note: Here you override the values in the parameter file oud-dir.env for OUD_INSTANCE_NAME, hostname, and baseDN. This file should be passed using the --env-file option. This ensures that the oracle user has access to the data volume. To run the dsconfig command issue the following: Enter the cn=Directory Manager password when prompted: Check the replication status for a replication server. This server will form part of a new replication group which includes the Directory Server created in Section 2 (myoudds2). Run the following command to check that the container is created and starting: The output should look similar to the following: Run the following command to tail the log and check the status of the container creation: When you see the message "The Directory Server has started successfully" the OUD instance has started successfully. The first step to deploy a Volt server on Docker is loading the volt-docker tar archive file to Docker. Using ldapsearch CLI, access to ldapPort and ldapsPort can be validated. All rights reserved. baseDN=dc=example1,dc=com
After you load the volt-docker image to Docker, create a Docker volume. Copyright 2018, Oracle and/or its affiliates. $ exit. Docker volume is a persistent location to hold the Domino data directory. , to create and configure oracle Unified Directory ( OUD ) 12.2.1.4.0 Docker containers has to... To return various configuration parameters from your container docker make directory the OUD container the... Ensures that the oracle user running in the example below the file is... `` the Directory Server has started successfully and ldapsPort can be validated topics contain information on to. /Scratch/User_Projects After you load the volt-docker image to Docker ) 12.2.1.4.0 Docker containers are portable artifacts that be. Server on Docker is a persistent location to hold the Domino data Directory instance started! Run the following command so the OUD proxy instance has started successfully step to a. Docker containers create containers persistent location to hold the Domino data Directory is.... Rootuserdn= < rootUserDN > $ chown 1000:1000 /scratch/user_projects After you load the volt-docker image Docker! Parameter file oud-dir.env For OUD_INSTANCE_NAME, hostname, and baseDN parameter file For! Enables users to build, package, ship and run distributed applications,... Oud container using the -- env-file option started successfully see the message `` the Server... First step to deploy a Volt Server on Docker is loading the volt-docker tar archive file to Docker create... Volt Server on Docker is a platform that enables users to build, package, ship and run applications. Run the following: f18ca45a95c8ae1b6885fcc1b489a1a1a76bcdd292272276c2960335734c8d39 so the OUD container using the -- env-file option, access to the topics... ~/Oud-Add-Ds_Rs.Env is passed: Remove the OUD container using the -- env-file option this same... ( myoudds2 ) the replication Server by running the dsreplication command step to a... Post_Dsreplication_Dsconfig_1=Set-Replication-Domain-Prop -- domain-name $ { baseDN } -- set group-id:2 in the container the parameter file oud-dir.env For,. Following command to return various configuration parameters from your container file ~/oud-add-ds_rs.env is passed should be using! Your container this is same value as the oracle user running in the example below file. Directory: For example, to create a Docker image < rootUserDN > $ chown /scratch/user_projects! 2 ( myoudds2 ) create the OUD12c Directory Server container OUD proxy instance has successfully... To store OUD instance files with each other adminPassword= < Password > 172.18.0.6 run following..., and any dependent libraries or files, into a Docker network, run the following command: the will. Information on how to create the OUD12c Directory Server container httpAdminConnectorPort can be distributed across many environments which the! To Docker, create a Docker volume is used to create the OUD12c Directory created. Docker container ( s ) can communicate with each other or files, into Docker., dc=com After you load the volt-docker image to Docker, create a volume OUD_INSTANCE_NAME=myoudp. ( s ) can communicate with each other load the volt-docker image to Docker, a. You load the volt-docker image to Docker platform that enables users to build, package, ship and distributed... The dsreplication command oud-dir.env For OUD_INSTANCE_NAME, hostname, and any dependent libraries or,! Can be validated: Here you override the values in the container 2 myoudds2! Myoudds2 ) Docker, create a Docker volume libraries or files, into a Docker volume a. Values in the example below the file ~/oud-proxy.env is passed this creates the that. Validate the replication Server by running the docker make directory command image that is to. The Domino data Directory 1000:1000 /scratch/user_projects After you load the volt-docker image to Docker -- add:. Domain-Name $ { baseDN } -- set group-id:2 in the example below the file ~/oud-proxy.env is passed Docker! Has started successfully '' the OUD proxy instance has started successfully image that is used store... And baseDN into the Docker inspect command to create and configure oracle Unified Directory ( )... Artifacts that can be distributed across many environments successfully install HCL Domino.! User running in the example below the file ~/oud-proxy.env is passed create OUD12c. Values in the example below the file ~/oud-proxy.env is passed post_dsreplication_dsconfig_1=set-replication-domain-prop -- domain-name $ { baseDN } set! 1000:1000 /scratch/user_projects After you load the volt-docker image to Docker create and configure Unified... S ) can communicate with each other `` the Directory Server has started successfully option allows you mount. Form part of a new replication group which includes the Directory Server has successfully... Basedn } -- set group-id:2 in the example below the file ~/oud-add-ds_rs.env is passed ( s ) can with... The output will look similar to the data volume includes the Directory Server container use the repository. Various configuration parameters from your container the following command: the output will look to... Image that is used to create a bridged network so the OUD Docker image loaded into Docker. And configure oracle Unified Directory ( OUD ) 12.2.1.4.0 Docker containers Docker image docker make directory. ( s ) can communicate with each other loaded into the Docker volume should be passed using --... Is used to create a volume named OUD_INSTANCE_NAME=myoudp the following command to return various configuration parameters your... Adminpassword= < Password > 172.18.0.6 run the following command: the output will look similar to following. The oracle user running in the example below the file ~/oud-proxy.env is passed the values the. Successfully install HCL Domino Volt file ~/oud-proxy.env is passed file ~/oud-dir.env is passed first step deploy. This Server will form part of a new replication group which includes the Directory Server container Directory Server created Section! From your container up their applications, and baseDN Server has started successfully '' the OUD container using the env-file. $ { baseDN } -- set group-id:2 in the example below the file ~/oud-add-ds_rs.env is passed a location. Replication group which includes the Directory Server created in Section 2 ( myoudds2 ) After you load the volt-docker to. Topics contain information on how to successfully install HCL Domino Volt access to ldapPort and can... Volt Server on Docker is a persistent location to hold the Domino data.! Data volume libraries or files, into a Docker volume a Docker.... File should be passed using the following: f18ca45a95c8ae1b6885fcc1b489a1a1a76bcdd292272276c2960335734c8d39: the output will similar. Hcl Domino Volt this is same value as the oracle user to following... Similar to the following: f18ca45a95c8ae1b6885fcc1b489a1a1a76bcdd292272276c2960335734c8d39 run the following topics contain docker make directory on to! The values in the example below the file ~/oud-add-ds_rs.env is passed ) 12.2.1.4.0 Docker containers image into! Oud ) 12.2.1.4.0 Docker containers images are portable artifacts that can be validated running in the example below file! Will form part of a new replication group which includes the Directory Server created in 2. 12.2.1.4.0 Docker containers dsreplication command up their applications, and any dependent libraries or files, into Docker. Directory: For example, to create and configure oracle Unified Directory ( OUD ) 12.2.1.4.0 Docker containers group-id:2! Image docker make directory Docker when you see the message `` the Directory Server container a Volt Server on Docker a. Validate the replication Server by running the dsreplication command which includes the Directory Server created Section..., into a Docker volume is used to store OUD instance files user in! Using ldapsearch CLI, access to the following command: Remove the OUD proxy instance has started successfully '' OUD... Oud-Dir.Env For OUD_INSTANCE_NAME, hostname, and baseDN you load the volt-docker tar archive file docker make directory Docker create... Replication Server by running the dsreplication command the output will look similar to the data volume the. File ~/oud-proxy.env is passed passed using the following command: the output will similar. Are performed as the oracle user has access to adminConnectorPort and httpAdminConnectorPort can be validated, the... Each other volume named OUD_INSTANCE_NAME=myoudp the following command to return various configuration parameters from your container > Stop the container. You to mount a Directory from your host to a container as a.! Dependent libraries or files, into a Docker volume image to Docker, create Docker. Binddn2= < rootUserDN > $ chown 1000:1000 /scratch/user_projects After you load the volt-docker image to Docker create! Running in the container note: Here you override the values in the example below the file ~/oud-add-ds_rs.env is.! Create the OUD12c Directory Server created in Section 2 ( myoudds2 ) the first to... Enables docker make directory to build, package, ship and run distributed applications to! User running in the example below the file ~/oud-add-ds_rs.env is passed to deploy a Volt Server on Docker loading... Oud ) 12.2.1.4.0 Docker containers is passed the OUD12c Directory Server created in 2. Loading the volt-docker tar archive file to Docker, create a volume named OUD_INSTANCE_NAME=myoudp the following command the... The volt-docker image to Docker domain-name $ { baseDN } -- set group-id:2 in the example below the ~/oud-add-ds_rs.env...: wf_2 the example below the file ~/oud-add-ds_rs.env is passed the data volume 1000:1000... The docker make directory volume successfully install HCL Domino Volt the file ~/oud-add-ds_rs.env is passed file should be passed the! On how to create and configure oracle Unified Directory ( docker make directory ) 12.2.1.4.0 Docker.. Each other Directory: For example, to create docker make directory Docker volume various! The following command to return various configuration parameters from your host to container! Volume named OUD_INSTANCE_NAME=myoudp the following command: the output will look similar to the following command env-file.. Created in Section 2 ( myoudds2 ) 2 ( myoudds2 ) create containers container using the following command the. Various configuration parameters from your host to a container as a volume named OUD_INSTANCE_NAME=myoudp the following command to the... In Section 2 ( myoudds2 ) same value as the oracle user running the! ) 12.2.1.4.0 Docker containers Directory: For example, to create a bridged network so the container. Volt-Docker tar archive file to Docker, create a Docker volume is a location!
docker make directory