PowerBuilder 11.1 Overview - Sybase

Market Focus – The PowerBuilderProductsPowerBuilder• 4GL development for Windows, Web, and distributed applications• Provide key technology to simplify .NET developmentPowerBuilder Application Server Plug-in• Deploy PowerBuilder business objects (NVOs) to J2EE applicationservers• Expose business logic as EJBs or Web ServicesPocketBuilder• 4GL RAD for Windows Mobile devices• Quickly extend the reach of business applications to mobile usersDataWindow .NET• 4GL productivity in Visual Studio .NET• Attract Microsoft developers to Sybase technologySybase Symposium 2007 – November 15 - Brussels 3

DataWindows Everywhere…• PowerBuilder for Client/Server, Web, Web Services and now .NET• PowerBuilder Application Server Plug-In• WebLogic• WebSphere• JBoss• DataWindow .NET• PocketBuilderDataWindows greatly reduce the amount of code youneed to write for your applicationThe DataWindow Painter provides an intuitive graphicaluser interface granting you immediate productivitySybase Symposium 2007 – November 15 - Brussels 4

MessagingSybase is committed to PowerBuilder• PowerBuilder 11 delivers core functionality enhancements• Database driver enhancements• DataWindow enhancements• IDE and user enhancements• …and major new features• .NET deployment options• Web Services DataWindow• New SQL Server database driverSybase is committed to fully supporting andexploiting .NET• PowerBuilder 11 release• DataWindow .NET 2.5Sybase Symposium 2007 – November 15 - Brussels 5

PowerBuilder 11 Release DefiningFeaturesIDE and user interface enhancementsDataWindow enhancementsUpdated database connectivity.NET deployment capabilities• .NET Web Form applications in ASP .NET 2.0• .NET Windows Form and Smart Client applications• .NET Web Services• .NET AssembliesSybase Symposium 2007 – November 15 - Brussels 6

IDE EnhancementsAutoScriptResizable dialog boxesUpdated menus and toolbarsSystem treeProject painterOutput window tabsException support in debuggerWindow animation and transparencySybase Symposium 2007 – November 15 - Brussels 7

DataWindow EnhancementsDisplay ellipsis for truncated dataRetain DataWindow retrieval argument valuesWeb TreeView DataWindowWeb Service DataWindow data sourceSybase Symposium 2007 – November 15 - Brussels 8

Database Connectivity EnhancementsNew Sybase Adaptive Server Enterprise (ASE) 15native driverNew Microsoft SQL Server native driverOracle RAC supportSybase Symposium 2007 – November 15 - Brussels 9

PowerBuilder’s 4-Phase .NETIntegration InitiativeWeb Services (PB9)DataWindow .NET (PB10 Timeframe).NET Deployment (PB11).NET Resource Consumption (PB12)Sybase Symposium 2007 – November 15 - Brussels 10

Simplified development for today, tomorrow,and beyond2007v11.0.NET Simplified• Deploy applicationsand NVOs to .NET• UI and IDEEnhancements• DataWindowEnhancements• New and UpdatedDatabase DriversLanguageIndependenceApplicationConnectivityMultiplePlatformSupportPowerAndPerformanceSybase Symposium 2007 – November 15 - Brussels 11

Simplified development for today, tomorrow,and beyond2007v11.0.NET Simplified2007v11.1.NET Enhanced• Deploy applications • .NET incrementaland NVOs to .NET compiler• UI and IDE • DBMS DriverEnhancements Enhancements• DataWindow • r.a.d. Controls for WebEnhancements Forms• New and Updated • Enhanced Vista SupportDatabase DriversLanguageIndependenceApplicationConnectivityMultiplePlatformSupportPowerAndPerformanceSybase Symposium 2007 – November 15 - Brussels 12

Simplified development for today, tomorrow,and beyond2007v11.0.NET Simplified2007v11.1.NET Enhanced2008v11.2.NET Enhanced• Deploy applicationsand NVOs to .NET• UI and IDEEnhancements• DataWindowEnhancements• New and UpdatedDatabase Drivers• .NET incrementalcompiler• DBMS DriverEnhancements• r.a.d. Controls for WebForms• Enhanced Vista Support• AJAX Support for WebForms Applications• EAServer .NET ClientSupportLanguageIndependenceApplicationConnectivityMultiplePlatformSupportPowerAndPerformanceSybase Symposium 2007 – November 15 - Brussels 13

