This section guides you through the process of installing the Identity Manager Fan-Out Driver shim container for a new driver deployment. After the shim is deployed, you must perform some additional configuration steps in order to connect the container with the Identity Manager engine.
Run the container, in interactive mode, to begin the installation process that will communicate with the Identity Manager host via LDAP and prime the volume with configuration files.
docker run --rm -it --network=host -v /data:/config asamcdrv:4.8.7.0000
When the installation is finished, the container will exit and your volume will contain configuration data that will be used for future container deployments. The --rm switch also removes the temporary container it created just for the purpose of the install.
To run the new container with our freshly installed volume:
docker run -d --ulimit nofile=8192 --name=asamcdrv-container --network=host -v /data:/config asamcdrv:4.8.7.0000
The -d will cause the container to run in the background (detached). The --ulimit nofile=8192 will set the limit on open files, which asamcdrv needs for adequately processing lots of client requests.
This example also uses the --network=host networking option. This is a convenient way to allow the container to access the same network as the Docker host. This serves as an advantage later on when Platform clients will need an IP/DNS name to connect to the container. If you do not use host-based networking, you will have to map two ports to make them accessible from the host, using Docker’s port mapping command-line switch:
docker run -d --ulimit nofile=8192 --name=asamcdrv-container -p 8090:8090 -p 3451:3451 -v /data:/config asamcdrv:4.8.7.0000
After deploying the new container, you will need to connect Identity Manager to this container, which will require importing rules that were generated in previous steps in order to create a new Driver object.
The rules file was written to the volume at /config/ASAM/rules/Fan-Out-IDM3_6_0-V1.xml. For example, if you had used a local directory, /data, to map to the /config volume, this file would be located at /data/ASAM/rules/Fan-Out-IDM3_6_0-V1.xml on your Docker host. If you used a Docker-created volume, you can obtain this file using the docker cp command:
docker cp asamcdrv-container:/config/ASAM/rules/Fan-Out-IDM3_6_0-V1.xml .
For detailed steps on importing the rules to create a new Driver Object, see the previous section, Setting Up the Core Driver in iManager