How to move PASOE instanse

Posted by Valeriy Bashkatov on 16-Mar-2016 04:17

Hello, 

How to move PASOE DEV instance from one machine to another were are installed  PASOE PROD?
Is there a guide for that?

Regards,
Valeriy

Posted by Roy Ellis on 17-Mar-2016 07:43

Hi Valeriy,

there is no one answer that handles all situations.  There are several ways to move your application from development to production.  The best way to deploy to production for you will depend on your situation, application and configuration needs.

Examples:

1) AppServer only - if your application is AppServer only then you can copy the r-code to a newly created instance on your production machine, set PROPATH, db connections, event values in openedge.properties and you are done

2) If you have self contained web apps (REST, SOAP) with r-code included you could export the correct war file and deploy it as new application on your newly created instance on your production machine

3) if you have everything in the instance with multiple ABL applications you may want to ZIP up your current development instance, copy it to your production machine, unzip it and then run "tcman register" to modify the script files and register the instance.  Note: you should upgrade to 11.6.1 before running "tcman register because of some known issues.

I hope this helps, Roy

Posted by Peter Judge on 16-Mar-2016 09:56

You can zip up the instance folder and copy it to a new machine.

Use the TCMAN REGISTER command to tell the target DLC that it's there.

And then follow the doc at community.progress.com/.../2869  to make it production-ready

Posted by David Cleary on 16-Mar-2016 10:14

The paper didn't cover moving a dev instance over to production. There are additional things that need to be done to make the instance equivalent to one created by a production server. We will look to add that information in a future update of the paper. At a minimum, the ROOT application is replaced with one that does nothing. Also, manager and oemanager web applications are not deployed.

Dave

All Replies

Posted by Peter Judge on 16-Mar-2016 09:56

You can zip up the instance folder and copy it to a new machine.

Use the TCMAN REGISTER command to tell the target DLC that it's there.

And then follow the doc at community.progress.com/.../2869  to make it production-ready

Posted by David Cleary on 16-Mar-2016 10:14

The paper didn't cover moving a dev instance over to production. There are additional things that need to be done to make the instance equivalent to one created by a production server. We will look to add that information in a future update of the paper. At a minimum, the ROOT application is replaced with one that does nothing. Also, manager and oemanager web applications are not deployed.

Dave

Posted by Valeriy Bashkatov on 17-Mar-2016 02:27

Many thanks Peter and David!

Meanwhile, my client is now ready to run in production environments PASOE instance under the OpenEdge 11.6.

David,

In this regard, could you please describe in more detail about additional things of which you speak? At least here or will you be kind  to specify where it can be written in the documentation for the OpenEdge.

This question is really very important and I will be very grateful to you for this help!

Regards,

Valeriy

Posted by Roy Ellis on 17-Mar-2016 07:43

Hi Valeriy,

there is no one answer that handles all situations.  There are several ways to move your application from development to production.  The best way to deploy to production for you will depend on your situation, application and configuration needs.

Examples:

1) AppServer only - if your application is AppServer only then you can copy the r-code to a newly created instance on your production machine, set PROPATH, db connections, event values in openedge.properties and you are done

2) If you have self contained web apps (REST, SOAP) with r-code included you could export the correct war file and deploy it as new application on your newly created instance on your production machine

3) if you have everything in the instance with multiple ABL applications you may want to ZIP up your current development instance, copy it to your production machine, unzip it and then run "tcman register" to modify the script files and register the instance.  Note: you should upgrade to 11.6.1 before running "tcman register because of some known issues.

I hope this helps, Roy

Posted by Valeriy Bashkatov on 17-Mar-2016 08:01

Thank you so much Roy!

No doubt this will help us very much.

Regards,

Valeriy

This thread is closed