Simplified development for today, tomorrow,and beyond2007v11.02007v11.12008v11.22008v11.5.NET Simplified.NET Enhanced.NET EnhancedTW 2008• Deploy applicationsand NVOs to .NET• UI and IDEEnhancements• DataWindowEnhancements• New and UpdatedDatabase Drivers• .NET incrementalcompiler• DBMS DriverEnhancements• r.a.d. Controls for WebForms• Enhanced Vista Support• AJAX Support for WebForms Applications• EAServer .NET ClientSupport• Enhanced GraphDataWindows• ISUG Enhance.• Requests• Windows Forms• Web Form• DBMS DriverEnhancementsLanguageIndependenceApplicationConnectivityMultiplePlatformSupportPowerAndPerformanceSybase Symposium 2007 – November 15 - Brussels 14

Simplified development for today, tomorrow,and beyond2007v11.02007v11.12008v11.22008v11.52009v12.NET Simplified.NET Enhanced.NET EnhancedTW 2008.NET Exploited• Deploy applicationsand NVOs to .NET• UI and IDEEnhancements• DataWindowEnhancements• New and UpdatedDatabase Drivers• .NET incrementalcompiler• DBMS DriverEnhancements• r.a.d. Controls for WebForms• Enhanced Vista Support• AJAX Support for WebForms Applications• EAServer .NET ClientSupport• Enhanced GraphDataWindows• ISUG Enhance.• Requests• Windows Forms• Web Form• DBMS DriverEnhancements• .NET in the IDE• WPF/WCF support• Fully managed codeDataWindow• Languageenhancements tosupport .NETinteroperabilityLanguageIndependenceApplicationConnectivityMultiplePlatformSupportPowerAndPerformanceSybase Symposium 2007 – November 15 - Brussels 15

PowerBuilder 11.1FeaturesSybase Symposium15 November 2007Diamant Brussels

PowerBuilder 11.1 FeaturesEnhanced Vista SupportIncremental Compile for .NET Application TargetsUpdated database connectivityOrcaScript Enhancement for Windows Forms DeploymentPipeline Support for .NET TargetsNull values allowed in DataWindow Retrieval Arguments DialogEnhanced Web Form ControlsSybase Symposium 2007 – November 15 - Brussels 17

PowerBuilder 11.1 Features(Continued…)Web service client support in Web FormsRightToLeft support for DatePicker and MonthCalendarPage display properties for RichTextEdit controlSybase Symposium 2007 – November 15 - Brussels 18

EnhancedWindows VistaSupportSybase Symposium15 November 2007Diamant Brussels

Windows Vista SupportTested on 32-bit and 64-bit Windows VistaBusiness EditionPowerBuilder and PowerBuilder applications runas 32-bit applications on both environmentsPowerBuilder 11.1 satisfies the Works withWindows Vista requirementsApplications built with PowerBuilder can bedesigned to meet the Certified for Windows VistarequirementsSybase Symposium 2007 – November 15 - Brussels 20

Windows Vista SupportYou must have administrativeprivileges to installPowerBuilder on WindowsVistaDevelopers should runPowerBuilder withAdministrative PrivilegesRight click on PowerBuilderand select Run asAdministrator from the popupmenuSybase Symposium 2007 – November 15 - Brussels 21

Deploying Applications to WindowsVistaFor certified Windows Vista Logo applications youmust follow User Account Control (UAC) guidelinesThe executable file must have an embeddedmanifest that defines the execution level andspecifies whether access to the user interface ofanother window is requiredUse the Security tab page in the Application and.NET Windows Forms Project painters to specifythe necessary propertiesSybase Symposium 2007 – November 15 - Brussels 22

• Embedded Manifest• Select if your applicationneeds to be certified for Vista• External Manifest• generate a standalonemanifest file in XML format• No Manifest• if you do not need to distributea manifest fileSybase Symposium 2007 – November 15 - Brussels 23

