1[]jd edwards enterpriseonetools system overview guide ... · 1[]jd edwards enterpriseonetools...

[1]JD Edwards EnterpriseOne ToolsSystem Overview Guide

Release 9.2.x

E64056-06

November 2019

Describes the runtime architecture and integrateddevelopment environment of the EnterpriseOne architecture.

JD Edwards EnterpriseOne Tools System Overview Guide, Release 9.2.x

E64056-06

Copyright © 2013, 2019, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions onuse and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverseengineering, disassembly, or decompilation of this software, unless required by law for interoperability, isprohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. Ifyou find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing iton behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,any programs installed on the hardware, and/or documentation, delivered to U.S. Government end usersare "commercial computer software" pursuant to the applicable Federal Acquisition Regulation andagency-specific supplemental regulations. As such, use, duplication, disclosure, modification, andadaptation of the programs, including any operating system, integrated software, any programs installed onthe hardware, and/or documentation, shall be subject to license terms and license restrictions applicable tothe programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information managementapplications. It is not developed or intended for use in any inherently dangerous applications, includingapplications that may create a risk of personal injury. If you use this software or hardware in dangerousapplications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and othermeasures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damagescaused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks oftheir respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarksare 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 AdvancedMicro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content,products, and services from third parties. Oracle Corporation and its affiliates are not responsible for andexpressly disclaim all warranties of any kind with respect to third-party content, products, and servicesunless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and itsaffiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use ofthird-party content, products, or services, except as set forth in an applicable agreement between you andOracle.

iii

Contents

Preface ................................................................................................................................................................ vii

Audience...................................................................................................................................................... viiDocumentation Accessibility .................................................................................................................... viiRelated Documents .................................................................................................................................... viiConventions ................................................................................................................................................ vii

1 Overview of the JD Edwards EnterpriseOne Architecture

2 EnterpriseOne Tools Release 9.2.3 Support Policy

3 Base Components

3.1 Enterprise Server......................................................................................................................... 3-13.1.1 Overview of Enterprise Server........................................................................................... 3-13.1.2 Enterprise Server Architecture .......................................................................................... 3-23.1.3 Enterprise Server Certified Platforms............................................................................... 3-23.1.4 Additional References ......................................................................................................... 3-23.2 HTML Server ............................................................................................................................... 3-23.2.1 Overview of HTML Server................................................................................................. 3-33.2.2 HTML Server Architecture................................................................................................. 3-43.2.3 HTML Server Certified Platforms ..................................................................................... 3-43.2.4 Additional References ......................................................................................................... 3-53.3 Database Server ........................................................................................................................... 3-53.3.1 Overview of the Database Server ...................................................................................... 3-53.3.2 Database Server Architecture............................................................................................. 3-63.3.3 Database Server Certified Platform................................................................................... 3-63.3.4 Additional References ......................................................................................................... 3-6

4 System Administration and Monitoring

4.1 Deployment Server ..................................................................................................................... 4-14.1.1 Overview of Deployment Server....................................................................................... 4-14.1.2 Deployment Server Architecture....................................................................................... 4-24.1.3 Deployment Server Certified Platforms ........................................................................... 4-24.1.4 Additional References ......................................................................................................... 4-24.2 Server Manager ........................................................................................................................... 4-24.2.1 Overview of Server Manager ............................................................................................. 4-2

iv

4.2.2 Server Manager Architecture ............................................................................................. 4-44.2.3 Server Manager Certified Platforms ................................................................................. 4-44.2.4 Additional References ......................................................................................................... 4-44.3 Oracle Application Management Suite for JD Edwards EnterpriseOne............................. 4-54.3.1 Overview of Oracle Application Management Suite for JD Edwards EnterpriseOne .....

4-54.3.2 Application Management Suite Architecture.................................................................. 4-54.3.3 Application Management Suite Certified Platforms ...................................................... 4-64.3.4 Additional References ......................................................................................................... 4-6

5 Integration and Interoperability

5.1 Overview of Integration and Interoperability ........................................................................ 5-15.2 Business Services Server ............................................................................................................ 5-15.2.1 Overview of Business Services Server .............................................................................. 5-25.2.1.1 Interoperability Patterns.............................................................................................. 5-25.2.1.2 Business Services Lifecycle.......................................................................................... 5-25.2.2 Business Services Server Architecture .............................................................................. 5-25.2.3 Business Services Server Certified Platforms .................................................................. 5-45.2.4 Additional References ......................................................................................................... 5-45.3 Application Interface Services (AIS) Server ............................................................................ 5-55.3.1 Overview of AIS Server ...................................................................................................... 5-55.3.2 AIS Server Architecture ...................................................................................................... 5-55.3.3 AIS Server Certified Platforms........................................................................................... 5-65.3.4 Additional References ......................................................................................................... 5-65.4 Transaction Server ...................................................................................................................... 5-65.4.1 Overview of Transaction Server ........................................................................................ 5-65.4.2 Transaction Server Architecture ........................................................................................ 5-75.4.3 Transaction Server Certified Platforms ............................................................................ 5-75.4.4 Additional References ......................................................................................................... 5-85.5 Connectors for Point-to-Point Integrations ............................................................................. 5-85.5.1 Connectors Certified Platforms ......................................................................................... 5-85.5.2 Additional References ......................................................................................................... 5-85.6 Batch Interfaces ........................................................................................................................... 5-85.6.1 Batch Interfaces Certified Platforms ................................................................................. 5-95.6.2 Additional References ......................................................................................................... 5-9

6 Reporting

6.1 JD Edwards EnterpriseOne Universal Batch Engine............................................................. 6-16.1.1 Universal Batch Engine Certified Platforms.................................................................... 6-16.1.2 Additional References ......................................................................................................... 6-16.2 Oracle Business Intelligence Publisher .................................................................................... 6-26.2.1 Overview of Embedded BI Publisher ............................................................................... 6-26.2.2 Embedded BI Publisher Architecture ............................................................................... 6-26.2.3 Embedded BI Publisher Certified Platform ..................................................................... 6-26.2.4 Data Access Driver with Standalone BI Publisher.......................................................... 6-36.2.5 Additional References ......................................................................................................... 6-36.3 One View Reporting ................................................................................................................... 6-3

v

6.3.1 Overview of One View Reporting..................................................................................... 6-36.3.1.1 One View Reporting Lifecycle .................................................................................... 6-46.3.2 One View Server Architecture ........................................................................................... 6-46.3.3 One View Reporting Certified Platforms......................................................................... 6-56.3.4 Additional References ......................................................................................................... 6-5

7 Security

7.1 Security Server............................................................................................................................. 7-17.1.1 Overview of Security Server .............................................................................................. 7-17.1.2 Security Server Architecture .............................................................................................. 7-27.1.3 Security Server Certified Platform .................................................................................... 7-37.1.4 Additional References ......................................................................................................... 7-37.2 LDAP ............................................................................................................................................ 7-37.2.1 Overview of LDAP .............................................................................................................. 7-37.2.2 LDAP Architecture .............................................................................................................. 7-47.2.3 LDAP Certified Platform .................................................................................................... 7-47.2.4 Additional References ......................................................................................................... 7-47.3 Single Sign-on.............................................................................................................................. 7-47.3.1 Overview of Single Sign-on................................................................................................ 7-57.3.2 Single Sign-on Architecture................................................................................................ 7-57.3.3 Single Sign-on Certified Platform...................................................................................... 7-67.3.4 Additional References ......................................................................................................... 7-6

8 Portal

8.1 Overview of Portal...................................................................................................................... 8-18.2 Portal Architecture...................................................................................................................... 8-38.3 Portal Certified Platform............................................................................................................ 8-38.4 Additional References ................................................................................................................ 8-4

9 Secure Search

9.1 Overview of Secure Search ........................................................................................................ 9-19.2 Secure Search Architecture ........................................................................................................ 9-29.3 Secure Search Certified Platform.............................................................................................. 9-29.4 Additional References ................................................................................................................ 9-2

10 Clients

10.1 Web Client................................................................................................................................. 10-110.1.1 Overview of Web Client .................................................................................................. 10-110.1.2 Web Client Architecture .................................................................................................. 10-210.1.3 Web Client Certified Platform ........................................................................................ 10-210.1.4 Additional References ...................................................................................................... 10-310.2 Development Client................................................................................................................. 10-310.2.1 Overview of Development Client .................................................................................. 10-310.2.2 Development Client Architecture .................................................................................. 10-410.2.3 Development Client Certified Platform ........................................................................ 10-4

