Welcome!

Technology and Community

Jim O'Neil

Subscribe to Jim O'Neil: eMailAlertsEmail Alerts
Get Jim O'Neil via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Jim O'Neil

In PowerBuilder 11.2, .NET meets J2EE head-on with the capability to deploy .NET Windows Forms and Web Forms applications (as well as assemblies and Web Services) that access Enterprise JavaBeans (EJBs) in Sybase’s own EAServer. As you’ll see over the course of this article, integrating these “competing” technologies is quite straightforward and leverages mechanisms that have been available since PowerBuilder 7. The enabling technology for the .NET to J2EE functionality in PowerBuilder is the new client support introduced in EAServer 6.1. The EAServer .NET runtime includes three fully managed code assemblies: com.sybase.iiop.net.dll: supporting the Internet Inter-ORB Protocol (IIOP), data marshalling, and secure sockets layer (SSL) com.sybase.ejb.net.dll: supporting invocation of EJBs as well as PowerBuilder components (NVOs) com.sybase.jms.net.dll: supporting inter... (more)

The Debut of DataWindow.NET

In Part 1 we looked at the overall architecture of DataWindow.NET (PBDJ, Vol. 11, issue 4); in Part 2 we'll start coding our first application. We'll code a simple client application that contains two DataWindows with a master-detail relationship using the Department and Employee tables from the PowerBuilder 10 Demo Database (EAS Demo DB V10). For simplicity's sake, we'll provide the option to update only the employee salaries, but obviously the application could be easily extended to allow for inserting and deleting employees as well as departments. Creating the DataWindow Obje... (more)

EAServer Problem Analysis & Troubleshooting

Designing and implementing an n-tier or Internet application is a complex task, and issues resulting from errors in the runtime configuration or the application code itself are practically inevitable. Problem analysis and troubleshooting are part art, part science. Therefore, although the techniques discussed here can be helpful, the sheer diversity of client and server environments precludes a single recipe for resolving all issues. We'll focus on problems that involve PowerBuilder that occur from the point of connectivity all the way through an EAServer component's lifecycle, an... (more)

IBM & Informix

In this article we'll discuss connectivity requirements, Informix-specific data type processing, and the use of Informix stored procedures within the PowerBuilder environment. PowerBuilder offers developers four specific connectivity options for IBM Informix databases: Third-party Open Database Connectivity (ODBC) drivers Third-party Java Database Connectivity (JDBC) drivers Third-party OLE-DB providers The "native" driver available in the PowerBuilder Enterprise version In this article we'll focus on the last option and in Part 2 we'll discuss TEXT and BYTE data, Stored Procedur... (more)

Introduction To PBNI

Have you ever thought of adding new features to PowerBuilder? Or wanted to call Java or .NET from PowerScript? Or imagined that you can call PowerScript from C++ or Java? With PBNI, you can do them all and more. PowerBuilder Native Interface (PBNI) is a standard interface for third parties to extend the functionality of PowerBuilder. PBNI is a valuable new addition to the PowerBuilder programmer's toolbox that allows developers to reach beyond the already feature-rich constructs of PowerScript and custom class user objects (commonly referred to as nonvisual objects or NVOs). The... (more)