msouterblight1a
Member
Hello,
Excuse my ignorance on this, but I don't really know the development side of Orchestrator studio, but I had some questions. I had previously installed Orchestrator studio for DV, as it is my understanding that only 1 install of the studio was needed and once the orchestrations were created, they were promoted as UDOs and the executed directly on the AIS server. I assume they would be called using the AIS endpoint, correct? We recently had a 3rd party perform a salesforce to JDE integration with Orchestrator, and they said a PD install of Orchestrator Studio was necessary for this to work. I understand that Orchestrations can be run directly from studio now, but I thought that was more for testing and debugging purposes, not to be used as the integration point. Am I wrong? Is this the standard way of calling integrations now, directly through Orchestrator Studio??
Matthew
Excuse my ignorance on this, but I don't really know the development side of Orchestrator studio, but I had some questions. I had previously installed Orchestrator studio for DV, as it is my understanding that only 1 install of the studio was needed and once the orchestrations were created, they were promoted as UDOs and the executed directly on the AIS server. I assume they would be called using the AIS endpoint, correct? We recently had a 3rd party perform a salesforce to JDE integration with Orchestrator, and they said a PD install of Orchestrator Studio was necessary for this to work. I understand that Orchestrations can be run directly from studio now, but I thought that was more for testing and debugging purposes, not to be used as the integration point. Am I wrong? Is this the standard way of calling integrations now, directly through Orchestrator Studio??
Matthew