How to install and configure Version 10 AppServer.
Problem:
How to install and configure Version 10 AppServer.
Solution:
Setting Up Progress V10 Application Server
Starting in Progress OpenEdge 10, Webspeed is bundled with the Application Server. In Progress version 9, WebSpeed and AppServer were separately priced products. The V10 basic AppServer setup is like that for V9 WebSpeed. The only difference is that Progress will not compile source code (".p" programs) on the fly with the V10 basic AppServer, so programs must be precompiled to ".r" files.
Install WebSpeed
Shut down the Admin Service in Windows Control Panel | Administrative Tools | Services if it is running.
If you already have Progress installed, you will get an error message; answer Yes to continue.
Exit all Windows programs and press the Next button.
Enter your serial and control numbers and press the Accept button.
Application Svr will appear under Product to be installed; Press the Next button.
Make sure you know what your web server and script folder are and press the Next button.
Accept the default installation folder and press the Next button.
Select COMPLETE and press the Next button.
Select your web server type and browse to select your web root and script folders and press the Next button.
Select your language and press the Next button.
Confirm the formats and press the Next button.
Accept the security default and press the Next button.
Accept the summary and press the Next button.
After installation select the Finish button.
Restart your computer and install the latest Progress Maintenance Pack.
Configure WebSpeed
Open the Progress Explorer and add Server "localhost". After installation of WebSpeed, the server will have to be re-added if it already existed. However, any databases you already had set up should still be set up once you connect to the localhost server.
Open the WebSpeed tree node under the server.
Select wsbroker1 under WebSpeed, right-click it, and select Properties.
Open Broker | General and change the working directory to the location of your application programs.
Open Agent | General and change the following:
* Agent startup parameters - add a connection to your database with a "-db" or "-pf" option
* Agent application mode - change to "Development" mode
Open Agent | Pool Range and change the initial, minimum and maximum number of agents to the appropriate values for your development or deployment environment, up to the number licensed.
(optional) Open Broker | Advanced Features and increase the "Auto trim timeout" from the default 1800 (seconds) to a larger value, to reduce the number of log entries created when WebSpeed tries to close unused agents (every half hour). If you have set the number of agents properly this is an unnecessary activity that does nothing but clog up the log file with useless entries.
To test the WebSpeed connection use a web browser to connect to
http://localhost/scripts/cgiip.exe/WService=wsbroker1/webutil/ping.p
The Agent application mode must be in Development mode to perform this test. If it is in Production mode, the ping.p test will fail and return "Unable to find web object file 'ping.p'.
When deploying, set the Agent application mode back to Production mode.
Return to Knowledge Base index
Special thanks to Roger Blanchard at Osprey Retail Systems for the above images and most of the content.
How to install and configure Version 10 AppServer.
Solution:
Setting Up Progress V10 Application Server
Starting in Progress OpenEdge 10, Webspeed is bundled with the Application Server. In Progress version 9, WebSpeed and AppServer were separately priced products. The V10 basic AppServer setup is like that for V9 WebSpeed. The only difference is that Progress will not compile source code (".p" programs) on the fly with the V10 basic AppServer, so programs must be precompiled to ".r" files.
Install WebSpeed
Shut down the Admin Service in Windows Control Panel | Administrative Tools | Services if it is running.
If you already have Progress installed, you will get an error message; answer Yes to continue.
Exit all Windows programs and press the Next button.
Enter your serial and control numbers and press the Accept button.
Application Svr will appear under Product to be installed; Press the Next button.
Make sure you know what your web server and script folder are and press the Next button.
Accept the default installation folder and press the Next button.
Select COMPLETE and press the Next button.
Select your web server type and browse to select your web root and script folders and press the Next button.
Select your language and press the Next button.
Confirm the formats and press the Next button.
Accept the security default and press the Next button.
Accept the summary and press the Next button.
After installation select the Finish button.
Restart your computer and install the latest Progress Maintenance Pack.
Configure WebSpeed
Open the Progress Explorer and add Server "localhost". After installation of WebSpeed, the server will have to be re-added if it already existed. However, any databases you already had set up should still be set up once you connect to the localhost server.
Open the WebSpeed tree node under the server.
Select wsbroker1 under WebSpeed, right-click it, and select Properties.
Open Broker | General and change the working directory to the location of your application programs.
Open Agent | General and change the following:
* Agent startup parameters - add a connection to your database with a "-db" or "-pf" option
* Agent application mode - change to "Development" mode
Open Agent | Pool Range and change the initial, minimum and maximum number of agents to the appropriate values for your development or deployment environment, up to the number licensed.
(optional) Open Broker | Advanced Features and increase the "Auto trim timeout" from the default 1800 (seconds) to a larger value, to reduce the number of log entries created when WebSpeed tries to close unused agents (every half hour). If you have set the number of agents properly this is an unnecessary activity that does nothing but clog up the log file with useless entries.
To test the WebSpeed connection use a web browser to connect to
http://localhost/scripts/cgiip.exe/WService=wsbroker1/webutil/ping.p
The Agent application mode must be in Development mode to perform this test. If it is in Production mode, the ping.p test will fail and return "Unable to find web object file 'ping.p'.
When deploying, set the Agent application mode back to Production mode.
Return to Knowledge Base index
Special thanks to Roger Blanchard at Osprey Retail Systems for the above images and most of the content.