Your Presenters: Your Presenters Steven Dunn – Sales and Marketing Manager, Europe Dave Fish – Engineering Evangelist John Strano – PowerBuilder Evangelist


PowerBuilder Market Focus and Road Map : PowerBuilder Market Focus and Road Map 15


Market Focus – Sybase Goals : Market Focus – Sybase Goals Attract next generation application developers Focus on .NET and Eclipse platforms to extend reach Support Sybase servers – key to Sybase platform success Provide key technology differentiators within an open 4GL IDE Use DataWindow technology as cornerstone of Sybase offerings


Market Focus – The PowerBuilder Products: Market Focus – The PowerBuilder Products PowerBuilder 4GL development Provide key unique technology to differentiate ourselves on .NET platform PowerBuilder App Server Plug-in The newest member of the PowerBuilder family Deploy PowerBuilder code to J2EE application servers PocketBuilder PowerBuilder for mobile devices Build data-driven mobile applications in less than one hour DataWindow .NET A Visual Studio Plug-in, bringing 4GL productivity to Visual Studio .NET


DataWindows Everywhere…: DataWindows Everywhere… PowerBuilder for Client/Server, Web, Web Services and now .NET Deployment PowerBuilder VM Application Server Plug-In WebLogic, WebSphere, JBoss(, Oracle, Geronimo…) DataWindow .NET PocketBuilder DataWindows greatly reduce the amount of code you need to write for your application. DataWindows provide an intuitive graphical user interface allowing developers to be immediately productive.


Messaging: Messaging We are committed to PowerBuilder PB 10.5 release delivers core functionality enhancements Major new features – DW presentation style, updated UI We are committed to fully supporting, embracing, and exploiting .NET PB 11 deploys .NET apps to web, Smart Client support, WinForm support Positions customers to leverage Vista & WPF functionality DataWindow .NET, PocketBuilder .NET


PowerBuilder Family Promotion:Valid until 30th June 2007: PowerBuilder Family Promotion: Valid until 30th June 2007 Buy either 1 copy of PowerBuilder Enterprise or 2 update licenses and you can also have one copy of: PocketBuilder Single CPU copy of the PowerBuilder Application Server Plug-In DataWindow .NET For more details contact the PowerBuilder Sales Team or send an email to: EuropePB@sybase.com


PowerBuilder Roadmap Simplified development for today, tomorrow: PowerBuilder Roadmap Simplified development for today, tomorrow .NET Simplified Additional Functionality Powerful Data Access with Sophisticated Presentation Applications deployed as .NET NVOs deployed as .NET assemblies and Web Services Leverage and extend investment UI updates MSS SNC support Updated Informix support Vista support Smart Client for Win32 Pipeline object EAS .NET support Incremental rebuild for .NET Callbacks (to reduce postbacks) .NET in IDE, support for visual controls Visually exciting apps based on WPF WPF controls in design time, runtime Managed code Inherit from other assemblies 2008 PowerBuilder 12 Language Independence Application Connectivity Multiple Platform Support Power And Performance 2007 PowerBuilder 11.1 2007 PowerBuilder 11.0


PowerBuilder 11 Features : PowerBuilder 11 Features 15


PowerBuilder 11 Release Defining Features: PowerBuilder 11 Release Defining Features IDE and User Interface Enhancements DataWindow enhancements Updated database connectivity .NET Deployment .NET Web Forms applications in ASP .NET 2.0 .NET Windows Forms and Smart Client applications .NET Web Services .NET Assemblies


IDE/User Interface Enhancements : IDE/User Interface Enhancements 10


IDE Enhancements: IDE Enhancements Autoscript Enhancements Resizable Dialog Boxes Updated Menus and Toolbars System Tree Enhancements Project Painter Enhancements Output window tabs Breaking into debugger


IDE/User Interface Enhancements Demonstration : IDE/User Interface Enhancements Demonstration


DataWindow Enhancements : DataWindow Enhancements 10


DataWindow Enhancements: DataWindow Enhancements Web Services supported as a data source Treeview DataWindow Enhancements Retain Retrieval Argument Values in the DataWindow Painter Use Ellipses


Web Services Data Source for DataWindows: Web Services Data Source for DataWindows This is intended to support database (RDBMS) data delivered via Web Services Access to RDBMS data without needing the vendors client software Not all Web Services are suitable for the DataWindow Complex return data such as nested structures Amazon.com returns some fairly complex return values The return value from the Web Service needs to look like a result set


