Skip navigation

041014_0529_ICT2[1].jpgJD Edwards has published a new performance white paper on the JD Edwards EnterpriseOne Application Interface Services (AIS) Server using Oracle ADF application and IoT orchestrations.


The tests described in the white paper demonstrate that the AIS Server is a low consumer of memory and CPU resources, and is therefore a viable technology to leverage add-ons to JD Edwards EnterpriseOne such as ADF applications and IoT orchestrations.


Read this new white paper here. You can also access the white paper from > White Paper Index > Performance.

Seeing is believing! – Watch two new videos to get a preview of the innovative capabilities soon to be delivered with UX One. Learn how to use one of the features that is leveraged by UX One – Form Personalization. How they can modify attributes on a page without having to customize the application.

AdvisorWebcast.pngYou may have attended on August 24th , 2016, the Advisor Webcast on JD Edwards EnterpriseOne General Ledger Integrity Issues. Or maybe you saw the MOSC thread on the webcast,


Whether you have or haven’t, I thought that it is an important enough topic to discuss on the best practices here in the blog as well.


Best Practices :

  • Designate only a group of Power Users who can update GL system constant(P000),Business Unit Master(P0006),Company Names and Numbers(P0010) and Account Master(P0901).This Users should not have a security set a BU/Company Level.
  • All Accounts which are meant for automatic entries(Example –AR/AP Trade Account) should always have a posting edit code of "M" and should not be removed.
  • Run GL Integrity as often as possible.
  • Run Integrity reports after office hours. Example - Repost Report(R099102), which takes a lot of system resources.
  • Post all batches (R09801) before running any integrity report.
  • Save the PDF Report Output for Integrity Reports such that it can be used for research in future.
  • Verify the Report Output for R09801 and make sure that the Dr and Cr entries are correct.
  • Create a central Contact to report, research and correct integrity issues at the earliest.


For more detailed information, you can play the recording of the webcast or review a PDF of the presentation. To find these:

  1. Go to knowledge article Advisor Webcast JD Edwards EnterpriseOne Schedule and Archived Recordings (Doc ID 1450327.1)
  2. Click on the tab named ‘Archived 2016’
  3. Scroll down to August 24.
  4. Then either click on the webcast title ‘JD Edwards EnterpriseOne General Ledger Integrity Issues.’, or on the recording or PDF links for this webcast.

JDE IOT OrchestratorStudio is a independent ADF Application which deployed on Weblogic Server and access via a URL.


OrchestratorStudio helps in designing IOT Orchestration XMLs which includes CrossReferences,Orchestrations,Rules,ServiceRequests,WhiteLists


Step 1.  Download and install ADF Runtime. Refer KM document - E1: ADF: Installation of ADF Runtime for IoT (Doc ID 2126884.1)


Step 2.  Create new Weblogic Domain with ADF Runtime and EM (Enterprise Manager Console).


Step 3.  Download and extract OrchestratorStudio related files. Follow KM document - E1: IOT: How To Download Orchestrator Studio Files (Doc ID 2109323.1)


Step 4. Login into Weblogic Admin console.


Step 4.1 - Click on Lock & Edit and navigate to Environments >Servers Click on NEW button for creating J2EE container.


Step 4.2 - Enter J2EE container name and valid/available port number and click on Finish



Note- Do not start J2EE container at this point


Step 5. Login into Weblogic EM console (http://<servername><port>/ ) , Select J2EE Container name and click on "Apply JRF Template".


   Confirmation message -



Step 6. Start Command prompt and navigate to WebLogic server path - C:\Oracle\Middleware\Oracle_Home\wlserver\server\bin and run setWLSEnv.cmd to setting-up WLS Environment variable.




Step 8. Navigate to folder where you have extracted OrchestratorStudio related files. this folder folder should have following files -


1. OrchestrationStudio.ear


3. build.xml


Step 9. Edit file using text editor and update Weblogic Server host name , WLS Admin Server port, J2EE container name and save it.


Snap14.jpg - Weblogic Server Host name

  weblogic.server.port - Weblogic Server's Admin Sever port

weblogic.deploy.targets - J2EE container name where OrchestratorStudio Application will be deployed.



Step 10. Now navigate to OrchestratorStudio folder using same command window ( this will keep WLS environment path available for the session ).


Step 11. Run command ant deploy



   Enter WebLogic Server's Admin Username and password when prompted on screen.



   Deploy Script will connect to WebLogic Admin console and will deploy OrchestrationStudio.ear file to defined J2EE container.



Step 12.  Login into Weblogic Admin console and start J2EE container for OrchestrationStudio.


Step 13. Once J2EE container is started , navigate to "Deployment" section and you should have below structure.-



Step 14. Now expand OrchestrationStudio and select Testing tab  to get URL for deployed OrchestrationStudio application -



Access OrchestrationStudio using URL - http://<ServerName/IP>:<port>/OrchestratorStudio/faces/index.jsf


Note - You may need to append  /faces/index.jsf at the end of URL




Step 15. Enter AIS Server URL under OrchestrationStudio. it will be used for Login and integrating AIS Test Client within OrchestrationStudio.



                          JDE IOT- OrchestratorStudio


Filter Blog

By date: By tag:

Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see for instructions.