Release Bulletin PowerBuilder® Application Server Plug-In 1.0 for Windows
Document ID: DC30121-01-0100-01
Last revised: December 8, 2006
Accessing current release bulletin information
A more recent version of this release bulletin may be available on the Web. To check for critical product or document information added after the product release, use the Sybase Product Manuals Web site.Accessing release bulletins at the Sybase Product Manuals Web site
Go to Product Manuals.
Select a product and language and click Go.
Select a product version from the Document Set list.
Select the Release Bulletins link.
From the list of individual documents, select the link to the release bulletin for your platform. You can either download the PDF version or browse the document online.
Enclosed is Sybase PowerBuilder™ Application Server Plug-In version 1.0, which is compatible with the following platform and operating system configurations:
Microsoft Windows 2000, Service Pack 4 or later
Microsoft Windows XP Professional, with Service Pack 2 or later
Microsoft Windows Server 2003, Standard Edition or Enterprise Edition
PowerBuilder Application Server Plug-In version 1.0 uses a streamlined installation program, and includes PowerBuilder version 10.5.1 support, which is optimized for JDK 1.4.
Supported application servers
PowerBuilder Application Server Plug-In version 1.0 runs in the following application servers:
BEA WebLogic 9.2
IBM WebSphere 6.1
See the User’s Guide for installation instructions and information about product features. You can view this book on the Sybase Product Manuals Web site. Browse to the PowerBuilder Application Server Plug-In 1.0 collection, then select this title. This manual is also available on the SyBooks™ CD included with your product.
Running the silent installer
(CR #449342) If you install the PowerBuilder Application Server Plug-In by running the silent installer, you must set the administrative password in SilentInstall.bat.
Workaround: Before you run the silent installer, edit SilentInstall.bat, and add this line to set the administrative password:
set JVM_ARG=%JVM_ARG% -Deas.password=password
See the User’s Guide for more information about running the silent installer.
Generating a license key is not required
(CR #449594) A license key ships with the product; therefore, you can skip the license server screen in the installer, the purpose of which is to generate a license key.
Reinstalling the server plug-in
If you attempt to reinstall the PowerBuilder Application Server Plug-In on a machine with an existing installation, the reinstallation may fail.
Workaround: Delete the C:\Program Files\Common Files\InstallShield\Universal\PBASP\Gen1 directory, then run the installer again.
Proxy server IIOPS listeners may not start
(CR #449081) Some proxy server IIOPS listeners do not start. See the following subsections for details.
Client Edition proxy server IIOPS listeners
Client Edition proxy server IIOPS listeners do not start. This problem exists for all of the supported application servers.
Configure the Client Edition proxy server, as described in the User’s Guide.
Copy %PB_SERVER_HOME%\Repository\Security\*.jks to %PB_SERVER_HOME%\..\EJBProxy\Repository\Security.
WebSphere only: copy %WAS_HOME%\plugins\com.ibm.ws.security.crypto_6.1.0.jar to %PB_SERVER_HOME%\..\EJBProxy\lib.
Server Edition proxy server IIOPS listeners
If a Server Edition proxy server is configured for a WebSphere application server, the IIOPS listeners do not start.
Configure the Server Edition proxy server for WebSphere, as described in the User’s Guide.
Copy %WAS_HOME%\plugins\com.ibm.ws.security.crypto_6.1.0.jar to %PB_SERVER_HOME%\lib.
Deploying to a WebSphere application server
(CR #448354) In a WebSphere application server, deployment may fail if global security is enabled.
Note:The following workaround negates the server’s deployment security.
Workaround: Add the user name and password of a user that has deployment privileges on the server (for example, the administrative user) to the soap.client.props file:
Change to the AppServer\profiles\AppSrv01\properties subdirectory of your WebSphere installation.
Edit soap.client.props, and supply values for com.ibm.SOAP.loginUserid and com.ibm.SOAP.loginPassword in the following section, then save and close the file:
#------------------------------------------------- # SOAP Client Security Enablement # # - security enabled status (false[default], true) #------------------------------------------------- com.ibm.SOAP.securityEnabled=true com.ibm.SOAP.loginUserid=userID com.ibm.SOAP.loginPassword=password
Restart the application server.
Documentation updates and clarifications
This section contains updates and clarifications for the PowerBuilder Application Server Plug-In User’s Guide.
Chapter 2, “Creating Embedded Installations”
The instructions in this chapter for setting the administrative password in SilentInstall.txt are incorrect. See “Running the silent installer” in this release bulletin.
Chapter 4, “Developing PowerBuilder Clients”
The section “Enabling PowerBuilder clients to communicate with EJBs” describes how to generate proxy classes for the EJBs deployed in an application server, and how to code a PowerBuilder client application to communicate with a proxy server. You can also set up IIOPS listeners for secure connections between PowerBuilder clients and proxy servers, which is documented below.Setting up IIOPS listeners for the Client Edition proxy server
On a machine where an EAServer 5.x client runtime is installed, set the JAGUAR_CLIENT_ROOT environment variable to the client runtime root directory.
Verify that the database files, sybcert.db and sybkey.db, exist in JAGUAR_CLIENT_ROOT\db.
Set the JAGSSL environment variable to true.
Start the PowerBuilder IDE in the same environment where JAGUAR_CLIENT_ROOT and JAGSSL are set.
Code your client application, using the “Sample PowerBuilder client,” below, as a guide.
set-certificate admin@system -file sample.crt
where sample.crt is a certificate file that contains an X509 certificate in Base64 encoding format.
To create a sample certificate file, see “Sample certificate”.
Code your PowerBuilder client application, using the sample below as a guide.
Sample PowerBuilder client
This sample PowerBuilder client sets up an IIOPS listener and uses the secure connection to invoke the pbtest/n_pbadd component, which is deployed in the application server.
SSLServiceProvider l_ssl integer li_rc this.getContextService("SSLServiceProvider", l_ssl) // Set the SSL properties li_rc = l_ssl.setglobalproperty( "qop", "sybpks_domestic_mutual_auth" ) if li_rc <> 0 then MessageBox("Error Setting SSL Parameters", "Error " + String(li_rc) + " when setting QOP") return end if li_rc = l_ssl.setglobalproperty( "pin", "sybase" ) if li_rc <> 0 then MessageBox("Error Setting SSL Parameters", "Error " + String(li_rc) + " when setting PIN") return end if li_rc = l_ssl.setglobalproperty( "certificateLabel", "Sample1 Test ID" ) if li_rc <> 0 then MessageBox("Error Setting SSL Parameters", "Error " + String(li_rc) + " when setting certificate label") return end if //Invoke component Powerscript long ll_rc connection ln_connect n_pbadd ln_mycomp ln_connect = CREATE connection ln_connect.userid = "admin@system" ln_connect.password = "sybase123" ln_connect.driver = "jaguar" ln_connect.options = "ORBLogIIOP='true', ORBLogFile='c:\orb.log'" ln_connect.location = "iiops://my-pc:2002" ln_connect.options = ln_connect.options + ",ORBForceSSL='true'" ll_rc = ln_connect.ConnectToServer() if ll_rc = 0 then ll_rc = ln_connect.CreateInstance(ln_myComp, "pbtest/n_pbadd") if ll_rc = 0 then MessageBox("Add Returned", ln_myComp.add(3,5) ) else MessageBox("Create Instance Failed", "Error: " + string(ll_rc) + + " " + ln_connect.errText, StopSign!) end if else MessageBox("Connect to Server Failed", "Error: " + string(ll_rc) + + " " + ln_connect.errText, StopSign!) end if ln_connect.disconnectServer()
To create a sample certificate, you can run the following Ant script, which calls the genkey task to generate a public/private key pair, then calls keytool.exe to export the public key to an X509 certificate in printable encoding format (Base64).
This example assumes familiarity with the keytool and certificate architecture used by Sun Microsystems. For more information, see the keytool documentation.
<!-- Generate a keypair --> <target name="gen-key-pair"> <genkey alias="duke" keypass="keypass" keystore="keystore.jks" storepass="storepass" verbose="true"> <dname> <param name="CN" value="Duke User Name"/> <param name="OU" value="Engineering"/> <param name="O" value="Sun Microsystems"/> <param name="L" value="Cupertino"/> <param name="ST" value="CA"/> <param name="C" value="US"/> </dname> </genkey> </target> <!-- Export the public key for duke --> <target name="export-pub-key"> <exec executable="keytool.exe"> <arg value="-export"/> <arg value="-rfc"/> <arg value="-keystore"/> <arg path="keystore.jks"/> <arg value="-storepass"/> <arg value="storepass"/> <arg value="-keypass"/> <arg value="keypass"/> <arg value="-alias"/> <arg value="sample"/> <arg value="-file"/> <arg path="sample.crt"/> </exec> </target>
Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you have any questions about this installation or if you need assistance during the installation process, ask the designated person to contact Sybase Technical Support or the Sybase subsidiary in your area.
Other sources of information
Use the Sybase Getting Started CD, the SyBooks CD, and the Sybase Product Manuals Web site to learn more about your product:
The Getting Started CD contains release bulletins and installation guides in PDF format, and may also contain other documents or updated information not included on the SyBooks CD. It is included with your software. To read or print documents on the Getting Started CD, you need Adobe Acrobat Reader, which you can download at no charge from the Adobe Web site using a link provided on the CD.
The SyBooks CD contains product manuals and is included with your software. The Eclipse-based SyBooks browser allows you to access the manuals in an easy-to-use, HTML-based format.
Some documentation may be provided in PDF format, which you can access through the PDF directory on the SyBooks CD. To read or print the PDF files, you need Adobe Acrobat Reader.
Refer to the SyBooks Installation Guide on the Getting Started CD, or the README.txt file on the SyBooks CD for instructions on installing and starting SyBooks.
The Sybase Product Manuals Web site is an online version of the SyBooks CD that you can access using a standard Web browser. In addition to product manuals, you will find links to EBFs/Maintenance, Technical Documents, Case Management, Solved Cases, newsgroups, and the Sybase Developer Network.
To access the Sybase Product Manuals Web site, go to Product Manuals.
Sybase certifications on the Web
Technical documentation at the Sybase Web site is updated frequently.Finding the latest information on product certifications
Point your Web browser to Technical Documents.
Click Certification Report.
In the Certification Report filter select a product, platform, and timeframe and then click Go.
Click a Certification Report title to display the report.
Point your Web browser to Availability and Certification Reports.
Either select the product family and product under Search by Base Product; or select the platform and product under Search by Platform.
Select Search to display the availability and certification report for the selection.
Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.
Point your Web browser to Technical Documents.
Click MySybase and create a MySybase profile.
Sybase EBFs and software maintenanceFinding the latest information on EBFs and software maintenance
Point your Web browser to the Sybase Support Page.
Select EBFs/Maintenance. If prompted, enter your MySybase user name and password.
Select a product.
Specify a time frame and click Go. A list of EBF/Maintenance releases is displayed.
Padlock icons indicate that you do not have download authorization for certain EBF/Maintenance releases because you are not registered as a Technical Support Contact. If you have not registered, but have valid information provided by your Sybase representative or through your support contract, click Edit Roles to add the “Technical Support Contact” role to your MySybase profile.
Click the Info icon to display the EBF/Maintenance report, or click the product description to download the software.
This document is available in an HTML version that is specialized for accessibility. You can navigate the HTML with an adaptive technology such as a screen reader, or view it with a screen enlarger.
PowerBuilder Application Server Plug-In 1.0 and the HTML documentation have been tested for compliance with U.S. government Section 508 Accessibility requirements. Documents that comply with Section 508 generally also meet non-U.S. accessibility guidelines, such as the World Wide Web Consortium (W3C) guidelines for Web sites.
The online help for this product is also provided in HTML, which you can navigate using a screen reader.
Note:You might need to configure your accessibility tool for optimal use. Some screen readers pronounce text based on its case; for example, they pronounce ALL UPPERCASE TEXT as initials, and MixedCase Text as words. You might find it helpful to configure your tool to announce syntax conventions. Consult the documentation for your tool.
For information about how Sybase supports accessibility, see Sybase Accessibility. The Sybase Accessibility site includes links to information on Section 508 and W3C standards.