1.3.1 Why use Java Service Manager?

Many vendors and open source communities are implementing their technology using Java classes.

For example, when a customer order is created, an application may want to send a customer an email with the order details as an attachment. This type of application can be achieved by using Java Mail classes with your LANSA order entry functions. Without the Java Service Manager, this type of application can present a significant technological challenge for traditional business systems developers.

How do you natively call a Java program from your LANSA or RPG application?

If you have thirty different Java classes, how will you handle the coding for each class?

How will you manage error handling?

How will you manage the threads and resources for the application?

Manually creating and coding the interface to Java classes can be a challenging and time consuming task that is focused on technology and not your ultimate business solution. The JSM simplifies the integration of Java classes with your application by standardizing the interface and by managing the execution of the services. It includes a number of Java classes for exception handling, message handling, data conversion, etc. It also provides a comprehensive set of tracing utilities for the application developer. These features can dramatically reduce the time to integrate new Java classes with an application because the developer is not creating these utilities on their own.

The JSM allows you to focus on the business objectives of the applications rather than the underlying technological implementation. By using the Java Service Manager, a complex task or protocol can be simplified to a series of commands. LANSA developers only need to understand how to use the commands offered by the Java service.