Archives by date

You are browsing the site archives for June 2017.

JD Edwards EnterpriseOne Tools Release 9.2.1.4

http://e1tips.com/wp-content/uploads/2017/07/cropped-information-technology-page.jpg

Just in case you missed it, the latest JD Edwards EnterpriseOne Tools Release is now generally available.

As with most new releases, there are some interesting features included: enhancements to EnterpriseOne Search, new Orchestration capabilities, additional flexibility for Media Object storage, and platform certifications.

However, there are a couple things that I think are especially interesting:

  • Rather than being licensed as a discrete product, the usage of Orchestrator is now included as part of JD Edwards EnterpriseOne Core Tools and Infrastructure.
    • Thats right! The way I read this is that if you are licensed for JDE Core Tools & Infrastructure, you are now licensed for Orchestrator. Good news if youve been on the fence about using this new technology or dont have a big enough project to make the licensing worth it.
  • You can now store Media Objects on the file system or in the database which enables you to upgrade to TR 9.2.1.4 without re-writing existing Medio Object integrations.

Its great to see all the improvements that are being made.

What do you think is the most compelling improvement to get you to upgrade?

Activate Callstack Dump From Server Manager

Server_Manager-Enterprise_Server_Processes

While doing some not-so-fun troubleshooting, we needed to get a callstack dump from a Call Object Kernel that was going into a zombie state. I hate those things!

Anyway, follow the steps below to get a callstack dump from Oracle JD Edwards EnterpriseOne Enterprise Server:

  1. Within the Network and Queue Settings configuration, verify Jdenet_n Signal Handler is enabled.
    Server_Manager-Network_Queue_Settings
  2. Set the Create Kernel Process Dumps to Create Kernel Dumps
    Server_Manager-Network_Queue_Settings2
  3. When a call object kernel crashes (zombie) locate it in Server Manager and open the jde.log.
  4. Scroll down to the bottom and you will see an entry related to a dump file. On a Windows Server, the entry will tell you exactly where the file is located. For Linux and Unix locate the dump file in the same directory as the parent logs files.

Now, the fun part you get to try and figure out what happened.

Do you have any tips when it comes to getting or reading dmp files?

Submit a Tip or Trick