Kbase P135863: Must the AdminServer be restarted whenever the Web Services Adapter (WSA) configuration is changed i
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/10/2008 |
|
Status: Unverified
GOAL:
Must the AdminServer be restarted whenever the Web Services Adapter (WSA) configuration is changed in the ubroker.properties?
GOAL:
Must the Java Servlet Engine (JSE) be restarted whenever the Web Services Adapter (WSA) configuration is changed in the ubroker.properties?
FACT(s) (Environment):
OpenEdge 10.x
All Supported Operating Systems
FIX:
You do not need to restart the AdminServer when making configuration changes to the WSA, but you have to restart the Java Servlet Engine (e.g. Tomcat). The WSA servlet will access the ubroker.properties during startup and apply the new changes.
The only exception is the wsaUrl. The AdminServer needs to know on which URL to communicate with the WSA, for example for when you deploy a Web Service application. When you change the wsaUrl in the ubroker.properties, the AdminServer does not pick this up dynamically, so it requires a restart. Furthermore the wsaUrl is not something you would change often in a production environment. If you do have to change the wsaUrl frequently in your production environment, then the alternative to restarting the AdminServer is to remove the WSA instance (e.g. wsa1) and to recreate it again (backing up your uborker.properties first).