-
Title
Oracle Application server not working -
Description
After instrumenting the agent and starting the application server, J2EE agent does not start.
ERROR
YYYY-MM-DD HH:MIN:SEC FATAL [PerformaSure Agent Main Thread] com.quest.pas.agent.app.AppServerAgent - Failed to retrieve all vital Application Server details: AppServerInfo{type: OracleAS, version: null, system name: xxxx-1, cluster name: C_127.0.0.1.1a786c3.134e6dd15d5.-8000} -
Cause
1. Preinstrumentation not done correctly.
2. Wrong path of opmn.xml is preinstrumented in the agent properties.
3. Server is standalone but noted as cluster server in opmn.xml file. -
Resolution
1. Go to FMS console | Dashboards | Administration | Agents | Agent status | Edit properties of JAVAEE agent | Oracle Application Server | Edit | check the path for opmn.xml
2. Determine JDK, Go to <oracle_home>/jdk
<java_home>/bin/java -version
2. Determine Versioned_subdirectory
For example, /opt/fglam/agents/JavaEE/3. Run the preinstrumentor command
/opt/fglam/agents/JavaEE/scripts/preinstrumentor.sh <oracle_home>/jdk4. Run the bootstrap command
/opt/fglam/agents/JavaEE/bootstrap5. Go to opmn.xml file, check the following
a) Go to opmn | <process-manager> | <ias-instance id> | <environment>
<variable id="TMP" value="/tmp" /> (this can be deleted, this tmp is not required)
<variable id="PERFORMASURE_HOME" value="/opt/fglam/agents/JavaEE/"/>
<variable id="PERFORMASURE_JDK14_OPTIONS" value="-Dquest.debug=0 -Xbootclasspath^/p:$PERFORMASURE_HOME/bootstrap/-eduapp-oas10g-jdk.jar"/>
</environment>b) Go to opmn | <process-manager> | <ias-instance id> | <ias-component id ="OC4J"> | <process-type-id> | <module-data> | <category id="start-parameters">
<data id="java-options" value="-server ... $PERFORMASURE_JDK14_OPTIONS"/> (please give the value for the PERFORMASURE_JDK14_OPTIONS)
</category>6. save opmn.xml
7. Restart Oracle Application server.