What is end point we have use to get job key form onpremises orchestrator

Help Orchestrator
1

Hi all,

While using the endpoint to get the job key, I am getting the XML format instead of the JSON format. This is the exception I am getting.
("deserialise json: unexpected character encountered while parsing value: <. path ‘’, line 0, position 0).
So can I know the exact endpoint?

Thanks,
Elluru

2

Hi @Elluru

Welcome to Community!!

Please check on this thread

I hope it helps!!

3

Hi Irtetela,

Thanks for the reply.

I have done exactly as your image suggests. Even though I’m getting the same exception.

And the endpoint I have used is

[orchestator url] [AccountLogicalName]/[TenantLogicalName]/odata/Jobs? $filter=ReleaseName eq ‘ProcessName’&$orderby=StartTime desc

img

Thanks
Elluru

4

@Elluru

Welcome tot he community

can you print the response and check if it is porper

and which activity are you using ? is it http request? if so did you give application/json in accepted format?

cheers

5

Hello Sir,

Imag2
Imag2838×443 44.9 KB

This is the output response I’m getting. Yes, I’m using an http request, and I have given application/json.

Thanks,
Elluru

6

@Elluru

Can you please try using orchestrator http request activity please…even using http it shpuld work…but need to check what is the difference…did you happen to check what is the response type ? Is it application/json in your properties?..also if using from UiPath we generally us it using orchestrtaor http request which does not need authwntication as well and we just need to provide the relative urla nd not tbe complete as well

A detailed step by step guide

Cheers

7

Hello sir,

Yes,the response type is application/json. My main requirement is to get logs for each process from the on-premise orchestrator. And in one folder, I have three processes.

Thanks ,
Elluru

8

@Elluru

Please follow the link it has detailed steps…please verify if everything is same

cheers

9

@Elluru

This looks like a possible reason for response being wrong

Cheers

10

Hello sir,
Yes, there is a mistake in the endpoint. But I need to know AccountLogicalName and TenantLogicalName from the on-premise orchestrator to get “JOB KEY,” and I’m using this endpoint.

“{orchestratorurl}/[AccountLogicalName]/[TenantLogicalName]/odata/Jobs? $filter=ReleaseName eq ProcessName&$orderby=StartTime desc”

Because I don’t know the account logic name and tenant logic name, the result is in XML format.

11

@Elluru

For on prem
You dont need to provide those i guess…did you try without them?

Also did you try to check the end point from swagger…it eould give you the full endpoint you need to use…

<orchurl>/swagger/index.html

Cheers