How to change timeout session in otm?

1)Shutdown OTM services
2)Take backup of web.xml file which is located in below location.
ls -ltrh /u01/OTM636/otm/tomcat/conf/web.xml
-rwxrwxr-x. 1 oracle dba 160K Jan 29  2015 /u01/OTM636/otm/tomcat/conf/web.xml


cp -r /u01/OTM636/otm/tomcat/conf/web.xml /u01/otm636/otm/tomcat/conf/web.xml_9sep2015

Default time out is 30 mins.


grep -i session /u01/OTM636/otm/tomcat/conf/web.xml
  <!-- ==================== Default Session Configuration ================= -->
  <!-- You can set the default session timeout (in minutes) for all newly   -->
  <!-- created sessions by modifying the value below.                       -->
    <session-config>
        <session-timeout>120</session-timeout>
    </session-config>




3)

ls -ltrh /u01/OTM636/otm/glog/gc3webapp/WEB-INF/web.xml

cp -r /u01/OTM636/otm/glog/gc3webapp/WEB-INF/web.xml /u01/OTM636/otm/glog/gc3webapp/WEB-INF/web.xml_2sep2015

grep -i session /u01/OTM636/otm/glog/gc3webapp/WEB-INF/web.xml


 <session-config>
      <session-timeout>120</session-timeout>
   </session-config>
        <listener-class>listeners.SessionListener</listener-class>
        <listener-class>glog.webserver.util.listener.SessionListener</listener-class>
       <filter-name>ClientSessionFilter</filter-name>
       <filter-class>glog.webserver.session.clientsession.ClientSessionFilter</filter-class>
      <filter-name>ClientSessionFilter</filter-name>
       <filter-class>glog.webserver.session.ParameterValidation</filter-class>
  <servlet-name>glog.webserver.session.ServletDiagServlet</servlet-name>
  <servlet-class>glog.webserver.session.ServletDiagServlet</servlet-class>
  <servlet-name>glog.webserver.session.ServletDiagServlet</servlet-name>
  <url-pattern>/glog.webserver.session.ServletDiagServlet/*</url-pattern>
  <servlet-name>glog.webserver.session.SessionErrorServlet</servlet-name>
  <servlet-class>glog.webserver.session.SessionErrorServlet</servlet-class>
  <servlet-name>glog.webserver.session.SessionErrorServlet</servlet-name>
  <url-pattern>/glog.webserver.session.SessionErrorServlet/*</url-pattern>
  <servlet-name>glog.webserver.session.SessionDiagServlet</servlet-name>
  <servlet-class>glog.webserver.session.SessionDiagServlet</servlet-class>
  <servlet-name>glog.webserver.session.SessionDiagServlet</servlet-name>
  <url-pattern>/glog.webserver.session.SessionDiagServlet/*</url-pattern>
  <servlet-name>glog.webserver.session.ProducerDiagServlet</servlet-name>
  <servlet-class>glog.webserver.session.ProducerDiagServlet</servlet-class>
  <servlet-name>glog.webserver.session.ProducerDiagServlet</servlet-name>
  <url-pattern>/glog.webserver.session.ProducerDiagServlet/*</url-pattern>
  <servlet-name>glog.webserver.sessionperf.SessionPerfServlet</servlet-name>
  <servlet-class>glog.webserver.sessionperf.SessionPerfServlet</servlet-class>
  <servlet-name>glog.webserver.sessionperf.SessionPerfServlet</servlet-name>
  <url-pattern>/glog.webserver.sessionperf.SessionPerfServlet/*</url-pattern>



Note

The default session timeout for the OTM Web Server is 30 minutes.
If you leave OTM idle for 30 minutes, your session will timeout and you will need to log in again.


For some Oracle Transportation Management installations, you may want to increase this timeout.
Please note that increasing the session timeout will increase the load on your Web server and may decrease the number of simultaneous users that can access the system. Oracle doesnt

recommend this setting more than 60 minutes.


To change this setting, edit the web.xml files on your OTM Web Server(s) at
<otm_install_path>/tomcat/conf/web.xml
<otm_install_path>/glog/gc3webapp/WEB-INF/web.xml


Below line should be edit in each file:
<session-timeout>30</session-timeout>


Change the setting to desired number of minutes.


Restart the OTM application for these changes to take effect.


See Note 1333246.1 - How Do I Alter The Session Time Before User Is Logged Out Of OTM Due To Inactivity?
Note 1351297.1 - How To Change The Session Timeout In Oracle BI Publisher 11g


If this is still not working, I suggest you log a Service Request with Oracle Support to investigate.