Plugin error message jiwa.

[Mike.Sheen]

thank you very much for the reply.
I am still getting an error unfortunately.
Please see attached image.
Thank you.
Cheers

You need to ensure that the Jiwa REST API plugin is enabled.

One of the changes I made was to add a plugin reference to the REST API plugin so that the GetManager() extension method could be used - and if that plugin is not enabled, then it won't know about that extension method.

Another possible cause of that specific error is if the REST API plugin is enabled, but you have an older version.

You should use the REST API version which ships with the SR - refer to the Service Release notes on how to obtain that.

[JuiceyBrucey]

I am currently on SR 16, this change is for SR 17.
Are you saying I must now upgrade to SR 17 as well?

[SBarnes]

Not necessarily, as Mike stated ensure that the RST API plugin is enabled and that its version number matches the version number of the one in the zip file that is mentioned in the screenshot from the release notes Mike posted.

You could also set the execution order of your plugin to be higher than that of the REST api to ensure the REST API is compiled before your plugin compiles.

[Mike.Sheen]

I am currently on SR 16, this change is for SR 17.
Are you saying I must now upgrade to SR 17 as well?

No. As Stuart pointed out, just follow the instructions to get the REST API from SR16. I showed you a screenshot from the SR17 docs page, but the same applies to SR16, SR15, SR14 and so on.

[JuiceyBrucey]

Thank you for replies.
So I have been successful in importing the revised ToDo plugin onto my test server.
I now want to import it onto the live server. There are about five terminals working on this JIWA installation at the moment.
If I import the REST API and ToDo plugins onto the server while people are working on them, will that cause any issues or loss of data?
What about restarting the API, will that cause any loss of data or issues for people using the system right now?
Thank you

[Mike.Sheen]

If I import the REST API and ToDo plugins onto the server while people are working on them, will that cause any issues or loss of data?

It won't cause any loss of data, the only potential problem is if your REST API service is configured to use the same username as another person or process that is using Jiwa, currently logged in on the same physical machine, your service may have trouble compiling the plugin on service start as the assembly won't be able to be overwritten as it is loaded and in-use by the other process.

Our guidance is to have a user in Jiwa specifically for your service(s), so this sort of conflict is avoided.

What about restarting the API, will that cause any loss of data or issues for people using the system right now?

No, no data loss and if they're using the Jiwa application and not anything using the REST API then they won't even notice. Only external systems and not the Jiwa application itself would be impacted by the restart of the REST API, and even then it would only be a minute or two of disruption.

[JuiceyBrucey]

Ok, tried on the live server and got the error attached.
I think its time to get one of you guys to do it.
I have the green light for that.
It is taking too long and I have tons of other work that needs to be done.
can someone contact me via private message or something?

[Mike.Sheen]

Ok, tried on the live server and got the error attached.

That error indicates the REST API plugin is an older version - see my previous post on how to get the latest version from the installed SR. It may be the live server is on an older SR version which your plugin is not compatible with.

can someone contact me via private message or something?

You need to log a helpdesk ticket to engage us directly for support.

[JuiceyBrucey]

Ok, will give it one more shot.
I followed the instructions, but I will try again in case I missed something.
If no result, I will lodge a ticket.
Thank you.
Cheers

[Mike.Sheen]

Ok, will give it one more shot.
I followed the instructions, but I will try again in case I missed something.
If no result, I will lodge a ticket.
Thank you.
Cheers

Also check the REST API plugin is enabled on their live server - that can also cause that error message.