Misleading or even indecipherable exception messages seem to be the rule of the day when it comes to debugging JCo connector installation exceptions. These are the exceptions that arise from misplaced libraries, mismatched library versions, or platform-specific installation issues. Over the years, I have run the gamut of JCo library installation errors. Whether I am simply trying to install a new version of JCo or porting an existing JCo-based application to a new operating system, I run into the inevitable JCo exception that sends me scouring the Web for a solution.
The following list is an attempt to gather the most common JCo installation exceptions into one concise checklist. My intent is to provide you with a single resource to quickly diagnose and resolve issues related to installing and supporting the SAP Java Connector.
Although these exceptions occur across different platforms, I have decided to keep my directory listings and library names specific to the Windows platform. This is not due to any strong bias I have for Microsoft (far from it, in fact), but to provide information relevant to the platform most developers use to support initial application development, i.e. Windows. The final section details issues around getting JCo to work on a UNIX-flavor system.
Austin Sincock, technical author and SAP/Java evangelist Austin Sincock is a freelance SAP integration architect, specializing in high performance Java development for SAP. He is also the author of Enterprise Java for SAP.
Copyright 2005TechTarget
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.
All Rights Reserved, Copyright 2000 - 2008, TechTarget | Read our Privacy Policy SearchSAP.com is a search service provided by TechTarget and is completely independent of and not affiliated with SAP AG.