Page 2 of 2 FirstFirst 1 2
Results 11 to 13 of 13

Thread: Orchestrator versus DSI

  1. #11
    To My prior project experience, Orchestration very depends on the Server Request manuplation. but even if it provides the custom service request made in Groovy, it still has some limit on flexibility, and the perforamnce is also you have to consider about Json. For example, do the same PO receipt for couples of lines,, BSSV&BSFN will be more ideally than JSON in response according to our testing. Besides Orchestration counts on JAS front end design, it is for high level solution, Whereas , BSFN is for the lowest level development, which can provide much lower level transaction control in. Orchestration of course has advantage on the fast implementation ,So that is all you need to consider.

  2. #12
    Member nkuebelbeck's Avatar
    Join Date
    Mar 2012
    I'd sooner put your eggs into the AIS/Orchestration basket. it's powerful stuff.
    E1: 9.2 | TR: | JAS: WebLogic | ES: OS400
    DB: DB2 | WebDev Client: Win7Pro (64 bit), VS 2013

  3. #13
    You might want to look at this informative thread:

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
The legal restrictions and terms of use applicable to this site are available here.
Use of this site signifies your agreement to the terms of use.
JDELIST is NOT affiliated with JD Edwards® & Company, Oracle or Peoplesoft. Contents of this site are neither endorsed nor approved by JD Edwards® & Company and, or Oracle.