Modifying properties of a WSA instance

To modify most startup properties of a WSA instance, you must stop and start the Java container associated with the WSA instance. However, the following WSA properties can be modified at run time (while the WSA is running):

Any modifications to these properties take affect immediately, but do not remain once the WSA is restarted. Changing these properties at run time does not save the new properties values. To make the run-time properties changes persistent you must also change the values of the startup properties.

To modify the run-time properties of a WSA instance, you can use OpenEdge Management/OpenEdge Explorer or the WSAMAN utility. To modify the startup properties of a WSA instance, use OpenEdge Management or OpenEdge Explorer.

For more information on OpenEdge Management or OpenEdge Explorer, see the online help. For more information on the WSAMAN utility, see Using the WSA Management Utility (WSAMAN) and Commandand Utility Reference.

At times, you might find that in order to update a WSA configuration, you must edit the ubroker.properties file by hand using a text editor, especially when you need to update the WSA security configuration. When you complete a manual update of the ubroker.properties file, use the WSACONFIG utility to verify the integrity of the WSA configurations in the file.

Note: You can also use the mergeprop utility installed with OpenEdge to manually edit the ubroker.properties file. For information on using mergeprop, see OpenEdge Getting Started: Installation and Configuration.

The WSACONFIG utility displays the property settings associated with WSA configuration, and checks that the syntax and values are valid. You must run the WSACONFIG utility locally on the machine on which the WSA is running. The utility does not run across the network.

This is the syntax used to invoke the WSACONFIG utility:

Table 19. Syntax
wsaconfig [ [[ -name WSA-instance-name] [ -propfile path-to-properties-file] [ -validate ] ]\| -help ]

For more information on the WSACONFIG utility, see WSACONFIG.

For example, the following command validates the syntax and views the configurations of all WSA instances defined within the test.properties file located in the current working directory: