Obviously, the JCo API was designed with flexible connectivity to the SAP application server in mind. Depending on the type of application you are building, any one of these connection mechanisms should fit your needs. Much of the development I do for SAP must be deployed within a Java application server, so the ResourceBundle approach gives me the ability to bundle the configuration file with the application. Likewise, you may find a combination of these approaches best suits your development needs. Regardless, the SAP connectivity delivered by the JCo API provides an invaluable resource to integrating Java applications within your SAP system landscape.
GETTING CONNECTED WITH JCO
Part 1: Specifying parameters as single String values
Part 2: Specifying parameters using a String array
Part 3: Specifying parameters using an external properties file
Part 4: Specifying parameters with a custom properties file
Review: Conclusion and more resources
|ABOUT THE AUTHOR:|
| 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 2005 TechTarget