• Highest Available•Have the AIS retrieve thehighest available accessprivileges for the user whostarted the process• Require Administrator•The application processmust be created by amember of theAdministrators group• As Invoker•The application does notneed elevated oradministrative privilegesSybase Symposium 2007 – November 15 - Brussels 24

• If the application needs todrive input to higher privilegewindows on the desktop, suchas an on-screen keyboard,select the Allow access toprotected system UI checkbox• For most applications youshould not select this checkbox. Microsoft provides thissetting for user interfaceAssistive Technology (Section508) applications• If you check this box, theapplication must beAuthenticode signed and mustreside in a protected location,such as Program Files orWindows\system32Sybase Symposium 2007 – November 15 - Brussels 25

Deploying Applications to WindowsVistaVista warns you if the application you want to runuses any DLLs that have not been signed with anAuthenticode certificateIf you want to deploy your application withWindows Vista Logo certification, all the DLLs thatyou distribute with it must be signedPowerBuilder runtime DLLs, and all otherPowerBuilder DLLs, are signedSybase Symposium 2007 – November 15 - Brussels 26

Moving Web Forms applications to aClassic .NET poolPowerBuilder web form applications are deployedto an application pool that uses a new IIS 7Integrated modeTo avoid compatibility issues, PowerBuilder WebForms applications must be run in an applicationpool that uses existing ASP.NET APIs, the “Classic.NET” modeSybase Symposium 2007 – November 15 - Brussels 27

Sybase Symposium 2007 – November 15 - Brussels 28

Sybase Symposium 2007 – November 15 - Brussels 29

Setting up permissions for Web FormsapplicationsWhen you deploy a new Web Forms target, a tempdirectory is created in theInetpub\wwwroot\application_name directoryFiles are written to and deleted from this directory,therefore the IIS_IUSRS group must have fullpermissions on tempSybase Symposium 2007 – November 15 - Brussels 30

Setting up permissions for Web FormsapplicationsBefore a PowerBuilder .NET Web Formsapplication connects to a SQL Anywhere®database, you must:• start the database manuallyor• grant the IIS_IUSRS group on IIS 7 default permissions for theSybase\Shared and Sybase\SQL Anywhere directories• Make sure you replace permissions of all child objects in thosedirectoriesFull permissions are required for the database anddatabase log files used by your applicationSybase Symposium 2007 – November 15 - Brussels 31

Web Forms deployment to IIS 7requires IIS compatibility componentDeploying a Web Forms target to a server runningVista and IIS 7 fails if the Vista MetabaseCompatibility component of IIS 7 is not installedThis component is not installed by defaultYou can install it from Internet InformationServices>Web Management Tools>IIS 6Management Capability FeatureSybase Symposium 2007 – November 15 - Brussels 32

Using Web Forms targets on 64-bitsystemsIf you create a Web Forms target on a Vista 64-bitsystem you might receive an error message that theapplication cannot be loaded when you try to run it inInternet ExplorerResolution: start 32-bit ASP.NET on the server usingthe following command line:• cscript c:\inetpub\adminscripts\adsutil.vbs SETW3SVC/AppPools/Enable32bitAppOnWin64 1You must have the Vista Metabase Compatibilitycomponent installed, and you must run this commandas administratorSybase Symposium 2007 – November 15 - Brussels 33

Windows Help filesWindows Vista does not distribute theWinHelp32.exe file required to open Windows Helpfiles such as the pbhlp110.hlp file used inPowerBuilderTo use .hlp files, you need to download a specialVista version of WinHelp32.exe from the MicrosoftWeb site athttp://go.microsoft.com/fwlink/?LinkID=82148Sybase Symposium 2007 – November 15 - Brussels 34

Windows Help filesCompiled HTML Help (.chm) files are supported,but you need to edit the Windows registry toenable a Help macro that supports links from thepbhlp110.hlp file to the pbman110.chm fileIf you do not edit the registry, the “For moreinformation” links at the bottom of many topics inthe Windows Help display an errorYou also need to edit the registry if you need to runWindows Help files at a remote location on anintranetSybase Symposium 2007 – November 15 - Brussels 35

