Infrastructure at your Service
Testing the log watcher This is part II of the article. Part I is here. All the above code has to be included in the entrypoint script so it gets executed at container start up time but it can also be tested more simply in a traditional repository installation. First, we’ll move the code into a excutable script, e.g. entrypoint.sh, and run it in the background in a first terminal. Soon, we will notice that…
Containers running under docker can have their stdout observed from the outside through the “docker logs”command; here is an excerpt of its usage: docker logs –help Usage: docker logs [OPTIONS] CONTAINER Fetch the logs of a container Options: –details Show extra details provided to logs -f, –follow Follow log output –since string Show logs since timestamp (e.g. 2013-01-02T13:23:37) or relative (e.g. 42m for 42 minutes) –tail string Number of lines to show from the end…
Stopping the unreachable repositories Suppose that the docbroker has been stopped prematurely and that we want to shut down the repositories but the out-of-the-box dm_shutdown_repository is not effective. Why is it so by the way ? If we look closely inside the shutdown script, we quickly notice the reason: #!/bin/sh ################## DOCUMENTUM SERVER SHUTDOWN FILE ###################### # # 1994-2018 OpenText Corporation. All rights reserved # Version 16.4 of the Documentum Server. # # A generated…
You have finally completed that migration and need to restart all the Documentum processes. So, you shut down the docbroker and move on to the repositories but then you receive an error message about them not being reachable any more. Or conversely, you want to start all the Documentum processes and you start first the repositories and later the docbrokers. Next, you want to connect to one repository and you receive the same error message….
In article A Small Footprint Docker Container with Documentum command-line Tools, we presented a possible way to containerize the usual Documentum clients idql, iapi, dmawk and dmdocbroker. Those are command-line tools mostly used in batch processing or for one-of-its-kind manual tasks such as investigating or troubleshooting. OpenText also offers Documentum Administrator (aka DA), a java WDK-based client which is very useful for the occasional manual tasks. With its GUI running in a browser, it gives…
The aim here is to have a minimalist container with the usual Documentum clients idql, iapi, dmawk and dmqdocbroker. Documentum Administrator (DA) could also be a useful addition to our toolbox. We will show how to containerize it in a future article. A word of warning is in order here: the title’s catchy “small footprint” qualifier is relative. Don’t forget that said container will contain a certified O/S, a JRE, the DFCs and a few…
This is part II of the 2-part article. See for part I of this article. Testing We will test on the host machine named docker that hosts 2 containers, container01 and container011. All 3 machines run a repository. Its name is respectively dmtest on docker (shortly, [email protected]:1489), [email protected]:1489 ([email protected]:2489 externally) and [email protected]:1489 ([email protected]:5489 externally). Incidentally, the enhanced syntax is also a good way to uniquely identify the repositories. The current dfc.properties file on the host…
Now that we have containerized content servers, it is very easy, maybe too easy, to create new repositories. Their creation is still not any faster (whether they are containerized or not is irrelevant here) but given a configuration file it just takes one command to instantiate an image into a running container with working repositories in it. Thus, during experimentation and testing, out of laziness or in a hurry, one can quickly finish up having…
A few months ago, I tripped over a very mysterious problem while attempting to connect to a 7.3 CS docbase from within dqMan. We had 3 docbases and we could connect using this client to all of them but one ! Moreover, we could connect to all three using a remote Documentum Administrator or the local idql/iapi command-line tools. Since we could connect to at least one of them with dqMan, this utility was not…
Ideally, but not mandatorily, the management of Documentum processes is performed at the service level, e.g. by systemd. In my blog here, I showed how to configure init files for Documentum under systemd. But containers don’t have systemd, yet. They just run processes, often only one, sometimes more if they are closely related together (e.g. the docbroker, the method server and the content servers), so how to replicate the same functionality with containers ? The…
