A docker (https://www.docker.com/) image build for the APM solution of Computer Asscociates (CA APM). This project build a docker image for an Introscope enterprise manager in version 9.7 It is meant to be used in combination with the docker image docker-introscope-postgres (https://github.com/stefansiegl/docker-introscope-postgres), which provides the database for the enterprise manager.
Note that due to licensing reasons, it is not possible to package the installation files and the license in this image. Please read the usage which file you have to put where.
The docker image needs the installation files from CA Wily Introscope. Simply copy the files:
- introscope9.7.0.0otherUnix.jar (installer of the enterprise manager)
- osgiPackages.v9.7.0.27.unix.tar (osgi packages that you can download from http://opensrcd.ca.com/ips/osgi/introscope_9.7.0.0/)
- license.lic (I noticed that the enterprise manager can start without a license, but you are expected to put one here)
It goes without saying that you need docker installed. If you are on Windows (like me) or Mac, you can use boot2docker - I works perfectly for me.
All the script and Dockerfile are ready to build the image for the latest version of Introscope, the script or manifest don't reference any EM version, if you want to use this project for EM 9.8 you just have to change Dockerfile variables:
ENV INTROSCOPE_BIN=introscope9.7.0.27otherUnix.jar
ENV INTROSCOPE_OSGI=osgiPackages.v9.7.0.27.unix.tar
Fire up docker (or like in my case boot2docker), navigate to the project and execute the
build-image.sh
file.
This aproach will start postgresql and Inroscope, if you need more information look at the file docker-compose.yml
docker-compose up -d
If you just want the easiest solution, simply start the enterprise manager by
run-default-em-container.sh
This image is expected to be connected to a container of stefansiegl/introscope-postgres:9.7 that will provide the database for the enterprise manager. Furthermore, the image expects that a docker link --link is setup with the logical name being set to "db".
docker run -d --name introscope-em --link introscope-db:db stefansiegl/introscope-em:9.7
There are two ways to manage management modules with this image. The quick (and dirty) approach is to "mount" a local folder that is then used as management module folder. Drawback of this approach is, that the local folder overwrites the management module folder of the enterprise manager. So you need to place the out-of-the-box management modules in this folder as well.
docker run -d --name introscope-em --link introscope-db:db -v [localfolder]:/root/Introscope/config/modules stefansiegl/introscope-em:9.7
The second approach allows to add management modules to the existing config/modules folder. The startup script of the container ensures that all files that are within /transfer/modules (in the container) are copied to the config/modules folder. Thus you could keep the management modules you want to integrate locally in a folder and run the container like this (note that the management modules you copied to the container are persisted):
docker run -d --name introscope-em --link introscope-db:db -v [localfolder_containing_MM]:/transfer/modules stefansiegl/introscope-em:9.7
The enterprise manager allows to install additional plugins. This image allows this during the build. Simply place your extensions in the folder addons/em and addons/workstation.
Additional configuration is possible with environment variables. This image currently supports the following:
| ENV | description | default | example |
|---|---|---|---|
| HEAP_XMX | sets the xmx heap of the EM. Use typical Java notation. | 1024m | 2048m |
Environment variables can be set for example by
-e HEAP_XMX="2048m"
The image is configured persist some important folders, so that changes are persisted when you stop the container and start it again. (check the volume definitions in the dockerfile) If you like you can also map local folders, but I dont like this approach as this hinders portability. (just have a look inside the Dockerfile and bind the folders that you need)
As I said I do not like to map the logfiles to my host. docker is great at providing access to them already. What I usually do is to connect to the container with either
docker logs em (to see all system.out log output)
or even better to simply start a shell
docker exec -it em bash
Check the checked-in response file for the default settings the introscope enterprise manager is installed with and adapt it to your needs. Please note that the database settings are set in a way that this image is interoperable with stefansiegl/introscope-postgres, so be careful when changing this. Especially note that the file write DATABASE_URL for the database. This string is replaced during startup of the enterprise manager and substituted by the linked stefansiegl/introscope-postgres container.