As an added point, if ever have pipeline variables that you want to write to the server.cnf file, you can call the wm.server.admin.setSettings service.
To call this service, you will have to add a service to your Flow first. Any service will suffice because you will be going to the Properties tab to change the path to the service. Replace the namespace of the service with “wm.server.admin.setSettings”.
Go back to your Pipeline tab and you will see that the setSettings service has no Service In inputs or outputs.
Whatever you have in the pipeline when this service is called will be written to the server.cnf file so be aware of your pipeline variables. Invoking pub.flow:clearPipeline may be in order here.
This is the same service that “Extended Settings” invokes so if you name your variables properly, you have the ability to overwrite server.cnf values or add new ones.
I have used this service to load variables from a config file into the Server Configuration file at runtime.
#webMethods#B2B-Integration#Integration-Server-and-ESB