Tag Archives: Progress OpenEdge

Issue with Progress OpenEdge AppServer 10.x

You need to escape the “$” character in hidden UNC paths in the ubroker.properties file.

http://progresscustomersupport-survey.force.com/ProgressKB/articles/Article/AppServerdoesnotstartasDomainUser?retURL=%2FProgressKB%2Fapex%2FProgressKBHome&popup=false

Advertisements

Progress Software Lowers Its Sights

The catalyst for Progress’ shift: activist investor Starboard Value LLP. Starboard’s public letter to new Progress CEO Jay Bhat [link] laid out the ugly financial picture the company had become. PRGS rose substantially after the announced strategy shift, as you’d expect from the promise of a cleaned-up balance sheet. But the hard challenges of future growth remain. First, there’s still no value greater than the sum of Progress’ parts. Second, OpenEdge remains the core of the company’s revenue (and culture), and it is an old platform. Yes, Progress has added BPM and a cloud-deployment option to the OpenEdge platform. But the product remains primarily interesting to long-time Progress ISVs, not the broader market. Persuading the wide world of developers to even consider OpenEdge will be an immense task.

Right on target.

http://blogs.forrester.com/john_r_rymer/12-04-29-progress_software_lowers_its_sights

Progress OpenEdge AppServer Session Models

Session-Managed

The AppServer maintains context between requests for each client that it services, and each such clientparticipates in a persistent connection to the AppServer.

The connected AppServer is dedicated to serving that one client until the connection between them is terminated.

In this session model, all client requests are single-threaded, meaning that the AppServer does not handle another request from the same client until it has completed and responded to any pending request from that client.

Session-Free

The AppServer maintains no context for any client that it services.

Requests from a session-free client are handled by any available AppServer (and AppServer agent) that supports the required application service.

Thus, a session-free AppServer executes requests from all clients as it receives them, and completes each request independently of any prior request.

In this session model, all requests from a client are multi-threaded, meaning that multiple requests from a single client can be executed in parallel, as AppServer resources permit.

Refer to page 1-13 of the OpenEdge Application Server: Developing AppServer Applications guide for details.