Thursday, October 25, 2007

Be a rebel...

I needed to validate LiveCycle ES 8.0.1 against Windows 2003 R2 - 64 bit and SQL 2000 Server. According to the install documentation (pg13) , this is a big no no.:
Intel x86 compatibilityOn supported Windows and Linux environments, LiveCycle ES supports Intel EDT64 and AMD64 compatible chipsets, but the operating system must be 32 bit.
Microsoft Windows Server 2003 Enterprise Edition or Standard Edition SP1 and R2 (32-bit edition only)

Good news!

The installation and configuration went basically flawlessly. The only thing I ran into problem with was the JDBC Driver.

I started the installation process using: SQL Server 2000 Driver for JDBC Service Pack 3 . Unfortunately I ran into some SQL issues during start up of my jboss app server. Specifically I got the "Can't start manual transaction mode because there are cloned connections". After a bit of googling, this turns out to be a problem with Microsoft Type 4 JDBC Driver and concurrent statements, transactions, or result sets on the same database connection. The resolution was to pass in "SelectMethod=cursor" in my connection string. I didn't like this very much, since SelectMethod=cursor potentially has performance impact.

After further researching, it turns out that the SQL Server 2005 JDBC Driver 1.2 supports SQL Server 2000 as well as 2005. Using this driver my connection issue went away, and I was unable to successfully complete the rest of my configuration steps for LCES.

The specifics of my environment below. Hopefully this may potentially help some of you.

Hardware: AMD X2 5600+ , 8GB of RAM
OS: Windows 2003 Server Enterprise Edition R2, 64 Bit
Java: JDK 1.5.0_13-windows-amd64
Database (on a remote machine): SQL 2000 Server SP4 on a Windows 2003 Enterprise (32bit)

Notes:
- Use the latest JDBC Drivers from Microsoft. Version 1.2 of the JDBC Driver was released recently, and my preliminary tests (Reader Extensions, create sample policies) worked without any issues.
- Set database to authenticate against mix mode (SQL Server and Windows authentication)
- Watch out for driver-class in adobe-ds.xml and mssql-ds.xml. I double checked by extracting the jar file to see what the path is.

Happy installation :-)

1 comment:

Hepzinde said...
This comment has been removed by a blog administrator.