01.06.2013 Views

OpenEdge 11 - Progress Software

OpenEdge 11 - Progress Software

OpenEdge 11 - Progress Software

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Progress</strong> ® ObjectStore ®<br />

<strong>Progress</strong> ® <strong>OpenEdge</strong> ®<br />

<strong>Progress</strong> ® Orbacus <br />

<strong>Progress</strong> ® Orbix ®<br />

<strong>Progress</strong> ® Savvion<br />

<strong>Progress</strong><br />

OPENEDGE<br />

® Sonic<br />

<strong>11</strong><br />

®<br />

BUILD DYNAMIC, BUSINESS PROCESS-CENTRIC<br />

APPLICATIONS FOR SECURE DEPLOYMENT ACROSS<br />

ANY PLATFORM, ANY MOBILE DEVICE, AND ANY CLOUD<br />

www.progress.com<br />

Are your customers and end users demanding applications that can adapt<br />

to their changing needs, such as support for mobile devices, constantly evolving<br />

business processes, and deployment in the Cloud? At <strong>Progress</strong> <strong>Software</strong>, we have<br />

always prided ourselves in our ability to simplify the job of creating and operating<br />

the world’s best business applications. In order to survive and thrive in today’s world<br />

of quickly evolving markets and technologies, you must be able to respond quickly<br />

while coping with strict budgets and tight timeframes. If you can deliver rapidly<br />

customized applications with minimum disruption to business and IT systems, you<br />

will be successful.<br />

With <strong>OpenEdge</strong> <strong>11</strong>, you can develop dynamic solutions that incorporate<br />

business process and integration capabilities securely across multiple platforms<br />

and devices. Whether you deploy on-premise, on a mobile device, or in the Cloud,<br />

<strong>OpenEdge</strong> <strong>11</strong> offers a single integrated development platform that is 40% more<br />

FEATURE HIGHLIGHTS<br />

KEY FEATURES<br />

<strong>OpenEdge</strong> <strong>11</strong> enables our<br />

customers and partners to<br />

deliver Responsive Business<br />

Applications through new<br />

enhancements that offer:<br />

> Mobile Development & Deployment<br />

> Multi-Tenancy<br />

> Increased Productivity<br />

> Improved Operational Excellence<br />

> Enhanced Integration & Workflow<br />

> Increased Security & Compliance<br />

> Improved Personalization<br />

> Greater User Interface Flexibility


productive and provides a 30% cost savings versus the competition. With<br />

<strong>OpenEdge</strong>, we help you grow—faster!<br />

www.progress.com<br />

<strong>OpenEdge</strong> <strong>11</strong> delivers new enhancements and benefits for enabling<br />

our customers and partners to deliver Responsive Business Applications:<br />

> Mobile Development & Deployment<br />

> Multi-Tenancy<br />

> Productivity<br />

> Operational Excellence<br />

> Integration & Workflow<br />

> Security & Compliance<br />

> Personalization<br />

> User Interface Flexibility<br />

MOBILE DEVELOPMENT & DEPLOYMENT<br />

<strong>OpenEdge</strong> Mobile provides the ability to quickly and easily extend<br />

existing <strong>OpenEdge</strong> applications to support multiple mobile devices on various<br />

2


platforms or to build new mobile apps for new business areas or new markets.<br />

Having an easy mobile app development environment tightly integrated with<br />

the familiar <strong>OpenEdge</strong> environment makes it quick and easy to develop and<br />

deploy mobile apps. Mobile apps have the power to make operations more<br />

efficient and businesses more competitive.<br />

www.progress.com<br />

With <strong>OpenEdge</strong> <strong>11</strong>.2, application developers can take advantage of<br />

a new Mobile application builder and visual designer that enables <strong>Progress</strong><br />

Developer Studio for <strong>OpenEdge</strong> to produce feature-rich Mobile applications<br />

for the iOS and Android platforms. With a “write once, deploy anywhere”<br />

approach, <strong>OpenEdge</strong> <strong>11</strong>.2 removes the need to learn device-specific languages<br />

or development environments, while enabling the creation of full-featured<br />

applications that can access all of the most important device capabilities,<br />

such as the camera, GPS, and microphone. The REST adapter, also introduced<br />

in <strong>OpenEdge</strong> <strong>11</strong>.2, provides the Mobile client’s access to the <strong>OpenEdge</strong><br />

AppServer, while ProDataSet and Temp-table support are built in using JSDO<br />

data-binding and form-based Business Entity support.<br />

MULTI-TENANCY<br />

A multi-tenant database is one which provides database support<br />

to a number of separate and distinct groups of users, also referred to as<br />

tenants. Multi-tenant applications have taken an increasing foothold in the<br />

database marketplace, largely due to the emergence of SaaS as a deployment<br />

strategy. For the SaaS application provider, a multi-tenant deployment<br />

strategy provides many benefits, especially when a Shared Tenancy approach<br />

is used. Management of the deployment can take place either at the overall<br />

