Jeffrey Black

PowerDynamo to JSP conversion tool

Jeff Black — Fri, 07 May 2010 20:38:55 +0000

While attending the Sybase Developer Days event in Houston, TX yesterday (May 6, 2010) I had a conversation with a gentleman from Dallas supporting PowerDynamo running on EAServer 5.x (Jaguar). He told me that he needed to convert the PowerDynamo scripts to JSP’s; however he was unaware of a tool that Sybase shipped with EAServer to facilitate migrating from PowerDynamo scripts to JavaServer Pages.

I am including the link to SyBooks Online which documents its functionality. Hopefully this will be of use to someone else out there that needs to convert their PowerDynamo scripts to JSP’s and were unaware of the utility.

Dyn2JSP

Welcome to the PowerDynamo to JSP conversion tool. This tool is designed to aid you in converting your PowerDynamo Dynamic File site to a JSP file site. The conversion tool will make every effort to logically convert the DynaScript to an equivalent JSP, however not all scenarios have a conversion. At the end of this document you will find a table that identifies several of these common scenarios and provides you with information that will aid you in a manual conversion.

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.dc38032_0550/html/new55/BHACABEA.htm

Convert PowerBuilder ResultSet from EAServer to Java Collection

Jeff Black — Mon, 12 Apr 2010 21:09:13 +0000

The State of Texas has a massive n-tier PowerBuilder application using EAServer. That means they have a significant investment in PowerBuilder and by proxy — Datawindows! I am involved in several projects developing Java web applications in addition to my PowerBuilder work and I needed to tap that PowerBuilder Datawindow investment.

I thought I would share with the community how one can take an EAServer component developed with PowerBuilder and return a DataStore ResultSet to a Java class and convert the rows and columns of the java.sql.ResultSet to a Collection of Java beans.

I have a method named getContractList in a PowerBuilder NVO called n_spr deployed to an EAServer package named JaguarSPR. For instruction on how to build EAServer components using PowerBuilder please refer to the Sybase documentation.

The PowerBuilder code is pretty self-explanatory. If you are a PowerBuilder developer there is nothing remarkable about the method other than the return type is ResultSet. The code listing for the getContractList follows:

// Begin PowerBuilder Code  ---------------------------------------------------------------------------------------
// Method: getContractList
// Returns: ResultSet

long ll_rows
resultset lrs
datastore lds_data

iel.Log("Executing getContractList")
lds_data = CREATE datastore
lds_data.dataobject = "d_aft_contract_list"
lds_data.settransobject(sqlca)
iel.Log("Datastore created")

ll_rows = lds_data.Retrieve()
iel.Log("Contracts retrieved --> "+ string(ll_rows) )

if (ll_rows >= 0) then
  lds_data.GenerateResultSet(lrs)
end if

// return ResultSet to caller
return lrs

// End PowerBuilder Code ---------------------------------------------------------------------------------------

The Java code requires a bit more explanation so I have included some comments along the way to guide you through the process. If you have any questions, comments, or observations please drop me a note.

// Begin Java Code -------------------------------------------------------------------------------------------------
package us.tx.state.twc.twist.spr;

import CTS.PBUserException;
import JaguarSPR.n_spr;
import JaguarSPR.n_sprHelper;
import com.sybase.CORBA.jdbc11.SQL;
import java.sql.SQLException;
import java.util.Collection;
import java.util.Iterator;
import java.util.logging.Level;
import java.util.logging.Logger;
import org.apache.commons.dbutils.BasicRowProcessor;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import org.apache.struts.util.ModuleException;
import org.omg.CORBA.ORB;

/**
 * Obtain ResultSet from EAServer/PowerBuilder Component and convert to a Collection of Java Beans
 *
 */
public class JaguarContractBean {

