calling a user defined job externally

[reddotrich]

In the RQL Doku manual it says that we can call a User-defined job,

<IODATA loginguid="[!guid_login!]">
<ADMINISTRATION>
<TASK action="start" guid="[!guid_task!]" />
</ADMINISTRATION>
</IODATA>

we have tried this using the user that normally calls it from within
RedDot, an account that was set up specially for it, but we keep
getting No Rights error message, what rights are needed to call a user
defined job externally? We are able to call all other RQL commands
without an issue. The call is being made from a WCF service.

Cheers

Rich

[Henry Lu a.k.a. Javahand]

Rich--

The CMS RQL Service aborts the job when the job specified user happen to be in session.

Try to call the job using a "ghost" user account.

Henry Lu

[kimdezen]

... and always make sure that you close the 'ghost' user session when
you are done with your RQL!!!!

Cheers,
Kim


On Jul 9, 1:29 am, "Henry Lu a.k.a. Javahand" <javah...@gmail.com>
wrote:

> Rich--
>
> The CMS RQL Service aborts the job when the job specified user happen to be
> in session.
>
> Try to call the job using a "ghost" user account.
>
> Henry Lu
>

[reddotrich]

Thanks for the suggestions, but I am not 100% sure what you mean by a
ghost user, is it some type of system account that you can't log into
the system normally with? Or is it something else? The user we are
using at the moment was created specially for running jobs and does
nothing else, although you could log in with it if you wanted to. How
would I set up a ghost user?

Cheers for your help

Rich

> > > Rich- Hide quoted text -
>
> - Show quoted text -

[RedDot in Toronto]

You basically make a user account only used by plugins or user defined
jobs. It should have the proper credentials.

[Julio Canadas]

Depending on the case you may also be able to reuse the active user's session by using info place holders to get their login guid / session key. In this case you don't need to worry about logging them off.

Keep in mind the ghosts use a license slot while active (why you MUST log them off) which may or may not be a problem depending on how long it takes them to complete their task and how many licenses you have available.

RedDot in Toronto wrote:

You basically make a user account only used by plugins or user defined
jobs. It should have the proper credentials.

On Jul 9, 5:00 am, reddotrich <Richard_Yo...@next.co.uk> wrote:
  

--

---

Julio Canadas - Senior Developer - Oshyn, Inc. - Powering Innovation ™
Direct 213.784.1332 | Cell (593) 994.05208 | Fax 213.612.0291  | Web www.oshyn.com

Oshyn's latest: lstudio.com | neamb.com
Follow Oshyn on...  Twitter  &  LinkedIn

[reddotrich]

Thanks guys, we have now got it working, it was missing the server
manager credentials, strange that it did not need them when it was
called from internally. Thanks for the tip about the licenses, we
will need to keep an eye on that.

Cheers all.

Rich

> ------------------------------------------------------------------------
>
> *Julio Canadas - Senior Developer - Oshyn, Inc. - /Powering
> Innovation ^(TM)/*

> Direct 213.784.1332 | Cell (593) 994.05208 | Fax 213.612.0291  |
> Webwww.oshyn.com
>

> Oshyn's latest: lstudio.com <http://www.lstudio.com> | neamb.com
> <http://www.neamb.com>
> Follow Oshyn on...  Twitter <http://www.twitter.com/Oshyn_Inc>  &  
> LinkedIn <http://www.linkedin.com/companies/oshyn-inc.>- Hide quoted text -