application or database level, or based on tenant and user. Operational<br />

complexity is greatly reduced due to the number of shared resources and<br />

because only one instance of the application and database is involved.<br />

With <strong>OpenEdge</strong> <strong>11</strong>, developing and deploying multi-tenant applications is<br />

transformed by using an approach that is unique in the industry, reducing and<br />

even eliminating the challenges typically presented when implementing a<br />

Shared Tenancy application. This is due to two major factors:<br />

Tenant support is implemented in the database layer, and Database<br />

utilities and tools are also tenant-aware.<br />

3


www.progress.com<br />

The significant advantage of the first point is that the application no<br />

longer has to manage tenancy—simplifying the code and making tenancy<br />

completely transparent. For the second point, the operational aspects of the<br />

database are also capable of acting in a mode that is either tenant-specific or<br />

database-specific. This streamlines key functions such as index maintenance,<br />

data dump and load, object moves, and other database functions.<br />

DATABASE MULTI-TENANCY<br />

1. Multi-tenant Database Tables<br />

A key addition to the <strong>OpenEdge</strong> database is built-in support for<br />

multiple tenants within a single database. Many database vendors are<br />

promoting multi-tenancy as a new capability for SaaS and Cloud. But with<br />

<strong>OpenEdge</strong>, the unique difference is that instead of the client managing access<br />

to tenant data, the database takes care of everything. This means that<br />

minimal changes are required for application code; in fact, tenants run the<br />

exact same r-code, and utilize the exact same schema definition, as users of a<br />

non-multi-tenant instance of the same application! Furthermore, each tenant’s<br />

data is stored in database partitions that are physically separate from those<br />

of other tenants, enhancing data access and making database maintenance<br />

easier and more efficient.<br />

2. Web-based Multi-tenant Tooling as an extension of <strong>OpenEdge</strong><br />

Explorer and <strong>OpenEdge</strong> Management<br />

<strong>OpenEdge</strong> <strong>11</strong> includes the Web-based Database Administration<br />

Console as an extension of <strong>OpenEdge</strong> Explorer and <strong>OpenEdge</strong> Management.<br />

This new interface for managing tenants—including tenant users, tenant<br />

storage, and tenant security—features a brand new look and feel. A<br />

template-based approach provides for increased productivity, and the tool<br />

can also generate ABL code that developers can re-purpose in scripts or<br />

ABL applications.<br />

3. ABL APIs for multi-tenancy<br />

An extensive set of ABL APIs for multi-tenancy allows application<br />

developers to integrate tenant management into their own applications, for<br />

example to provide the capability for tenants to provision themselves, or<br />

to build multi-tenant management tools that are more customized to your<br />

development and deployment needs.<br />

4


4. SQL DDL support for multi-tenancy<br />

www.progress.com<br />

SQL has been enhanced to multi-tenancy, allowing application<br />

tenants to enjoy equivalent functionality with both ABL and SQL.<br />

*New database multi-tenancy functionality for <strong>OpenEdge</strong><br />

<strong>11</strong>.1 includes:<br />

5. Multi-tenant Governor for users per tenant<br />

With <strong>OpenEdge</strong> <strong>11</strong>.1, it is possible to limit the number of users (-n)<br />

that an individual tenant is able to connect to a multi-tenant database.<br />

6. Multi-tenant Governor for record locks per tenant<br />

This governor, available starting in <strong>OpenEdge</strong> <strong>11</strong>.1, limits the number<br />

of record locks (-L) available to a particular tenant at one time.<br />

7. Enhanced multi-tenant tooling in the <strong>OpenEdge</strong> Explorer Data<br />

Administration Console<br />

<strong>OpenEdge</strong> <strong>11</strong>.1 introduces several new capabilities to <strong>OpenEdge</strong><br />

Explorer’s Data Administration Console, making it easier to manage<br />

tenants. Included are the ability to rename tenants, tenant groups, and/or<br />

tenant domains; the ability to dump and load tenant data; and an improved<br />

user interface for filtering and batching large datasets. Tenant partition<br />

management is also made much easier with the addition of drag-and-drop<br />

support. In addition, <strong>OpenEdge</strong> Explorer includes the ability to manage the<br />

new multi-tenant governors.<br />

8. SQL support for Tenant Groups<br />

<strong>OpenEdge</strong> <strong>11</strong>.1 includes functionality that enables SQL to work with<br />

tenant groups in terms of data definition, data management, and data access.<br />

9. Super-tenant SQL access to LOB data<br />

Starting with <strong>OpenEdge</strong> <strong>11</strong>.1, the super-tenant is able to access<br />

tenant LOB data.<br />

PRODUCTIVITY<br />

<strong>OpenEdge</strong> <strong>11</strong> continues to focus on improving productivity so you<br />

can spend more time working in ways that will add value to your business.<br />

From <strong>Progress</strong> Developer Studio for <strong>OpenEdge</strong> and ABL to the DataServers<br />