 private static Log log = LogFactory.getLog(JaguarContractBean.class);    // commons logging reference
 public void getContractList() throws ModuleException {
 TabularResults.ResultSet contractResultSet = null;
 java.sql.ResultSet rs = null;

 //
 // Initialize the CORBA client-side ORB and
 // obtain a stub for the EAServer component instance.
 //
 log.info("... Creating CORBA session.");
 //
 // Initialize the ORB.
 //
 log.info("... Initialize ORB and get ORB object.");
 java.util.Properties props = new java.util.Properties();
 props.put("org.omg.CORBA.ORBClass", "com.sybase.CORBA.ORB");
 ORB orb = ORB.init((java.lang.String[]) null, props);

//
// Get reference to Jaguar (EAServer) component
//
log.info("... Create Jaguar component using FactoryHelper.");
org.omg.CORBA.Object object = null;
object = orb.string_to_object("JaguarSPR/n_spr");
n_spr comp = n_sprHelper.narrow(object);
//
// Call PowerBuilder component to obtain ResultSet
//

try {

contractResultSet = comp.getcontractlist();

if (contractResultSet != null) {

// We have a TabularResults::ResultSets CORBA IDL object returned from EAServer/PowerBuilder
// Convert the TabularResults::ResultSets CORBA IDL to an equivalent java.sql.ResultSet object
//
// http://infocenter.sybase.com/help/topic/com.sybase.dc37774_1100/html/apptech/BABBEEFI.htm
// http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc38037.0600/html/easref/X27842.htm
//
rs = SQL.getResultSet(contractResultSet);
XContractDTO contractObj = null;

//
// Use the Apache Commons DBUtils package to convert the SQL ResultSet to a Collection of Java Objects
// http://commons.apache.org/dbutils/apidocs/index.html
// 
BasicRowProcessor brp = new BasicRowProcessor();
Collection contractObjs = brp.toBeanList(rs, XContractDTO.class);
Iterator contractIter = contractObjs.iterator();
while (contractIter.hasNext()) {
  contractObj = (XContractDTO) contractIter.next();
  log.info("XContractDTO --> "+ contractObj.getAft_contract_id());
}

brp = null;
contractObjs = null;
contractObj = null;}
} catch (SQLException ex) {
  Logger.getLogger(JaguarContractBean.class.getName()).log(Level.SEVERE, null, ex);

} catch (PBUserException pbue) {


  log.error("error retrieving contract list from PowerBuilder component JaguarSPR/n_spr");
  log.error(pbue.getLocalizedMessage());
  ModuleException me = new ModuleException("error.pbue.message");
  throw me;
} finally {rs = null;
  contractResultSet = null;
  comp = null;
}
return;
}
}

    // End Java code --------------------------------------------------------------------------------------------------------------

Resources:

http://infocenter.sybase.com/help/topic/com.sybase.dc37774_1100/html/apptech/BABBEEFI.htm

http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc38037.0600/html/easref/X27842.htm

http://commons.apache.org/dbutils/apidocs/index.html

http://www.sybase.com/detail?id=1002670

Roll your own (sort of) sybase-easerver-config.xml file

Jeff Black — Tue, 30 Mar 2010 22:18:08 +0000

I am developing a Java Web-Application for deployment to Jaguar 5.5 (don’t ask). Anyway, whenever I finished deploying my application, using Jaguar Manager, I had to manually assign my JNDI Datasource (res-ref-name property) to the Connection Cache defined in Jaguar (res-link property) on the “Resource Refs” property tab of my application. After doing this entirely too many times I took the time away from my development efforts to automate this task on deployment.

The good people at Sybase enable me to perform this configuration via an EAServer XML configuration file embedded in the META-INF directory of my WAR file. Armed with the XML file appropriately named sybase-easerver-config.xml I can configure components, applications, Web applications, and connectors to my hearts content — automatically.

Creating the XML from scratch can be difficult and time consuming; however running the following command can provide you with a great start:

%jaguar_home%\bin>jagtool exportconfig -configtype create WebApplication:MyWebApplication

I have output from a sample application to review for your convenience:


 " + dsName);
   DataSource ds = (DataSource) ic.lookup(dsName);

   // 2. Obtain the ConnectionObject from the DataSource.
   System.out.println("... obtain reference to connection from our DataSource.");
   connectionObject = ds.getConnection();

   // 3. Create instance of Transaction object and "bind" it to the ConnectionObject.
   transObject = new Transaction();
   transObject.setDbms("JDBC");
   transObject.bindJDBCConnection(connectionObject);
   transObject.setAutocommit(true);

 } catch (NamingException e) {
   e.printStackTrace();
 } catch (SQLException e) {
   e.printStackTrace();
 }

 return;
}

Finally when you are finished using your Transaction object issue a disconnect to release the connection:

transObject.disconnect();

Datawindows and Chained Transactions: Part Two

