JD Edwards EnterpriseOne Tools Release 9.1 Update 5 and Application Enhancements

End-User experience enhancement

• Alta Adoption

JD Edwards has adopted a new style sheet called Alta for all of its interactive applications. The Alta style provides the most modern user interface design and also provides a consistent look with JD Edwards EnterpriseOne mobile applications along with other Oracle ERP and Cloud product offerings

• Simplified Media Object

Now file can be drag and drop from the desktop

• Improved Menu Navigation

Menu navigation using “breadcrumb”, which provides quick access to recently run applications by preserving recent breadcrumbs between the user sessions

Breadcrumbs enable you to:

• Quickly and easily navigate to any other application within the menu structure of the currently open application
• View the breadcrumbs history and access the application as required.
• View and access the breadcrumbs history even after you log out and log in again to the JD Edwards EnterpriseOne application

• User interface navigation for the casual or infrequent user

Simplified user interface navigation designed for the casual or infrequent user. Configurable by user or role, EnterpriseOne Pages provide simplified navigation, contain minimal applications, and exclude extra features such as menus and the carousel.

• Calendar and email integration

Improved calendar and email integration enabling users to send email and create meeting invitations from any application with a link back to the application

One View reporting features

• Display a notification or warning message when a report exceeds the maximum amount of records that can be displayed and is configurable for PDFs that are shared among users.
• Display the query criteria used on the application to generate the One View Report.
• Simplify interaction by using a drill-back link from a report to automatically start the process of loading results into the called application.

Server Management and System Administration enhancement

• Management of mobile applications through Server Manager to include the daily tracking of key metrics such as connected users, connected device type, mobile application and version, monitoring, and logging.
• Support for clustered Business Services Server instance for JD Edwards EnterpriseOne outbound web services and Application Interface Services (AIS) Server to enable scalability, load balancing, and high availability for JD Edwards environments

Outbound BSSV Clustering

This feature enables configuring a clustered Business Services Server instance for JD Edwards EnterpriseOne outbound web services. The clustering feature enables scalability, load balancing, and high availability for JD Edwards’s outbound web services by providing multiple ports to receive JDENet messages from the Enterprise Server, and the Enterprise Server can send JDENet messages to multiple clustered Business Services Server ports

Server Only Packages

This feature removes the requirement to build a client package before building server packages, and by doing so, reduces the time required to build and deploy packages to enterprise (and HTML) servers.

Product Certification

• Oracle Database 12.1.0.2 including Database In-Memory option
• Oracle Database 12.1.x on IBM AIX and HP-UX
• Internet Explorer 11 in native mode rather than in compatibility mode
• IBM DB2 on IBM AIX and Microsoft Windows
• IBM I 7.2

Important change in package build process

Full Package Build Changes

The following changes have been made to the enterprise server for full packages:

• R9621S is a new UBE that runs first and initiates the server package build.
• The system copies all of the business functions’ .c and .h files to the enterprise server from the deployment server check-in location. This is done to preserve a snapshot of the .c and .h files at the time of the build.
• The system generates the C code from the NER on the Enterprise Server. These .c and .h files will be compiled with the rest of the business functions on the enterprise server so the generation is now done on the enterprise server.  Enterprise server does NER gen!
• Before the generation of NER(named event rules), the system will lock all processes, delete ddict, ddtext, glbtbl .xdb and ddb. It will unlock the processes and continue with the Generation.  
• The system builds the specs directly from Central Objects, putting the results in the package’s spec tables (<tablename>_<packagename>, for example, F98710_DV910FA) in the database. The client package’s local specs are no longer used to build the server spec tables in the database. Building the specs happens on the enterprise server; whereas before this enhancement, it happened on the build (client or deployment server) machine.
• The Package Definition application now has an option to compress the server package and/or the client package. The jde.ini setting is no longer valid.
• The system moves the server log, svrpkgbuild.log, from each server to the deployment server. Also, the files located under the text directory on the enterprise server are moved to the deployment server.
• You can now view the server package build logs in the Build History application when using the View Logs option. However, if the client was not built, the client logs do not appear.

Update Package Build Changes

The following changes have been made to the Enterprise server for update packages:

• R9621S is a new UBE that runs first and initiates the server package build.
• The update package business functions’ .c and .h files are transferred to the enterprise server.
• The Generation of NERs’ .c and .h files occurs on the enterprise server.
• Before the generation of NER, if the update package includes NER, the system will lock all processes, delete ddict, ddtext, glbtbl .xdb and ddb. It will unlock the processes and continue with the Generation. This only happens if there are NER in the update package.
• The specs are built from the Central Objects and put in the package’s spec tables (<tablename>_<packagename>, for example, F98710_DV910UP) in the database.  The system moves the server log, svrpkgbuild.log, from each server to the deployment server. Also, the files located under the text directory on the enterprise server are moved to the deployment server.
• You can now view the server package build logs in the Build History application when using the View logs option. However, if the client was not built, the client logs do not appear.

Changes to the Client Package Build Process

Numerous changes have also been made to the client build for both full packages and update packages.

Full Package Build Changes

The following changes have been made to the full package client build.

If Building a Server and Client Package

• R9621S is a new UBE that runs first and initiates the server package build.
• R9622C is a new UBE that runs next and initiates the client package build. The client build only occurs if it was selected in the application.
• All of the business functions’ .c and .h files are moved from the enterprise server to the package’s directory on the deployment server.
• There is no generation of NERs’ .c and .h files on the client.
• The system compiles the .c and .h files.
• The specs are built from the package’s spec tables (<tablename>_<packagename>, for example, F98710_DV910FA) in the database and put into the package’s local spec database. 

If Building a Client-Only Package

• R9622C is a new UBE that runs and initiates the client package build.
• The build behaves the same as before the enhancement.
• The business functions’ .c and .h files are retrieved from the deployment server.
• The NERs’ .c and .h files are generated on the client.
• Business functions are compiled.
• The specs are built from Central Objects into the package’s local specs.
• If the user adds a server after building a client-only package, the package will build assuming that the client was not built first. This will cause the system to overwrite the package’s business functions’ .c and .h files on the deployment server with those from the enterprise server. Also, all specs will be rebuilt.