5


and user interface, critical productivity enhancements have been made to<br />

help you keep up with rapidly changing customer and business demands.<br />

<strong>OpenEdge</strong> <strong>11</strong> is more flexible than ever, offering support for new platforms<br />

and programming models, and providing new development options. In direct<br />

response to customer requests, changes have been made to improve the<br />

usability of the system, the ability to troubleshoot, and the ability to manage<br />

and extend your .Net interface. And <strong>OpenEdge</strong> <strong>11</strong> provides even greater<br />

support for SaaS and Cloud application development with increased user<br />

interface flexibility that delivers a dynamic web experience that is rich,<br />

engaging, and interactive.<br />

PROGRESS DEVELOPER STUDIO FOR OPENEDGE (FORMERLY<br />

KNOWN AS OPENEDGE ARCHITECT)<br />

1. Usability enhancements<br />

www.progress.com<br />

<strong>OpenEdge</strong> <strong>11</strong> includes several usability enhancements to Developer<br />

Studio for <strong>OpenEdge</strong> based upon customer requests and research into<br />

customer issues. Included are improvements to the ProBindingSource<br />

designer, the handling of preprocessors, and the Build and Compile functions.<br />

2. Support for WebSpeed programming models<br />

The evolution of Developer Studio for <strong>OpenEdge</strong> as a comprehensive<br />

development environment for <strong>OpenEdge</strong> applications continues with the<br />

addition of support for WebSpeed programming models; included are CGI<br />

Wrappers and Embedded SpeedScript.<br />

3. Remote server development for AppServer and WebSpeed<br />

One of the hallmarks of the <strong>OpenEdge</strong> platform is how it facilitates<br />

multi-tiered application design and development. In <strong>OpenEdge</strong> <strong>11</strong>, Developer<br />

Studio for <strong>OpenEdge</strong> adds support for building AppServer and WebSpeed<br />

application components. Debugger support for AppServer and WebSpeed<br />

is included.<br />

4. Remote Debugger and other Debugger enhancements<br />

<strong>OpenEdge</strong> <strong>11</strong> allows the Debugger to connect to an already-running<br />

AVM (local or remote) and debug the executable with full capabilities. In<br />

addition, the Debugger has been enhanced to support breakpoints in “include”<br />

6


files, the ability to step into code on a remote AVM from a local debug<br />

session, and the ability to debug without the need for debug listing files.<br />

Security of a debug session over a remote connection has also improved.<br />

*New <strong>Progress</strong> Developer Studio for <strong>OpenEdge</strong> functionality for<br />

<strong>OpenEdge</strong> <strong>11</strong>.1 includes:<br />

5. Debug listing support<br />

www.progress.com<br />

Beginning in <strong>OpenEdge</strong> <strong>11</strong>.1, while debugging an application it will be<br />

possible to go directly to the source code line number rather than the debug<br />

listing line number given by the Debugger.<br />

6. Ability to open files from the commend line or by double-clicking<br />

With <strong>OpenEdge</strong> <strong>11</strong>.1 application developers can open a file within<br />

<strong>Progress</strong> Developer Studio from the command line or by double-clicking on the<br />

ABL file.<br />

7. Certification of Eclipse 3.7.1.<br />

8. Update DB Navigator’s JDBC drivers to Version 5.0 DataDirect<br />

JDBC drivers<br />

*New <strong>Progress</strong> Developer Studio for <strong>OpenEdge</strong> functionality for<br />

<strong>OpenEdge</strong> <strong>11</strong>.2 includes:<br />

9. ABL Scratch Editor.<br />

The new Scratch Editor in <strong>Progress</strong> Developer Studio provides<br />

the ability to write and execute ABL code without having to save it as a<br />

project. Features in the Scratch Editor include content assist, color-coding,<br />

and syntax-checking.<br />

7


10. AppBuilder Integration.<br />

www.progress.com<br />

<strong>OpenEdge</strong> <strong>11</strong>.2 provides improved integration of <strong>Progress</strong> Developr<br />

Studio and the AppBuilder by significantly improving usability and providing<br />

more screen real estate to ABL developers wanting to develop and maintain<br />

ABL-based applications. Included is integration of the AppBuilder design<br />

window and tools along with enhancements to <strong>Progress</strong> Developer Studio’s<br />

text editor which make it easier to work with AppBuilder-generated code.<br />

Now it’s easier than ever to build and maintain ABL-based applications in the<br />

Eclipse environment.<br />

ABL (ADVANCED BUSINESS LANGUAGE)<br />

1. Unified r-code for portability between 32-bit and 64-bit systems<br />

<strong>OpenEdge</strong> <strong>11</strong> features complete r-code compatibility between 32-bit<br />

and 64-bit platforms, providing for more efficient development<br />

and deployment.<br />

8


2. Object-oriented language extensions (interface inheritance and<br />

dynamic properties)<br />

www.progress.com<br />

Interface Inheritance allows a developer to create class interfaces<br />