Jeff Black — Thu, 25 Feb 2010 02:37:01 +0000

I recently authored a post about the failure of my Datawindows sourced from stored procedures to retrieve any data. What was remarkable about my Datawindows, other than the fact that they were sourced from stored procedures instead of SQL Selects, was that they “lived” on JSP’s in a JSF application deployed to EAServer.

The root of the problem with my Datawindows not retrieving any data after being deployed to EAServer was the fact that the connection cache the Datawindows were using was defaulting to “Chained Transactions” on.

Our DBA expressed a concern that something was forcing the connection cache, defined in EAServer, to “set chained on”.

This led to an interesting and enlightening conversation and fact-finding mission about Chained and Unchained Transactions and how they impact our database and applications.

At the end of the day we discovered that the jConnect for JDBC Driver was defaulting to “set chained on”. To force “set chained off” which allows “Unchained” database transactions I needed to specify the property SERVER_INITIATED_TRANSACTIONS=FALSE in the connection URL. Here is an example:

jdbc:sybase:Tds:dbserver.twc.state.tx.us:5000?SERVER_INITIATED_TRANSACTIONS=FALSE

Configuring this property to false forces the connection to operate with “Unchained Transactions”.

If you’re still reading this you may be asking “why do I care?”

If you are a PowerBuilder developer and familiar with the Transaction object’s AutoCommit property and its use in managing your database transactions, then you will want to know about this property when using jConnect for JDBC from your Java applications. Before changing this property you should check with your DBA to determine the impact on your transaction management strategy.

Datawindows and Chained Transactions

Jeff Black — Tue, 23 Feb 2010 21:00:34 +0000

During the course of working on a JSF project adorned with lovely Datawindows I decided to proceed the route that I had become very familiar with and that was the practice of sourcing my Datawindows from database stored procedures versus SQL Selects.

Having created the appropriate stored procedures I designed my Datawindow objects using the Datawindow Designer in Sybase Workspace. Using Workspace’s page editor I then dropped my Datawindows on my JSP and configured the appropriate property settings.

After deploying my application to EAServer I used my trusty browser to request the JSP. I was presented with my Datawindow however no data was returned. After opening my Datawindows in the designer I previewed them properly. Next I executed the procedures within ISQL. My procedures returned the data properly. The data was being returned in both ISQL and Sybase Workspace’s Datawindow Designer.

I decided to create Datawindow objects using SQL Select statements and reference them from my JSPs instead of those using stored procedures. After I deployed my application again I previewed my page: The Datatwindows retrieved the data as intended on my JSP.

What could possibly be the matter with my stored procedure sourced Datawindow objects and their ability to retrieve data via EAServer in my JSF application?

After a half-hour WebEx and conference call with Kevin Bates and Patricia Steinhardt of Sybase Technical Support the problem was identified and resolved.

Kevin ran a TDS Trace using Ribo against my target database (ASE 15). It was determined that my stored procedures were executing in “unchained” mode (See below):

EED Token (0xE5); variable length.
Length [2]:                   224
Message Number [4]:           7713
Message State [1]:            2
Message Class [1]:            16
SQL State Length [1]:         5
SQL State [5]:                “ZZZZZ”
Status [1]:                   NO_EED (0×00)
Transaction State [2]:        TDS_TRAN_SUCCEED (0×0001)
Message Length [2]:           195
Message Text [195]:           “Stored procedure ‘dbo.p_oltp_aft_contract_retrieve’ may be run only in unchained transaction mode. The ‘SET CHAINED OFF’ command will cause the current session to use unchained transaction mode.”
Server Name Length [1]:       8
Server Name [8]:              “OLTP_DEV”
Stored Proc. Name Length [1]: 0
Line Number [2]:              1

The solution for my problem was to execute the following statement on my database:

sp_procxmode p_oltp_aft_contract_retrieve, "anymode"

Following execution of the above statement, I used my browser to request the JSP containing my stored procedure sourced Datawindow and it retrieved the data as intended.

If you happen to experience similar symptoms don’t forget to check the transaction mode in which your stored procedures may be executing. An excerpt from Sybase’s jConnect for JDBC documenation addresses the subject:

Chapter 4: Troubleshooting

Stored procedure executed in unchained transaction mode

Sybase Error 7713 - Stored Procedure can only be executed in unchained transaction mode.

