Reputation: 13
in SOA suite 12c, I am running a sample OSB WLST script which has from com.bea.wli.sb.security.management.configuration import ALSBConfigurationMBean but getting an import error as no module named security, have added all the jars from %OSB_HOME%/lib/modules/.jar and %OSB_HOME%/lib/.jar, but still getting the same import error, any idea how to resolve this, also could you please help on this query, is it possible to select/attach the OWSM policy to a proxy service using the wlst script, if so please advice how it can be achieved?
Thanks for the help.
Upvotes: 0
Views: 1512
Reputation: 2253
As far as classpath goes, the classpath I use to call WSLT is:
${weblogic.home}/server/lib/weblogic.jar:${osb.home}/modules/*:${osb.home}/lib/alsb.jar:${osb.home}/lib/sb-kernel-wls.jar:${osb.home}/lib/sb-kernel-impl.jar:${osb.home}/lib/sb-kernel-api.jar${osb.home}/lib/modules/*:${osb.home}/lib/transports/*
(replace with windows-style ;
path separators if required)
is it possible to select/attach the OWSM policy to a proxy service using the wlst script, if so please advice how it can be achieved?
Personally, I'd extend Configurator so I could add it to the sb-jar, preferably before it goes into a Maven repository. I believe I've mentioned something similar in a question you asked previously.
Upvotes: 0