vi

10.2.4 Additional References ...................................................................................................... 10-4

11 Java Platform

11.1 Overview of Java Platform ..................................................................................................... 11-111.2 Java Platform Architecture ..................................................................................................... 11-211.3 Java Platform Certified Platform ........................................................................................... 11-211.4 Additional References ............................................................................................................. 11-2

vii

Preface

Welcome to the JD Edwards EnterpriseOne Tools System Overview Guide. This guide hasbeen updated for JD Edwards EnterpriseOne Tools releases 9.2.1 and 9.2.4.

AudienceThis guide is intended as an overview of hardware and software requirements forsystem administrators and technical consultants.

Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the OracleAccessibility Program website athttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle SupportOracle customers that have purchased support have access to electronic supportthrough My Oracle Support. For information, visithttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visithttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearingimpaired.

Related DocumentsFor more information, see the resources list at the end of each section in this guide.

ConventionsThe following text conventions are used in this document:

Convention Meaning

boldface Boldface type indicates graphical user interface elements associatedwith an action, or terms defined in text or the glossary.

italic Italic type indicates book titles, emphasis, or placeholder variables forwhich you supply particular values.

monospace Monospace type indicates commands within a paragraph, URLs, codein examples, text that appears on the screen, or text that you enter.

1

Overview of the JD Edwards EnterpriseOne Architecture 1-1

1Overview of the JD Edwards EnterpriseOneArchitecture

JD Edwards EnterpriseOne is a complete suite of modular, preintegrated,industry-specific business applications designed for rapid deployment, ease ofadministration, and low total cost of ownership. It is ideally suited for organizationsthat manufacture, construct, distribute, service, or manage products or physical assets.

JD Edwards EnterpriseOne Tools is the runtime architecture and integrateddevelopment environment at the heart of the EnterpriseOne architecture. JD EdwardsEnterpriseOne Tools is the technology layer that integrates with database systems, webapplication servers, reporting tools, and other third-party solutions. JD EdwardsEnterpriseOne Tools provides an abstraction layer that allows the JD EdwardsEnterpriseOne applications to function without a direct dependency on the platformsand middleware beneath them.

JD Edwards EnterpriseOne Tools supports the industry's leading hardware, operatingsystems, and database platforms. Moreover, JD Edwards EnterpriseOne applicationslook the same to application users, regardless of the database or hardware platformbeing used.

1-2 JD Edwards EnterpriseOne Tools System Overview Guide

Figure 1–1 JD Edwards EnterpriseOne Application Suites

The following illustration provides a high-level overview of the components thatcomprise the JD Edwards EnterpriseOne technology layer. These components enablefunctionality such as user interface, security, reporting, and so on, across all JDEdwards EnterpriseOne application modules. Although depicted and often named asservers, these are actually logical components, which often can be colocated on thesame physical hardware or installed into virtual machines.

Overview of the JD Edwards EnterpriseOne Architecture 1-3

Figure 1–2 JD Edwards EnterpriseOne Technology Layer

This System Overview Guide provides a brief description of each of these technologycomponents within the JD Edwards architecture. The information will help you planthe topology of your JD Edwards EnterpriseOne implementation by helping youunderstand the general function of each component, which components aremandatory, which are optional, and which components run on which platforms.

2

EnterpriseOne Tools Release 9.2.3 Support Policy 2-1

2EnterpriseOne Tools Release 9.2.3 SupportPolicy

JD Edwards EnterpriseOne Tools 9.2.3 Release supports Application Releases 9.1 and9.2. Tools 9.2.3 is not supported with Application Release 9.0 or 9.0.2, which goes intoSustaining Support effective December 2018. For customers on Application Release 9.0and 9.0.2, Tools Release 9.2.2.x is the supported Tools release through the ExtendedSupport and Sustaining Support stages for these releases. As per the Lifetime SupportPolicy: "Each JD Edwards EnterpriseOne Tools release or update expires six monthsafter a new JD Edwards EnterpriseOne Tools release or update becomes generallyavailable." Customers on Application Releases 9.0 or 9.0.2 will receive Tools 9.2.2.xpatches and Critical Patch Updates (CPU) according to the Support Policy. No Toolspatches or CPUs are planned for Tools 9.2.2.x after the second half of calendar year2019.

Additionally, Oracle has announced that Tools Release 9.2.3 provides 64-bit processingon the Enterprise Server. Below details the support for 64-bit processing:

■ Both Tools 9.2.2 and 9.2.3 continue to run on 64-bit operating systems, databases,and web application servers according to the Certifications published on MyOracle Support.

■ Enterprise Server foundation systems and business functions that are compiled foreither 32-bit or 64-bit processing. See the Implementing 64-bit Processing learningpath on LearnJDE for details on implementing 64-bit.

■ 64-bit processing is available only for Application Release 9.2.

Application Release Tools 9.2.2 (32-bit) Tools 9.2.3 (32-bit) Tools 9.2.3 (64-bit)

9.0 X

9.1 X X

9.2 X X X

■ Tools 9.2.3 64-bit is available for the following JD Edwards certified platforms (seethe Certifications tab on My Oracle Support for current certifications):

Operating System Database

Oracle Linux Oracle Database

Microsoft Windows Microsoft SQL Server and Oracle Database

IBM i on PowerSystems

IBM DB2 for i


References■ Oracle Lifetime Support Policy for Oracle Applications

https://www.oracle.com/us/assets/lifetime-support-applications-069216.pdf

■ Certifications on My Oracle Support

https://support.oracle.com/epmos/faces/CertifyHome

■ JD Edwards EnterpriseOne 64-bit Processing Frequently Asked Questions (Doc ID2390692.1)

https://support.oracle.com/epmos/faces/DocumentDisplay?id=2390692.1

■ "Implementing 64-bit Processing with JD Edwards EnterpriseOne" learning path

https://apexapps.oracle.com/pls/apex/f?p=44785:50:0:::50:P50_EVENT_ID,P50_COURSE_ID:6054,319

■ EnterpriseOne Tools Releases on the JD Edwards Update Center

https://updatecenter.oracle.com/apps/WebSearch/updatecenter.jsp?action=news&pkgType=06



https://support.oracle.com/epmos/faces/CertifyHome

https://support.oracle.com/epmos/faces/DocumentDisplay?id=2390692.1





3

Base Components 3-1

3Base Components

This chapter contains the following topics:

■ Section 3.1, "Enterprise Server"

■ Section 3.2, "HTML Server"

■ Section 3.3, "Database Server"

3.1 Enterprise ServerThis section discusses these topics:

■ Overview of Enterprise Server

■ Enterprise Server Architecture

■ Enterprise Server Certified Platforms

■ Additional References

3.1.1 Overview of Enterprise ServerThe JD Edwards EnterpriseOne Enterprise Server is a critical component of theEnterpriseOne architecture. It validates users (Security Server), runs Business Logic(Logic Server) and Batch processing (UBEs), Interoperability Logic (XML requests),Embedded BI, and many other critical functions for EnterpriseOne.

Using Object Configuration Manager (OCM), it is possible to create separateEnterprise Server instances to distribute workload or work type (Batch Server,Interactive Server, XML Server, etc.), but each Enterprise Server instance is capable ofdoing all types of work if so desired and configured.

OCM can also be used to map third-party (such as Vertex, PC Miler) interface logic toan Enterprise Server where these products are installed, while most of the Interactiveand Batch logic runs on larger server-class machines.

Enterprise Servers can be set up so that they trust each other from a Securityperspective. This allows a central Security Server that can authenticate EnterpriseOneusers, while their activities can run on other Enterprise Server instances.

HTML Server


3.1.2 Enterprise Server Architecture

Figure 3–1 Enterprise Server Architecture

The Enterprise Server is the central hub that receives requests from multiple clients aswell as other Enterprise Server Instances. It communicates with the database fortransactional processing and can be clustered for failover and hot-swap capabilities.

3.1.3 Enterprise Server Certified PlatformsEnterprise Server is certified to run on the following platforms:

■ Linux / x86-64

■ Oracle Solaris / SPARC

■ Microsoft Windows /x86-64

■ HP-UX / Itanium

■ IBM AIX /Power

■ IBM i/Power

3.1.4 Additional References■ Oracle Certification: https://support.oracle.com, Certifications tab

