Appserver connection
- Thread starter atuldalvi
- Start date
taqvia
Member
How did you configure the appserver? through progress explorer or modifying the ubroker.properties file manually. check for the nameserver with which the appserver is getting registered with. check that the particular nameserver is running or not by running the command nsman <nameserver name> -q -port <portnumber> default port is 20931 if not started specifically on other port.If name server is not running start it and restart the appserver.
Arshad
Arshad
Setting up the AppServer with a DataBase
Step by Step
* note this is for the default settings of the AppServer (after a new installation of Progress) on Windows XP operating system.
We will try to use the default settings since this is the easiest way:
- check to see if the corresponding Progress Admin Service is running, whatever version you try to put ‘online’, in Control Panel -> Administrative Tools -> Services
- start the Progress Explorer Tool connect to “localhost” in (domain\username and password or just hit OK)
- go to Databases -> New, give it a name e.g. sports2000
- specify path to the database x:\path\sports2000.db (Warning: the database from e.g. c:\Progress\10.1B\sports2000.db directory can not be used since Progress won’t allow it, make a safe copy somewhere else, out of the default Progress installation directory)
- Set Port for database (properties) eg. 9999
- Start the database (In case of an error message, the database should be checked if can be connected locally to an AppBuilder session, the database should be from the directory of progress version we want to run the AppServer session)
- in the NameServer option, check if default name server NS1 is up and running
- in the AppServer option create a new broker (name as you wish) or use asbroker1, set up the parameters for Agent propath just us the default ones and add your propath e.g @{WinChar Startup\PROPATH};@{WorkPath};C:\ProiectDotNet;C:\ProiectDotNet\AppService
- you can use the default port number 3090 or specify yourself the port number
- connect the AppServer with the database: Agent / Server startup parameters, we will add the database server it’s name and the connection port of our previously created database server broker e.g -db sports2000 -N tcp -H localhost -S 9999
- Add in x:\windows\drivers\etc\services add a line for our newly created AppServer broker, our default name is asbroker1(if you named your broker please proved that name, also for the port number) we will add a line in the services file e.g. asbroker1 3090/tcp and hit ENTER (there should be a CR/LF at the end of the file)
- start the broker and check with the Info icon if it works (if you followed the previous steps it should work just fine)
Testing the newly created AppServer broker:
- Create a procedure named customer.p, then save it in the a directory that is in the propath and add the following code:
FIND FIRST customer.
IF AVAIL(customer) THEN
RETURN customer.NAME.
ELSE
RETURN "".
- Create a second procedure that will connect to the AppServer broker and run the procedure, then display the returned value:
CREATE SERVER hAppServer.
hAppServer:CONNECT('-H localhost -S 5162 -AppService asbroker1') no-error.
RUN customer.p ON hAppServer.
MESSAGE RETURN-VALUE
VIEW-AS ALERT-BOX INFO BUTTONS OK.
- If everything went well the message with the first customers name should be displayed
