Top 5 Takeaways from INFOCUS 2018
By Hari Karnati and Sarah Mills
If you were at INFOCUS last week, you were most likely consumed with an abundance of JD Edwards education, networking, and a vendor showcase that was buzzing! For those of you who weren’t able to make it to the conference (and for those of you who did, but couldn’t take notes fast enough!), our team has pulled together the key takeaways from the annual conference. As you review, keep in mind the following overarching themes from the event:
- Support of JDE E1 release 9.2 will continue until 2030, with a focus on continuous improvement and adoption
- Orchestrator, Operations Simplification, and UXOne continue to be hot topics
- “You Can Make It Happen” – Oracle’s philosophy empowering the Citizen Developer; the business analysts, non-developers and the end-users
Now that you have these themes in mind, here are the top 5 key takeaways:
5. Server Manager Enhancements
Server Manager enhancements that enable provisioning of a code current EnterpriseOne environment for customers on Power Systems with IBM i. Server Manager for JD Edwards EnterpriseOne enables administrators to easily provision, configure, and manage EnterpriseOne server components. The provisioning capabilities in Server Manager are expanded to include provisioning of Enterprise Server on IBM i and database server – IBM DB2 for IBM i with Application Release 9.2 update2 which includes all current enhancements, application patches and Tools Release 220.127.116.11. These capabilities are available from both the Server Manager UI and REST APIs and provide lowered TCO for setting up a JD Edwards EnterpriseOne environment on IBM I
4. UX One
JD Edwards continues to enhance the user experience through UX One by providing navigation capabilities on Analytic Components. Additional roles and their Analytic Components now provide drilldown and right-click options on context menus with a selection of applications that can be launched. This allows users to easily navigate from analytic graphical presentations to review and act upon detailed master data or transaction information.
UX One Analytic Components provide real-time, transactional information to JD Edwards end users in an intuitive and graphical format. Users are able to visually analyze current business conditions and more easily identify problems that need attention. Navigation from the Analytic Components allows users to quickly take action.
JD Edwards EnterpriseOne Orchestrator is a framework that enables Digital Transformation. There was added focus on Orchestrator and the released orchestrations out of the box to help customers adopt them. JD Edwards EnterpriseOne Orchestrator continues to provide significant functionality for automating EnterpriseOne transactions and interfacing with external systems. The following recent enhancements to Orchestrator further expand its capabilities:
- Process Recorder allows a user to create a form service simply by recording the step-by-step actions directly in the EnterpriseOne applications. For example, a user could create a form service to return the status of equipment by turning on the Recorder, launching the Work with Equipment Master application, querying on a piece of equipment, selecting the equipment, and turning off the Recorder. The user can choose what information, in this case equipment status, to return from the form. The recorded process can be a single form or a chain of forms, known as an “application stack.” The resulting form service can then be edited in Orchestrator Studio and included as a step in an orchestration. The process of recording the steps is more intuitive, requires less training, and is less error-prone than building the form service manually in Orchestrator Studio, allowing a broader range of citizen developers to participate in the process of creating form services.
- Report is a new type of service request that allows an orchestration to launch a report (batch job) as an orchestration step. Values for data selection, data sequencing, and version overrides can be passed into the service request as inputs, or they can be saved in the service request as defaults. The result of the process is the same as if the report had been run manually, and the report output file can be manipulated using the File Transfer feature. · File Transfer allows an orchestration step to move a file to a given location using REST, FTP, or SFTP protocols. For example, after a JD Edwards report completes, a file is typically written to a JD Edwards specific output location. Using the File Transfer feature, an orchestration step could automatically move that file from the JD Edwards report output location to another location, such as the Oracle Content and Experience Cloud Service, from where yet another automated process may be triggered. Leveraging this feature to dynamically transfer files can eliminate the development and maintenance of a custom solution to perform the same functionality.
- Confirmed Completion of Orchestrations provides a set of logged data about the events — and possibly exceptions or errors—that may have occurred during the execution of an orchestration. Administrators can monitor the logs to ensure that orchestrations are completing as expected and react to correct any errant results.
Orchestrator Studio version 6.1 includes usability improvements and enhancements:
- Users can define an input as an array to process many items in a single orchestration. For example, you can define an orchestration that adds equipment to the Equipment Master application. You can then input an array of data to create many equipment records in a single orchestration. Users can pass the application version as an input to a form service request, allowing the same form service to behave differently depending on which version is specified at runtime. The Studio can automatically load the inputs of form services as orchestration inputs, relieving the user from having to type them manually.
- Resilient Scheduler allows multiple instances of the Scheduler for executing orchestrations and notifications. The multiple instances of the Scheduler behave like a cluster, providing fault-tolerance and scalability solution.
2. JD Edwards Personalization Framework
JD Edwards EnterpriseOne continues to empower citizen developers and enrich the extensibility frameworks to help customers personalize and extend their solution at a low cost without creating barriers to stay current with JD Edwards. This enables customers to avoid customizations which will help with continuous adoption which was talked about during keynote. The personalization framework with form extensions was a new feature and there are several other planned features to be released in new versions.
Oracle’s JD Edwards EnterpriseOne has supported vendor 64-bit hardware, operating systems, databases, Java, and middleware for many years. Additionally, multiple JD Edwards components, such as HTML Server, AIS Server, Orchestrator and other Java-based components, are 64-bit enabled. Now, to round out our architecture, JD Edwards will enable 64-bit processing for the Enterprise Server and development client. This empowers you to move completely from 32-bit to 64-bit processing. There are several reasons why you would want to move to 64-bit processing:
- Moving to 64-bit enables you to adopt future technology and future-proof your environments. If you do not move to 64-bit, you incur the risk of facing hardware and software obsolescence. The move itself to 64-bit is the cost benefit.
- Many vendors of third-party components, such as database drivers and Java, which JD Edwards EnterpriseOne requires, are delivering only 64-bit components. They also have plans in the future to end or only provide limited support of 32-bit components.
- It enables JD Edwards to deliver future product innovation and support newer versions of the required technology stack.
There is no impact to your business processes or business data. Transitioning to 64-bit processing is a technical uplift that is managed with the JD Edwards Tools Foundation.