What it does. EveREST²JDE turns JD Edwards business logic into REST endpoints — the same programming model the rest of your application landscape is already using. Any JDE Business Function, any UBE, any combination of them, callable over HTTP / HTTPS, returning JSON, from anything that can speak REST.

Why it exists. JDE’s own interface story leaves a gap. AIS gives you REST, but not for BSFNs. BSSV gives you BSFNs, but only over old SOAP. Both can trigger additional per-device licensing in JDE, and AIS may also trigger additional module licensing — sometimes enough to make the project not worth doing. EveREST²JDE uses JDE’s XML interfaces, which have no licensing implications, and bridges the gap.

Capabilities at a glance:

• Any BSFN over REST — not just a curated subset.
• UBE submission over REST — with full RI, PO, DS, Queue and Printer override support, and the full JDE UBE XML manipulation set.
• Arbitrary structured XML payloads — transactions, variables, multi-function calls passing parameters to each other, and error handling.
• Programmatic lookups — Function Names, Function Data Structure parameters, and JSON-payload builders for the developer’s convenience.
• ~5 ms per-call overhead — at least 20× faster than BSSV.
• No additional JDE licensing — uses XML kernel only.
• All JDE releases supported — from XE all the way through E920.

The simplest possible example: an intranet page reading a live JDE value from ~30 lines of PHP. That is the level of friction this product targets.

For Developers

If you have a REST client, you have a JDE client. Every modern language and every mobile platform has direct REST and JSON support — nothing to install, nothing to license, nothing JDE-specific to learn before the first call.

Three things you get on day one:

• Programmatic Function-name lookup. Discover what JDE BSFNs are available, by name, from the API itself.
• Programmatic Data-Structure lookup. Discover the parameters of a given BSFN, so you do not have to dig through JDE objects to find them.
• JSON-payload builder. Build a complete JSON structure for a subsequent BSFN call without hand-rolling every field.

With that scaffolding in place, this is the easiest development platform for JDE BSFN integration on the market.

Beyond simple BSFN calls:

• Structured XML programs. JDE supports an extended XML call syntax with transactions, variables, multi-function calls passing parameters between each other, and error handling. EveREST²JDE will submit any such structured XML — multi-step business logic in a single round trip.
• UBE XML. The JDE UBE XML kernel supports very flexible syntax covering most UBE operations, including overrides of RI, PO & DS parameters, Queue and Printer assignment, and a complete job manipulation set of calls. EveREST²JDE exposes all of this over REST.
• Mobile applications. Building mobile applications against JDE is, in practice, the easiest with this platform — the mobile side already speaks REST and JSON natively.
• Intranet integrations. Counters, gadgets, watchlists, status pages — deliverable in hours, in any web stack, from any internal page.

For IT & CNC

From a CNC perspective, the question is always “what does this add to my landscape?” The honest answer here is: very little.

• No additional JDE licensing. The solution uses JDE’s XML interfaces, not AIS, not BSSV. Neither per-device nor AIS module licensing is triggered.
• Lightweight deployment. Typical installation uses an ISAPI extension module under Microsoft IIS, optionally with SSL. That is an order of magnitude less hassle than standing up BSSV, and the IIS host can be a small VM running on an older Windows version if necessary.
• Server-side only. Nothing on user workstations, nothing on the Deployment Server, nothing on the Fat Client.
• Multi-threaded, multi-user. The solution fully supports concurrent operation. Multiple EveREST²JDE installations can be deployed against multiple JDE servers for scaling.
• Single audit trail. Calls run as JDE jobs against the JDE Enterprise Server — the same logs, the same WSJ, the same security boundary as everything else JDE does.
• Free trial available. Please contact us.

Performance & Architecture

The performance claim is concrete: a per-call overhead of about 5 ms, and at least 20× faster than Oracle’s BSSV. Three implementation choices get that number:

1. Native code, not interpreted. The middleware is implemented as a native 64-bit (or 32-bit) executable, not Java, not .NET, not Node. There is no JIT warm-up, no garbage-collector hesitation, no interpreter overhead between the request and the BSFN call.
2. Advanced caching. The middleware caches what is cacheable to minimise round-trips to the JDE Enterprise Server.
3. Reimplemented server comms. The middleware speaks to the JDE Enterprise Server directly — the standard JDE client components and their associated overhead are not in the path.

The practical consequence: interfaces wait for the JDE Business Function to finish, not for the middleware to think about it. That is the difference between a snappy integration and a slow one, and it is what makes lights-out, high-throughput automation actually possible.

Deployment model. Typical installation is an ISAPI extension under Microsoft IIS, optionally TLS-terminated at the same IIS instance. The IIS host can be physical or virtual, and can run on an older Windows release if needed. For larger landscapes, multiple EveREST²JDE installations can sit in front of multiple JDE Enterprise Servers, scaling horizontally.

OS: MS Windows (x32 or x64)
OS Editions: Workstation or Server, excluding Home Edition
CPU: Intel / AMD (x32 or x64)
System Type: Physical or Virtual
JDE Releases: XE (B7333), ERP8 (B7334), B9 (E1 8.9), E810, E811 (incl. SP1), E812, E900, E910, E920
JDE Tools Releases (pre-Unicode): SP16 onwards inclusive
JDE Tools Releases (Unicode): TR891 and up
JDE Backend Hardware Platforms: hardware-independent — all platforms supported by JDE are supported
JDE Backend Database Platforms: DB-independent — all platforms supported by JDE are supported

This software is licensed Per Server.

The optional Yearly Update / Upgrade Subscription is available at the time of purchase (not available separately) for an additional yearly fee. It is payable in advance per licence, per year. It includes premium support and all software updates released during the paid period. Its cost is calculated as 20% of the product’s list price at the time of invoicing, as may change from time to time. Unless the software is purchased for a single, short-term application, we generally recommend opting in for this Subscription: any future JDE Tools Releases and Releases / Updates may require an updated version of this solution, and the Subscription is generally more cost-efficient than one-off Upgrades.