This error occurs when JDBC attempts to put the connection in autocommit(true) mode. The application can change the connection to chained mode using Connection.setAutoCommit(false) or by using a “set chained on” language command. This error occurs if the stored procedure was not created in a compatible mode.

To fix the problem, use:

sp_procxmode procedure_name,"anymode"

The Sybase Datawindow and the JSF Life-cyle

Jeff Black — Tue, 23 Feb 2010 15:15:43 +0000

I recently began working on a Java Server Faces project using Sybase Workspace and my beloved Datawindow. Sybase Workspace enables me to easily integrate my Datawindow programming expertise with the Java Server Faces web-application framework.

However, to get the most out of your JSF based Datawindow projects it is important to know when the various Datawindow “Handlers” and “Listeners” execute during the JSF life-cycle:

The Datawindow component’s onLoadHandler is executed between the BEFORE and AFTER APPLY_REQUEST_VALUES phase (Phase 2).
Any Sybase Datawindow component with registered Listeners (e.g. RetrieveListener, UpdateListener, SQLPreviewListener) will be executed between the BEFORE and AFTER APPLY_REQUEST_VALUES phase (Phase 2).
Any actions which call methods on Managed Beans used in conjunction with the Datawindow component (e.g. Updating a Datawindow) are executed between the BEFORE and AFTER INVOKE_APPLICATION phase (Phase 5).

The Sybase Datawindow component in conjunction with the Sybase Java Datastore provides the Datawindow programmer familiar and tremendous power when architecting and developing browser-based JSF applications. Understanding the JSF life-cycle and where the Datawindow fits within that life-cycle is crucial to exploit the full capability of the Datawindow that PowerBuilder developers have become so familiar.

Upgrading your “ancient” SQL Anywhere database

Jeff Black — Fri, 15 Jan 2010 16:55:34 +0000

I recently needed to upgrade an “ancient” Sybase Adaptive Server Anywhere database to SQL Anywhere 11. Sybase has some “terrific” tools that make upgrading your “ancient” database to their latest offering a snap.

Follow these steps borrowed from Sybase’s own documentation (iAnywhere Solutions, Inc.):

To rebuild a database (Sybase Central)

1. Carry out the standard precautions for upgrading software. See Important upgrade precautions.

2. If possible, defragment the drive where the new database will be stored because a fragmented drive can decrease database performance.

3. Ensure that you have exclusive access to the database to be unloaded and reloaded. No other users can be connected.

4. From the Start menu, choose Programs » SQL Anywhere 11 » Sybase Central.

5. From the Tools menu, choose SQL Anywhere 11 » Unload Database.

6. Read the introductory page of the Unload Database Wizard, and click Next.

7. Select Unload A Database Running On An Earlier Version Of The Server, Or A Database That Is Not Running. Enter the connection information for the database.
Click Next.

8. Select Unload And Reload Into A New Database. Click Next.

9. Specify a new file name for the database. Click Next.
You can specify the page size for the new database. In version 11, the default (and recommended) page size is 4096 bytes.
You can encrypt the database file if you want. If you choose strong encryption, you need the encryption key each time you want to start the database. See Encrypting a database.

10. Choose to unload structure and data. Click Next.

11. Specify whether you want to connect to the new database when the unload/reload is complete.

12. Click Finish. Examine the new database to confirm that the rebuild completed properly.

iAnywhere Solutions, Inc., “Rebuilding version 9 and earlier databases for version 11.0.0.” 2008.http://dcx.sybase.com/1100en/sachanges_en11/unloading-reloading-upgrading-newjasper.html#v10upgrade-b-3548731 (accessed 01-14-2010).

News Cycles

Jeff Black — Fri, 15 Jan 2010 12:32:11 +0000

Deep Thoughts: Do you suppose Tiger Woods is “thankful” for the Detroit airplane terrorist and the Haitian earthquake?

Sybase: Search stored procedures containing specific text

Jeff Black — Mon, 28 Dec 2009 16:32:27 +0000

I frequently have a need to search my Sybase ASE 15 database for stored procedures containing a specific string of text.

The following SQL may be used to return a listing of stored procedures that contain a fragment of text:

select distinct object_name(c.id) from syscomments c where c.texttype = 0 and c.text like '%correct defect 9781%'