Product = JD Edwards EnterpriseOne Enterprise Server

■ JD Edwards EnterpriseOne Administration Guide

■ JD Edwards EnterpriseOne Tools System Administration Guide

■ My Oracle Support document [1382706.1]

3.2 HTML ServerThis section discusses these topics:

■ Overview of HTML Server

HTML Server

Base Components 3-3

■ HTML Server Architecture

■ HTML Server Certified Platforms


3.2.1 Overview of HTML ServerThe HTML Server component of the JD Edwards EnterpriseOne architecture is largelya presentation/user interface layer. It is one module of the JD Edwards EnterpriseOneweb client solution architecture. The HTML Server also executes some Java processing;therefore, it is sometimes referred to as the Java Application Server (JAS). The termsHTML Server and JAS are synonymous.

The web client solution consists of the following:

■ HTTP server

This makes the web client available via a TCP/IP port. The JD Edwards interactiveapplications are presented to the user via an html interface accessed through aport on an http server. Examples include Oracle HTTP Server, IBM HTTP Server,and Microsoft Internet Information Services (IIS).

■ Java J2EE runtime environment

This is the Java-based web application server. JD Edwards web applications arehosted in the framework of a J2EE web application server, such as OracleWebLogic Server or IBM WebSphere Application Server.

The J2EE environment is a web server plug-in for running Java servlets, JSBs andEJBs. HTML Server is running on top the J2EE environment and manifests itself asone or more Java Virtual Machines (JVMs). This is a runtime process which runsthe Java-based code, which generates the HTML pages presented to the user andruns a portion of the application logic. To run the logic and present the userinterface, HTML Server accesses the Serial Objects tables, which contain themetadata for same (specs). A JNI-based generation process creates these SerializedObjects (F989998/F989999) from the TAM-formatted data in the JD EdwardsEnterpriseOne metadata tables (F987*). The Serialized Objects are suitable formanipulation by Java code.

■ HTML Server

The role of HTML Server itself is to build the HTML, which presents theapplications to the user. It also retrieves the other components necessary, such as.jpg graphics and JavaScript files which run some application logic on the browser.

The user logs into a known URL which points to the HTML Server instance inquestion. The URL contains a specific path on the machine hosting the J2EEinstance as well as the http port pointing to that instance. The first page is a sign-inpage. The user credentials are passed by HTML Server to the Security Server(which resides on the Enterprise Server) and authenticates them.

Application logic is coded in Event Rules (ER), a JD Edwards EnterpriseOneproprietary development language. This code takes the form of metadata calledspecifications (specs) which is read and interpreted by a JVM running on theHTML Server server in the web application server framework. ER code also makessome direct access to the JD Edwards EnterpriseOne Business data in the course ofrunning application logic.

ER code in turn makes calls to Business Functions, which are written in ANSI C.Business Functions do not run in the HTML Server environment (Java-based), butare passed to the Enterprise Server (C-based). Only a few small, simple BSFNs

HTML Server


(about two dozen) run on HTML Server as Java code plug-ins for performancereasons. The results are passed back to the machine running the HTML Serverinstance.

Finally, some logic actually runs on the browser itself in the form of javascriptcode. The .js executables are downloaded as part of the HTML stream.

The JD Edwards EnterpriseOne Enterprise Server and Database must be installedand ready to use before HTML Server is installed for production. HTML Serverdoes not replace the Enterprise Server's functionality. All UBEs and most BusinessFunctions run on the Enterprise Server.

3.2.2 HTML Server Architecture

Figure 3–2 HTML Server Architecture

3.2.3 HTML Server Certified PlatformsHTML Server is certified to run on the following platforms (operating systems andweb application servers):

■ Linux/x86-64

■ Oracle Solaris/SPARC

■ Microsoft Windows/x86-64

Database Server

Base Components 3-5

■ HP-UX/Itanium

■ IBM AIX/Power

■ IBM i/Power

■ Oracle WebLogic Server

■ IBM WebSphere Application Server


Product = JD Edwards EnterpriseOne HTML Server

■ JD Edwards EnterpriseOne HTML Server on WebLogic Reference Guide for MicrosoftWindows

■ JD Edwards EnterpriseOne HTML Server on WebSphere Reference Guide for MicrosoftWindows

3.3 Database ServerThis section discusses these topics:

■ Overview of the Database Server

■ Database Server Architecture

■ Database Server Certified Platforms


3.3.1 Overview of the Database ServerThe Database Server is the generic term given to the server and the databasemanagement software that provides the storage of data used for the EnterpriseOneapplication. There can be multiple database sources serving the JD EdwardsEnterpriseOne architecture. The database management software stores data in tablesthat are accessed by the application.

There are four different database management software systems that are supported bythe JD Edwards EnterpriseOne application:

■ Oracle Database

■ Microsoft SQL Server

■ IBM DB2

■ IBM DB2 for Linux, Unix, and Windows (JD Edwards EnterpriseOne supportsIBM DB2 only on AIX and Windows)

Database Server


3.3.2 Database Server Architecture

Figure 3–3 Database Server Architecture

The EnterpriseOne Database serves as the repository of all of the tables used by theEnterpriseOne application.

3.3.3 Database Server Certified Platform■ Oracle Database on linux/x86-64; Oracle Solaris/SPARC; Microsoft

Windows/x86-64; IBM AIX/Power; HP-UX/Itanium

■ Microsoft SQL Server on Microsoft Windows/x86-64

■ IBM DB2 on IBMi, IBM AIX/Power, and Microsoft Windows/x86-64


Product = JD Edwards EnterpriseOne Database Server

4

System Administration and Monitoring 4-1

4System Administration and Monitoring


■ Section 4.1, "Deployment Server"

■ Section 4.2, "Server Manager"

■ Section 4.3, "Oracle Application Management Suite for JD EdwardsEnterpriseOne"

4.1 Deployment ServerThis section discusses these topics:

■ Overview of Deployment Server

■ Deployment Server Architecture

■ Deployment Server Certified Platforms


4.1.1 Overview of Deployment ServerThe complete JD Edwards EnterpriseOne product comprises many components, suchas kernels that run on the enterprise server, Java components that run on webapplication servers, database tables and schemas that reside on the database server,and development clients with local copies of objects. The JD Edwards EnterpriseOneplatform certification matrix provides a broad set of platform options for deployingthese various components. Therefore, the complete set of possible deploymentscenarios can be daunting.

As its name implies, the job of the deployment server is to help the system architectand system administrator to plan the topology of the JD Edwards EnterpriseOnecomponents, to deploy those components to the appropriate servers, and to deployElectronic Software Updates and custom modifications throughout the lifecycle of a JDEdwards EnterpriseOne implementation. The deployment server accomplishes thesetasks regardless of which platforms the JD Edwards EnterpriseOne components runon.

Server Manager


4.1.2 Deployment Server Architecture

Figure 4–1 Deployment Server Architecture

4.1.3 Deployment Server Certified PlatformsThe deployment server is certified to run on the following platforms:

■ Microsoft Windows /x86-64 (64-bit)

Server and desktop operating systems are supported.


Product: JD Edwards EnterpriseOne Deployment Server

■ JD Edwards EnterpriseOne Deployment Server Reference Guide for Enterprise Systemsfor Microsoft Windows

4.2 Server ManagerThis section discusses these topics:

■ Overview of Server Manager

■ Server Manager Architecture

■ Server Manager Certified Platforms


4.2.1 Overview of Server ManagerServer Manager for JD Edwards EnterpriseOne is a web based application used tomanage the complete life cycle of the JD Edwards EnterpriseOne server products. It isavailable with the JD Edwards EnterpriseOne Tools Release 8.97 and later. ServerManager supports the same JD Edwards EnterpriseOne application releases that aresupported by the tools releases.

With JD Edwards Server Manager you can:

■ Securely access and manage the configuration of your JD Edwards EnterpriseOneinstalled components from anywhere using a standard web browser

Server Manager


■ Install, uninstall, and update your JD Edwards EnterpriseOne servers regardlessof their physical location or platforms

■ Start and stop any of your JD Edwards EnterpriseOne servers, Oracle WebLogicapplication servers, or supported third party J2EE application servers directlyfrom the Management Console

Server Manager Features:

Configuration Management: Easily change and manage configuration settings for allmanaged servers. View each configuration item along with integrated help describingthe setting.

Configuration Comparison: Compare the configuration of two or more servers toidentify configuration differences, regardless of the platform or physical location of theJD Edwards EnterpriseOne server.

Save and Restore Configuration: Save a complete configuration state before makingchanges or updates.

Integrated EnterpriseOne Software Management: Use Server Manager to centrallymaintain all your JD Edwards EnterpriseOne server tools releases, including theability to copy the software to the remote server machines.

Logical Server Grouping: Server Manager allows you to group servers with a similarpurpose. These groups can include any of the server types, such as Enterprise Server,HTML Server and a Web Server. A default or template configuration is maintained foreach server group.

Tools Release Independence: Newer versions of the Server Manager application willcontinue to support the management of earlier tools releases back to JD EdwardsEnterpriseOne initial release in Tools Release 8.97.

Audit History: Server Manager maintains a history of changes made to the managedservers. This includes a history of each configuration change, each server start andstop, and each tools release update. Including the user that performed the change oroperation. The Management Console application provides mechanisms to query andview the audit history that is maintained.

Server Manager


4.2.2 Server Manager Architecture

Figure 4–2 Server Manager Architecture

Server Manager consists of a web based 'console' application and a set of 'agents' thatcommunicate with the console. The console sends control commands and informationrequests to the agents and the agents pass along control commands to the local webapplication server or enterprise server or reports status and runtime information backto the console.

4.2.3 Server Manager Certified PlatformsServer Manager console is certified to run on the following platforms:

■ Linux / x86-64 with Oracle Weblogic Server

■ Oracle Solaris / SPARC with Oracle Weblogic Server

■ Microsoft Windows /x86-64 with Oracle Weblogic Server, Oracle Containers forJ2EE (OC4J), and IBM WebSphere Application Server

Server Manager Agent is certified to run on the following platforms:

■ Linux / x86-64



■ HP-UX / Itanium

■ IBM AIX /Power

■ IBM i/Power


Oracle Application Management Suite for JD Edwards EnterpriseOne


Product = JD Edwards EnterpriseOne Server Manager

■ JD Edwards EnterpriseOne Tools Server Manager Guide

4.3 Oracle Application Management Suite for JD Edwards EnterpriseOneThis section discusses these topics:

■ Overview of Oracle Application Management Suite for JD Edwards EnterpriseOne

■ Oracle Application Management Suite for JD Edwards EnterpriseOne Architecture

■ Oracle Application Management Suite for JD Edwards EnterpriseOne CertifiedPlatforms

4.3.1 Overview of Oracle Application Management Suite for JD Edwards EnterpriseOneThe Oracle Application Management Suite for JD Edwards EnterpriseOne allows youto use the graphical user interface of Oracle Enterprise Manager to monitor andmanage your JD Edwards server products. This product leverages the existing JDEdwards Server Manager functionality that monitors all entities constituting anEnterpriseOne installation.

It supports discovering all servers managed by server manager in Enterprise Manageras one JD Edwards EnterpriseOne domain which can consist of following differenttarget types:

■ Enterprise Server

■ HTML Server

■ Transaction Server

■ Business Services Server

■ Collaborative Portal Server

■ Data Access Driver

■ Data Access Server

It monitors the configuration metrics (jde.ini, HTML Server.ini, jdbj.ini, interop.inietc.). It also provides options to save configuration and compare configuration forsimilar target types.

It also collects runtime metrics like user sessions, open applications, Java memoryusage, JDBj connection, kernel process metrics, and prepared statement configurations.

The Oracle Application Management Suite for JD Edwards EnterpriseOne provides thefollowing additional benefits:

■ Service level management

■ History and trending (usage, server metrics, uptime)

■ Enhanced graphics and dashboards for administrators

■ Reporting capabilities

■ Single view of an organization's complete system topology

4.3.2 Application Management Suite ArchitectureEnterprise Manager consists of a web based 'console' OMS application and a set of EM'agents' that communicate with the console. The console sends control commands and

Oracle Application Management Suite for JD Edwards EnterpriseOne


information requests to the agents and the agents pass along control commands to theHTML server or enterprise server via server manager, or report status and runtimeinformation back to the console.

Figure 4–3 Application Management Suite Architecture

4.3.3 Application Management Suite Certified PlatformsThe Application Management Suite is certified to run on the following platforms:

■ Linux/x86-64

■ Oracle Solaris


Product = Enterprise Manager for JD Edwards EnterpriseOne Plug-in

■ JD Edwards EnterpriseOne Application Pack for Oracle Enterprise Manager CloudControl 13c Implementation Guide

5

Integration and Interoperability 5-1

5Integration and Interoperability


■ Section 5.1, "Overview of Integration and Interoperability"

■ Section 5.2, "Business Services Server"

■ Section 5.3, "Application Interface Services (AIS) Server"

■ Section 5.4, "Transaction Server"

■ Section 5.5, "Connectors for Point-to-Point Integrations"

■ Section 5.6, "Batch Interfaces"

5.1 Overview of Integration and InteroperabilityAlthough equipped with a robust set of over eighty application modules, the JDEdwards EnterpriseOne product suite typically does not cover 100% of an enterprises'sapplication requirements. As with any implementation of enterprise software, perhapsthe most important requirement is that it integrates easily with other complementaryapplications. In this regard JD Edwards EnterpriseOne does not take a one-size-fits-allapproach. Rather, it offers several interoperability and integration patterns to ensurethat system architects can apply the appropriate technology for an optimal solution tothe requirements.

JD Edwards EnterpriseOne offers the following methods for interoperability andintegration with other Oracle applications and third-party products:

■ Business Services Server

■ Application Interface Services (AIS) Server

■ Transaction Server

■ Connectors for point-to-point integration

■ Batch interfaces for bulk data transfer

5.2 Business Services ServerThis section discusses these topics:

■ Overview of Business Services Server

■ Business Services Server Architecture

■ Business Services Server Certified Platforms


Business Services Server


5.2.1 Overview of Business Services ServerThe Business Services Server provides interoperability between JD EdwardsEnterpriseOne and other Oracle applications and third-party systems by nativelyproducing and consuming web services. It can also send XML over HTTP(s) in anasynchronous request/reply model when the third party does not support web servicecalls. The business services server is built on top of a Java 2 Platform, EnterpriseEdition (J2EE) server, which can be an Oracle WebLogic Server or a WebSphereApplication Server. Applications that are developed or run on the Business ServicesServer are written in the Java programming language.

The business services server exposes business services as web services. A web serviceis a standardized way of integrating web-based applications, and in JD EdwardsEnterpriseOne, web services are referred to as published business services. Businessservices provide operations that access the business logic in JD EdwardsEnterpriseOne for many supported business transactions, such as journal entries,exchange rates, accounts payable vouchers, inventory look-ups, pricing, sales orders,etc and they enable JD Edwards EnterpriseOne to expose transactions as a basicservice that can expose an XML document-based interface.

5.2.1.1 Interoperability PatternsThe business services server supports the following integration patterns forinteroperating with other Oracle applications and third-party applications or systems:

■ Service provider

■ Service consumer

■ Event Notification

5.2.1.2 Business Services LifecycleThe lifecycle of a business service is similar to the lifecycle of a business function. Abusiness service is created on the development client as a JD Edwards EnterpriseOneobject using both JD Edwards EnterpriseOne tooling and JDeveloper. ObjectManagement Workbench (OMW) controls the artifacts for add, check-in, check-out,get, restore, and delete. The business service is compiled and assembled into adeployable artifact during the package build process. Server Manager uses thatdeployable artifact to deploy a business services server. Subsequent client installs willinclude any new or updated business service artifacts.

5.2.2 Business Services Server ArchitectureThe following diagram depicts the relationships between the various JD EdwardsEnterpriseOne servers and the Business Services Server and it also shows how thebusiness services server provides interoperability with other Oracle applications andthird-party systems:



Figure 5–1 Business Services Server Architecture

The below diagram provides an architectural overview of the business serviceslifecycle:



Figure 5–2 Business Services Server Lifecycle Architecture

5.2.3 Business Services Server Certified PlatformsBusiness Services Server is certified to run on the following platforms:

■ Linux / x86-64



■ HP-UX / Itanium

■ IBM AIX /Power

■ IBM i/Power




Product = JD Edwards EnterpriseOne Business Services Server

■ JD Edwards EnterpriseOne Tools Business Services Server Reference Guide

■ JD Edwards EnterpriseOne Tools Business Services Development Guide

■ JD Edwards EnterpriseOne Tools Business Services Development Methodology Guide

