TIBCO LogLogic SEM connection lost multiple times each day
Article ID: KB0077427
Updated On:
| Products | Versions |
|---|---|
| TIBCO LogLogic Security Event Manager | 3.1.0 |
Description
1. Connect with SSH to the SEM host using the “root” account.
2. Stop the runtime
/etc/init.d/exa_runtime_INSTANCE stop (where “INSTANCE” corresponds to the name of your instance)
3. Backup the existing ExaProtect.war file:
cp /home/exaprotect/runtime/ExaProtect.war /root/ExaProtect.war.orig
4. Copy the new file to the SEM server to this location:
/home/exaprotect/runtime/ExaProtect.war
5. Check the rights and execution rights with the command
ls -l /home/exaprotect/runtime/ExaProtect.war
The output should be like this:
-rw-r--r-- 1 exaprotect exaprotect 34899088 Jan 27 07:25 /home/exaprotect/runtime/ExaProtect.war
6. Start the runtime
/etc/init.d/exa_runtime_INSTANCE start (where “INSTANCE” corresponds to the name of your instance)
7. Connect to the GUI
2. Stop the runtime
/etc/init.d/exa_runtime_INSTANCE stop (where “INSTANCE” corresponds to the name of your instance)
3. Backup the existing ExaProtect.war file:
cp /home/exaprotect/runtime/ExaProtect.war /root/ExaProtect.war.orig
4. Copy the new file to the SEM server to this location:
/home/exaprotect/runtime/ExaProtect.war
5. Check the rights and execution rights with the command
ls -l /home/exaprotect/runtime/ExaProtect.war
The output should be like this:
-rw-r--r-- 1 exaprotect exaprotect 34899088 Jan 27 07:25 /home/exaprotect/runtime/ExaProtect.war
6. Start the runtime
/etc/init.d/exa_runtime_INSTANCE start (where “INSTANCE” corresponds to the name of your instance)
7. Connect to the GUI
Issue/Introduction
This article explains how to resolve the issue of LogLogic SEM connection being lost multiple times each day.
Feedback
Yes
No
Powered by
