After pi is installed and upgraded: The jar resource signature certificates in the JNLP file are inconsistent.

After pi is installed and upgraded: The jar resource signature certificates in the JNLP file are inconsistent.

Pi installation or upgrade: jar resources in JNLP file are not signed by same Certificat

Problems that may occur after PI upgrade or installation. When Enterprise Services builder or integration builder is started, Jar resources in JNLP file are not signed by same Certificat is reported. The solution is as follows:

1. log on to http: // host: 5xx00/DIR/start/index. jsp-> Administration-> Java Web Start administration-> restore archives/restore archives and generate new signature

2. Clear the Java client cache

Start Java Control Panel: Start-> Run-> javaws-viewer/javaw, General-> set-> delete file

3. Check component version consistency

See note 1598282-XI/PI: jar files are signed by different certificates in 2011

Core-tools, sap_xi_esr, sap_xitool and sap_xigui

Mostly for this reason

4. Other notes

Note 1335523-FAQ: Deployment PI patches in release 7.1 and higher

Note1602945-Not able to start integration builder after SPS upgrade

Note 1309239-Configuration Wizard: PI NetWeaver initial setup