Salesforce

OpenEdge 12.2.1 or 12.2.2 full install is missing the OEMGMT/bin directory

Printable View
« Go Back

Information

 
TitleOpenEdge 12.2.1 or 12.2.2 full install is missing the OEMGMT/bin directory
URL Name12-2-1-install-is-missing-the-bin-directory-under-oemgmt
Article Number000195040
EnvironmentProduct: OpenEdge
Version: 12.2.1, 12.2.2
OS: All Supported Operating Systems
Other: Install Updates
Question/Problem Description
OpenEdge Management is not installed when using an Update as a complete install.

When an OpenEdge 12 update is used as a full install OEM/OEE fails to start.

OpenEdge 12.2.1 or 12.2.3 install is missing the bin directory under the oemgmt directory when installing licenses that include the AdminServer and Fathom web app like Enterprise RDBMS and the PASOE dev license.

 
Steps to Reproduce
Clarifying Information
When an OpenEdge Update is applied to an existing 12.2.0 install, OEE / OEM works as expected.

There are no errors during the installation. 

The AdminServer is started, but the 'fathom -start' command fails with the following error:
Error while getting the PAS instance status
File <path>/oemgmt/bin/tcman.sh cannot be found or does not exist. (19177)

Accessing the OpenEdge Explorer URL (http://localhost:9090/login.jsp) fails.
Error MessageError while getting the PAS instance status
File /oemgmt/bin/tcman.sh cannot be found or does not exist. (19177)
insfathom.service: Control process exited, code=exited status=1
insfathom.service: Failed with result 'exit-code'.
Failed to start OpenEdge Management for OE 12.0.
Defect NumberOCTA-29355
Enhancement Number
Cause
There is a defect with the script that tailors the fathom component. 

When running a new 12.2 install with the Update install media, the OEM tailoring fails because it treats the 12.2.1 or 12.2.2 install as a Service Pack / Update install, instead of an initial install. This means that the OEMGMT/bin does not get created, nor the fathom_12 instance.
Resolution
Fixed version(s): OpenEdge 12.3, OpenEdge 12.4, OpenEdge 12.2.3
Workaround
It is not necessary to first install OpenEdge 12.2 and then install the update. As a workaround, after a new OpenEdge 12.2 installation using 12.2.1 or 12.2.2 Update install media, within a Proenv session manually run the tailoring to first run the initial install tailoring and then to update as shown below:
 
$   proant -f $DLC/install/tlr/cleanup/60_fathom_tlr.xml -propertyfile $DLC/install/tlr/anttlr.properties -v -DDLC=$DLC install > $DLC\install\oem_tailor_install.log

$   proant -f $DLC/install/tlr/cleanup/60_fathom_tlr.xml -propertyfile $DLC/install/tlr/anttlr.properties -v -DDLC=$DLC update > $DLC\install\oem_tailor_update.log

Alternatively, first install the OpenEdge 12.0 FCS media and then install the OpenEdge 12.2.1 / 12.2.2 Update.

 
Notes
Keyword Phrase
Last Modified Date10/23/2023 12:08 PM
Powered by