My Oracle Support Banner

Custom Automation Plug-in with Custom XSD in optimized mode implemented and deployed is giving error during provisioning "Cannot create automator" (Doc ID 1500158.1)

Last updated on MARCH 03, 2019

Applies to:

Oracle Communications Design Studio - Version 3.1.3 and later
Information in this document applies to any platform.


I'm trying to utilize the "Custom Plug-in" tab on an Automated Task in Design Studio.
As reference I'm using the "Database Plug-in" included in the SDK.

I have created my own XSD file which extends the base complexType Implementation of the AutomationMap.xsd - see isEmailPlugin.xsd
I have created an Automator which handles the parameters and send email etc.
In design studio, I should now be able to add the xml into the Custom Plug-in tab and so send parameters to the Automator.

Firstly - I had this set up in OSM 7.0.1 and worked perfectly!
Now, we've restarted the project and installed a new/fresh OSM 7.0.3
When I deploy the cartridge, the returning message is successful (first issue)
But when looking at the log - the automationmap is not loaded - therefore the automation ejb is not created, and this results in an endless loop when trying to lookup the ejb on an OSM Order.
It seems like the additional .xsd is simply not found when deploying to weblogic.




To view full details, sign in with your My Oracle Support account.

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

In this Document

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