■ JD Edwards EnterpriseOne Tools Interoperability Guide

■ JD Edwards EnterpriseOne Tools Interoperability Reference Implementations Guide

Application Interface Services (AIS) Server


5.3 Application Interface Services (AIS) ServerThis section discusses these topics:

■ Overview of AIS Server

■ AIS Server Architecture

■ AIS Server Certified Platforms


5.3.1 Overview of AIS ServerThe AIS Server provides a JSON over REST interface, which is a light-weight interfacethat AIS clients (such as mobile enterprise applications, AIS Java API clients, andInternet of Things devices) use to interact with EnterpriseOne applications and forms.The interaction with EnterpriseOne requires an AIS Server configuration with theEnterpriseOne HTML Server.

Starting with EnterpriseOne Tools release 9.2.1, the AIS Server also serves as thecommunication interface for components created with Oracle Java Extension Toolkit(JET) that run inside EnterpriseOne UX One pages.

5.3.2 AIS Server ArchitectureThe following illustration shows how the AIS Server functions as the interfacebetween AIS clients and JD Edwards EnterpriseOne.

Figure 5–3 EnterpriseOne Architecture with an AIS Server

Note: The Orchestrator Studio 9.2.4 is deployed along with the AISserver 9.2.4.0 and can be accessed by using the AIS Server URL.Therefore, the Orchestrator Studio 9.2.4 does not require anyadditional set-up or installation steps. The JD Edwards EnterpriseOneOrchestrator Studio 9.2.4 is installed on AIS server instance. (Release9.2.4.0)

Transaction Server


5.3.3 AIS Server Certified PlatformsThe AIS Server is certified to run on the following platforms (operating systems andweb application servers):

■ Linux / x86-64



■ HP-UX / Itanium

■ IBM AIX /Power

■ IBM i/Power




Product = JD Edwards EnterpriseOne AIS Server

■ JD Edwards EnterpriseOne Application Interface Services Server Reference Guide

■ JD Edwards EnterpriseOne Tools Developing and Customizing Mobile EnterpriseApplications Guide

■ JD Edwards EnterpriseOne Application Interface Services Client Java API Developer'sGuide

■ JD Edwards EnterpriseOne Tools Deploying and Developing Oracle ApplicationDevelopment Framework (ADF) Applications for EnterpriseOne

■ JD Edwards EnterpriseOne Tools Internet of Things Orchestrator Guide

■ JD Edwards EnterpriseOne Tools UX One Deployment and Development Guide

5.4 Transaction ServerThis section discusses these topics:

■ Overview of Transaction Server

■ Transaction Server Architecture

■ Transaction Server Certified Platforms


Transaction Server


5.4.1 Overview of Transaction ServerTransaction Server is a key component for the Real Time Event (RTE) notificationsystem. RTE is an extension of the normal transaction process. This additionalprocessing is performed to capture the JD Edwards EnterpriseOne transaction data forsubsequent notification and delivery to external parties. This can also be termed as anOutbound Notification.

Transaction Server and Real time Event system consists of the following components:

■ Event - Contains JD Edwards EnterpriseOne data structure and values in binaryand XML format for outbound notification in both single and aggregate format.

■ Event Category - Decides how event data is processed: for example RTE, XAPI,Z-FILE etc.

■ Transport Type - How the event is delivered using JAVA connector, COMconnector, JDENET, MQ Series, JMS Topic etc.

■ Subscriber - Third party interested in receiving event and is associated with atransport type.

Following are the three life cycle events of processing in transaction server:

■ Event Generation

Business Function calls JdeIEO_EventFinalize API - An event or set of events isinserted into F90710 table

A JDENET message is sent to RTE server to trigger event transfer.

■ Event Transfer

Sequencing - Provides multiple options to sequence events

Transaction - Uses JMS Bean managed transaction.

■ Event Processing/Delivery

Convert binary format of data structure into XML format

Delivered to all interested subscribers based on transport type

5.4.2 Transaction Server Architecture

Figure 5–4 Transaction Server Architecture

Connectors for Point-to-Point Integrations


5.4.3 Transaction Server Certified PlatformsTransaction Server is certified to run on the following platforms:

■ Linux / x86-64



■ HP-UX / Itanium

■ IBM AIX /Power

■ IBM i/Power

■ Oracle Weblogic Server

■ IBM WeSphere Application Server


Product = JD Edwards EnterpriseOne Transaction Server

■ JD Edwards EnterpriseOne Transaction Server Reference Guide for Microsoft Windowsusing Oracle WebLogic Server

■ JD Edwards EnterpriseOne Tools Interoperability Reference Implementations Guide

■ JD Edwards EnterpriseOne Tools Interoperability Guide

5.5 Connectors for Point-to-Point IntegrationsConnectors are point-to-point, component-based models that enable third-partyapplications and JD Edwards EnterpriseOne to share logic and data. JD EdwardsEnterpriseOne connector architecture includes Java and COM connectors. Theconnectors accept inbound XML requests and expose business functions for reuse.Output from the connectors is in the form of an XML document. The connectorsinclude:

■ Java

Java is a portable language, so you can easily tie JD Edwards EnterpriseOnefunctionality to Java applications. The JD Edwards EnterpriseOne dynamic Javaconnector supports real-time event processing.

■ COM

The JD Edwards EnterpriseOne COM connector solution is fully compliant withthe Microsoft component object model. You can easily tie JD EdwardsEnterpriseOne functionality to Visual Basic and VC++ applications. The COMconnector also supports real-time event processing.

Some benefits of using connectors include:

■ Scalability

■ Multi-threaded capability

■ Concurrent users

Batch Interfaces


5.5.1 Connectors Certified PlatformsThe JD Edwards EnterpriseOne integration connectors run on the enterprise server.Refer to certified platforms for enterprise server for more information.

5.5.2 Additional References■ JD Edwards EnterpriseOne Tools Interoperability Guide

5.6 Batch InterfacesBatch implies processing multiple transactions at the same time and usually involvesmovement of bulk information. Batch processing is often scheduled and isnon-interactive. JD Edwards EnterpriseOne provides several model types for batchprocessing, and each model type has one or more capabilities that enable you to accessJD Edwards EnterpriseOne data. The model types include:

■ Interface tables

■ Electronic Data Exchange

■ Table conversions

■ Output Stream Access

■ Open Data Access

5.6.1 Batch Interfaces Certified PlatformsThe JD Edwards EnterpriseOne batch interfaces run on the Enterprise Server. Refer tocertified platforms for Enterprise Server for more information.

5.6.2 Additional References■ JD Edwards EnterpriseOne Tools Interoperability Guide

Batch Interfaces


6

Reporting 6-1

6Reporting


■ Section 6.1, "JD Edwards EnterpriseOne Universal Batch Engine"

■ Section 6.2, "Oracle Business Intelligence Publisher"

■ Section 6.3, "One View Reporting"

6.1 JD Edwards EnterpriseOne Universal Batch EngineJD Edwards EnterpriseOne provides a fully integrated reporting engine to generatereport output from any transactional data stored within its database. This informationincludes employee data, accounts receivable and payable information, financial data,and product information. The JD Edwards EnterpriseOne reports might be used toconvey information about business operations, for example profitability reports, orthey might function as transactional documents, such as invoices or pay checks.

The Universal Batch Engine executes the runtime processing of reports, which can besubmitted manually by end users, scheduled, or automatically launched by other JDEdwards EnterpriseOne applications. Because they are processed by the universalbatch engine, reports are often referred to as "UBEs" by the JD Edwards community.

JD Edwards EnterpriseOne provides many predesigned reports; however, it is unlikelythat any report can anticipate the needs of individual customers. Therefore, JDEdwards EnterpriseOne also includes the Report Design Aid application, which allowsend users to modify or create new reports to suit their requirements.

Reports that are used primarily to manipulate data are referred to as batch processes.Reporting and batch processing can be combined in a single report. Reports and batchprocesses are considered by the system as batch applications.

6.1.1 Universal Batch Engine Certified PlatformsThe JD Edwards EnterpriseOne Universal Batch Engine runs on the Enterprise Server.Refer to certified platforms for enterprise server for more information.

The Report Design Aid tool runs on a JD Edwards EnterpriseOne developmentworkstation, which requires a 64-bit edition of Microsoft Windows desktop operatingsystem.

6.1.2 Additional References■ JD Edwards EnterpriseOne Tools Report Design Aid Guide

