Skip to Content

I would like to flag this issue with the community and hopefully this will help prevent you from encountering the “JAR resources in JNLP file are not signed by the same certificate” error when opening the Enterprise Services Repository (ESR) or Integration Builder Directory.

Background:

SAP have changed the certificates used for launching the Process Integration (PI), Integration Builder tools. This change affects all Support Packs (SP’s) and/or Patch Levels (PL’s) delivered after 05.03.2014.

If required, you can use SAP Note 1381878 How/where to check the patch levels of your XI/PI system, to verify the release date of the relevant Software Components.

Solution:

See the SAP Note 1981572 XI/PI:Jar Files are signed by different certificates in 2014, for details on the Software Components which require patching. Please make your Basis teams aware of this change.

If your Software Components were delivered prior to the 05.03.2014 cut off date then you will not encounter this error. However, if for example, you update one component and not the other required components, you will most likely hit this issue.

It is important to ensure that all required Software Components are updated as updating only one or two will not prevent the “JAR resources in JNLP file are not signed by the same certificate” error.

Steps required after patch deployment:

After the new patches are imported, it may be necessary to clear the caches on your Java console. See Troubleshooting PI ESR and Integration Builder Logon Issues -> Java Cache

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Poitras Alexandre

    Thanks a lot for this new article.

    I fall on this bug yesterday which leads me to not be able to launch the Integration Builder or the ESR because the JAR signature cannot be recongnized.

    I’ll will try to apply these patch to my just updated system Stack 11.

    Thanks a lot !

    @+

    (0) 

Leave a Reply