that inherit from existing interfaces. <strong>OpenEdge</strong> <strong>11</strong> also introduces the ability<br />

of OOABL interfaces to extend .NET interfaces. Dynamic Properties allow a<br />

developer to set and get an ABL class property dynamically.<br />

3. Improved ProDataSet to XML support<br />

With <strong>OpenEdge</strong> <strong>11</strong>, additional XML documents that conform to the<br />

structure of a ProDataSet can be read into a ProDataSet.<br />

4. Logging of temp-table information<br />

The <strong>OpenEdge</strong> Logging Infrastructure has been enhanced so that<br />

application developers can trace the creation and deletion of temp-tables<br />

in their applications. This logging capability strengthens the ability to<br />

troubleshoot applications that utilize temp-tables and ProDataSets as their<br />

primary data structures.<br />

5. Virtual System Tables for temp-tables<br />

This ABL enhancement allows clients to gather information about the<br />

temp-tables used by the application via Virtual System Tables (VSTs). These<br />

tables give the application access to database activity and status information,<br />

enabling an application to understand, debug, and tune the use of temp-tables<br />

within their application at runtime.<br />

6. Improved support for large objects<br />

<strong>OpenEdge</strong> <strong>11</strong> removes several large-object restrictions that have<br />

existed in previous releases. The BUFFER object’s SAVE-ROW-CHANGES( )<br />

and BUFFER-COMPARE( ) methods, and the BUFFER-COMPARE statement,<br />

now allow CLOB fields to be compared. Additionally, when used on records<br />

that contain LOB fields, the CURRENT-CHANGED( ) function now can detect<br />

when a LOB field has been altered. The ABL also supports the comparing of<br />

LOB fields. One benefit of this change is that programs using GUI for .NET may<br />

now include LOBs in updateable grids.<br />

9


7. ProBindingSource improvements<br />

www.progress.com<br />

Prior to <strong>OpenEdge</strong> <strong>11</strong>, for a grid control that supports a hierarchy of<br />

tables (thereby allowing you to bind to a ProDataSet), you had to rely upon<br />

the grid to do any sorting of the child tables. In <strong>OpenEdge</strong> <strong>11</strong> the application<br />

can now change the Data-Relation’s WHERE-STRING attribute if the<br />

corresponding ProDataSet is bound to a .NET BindingSource.<br />

8. Allow input- blocking statements anywhere<br />

<strong>OpenEdge</strong> <strong>11</strong> removes all restrictions on where an input-blocking<br />

statement can occur, providing more flexibility when using user-defined<br />

functions, OOABL non-void methods, and elsewhere.<br />

9. ABL performance enhancements<br />

Analyzing and improving the performance of ABL is an ongoing task<br />

for <strong>OpenEdge</strong>. In <strong>OpenEdge</strong> <strong>11</strong> some of the key performance benefits include<br />

faster deletion of tables in Type II storage, as well as others. For example, in<br />

<strong>OpenEdge</strong> <strong>11</strong>, the AVM delays the instantiation of temp-tables, ProDataSets<br />

and their associated indexes until the object is used in the program. This<br />

change improves procedure-and class-instantiation performance. Additionally,<br />

ABL “FOR EACH” blocks include a new TABLE-SCAN option, which improves<br />

performance when a program is reading all of the records stored in a Type II<br />

storage area.<br />

*New ABL functionality for <strong>OpenEdge</strong> <strong>11</strong>.1 includes:<br />

10. Encoded password support<br />

A frequent regulatory requirement, in <strong>OpenEdge</strong> <strong>11</strong>.1 administrators<br />

are provided with a single means of creating, storing, and using encoded<br />

passwords in an <strong>OpenEdge</strong> application.<br />

<strong>11</strong>. LIKE phrase for method and function parameters<br />

Beginning with <strong>OpenEdge</strong> <strong>11</strong>.1, the LIKE phrase is supported in<br />

Method and Function parameter syntax.<br />

10


*New ABL functionality for <strong>OpenEdge</strong> <strong>11</strong>.2 includes:<br />

12. Session-level support for Structured Error Handling.<br />

www.progress.com<br />

Prior to <strong>OpenEdge</strong> <strong>11</strong>.2, Structured Error Handling worked only at the<br />

routine level (procedures, functions, methods, and “ON” triggers). <strong>OpenEdge</strong><br />

<strong>11</strong>.2 introduces a new statement and new startup parameter that allow an<br />

ABL programmer to utilize the UNDO/THROW ERROR directive within all<br />

blocks in a source file.<br />

13. Sub-second capability for the PAUSE statement.<br />

Previously, the PAUSE statement had a minimum value of one<br />

second. In <strong>OpenEdge</strong> <strong>11</strong>.2 the PAUSE statement can now be use with<br />

sub-second timing.<br />

14. “DefaultScrolling” startup option.<br />

A new -defaultscrolling startup option causes DEFINE QUERY<br />