Define a Web Service Retrieval: Define a Web Service Retrieval DataWindow Painter PowerBuilder Web Service support using the .NET engine Metadata WSDL A DataWindow Object A generated Assembly


Run time Web Service Retrieval : Run time Web Service Retrieval Retrieve works just like it does now, you can specify retrieval arguments as parameters. wsconnection object (optional) Allows runtime overrides of Endpoint Userid and password Timeout Security and proxy overrides Port override And more….(continued)…


Run time Web Service Retrieval: Run time Web Service Retrieval The Web Service The DataWindow engine PowerBuilder Web Service support using the .NET engine Generated assembly and the .NET framework Retrieval method call Returned data Metadata


New TreeView DataWindow Features: New TreeView DataWindow Features TreeView Style DataWindow can now be used in a Web DataWindow control Removed the height limit from the detail band Tree nodes can be hidden with a height of 0 Moving rows in a TreeView will retain their collapsed/expanded state


Retrieval Arguments Retained: Retrieval Arguments Retained Retrieval arguments can be remembered in the DataWindow object


Use Ellipses: Use Ellipses


DataWindow Enhancements Demonstration : DataWindow Enhancements Demonstration


Database Connectivity Enhancements : Database Connectivity Enhancements 5


DataBase Connectivity Enhancements: DataBase Connectivity Enhancements ASE 15 New MS SQL Server Native Driver Oracle RAC support Enhanced MobilLink Support


Slide26: ASE 15 A new database interface has been added to support Adaptive Server® Enterprise 15 and later releases This interface is identical to the existing SYC interface, except that: It currently supports only Adaptive Server 15 (the Release database parameter can only be set to 15) It supports large identifiers with up to 128 characters. This support is not available in the SYC interface To use this interface, the Adaptive Server 15 client must be installed on the client computer (The ASE interface is also available in PowerBuilder 10.5.1)


Slide27: New Microsoft SQL Server Native Driver The new interface uses the SQL Server 2005 native client (sqlncli.h and sqlncli.dll) on the client side and connects using OLE DB The PBODB initialization file not used Connections made directly through OLE DB use the PBODB initialization file to set some parameters, but connections made using the SNC interface do not depend on the PBODB initialization file The SNC interface can be used to connect to SQL Server 2005 and SQL Server 2000 For SQL Server 2000, the SQL client SDK was provided with the Microsoft Database Access Components (MDAC) MDAC does not support new features in SQL Server 2005 To use the SNC interface, the SQL Server 2005 SQL Native Client and the .NET Framework 2.0 must be installed on the client computer


Slide28: Oracle RAC support This is a cluster database that uses a shared cache architecture A High Availability (HA) client connected to an RAC database can register a callback to indicate that it wants the server to notify it in case of a database failure event that affects a connection made by the client PowerBuilder developers can script a new event, DBNotification, that has been added to the Transaction object See the description of the DBNotification event and the HANotification database parameter in the online Help for more details


Slide29: Enhanced MobilLink Support MobiLink is a session-based synchronization system that allows two-way synchronization between a main database, called the consolidated database, and multiple remote databases The ASA MobiLink Synchronization wizard on the Database tab of the New dialog box creates objects that facilitate control of database synchronization from a PowerBuilder application


Slide30: Enhanced MobilLink Support In PowerBuilder 11, system objects have been added to enable MobiLink functionality to work with .NET applications Although the ASA MobiLink Synchronization wizard still generates objects that facilitate control of database synchronization from PowerBuilder applications, the main nonvisual object generated by the wizard is now an instance of the MLSync system object (that inherits from the MLSynchronization base class) The wizard no longer generates a global structure object for storage of synchronization parameters entered by the user, but the synchronization window that it generates uses the SyncParm system structure instead These differences apply even in targets that are not deployed to .NET platforms


PowerBuilder and .NET: PowerBuilder and .NET 5


PowerBuilder’s 4-Phase .NET Integration Initiative: PowerBuilder’s 4-Phase .NET Integration Initiative Phased approach Web Services (PB9) DataWindow .NET (PB10 Timeframe) .NET Deployment (PB11) .NET Resource Consumption (PB12)


PowerBuilder .NET Compiler Internals: PowerBuilder .NET Compiler Internals .NET Integration Compiler steps: Relies on redistributing .NET SDK’s C# compiler PBL Files PB2CS PowerBuilder .NET Compiler Framework PowerBuilder System Library for .NET C# Code WinForm / ASP.NET Application Generates Compiles Depends On References


