Unsigned jar error when importing custom actions in MII 12

[Former Member]

Hi,

When testing a migration from 11.5 to 12 we have come across a problem when importing custom action blocks into MII. I've followed the migration guide for custom action blocks but i'm continually getting an error stating that the jars are unsigned. Can someone please provide some advice on how to address this issue.

Many thanks,

Nicholas

[salvatore_castro]

Nick,

I like the post...

If you get this error it's due to the Java Security Policy that is generated by the workbench.jsp page to launch the MII Workbench Java Web Start application and is caused by the fact that your custom action is accessing an internal library. To sign your jar you need create a key store and generate a certificate from the key store then use the Jarsigner tool to sign your action JAR:

• jarsigner -verbose -certs -keystore C:\<Path>\<MyKeyStore> -storepass <KeyPassword> <MyCustomAction>.jar <MyKeyStoreName>

• To Verify that it is signed:

• jarsigner -verify -verbose <MyCustomAction>.jar

Hereu2019s a good reference URL from Sun:

[http://java.sun.com/developer/technicalArticles/Programming/jnlp/|http://java.sun.com/developer/technicalArticles/Programming/jnlp/]

• Just do a search on the page for u201Cjarsigneru201D

Hope this helps,

Sam

[jcgood25]

There were some custom action changes between 11.5 and 12.0, which will require modification on your end. You mention following the migration guide for custom action blocks - is this the one located in the 12.0 sample projects download area - the custom action developer kit?

Regards,

Jeremy