Oracle Pre-Built Developer Virtual Machines

I wanted to bring to your awareness the Oracle Pre-Built Virtual Machines that are available to us in OTN with our Oracle accounts.

All you need to do is install Oracle Virtual Box (Free Virtual Machine Client), and then import any appliance (Pre-Built VM), that you download from OTN, to it and start using it.

Oracle has several Pre-Built VM’s available at the following location: https://www.oracle.com/technetwork/community/developer-vm/index.html

The one that’s probably most useful for the typical Oracle (including EBS) development activities is the “Database App Development VM”. This one comes with the below pre-installed:

• Oracle Linux 7
• Oracle Database 12c Release 2 Enterprise Edition (12.2.0.1 Linux x86-64)
• Oracle XML DB
• Oracle SQL Developer
• Oracle SQL Developer Data Modeler
• Oracle Application Express
• Hands-On-Labs (accessed via the Toolbar Menu in Firefox)

Note that it includes Oracle Application Express (APEX) so it is a great way to get familiar with that product without having to go through the installation steps or using the Cloud version, where your workspace gets wiped periodically.

Also, this VM, like others, comes with Hands on Labs, where you can learn to use certain software like APEX by following the training included in the VM.

When you launch this particular VM and open the Browser, it takes you to the Learning Center and you can go through the Labs for each of the topics for the given VM,  the Database App Development VM contains the below training material:

This development VM is a really good alternative to install development tools and try things you wouldn’t want to try on your workstation out of fear of messing up your environment, so everyone should install Virtual Box and download this VM!

Other interesting VM's available for download:

• SOA Suite 12.1.3.0.1 VM

• Oracle Data Integrator 12c VM (Comes with Golden Gate)

• Oracle WebCenter Portal VM (Full Webcenter Suite)

Needles to say, the above VM's provide an excellent opportunity to gain exposure and experience with tools like Webcenter and Golden Gate without going through complex installations and having to involve any vendors.

To summarize, the key benefits of utilizing these Virtual Machines include:

• Utilizing new Oracle software without having to perform complex installations or vendor involvement.
• Experimenting without exposing your workstation.
• Free guided training provided by Oracle in the form of Hands On Labs.

Thanks!

The Oracle EBS Invalid Object Utility

If you are familiar with Oracle databases then you are familiar with invalid objects. Specially in the realm of EBS, where making a code change to a package, changing a table or applying a patch can cause many objects to become invalid within the various schemas in your database. There are of course tables you can query to see which objects are invalid, like dba_objects, where you can see whether a particular object is in an invalid state. However, the reason as to why that is, is not as easy to discern.

Here is where the EBS Invalid Object Utility (Doc ID 2214169.1) comes in. According to Oracle, "this utility is provided by Oracle Support to proactively assist you with maintaining Oracle Application environments and can also be used for data collection by Support engineers".

So, what does it do? It generates an HTML output with good details around invalid objects in the target instance and insights as to why they are invalid. If you have ongoing research efforts to reduce the invalid objects within your EBS Oracle database then this is a must, also it is a great a tool going forward whenever you need to research any invalid objects. A good use case would be to run the utility after releases or maintenance activities where patches are applied in order to get information regarding any objects that may have become invalid and why that happened.

Unlike your basic SQL against the tables provided by Oracle, the UI within the report looks great, and aside from aiding the research of invalid objects it has a couple of additional features. First is the "droppable" objects feature, which lists obsolete objects that can be dropped, since many objects don’t get dropped automatically after patches or upgrades, even if they get deprecated, thus creating noise within your instance and making subsequent upgrades harder and true invalid objects difficult to mine. The second additional feature is the patches applied feature, this one is really useful since it helps show which patch caused which object to become invalid, which really narrows down the root cause analysis as to why an object became invalid after a patch was applied.

There is no configuration required, all that is required is for the utility to be unzipped and executed. There are some basic requirements such as having Perl installed and the APPS environment set, all of which can be seen in the note I included above.

Oracle has a dedicated thread to share feedback regarding the utility and ask any questions, the thread can be found at: https://community.oracle.com/docs/DOC-1011252

Happy invalid objects hunting!

Java Web Start for Oracle EBS

Hello Everyone,

