Java Business Service Use (Doc ID 1680479.1)

Last updated on MARCH 21, 2016

Applies to:

Siebel CRM - Version 8.0 SIA [20405] and later
Information in this document applies to any platform.
*** Checked for currency MAR-21-2016 ***

Goal

Regarding use of Java Business Service :-

As stated in Transports and Interfaces: Siebel Enterprise Application Integration > EAI Java Business Service > About the Lifecycle of a Java Business Service :-

A JVM is created in-process with the Siebel process the first time a Java business service is invoked. Thereafter, the same JVM is used for all invocations of any Java business services.

An instance of the Java class implementing a business service is created the first time that business service is invoked. This instance is released through JNI when the native business service is destroyed. For business services that are not cached, this occurs whenever the caller (workflow, script) releases the native business service. For business services that are cached, this occurs when the session is destroyed (for example the user logs out). For a business service marked as cached in the repository, repeated invocations by a user during a single session will invoke methods on the same Java object.

What does 'in-process' mean, is the is JVM loaded in every OM thread, or only into the main thread ?
Also, if the JVM is shared across threads, is this a potential 'blocking point', with multiple concurrent Java Business Service (JBS) calls ?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms