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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<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 />

Notes • A single Name<strong>Server</strong> can simultaneously support all of the App<strong>Server</strong>,<br />

WebSpeed and <strong>Data</strong><strong>Server</strong> products using <strong>OpenEdge</strong> <strong>Management</strong> or<br />

<strong>OpenEdge</strong> Explorer.<br />

• 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 NSCONFIG, use this file to store, validate and manage the configurations<br />

<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 />

The Name<strong>Server</strong> configurations in ubroker.properties can include:<br />

Configuration entity<br />

name<br />

Configuration entity<br />

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 />

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

all instances of a Name<strong>Server</strong>.<br />

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

instance of a Name<strong>Server</strong>. The<br />

ubroker.properties file can contain<br />

several of these entities each with a<br />

unique 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 />

[Name<strong>Server</strong>], and then again by its child<br />

[Name<strong>Server</strong>.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 />

Optionally, you can edit the ubroker.properties file using a text editor such as<br />

Notepad. If you want to manually edit this file to create or modify a product<br />

configuration, begin by making a backup copy from the installed<br />

ubroker.properties file (and naming it <strong>for</strong> example, test.properties). Once<br />

you edit the properties file, use the relevant validation utility such as NSCONFIG<br />

to validate the changes and make sure there are no syntax errors or conflicts.<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> 345

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

Saved successfully!

Ooh no, something went wrong!