I have been exploring options in regards to our dependency on Internet Explorer (slow and clunky) due to the fact that we rely on the Java Plug-in (NPAPI) to launch the EBS Forms, and IE is the last reliable browser to support the Netscape Plug-in Application Programming Interface (NPAPI), which limits our users to only utilize this browser. Additionally, Microsoft continues to slowly but surely phase out IE in favor of Edge.

Those used to be our only problems, Oracle planned to deprecate the Java Plug-in for web browsers starting with the release of Java SE 9 (and they have).

The solution that Oracle is now offering in regards to these problems is Java Web Start. Java Web Start applications can be launched independently of a browser since they do not rely on a browser plug-in, and it provides a migration path from Java applets.

Below is a snippet of the architectural differences between the NPAPI approach and the Java Web Start approach:

The below is a snippet from Oracle in regards to Java Web Start:

What is Java Web Start?

Java Web Start provides a browser-independent architecture for deploying Java 2 technology-based applications to the client desktop. With Java Web Start, users can launch a Java application by clicking a link in a web page. The link points to a Java Network Launch Protocol (JNLP) file, which instructs Java Web Start software to download, cache, and run the application. This way, users can download and launch applications without going through additional installation procedures.

Java Web Start software is installed as part of the Java Runtime Environment (JRE) software. Users do not have to install Java Web Start software separately or perform additional tasks to use Java Web Start applications.

What will this help solve?

1. Oracle, and modern browsers, will soon (already have) stop supporting NPAPI and launching Oracle Forms as we do today will not be possible (without major security concerns).
2. Many On-Prem EBS shops have issues today keeping up with JRE versions, and continue to use JRE 6 or 7, due to complexities around signing JAR files and the JRE executable (and compatibility issues with customizations).
3. Internal security guidance at most companies is aggressively moving to being more up to date with JRE versions on workstations, and Java Web Start is less dependent on the JRE and Oracle is working hard on ensuring the latest versions of JRE support Java Web Start.
4. Users can again utilize their preferred browser to navigate Oracle EBS Forms (such as Chrome, Firefox and Edge), and will no longer be limited to Internet Explorer.

In terms of implementation, if you are still on SSL, I believe you should combine these initiatives (Webstart and TLS migration) given you will also need to perform Forms testing when implementing TLS due to certain pre-requisite patches, and some tech-stack prerequisites are shared.

These are not nice to haves, this is the guidance from Oracle in terms of where they are moving with Forms and browser security. I believe the sooner you take these on the better, both of these are recommendations/mandates from Oracle noted in the Quarterly EBS Upgrade Recommendations: July 2018 Edition (and previous editions going back to 2017, however, they weren’t very mature).

I recommend you do a POC of the Java Web Start component by applying the pre-requisite patches in a test environment to test functionality and some key custom forms (which Oracle says should be fully supported by switching from NPAPI to Java Web Start).

Below are some key documents around Java Web Start (which is now fully supported for Oracle E-Business Suite Releases 12.2 and 12.1):

Using Java Web Start with Oracle E-Business Suite (Doc ID 2188898.1)

https://blogs.oracle.com/stevenchan/java-web-start-now-available-for-ebs-121-and-122

https://blogs.oracle.com/stevenchan/e-business-suite-and-java-web-start%3a-frequently-asked-questions

Thanks,
Julio

SSL to TLS, Oracle EBS 12.2

Hello Everyone,

In reviewing the Quarterly EBS Upgrade Recommendations: July 2018 Edition one of the key recommendations is to migrate from SSL to TLS.

12.2 inbound, outbound, and loopback connections are now (as of Q3 2016) certified with TLS 1.2, 1.1, and 1.0 as noted in the below article:

https://blogs.oracle.com/stevenchan/tls-12-certified-with-e-business-suite-122

The below doc ID contains the instructions for the move:

Enabling TLS in Oracle E-Business Suite Release 12.2 (Doc ID 1367293.1)

There is a  workflow patch, in addition to performing the migration work, so there is definitely a lot to do, specially if you are on an older version of the AD & TXK patches and your JDK version is pretty outdated.

The benefits for this are many, including easing the path to making your EBS accessible to external clients and better browser security!

Thanks,

Julio