■ JD Edwards EnterpriseOne Tools Batch Versions Guide

Oracle Business Intelligence Publisher


6.2 Oracle Business Intelligence PublisherThis section discusses these topics:

■ Overview of Embedded BI Publisher

■ Embedded BI Publisher Architecture

■ Embedded BI Publisher Certified Platforms

■ Data Access Driver with Standalone BI Publisher

■ Data Access Driver with Standalone BI Publisher Certified Platforms


6.2.1 Overview of Embedded BI PublisherJD Edwards EnterpriseOne provides an embedded BI Publisher reporting solutionbased on Oracle's BI Publisher. The solution integrates the embedded BI Publisherreports into JD Edwards EnterpriseOne life cycle management, and the embeddedreports are created, managed and processed using the JD Edwards EnterpriseOnetoolset.

Embedding BI Publisher reduces the high cost of producing, customizing, andmaintaining business documents. Built on the open XSL-FO (Extensible StylesheetLanguage Formating Objects) The extended standard provides a full range ofreporting capabilities, including charts, formulas, watermarks, and graphics. Using aset of familiar desktop tools, users can create and maintain their own report formatsbased on data extracts from JD Edwards EnterpriseOne reports.

This tight integration between the Universal Batch Engine and BI Publisher allows thebatch engine to handle data selection, logic processing, and output to XML format. BIPublisher then accepts the XML and formats the data according to predefinedtemplates for fonts, layouts, graphics, and distribution to a variety of print andelectronic outputs.

6.2.2 Embedded BI Publisher ArchitectureThe Embedded BI Publisher solution works by having the Universal Batch Enginegenerate and extract XML data, which is then sent to a BI Publisher Kernel inEnterpriseOne, which hosts the embedded BI Publisher JVM. This kernel takes theXML generated along with the report template and translation/transformation datacalls into the hosted BI Publisher to create the output(s) desired. These outputs arestored and then, depending on the configuration, optionally printed or emailed to thedesired recipients.

Figure 6–1 Embedded BI Publisher Architecture

One View Reporting

Reporting 6-3

6.2.3 Embedded BI Publisher Certified PlatformEmbedded BI Publisher is certified to run on the following platforms:

Linux / x86-64

Oracle Solaris / SPARC

Microsoft Windows /x86-64

HP-UX / Itanium

IBM AIX /Power

IBM i/Power

6.2.4 Data Access Driver with Standalone BI PublisherIn addition to the use case of BI Publisher being embedded within the JD EdwardsEnterpriseOne reporting process, the BI Publisher desktop application can be used tocreate custom reports from JD Edwards EnterpriseOne data sources.

JD Edwards EnterpriseOne provides a Data Access Driver (DAD) that is a JDBCdatasource plugin for the Standalone BI Publisher product. This allows processingreports in Oracle BI Publisher with JD Edwards data using the Oracle BI Publishertoolset.

Figure 6–2 Data Access Driver with Standalone BI Publisher

6.2.5 Additional References■ JD Edwards EnterpriseOne Tools BI Publisher for JD Edwards EnterpriseOne Guide

6.3 One View ReportingThis section discusses these topics:

■ Overview of One View Reporting

■ One View Reporting Architecture

■ One View Reporting Certified Platforms


6.3.1 Overview of One View ReportingOracle's JD Edwards EnterpriseOne One View Reporting provides an intuitive,easy-to-use method for you to access data and produce reports with Oracle BIPublisher.

One View Reporting enables end users to create and run their personalized reportsdirectly from JD Edwards EnterpriseOne interactive applications. These reports are

One View Reporting


typically specific to the user or role and are those that users will run on a daily, weekly,or other periodic basis as part of their normal activities. Users require a high degree ofpersonalization regarding data selection, sequencing, data columns included, and datavisualization (charts, tables, graphs) with this type of report. These end user reportsimprove user productivity by providing users with better visibility into operationaldata as part of their standard day-to-day business process. One View Reportingenables users to select data fields and perform specific data selection from within JDEdwards EnterpriseOne applications and leverage the layout capabilities within BIPublisher to define the report output formatting. Common use cases might be salesreports, customer reports, supplier reports, and employee reports.

One View Reporting allows the use of standard and customized find browse forms tolocate report data and One View applications, which use joined business views toaccess records from multiple tables. The One View find browse forms combinebusiness transactional and master data in combinations not previously available, andyou can view these data combinations in the BI Publisher layout you choose. You canalso use Data Browser to locate report data and produce One View reports.

6.3.1.1 One View Reporting LifecycleThe diagram below provides an architectural overview of the One View Reportinglifecycle.

Figure 6–3 One View Reporting Lifecycle

One View Reporting

Reporting 6-5

6.3.2 One View Server ArchitectureThe following diagram depicts the relationships between the various JD EdwardsEnterpriseOne HTML Server and the BI Publisher Server and it also shows how theOVR report interacts with the system.

Run the Report

Figure 6–4 One View Server Architecture

6.3.3 One View Reporting Certified PlatformsOne View Reporting is certified to run on the following platforms:

■ Linux / x86-64



■ HP-UX / Itanium

■ IBM AIX /Power


Product = JD Edwards EnterpriseOne One View Reporting

■ JD Edwards EnterpriseOne Tools One View Administration Guide

■ JD Edwards EnterpriseOne One View Reporting - Functional Content Overview

http://www.oracle.com/us/products/applications/jd-edwards-enterpriseone/one-view-reporting-presentation-1579089.pdf

■ JD Edwards EnterpriseOne One View Reporting demo

http://www.youtube.com/watch?v=TqXajQ9GrbA

One View Reporting


7

Security 7-1

7Security


■ Section 7.1, "Security Server"

■ Section 7.2, "LDAP"

■ Section 7.3, "Single Sign-on"

7.1 Security ServerThis section discusses these topics:

■ Overview of Security Server

■ Security Server Architecture

■ Security Server Certified Platforms


7.1.1 Overview of Security ServerJD Edwards EnterpriseOne security runs on an enterprise server in a dedicatedinternal process. You create a security table on the database server that storesinformation, such as:

Value Description

EnterpriseOne User The user ID used to sign in to JD EdwardsEnterpriseOne.

EnterpriseOne Password The user's password, which the softwarevalidates when the user signs in to JDEdwards EnterpriseOne.

System User and System Password The actual user and password used toconnect to all database managementsystems (DBMS). If the JD EdwardsEnterpriseOne environment includes morethan one DBMS, you can create differentsystem users and passwords for each datasource.

Change Frequency The frequency of password changesrequired by the software.

Last Change The date that the password was lastchanged.

Security Server


You must define a security record for each user either by group or by individual. It isrecommended that you map multiple users to the same system user. For example, eachuser can use the same system user that the software uses to connect the databasemanagement systems. By setting up the security in this manner, you can simplifydatabase administration of users and passwords.

You can also set up unified logon with JD Edwards EnterpriseOne (prior to release9.2.2) to simplify sign-in security. When you set up unified logon, JD EdwardsEnterpriseOne uses Windows Authentication to verify security. This verificationenables sign-in security to use the network logon information that a user supplieswhen logging on to Windows; JD Edwards EnterpriseOne does not require the user toenter another user ID and password when signing in.

7.1.2 Security Server Architecture

Figure 7–1 Security Server Architecture

As the security intermediary, the HTML Server security server handles these tasks:

■ Connecting to the JD Edwards EnterpriseOne Security Server for user securityauthentication and password when a web user signs in.

■ Switching to a secondary JD Edwards EnterpriseOne Security Server when theprimary server is down, provided the correct HTML Server.ini settings aredefined.

■ Notifying Java/HTML, Portal, and Interoperability client workstations when auser password has expired.

■ If an Interoperability user's password has expired, sign-in fails withoutnotification of the cause.

■ Sending error message to user log after the web user has attempted unsuccessfullyto sign in x number of times to JD Edwards EnterpriseOne, where x is the numberof sign-in attempts defined in the F98OWSEC table.

■ Allowing Java/HTML and Portal users to change name and password.

■ Encrypting JDENET messages sent between the HTML server security Server andthe JD Edwards EnterpriseOne security server.

LDAP

Security 7-3

■ Keeping a valid user session open until the user signs off or the session expires.

■ To the web user, sign-in and sign-out function the same as they do to a user onWindows, UNIX, or IBM i platforms.

7.1.3 Security Server Certified PlatformThe Security Server is certified to run on the following platforms:

■ Linux / x86-64



■ HP-UX / Itanium

■ IBM AIX /Power

■ IBM i/Power


Product = JD Edwards EnterpriseOne Enterprise Server

■ JD Edwards EnterpriseOne Tools Security Administration Guide

7.2 LDAPThis section discusses these topics:

■ Overview of LDAP

■ LDAP Architecture

■ LDAP Certified Platforms


7.2.1 Overview of LDAPLDAP is an open industry standard protocol that directory services use to manageuser profiles, such as user IDs and passwords, across multiple application systems.You can enable EnterpriseOne to use an LDAP-compliant directory service to manageEnterpriseOne user profiles and user-role relationships. After enabling EnterpriseOnefor LDAP, user profiles can be administered through an LDAP version 3 compliantdirectory server, otherwise referred to as the LDAP server. System administrators use athird-party LDAP-enabled application to access the LDAP server.

LDAP provides these benefits:

■ Central administration and repository for user profiles.

■ You can easily maintain user profiles in a single location that serves multiple enduser applications, including EnterpriseOne applications.

■ Reduced complexity.

You are not required to use several applications to maintain user profiles. In addition,users are not required to maintain multiple passwords across multiple systems.

Single Sign-on


LDAP support does not address single sign-on functionality that might exist throughother EnterpriseOne functionality.

LDAP does not support certain user profile information. Such information remains inthe domain of the EnterpriseOne server and must be maintained by the EnterpriseOnesystem administrator. Therefore, two distinct and separate user profiles may exist:

7.2.2 LDAP Architecture

Figure 7–2 LDAP Architecture

The security kernel in the Enterprise Server performs authentication against the LDAPserver when LDAP is enabled in the [SECURITY] section of the jde.ini file of theEnterprise Server. Otherwise, when LDAP is disabled, the security kernelauthenticates the user against the Enterprise Server database.

7.2.3 LDAP Certified PlatformLDAP is certified to run on the following platforms:

■ Linux / x86-64



■ HP-UX / Itanium

■ IBM AIX /Power

■ IBM i/Power


Product = JD Edwards EnterpriseOne LDAP


7.3 Single Sign-onThis section discusses these topics:

Single Sign-on

Security 7-5

■ Overview of Single Sign-on

■ Single Sign-on Architecture

■ Single Sign-on Certified Platforms


7.3.1 Overview of Single Sign-onJD Edwards EnterpriseOne single sign-on enables users to access JD EdwardsEnterpriseOne applications without re-entering a user ID and password. Singlesign-on increases the security for the JD Edwards EnterpriseOne system sincepasswords are no longer passing between different sub-systems in JD EdwardsEnterpriseOne.

Integration with Oracle Access Manager provides an alternative to the native sign-onsecurity with JD Edwards EnterpriseOne. Using Oracle Access Manager as the sign-onmechanism to JD Edwards EnterpriseOne provides several benefits including:

■ Use of long user ids and passwords

■ Windows Native Authentication

■ Single sign-on with other Oracle and third-party applications

7.3.2 Single Sign-on ArchitectureSingle sign-on with Oracle Access Manager integrates with the JD EdwardsEnterpriseOne HTML Server to provide an alternative to the native JD EdwardsEnterpriseOne sign-on screen. An Oracle Access Manager Web Gate is installed on anOracle HTTP Server, and it must be configured to protect the JD EdwardsEnterpriseOne URLs that are used to access the HTML Server.

The following illustration shows the integration environment and process flow:

Single Sign-on


Figure 7–3 JD Edwards EnterpriseOne Single Sign-on through Oracle Access Manager

7.3.3 Single Sign-on Certified PlatformSingle Sign-on with Oracle Access Manager integrates with the JD EdwardsEnterpriseOne HTML Server running on Oracle WebLogic Server. Refer to the HTMLServer section for Certified Platforms.


Product = JD Edwards EnterpriseOne HTML Server

Product = Oracle Access Manager


8

Portal 8-1

8Portal


■ Section 8.1, "Overview of Portal"

■ Section 8.2, "Portal Architecture"

■ Section 8.3, "Portal Certified Platform"

■ Section 8.4, "Additional References"

8.1 Overview of PortalA portal can be thought of as a Web-based application that is customizable by theend-user both in the look and feel of the portal and in the available content andapplications which the portal contains. A portal is an aggregator of content andapplications or a single point of entry to a user's set of tools and applications. A portletis a Web component which is managed by a container and can process requests andgenerate dynamic content. Portlets come in many flavors -- some are standards-based(JSR-168, WSRP), while others are proprietary to the portal which hosts them (JPDK).

EnterpriseOne Tools supports these Portal Servers:

■ Oracle WebCenter Portal

■ IBM WebSphere Portal

JD Edwards EnterpriseOne Portal solution is based on the WSRP standard. Twofoundational terminologies in Web Services for Remote Portlets (WSRP) standards areProducer and Consumer. The Producer is a web service that offers one or more portletsand implements various WSRP interfaces and operations. In the JDEdwardsEnterpriseOne solution, the JD Edwards EnterpriseOne HTML Web Server is theWSRP producer. Many JD Edwards EnterpriseOne application modules provideprebuilt Portlets, such as Employee Self-Service and Customer Self-Service, which aredeployed and run in the HTML Server.

The Consumer is a web service client that invokes producer-offered WSRPwebservices and provides an environment for users to interact with portlets offered byone or more producers. JD Edwards EnterpriseOne supports two portal products asWSRP Consumers:

■ Oracle WebCenter Portal

■ IBM WebSphere Portal

Server Manager must be used to deploy the EnterpriseOne HTML Web Client as aWSRP/Portal producer.

Overview of Portal


You have an option not to deploy WSRP components if the instance is for an HTMLServer only. If you are planning to use the instance as your WSRP producer, ensureyou have this option checked during deployment. The default is checked. Changingthe ini setting after deployment will not install or un-install the WSRP components.You must re-deploy the application for the ini settings to take effect.

Figure 8–1 Install WSRP

The default is to deploy WSRP components.

You can register the Producer by logging into the consumer (portal server) andregistering the WSDL service definitions (producer/HTML Server server URL) andconsume the portals from the registered producer. You can create a new portal pageand place the portlets on the new portal page consumed from the producer.

Portal Certified Platform

Portal 8-3

8.2 Portal Architecture

Figure 8–2 Portal Architecture

8.3 Portal Certified PlatformEnterpriseOne Tools supports these Portal Servers as WSRP Consumers:

Oracle Webcenter Portal is certified to run on the following platforms:

■ IBM AIX

■ Linux /x86-64

■ Oracle Solaris /SPARC


■ HP-UX /Itanium

■ IBM AIX /Power

IBM Web Sphere Portal is certified to run on the following platforms:

■ Linux /x86-64

■ Oracle Solaris /SPARC


■ HP-UX /Itanium

■ IBM AIX /Power

Additional References


■ IBM i /Power

8.4 Additional References■ Oracle Certification: https://support.oracle.com, Certifications tab

Product = JD Edwards EnterpriseOne Portal

■ JD Edwards EnterpriseOne Tools IBM WebSphere Portal Reference Guide

■ Creating Custom Portal Using WebCenter Framework: How-To Tutorial

9

Secure Search 9-1

9Secure Search


■ Section 9.1, "Overview of Secure Search"

■ Section 9.2, "Secure Search Architecture"

■ Section 9.3, "Secure Search Certified Platform"


9.1 Overview of Secure SearchJD Edwards EnterpriseOne contains a text search engine that takes information fromthe tables and associated media objects and builds a text search index. When a textsearch is initiated, it goes through the text search index and returns database recordsthat match the search criteria. In JD Edwards EnterpriseOne, the text search engineuses a business view-data source pair to retrieve table data.

Text search indexes exist as folders on a file system, so text search indexes must beaccessible using a path name to the enterprise server. Administrators must designatethe locations of these folders by specifying the base folder in Text Search Properties.

To achieve text searches from database records, JD Edwards EnterpriseOne uses OracleSecure Enterprise Search (SES).

SES is a standalone, self-contained server for search; it operates as a black box thatindexes information from the crawler and serves up the results. It comes with its ownuser interface and administration; it does not, for example, need you to program usingSQL or administer as a DBA.

SES enables a secure, high quality, easy-to-use search across all enterprise informationassets. Key features include:

■ The ability to search and locate public, private and shared content across IntranetWeb servers, databases, IMAP e-mail, document management systems,applications, and portals.

