Displays the property settings associated with a NameServer configuration and checks that the syntax and values are valid. The NSCONFIG utility runs locally on the machine where the AdminService is running. The utility does not run across the network.
Specifies which existing NameServer configuration to examine. The name must match the name of an existing NameServer configuration in the specified properties file. If you do not specify a NameServer, the NSCONFIG utility analyzes all NameServer configurations defined in the properties file specified by the -propfile parameter.
-propfile path-to-properties-file
Specifies a filename or pathname to a file that contains the property settings to be validated, for example, test.properties. If a filename or pathname is not specified, it defaults to the installation version of the ubroker.properties file, such as:
install-path\properties\ubroker.properties in Windows
install-path/properties/ubroker.properties on UNIX
-validate
Checks the syntax and values of property settings defined in the specified properties file.
-help
Displays command-line help.
Notes
Never needed if you always use OpenEdge Management or OpenEdge Explorer.
A single NameServer can simultaneously support all of the AppServer, WebSpeed, and DataServer products using OpenEdge Management or OpenEdge Explorer.
Example
The following table shows two examples that use the NSCONFIG command. Assume the NameServer is NS1.
Table 101. NSCONFIG command examples
Task
Command
View a NameServer configuration
nsconfig -name NS1
View a NameServer configuration defined within a different property file
install-path \properties\ubroker.properties in Windows