Public | Automated Build

Last pushed: a year ago
Short Description
IBM Tivoli Directory Integrator 7.1.1 Docker Container
Full Description

IBM Tivoli Directory Integrator 7.1.1 Docker Container

SUSE Linux Enterprise Server 11.4 running IBM TDI 7.1.1 also known as IBM Security Directory Integrator.
TDI Configuration Editor GUI is started when the container is run.
The build does not include TDI itself, which you must download from the IBM's software access catalog website.

Building

This container is built from the scratch, meaning that you need the OS first. You also need TDI and TDI FP5 installation packages. Docker Hub automated builds will not work for you because these packages are not included in this Docker distribution.

  1. You can create Just enough OS image with SUSE Studio, or do it using the included kiwi script. jeos-config.xml file contains the JeOS configuration details. (list of needed packages is in the JeOS section below)
  2. Once you have downloaded or created the JeOS disk image you need to convert it to a "file and folder" archive by running sles2docker
  3. Download TDI 7.1.1 for Linux from IBM's Software access catalog. Save it to TDI_IDENTITY_E_V7.1.1_LIN-X86-64(CZUF3ML).tar
  4. Download TDI 7.1.1 Fix Pack 5 from IBM's support site and save it to 7.1.1-TIV-TDI-FP0005.zip
  5. Now run ./build

JeOS

If you are building your own JeOS note of the several packages are required:

  • gawk, tar, gtk2m, unzip - to install and run TDI
  • xorg-x11-fonts, liberation-fonts, xorg-x11-fonts-core, gtk2-theme-SLED, gnome-themes - to make TDI GUI pretty

Packages that are included automatically by SUSE Studio. Although you can take them off the list, SUSE studio will not allow you to build the appliance without them. They are not actually needed by TDI and you could remove them when the appliance image is being built or after.

  • suse-sam-data, kernel-default, bootsplash, gfxboot-devel, timezone, grub,zypper,suse-sam - required by the OS and will be included

Optional packages:

  • iputils, curl, less, vim - for network connectivity troubleshooting and general editing within the container
  • fastjar - for packacking TDI adapters

Optional:

  • vim for general editing/testing stuff from within a running container

Everything else you can take off the list. The size of the appliance could potentially be reduced later when the appliance is being built by removing unneeded packages like this:

RUN rpm -ev --noscripts \
    bootsplash branding-SLES bridge-utils cron dhcpcd e2fsprogs elfutils file grub ifplugd initviocons iproute2 iputils irqbalance kbd kernel-default \
    kernel-default-base klogd lcms less libaio libasm1 libdw1 libelf1 libext2fs2 libgssglue1 libjpeg liblcms1 libmng libnet libnuma1 libtiff3 libtirpc1 \
    logrotate mdadm mkinitrd module-init-tools netcfg openldap2-client openssl-certs perl-Bootloader perl-satsolver perl-XML-Parser perl-XML-Simple postfix rpcbind suse-build-key \
    suse-sam suse-sam-data sysconfig sysfsutils syslog-ng tar timezone tunctl update-alternatives vim-base vlan xz
RUN zypper clean --all

and possibly other packages...

Running

Use the bundled 'run' command or

docker run -ti --rm -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix:ro -v ~/Shared\ Folder/Docker:/opt/IBM/TDI/V7.1.1/workspace -u 1000 aiv/tdi711`

When TDI starts it will prompt for the workplace location, just ok it.
TDI GUI is running nativelly via a shared X socket, no ssh is needed.

The container is running under user developer that mimics your ID and group so that the shared volumes have the same permission structure

root password is Passw0rd, and so is the developer's password.

When ibmditk starts it creates the folder structure under /home/developer. To add server SSL certificates edit /home/developer/serverapi/testadmin.jsk keysotore. You can run java tools by adding them to the path

export PATH=$PATH:/opt/IBM/TDI/V7.1.1/jvm/jre/bin/

To add packages use susestudio to create a proper package or add a OpenSUSE repos and update it from within the container. Note though that several opensuse updates break TDI.

RUN zypper ar http://download.opensuse.org/update/11.4/ Update
RUN zypper --gpg-auto-import-keys refresh -s
RUN zypper --non-interactive up

Other repos:

zypper ar http://download.opensuse.org/distribution/11.4/repo/oss/ OSS
zypper ar http://download.opensuse.org/source/distribution/11.4/repo/oss/ Src-OSS
zypper ar http://download.opensuse.org/repositories/openSUSE:/11.4:/Contrib/standard/ Contrib
zypper ar http://download.opensuse.org/repositories/Java:/packages/SLE_11/ Java

There are several GTK themes installed that you can use to change look-and-feel of TDI. Set

GTK2_RC_FILES=/usr/share/themes/Glossy/gtk-2.0/gtkrc -  clearlooks with mac'y feel
GTK2_RC_FILES=/usr/share/themes/Gilouche/gtk-2.0/gtkrc -  washedout clearlooks
GTK2_RC_FILES=/usr/share/themes/ClearlooksClassic/gtk-2.0/gtkrc - simplified clearlooks
GTK2_RC_FILES=/usr/share/themes/Synchronicity/gtk-2.0/gtkrc - very washed out
GTK2_RC_FILES=/usr/share/themes/Glider/gtk-2.0/gtkrc -  square-ish

Other alternatives

  • ./themes/LargePrint/gtk-2.0/gtkrc
  • ./themes/LowContrastLargePrint/gtk-2.0/gtkrc
  • ./themes/ThinIce/gtk-2.0/gtkrc
  • ./themes/Redmond/gtk-2.0/gtkrc
  • ./themes/Simple/gtk-2.0/gtkrc
  • ./themes/LowContrast/gtk-2.0/gtkrc
  • ./themes/Crux/gtk-2.0/gtkrc
  • ./themes/Mist/gtk-2.0/gtkrc
  • ./themes/Industrial/gtk-2.0/gtkrc
Docker Pull Command
Owner
alexivkin
Source Repository

Comments (0)