Deploying Applications as .NET WebForms Applications in ASP .NET 2.0: Deploying Applications as .NET WebForms Applications in ASP .NET 2.0 20


Architecture:.NET Web Forms Applications: Architecture: .NET Web Forms Applications PBSHR.DLL DB Drivers DataWindow .NET WebForm Control PB Web Forms Application PB System Library for .NET PB Application Compiles to PBDWN.DLL PB Runtime DLLs (without PBVM)


What happens at deployment-time: What happens at deployment-time PowerScript code is compiled to a .NET assembly PBDs with DWO definitions are copied Resource files are copied Including PowerBuilder stock images ASP.NET files are generated Default.aspx: the main ASP.NET page Default.htm: hide menu and toolbars of IE


What PowerBuilder features can I use?: What PowerBuilder features can I use? Most PowerScript language features All data types Arrays Function invocation (dynamic, post, trigger) Event handling Embedded SQL Most Controls Exceptions: InkPicture, InkEdit, OleControl and OleCustomControl, Data Pipeline Drag and Drop is not supported in Web Forms applications File operations Sending Email DataWindow printing


PowerBuilder features not supported: PowerBuilder features not supported Some system classes such as: Profile-related classes Trace-related classes Some system functions such as: DDE-related functions Clipboard-related functions Some Controls, properties or events such as: OLE – Partially supported Drag & drop events EditLabels of TreeView


.NET WebForms Application Demonstration: .NET WebForms Application Demonstration


Deploying Applications as .NET Windows Forms Applications and Optionally as Smart Client Applications: Deploying Applications as .NET Windows Forms Applications and Optionally as Smart Client Applications 30


PowerBuilder .NET Windows Forms Application: PowerBuilder .NET Windows Forms Application Supports most features available in a PowerBuilder Win32 application PowerScript language features DataWindow, Editmask,RichText, InkEdit, InkPicture,… DataStore, Transaction, ResultSet,… Most System functions Consume .NET framework library through PowerBuilder’s .NET language interop. Preserve PowerBuilder development skills Create a PowerBuilder application Deploy it as a .NET Windows Forms application


Architecture:.NET WinForm Applications: Architecture: .NET WinForm Applications PBSHR.DLL DB Drivers DataWindow .NET WinForm Control PB Win Forms Application PB System Library for .NET PB Application Compiles to PBDWN.DLL PB Runtime DLLs (without PBVM) Application config Application manifest


PowerBuilder’s .NET Smart Client Support: PowerBuilder’s .NET Smart Client Support Solves the biggest headache of all… …Application Deployment The Best of the Rich Client World The Ubiquity of the Web


Comparison Between Rich/Thin/Smart Clients : Comparison Between Rich/Thin/Smart Clients


PowerBuilder’s.NET Smart Client Support: PowerBuilder’s .NET Smart Client Support .NET Smart Client Defined… Occasionally connected PowerBuilder with MobiLink Always up-to-date applications via Smart Updates PowerBuilder’s “Intelligent Updater” Maximize performance using client resources PowerBuilder deployed as WinForm (Rich Client) Communicate utilizing Web Services PowerBuilder’s Web Service DataWindow Utilize network resources PowerBuilder’s Web Service DataWindow PowerBuilder’s “Intelligent Updater” PowerBuilder with MobiLink


MobiLink Synchronization Overview: MobiLink Synchronization Overview MobiLink Synchronization Objective Create Smart Client offline enabled application MobiLink Synchronization is the most productive way to create offline enabled application. Feature Requirements Runtime ASA 9 or 10 DB drivers and MobiLink deployed. PB Win32 or PB .NET Windows Forms application. Design Time PowerBuilder 11.0 SQL Anywhere 9/10.


MobiLink Synchronization Architecture: MobiLink Synchronization Architecture


Intelligent Updater Overview: Intelligent Updater Overview “Intelligent Updater” is a new application deployment technology that makes deploying a Windows Forms based application as easy as deploying a Web application Based on “ClickOnce” technology of .NET Framework 2.0 “Intelligent Updater” is designed to address the pain of updating a typical Client/Server application


Deployment Model: Deployment Model Application installations and updates are deployed via centralized servers (via HTTP, FTP, UNC,…)


.NET Windows Forms/Smart Client Demonstration: .NET Windows Forms/Smart Client Demonstration