statements to default to SCROLLING, guaranteeing the possibility of<br />

pre-fetching when resolving an ABL query over a network.<br />

15. Offset and fetch for SQL query result sets.<br />

When processing the result set from a SQL query, instead of having<br />

to load the entire result set to process it, <strong>OpenEdge</strong> <strong>11</strong>.2 allows an application<br />

query to define an offset within the result set and fetch a limited number of<br />

rows at the offset. This direct access to only a piece of the result set can lead<br />

to faster query execution and may better suit the needs of applications where<br />

an entire result set is unnecessary.<br />

DATASERVER<br />

1. MS SQL Server DataServer CLOB support<br />

<strong>OpenEdge</strong> <strong>11</strong> adds support for the <strong>OpenEdge</strong> CLOB datatype to the<br />

DataServer for MS SQL Server, allowing a CLOB field in <strong>OpenEdge</strong> to be<br />

migrated and pulled against MS SQL Server.<br />

*New DataServer functionality for <strong>OpenEdge</strong> <strong>11</strong>.1 includes:<br />

2. Update to Version 7.0 of <strong>Progress</strong> DataDirect Connect and<br />

Connect64 for ODBC drivers<br />

<strong>OpenEdge</strong> <strong>11</strong>.1 embeds <strong>Progress</strong> DataDirect’s 32-bit and 64-bit<br />

Version 7.0 drivers for ODBC DataServers.<br />

<strong>11</strong>


USER INTERFACE<br />

1. Improvements to ProBindingSource at design time and support for<br />

recursive relations<br />

www.progress.com<br />

Usability issues with ProBindingSource are addressed in <strong>OpenEdge</strong><br />

<strong>11</strong>, including the removal of multiple modal dialogs for schema selection.<br />

ProBindingSource also can now define recursive relationships amongst tables,<br />

which was previously possible only by coding the ABL directly.<br />

2. JSON Parser<br />

<strong>OpenEdge</strong> <strong>11</strong> introduces a package of built-in ABL objects to<br />

represent JSON. These objects can be created by parsing JSON, and JSON<br />

can be created by serializing these objects. This will allow applications to<br />

work directly with JSON using ABL rather than having to parse the DOM<br />

structure themselves, a capability that particularly benefits programs that<br />

take advantage of AJAX and Web UI programming.<br />

3. .NET Open Client changes<br />

The .NET Open Client adds an additional way of supporting NULL<br />

data values by supporting nullable value types, which are essentially<br />

structures that can represent the normal range of values for its underlying<br />

type, plus an additional null value.<br />

DIAGNOSTICS<br />

*New Diagnistics functionality for <strong>OpenEdge</strong> <strong>11</strong>.2 includes:<br />

1. PROVERSION enhancement.<br />

The PROVERSION statement can now report Service Pack, patch<br />

level, and build number information in addition to the main version of the<br />

installed product.<br />

2. ProInventory included with the <strong>OpenEdge</strong> product distribution.<br />

Beginning with <strong>OpenEdge</strong> <strong>11</strong>.2, installations of <strong>OpenEdge</strong> will<br />

automatically include the ProInventory diagnostic utility. ProInventory is<br />

often used by <strong>Progress</strong> Customer Support to obtain comprehensive system<br />

information from customers.<br />

12


PLATFORM SUPPORT<br />

64-bit SQL drivers for Linux<br />

www.progress.com<br />

Integrating 64-bit SQL drivers for 64-bit Linux platforms completes<br />

the work to provide 32-bit SQL drivers for 32-bit platforms and 64-bit SQL<br />

drivers for 64-bit platforms, across the board.<br />

*New Platform support for <strong>OpenEdge</strong> <strong>11</strong>.2 includes:<br />

<strong>OpenEdge</strong> <strong>11</strong>.2 introduces support for Eclipse 3.7. It is also certified<br />

for Microsoft Windows 8 and Microsoft Windows Server 2012.<br />

OPERATIONAL EXCELLENCE<br />

<strong>OpenEdge</strong> <strong>11</strong> continues to focus on supporting the development of<br />

high-performance and ultra-reliable applications to support the needs of<br />

24x7 business operations with ever-increasing numbers of users. Across the<br />

board—the AppServer, the database, the DataServers, and more—critical<br />

performance enhancements have been made to ensure that your application<br />

matches aggressive business demands. Diagnostic and monitoring tools have<br />

been improved and enhanced to provide a more proactive environment for<br />

troubleshooting issues. Additionally, special considerations have been made<br />

to facilitate deployments to the Cloud where performance and reliability<br />

are paramount.<br />

APPSERVER<br />

1. Improved AppServer error handling<br />

Improvements to AppServer error handling provide better information<br />

regarding the type of error that has resulted and where it has occurred.<br />

Included is better handling of the error condition when an AppServer<br />

connection has been refused as well as the error when there are no ports<br />

available to allocate to an agent.<br />

2. Diagnostics to determine which AppServer code is running<br />

