Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML DIM12.2.1: HPUX agent install - No Java Runtime Environment(JRE) was found on this system
Initializing InstallShield Wizard........ Verifying JVM. . No Java Runtime Environment ( JRE ) was found on this system.
PDF How To: Import SSL certificates into the Java keystore used by DA Agent
For SDA, the certificate trust store is Tomcat based and located in the JRE \LIB\SECURITY folder which by default is in the following location for Serena Common Tomcat: C:\Program Files\Serena\common\jre\8.0\lib\security
CMS-XML SRA: Agent installation is not succeeding. Logs may indicate no jvm
SRA: Agent installation is not succeeding. Logs may indicate no jvm
CMS-XML DA: "Error calculating the uncompressed size of bundled JRE or it is corrupt. Installation of bundled JRE failed."
During the installation of DA agent version 6.3.1 on AIX 7.2 the following message was received:
CMS-XML SDA: The client browser does not require any Java or JRE
The SDA client does not require any Java or JRE in the browser. This applies to SDA versions 5.x and 6. SDA Servers, Agent Relays and Agents will require a JRE -- please refer to the documentation for the SDA version in question to determine acceptable version numbers for these components.
CMS-XML SRA: JRE or JDK when oracle database is used
"Download and install the JDK – not a JRE – that corresponds to your operating system" However it also says on page 43: "All server and agent relay machines require Java JRE 6 or greater."
CMS-XML Resolving Common Problems Encountered while installing a DA Agent
Unexpected Problems Installing when you do not have full permissions on folder where install kit is located /tmp file system is configured noexec Error: Bundled JRE is not binary compatible with OS/Architecture
CMS-XML DA: Notes on agent upgrade or reinstallation
When an agent is upgraded using the GUI, the Agent's war file is upgraded, but the JRE used by the agent is not upgraded. If an agent has been deployed for some time and perhaps even upgraded a time or two, the JRE may be rather old. Sometimes it is desirable to update the bundled JRE, sometimes there are other reasons to upgrade an agent, such as a corrupt installation folder.
CMS-XML SRA: How to install and run an agent as a non root user on Linux/UNIX systems
This is a generic agent that does not include the JRE 2.
CMS-XML SRA Agent registration uses internal UID to register rather than agent name
SRA 4.0.1 Agent JRE 1.5 installed with Agent Agent is directly connecting to the SRA server, no mutual auth, no relay.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs