Imported Commands/Functions Fail When Called Out in Other WLST Scripts, After Customizing WLST (Doc ID 2953985.1)

Last updated on AUGUST 09, 2023

Applies to:

Symptoms

While attempting to use the functionality of Customizing WLST to make global Functions for other WLST scripts
that import and call these functions it fails on the functions imported.

This is documented here:

https://docs.oracle.com/en/middleware/fusion-middleware/12.2.1.4/wlstg/using_wlst.html#GUID-EDBA9BD8-2161-45A1-B09C-AE3C12879BAD
Table 2-6 Customizing WLST

Based on the document reference, it is expected that to import the customized WLST scripts placed in WL_HOME/common/wlst
or WL_HOME/common/wlst/lib, that they would be able to be called and used within other WLST Scripts by importing them,
then calling the functions from within.

The issue can be reproduced at will with the following steps:
1. Create a Python script that defines a common, often used function/command.
2. Place this script under $WL_HOME/common/wlst(Windows: %WL_HOME%\common\wlst).
3. Create another WLST script that has an import statement calling the first Python script and calls a function from this first script.
4. It fails with a general error stack "Problem invoking WLST - Traceback (innermost last):" which makes reference to the function in the first script.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.