PowerBuilder 11 .NET Interoperability :Consuming .NET Resources: PowerBuilder 11 .NET Interoperability : Consuming .NET Resources 10


Slide52: .NET Interop The .NET Framework and other associated third-party managed libraries provide a very rich resource PowerBuilder users can use these libraries to extend the functionality of PowerBuilder .NET targets and save development time .NET language interoperability makes it possible to consume .NET classes and methods in PowerBuilder applications With .NET language interoperability, you can use PowerBuilder syntax to create .NET classes, call .NET methods, and access .NET properties You can make use of .NET collection classes, such as Hashtable and Set, and you can also make use of powerful .NET communication classes and other .NET services


.NET Interoperability (Consuming .NET Resources): .NET Interoperability (Consuming .NET Resources) All types in the CTS (Common Type System) may be consumed Classes, Interfaces conforming to CTS may be consumed IDE support in the PowerScript Painter Support for: Parameterized constructors, static properties, static methods Exception handling Propagates from .NET=>PowerBuilder=>.NET


PowerBuilder 11 .NET Interoperability Demonstration: PowerBuilder 11 .NET Interoperability Demonstration


Deploying PowerBuilder Nonvisual Objects (NVOs) as .NET Assemblies :Creating .NET Resources: Deploying PowerBuilder Nonvisual Objects (NVOs) as .NET Assemblies : Creating .NET Resources 10


Deploying NVOs as .NET Assemblies: Deploying NVOs as .NET Assemblies PowerBuilder NVOs can be deployed as .NET Assemblies A .NET Assembly Target Wizard is provided to facilitate this process Data types are automatically mapped between PowerScript and C#


The runtime:NVO .NET Assembly: The runtime: NVO .NET Assembly DataWindow .NET NVO .NET Assembly PBLs with NVOs PBSHR.DLL DB Drivers PB System Library for .NET PBDWN.DLL PB Runtime DLLs (without PBVM)


NVOs as .NET Assemblies Demonstration: NVOs as .NET Assemblies Demonstration


Deploying PowerBuilder Nonvisual Objects (NVOs) as .NET Web Services:Creating .NET Resources: Deploying PowerBuilder Nonvisual Objects (NVOs) as .NET Web Services: Creating .NET Resources 15


NVO  .NET Web Service: NVO  .NET Web Service What can be exposed as a Web Service? Custom Class User Objects (NVOs) Within each Web Service, what can be exposed as Messages? Public methods of NVOs with signatures that use supported data types can be valid Web Service “operations” Must be Stateless Be mindful of instance lifecycle


The runtime:NVO ASP.NET Web Services: The runtime: NVO ASP.NET Web Services Sybase.PowerBuilder.Core.DLL Sybase.PowerBuilder.Interop.DLL Sybase.PowerBuilder.Common.DLL Sybase.PowerBuilder.Web.DLL PBSHR.DLL DB Drivers DataWindow .NET NVO ASP.NET Web Service PB System Library for .NET PBLs with NVOs compiled PBDWN.DLL PB Runtime DLLs (without PBVM)


NVOs as .NET Web Services Demonstration: NVOs as .NET Web Services Demonstration


Future PowerBuilder Technology Showcase: Future PowerBuilder Technology Showcase 10


Windows Vista:Windows Presentation Foundation: Windows Vista: Windows Presentation Foundation High fidelity application experiences. Blends together UI, documents and media content. Ultra-rich UI and data visualization through XAML. Extensible Application Markup Language. Vector-based animation.


WPF DataWindow Demonstration: WPF DataWindow Demonstration


WPF DataWindow Demonstration: WPF DataWindow Demonstration


Slide67: Questions?


PowerBuilder Family Promotion:Valid until 30th June 2007: PowerBuilder Family Promotion: Valid until 30th June 2007 Buy either 1 copy of PowerBuilder Enterprise or 2 update licenses and you can also have one copy of: PocketBuilder Single CPU copy of the PowerBuilder Application Server Plug-In DataWindow .NET For more details contact the PowerBuilder Sales Team or send an email to: EuropePB@sybase.com


Slide69: Thank you!


Afternoon Walks-Through:PowerBuilder 11 .NET Deployment: Afternoon Walks-Through: PowerBuilder 11 .NET Deployment .NET Web Forms applications in ASP .NET 2.0 .NET Windows Forms and Smart Client applications .NET Web Services .NET Assemblies (Interop creation) .NET Interop (Consuming)