SOAP is quite specific and critical to data format and structure.
You might extend it, but then Edge Server is the active part and you depend on its regular "broadcast".
If Doc Server should be the active partner I'd rather suggest to use JDBC in Linux.
Your actual $get might be embedded as a Method projected as SQL Procedure that you call.
There exist examples to even execute COS commands by that approach:
see: ObjectScript over ODBC

Hi @Ditmar Tybussek 
Raw containers from ISC are always just US versions. (aka. international)
If you use Dockfile you have all freedom to condition  YOUR container according to your needs.

MgmtPortal: this is a good old  CSP feature that looks for the primary language of your browser
and translates your pages to DE if available.
Docker itself seems to have no idea about your environment.

Your keywords >90% COS + SAMPLES indicate your background.
if you don't intend to win a prize in a contest adapting some CSP Samples will be fastest. Forget any ZEN.
And just call the CSP class. never the .CSP itself.
what I mean:
NOT http://localhost:56773/csp/samples/form.csp
BUT http://localhost:56773/csp/samples/csp.form.CLS

It's my quick and dirty approach

It's funny you raise that subject now, as I just finished writing my "technologic bio" for my sons.
I won't translate the whole booklet but just pick out some highlights, 

#1) Why did you choose to become a software engineer / developer?

To become Engineer was an almost a genetic determination. I could roll back my ancestors down
to 1600 to find a repeating pattern of technical construction in wood, stone, metal, ...
and started with studying electronics. Software just happened by consequence and found its
summit by a complete operating system, with a distributed  M-database, interpreter, ... on VAX.

#2) How and when did you start to generate a "flow state of mind" during your career?

As a boy I was reading Walt Disney's comics. "Gyro Gearloose" was the most impressive
character to me and his statement "An engineer can invent everything" just caught me.
I was reading the German translation that added some extra fun:  "Dem Intschinör ist nix zu schwör!".
It became my personal mission statement:  "For a real engineer ‘IMPOSSIBLE’ doesn’t exist !"
It became a red trace throughout my whole life. And the epigenetic 'fighter gen' inherited from my
first ancestor surviving the 30years war with honors formed me to never give up.  

#3)What are recommended habits inside and outside, during you own time and during
your work time, to be focused during your coding session and daily tasks?

  • For software development, you should understand the language you use down to its darkest corner. You have to be as fluent as in a foreign language you speak. You know that you are there if you use it also in your dreams.
  • Let your creativity roll on and seek to have fun with it to find the 'impossible' solution, and forget about thinking: "this can never happen!" This is just an illusion.
  • Don't accept stops by rules that are not yours. I've seen so many nonsense measurements like the number of lines by month. In the first years even the number of punched cards (!) length of code, length of lines, number of comment lines by method, sick naming conventions, .. 
  • find your solution first and make it fast and stable and leave the polishing to please Code Quality and similar tools that will never follow your mind to the  "coding clerks"  (minor qualified engineers) to please controllers and administrators and managers who are not able to follow your great ideas. 
  • Finally, share your oeuvre with a qualified software engineer that you trust, to add the minimum required comments and explanations triggered by his questions. 
  • If your employer dislikes your style., leave it. Working against your own fire of creativity and your own fun at working can never be compensated by money. I did it for some short years and was not happy at work at all. I fought for my success and had my achievements. But fun at work came back only until returned to software engineering.