I have tried to do the JDBC provisioning using the external Jar Upload in the JDBC Source. But i am getting below error while trying to call the provision method of the TestDemo class. I have made sure that i am passing correct Parameters to the method. The connector rule has “script”: “import sailpoint.services.rule.TestDemo; return TestDemo.provision(application, connection, plan);”
Error :
[“BeanShell script error: bsh.EvalError: Sourced file: inline evaluation of: import sailpoint.services.rule.TestDemo; return TestDemo.provision(application, . . . \u0027\u0027 : Attempt to resolve method: provision() on undefined variable or class name: TestDemo : at Line: 1 : in file: inline evaluation of: import sailpoint.services.rule.TestDemo; return TestDemo.provision(application, . . . \u0027\u0027 : TestDemo .provision ( application , connection , plan ) \n BSF info: JDBC Provisioning Adapter Rule at line: 0 column: columnNo”,“BeanShell script error: bsh.EvalError: Sourced file: inline evaluation of: import sailpoint.services.rule.TestDemo; return TestDemo.provision(application, . . . \u0027\u0027 : Attempt to resolve method: provision() on undefined variable or class name: TestDemo : at Line: 1 : in file: inline evaluation of: import sailpoint.services.rule.TestDemo; return TestDemo.provision(application, . . . \u0027\u0027 : TestDemo .provision ( application , conn… 0 column: columnNo”]
Note : This was working before when I uploaded for the first time for a different source. But now it is not working anywhere. Moreover I have renamed the Jar on every upload and waited for more than 5-10 mins for it to be published to the VA.
sudo docker exec ccg ls /opt/sailpoint/ccg/lib/custom
I saw the same error recently, and the jar was visible on the source and seemingly uploaded successfully but did not make it to the VA. Removing the previous jar from the source and reuploading it with a unique name solved that particular issue for us.
FYI, the External Jar method was really only necessary when SailPoint required all Rules to be approved before installing. Now that you can write/install Connector Rules directly using APIs, you can take the same code that would be in your External Jar and just install it as a Connector Rule.
some weeks ago, i had tried this external jar solution followed below link, however i got some strange issue that updated jar could not be picked up and it still loaded the original jar.
As @brad_grutsch mentioned, I had to change another JDBC rule, however it is struggling for debugging this way since it is bean file, not pure java file, could not verify in the local, I had to deploy it to the VA by printing different logs and searching key words each time, it consumed a lot of time…
so i would like to explore this external jar solutiona again. @nsorlien as your mentioned, how can you removed your previsous jar using command? Can we remove using some commands from our side?