Identity Governance
This is very resource intensive and will require at least 12GB RAM. I've managed to get it running with 8GB but were edging the VM with 92% RAM usage.
Download everything needed.
## Oracle Identity Governance (OIG)
kiot :: ~/oracle » docker pull container-registry.oracle.com/middleware/oig:14.1.2.1.0-jdk17-ol8-250315
kiot :: ~/oracle » docker tag container-registry.oracle.com/middleware/oig:14.1.2.1.0-jdk17-ol8-250315 localhost/oracle/oig:14.1.2.1.0
## Oracle 19c DB
kiot :: ~/oracle » docker pull container-registry.oracle.com/database/enterprise:19.3.0.0
kiot :: ~/oracle » docker tag container-registry.oracle.com/database/enterprise:19.3.0.0 localhost/oracle/database:19.3.0.0-ee
## Docker files
# kdev :: ~/oracle » git clone https://github.com/oracle/docker-images
kiot :: ~/oracle » git clone https://github.com/0xPThree/WebLogicConfiguration
Due to setup issues (probably related to insufficient RAM) I have rebuilt the setenv.sh and docker-compose.yaml files to a format that makes more sense to me. See below for full code.
You can most likely use the default sample files from Oracles repo (docker-images/OracleIdentityGovernance/setenv.sh, and docker-images/OracleIdentityGovernance/samples/containerizedDB/docker-compose.yaml) to achieve the same result.
With my configuration you must add kiot.dev.local 172.30.0.1 and oimdb.dev.local 172.30.0.2 to /etc/hosts.
Start environment
The environment is very sensitive and must be started in correct order as the containers are dependant of each other. Either tweak the docker-compose.yml to wait, or start the containers manually and observe the status using docker logs -f <container-name>. Starting the containers will take several minutes.
Important: You must use the same terminal window as the one where you set the variables.
Access environment
The login credentials are set in setenv.sh (weblogic:Passw0rd123 ) these will work for all services except Oracle Identity System Administration Console, which use xelsysadm:Passw0rd123.
WebLogic Administration Console
http://kiot.dev.local:7001/console
Oracle Enterprise Manager Console
http://kiot.dev.local:7001/em
Oracle SOA Platform
http://kiot.dev.local:8001/soa-infra
Oracle Identity Self Service Console
http://kiot.dev.local:14000/identity
Oracle Identity System Administration Console
http://kiot.dev.local:14000/sysadmin


Troubleshooting
Container out of memory
If you get an error similar to:
Solve it by configuring ulimits to your container. Either do this globally, or locally, in the docker-compose.yml file. I think it's easiest to do it globally and apply to all containers like so:
Domain Configuration failed
The issue is likely due to password requirements are not being met. Change password in the setenv.sh file to something longer and/or more complex. For dev installations I use Passw0rd123 which suffice.
Stuck at startup
If your SOA or IOM container get stuck at startup and the logs don't get past:
It may be that you don't meet the hardware requirements. I had my last container, OIM, stuck at this stage until I noticed that the RAM was maxed out. Increasing the RAM from 8 to 16 GB solved it and I was able to start all four containers.
Resources
Last updated
Was this helpful?