Hi,
I'm not familiar with "template designer" - is that CRM-specific functionality? If so, you might find some more info in that forum?
Our experience has been with web services in both ECC5 - using the old WSCONFIG / WSADMIN transactions, and then ECC6 using the new framework with development of the Service Definition within SE80 (transportable) and the Runtime Definitions in SOAMANAGER (not transportable).
With ECC6, we develop the Service Definition in SE80 in DEV (typically sitting over an RFC-enabled function module) and the Service Definition is transported to Test and, eventually, Production. We create the Service Definition specifying the lowest level of security (e.g. Authentication = none) because it will be the Runtime Definition in SOAMANAGER that defines what the consumer will need in order to interact with SAP.
For example, in DEV we might create two Runtime Definitions in SOAMANAGER for the same SAP web service Service Definition, one with anonymous login (so the the developer of the consumer to get their code running without worrying about security) and another with X.509 security (to match what we may have in Test and Production). We sometimes need to have different security depending on the SAP client - so we run SOAMANAGER in the relevant DEV client and create the Runtime Definition - these show up in SICF along the lines of:
z_my_web_service_name
201 (SAP client #)
servicename (as per SOAMANAGER)
bindingname (as per SOAMANAGER)
anotherservicename
anotherbindingname
204
yetanotherservice
bindingnumber3
Jonathan