Java and SNA: A case study

By Matt MacKinnon, Adam King, David Kaminsky
2003-05-24

Conclusions

As we demonstrated above, it's a fairly straightforward design exercise to create a Java-callable CPI-C library. The biggest problem--the conflicting method-calling conventions--is solved by passing objects.

More importantly, we have shown that Java needn't be considered an IP-only tool. Enterprises use SNA and will continue to demand its reliability and stability. We've shown that Intranet technologies such as Java do not exclude SNA networks. We expect enterprises to benefit from the combination of Java's strengths (such as platform-independence and dynamic download) and SNA's mission-critical reliability.

[1]

Tutorial Pages:
» Java and SNA: A case study
» The Java/CPI-C API
» Classic Transaction #1: The Pipe
» Classic Transaction #5: The Database Update
» Native Calls
» Diversion: Native Calls and Applets
» Performance
» CPIC Calls That Have Been Implemented
» Conclusions
» Footnotes

First published by IBM DeveloperWorks

Related Tutorials:
» All about JAXP, Part 1
» Make Database Queries Without the Database
» Load List Values for Improved Efficiency
» 2 Ways To Implement Session Tracking
» A Simple Way to Read an XML File in Java
» Develop Aspect-Oriented Java Applications with Eclipse and AJDT