In our current environment, we do not have users that have fully developed the skillset or understanding of the new Teamcenter feature. Until they get their hands on it and become more accustomed to the features of the new Teamcenter, we made a quick tweak to ensure that the default landing page for APM goes right to the WebView. Unless there was an option I have overlooked, the tweak is an easy and quick fix here, basically we are looking for the osgi bundle that contains the ‘WebContent’ just like we needed to for editing that javascript file to allow us to open WebView with IE (Bug Report: TeamCenter's WebView Link Doesn't Work in IE (FIXED)) (in the case of this example: /opt/SA/Introscope10.0.0.12/product/webview/configuration/org.eclipse.osgi/bundles/93/1/.cp/WebContent). Open the index.jsp file within the WebContent folder, and make the following modification
(Please note, what I bolded and underlined above indicates a variant bundle number that will vary across different installations)
Reference:: Line 255
From:::::
<c:if test="${jspShowLoginPage == true}">
<c:if test="${apmServerEnabled == true}">
<script type="text/javascript">
if (location.hash == '' && location.search == '') {
window.location.href = '/ApmServer/';
}
</script>
</c:if>
<div style="width:100%;height:100%">
<iframe id="LoginFrame" name="LoginFrame" src=${pageContext.request.contextPath}/jsp/login.jsf></iframe>
</div>
</c:if>
To:::::::
<c:if test="${jspShowLoginPage == true}">
<c:if test="${apmServerEnabled == true}">
<script type="text/javascript">
if (location.hash == '' && location.search == '') {
// Disabled this for now... instead, lets go home
// window.location.href = '/ApmServer/';
window.location.href = '/#Home';
}
</script>
</c:if>
<div style="width:100%;height:100%">
<iframe id="LoginFrame" name="LoginFrame" src=${pageContext.request.contextPath}/jsp/login.jsf></iframe>
</div>
</c:if>