Problem in deploying Custom action block in 12.0

[Former Member]

Hi,

I have succesfully deployed a custom action block in 12.0 server.

But I am not able to see its image in the panel.

Also I am not able to drag and drop it in any sequence block.

Please provide input ASAP.

Thanks,

Vishal Jadhav

[Former Member]

Hi

You can go through the following weblog:

Hope this may help you how to deploy the custom action block.

[Former Member]

Hi Vishal,

Have you tried restarting the instance? You may also want to try clearing the Java Web Start Cache.

Regards,

Diana Hoppe

[Former Member]

Hi,

I am using MII 12.0. So no need to restart the server.

Also as I am deploying the action block from a system other than mII server, So I cant restart the server.

I have am able to deploy the action block on server and I can see that in the list.

But i cant see its image.neither I able to use it.

Thanks,

Vishal Jadhav

[Former Member]

Were there any errors in the log?

[Former Member]

Hi Vishal

I had deployed the action block from a system other than mII server, but i had restarted the server.I have worked on 11.5

You have written that for MII 12.0, we no need to restart the server.

I want to know why?

[Former Member]

Hi Vishal, how are you doing there.

Have you signed the Jar that you build for your custom actions.

Try with the unsigned version of you jar.

Regards

Rupesh

[Former Member]

Hi Rupesh,

I am fine yaar.

I have signed the jar file and done every thing that is needed.

Also I have successfully deployed an action block and its working fine.

But in other case I am able to deploy the PDF creater but I cant see its image .Also I not able to use that action block.

Also the earlier action block which I have successfully deployed works on some system but not on other. We have drop that idea and working on some work around it.

Manisha,

In 12.0 we can deploy the action from any client system.

We never directly copy paste the code on server. Instead we use a wizard from client system.

Thatu2019s why we didnu2019t need to restart the 12.0 server.