Hosted by Chandra Wobschall and Paul Houtkooper

Hey there, JDE Connection listeners! We’re back with another insightful episode, and this time, we’re diving into a topic that stirs up a mix of excitement and trepidation—security, objects, packages, and builds. Joining us once again is the one and only Clayton Seeley, our go-to expert on all things CNC.

Who Owns Security? The Big Debate

We start off with a topic near and dear to Chandra’s heart, security administration! (Yes, Chandra might be the only one who loves talking about security). One of the biggest questions is: Who should own security in a JD Edwards environment?

• Is it a CNC function?
• Is it an application/business analyst (BA) function?
• Should there be a dedicated security role?

Clayton’s answer? Yes. Security isn’t just one team’s responsibility—it requires a cross-functional approach. CNC admins understand the system architecture, but BAs understand the data and applications. The most successful organizations have a dedicated security admin, but collaboration across teams is key to getting it right.

Understanding Security Hierarchy

We broke down the JD Edwards security model, which includes:

• User and role-based security
• Application, action, and object security
• The hierarchy of security settings

Security settings cascade, much like OCM mappings, meaning role precedence and public settings dictate user access levels. Getting this right ensures that your JD Edwards environment stays secure yet accessible.

Objects and Packages: The Build Process Explained

Clayton walked us through the package build process—one of the most crucial CNC functions. Here’s a quick breakdown:

1. Development Objects: Developers create and modify JD Edwards objects.
2. Package Assembly: Selected objects are grouped into a package.
3. Building the Package: The system compiles the objects into a deployable format.
4. Deployment: The package is pushed into the environment.

Game-Changer: Zero Downtime Deployments

We also discussed zero downtime deployments (introduced in JD Edwards 9.2.5). With this technology, updates can be pushed without taking users offline. By leveraging a blue-green deployment model, businesses can switch between live environments seamlessly. The result? No more scheduling weekend outages just to push a package!

Midwesternism of the Day

This week we take a break from the outdoor winter activities and enjoy a story about an ice-cold frosty beverage, a former CU Buffalo Lineman and Green Bay Packer, and an epic trip to Lambeau Field!

What’s Next?

We barely scratched the surface of security best practices, package management, and object lifecycle strategies. Expect future episodes where we dive deeper into:

• Code Current strategies and impact analysis reports
• Best practices for reducing customizations
• Understanding the full lifecycle of JD Edwards objects

Join the Conversation

Got a security horror story? Questions about package builds? Drop us a line at thejdeconnection@questoraclecommunity.org. We love hearing from our listeners!

Until next time, let’s keep learning, sharing, and—most importantly—laughing together. Toodles!

Missed an episode? Check out the full episode list! Also, be sure to subscribe on your favorite podcast provider, or select a provider below!

Learn More

Quest Oracle Community is where you learn. Ask questions, find answers, swap stories and connect to other JD Edwards customers and product experts in the JD Edwards Community, where you can also check out what’s happening in the Business Analyst SIG.