top of page
Writer's pictureRajesh S Nair

NameServer,AppServer,AdminServer,Webspeed Configuration and Commands

Since we are done with the theoritical part of the various entities , lets see how we use them in a real work scenario for a progress DB environment. Admin Server Admin server properties is configured in the AdminServerplugins.properties file present in the <openedge-install-dir>/properties path.

The default port of admin server is 20931.

To start admin server , use

proadsv -start

To start in a different port, use

proadsv -port <portnumber> -start To stop admin server use,

proadsv -stop To query the admin server status, use proadsv -query NameServer

We can configure nameserver instance using the ubroker,properties file.The different commands to start,stop,query nameserver are:

To Stop:

nsman -name <nameserver-name> -stop

To Start:

nsman -name <nameserver-name> -start To query

nsman -name <nameserver-name> -query

Configuring Appserver and Webspeed

The appserver and webspeed configuration is done in the ubroker.properties file,By default wsbroker1 and asbroker1 entries can be found as sample configuration for webspeed and appserver respectively.

The following would be how a configuration for a new webspeed will look like:



The following would be how a configuration of a new appserver will be:



Once configuration done, you need to start admin Server, web speed and app Server.

Admin Server Start/Stop/Query

/usr/dlc/bin/proadsv –start/stop/q

App Server Start/Stop/Query

asbman –i <appServer-broker-name> -start/stop/q

Web speed Start/Stop/Query

wtbman –i <webspeed-broker-name> -start/stop/q

Checking status of naming Server

nsman –i  NS1  -q

410 views0 comments

Recent Posts

See All

Comments


bottom of page