Java Components

You can catalog Java class libraries (.jar files) and use them on your BPM project. Use Java components to integrate with external APIs or leverage Java code from your BPM project.

Integrating Java libraries

To catalog Java class libraries you must provide a the .jar files containing the Java classes and their dependencies.

Once the library is cataloged, Studio stores a copy of the .jar files in the lib/ directory of the project.

Cataloging Requirements

You can catalog any Java class or interface defined within a named Java package. You cannot catalog Java types defined without a package name.

You must also catalog any additional Java types referred by the Java classes and methods you need to use from your BPM project.

Runtime Requirements

If the Java classes you catalog depend on other .jar libraries on runtime, you must include these libraries into your BPM project.

All Java code used from a BPM project runs under the control of the SecurityManager of the Process Execution Engine runtime environment. Its security policies prevent cataloged Java code from performing some operations, including the following:

Shutting down the JVM
Spawning Threads or modifying/stopping existing Threads
Creating new ClassLoaders
Changing the Socket Factory
Changing the standard input/output of the JVM

Cataloging Java Libraries
Before using external Java components from processes or BPM Objects, you must include them into the project catalog. When you catalog a component, you are gathering all the necessary information that Studio needs in order to call and execute it at runtime.
Using Java Components
Follow this guidelines when using Java components on you BPM projects.
Versionable Java Libraries
External Resources of type Java Class Libraries can be defined as versionable or non-versionable to define how the Engine handles the library at runtime.
Mapping Java to BPM Components
This section explains how Java types are presented as PBL types when cataloged.

Parent topic: External Components