WLST Script To Import Jar File Into OSB Fails With ClassNotFoundException

(Doc ID 2156419.1)

Last updated on FEBRUARY 11, 2017

Applies to:

Oracle Service Bus - Version and later
Information in this document applies to any platform.


On : version, OSB Core Functionality

WLST script to import jar file into OSB fails with ClassNotFoundException

The WLST script used to deploy in OSB 12.1.3 fails to deploy to OSB 12.2.1. Issue seems to be same as in Doc ID 2104770.1 .

Starting from 12.2.1 the classpath is not to be amended via the product-specific wlst.cmd/sh command. Instead, one single wlst.cmd/sh command is provided, which relies on plugins to amend the classpath as required for the installed products. It is OSB WLST plugin's responsibility to set it when running WLST scripts.

The classpath for the OSB WLST plugin is (as per the manifest in servicebus-client.jar):


It was made it work manually by adding the following jar:


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