How to add on-prem Orchestrator as package source when not connected

Help Activities
, ,
1

Hi

Can I define an on-prem Orchestrator as a secondary Package Source, when connected to a different tenant?

I am connected to a Cloud Orchestrator/Tenant, and would like to add my on-prem Orchestrator as a Package Source, so that I can use the local libraries there.
Is this possible? And how to authenticate?

I have tried defining the URL for the On-Prem Orchestrator but I am getting the following error:

on prem package source
on prem package source725Ă—133 8.9 KB

Regards
Soren

2

I havent tried this myself, but if you check the following when you are connected to the On Prem Orchestrator, then check to see if you can ping the URL its gives as the package feed, as all these URLs and locations need to be reachable.

Its possible Studio itself does some voodoo under the hood to authenticate to certain feeds or sites, I am not sure.

Its abit of a weird requirement to be honest.
I think a better solution would be to define another feed, which can be reached by both the On Premise Robots and the Cloud Robots, and publish your stuff there?

The image shows a software interface for managing package sources, displaying both default and user-defined package sources with options to add, update, and organize them. (Captioned by AI)
The image shows a software interface for managing package sources, displaying both default and user-defined package sources with options to add, update, and organize them. (Captioned by AI)1286Ă—913 38.2 KB

1 Like
3

Hi @Jon_Smith

Thank you for your suggestion - it worked :grinning_face:
Initially I only had the basic URL for our on-prem Orchestrator, but when adding the entire URL, including the ID-part, it worked.

It is quite a unique scenario/requirement.
It is for a live demo at a conference, where I would like to use Document Understanding, but base its contents (documents) on data that our participants can relate to.

This data is fetched through API-calls to a digital document platform, for which we have made several libraries (on the on-prem), and I would like to show them how easy they can build something that works.

By combining the two tenants, I can showcase “new” features, but do so with libraries that are already available to all our developers/citizen developers.

Regards
Soren

4

Wahey! Glad it worked, and good for me to remember that the feed is public like that.

Thanks for sharing the context.

JS

1 Like
5

Yea but perhaps it is only “public” in the sense that my machine has already been connected to the tenant.

I am using my “program” to switch between the two tenants, from the same machine:

It could however be fun to test if others can connect through “my” URL - I will have to check that out.

Update:
It looks like the URL is unique - this screenshot is from another developer’s machine, when trying to add my URL as Package Source.

asd
asd509Ă—152 9.15 KB

6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.