Use Script from External Package, IDM v8.0

[brandonbollin]

I have a script that is public in the com.sap.idm.provisioning.engine package but I cannot figure out how to use it in a job that I'm building in my custom package. How do I reference scripts from other packages?

I've combed the IDM documentation but I'm coming up empty on how to perform this process. Thanks in advance IDM experts!

[brandonbollin · Accepted solution]

When we originally did this installation, it was SP5. When we started having this issue, we were advised to upgrade all components to SP6. We thought we did that but SAP support connected to our system and discovered that, while most components did indeed get upgraded to SP6, a couple were missed and still on SP5. They told us what to install and we did this. Now the problem is solved.

[devaprakash_b]

Hi Brandon,
You can reference or link the public script available in other packages as below

1. Go to the scripts tab in the job, right click and select Add Link To Package Script

2. Select the package, in which script is located and select the script and click on ok, the script would be linked sucessfully.

Regards,

Deva

[brandonbollin]

When I try to do that, I get an Eclipse error. What could be happening? Have you ever seen this before?

eclipse.buildId=4.7.2.M20171130-0510
java.version=1.8.0_171
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.java.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.java.product


com.sap.idm.dev-studio-userinterface
Error
Tue May 22 08:34:28 EDT 2018




java.lang.NullPointerException
	at com.sap.idm.ic.rcp.handlers.menudialogs.LinkToPackageScriptDialog.createDialogArea(LinkToPackageScriptDialog.java:112)
	at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:768)
	at org.eclipse.jface.window.Window.create(Window.java:426)
	at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
	at org.eclipse.jface.window.Window.open(Window.java:783)
	at com.sap.idm.ic.rcp.commands.JobScriptsContributor.createNewExternal(JobScriptsContributor.java:345)
	at com.sap.idm.ic.rcp.commands.JobScriptsContributor.widgetSelected(JobScriptsContributor.java:171)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4428)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4238)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3817)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1499)

[devaprakash_b]

What is the version of your eclipse idm plugin and idm 8.0 support pack (SP) ?

Can you please check the error details in the developer traces logs available in nwa -> troubleshooting -> logs and traces -> log viewer, you might find more information regarding the error.

Regards,

Deva

[brandonbollin]

This is a brand new install in a DEV environment so we're on the latest SP for IDM, SP6, and the IDM plugin is 8.6.2.

[brandonbollin]

As for the NWA Log Viewer, we've actually submitted an OSS ticket and we're getting our tech a WTS connection. We're also having an issue where we cannot create custom processes and make the public. When we right click on a process and select Make Public, nothing happens. Now we're having this issue too. It just seems like something isn't working right with our install.

I've been developing for IDM for 6 years now. This is my first, from scratch IDM v8 install and it's not going well. Everything went along just fine while we were installing and following the SAP documentation. I have no idea why these simple things don't work. What could have been done incorrectly?