Further improvements to AppServer diagnostics include the ability to<br />

determine which specific r-code is running, allowing verification of whether<br />

the agent is actually hung or is just running for a very long time.<br />

13


3. Network compression for state-free AppServer mode, Java<br />

OpenClient, and .NET OpenClient<br />

Message compression improves application performance on a<br />

network. In <strong>OpenEdge</strong> <strong>11</strong>, AppServer messages are compressed when<br />

operating in state-free mode and communicating with any client. This<br />

completes compression work for all modes of the AppServer. In addition,<br />

the Java and .NET OpenClient include compression as well.<br />

*New AppServer functionality for <strong>OpenEdge</strong> <strong>11</strong>.1 includes:<br />

4. TCP Keepalive properties for the .NET OpenClient<br />

In <strong>OpenEdge</strong> <strong>11</strong>.1 the .NET OpenClient supports runtime properties<br />

that allow direct control of the TCP socket’s Keepalive messages, allowing<br />

applications to adapt to the needs of the network that the application is<br />

operating within.<br />

*New AppServer functionality for <strong>OpenEdge</strong> <strong>11</strong>.2 includes:<br />

5. REST Adapter<br />

The <strong>OpenEdge</strong> <strong>11</strong>.2 REST Adapter leverages the power of XML to give<br />

your application the ability to integrate with any other application, written in<br />

any language and on any platform. This provides access to the AppServer by<br />

any client built outside of <strong>OpenEdge</strong> and opens up your application to a world<br />

of unlimited connectivity, to any app on any platform.<br />

6. Improved AppServer Performance<br />

<strong>OpenEdge</strong> <strong>11</strong>.2 improves AppServer performance for single-run<br />

and singleton persistent procedures. Operations that previously required<br />

multiple round trips from the client to the AppServer are now accomplished<br />

with just one round trip.Single-run procedures apply to the frequent case<br />

where an application needs to run a persistent procedure just one time. The<br />

Single Run combines the three separate calls for Create, Run, and Delete<br />

of the procedure into a single call that executes them all together, resulting<br />

in just one round-trip where previously three were necessary. For Singleton<br />

procedures, the persistent procedure is instantiated only if it is not already<br />

running from a previous invocation, and remains instantiated after each run.<br />

www.progress.com<br />

14


OPENEDGE MANAGEMENT<br />

Support for remote jobs<br />

Administrators can now use <strong>OpenEdge</strong> Management as a central<br />

console to manage jobs on remote systems in addition to the local system.<br />

The ability to manage scripts that reside on remote machines is also included.<br />

DATASERVER<br />

MS SQL Server DataServer dynamic query join optimization<br />

When using a large array of table join conditions with MS SQL Server<br />

DataServer, <strong>OpenEdge</strong> <strong>11</strong> shows performance improvements by reducing the<br />

number of round trips to the foreign database server and/or by pushing as<br />

much of the processing as possible to the MS SQL Server database.<br />

DATABASE<br />

*New Database functionality for <strong>OpenEdge</strong> <strong>11</strong>.1 includes:<br />

1. Improved performance of Index Rebuild<br />

The performance of index rebuild operations is significantly enhanced<br />

in <strong>OpenEdge</strong> <strong>11</strong>.1 with the addition of new parameters to use when starting<br />

an idxbuild. While the exact benefits will depend on the particular database<br />

and index configuration, DBAs can expect performance improvements of three<br />

times faster, or even more.<br />

2. New startup parameters to tune network performance<br />

In <strong>OpenEdge</strong> <strong>11</strong>.1, five new startup parameters have been introduced<br />

that can be used to tune network performance when using prefetch queries.<br />

Especially beneficial to large databases, the new parameters affect when and<br />

how data is sent across the network when executing a prefetch query.<br />

3. New startup parameters to reduce contention when updating the<br />

LRU (least recently used) chain<br />

This enhancement to <strong>OpenEdge</strong> <strong>11</strong>.1 provides a way to set a skip<br />

value that governs the number of times that a buffer will be accessed before<br />

it is moved to the end of the LRU chain. When this LRU skip value is set<br />

properly it reduces contention on the LRU latch, improving concurrency<br />

and performance.<br />

www.progress.com<br />

15


*New Database functionality for <strong>OpenEdge</strong> <strong>11</strong>.2 includes:<br />

4. Support for enabling JTA (Java Transaction API) along with<br />

<strong>OpenEdge</strong> Replication<br />

With <strong>OpenEdge</strong> <strong>11</strong>.2 you are able to incorporate disaster recovery<br />

into your distributed transaction solution by running <strong>OpenEdge</strong> Replication and<br />

JTA at the same time on the same database.<br />

INTEGRATION AND WORKFLOW<br />

To remain competitive, it is vital companies have the agility to meet<br />

ever-changing customer and market demands. This level of agility requires<br />

flexible business applications—both in terms of process and integration.<br />

The days of making code changes every time a business process is defined<br />

