Application Interface Services (AIS) is the magic portal for exposing JD Edwards applications and data. That includes orchestrations. We shared a simple diagram in a previous post. Now let's go deeper into EnterpriseOne architecture to uncover the best plan for installing AIS and Orchestrator on your system.
JAS/HTML instances for development and production architecture
In a general EnterpriseOne architecture plan, the AIS server points to the main JAS/HTML instance. This design works well for development and prototyping, where usage is limited. However, moving to production, you should add a separate JAS/HTML instance pair for AIS.
When a JAS or AIS/orchestration REST call launches an AIS request, it uses a new JAS session. If the AIS instance is pointing to the main JAS/HTML instance, it might double—even triple—the number of web sessions and tax the system. Fortunately, EnterpriseOne architecture for Orchestrator is flexible so you can add the second instance.
Architecture with multiple AIS/JAS instance pairs
Businesses taking full advantage of orchestration might dedicate multiple AIS/JAS instance pairs in their architecture plan. Consider how the following applications impact resources:
- UX/One, Task, or EnterpriseOne Search can increase AIS/JAS activity for the graphs and searches performed.
- IoT requests, large volume transactions, and scheduled jobs all generate a high orchestration count.
- Quartz Scheduler running within AIS uses more memory, CPU, and resources to launch orchestrations/notifications.
Notifications and Watchlists are good candidates for a separate AIS/JAS instance if performing large scale monitoring. Likewise, mobility users might benefit from a separate AIS/JAS instance for different timeouts.
Orchestrator insights for architecture
- Orchestrator Studio is considered a development tool. Typically only admin access/connections are permitted to development or prototype AIS instances. You do NOT need a separate Classic Orchestrator Studio instance for production if recommended change management practices are in effect. Tools 9.2.4.x may be an exception. If you must use the production Orchestrator client, then another REST client, such as SoapUI/Postman, is recommended. Do not change orchestrations in production.
- Treat orchestration UDOs like code and use existing change management practices. Since UDO web objects don't need a package build/deployment, they won't interrupt the business. Generally, you can promote, share, and apply security to release the functionality.
- The typical Classic Orchestrator Studio WebLogic ADF instance can handle 20–30 users assuming Java memory is allocated correctly. It may exceed 30 with some XML setting changes or create another Orchestrator Studio instance/server. Best yet, upgrade to Tools 9.2.4.x to eliminate the need for an ADF instance altogether.
With the right plan in place, you are ready to install Orchestrator Studio or modify your current EnterpriseOne architecture for a better fit and performance. Continue to review My Oracle Support, E1 documentation, LearnJDE sites, and this ERP Suites blog for updates that can save you time and trouble.
Need help getting started? Click to learn about our Orchestrator Services. ERP Suites is a JD Edwards Gold Partner and winner of the 2019 Oracle Distinguished Partner Award for Successful Adoption of Orchestrator.
Topics:
