Kbase 18606: How to Migrate Progress V8 AppServer to Progress V9 Appserver
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Verified
GOAL:
How to Migrate Progress V8 AppServer to Progress V9 Appserver
FACT(s) (Environment):
Progress 8.x
Progress 9.x
CAUSE:
To easily move a version 8 AppServer to a version 9, use parameters that cause an application server instance to function similar to a V8 AppServer.
FIX:
Migration of an existing Version 8 AppServer installation can be achieved in a few steps. To be able to configure unified brokers, an AdminServer process must be started either local or remote.
Progress 9.0 AppServer allows business logic to run in one of three operating modes. State-reset, state-aware, and stateless.
Version 8.x AppServer had one 'operating mode'.
To migrate, you need to configure the equivalent of this 'operating mode' which is state-reset operating-mode in Version 9.
Progress 9.0 AppServer can make use of three types of control procedures.
-- Startup - shutdown procedures,
-- connect - disconnect procedures and
-- activate - deactivate procedures.
Version 8 AppServer had one type of 'control procedure';
-- connect - disconnect procedures.
The equivalent of 'connect - disconnect' procedures in Version 8 is 'startup - shutdown' procedures in Version 9.
Creating an initial Application Server context like connect to a database, starting persistent procedures is now better realized in a Startup procedure. Connect procedures are useful to implement security -- performing user verification and authorization and restricting access to procedures based on the privileges of the user logging in.
Server parameters --
Startup parameters accept valid database connection parameters.
Minimum and maximum portnumbers allow you to specify a specific port-range in which Application Server processes will be started.
Server pool parameters are used to set the number of Application Server processes to be started by the broker at broker startup.
Advanced --
Brokers need to register with a NameServer. Select a NameServer from the combo-box.
Priority weight is used for loadbalancing if loadbalancing option is purchased.
Server Control procedures.
Specify a startup procedure name. Startup procedure requires one input parameter. The value can be left blank.
Specify a connect procedure name. Connect procedure requires three input parameters as with version 8.
Existing source needs to be compiled in version 9.