Supported datatypes – PB Docs 110
Supported datatypes The following table describes the basic CORBA IDL types supported and their corresponding PowerScript type. CORBA IDL type Mode PowerScript type boolean in, return Boolean by value out, inout Boolean by reference char in, return Char by value out, inout Char by reference octet in, return Byte by value out, inout Byte by…
Supported datatypes – PB Docs 115
Supported datatypes The following table describes the basic CORBA IDL types supported and their corresponding PowerScript type. CORBA IDL type Mode PowerScript type boolean in, return Boolean by value out, inout Boolean by reference char in, return Char by value out, inout Char by reference octet in, return Byte by value out, inout Byte by…
About unsupported features – PB Docs 115
About unsupported features When you deploy a PowerBuilder application as a Web Forms application to an IIS server, PowerBuilder lists any unsupported features in the Output window. For the most part, unsupported features fail silently in the Web Forms application, but unexpected results can also occur. If an unsupported feature prevents the PowerBuilder to .NET…
About unsupported features – PB Docs 110
About unsupported features When you deploy a PowerBuilder application as a Web Forms application to an IIS server, PowerBuilder lists any unsupported features in the Output window. For the most part, unsupported features fail silently in the Web Forms application, but unexpected results can also occur. If an unsupported feature prevents the PowerBuilder to .NET…
Chapter 2 Moving PowerBuilder Applications to the Web – PB Docs 115
Chapter 2 Moving PowerBuilder Applications to the Web About this chapter In PowerBuilder 11.5 you can deploy PowerBuilder applications as ASP.NET Web applications. This chapter explains how to generate PowerBuilder applications as Web Forms applications. Contents Topic About PowerBuilder Web Forms applications Creating a PowerBuilder .NET Web Forms target Deploying and running a .NET Web…
Chapter 15 Building .NET Clients for EAServer – PB Docs 115
Chapter 15 Building .NET Clients for EAServer About this chapter This chapter describes how to connect to an EAServer component from a .NET client that you build in PowerBuilder. Contents Topic EAServer requirements Using the Connection object Using the JaguarORB object Support for CORBAObject and CORBACurrent objects Supported datatypes SSL connection support Document get from…
EAServer requirements – PB Docs 115
EAServer requirements You can build a .NET client application or component that invokes methods of Enterprise JavaBeans (EJB) components or PowerBuilder EAServer components running in EAServer 6.1 or later. This capability is based on the .NET client ORB library introduced in EAServer 6.1. Note When you install EAServer, you must install the .NET support option….
Support for CORBAObject and CORBACurrent objects – PB Docs 115
Support for CORBAObject and CORBACurrent objects The CORBAObject object gives PowerBuilder clients access to several standard CORBA methods. All proxy objects generated for EAServer components using the EAServer proxy generator are descendants of CORBAObject. The CORBACurrent service object provides information about the EAServer transaction associated with a calling thread and enables the caller to control…
SSL connection support – PB Docs 115
SSL connection support To enable .NET client applications developed in PowerBuilder to connect with EAServer using the Secure Sockets Layer (SSL), the computer where the .NET application runs must be configured to work correctly with the SSL authentication mode. You can connect using Server authentication or Mutual authentication. Server authentication If only server authentication is…
Creating a PowerBuilder .NET Web Forms target – PB Docs 115
Creating a PowerBuilder .NET Web Forms target System requirements You must install the .NET Framework 2.0, 3.0, or 3.5 SDK (x86) and AJAX Extensions on the same computer as PowerBuilder, and you must make sure that the system PATH environment variable includes the location of the .NET Framework. If you installed a 1.x version of…