In any other environment, invoking system commands is considered a last resort. Especially, executing shell scripts or batch commands is a big security no-no because it’s so easy to introduce opportunities for command injection attacks this way.
I have worked in environments where auditors would check for the system() and exec() keywords in your code, and refuse to allow it to be run in a production environment.
I see no reason why webMethods should be an exception.
To create a directory, if there is no built in service to do so (I have not checked), I would suggest writing a Java service. There are plenty of examples online of how to use the java.io.File class to make a directory.
Taking your cue from the built in services, write a simple Java service to do the job. Then you can access it from your flow services.
#webMethods-General#webMethods#Integration-Server-and-ESB