Setting Up Your Docker Environment
OneData certifies support for Docker CE 17.5 and later on a Linux container, with Centos as the base image. Although you can install Docker on a Windows operating system, you will require a Linux container as the container running your OneData Docker image.
To set up your Docker Environment for
OneData1. Use the following command to pull the OneData Docker image from the Docker registry:
To install the latest version of
OneData:
docker pull daerepository03.eur.ad.sag:4443/mdm/onedata
To install an earlier version of
OneData:
docker pull daerepository03.eur.ad.sag:4443/mdm/onedata: 10.3.0.0.144
Here, replace 10.3.0.0.144 with the version you want.
2. In case the pull command fails with an exception for the security certificate, follow these steps:
a. Obtain a security certificate for your repository from a trusted source.
b. Apply the certificate to the machine hosting your Docker image.
a. Obtain the CA certificate from the server.
Note: Only Red Hat Enterprise Linux (RHEL) and Ubuntu operating system commands are provided here. If you want to use any other operating system, refer to the operating system documentation for the commands to use.
RHEL commands
cd /etc/pki/ca-trust/source/anchors/
curl -k
https://daerepository03.eur.ad.sag:4443/mdm/onedata/ca > ucp-ca.pem
Ubuntu commands
curl -k https://daerepository03.eur.ad.sag:4443/mdm/onedata/ca > ucp-ca.crt
sudo cp ucp-ca.crt /usr/local/share/ca-certificates/
b. Add the certificate to the local trusted keys.
RHEL commands
update-ca-trust force-enable
update-ca-trust extract
Ubuntu commands
update-ca-certificates
c. If you are using Ubuntu, verify if you are able to connect the Docker service to the Docker trusted registry (DTR).
d. Restart the Docker service.
e. After the certificate is successfully applied, pull the OneData Docker image with the command:
docker pull daerepository03.eur.ad.sag:4443/mdm/onedata
f. Run the following command to verify if the OneData Docker image is pulled to your Docker:
docker images
The results must include the OneData Docker image you pulled.
3. Create a OneData environment file with the name ODE_DOCKER_ENV when running the OneData Docker image by using this template:
Inclusion of database schema passwords in the environment file is not a security best practice that
Software AG recommends. To avoid this security vulnerability, exclude the schema passwords in the environment file and pass them in the
-e command parameter when starting the
OneData Docker image.
If the database container and the Elasticsearch container share the same VM or machine as the
OneData container, use the container IP address of the database server to connect to
OneData.
ODE_DOCKER_ENV Template
#***start ODE_DOCKER_ENV ******************
##DBMS TYPE either Oracle or SQL Server
DBMS=<Database type either Oracle or SQL Server.>
#
##*******************Metadata connection details*************************
jndinamemd=<JNDI name for OneData metadata database connection. If not
provided, default value jdbc /onedatamd is used.>
jdbcurlmd=<JDBC URL to connect to onedata OneData Metadata database or
schema.>
usernamemd=<OneData Metadata database or database/schema user name.>
passwordmd=<OneData Metadata database password.>
#
##*******************Work Area connection details*************************
jndinamewa=<JNDI name for OneData Work Area database connection. If not
provided, default value jdbc /onedatamd is used.>
jdbcurlwa= <JDBC URL to connect to OneData Work Area database or schema.>
usernamewa=<OneData Work Area database or schema user name.>
passwordwa=<OneData Work Area database password.>
#
##*******************Release Area connection details*************************
jndinamera=<JNDI name for OneData Release Area database connection. If not
provided, default value jdbc /onedatara is used.>
jdbcurlra=<JDBC URL to connect to onedata Release Area database or schema.>
usernamera==OneData Release Area database or schema user name.>
passwordra=<OneData Release Area database password.>
##*******************Default onedata property update*************************
##Below are sample properties to enable the elasticearch in OneData,
required to enable the onedata search ##capability.
enable_elasticsearch=<true, to enable the Elasticsearch search capability.
false, is the default value.>
elasticsearch_clustername=<Your Elasticsearch cluster name.
SAG_EventDataStore is the default value.>
elasticsearch_httpurl=<Your Elasticsearch HTTP URL. http://localhost:9240 is
the default value.>
elasticsearch_dataloadonstartup=<true, if want to reload the Elasticsearch
index at every restart. false, is the default value.>
elasticsearch_server_hostname=<The host name of the Elasticsearch server.
localhost is the default value.>
elasticsearch_server_tcpport=<Elasticsearch server TCP port. 9340 is the
default value.>
#
#***end ODE_DOCKER_ENV ******************
Sample ODE_DOCKER_ENV Content for SQL Server Database
#***start ODE_DOCKER_ENV ******************
##DBMS TYPE either Oracle or SQL Server
DBMS=SQL Server
##*******************Metadata connection details*************************
jndinamemd=jdbc/onedatamd
jdbcurlmd=jdbc:wm:SQL Server://127.0.0.1:1433;databaseName=OneDataMD
usernamemd=ODEMD
passwordmd=Tam%nge
##*******************Work Area connection details*************************
jndinamewa=jdbc/onedatawa
jdbcurlwa=jdbc:wm:SQL Server:// 127.0.0.1:1433;databaseName=OneDataWA
usernamewa=ODEWA
passwordwa=manage3@
##*******************Release Area connection details*************************
jndinamera=jdbc/onedatara
jdbcurlra=jdbc:wm:SQL Server://127.0.0.1:1433;databaseName=OneDataRA
usernamera=ODERA
passwordra=l!Stl33s
##*******************Default onedata property update*************************
##Below are sample properties to enable the elasticearch in OneData, required
to enable the OneData search ##capability.
enable_elasticsearch=true
elasticsearch_clustername=elasticsearch
elasticsearch_httpurl=http://127.0.0.1:9240
elasticsearch_dataloadonstartup=true
elasticsearch_server_hostname=127.0.0.1
elasticsearch_server_tcpport=9340
#***end ODE_DOCKER_ENV ******************
Sample ODE_DOCKER_ENV Content for Oracle Database
#***start ODE_DOCKER_ENV ******************
##DBMS TYPE either Oracle or SQL Server
DBMS=Oracle
##*******************Metadata connection details*************************
jndinamemd=jdbc/onedatamd
jdbcurlmd= jdbc:wm:oracle://127.0.0.1:1521;serviceName=orcl;catalogOptions=1
usernamemd=ODEMD
passwordmd=Tam%nge
##*******************Work Area connection details*************************
jndinamewa=jdbc/onedatawa
jdbcurlwa= jdbc:wm:oracle://127.0.0.1:1521;serviceName=orcl;catalogOptions=1
usernamewa=ODEWA
passwordwa=manage3@
##*******************Release Area connection details*************************
jndinamera=jdbc/onedatara
jdbcurlra= jdbc:wm:oracle://127.0.0.1:1521;serviceName=orcl;catalogOptions=1
usernamera=ODERA
passwordra=l!Stl33s
##*******************Default onedata property update*************************
##Below are sample properties to enable the elasticearch in OneData,
required to enable the OneData search ##capability.
enable_elasticsearch=true
elasticsearch_clustername=elasticsearch
elasticsearch_httpurl=http://127.0.0.1:9240
elasticsearch_dataloadonstartup=true
elasticsearch_server_hostname=127.0.0.1
elasticsearch_server_tcpport=9340
#***end ODE_DOCKER_ENV ******************
4. Start the OneData Docker image with the run command (without line breaks).
OneData only
docker run -e ACCEPT_EULA=Y --name unique_container_name --env-file /
ODE_DOCKER_ENV_file_path/ODE_DOCKER_ENV -p Docker_machine_name_or_
IP_address:Port_where_you_want_to_run_Docker
-d daerepository03.eur.ad.sag:4443/mdm/onedata
Example:
docker run -e ACCEPT_EULA=Y --name onedata --env-file /ODE_DOCKER_ENV
-p 10.60.1.78:9090:9090 -d daerepository03.eur.ad.sag:4443/mdm/onedata
Example (including the database schema passwords):
docker run -e ACCEPT_EULA=Y --name onedata -e passwordmd=Tam%nge -e
passwordwa=manage3@ -e passwordra=l!Stl33s --env-file /ODE_DOCKER_ENV
-p 10.60.1.78:9090:9090 -d daerepository03.eur.ad.sag:4443/mdm/onedata
OneData and Locate
docker run -e ACCEPT_EULA=Y --name unique container name --env-file /
ODE_DOCKER_ENV_file_path/ODE_DOCKER_ENV --mount
source=Locate_data_volume_name,destination=/opt/softwareag/Locate/data
-p Docker_machine_name_or_IP_address:Port_where_you_want_to_run_Docker
-d daerepository03.eur.ad.sag:4443/mdm/onedata
Example:
docker run -e ACCEPT_EULA=Y --name onedata1 --env-file /ODE_DOCKER_ENV
--mount source=locateData,destination=/opt/softwareag/Locate/data
-p 127.0.0.1:9090:9090 -d daerepository03.eur.ad.sag:4443/mdm/onedata
If you wan to run the
OneData Docker image in interactive mode in order to check the
OneData in the same console, execute the
run command by replacing
-d with the
-it. For details on the
-it parameter, see
Docker Command Parameters.