Windows Help filesMicrosoft prohibits the distribution ofWinHelp32.exe with deployed applicationsIf your application uses .hlp files, you shouldprovide your users with instructions on how todownload WinHelp32.exeFor more information, see the Microsoft supportsite at http://support.microsoft.com/kb/917607Sybase Symposium 2007 – November 15 - Brussels 36

Limitations on Windows VistaJSP Targets are not supported on VistaSeveral properties of the DatePicker, calendar editmask and MonthCalendar control are notsupported on Vista• The WeekNumbers property is not supported for theDatePicker• The MonthCalendar property does not display correctly withthe WeekNumbers property selected and AutosizeHeight setto FALSESave As PDF has special requirements on Vista(see the New Features document for details)Sybase Symposium 2007 – November 15 - Brussels 37

Vista manifest files may crash otheroperating systemsIf you add a manifest file that contains Vistaextensions to an executable or DLL file onWindows XP with Service Pack 2, memory may becorrupted, causing the operating system to crashor restartKnown Microsoft issue described on the Microsoftsupport site athttp://support.microsoft.com/Default.aspx?kbid=92A patch is available on the Microsoft Web site athttp://www.microsoft.com/technet/security/Bulletin/MS06-075.mspxSybase Symposium 2007 – November 15 - Brussels 38

IncrementalCompile for .NETApplicationTargetsSybase Symposium15 November 2007Diamant Brussels

Incremental rebuild for .NETapplication targetsWhen used, only the classes that are affected by one ormore changes are recompiled during the build processThe incremental rebuild process for .NET targets isconducted as the first step of a project's deployment toa .NET platformAlthough deployment remains at the project level,incremental rebuilds are done at the target levelMultiple projects within a single target can benefit bysharing the same incremental build assemblies or .NETmodules.Sybase Symposium 2007 – November 15 - Brussels 40

.NET Web Service and .NET AssemblytargetsIncremental builds are not available for .NETcomponent targetsThe PowerBuilder .NET compiler always does fullrebuilds for these target typesSybase Symposium 2007 – November 15 - Brussels 41

Triggering build and deployoperationsPowerBuilder lets you trigger build and deployoperations when you run or debug a .NET WebForms or Windows Forms projectBy default, whenever your run or debug a .NETapplication PowerBuilder determines if there is acorresponding build directory for the selectedtarget• If there is, PowerBuilder checks to see if the .NET modules inthe build directory are consistent with the latest changes toeach object in your current applicationSybase Symposium 2007 – November 15 - Brussels 42

Triggering build and deployoperations (continued…)If PowerBuilder detects a change to animplementation or interface or if the build directorydoes not exist for the current target, PowerBuilderdisplays a message box that tells you the project isout of date and that prompts you to redeploy theprojectThe message box has three buttons (Yes, No, andCancel) and a check box that lets you prevent thedisplay of the message box the next time you clickor select run (or debug)Sybase Symposium 2007 – November 15 - Brussels 43

If You Select:Yes – The project is built based on the setting youhave selected in the project painter (Incremental orFull)No – PowerBuilder attempts to run the currentlydeployed target even though it is out of dateCancel – Terminates the run or debug requestSybase Symposium 2007 – November 15 - Brussels 44

Do not ask me again:If you select the “Do notask me again” check boxand then click the Yes orNo button, PowerBuildermodifies a drop-down listselection on the Generaltab of the System Optionsdialog boxSybase Symposium 2007 – November 15 - Brussels 45

.NET ModulesFor a debug build, the PowerBuilder .NET compilercreates a .NET module for each PowerBuilder classor class group• Applications with a large number of objects or windows withmany controls will have a large number of .NET modulesgenerated at deployment timeFor a release build, the compiler creates a .NETmodule for each PBL rather than for each class orclass group• This greatly reduces the number of files that need to bedeployed with the applicationSybase Symposium 2007 – November 15 - Brussels 46

