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.

Configuring WebSpeed Messengers <strong>and</strong> WebSpeed Transaction Servers<br />

7–20<br />

Table 7–12: WebSpeed Agent General properties<br />

Property Description<br />

Server executable file<br />

(dynamic property)<br />

Server startup parameters<br />

(dynamic property)<br />

Either the default agent executable pathname or a<br />

different agent executable file of your choosing.<br />

You generally only need to specify a nondefault<br />

value if you have generated a new executable<br />

using the OEBUILD utility.<br />

You can update this property dynamically. Any<br />

changes will affect only new agents that start after<br />

the property value has changed; existing (running)<br />

brokers <strong>and</strong> agents are not updated.<br />

The <strong>OpenEdge</strong> startup parameters that you want to<br />

specify to start each agent.<br />

You can update this property dynamically. Any<br />

changes will affect only new agents that start after<br />

the property value has changed; existing (running)<br />

brokers <strong>and</strong> agents are not updated.<br />

PROPATH The search path that agents use to locate ABL<br />

procedures that they execute. Specify a list of<br />

directory pathnames in the form of an <strong>OpenEdge</strong><br />

PROPATH. Make sure that you have copied all of<br />

your WebSpeed Transaction Server procedures to<br />

one or more of the directories in the PROPATH.<br />

Minimum port number<br />

(dynamic property)<br />

Maximum port number<br />

(dynamic property)<br />

The minimum TCP/IP port number from a range<br />

that each agent process can listen on. When each<br />

agent starts, it allocates a port that is not being used<br />

from the specified range, up to the Maximum port<br />

number setting.<br />

You can update this property dynamically. Any<br />

changes will affect only new agents that start after<br />

the property value has changed; existing (running)<br />

brokers <strong>and</strong> agents are not updated.<br />

The maximum TCP/IP port number from a range<br />

that each agent can listen on. When each agent<br />

starts, it allocates a port that is not being used from<br />

the specified range, down to the Minimum port<br />

number setting.<br />

You can update this property dynamically. Any<br />

changes will affect only new agents that start after<br />

the property value has changed; existing (running)<br />

brokers <strong>and</strong> agents are not updated.<br />

Server application mode Development or Production.<br />

Flush statistical data<br />

(dynamic property)<br />

How often the data is flushed by the agent to the<br />

broker. This is expressed as the number of remote<br />

procedure calls between flushes.<br />

You can update this property dynamically. Any<br />

changes will affect all current <strong>and</strong> new brokers<br />

<strong>and</strong>/or agents.

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

Saved successfully!

Ooh no, something went wrong!