or refined, or whenever a customer has unique requirements, are gone.<br />

Companies need the ability to support the fast pace of business by quickly<br />

and efficiently incorporating those new processes and capabilities into their<br />

new and existing applications. And those applications need to be adaptable<br />

enough to integrate easily with other applications—now and in the future.<br />

<strong>OpenEdge</strong> <strong>11</strong> delivers additional integration flexibility as well as<br />

Business Process Management (BPM)—a new feature set integrated into<br />

the <strong>OpenEdge</strong> development environment. <strong>Progress</strong> customers and partners<br />

now have a simple way to modernize existing applications with <strong>OpenEdge</strong><br />

BPM in addition to building new and add-on business process applications.<br />

With BPM, <strong>OpenEdge</strong> developers can add process workflow into their<br />

<strong>OpenEdge</strong> applications in a natural and intuitive manner—while also reducing<br />

development costs and delivering greater business value to their customers.<br />

INTEGRATION<br />

Sonic 8.0 support for Sonic adapter<br />

from Sonic.<br />

www.progress.com<br />

The Sonic adapter for <strong>OpenEdge</strong> supports the Version 8.0 release<br />

16


WORKFLOW<br />

<strong>OpenEdge</strong> BPM<br />

From the eclipse-based <strong>Progress</strong> Developer Studio for <strong>OpenEdge</strong><br />

development environment, developers can:<br />

> Define how process steps execute <strong>OpenEdge</strong> business logic via the<br />

<strong>OpenEdge</strong> Application Server through a purposed managed adapter,<br />

and an intuitive “drag and drop” of ABL procedure code onto the<br />

workflow design canvas<br />

> Pass native <strong>OpenEdge</strong> data types from process step to process step<br />

through an enhanced dataslot capability<br />

> Have access to a new set of process-related ABL APIs to carry<br />

out a variety of standard BPM functions, such as obtain the task<br />

information for a user to display in the application User Interface,<br />

inform the BPM processing engine that a process step is now<br />

completed, and so on<br />

> Simplify the use of existing WebSpeed Forms in business<br />

process flows<br />

*New <strong>OpenEdge</strong> BPM functionality for <strong>OpenEdge</strong> <strong>11</strong>.1 includes:<br />

1. Character extent support in the ABL API<br />

In <strong>OpenEdge</strong> <strong>11</strong>.1, it is possible to set and retrieve a List dataslot<br />

value using an ABL <strong>Progress</strong>.BPM.DataSlot or DataSlotTemplate.<br />

2. Get*Tasks method to support advanced filtering<br />

Beginning with <strong>OpenEdge</strong> <strong>11</strong>.1, a new method is available in the<br />

UserSession object to support advanced filtering of the Task objects that<br />

are obtained.<br />

SECURITY & COMPLIANCE<br />

<strong>OpenEdge</strong> <strong>11</strong> reinforces our commitment to our customers’ needs<br />

for security, privacy and compliance. In this era of increased regulatory<br />

requirements, data must be secure and private in order to protect intellectual<br />

property, maximize business success, and prevent liability. The stakes are<br />

even higher in a SaaS or Cloud environment, where security and compliance<br />

www.progress.com<br />

17


are vital for customer trust and market success. Customers adopting SaaS-<br />

and Cloud-based applications expect the same assurances of data security<br />

and compliance that they have long expected from applications that run<br />

on-premises in their own data centers. <strong>OpenEdge</strong> <strong>11</strong> includes enhancements<br />

that improve and simplify identity management. And essential updates and<br />

support for new encryption methods significantly improve performance and<br />

ensure you keep pace with current industry regulations.<br />

SECURITY<br />

1. Improved identity management<br />

management:<br />

<strong>OpenEdge</strong> <strong>11</strong> introduces the following improvements to identity<br />

> A simplified process for creating and using user credentials for both<br />

client-server and Application Server <strong>OpenEdge</strong> applications<br />

> A single programming model for configuring any combination of<br />

runtime security features at production time, requiring few, if any,<br />

changes to the application code<br />

> Support for multiple tenants with one or more domains per tenant.<br />

> Support for the configuration per-tenant of user authentication<br />

methods that meet the tenant’s specific security requirements<br />

> A simplified way for using SQL Server together with ABL in the<br />

same <strong>OpenEdge</strong> application without having to rely on the security<br />

standards of the _user table accounts<br />

2. RC4 for ENCRYPT( ) and DECRYPT( )<br />

Supporting RC4 encryption for the ENCRYPT( ) and DECRYPT( )<br />

functions significantly enhances the performance of these functions.<br />

3. SHA-256 and SHA-512<br />

An upgrade to SHA-256 and SHA-512 hashing algorithms is essential<br />

to keep current with recommendations by security organizations, standards<br />

councils, and government authorities.<br />

www.progress.com<br />

18


4. More SSL certificate support<br />

Upgrading to version 5.1.0.1 allows <strong>OpenEdge</strong> to take advantage of<br />

