Online Work Order Case Study
OVERVIEW
1. Project Name and Description
Online Work Order
Last year at Collaborate an Ideathon was held that allowed customers and partners to
submit their ideas to show innovation and share insights from their journey towards digital
transformation. The winning idea came from JD Edwards customer Little Rapids in the form
of an Online Work Order application they built in JD Edwards to improve an operator’s
accuracy and efficiency on the manufacturing line.
We are now going to show how the same composite application can be built using JD
Edwards capabilities, with no coding required. This approach is faster to build and reduces
overhead during upgrades. It is also an approach that can be used by any customer for their
specific needs across industries.
2. Other Uses
Anytime users need information from multiple forms together in one screen.
3. The Pain
JD Edwards provides deep and rich industry functionality; however, there are situations
when modifications are necessary to really optimize the user experience. Modifications help
cater to variations in the sequence of tasks performed and unique business processes.
Typical modifications include rearranging existing fields on forms, adding new fields to
forms, and combining information from multiple forms into one.
While these modifications are generally not complex, they do pose a problem for customers
when they apply ESUs and perform upgrades.
This leaves IT managers with the dilemma of balancing managing modifications versus
demands for what appear to be simple requests from users.
4. High Level of the JDE Solution
CafeOne
Form Personalization
Form Extensions (NEW)
Dispatch List
Parts List Inquiry
Super Backflush
2
5. The Benefits
Users can perform their jobs more efficiently with less room for error.
Customers reduce their risk of disruption when applying ESUs and performing upgrades.
6. Minimum Technical Requirements
Tools 9.2.1 and Apps 9.1+
Tools 9.2.2.4 for Form Extensions
7. Cast of Characters
The operator on the manufacturing line who has a lot of information that needs to be
captured accurately and efficiently. It’s also important to be able to easily view the work
scheduled for the day to keep production on schedule and instructions to ensure product
quality.
The IT department that is strapped for resources and can’t get the modifications the
operator needs prioritized. It is also too costly to take the time to develop and maintain the
modifications into the future.
The Business Analyst who is able to use CafeOne, Form Personalization, and Form
Extensions to create the composite application for the Online Work Order.
8. Follow-on Session or Demo Grounds to Note
111160 – Transforming the JD Edwards User Experience with UX One
Tuesday, April 24 at 11:00 AM in Lagoon H
111180 – JD Edwards Citizen Developer Unleashing the Power of Configuration and
Personalization
Wednesday, April 25 at 9:45 AM in Lagoon E
111050 - Driving Business Value Through the Digital Transformation of Manufacturing
Management
Monday, April 23 at 4:15 PM in Mandalay Bay Ballroom J
Demo Grounds – UX, Digital Business
3
Regulatory Compliance Case Study Outline
OVERVIEW
1. Project Name and Description
Orchestrating Regulatory Compliance
This use case is about using the Orchestrator to extract and send JD Edwards data to a
third party that will input the data into the correct formatted form and deliver the final PDF
version back to JDE so that the customer can submit and comply. This gets the customer
out of the business of building and maintaining report formats and lets them concentrate
instead on getting the correct data into JD Edwards accurately. The third party brings the
expertise of having the correct report formats created and maintained by them and made
available via a cloud-based service. Many times the same report information is used by
different countries, states, territories, and provinces but in their own formats.
2. Other Uses
While we will be showing this use case in the context of Health & Safety and one of the
OSHA reports, the concept is applicable for any regulatory report across the globe.
3. The Pain
Regulations are always changing and require constantly creating reports. Let’s get the
customer out of the business of building reports and let them focus on capturing and storing
the requisite data.
Regulations are very similar across jurisdictions, and even countries, although the report
formats often vary. In our example, the OSHA report, the same data is required for nearly
every country, state, province, and territory across the globe, though each will have their
own report format. There are hundreds of versions of the same report. Our global customers
would never be able to create, nor would JD Edwards be able to provide, all of these report
formats.
4. High Level of the JDE Solution
We are using the Orchestrator to extract data from JD Edwards and a groovy script to
transform the extracted data into a JSON file in the format required by the cloud service.
We will need a triggering mechanism to begin the orchestration. Current functionality would
be to use a scheduled orchestration that picks up incidents ready for reporting to the cloud
service based on incident status. We are looking at ‘future functionality’ such as a table
trigger that detects this as soon as the incident status is updated or a button that starts the
orchestration that is accessed via an app in a CafeOne window.
4
5. The Benefits
The customer would be able to comply with global regulation without having to spend
resources to build and format reports.
They would be able to focus on data capture and accuracy and not have to worry about
report appearance or construction.
This would facilitate compliance in a timely manner, which is important as regulations and
report formats are constantly changing.
6. Minimum Technical Requirements
We are using the Orchestrator, which is available for Apps release 9.0 forward.
7. Customers Interested
Anyone using JDE for regulatory compliance, possibly even localizations would find benefit
from this solution.
8. Cast of Characters
The Safety Manager or employee of the customer responsible for regulatory compliance.
The IT team, who would otherwise be assigned to create the numerous regulatory reports.
The IT team, who uses the orchestrator to solve this problem and helps the Safety Manager
comply in a timely and accurate manner.
9. Follow-on Session or Demo Grounds to Note
111410 Discover the Awesome Power of JD Edwards Orchestrator and AIS Server
Wednesday, April 25 at 2:30 PM in Mandalay Bay Ballroom K
Demo Grounds – Digital Business
5
Quality Test Results Case Study
OVERVIEW
1. Project Name and Description
Quality Test Results from a Blend Operation
It’s harvest time for grapes, and each load is tested for sugar content and other quality
characteristics. The test results influence the winemaker’s decision as to whether the load
will be rejected or accepted, and, if accepted, how they will be dispositioned for processing.
Until the winemaker’s decision is made, the grapes may be sitting in a truck in the hot sun.
They must not sit too long!
(illustration – trucks filled with grapes in the hot sun)
------------------------------------------------
Today, the test results are often written on a clipboard. Can you clearly read this test result?
The paper is delivered to the back office, where it’s recorded in JD Edwards as a quality
test. The JD Edwards system tracks the result and the cost of performing the test. The
winemaker will review the paper or go online to see the results.
(illustration: clipboard paper with grape smudges over the handwritten quality result)
------------------------------------------------
Is the test result being entered now? Unfortunately, our person has been called away from
their desk to help direct some new employees.
(illustration: computer workstation with no one sitting there)
-----------------------------------------------
An Orchestration can enter results quickly and precisely. We need to free up employees
from having to record the results on paper, transport them, and do manual data entry. The
winemaker needs to be notified quickly, especially if the test on a particular load is out of
tolerance.
It‘s SIMPLE to create an Orchestration.
(illustration: Quality Workbench P40G25 with the Process Recorder button showing)
-----------------------------------------------
Demo – Using PROCESS RECORDER
to create an Orchestration
-----------------------------------------------
6
The Robotic Process Recorder allowed us to easily automate an inefficient and error-prone process.
The Orchestration entered the Quality Operation in EnterpriseOne
It was easy to set up
The result is a faster, more accurate decision
And, a better product!
(illustration: Quality Workbench P40G25 with the Process Recorder button, and a crate of
wine bottles)
2. Other Uses
Do you have processes where results are manually recorded and then given to someone
else to be entered into the system? If that data were entered quickly and accurately, could
the employees who are currently doing those tasks use that time to perform more valuable
services? Could your decision-makers be confident in data that was recorded automatically
instead of being manually written down first and then typed?
It’s easy and it’s not expensive to set up JD Edwards for this level of automation, so we
encourage you to get ahead by taking advantage of this technology.
3. The Pain
Processes that rely on multiple people handling the same data are inefficient and error-
prone. The time involved means that data is not readily available for making the best
decisions about the goods or the service.
4. High Level of the JDE Solution
We will show recording the key strokes of entering a Quality operation (in Blend
Management) via the Process Recorder to create a Service Request, which we wrapped
in an Orchestration and connected a Notification Service Request. The Notification sends
an email or text message if a load of grapes is above or below the accepted threshold.
5. The Benefits
Instead of training and supervising employees who write test results and type data, have a
business analyst spend a little time creating an Orchestration that can reliably perform that
process from now on. Benefit from accurate, timely data for decision-making.
6. Minimum Technical Requirements
Tools 9.2.2.4, Apps 9.2, Orchestrator Studio 6.1
7. Cast of Characters
The winemaker, who is responsible for selecting grapes that will produce another selection
of award-winning wines this year.
7
Weather conditions play a huge role, having a variable effect on the grape harvest,
necessitating that the winemaker quickly obtain accurate test data about each load before
making a decision.
The data entry person, who has been called away from their desk to help direct some new
employees.
8. Follow-on Session or Demo Grounds to Note
111410 Discover the Awesome Power of JD Edwards Orchestrator and AIS Server
Wednesday, April 25 at 2:30 PM in Mandalay Bay Ballroom K
Demo Grounds – Digital Business, Industry and Applications
8
Irrigation Case Study Outline
OVERVIEW
1. Project Name and Description
Irrigation Demo
This demo shows how an orchestration can automate the process of detecting conditions,
deciding a course of action, and doing that action.
The conditions detected are:
The current moisture content of soil (presumed from an Internet of Things (IoT) moisture
sensor in the field)
The rain and temperature forecast (from an external weather forecast system)
The system makes decisions based on built-in rules:
Whether irrigation is required based on the conditions detected
Whether an irrigation operation has already been created (possibly manually)
If irrigation is necessary, how long it should last
The course of action–the “doing”–is:
To create an irrigation operation in the JDE Grower Management module
To automatically turn the irrigation system on and off
To update the status of the irrigation operation in JDE to “Complete.”
2. Other Uses
Although the setting of this demonstration is a vineyard and it is invoking the JD Edwards
Grower Management module, the overall pattern of detecting a condition, making a rules-
based decision, and doing some action is applicable to virtually all industries and functional
areas. The individual JD Edwards features shown in this demo are equally useful in many
situations. Here are some generalized examples:
Outbound REST calls to external systems (including Oracle Cloud services)
Form Request to any JD Edwards application, not just Grower Management
Data Request: Use your JD Edwards system as an input to itself by reading data from
any JD Edwards table or business view. In other words, a change in your JD Edwards
data could act as the impetus to invoke an orchestration, just like the IoT moisture
sensor did in this example.
External Database Connector: Read and write to any non-JDE database for cases when
the data doesn’t belong in JD Edwards
Custom Groovy Logic: Virtually anything a Java programmer can code
9
Message: Email content that the orchestration collects to anybody
Scheduler: Give orchestrations a “pulse” by scheduling them to Detect/Decide/Do on a
repeated frequency
3. The Pain
In this demo, the pain is the tedious, error-prone, delayed, and possibly misinformed
process of deciding whether to irrigate a field.
In the most primitive case, a Field Manager would have to visit a plot, observe the
moisture, set the irrigation system to start and stop, open a JD Edwards user session
(desktop or mobile), and record the operation in Grower Management. That leaves
opportunity for delayed action and dry crops (if the Field Manager can’t visit a plot) and
inaccurate data (if he fails or errs in recording the operation in JDE Grower
Management).
Modern irrigation systems can be programmed to detect soil moisture and irrigate in
response. But they probably cannot consult the weather forecast, so they may over-
irrigate today if it rains tomorrow. And even if the irrigation itself can be automated, the
tracking of that operation in Grower Management would still be a manually entered
transaction.
4. High Level of the JD Edwards Solution
Orchestrator features:
o External REST Connector: Weather forecast service
o Custom Groovy Logic: Complex logic to determine conditions
o Rule: Decision to irrigate based on result of Groovy logic
o Form Request: Grower operation
o Data Request: Fetch active grower operations
o Message: Notify via email if the grower operation is expired
o External Database Connector: Save and read field conditions
o Scheduler: Periodically check for active operations in the queue
External forms: Allows for custom Oracle JET charts to be embedded and shown within
a JD Edwards page
JD Edwards EnterpriseOne Grower Management
5. The Benefits
Reduction of tedious, costly tasks, such as human visits to plots and manual data entry
Rule-based determination of whether to irrigate, eliminating over-irrigation and under-
irrigation
Accuracy of data in the Grower Management module, automatically recording every
irrigation operation in ever plot, for auditing and analytics
10
6. Minimum Technical Requirements
JD Edwards EnterpriseOne Applications release 9.0, 9.1, or 9.2
JD Edwards EnterpriseOne Tools release 9.2.2.2
JD Edwards EnterpriseOne Orchestrator (Application Interface Services (AIS) Server)
JD Edwards EnterpriseOne Orchestrator Studio 6.0
7. Cast of Characters
The CEO, who wants the ship to sail smoothly, and who makes brilliant decisions based on
real-time, accurate data.
The CIO, who, by deploying Orchestrator, has empowered the business to improve their
own state.
Business analysts from all parts of the business (in this story, the Field Managers) who know
their business, know the conditions to monitor, and know what must be done.
8. Follow-on Session or Demo Grounds to Note
111410 Discover the Awesome Power of JD Edwards Orchestrator and AIS Server
Wednesday, April 25 at 2:30 PM in Mandalay Bay Ballroom K
Demo Grounds – Digital Business
11
Preconfigured Notification Case Study
OVERVIEW
1. Project Name and Description
Preconfigured Notifications Content
This demo highlights the value of not only the notifications feature but also the 35 pre-
configured notifications that are being delivered in 2018.2.
We start with the simple use case of needing to know when a purchase order for a new
tablet has been received. The user has subscribed to the notification and specified the
purchase order for the tablet they want to be notified about as well as the delivery method
(email and notification list in JDE). Once the purchase order has been received, the user
receives the notification via their email on their phone and immediately know that they can
go pick up their new tablet. They didn’t need to be signed into JD Edwards to find this out.
With the new notifications feature, this same notification can be subscribed to by a
Maintenance Manager who is waiting for a part to arrive that is needed to fix a critical piece
of equipment. The point here is that notifications can be used for many different types of
notifications, things such as simple reminders, action required for an exception condition, or
keeping you up to date on the status of a customer, order, or other business activity.
Notifications are managed through the Notification List (the “Bell”) in JD Edwards. They can
even include a link to an application the user can use to act upon the notification.
We have delivered 35 high value preconfigured notifications that our customers can use out
of the box, personalize for their business needs, and use as examples of how to create their
own. These notifications support the Order to Cash, Procure to Pay, and Approval
processes as well as many other processes across the EnterpriseOne suite of products.
2. The Pain
Users have to be signed in to JD Edwards and utilize Watchlists or perform queries on
applications in order to know if there is something important they need to take care of or if
something they are waiting for is ready for them.
3. High Level of the JDE Solution
Notifications framework to send notifications to users via email, text message (via email),
and the notifications list in JDE.
35 preconfigured notifications across the EnterpriseOne suite of products.
4. The Benefits
What benefits would customers receive?
12
Ability to be proactively notified by their ERP system of an event that is important to
them.
Eliminates the need to be signed in to JDE and run queries or monitor Watchlists to
know when something important has occurred.
5. Minimum Technical Requirements
Tools 9.2.2.4
6. Customers Using or Interested
New feature – all should be interested
7. Cast of Characters
Users that do not spend their entire day at their computer querying data – basically
everyone.
Business Analysts who create the notifications for users to subscribe to.
8. Follow-on Session or Demo Grounds to Note
111390 – Stay Informed and Act Fast with JD Edwards Notifications
Monday, April 23 at 4:15 PM in Lagoon I
111400 – JD Edwards Notifications: Under the Hood
Tuesday, April 24 at 11:00 AM in Lagoon I
Demo Grounds – UX, Digital Business
Procure-to-Pay Process Automation Case Study
OVERVIEW
1. Project Name and Description
Procure-to-Pay Process Automation
The procure-to-pay process for most customers remains a manual-intensive, paper-driven
process. Purchase orders are manually created, approved, printed, mailed, and managed.
Communications with suppliers is limited, leaving both buyer and supplier disconnected.
Often, paper invoices are received and require manual data entry to create vouchers. This is
time-consuming and error-prone. Phone calls for problem resolution often go to voicemail
and slow down the process even more.
This entire manual-driven process can now be fully automated using JD Edwards
capabilities such as IoT sensors, notifications, orchestrations, and PaaS solutions such as
Content and Experience Cloud and Process Cloud. These capabilities allow you to extend
your investment in JD Edwards and create a digital driven peer-to-peer process that saves
time, reduces costs, and improves supplier relationships.
The demo highlights the following automation in the procure-to-pay process.
An IoT sensor weighs coffee and issues a PO as the weight is below a reorder point.
A Procurement Manager is alerted that purchase orders are waiting for approval. She
reviews and approves the orders.
After approval, a PO document is automatically generated and routed to the supplier portal.
The supplier receives an email letting them know about the new order with a link opening
the order in the supplier portal. The supplier can review the details within the order, ask
questions if anything needs to be clarified and if all is good, click the ‘Acknowledgement’
button, which automatically updates the order status in JD Edwards. The buyers will be
notified of the acknowledgement; they can even be notified if a supplier does not
acknowledge the order after a set period of time so your buyer knows exactly who to contact
to follow up.
When your suppliers are ready to ship goods for an order, they can easily let you know and
submit an invoice for the shipment in one easy flow within the portal.
When an invoice is submitted, a message is automatically sent to an invoice approver for
review. Once AP signs off, the supplier invoice is loaded in JD Edwards and is ready to be
processed by voucher match automation. There is no more manual data entry. And your
14
suppliers are kept in the loop as invoices get processed, meaning no more emails and
phone calls to find out when payment is coming.
2. Other Uses
The concepts shown in this demo can be leveraged to improve most business processes.
Generate a transaction based on an IoT sensor or reorder point, and send/receive
notifications of required actions with JDE notifications. Automate steps in a business
process with orchestrations, and provide access to documents to customers, partners, or
employees with a portal from Content and Experience Cloud. Automate process steps
outside of JD Edwards with Process Cloud.
3. The Pain
The procure-to-pay process for most customers remains a manual-intensive, paper-driven,
process. Purchase orders are manually created, approved, printed, mailed, and managed.
Communications with suppliers is limited, leaving both buyer and supplier disconnected.
Has the supplier reviewed the PO? Are they going to fill it? Has the order shipped? Often,
paper invoices are received and require manual data entry to create vouchers. This is time-
consuming and error-prone. Phone calls for problem resolution often go to voicemail and
slow down the process even more.
4. High Level of the JDE Solution
IoT sensor weighs coffee. When weight is lower than reorder point, a JDE Orchestration
automatically creates a purchase order.
A Procurement Manager is alerted via a JDE Notification that purchase orders are
waiting for approval. She reviews and approves the orders.
Once the order is approved, a JDE Orchestration prints the order.
The order is printed using a BI Publisher format.
A JDE Orchestration places the BIP PO Document in the suppliers’ folder in Content and
Experience Cloud.
Process Cloud notifies the supplier that they have a PO to review.
The supplier uses the Content and Experience Cloud Supplier Portal interface to
acknowledge the PO and notify the buyer of shipment status and to upload invoices.
A JDE Orchestration maintains PO status along the way.
Process Cloud Service submits an approval form to the buyer for approval of supplier
invoice.
A JDE Orchestration loads the supplier invoice in JD Edwards where it can be picked up
by Voucher Match Automation.
5. The Benefits
Eliminates manual data entry of Purchase Order and Voucher transactions
Eliminates manual updates for Purchase Order Status
Drives the approval process for Purchase Orders and Invoices
15
Reduces process time
Engages suppliers and simplifies their user experience
Simplifies buyer side and supplier side access to Purchase Order, Receipt, and Invoice
documents
Keeps buyers and suppliers on the same page
6. Minimum Technical Requirements
Tools 9.2.2
7. Customers Using or Interested
Multiple industries including beverage, distribution, manufacturing, and others.
8. Cast of Characters
The Procurement Manager responsible for making sure required supplies and materials are
available when needed.
The buyer, procurement and Accounts Payable members who would otherwise be
responsible for manually creating the transactions, who are waiting to hear from their
suppliers and who are trying to maintain appropriate transaction status.
The IT team who uses the Orchestrator and notification and the Content and Experience
Cloud and Process Cloud to automate the process.
9. Sessions to Learn More
111390 Stay Informed and Act Fast with JD Edwards Notifications
Monday, April 23 at 4:15 PM in Lagoon I
111400 JD Edwards Notifications: Under the Hood
Tuesday, April 24 at 11:00 AM in Lagoon I
111090 Transform Procure to Pay with a Supplier Portal for JD Edwards
Wednesday, April 25 at 1:15 PM in Lagoon J
111410 Discover the Awesome Power of JD Edwards Orchestrator and AIS Server
Wednesday, April 25 at 2:30 PM in Mandalay Bay Ballroom K
Demo Grounds – Industry and Applications, Cloud
16
Chatbot Case Study
OVERVIEW
1. Project Name and Description
Integrated Chatbot User Experience for the AP Manager Role
This case study highlights a possible “future state” JD Edwards functionality built around the
financial close business process. JD Edwards Development JDELabs is researching use of
Chatbots with EnterpriseOne and this functionality is not generally available. There are two
aspects of this demo:
Seamless and natural future state extension: There are currently Generally Available
citizen developer tools that allow our customers to digitally transform a very common
business process in JD Edwards – from creating a purchase order all the way to voucher
match automation and creating an A/P voucher. This demo shows extending this digital
process to review, approve, and post voucher batches.
Modern technology and user experience: The Chatbot interface demonstrates how this
modern technology can be integrated not only in an ERP context but all the way down to
a specific user role (A/P Manager in this case). And the seamless user experience to
direct the system to do a set of mundane process steps while the human user focuses
on exception handling and analysis for more complex scenarios.
2. Other Uses
Similar model (integrated modern Chatbot interface technology) can be applied to several
business process within JD Edwards. It would be especially worthwhile in areas where:
The user does a certain set of actions very infrequently (such as once a month, once a
quarter, and so on) or just once in a while: In this case, the Chatbot interface can not
only serve as a guided helper for the user to navigate through the steps of the
infrequent business process but also perform the well-defined steps on the backend, on
behalf of the user. Examples include financial close process, query for some related
information outside the regular business process, and so on.
There are several repetitive steps, prone to manual user errors. In this case, the
Chatbot interface can open up this multi-step process via a progressive conversational
interaction, where the user focuses only on inputs and the system executes the
repetitive steps on the backend. Examples include entering new assets in the system,
creating new users, and so on.
17
3. The Pain
During the financial close process A/P can be inundated with vouchers to be paid prior to the end of the period. Each batch of vouchers must be reviewed, approved, and posted prior to payment. Most of the vouchers will be approved and posted “as is” as they are within normal amounts for a particular supplier. Only those vouchers that are higher than normal really need to be reviewed for accuracy by an A/P Manager.
4. High Level of the JDE Solution
1. Chatbot interface for user interaction and experience – Intelligent Bots feature of the
Oracle Mobile Cloud Enterprise (OMCe)
2. Orchestrations to automate mundane, repetitive tasks – JD Edwards Orchestrations
5. Demo Script / Interaction
A/P Manager: Starts the chat
Edward: What can I help you with?
A/P Manager: Process vouchers
Edward: There are 31 pending voucher batches. Would you like me to review, approve, and post them?
A/P Manager: Clicks “Yes”.
Edward: Reviewing vouchers…
{time passes}
Edward: I’ve approved and posted 30 of the 31 batches.
Edward: I did not approve or post voucher batch 4312980 as it contains voucher 5678902 PV for supplier ABC Supplies that is above their normal amount. Link to Review
Edward: Monitoring post process…
Edward: Batch 4568971 ended in error due to a posting edit code error for document 345180 PV for account 30.5679 that will need to be corrected. Link to Review
6. The Benefits
Reduced friction and digitally transformed process (for the A/P financial close in this
case). Quicker turnaround time for the business process completion.
Improved productivity, reduced error rate: System doing the mundane, repetitive tasks,
thereby allowing the human user to focus on exceptions and complex business
conditions.
7. Minimum Technical Requirements
N/A – this is currently not part of the product. This is a potential “future state”
functionality.
18
8. Customers Using or Interested
Still a Proof of Concept. The conceptual use case should apply to most customers.
9. Cast of Characters
Users who do certain tasks very infrequently (thereby prone to making errors or spending
time to figure out on how to do the task) or are wasting time on doing repetitive mundane
tasks within JD Edwards EnterpriseOne.
Virtual digital assistant, user’s digital persona/twin who can guide, help, or do work on behalf
of the user.
10. Follow-on Session or Demo Grounds to Note
110990 – JD Edwards Roadmap
- Monday, April 23 at 1:15 PM in Mandalay Bay Ballroom J
111360 – Innovating Ahead of Your Competition with JDELabs
- Wednesday, April 25 at 8:30 AM in Reef D
Demo Grounds – UX
Note: Please check all sessions for changes in times or location.
CONNECT WITH US
Call +1.800.ORACLE1 or visit oracle.com.
Outside North America, find your local office at oracle.com/contact.
blogs.oracle.com/oracle facebook.com/oracle twitter.com/oracle
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents
hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or
conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a
particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either
directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or
mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks
or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0418