3494668 - HTTP 500 error while accessing CMC or BI launchpad after Upgrading Tomcat to non-bundled Tomcat version

After installing or upgrading to BI 4.3 SP02 or above, then deploying the web applications ( BOE, biprws ) to non-bundled Tomcat server, you may run into-   

• • HTTP 500 Error accessing CMC or BI launchpad after upgrade to BI 4.3 SP2
  • CMC or BI Launchpad fail with below message
    Http Status 500-Internal Server Error
    Internal Server Error
  • Accessing CMC/BI fails with the HTTP 500 error even without prompting for login page
  • Able to access AdminTools.

• SAP Business Intelligence Platform 4.3 Sp2 or above
• PAM supported Tomcat servers

1. Upgrade BI platform from BI 4.3 Sp1 (or lower) to BI 4.3 Sp2 or above
2. Deploy BOE.war to non-bundled Tomcat server.
3. Open CMC/BI page.
4. Receive HTTP 500 error.

The lack of the Tomcat memory.

By default , The Initial Memory pool and maximum memory pool will be 128mb and  256mb which won't be enough to open BOE application. So follow the below step :

1. Go to Start menu and type "Tomcat configuration".
2. Go to Java tab.
3. Go to Maximum memory pool field.
4. Increase the value in MB as per your usage.

3153615 - HTTP 500 error while accessing CMC or BI launchpad after deploying BI 4.3 SP02 or above [sapjce]

2232191 - Install or upgrade Tomcat bundled with SAP BI 4.x [How-To

112338 - List of Bundled Tomcat and JVM versions shipped with each SP of SAP BusinessObjects Business Intelligence Platform 4.x

Tomcat . Upgrade , Unbundled , version , 4.3 . weblogic , websphere , jboss , HTTP500 , Internal Server Error. , KBA , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , Problem