Remote Deployment and Smart ClientApplicationsIncremental rebuilds are supported for deploymentto remote servers as well as for MSI file generationIn addition to saving time on deployment, thegeneration of .NET modules is especially beneficialfor smart client Windows Forms applications,because the modules can reduce the size of theassembly files that need to be updatedSybase Symposium 2007 – November 15 - Brussels 47

PBD GenerationPowerBuilder generates PBD files for applicationPBLs containing DataWindow, Query, or PipelineobjectsThe PBD files are linked as external resources withthe generated .NET modules and assembliesSybase Symposium 2007 – November 15 - Brussels 48

PBD Generation – Incremental BuildsThe PBD files are generated only for PBLs in whichmodifications have been made to DataWindow,Query, or Pipeline objectsFor .NET target types, the PBD files are generatedin a “pbd” subdirectory of theTargetName.pbt_build directoryThe PBD files are deployed together with thegenerated .NET modules or assembliesOn deployment, they are not deleted from thissubdirectory since they are used to check forchanges during subsequent incremental buildsSybase Symposium 2007 – November 15 - Brussels 49

PBD Generation – Incremental BuildsIf you only make data changes to DataWindowobjects before an incremental rebuild, the .NETrebuild process is skipped entirely and onlyapplication PBD files are redeployed.Sybase Symposium 2007 – November 15 - Brussels 50

PBD Generation – Full BuildsPBD files are always generated for PBLs containingDataWindow, Query, or Pipeline objects even whenthere are no changes to these objects• You can prevent generation by clearing a check box next to thePBL name on the Library Files tab page of the Project painterSince you cannot use incremental builds with .NETcomponent targets, PBD files are always generatedby default for these target typesSybase Symposium 2007 – November 15 - Brussels 51

How Incremental Compile WorksThree kinds of changes handled by the compiler:• Implementation changes, such as modifications to a functionbody or to the properties of a class• Interface changes, such as the removal of a function or themodification of a function prototype• Data changes, including edits made to a DataWindow, Query,or PipelineobjectSybase Symposium 2007 – November 15 - Brussels 52

How Incremental Compile Works(continued…)The IDE collects the information that has changed,performs a full or incremental PowerScript rebuild, andpasses the necessary information to thepb2cs .NETtranslatorIf the PowerScript compiler reports any errors the IDEdoes not invoke the .NET translatorAn interface change can also affect code in classes thatare compiled in a different .NET module of the sametarget• If you rebuild the project using the incremental rebuild process,the .NET runtime throws an exception when you try to run theapplication!Sybase Symposium 2007 – November 15 - Brussels 53

Runtime ExceptionsPowerBuilder catches and translates .NET runtimeexceptions to error messages describing theexception sourceBefore redeploying the application, you can correctthis type of error by changing the PowerScript codebased on the contents of the error message or byperforming a full rebuildIf there are many places in other .NET modulesaffected by the interface change, it is best to do afull rebuildSybase Symposium 2007 – November 15 - Brussels 54

UpdateddatabaseconnectivitySybase Symposium15 November 2007Diamant Brussels

Informix 10 SupportThe I10 interface supports ANSI/DBCS and UnicodedatabasesThe I10 interface supports Informix long objectnames with up to 128 charactersWith IDS 9.2.1 and later, you can change the nameof an index in the Database painter when you areconnected using the I10 interfaceSQL Statement Caching is SupportedSybase Symposium 2007 – November 15 - Brussels 56

Informix 10 SupportCreating and dropping indexes without lockingColumn-level encryption is supportedUsing multiple OUT parameters in user-definedroutinesSybase Symposium 2007 – November 15 - Brussels 57

Oracle 10g SupportStatement caching in Oracle 10g provides andmanages a cache of statements for each sessionTo set the maximum size of the statement cache,set the StatementCache DBParm to the number ofstatements you want to cache• 0 (Default) means caching is disabledThis option is available only in the O10 databaseinterfaceSybase Symposium 2007 – November 15 - Brussels 58