AES data encryption ciphers and x509 version 3 extensions support available<br />

in the newer release.<br />

*New security functionality for <strong>OpenEdge</strong> <strong>11</strong>.1 includes:<br />

5. ABL-based username/password authentication with<br />

Client-Principal<br />

This <strong>OpenEdge</strong> <strong>11</strong>.1 feature aids user authentication by allowing<br />

application developers to use a single code path regardless of how and where<br />

the physical authentication actually takes place. <strong>OpenEdge</strong> Management<br />

support for this capability is also included.<br />

PERSONALIZATION<br />

Improved personalization options within <strong>OpenEdge</strong> <strong>11</strong> increase<br />

the productivity associated with installing, uninstalling and upgrading your<br />

<strong>OpenEdge</strong> application. Users can take advantage of new personalizatiion<br />

options for simplifying and accelerating the install process as well as<br />

automating the upgrade process.<br />

1. Install “Finish” button<br />

To streamline the installation process, a new option has been<br />

provided on each dialog that allows the user to finish the data collection<br />

phase of an installation. The user will still be able to navigate through each<br />

dialog if desired, but they will be brought directly to the summary screen<br />

when they choose to finish data collection. The summary screen will display<br />

all of the user’s selections and for all skipped dialogs the default values will<br />

be used.<br />

2. Option to uninstall WebClient<br />

When installing the WebClient, the install program now determines<br />

whether previous installations of WebClient already exist and provides a list<br />

to the user so that any or all may be uninstalled. The uninstall will complete<br />

prior to beginning the new install.<br />

www.progress.com<br />

19


3. Option to suppress WebClient dialog-box when upgrading<br />

This feature provides an optional override of the dialog-box presented<br />

to the user by the WebClient when it detects that an application has changed<br />

and needs to be upgraded. User confirmation of the upgrade is bypassed and<br />

the upgrade begins automatically.<br />

USER INTERFACE FLEXIBILITY<br />

Today, the market demand is high for web applications that have<br />

many of the qualities and characteristics of desktop applications but are<br />

delivered over the web. <strong>OpenEdge</strong> <strong>11</strong> now offers greater user interface<br />

flexibility with support for Enhanced Rich Internet Applications (RIAs).<br />

RIAs combine the flexibility, responsiveness, and ease of use of desktop<br />

applications with the broad reach of the web. RIAs provide a dynamic web<br />

experience that is rich and engaging, as well as interactive. RIA technologies<br />

provide a variety of development, deployment, and runtime options for SaaS-<br />

based applications. Due to the flexibility of the platform, <strong>OpenEdge</strong> already<br />

supports many different RIA technologies. Since no RIA technology has taken<br />

the lead, <strong>OpenEdge</strong> <strong>11</strong> will provide support for many additional options,<br />

more specifically: JSON parser support in the ABL, updated Infragistics<br />

controls (GUI for .NET), and architect support for custom project types (Ajax/<br />

WebSpeed).<br />

USER INTERFACE<br />

1. Updated Infragistics controls<br />

<strong>OpenEdge</strong> <strong>11</strong> includes an update to the current release of the<br />

Infragistics Net Advantage WinForm Controls, providing enhanced<br />

functionality as well as bug fixes.<br />

2. Allow the use of .NET objects for non-GUI<br />

In <strong>OpenEdge</strong> <strong>11</strong>, .NET objects that are not related to UI can now be<br />

used. Also, ABL access to .NET objects is now allowed in non-user-interface<br />

executables. This means that AppServer agents, WebSpeed agents, batch<br />

jobs, and the character client can now work with .NET objects.<br />

www.progress.com<br />

20


PROGRESS SOFTWARE<br />

<strong>Progress</strong> <strong>Software</strong> Corporation (NASDAQ: PRGS) is a global software company that simplifies the development, deployment<br />

and management of business applications on-premise or on any Cloud, on any platform and on any device with minimal IT<br />

complexity and low total cost of ownership.<br />

WORLDWIDE HEADQUARTERS<br />

<strong>Progress</strong> <strong>Software</strong> Corporation, 14 Oak Park, Bedford, MA 01730 USA Tel: +1 781 280-4000 Fax: +1 781 280-4095 On the Web at: www.progress.com<br />

Find us on facebook.com/progresssw twitter.com/progresssw youtube.com/progresssw<br />

For regional international office locations and contact information, please go to www.progress.com/worldwide<br />

<strong>Progress</strong> and <strong>OpenEdge</strong> are trademarks or registered trademarks of <strong>Progress</strong> <strong>Software</strong> Corporation or one of its affiliates or subsidiaries in the U.S. and other countries. Any other marks<br />

contained herein may be trademarks of their respective owners. Specifications subject to change without notice. © 2013 <strong>Progress</strong> <strong>Software</strong> Corporation and/or its subsidiaries or affiliates.<br />

All rights reserved.<br />

Rev. 01/13 | 130121-0091<br />

www.progress.com

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!