30.11.2012 Views

OpenEdge Management and OpenEdge Explorer: Configuration

OpenEdge Management and OpenEdge Explorer: Configuration

OpenEdge Management and OpenEdge Explorer: Configuration

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.

Creating a NameServer<br />

Creating a NameServer<br />

<strong>OpenEdge</strong> <strong>Management</strong> <strong>and</strong> <strong>OpenEdge</strong> <strong>Explorer</strong> provide a sample configuration NameServer<br />

instance (NS1) that it uses as a default.<br />

You can create two types of NameServer instance:<br />

• Local — Where the instance definition resides on, <strong>and</strong> the NameServer itself executes on,<br />

the selected host.<br />

• Remote — Where the instance definition is a reference to a NameServer that resides <strong>and</strong><br />

executes on a machine that is remote from the selected host.<br />

To create a NameServer:<br />

1. Click Resources in the management console menu bar. The main resource types appear in<br />

the list frame.<br />

2. In the Details frame, click New Resource Monitor. The New Resource Monitor page<br />

appears.<br />

3. Click NameServer. The NameServer <strong>Configuration</strong> page appears.<br />

4. Type the name of the new NameServer in the field provided.<br />

Note: The NameServer name is case sensitive <strong>and</strong> can include any character except a<br />

period (.) or square brackets ([ ]). The name must be unique among all configured<br />

NameServer names.<br />

5. Click Save. The NameServer <strong>Configuration</strong> page appears, allowing you to configure the<br />

NameServer’s properties. (For details about the properties, see Table 4–1.)<br />

Once you create a NameServer instance, you cannot change the location setting unless you<br />

delete <strong>and</strong> recreate the instance.<br />

Note: If you are defining a remote NameServer instance, set its host name <strong>and</strong> port<br />

number properties to reference a NameServer that is defined as a local NameServer<br />

on some other machine in your network. For details, see the “Configuring remote<br />

instances” section on page 4–10.<br />

4–13

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

Saved successfully!

Ooh no, something went wrong!