13.01.2013 Views

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>OpenEdge</strong> <strong>Management</strong> or <strong>OpenEdge</strong> Explorer command line utilities <strong>for</strong> the <strong>Data</strong><strong>Server</strong><br />

-validate<br />

-help<br />

Checks the syntax and values of property settings defined in the specified<br />

properties file.<br />

Displays command line help.<br />

Notes • The ubroker.properties file stores all the configuration definitions <strong>for</strong> each<br />

instance of the Name<strong>Server</strong>, App<strong>Server</strong>, <strong>Data</strong><strong>Server</strong> and WebSpeed Transaction<br />

<strong>Server</strong> products. Each configuration definition contains environment variables,<br />

registry entries if Windows, and property settings <strong>for</strong> each product instance.<br />

<strong>OpenEdge</strong> <strong>Management</strong>/<strong>OpenEdge</strong> Explorer and certain command line utilities<br />

such as MSSCONFIG, use this file to store, validate and manage the<br />

configurations <strong>for</strong> the products.<br />

• The ubroker.properties file is installed in the properties subdirectory of the<br />

<strong>OpenEdge</strong> installation directory. For example,<br />

%DLC%\properties\ubroker.properties in Windows.<br />

• The file consists of a hierarchical structure of configuration entities, where parent<br />

entities provide configuration in<strong>for</strong>mation that you can override or extend in each<br />

child entity. Each configuration entity has a name that begins the entity definition,<br />

and the definition contains configuration settings <strong>for</strong> one or more product<br />

instances.<br />

For example, the <strong>Data</strong><strong>Server</strong> <strong>for</strong> MS <strong>SQL</strong> <strong>Server</strong> configurations in<br />

ubroker.properties can include:<br />

Configuration entity name Configuration entity function<br />

[UBroker] Defines default property settings <strong>for</strong><br />

all Name<strong>Server</strong>, App<strong>Server</strong>,<br />

<strong>Data</strong><strong>Server</strong>, and WebSpeed<br />

Transaction <strong>Server</strong> brokers.<br />

[UBroker.MS] Defines default property settings <strong>for</strong><br />

all instances of <strong>Data</strong><strong>Server</strong>s <strong>for</strong> MS<br />

<strong>SQL</strong> <strong>Server</strong>.<br />

[UBroker.MS.product–instance–name] Defines property settings <strong>for</strong> this<br />

instance of a <strong>Data</strong><strong>Server</strong> <strong>for</strong> MS <strong>SQL</strong><br />

<strong>Server</strong>. The ubroker.properties file<br />

can contain several of these entities<br />

each with a unique<br />

product–instance–name.<br />

• Parent entities provide default values <strong>for</strong> all of their child entities. For example, the<br />

parent [UBroker] contains a set of definitions that can be inherited by its child<br />

[UBroker.MS], and then again by its child<br />

[UBroker.MS.product–instance–name]. However, at any child level, a<br />

redefinition of any value supersedes the default value of its parent. All children<br />

from the redefinition level down inherit this new value.<br />

<strong>OpenEdge</strong> <strong>Data</strong> <strong>Management</strong>: <strong>Data</strong><strong>Server</strong> <strong>for</strong> <strong>Microsoft</strong> <strong>SQL</strong> <strong>Server</strong> 341

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!