From a practical perspective it might be best to avoid hard-coding values via setValue if they are likely to change. I would instead recommend using global variables or even using a config file that you host directly in the config directory of your package.
You can use a utility service to read the file and return all of the properties so that they can be used instead.
That way everything is externalised, albeit you still won’t know which values are used in which services unless you use a sophisticated naming scheme for keys.
regards,
John.
#webMethods#Integration-Server-and-ESB