Infrastructure at your Service
In a previous blog I talked about the domain creation, we saw at the end that some server groups and servers are created by default which usually are not what we need. Through this blog, I will show you how to clean this unneeded configuration and how to configure your domain according to your defined architecture.
As promised in my previous blog, I will give you a short feedback on the second day here at DevOpsDays 2020 Geneva. In fact, I prepared a very interesting program of sessions to attend and people to meet. I must say that the open-spaces concept applied on the second day allowed participants to discuss on different topics without limit.
It is a pleasure to come back to Geneva after 5 years to attend my first DevOps event. I’m very excited to share with you my first day feedback, but before I would like to thank dbi services for allowing me to attend this event and continuously improving my knowledge in this growing field.
At a customer, we are upgrading Control-M Agents running on Windows/Unix from 9.0.00.400 to 9.0.19.200 using Agent Deployment, an upgrade of one agent fails with error talking about communication issue between Control-M/server and Control-M agent:
The emdef is a command line utility used to make various modifications to job definitions in the Control-M/EM database. we saw how emdef can help to manage Calendars and Folders, today it the Jobs turn so let’s deep in 😉
In a previous blog I talked about the emdef utility and how it can help to manage and standardize calendars across multiple environments. In this blog we will deal with folders definitions in the Control-M/EM database. This can be used to extract data as a backup, or for migration from one to another environment.
The emdef is a command line utility used to make various modifications to calendar definitions in the Control-M/EM database. It can be used to extract data as a backup, or for migration from one to another environment.
I already talked about the domain creation in a previous blog, it is nice to start with but of course not enough if you want to understand the domain architecture, its components, and how they are related to each other.
The Documentum installation owner is the operating system user that owns the server executable and other related files along with the OS process when the server is running. It is originally determined when the server is installed, in fact, it is the logged-in user that performed the Documentum installation.
In a previous blog I talked about CMIS in general and showed you what importance it does have in ECM World. In fact, I already experienced CMIS in a project with Documentum and Alfresco involved! The goal was to make the same operations on both ECM from a single interface, so CMIS was the solution. In this blog, I will talk about CMIS with Documentum.
