Did you know that you can now verify if your JD Edwards environment is functional without having to identify with it?
The server manager application’s Health Check can indeed make the verification for you. However, you need the « Tools Release » 9.2.2.X version to access this functionality.
The Health Check performs the following activities. It validates:
The proper start-up of the instances listed below:
Application Interface Service (AIS) server,
Entreprise Service Server (BSSV),
A « Oneview » report on the HTML server;
The JMS resource deployment while ensuring that event triggers are active on the transaction server.
Plus, the Health Check launches:
identification on the HTML, BSSV and AIS servers
the P01012 application on HTML and AIS servers
a port test on the enterprise server
Without forgetting that italso:
runs the R0006P report on enterprise and HTML servers;performs the "GetEffectiveAddress" function on enterprise and BSSV servers;
starts the "GetAddressBook" service on the Business Service server;
tests the connection to the database on the transaction servers (RTE) and Oracle databases;
Checks some settings including archive logs and password lifetime on the Oracle database server.
64-bit version - JD Edward EnterpriseOne.
Did you know that JD Edwards EnterpriseOne will soon be available in a 64-bit version?
Indeed, the new 64-bit version is planned for this fall for 9.2, for "Tools Release" 9.2.3 and later.
How the 64-bit version works
The upgrade will be done by paths code; carried out step by step. The new ESUs will be available in 32 and 64 bits, as of fall 2018. As for the development, it will be done in 32 bits and it is during the registration in the object manager (“check in” in the OMW) that the 64-bit conversion will be completed. The migration to the 64-bit version will not be mandatory since both versions will remain available.