are there core code modifications needed when migrating from Classic to PAS?

[ChadThomsonPSC]

"Is there any core code modification needed when we migrate it classic to PAS. apart from the properties or connection files"

[ChadThomsonPSC]

There aren't any modifications required to your classic application's server code to have it run on PAS.

For Classic AppServer:

• The PAS AVM has configuration points for AS event hooks: sessionStartup, sessionActivate, sessionConnect, etc.
  • If you have procedures in your Classic environment, those should be portable to PAS as-is

For Classic WebSpeed:

• Mapped HTML does not work
• in many cases, you might benefit from reimplementing your WebSpeed code with new 'webhandler' classes

Both:

• plenty of opportunity to improve security (authZ vs authN, use CPO)
• don't forget about the client-side
  • AppServer clients will need to use a different connection string, and the client is responsible for indicating desired session-model
  • WebSpeed clients (browsers) will need to have their URLs, which may contain a segement for the WebSpeed Messenger, will need to be translated to the PAS /web/ transport
• Test, observe, change, repeat
  • consider PAS to be backward-compatible with Classic, which means your original code will run, but in a very new way
  • if you migrate your code and things work the first try, great -- don't stop -- you'll still want to continue testing concurrent access to your services