Sybase ASE 15 SupportIn Adaptive Server® Enterprise 15.0 and later, youcan use the following datatypes as identitycolumns:• bigint, int, numeric, smallint, tinyint, unsigned bigint, unsignedint, and unsigned smallintThis support has been added to the ASE and SYCdatabase interfaces for PowerBuilder 11.1Sybase Symposium 2007 – November 15 - Brussels 59

OrcaScriptEnhancement forWindows FormsDeploymentSybase Symposium15 November 2007Diamant Brussels

OrcaScript SupportPowerBuilder 11.1 includes a new ORCA libraryfunction for silently building and deploying aWindows Forms project according to thespecifications contained in the project objectYou can call the Windows Forms deploymentfunction with the following OrcaScript command:Deploy WinForm Project "pblName", "entryName", "iconName"Sybase Symposium 2007 – November 15 - Brussels 61

Pipeline Supportfor .NET TargetsSybase Symposium15 November 2007Diamant Brussels

Pipeline SupportPowerBuilder 11.1 supports the use of Pipelineobjects in:• Windows Forms targets• .NET Web Service targets• .NET Assembly targets(Note: The pipeline is not directly supported in .NET Web Formapplications but can be called using a .NET assembly or .NETWeb Service)Pipelines are now supported through thepbdpl110.dll, which must be deployed with both.NET and standard PowerBuilder applicationsPbdpl110.dll has been added to the RuntimePackagerSybase Symposium 2007 – November 15 - Brussels 63

Null valuesallowed inDataWindowRetrievalArguments DialogSybase Symposium15 November 2007Diamant Brussels

Sybase Symposium 2007 – November 15 - Brussels 65

Enhanced WebForm ControlsSybase Symposium15 November 2007Diamant Brussels

Enhanced Web ControlsImproved menu, toolbar, DatePicker, andMonthCalendar controls are available in 11.1Set the PBWebControlSource property to RADSybase Symposium 2007 – November 15 - Brussels 67

Enhanced Menu and Toolbar ControlsSybase Symposium 2007 – November 15 - Brussels 68

Enhanced DatePicker and MonthCalendarControlsSybase Symposium 2007 – November 15 - Brussels 69

Web serviceclient support inWeb FormsSybase Symposium15 November 2007Diamant Brussels

Web service client support in Web FormsWorked in PowerBuilder 11.0, but was not fullyQA’dYou must import the pbwsclient110.pbx extensioninto your .pbl (you can’t add the .pbd to your librarylist)Other PBNI Extensions (PBDOM, EJB Client, etc.)are not supported in .NET TargetsSybase Symposium 2007 – November 15 - Brussels 71

RightToLeftsupport forDatePicker andMonthCalendarSybase Symposium15 November 2007Diamant Brussels

RightToLeft support for DatePicker andMonthCalendarNow supported for Win32 and Windows FormsapplicationsNot supported in Web Form ApplicationsSybase Symposium 2007 – November 15 - Brussels 73

Page displayproperties forRichTextEditcontrolSybase Symposium15 November 2007Diamant Brussels

Page display properties for RichTextEditcontrolAllows you to manage the size and orientation ofdocuments inside the RT controlsSeparate from the page properties that can be set atruntime for printing the contents of RichTextEditcontrolsThey are also separate from the height and widthproperties of the controls themselvesSybase Symposium 2007 – November 15 - Brussels 75

PropertyPaperHeightPaperWidthPaperOrientationDescriptionValue for the height of the page in current unitsValue for the width of the page in current unitsSwitches the values for PaperHeight andPaperWidth• PaperPortrait!•If current PaperWidth is larger than current PaperHeight, values switched soPaperHeight is larger•If current PaperWidth is smaller than current PaperHeight, values not changed•Returns 0 for this setting• PaperLandscape!•If current PaperHeight is larger than current PaperWidth, values switched soPaperWidth is larger•If current PaperHeight is smaller than current PaperWidth, values not changed•Returns 1 for this setting• PaperOrientation value is also set to PaperLandscape! when PaperHeight andPaperWidth are the same sizeSybase Symposium 2007 – November 15 - Brussels 76

Q & ASybase Symposium 2007 – November 15 - Brussels 77

Sybase Symposium 2007 – November 15 - Brussels 78