■ Highly secure crawling, indexing, and searching.

■ A simple, intuitive search interface leading to an excellent user experience.

■ Excellent search quality, with the most relevant items for a query shown first, evenwhen the query spans diverse public and private data sources.

■ Analytics on search results and usage patterns.

■ Sub-second query performance.

■ Ease of administration and maintenance, leveraging existing IT expertise.

Secure Search Architecture


9.2 Secure Search Architecture

Figure 9–1 Secure Search Architecture

Records from text enabled business views are fed into the SES server to index in theform of XML feeds. SES server reads these XML feeds and indexes them under thesource group created in the name of business view/data source combination.

Through the SES Text Search Properties application (P95820A0) we define SES/FTPproperties and validate them. Then we define business view data sources through theSES index build definition (P95800A) and build the indexes through the SES TextSearch Build report (R958001A).

While searching texts from text enabled applications, the search query formed by thetext search kernel is sent to the SES server along with the source group name. The SESserver returns data to the text search kernel and that result returned back to text searchapplication through the HTML Server.

9.3 Secure Search Certified PlatformOracle Secure Enterprise Search can be integrated with JD Edwards EnterpriseOnerunning on any of it's certified platforms. Oracle Secure Enterprise Search itself iscertified on the following Platforms:

■ Linux / x86-64


■ Microsoft Windows x64 (64-bit)

■ IBM AIX /Power


Product = Oracle Secure Enterprise Search

■ JD Edwards EnterpriseOne Tools System Administration Guide

■ JD Edwards EnterpriseOne Tools Form Design Aid Guide

10

Clients 10-1

10Clients


■ Section 10.1, "Web Client"

■ Section 10.2, "Development Client"

10.1 Web ClientThis section discusses these topics:

■ Overview of Web Client

■ Web Client Architecture

■ Web Client Certified Platforms


10.1.1 Overview of Web ClientJD Edwards EnterpriseOne end users access all applications through the web client viaa web browser. The HTML server delivers the user interface to the web browser asHTML and JavaScript. The user interface is highly interactive, allowing the end usernot only to simply enter and retrieve transactional data, but also to personalize theinterface, set lists of favorites, view business intelligence reports, and aggregatecontent from other external web sources.

There are no requirements to install additional components on the end-user's desktop;all interaction with the JD Edwards EnterpriseOne applications takes place throughthe web browser. Certain JD Edwards EnterpriseOne functionality, such as the abilityto import/export data to/from the grid, may require third party software such asMicrosoft Office to be installed on the users' desktops; however, such features aregenerally optional.

Web Client


Figure 10–1 Web Client

10.1.2 Web Client Architecture

Figure 10–2 Web Client Architecture

10.1.3 Web Client Certified PlatformWeb Client is certified to run on the following platforms:

Microsoft Windows /x86-64 (32-bit or 64-bit desktop operating systems)

■ Internet Explorer

■ Firefox

Development Client

Clients 10-3

■ Chrome

Apple Mac OS

■ Firefox


Product = JD Edwards EnterpriseOne Web Client

■ JD Edwards EnterpriseOne Tools Foundation Guide

10.2 Development ClientThis section discusses these topics:

■ Overview of Development Client

■ Development Client Architecture

■ Development Client Certified Platforms


10.2.1 Overview of Development ClientThe JD Edwards EnterpriseOne development client (also known as a WebDevelopment Client, Fat Client, Administrative Client, Windows client, orWorkstation) contains components that run as standard Microsoft Windowsapplications (for example, Active Console, Forms Design Aid (FDA), and ReportDesign Aid (RDA)) and components that run in a web browser.

This document uses the following terminology when discussing JD EdwardsEnterpriseOne clients:

■ Web Client - Components that run in a web browser.

■ Development Client - Composed of standard Windows components and WebClient.

■ The Web Client part of the Development Client runs inside an application serverthat is installed locally on the development client. The local application serverallows the developer to preview web applications on the desktop before deployingthem to the production environment.

The supported Application Servers are:

■ WebLogic Server (WLS)

■ IBM WebSphere Application Server (WAS) Express or WebSphere ApplicationServer for Developers.

The development client also uses a locally installed database, which stores localversions of objects that are under development. An integrated object managementfacility controls the check-out, check-in, and promotion of objects throughout theirlifecycle.

Development Client


10.2.2 Development Client Architecture

Figure 10–3 Development Client Architecture

10.2.3 Development Client Certified PlatformDevelopment Client is certified to run on the following platforms:

■ Microsoft Windows /x86-64 (64-bit) desktop operating systems

Local Web Application Server

■ WebLogic Server

■ IBM WebSphere Application Server Express

■ IBM WebSphere Application Server for Developers

Local Database

■ Oracle Database

Compiler

■ Microsoft Visual Studio


Product: jD Edwards EnterpriseOne Development Client

■ JD Edwards EnterpriseOne Tools Development Tools Overview Guide

■ JD Edwards EnterpriseOne Tools Development Guidelines for Application Design Guide

■ JD Edwards EnterpriseOne Tools Development Standards for Business FunctionProgramming Guide

■ JD Edwards EnterpriseOne Deployment Server Reference Guide for Enterprise Systemsfor Microsoft Windows

■ JD Edwards EnterpriseOne Development Client Installation Guide for Oracle WebLogicServer (WLS) and WebSphere Application Server (WAS) Express

Development Client

Clients 10-5

■ JD Edwards EnterpriseOne 9.1.X Web Client Support Statement (Doc ID1487909.1)

Development Client


11

Java Platform 11-1

11Java Platform


■ Section 11.1, "Overview of Java Platform"

■ Section 11.2, "Java Platform Architecture"

■ Section 11.3, "Java Platform Certified Platform"


11.1 Overview of Java PlatformJava is a set of several computer software products and specifications from Oracle /Sun Microsystems that together provide a system for developing application softwareand deploying it in a cross-platform computing environment. Java is used in a widevariety of computing platforms from embedded devices and mobile phones on the lowend, to enterprise servers and supercomputers on the high end. Writing in the Javaprogramming language is the primary way to produce code that will be deployed asJava bytecode.

The platform is not specific to any one processor or operating system, but rather anexecution engine (called a virtual machine) and a compiler with a set of libraries thatare implemented for various hardware and operating systems so that Java programscan run identically on all of them. A Java virtual machine is a virtual machine that canexecute Java bytecode. It is the code execution component of the Java platform. TheJava Development Kit (JDK) is an implementation of either one of the Java SE, Java EEor Java ME platforms released by Oracle Corporation in the form of a binary productaimed at Java developers on Solaris, Linux, Mac OS X or Windows. A Java RuntimeEnvironment (JRE) is the set of Java libraries that can be installed on various platformsand used to run Java programs that have been previously written using the Javaprogramming language.

JD Edwards EnterpriseOne products contain a variety of components written in Java,and therefore require a JRE or JDK in order to run.

Java Platform Architecture


11.2 Java Platform Architecture

Figure 11–1 JD Edwards EnterpriseOne Java Platform Architecture

Several JD Edwards EnterpriseOne components are written in Java and deployed torun within Java runtime environments. Specifically:

■ HTML Server, Business Services Server, and Transaction Server all deploy into aJava runtime environment managed by a Java application server (Oracle WebLogicServer or IBM WebSphere Application Server).

■ Oracle BI Publisher, used for JD Edwards EnterpriseOne One View Reporting or asa standalone report creation tool, runs in a JRE within Oracle WebLogic Server.

■ Portal frameworks (WSRP consumers) such as Oracle WebCenter Portal or IBMWebSphere Portal, run within Java application servers and communicate with theHTML server (WSRP producer).

■ The Server Manager console runs within a Java application server andcommunicates with agents installed on JD Edwards EnterpriseOne componentsvia Java Management Extensions (JMX).

■ Although no full Java application server is required, the enterprise server runs aJava virtual machine to process certain Java functions called from C/C++programs.

■ To enable a rich and dynamic end user experience, certain functionality within theweb client runs as JavaScript on the client.

11.3 Java Platform Certified PlatformVarious versions of the Java runtime environment are certified to run on all supportedplatforms.


■ Under Certifications, check the requirements for individual JD EdwardsEnterpriseOne products and look for supported JDK versions.

■ Supported JDK versions for JD Edwards EnterpriseOne 9.1.x HTML Server

■ My Oracle Support document [1506201.1]