Finally (a few months after previous release) it´s commercially available.
It keeps getting bigger and broader, so hard to get up to date with the offerings.
Any toughs? any advice? any doc?
Architect of the SmartComponent Library and WinKit
Thanks. It covers the "soft" facts of upgrading.
But who will give the hard facts , or opinions on the moving target is has become openedge?
quite a lot of new tech. and so little time to keep up.
it's been 2 days since I started to embrace the REST appserver, and now there is a pacific (competing?) server..
What would be a safe bet to adopt? since I have no source code written yet...
Is it the due path to follow? If I'm about to start developing remote clients, should I wait few hours to get 11.5 and start scratching on Pacific?
Hope to be able to express my toughs and confusions.
> quite a lot of new tech. and so little time to keep up. > it's been 2 days since I started to embrace the REST appserver, and now there is a pacific (competing?) server..
Flag this post as spam/abuse.
Just to add a small side note:
“PAS for OE is an evolution of, and replacement for, the OE AppServer (ie the pre 11.5 product).”
The classic OpenEdge AppServer is still available!
Yes, let's be very clear that the OpenEdge AppServer continues to be part of the OpenEdge product offering in OE11.5 and beyond. The Pacific Application Server for OpenEdge is offered as a more performant and less resource-consuming alternative.
As Peter points out, your code can be written to operate in either AppServer without much effort.
Which suggests, of course, that if one is just starting out, there would be a good reason to go PASOE.
Consulting in Model-Based Development, Transformation, and Object-Oriented Best Practice http://www.cintegrity.com
Good point Thomas- for those who have not started to take advanted of AppServer capabilities, we would strongly suggest starting with the Pacific Application Server (PAS) for OpenEdge. The advantages over the current OpenEdge AppSever will stand on their own merits, and we also believe that the PAS for OpenEdge can make it a bit easier when contemplating application modernization and a migration to using an AppServer.
There will be a difference in the URL that exposes the REST service, but beyond that the code is portable.
You should be ok.
For both PAS for OE and generic Tomcats the REST service's URL may change according to the name of the deployed web application hosting it. The relative portion of the URL that starts with 'rest/...' remains the same.
/test1/rest/warehouse/east/status ( deployed from warehouse.war )
is the same REST service as
/live/rest/warehouse/east/status ( deployed from warehouse.war )
I'm, a little confused. The PAS is being promoted here as a replacement for the existing AppServer. I've taken a look at the PAS documentation, and it appears that it only supports HTTP/HTTPS connections.
I use the existing AppServer in the following ways:
It looks like the PAS will easily replace the standard AppServer for SOAP and REST but what about the others?
Did I miss something in the documentation?
I'm, a little confused. The PAS is being promoted here as a replacement for the existing AppServer. I've taken a look at the PAS documentation, and it appears that it only supports HTTP/HTTPS
this post as spam/abuse.
That was very helpful.
Do you know of plans to support WebSpeed?
It is on our backlog, and something that we are looking at seriously. As this is a future possible feature, we are limited by what we can say about if and/or when we might implement this- there are revenue recognition implications that we have to be mindful of.
I will add that we have settled on a common AppServer technology for OpenEdge, Rollbase and Corticon, so the direction of having one vs. several is clear.