Progress
DataServer for
Microsoft SQL Server
Guide
MSSCONFIG Utility
Use the MSSCONFIG utility to help you debug existing DataServer for SQL Server™ configurations defined in a properties file, such as the
ubroker.properties
file. This utility displays the property settings associated with a DataServer for SQL Server™ configuration, and checks that the syntax and values are valid.The MSSCONFIG utility runs locally, on the machine on which the AdminServer is running. The utility does not run across the network:
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 theubroker.properties
file, such as%DLC%\properties\ubroker.properties
on Windows NT.SYNTAX
Operating System
Syntax Windows mssconfig
[
[
[ -name DataServer-name ]
[ -propfile path-to-properties-file ]
[ -validate ]
]
| -help
]
PARAMETERS
-name DataServer–nameSpecifies which existing configuration to examine. The name must match the name of an existing DataServer for SQL Server™ configuration defined in the specified properties file. If you do not specify a DataServer by name, the MSSCONFIG utility analyzes all DataServer for SQL Server™ configurations defined in the properties file specified by the
-propfile
parameter.-validate
Checks the syntax and values of property settings defined in the specified properties file.
-help
Displays command-line help.
NOTES
- The
ubroker.properties
file stores all the configuration definitions for each instance of the NameServer, AppServer, DataServer and WebSpeed Transaction Server products. Each configuration definition contains environment variables, registry entries if Windows NT, and property settings for each product instance. Progress Explorer and certain command-line utilities such as MSSCONFIG, use this file to store, validate and manage the configurations for the products.- The
ubroker.properties
file is installed in theproperties
subdirectory of the Progress installation directory. For example,%DLC%\properties\ubroker.properties
on Windows NT.- The file consists of a hierarchical structure of configuration entities, where parent entities provide configuration information that you can override or extend in each child entity. Each configuration entity has a name that begins the entity definition, and the definition contains configuration settings for one or more product instances.
For example, the DataServer for SQL Server™ configurations in
ubroker.properties
may include:- Parent entities provide default values for all of their child entities. For example, the parent
[UBroker]
contains a set of definitions that can be inherited by its child[UBroker.MS]
, and then again by its child[UBroker.MS.
product–instance–name]
. However, at any child level, a redefinition of any value supersedes the default value of its parent. All children from the redefinition level down inherit this new value.- Optionally, you may edit the
ubroker.properties
file using a text editor such as vi or Notepad. If you want to manually edit this file to create or modify a product configuration, begin by making a backup copy from the installedubroker.properties
file (and naming it for example,test.properties
). Once you edit the properties file, use the relevant validation utility such as MSSCONFIG to validate the changes and make sure there are no syntax errors or conflicts.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |