E9.2 Orchestrator - Creating Rest API using Connector

[nasur.mca]

Dear All,

I have created and published a orchestration to create item in item master and its working fine locally.

I want to generate service file to call it from outside.

I am new to this orchestrator development .

Can anyone please help me how to create a connector file using rest api for the below .

Thanks & Regards,

 

[lfurino]

You can think of the Orchestrator as an API factory. Every time you build an Orchestration you are really creating another REST API on the AIS server. In other words, your Orchestration is already published and available to be called externally by sending a REST request to https://{AIS Server ip or name}:{AIS Port}/jderest/v3/orchestrator/{orch name}

Note: until you share the orchestration and its components, you can only call it with your credentials.

 

[DaveWagoner]

You can think of the Orchestrator as an API factory. Every time you build an Orchestration you are really creating another REST API on the AIS server. In other words, your Orchestration is already published and available to be called externally by sending a REST request to https://{AIS Server ip or name}:{AIS Port}/jderest/v3/orchestrator/{orch name}

Note: until you share the orchestration and its components, you can only call it with your credentials.

This is perhaps what I'm running into. I want to use the method described in this doc to add a text media object attachment using rest API call https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=2oaevi5es_4&id=2689626.1 but am doing my testing on unpublished orchestrations and components. The API call works when I hard code basic auth credentials into the API call connector but doesn't when I want to try to emulate the API call using the same credentials as the original orchestration. (and don't get me started on trying to pull the token via orchAttr, then passing it to the API call via body).

 

[eydeak]

You do need to authenticate to JDE when you call the orchestration. If you have access to the "JD Edwards EnterpriseOne Application Interface Services Server Reference Guide Tools Release 9.2", Chapter 4 talks about AIS authentication. There are different types. We get an authentication token that is then passed in as an input to subsequent orchestration calls. So, our caller follows this pattern:

https://{AIS Server ip or name}:{AIS Port}/jderest/v2/tokenrequest
invoke 1 or more orchestrations, passing in the token as the first input
https://{AIS Server ip or name}:{AIS Port}/jderest/v2/tokenrequest/logout

When you make the orchestration call, you include the token as the first input. This is an example of the json input structure for a sales order inquiry orchestration we use:

{
"token": "",
"SalesOrderCompany_in" : "",
"SalesOrderNumber_in" : "",
"SalesOrderType_in" : ""
}

Regards,
Ellen

 

[DaveWagoner]

You do need to authenticate to JDE when you call the orchestration. If you have access to the "JD Edwards EnterpriseOne Application Interface Services Server Reference Guide Tools Release 9.2", Chapter 4 talks about AIS authentication. There are different types. We get an authentication token that is then passed in as an input to subsequent orchestration calls. So, our caller follows this pattern:

https://{AIS Server ip or name}:{AIS Port}/jderest/v2/tokenrequest
invoke 1 or more orchestrations, passing in the token as the first input
https://{AIS Server ip or name}:{AIS Port}/jderest/v2/tokenrequest/logout

When you make the orchestration call, you include the token as the first input. This is an example of the json input structure for a sales order inquiry orchestration we use:

{
"token": "",
"SalesOrderCompany_in" : "",
"SalesOrderNumber_in" : "",
"SalesOrderType_in" : ""
}

Regards,
Ellen

Good info Ellen thanks! In our case, the REST API call to the very AIS on which the orchestration is running on is just an /file/addtext endpoint call. I assume that I need to get a NEW token as opposed to the one on which the orchestration is already running. We're hitting a case where trying to use the current token on this API call invalidates the current session.

Of course, I wouldn't need to do any of this if the process recorder (or even the form request orchestrator object) would allow me to add a media object through the health and safety interface. I might end up submitting an enhancement request.

 

[DaveWagoner]

Good info Ellen thanks! In our case, the REST API call to the very AIS on which the orchestration is running on is just an /file/addtext endpoint call. I assume that I need to get a NEW token as opposed to the one on which the orchestration is already running. We're hitting a case where trying to use the current token on this API call invalidates the current session.

Of course, I wouldn't need to do any of this if the process recorder (or even the form request orchestrator object) would allow me to add a media object through the health and safety interface. I might end up submitting an enhancement request.

Larry Furino, Mr Orchestrator, set me on the right path. I had created a brand new connection to call the REST server and because of that needed to figure out auth. But selecting "Local AIS Connection" passes thru the auth as if the rest call was just another step on an orchestration, which was ultimately all I was really after.

Thanks Larry and all! @lfurino

 

[lfurino]

Larry Furino, Mr Orchestrator, set me on the right path. I had created a brand new connection to call the REST server and because of that needed to figure out auth. But selecting "Local AIS Connection" passes thru the auth as if the rest call was just another step on an orchestration, which was ultimately all I was really after.

Thanks Larry and all! @lfurino

Good info Ellen thanks! In our case, the REST API call to the very AIS on which the orchestration is running on is just an /file/addtext endpoint call. I assume that I need to get a NEW token as opposed to the one on which the orchestration is already running. We're hitting a case where trying to use the current token on this API call invalidates the current session.

Of course, I wouldn't need to do any of this if the process recorder (or even the form request orchestrator object) would allow me to add a media object through the health and safety interface. I might end up submitting an enhancement request.

@DaveWagoner There is an attachment component now in 9.2.6 which makes this process much more intuitive without the need for a REST call at all. I should create a youtube video to demo that, but I will definitely show you how to use it in our training class. In earlier versions, you can use an OpenAPI call which is like the REST connector but it predefines all of the information for you.