For V18 Web Services, in the CSIQUSSM file system, file:
/products/cai/CSIQ180/ESCM/tpv/tomcat/webapps/endevor/enws.xsd
Shouldn't the AgedTimeout maxInclusive value be 86400?
<xs:attribute name="AgedTimeout" use="optional" default="1200">
<xs:annotation>
<xs:documentation>AgedTimeout
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:integer">
<xs:minInclusive value="0" />
<xs:maxInclusive value="1200" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
Release : 18.0
Component : CA Endevor Software Change Manager
maxInclusive value should be 86400 in enws.xsd.
However, Endevor web services is not using enws.xsd from CSIQUSSM file system tpv/tomcat, is using enws.xsd from EndevorService.war.
After EndevorService.war get deployed, enws.xsd is placed to $ENDEVOR_TOMCAT_INSTANCE/webapps/EndevorService/WEB-INF/classes/enws.xsd
And this enws.xsd has the correct maxInclusive value.
<xs:attribute name="AgedTimeout" use="optional" default="1200">
<xs:annotation>
<xs:documentation>AgedTimeout
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:integer">
<xs:minInclusive value="0" />
<xs:maxInclusive value="86400" />
In Endevor V18.1, enws.xsd has been removed from web services USS file system tpv/tomcat to eliminate the confusion.